Bug ID 1095690
Summary virt-manager fails to start existing VM
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware x86-64
OS Other
Status NEW
Severity Major
Priority P5 - None
Component Xen
Assignee xen-bugs@suse.de
Reporter conde.philippe@skynet.be
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Hello,

Some month ago I created a VM;
Host is tumbleweed current on a HP Proliant.
After the last update (via zypper dup) i vannot more start the vm

I receive this error
Error starting domain: internal error:
libxenlight failed  to create new domain 'vmsamba'

Details 
Error starting domain: internal error: libxenlight failed to create new domain
'vmsamba'

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 89, in
cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 125, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/libvirtobject.py", line 82, in
newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1508, in startup
    self._backend.create()
  File "/usr/lib64/python3.6/site-packages/libvirt.py", line 1069, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: libxenlight failed to create new domain
'vmsamba'

the VM is also tumbleweed.

in journalctl I have
Jun 03 15:07:53 hpprol2 libvirtd[1682]: 2018-06-03 13:07:53.688+0000: 1694:
error : virConnectGetCPUModelNames:1035 : this function is not supported by the
connection driver: virConnectGetCPUModelNames
Jun 03 15:07:54 hpprol2 libvirtd[1682]: 2018-06-03 13:07:54.529+0000: 1694:
error : virDomainGetMetadata:8053 : this function is not supported by the
connection driver: virDomainGetMetadata
Jun 03 15:07:54 hpprol2 libvirtd[1682]: 2018-06-03 13:07:54.584+0000: 1698:
error : virDomainListAllSnapshots:520 : this function is not supported by the
connection driver: virDomainListAllSnapshots
Jun 03 15:07:55 hpprol2 wicked[26339]: ifcfg-br1: bridge validation: bridge
forward-delay is out of supported range (2.0-30.0)
Jun 03 15:07:55 hpprol2 wicked[26349]: ifcfg-br1: bridge validation: bridge
forward-delay is out of supported range (2.0-30.0)
Jun 03 15:07:55 hpprol2 wicked[26357]: ifcfg-br1: bridge validation: bridge
forward-delay is out of supported range (2.0-30.0)
Jun 03 15:07:55 hpprol2 wicked[26365]: ifcfg-br1: bridge validation: bridge
forward-delay is out of supported range (2.0-30.0)
Jun 03 15:08:06 hpprol2 root[26410]: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/4/2080
Jun 03 15:08:06 hpprol2 root[26412]: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/4/2096
Jun 03 15:08:06 hpprol2 root[26423]: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/4/2112
Jun 03 15:08:06 hpprol2 root[26443]: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/4/2128
Jun 03 15:08:07 hpprol2 root[26550]: /etc/xen/scripts/block: Writing
backend/vbd/4/2080/physical-device 8:21 to xenstore.
Jun 03 15:08:07 hpprol2 root[26552]: /etc/xen/scripts/block: Writing
backend/vbd/4/2080/physical-device-path /dev/sdc1 to xenstore.
Jun 03 15:08:07 hpprol2 root[26554]: /etc/xen/scripts/block: Writing
backend/vbd/4/2080/hotplug-status connected to xenstore.
Jun 03 15:08:07 hpprol2 root[26608]: /etc/xen/scripts/block: Writing
backend/vbd/4/2096/physical-device 8:22 to xenstore.
Jun 03 15:08:07 hpprol2 root[26610]: /etc/xen/scripts/block: Writing
backend/vbd/4/2096/physical-device-path /dev/sdc2 to xenstore.
Jun 03 15:08:07 hpprol2 root[26612]: /etc/xen/scripts/block: Writing
backend/vbd/4/2096/hotplug-status connected to xenstore.
Jun 03 15:08:08 hpprol2 root[26664]: /etc/xen/scripts/block: Writing
backend/vbd/4/2128/physical-device 8:24 to xenstore.
Jun 03 15:08:08 hpprol2 root[26666]: /etc/xen/scripts/block: Writing
backend/vbd/4/2128/physical-device-path /dev/sdc4 to xenstore.
Jun 03 15:08:08 hpprol2 root[26668]: /etc/xen/scripts/block: Writing
backend/vbd/4/2128/hotplug-status connected to xenstore.
Jun 03 15:08:08 hpprol2 root[26718]: /etc/xen/scripts/block: Writing
backend/vbd/4/2112/physical-device 8:23 to xenstore.
Jun 03 15:08:08 hpprol2 root[26720]: /etc/xen/scripts/block: Writing
backend/vbd/4/2112/physical-device-path /dev/sdc3 to xenstore.
Jun 03 15:08:08 hpprol2 root[26722]: /etc/xen/scripts/block: Writing
backend/vbd/4/2112/hotplug-status connected to xenstore.
Jun 03 15:08:09 hpprol2 systemd-udevd[26730]: link_config: autonegotiation is
unset or enabled, the speed and duplex are not writable.
Jun 03 15:08:09 hpprol2 systemd-udevd[26730]: Could not generate persistent MAC
address for vif4.0-emu: No such file or directory
Jun 03 15:08:09 hpprol2 libvirtd[1682]: 2018-06-03 13:08:09.266+0000: 1694:
error : virFileReadAll:1420 : Failed to open file
'/sys/class/net/vif4.0-emu/operstate': No such file or directory
Jun 03 15:08:09 hpprol2 libvirtd[1682]: 2018-06-03 13:08:09.266+0000: 1694:
error : virNetDevGetLinkInfo:2552 : unable to read:
/sys/class/net/vif4.0-emu/operstate: No such file or directory
Jun 03 15:08:09 hpprol2 root[26758]: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/4/2080
Jun 03 15:08:09 hpprol2 root[26771]: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/4/2096
Jun 03 15:08:09 hpprol2 root[26794]: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/4/2112
Jun 03 15:08:09 hpprol2 root[26810]: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/4/2128
Jun 03 15:08:11 hpprol2 libvirtd[1682]: 2018-06-03 13:08:11.658+0000: 1698:
error : libxlDomainStart:1322 : internal error: libxenlight failed to create
new domain 'vmsamba'

I attach also the vm defintion  (vmsamba.xml)
Regards
Philippe


You are receiving this mail because: