On 21 May 2018, at 13:23, Ales Musil <amusil@redhat.com> wrote:

On Mon, May 21, 2018 at 1:15 PM, Francesco Romani <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
To unsubscribe send an email to 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

amusil@redhat.com   IM: amusil

_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-leave@ovirt.org