1:01 a.m.
Dear All,
Our vGPU installation is progressing, though the VM is failing to start.
2018-05-16 22:57:34,328+0100 ERROR (vm/1bc9dae8) [virt.vm]
(vmId='1bc9dae8-a0ea-44b3-9103-5805100648d0') The vm start process failed
(vm:943)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872, in
_startUnderlyingVm
self._run()
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2872, in _run
dom.createWithFlags(flags)
File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line
130, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in
wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in
createWithFlags
if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed',
dom=self)
libvirtError: Cannot get interface MTU on '': No such device
That's the specific error, some other information. It seems the GPU
'allocation' of uuid against the nvidia-xx mdev type is proceeding correctly, and
the device is being created by the VM instantiation but the VM does not succeed in going
up with this error. Any other logs or information relevant to help diagnose?
Regards,
Callum
--
Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. callum@well.ox.ac.uk<mailto:callum@well.ox.ac.uk>
2:15 p.m.
On 05/17/2018 12:01 AM, Callum Smith wrote:
Dear All,
Our vGPU installation is progressing, though the VM is failing to start.
2018-05-16 22:57:34,328+0100 ERROR (vm/1bc9dae8) [virt.vm]
(vmId='1bc9dae8-a0ea-44b3-9103-5805100648d0') The vm start process
failed (vm:943)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872,
in _startUnderlyingVm
self._run()
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2872,
in _run
dom.createWithFlags(flags)
File
"/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
line 130, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/function.py",
line 92, in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in
createWithFlags
if ret == -1: raise libvirtError ('virDomainCreateWithFlags()
failed', dom=self)
libvirtError: Cannot get interface MTU on '': No such device
This is another bug, related to
https://bugzilla.redhat.com/show_bug.cgi?id=1561010.
The proper fix is on Engine side, even though we can fix it on Vdsm side too
Bests,
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
3:23 p.m.
On Mon, May 21, 2018 at 1:15 PM, Francesco Romani <fromani(a)redhat.com>
wrote:
On 05/17/2018 12:01 AM, Callum Smith wrote:
> Dear All,
>
> Our vGPU installation is progressing, though the VM is failing to start.
>
> 2018-05-16 22:57:34,328+0100 ERROR (vm/1bc9dae8) [virt.vm]
> (vmId='1bc9dae8-a0ea-44b3-9103-5805100648d0') The vm start process
> failed (vm:943)
> Traceback (most recent call last):
> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872,
> in _startUnderlyingVm
> self._run()
> File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2872,
> in _run
> dom.createWithFlags(flags)
> File
> "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
> line 130, in wrapper
> ret = f(*args, **kwargs)
> File "/usr/lib/python2.7/site-packages/vdsm/common/function.py",
> line 92, in wrapper
> return func(inst, *args, **kwargs)
> File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in
> createWithFlags
> if ret == -1: raise libvirtError ('virDomainCreateWithFlags()
> failed', dom=self)
> libvirtError: Cannot get interface MTU on '': No such device
This is another bug, related to
https://bugzilla.redhat.com/show_bug.cgi?id=1561010.
The proper fix is on Engine side, even though we can fix it on Vdsm side
too
Bests,
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Dear Callum,
can you send us also the engine.log? And which version of the engine are
you using?
Regards,
Ales.
--
ALES MUSIL
INTERN - rhv network
Red Hat EMEA <https://www.redhat.com/>
amusil(a)redhat.com IM: amusil
<https://red.ht/sig>
3:42 p.m.
Dear Ales,
4.2.3,5-1
Through extensive testing done with the help of Martin Polednik the issues with the vGPU
startup appear to be within the nvidia drivers, so continuation of that issue is now going
through nvidia.
The issue with the nics MTU appears to have gone away with the upgrade of host to the
version above.
Regards,
Callum
--
Callum Smith
Research Computing Core
Wellcome Trust Centre for Human Genetics
University of Oxford
e. callum@well.ox.ac.uk<mailto:callum@well.ox.ac.uk>
On 21 May 2018, at 13:23, Ales Musil
<amusil@redhat.com<mailto:amusil@redhat.com>> wrote:
On Mon, May 21, 2018 at 1:15 PM, Francesco Romani
<fromani@redhat.com<mailto:fromani@redhat.com>> wrote:
On 05/17/2018 12:01 AM, Callum Smith wrote:
Dear All,
Our vGPU installation is progressing, though the VM is failing to start.
2018-05-16 22:57:34,328+0100 ERROR (vm/1bc9dae8) [virt.vm]
(vmId='1bc9dae8-a0ea-44b3-9103-5805100648d0') The vm start process
failed (vm:943)
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 872,
in _startUnderlyingVm
self._run()
File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 2872,
in _run
dom.createWithFlags(flags)
File
"/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py",
line 130, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/common/function.py",
line 92, in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1099, in
createWithFlags
if ret == -1: raise libvirtError ('virDomainCreateWithFlags()
failed', dom=self)
libvirtError: Cannot get interface MTU on '': No such device
This is another bug, related to
https://bugzilla.redhat.com/show_bug.cgi?id=1561010.
The proper fix is on Engine side, even though we can fix it on Vdsm side too
Bests,
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Dear Callum,
can you send us also the engine.log? And which version of the engine are you using?
Regards,
Ales.
--
ALES MUSIL
INTERN - rhv network
Red Hat EMEA<https://www.redhat.com/>
amusil@redhat.com<mailto:amusil@redhat.com> IM: amusil
[https://www.redhat.com/files/brand/email/sig-redhat.png]<https://red.h...
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to users-leave@ovirt.org<mailto:users-leave@ovirt.org>
![https://www.redhat.com/files/brand/email/sig-redhat.png]<https://red.h...](https://www.redhat.com/files/brand/email/sig-redhat.png]%3Chttps://red.ht/sig%3E){kind=link}
3:47 p.m.
On 05/21/2018 02:42 PM, Callum Smith wrote:
Dear Ales,
4.2.3,5-1
Through extensive testing done with the help of Martin Polednik the
issues with the vGPU startup appear to be within the nvidia drivers,
so continuation of that issue is now going through nvidia.
The issue with the nics MTU appears to have gone away with the upgrade
of host to the version above.
Nice to know!
If the MTU issue reappears, please file a bug
--
Francesco Romani
Senior SW Eng., Virtualization R&D
Red Hat
IRC: fromani github: @fromanirh
2378
days inactive
2383
days old
4 comments
3 participants
participants (3)
-
Ales Musil -
Callum Smith -
Francesco Romani