|
Bugzilla – Full Text Bug Listing |
| Summary: | virt-manager fails to start existing VM | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Philippe Condé <conde.philippe> |
| Component: | Xen | Assignee: | Charles Arnold <carnold> |
| Status: | RESOLVED UPSTREAM | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | conde.philippe |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
VM definition
qemu-dm-vmsamba.log vmsamba.log output ifconfig output of fdisk -l ip addr output settings for the VM |
||
Created attachment 772207 [details]
VM definition
*** Bug 1095690 has been marked as a duplicate of this bug. *** *** Bug 1095691 has been marked as a duplicate of this bug. *** *** Bug 1095692 has been marked as a duplicate of this bug. *** *** Bug 1095693 has been marked as a duplicate of this bug. *** *** Bug 1095694 has been marked as a duplicate of this bug. *** Please also attach, /var/log/xen/qemu-dm-vmsamba.log and /var/log/libvirt/libxl/vmsamba.log Thanks Created attachment 773058 [details]
qemu-dm-vmsamba.log
Created attachment 773059 [details]
vmsamba.log
current vmsamba.log has a size of 0.
i attach the last log with a size.
More sanity check questions. The VM uses br0 for a bridge. Does br0 still exist as an interface on your host? (output of 'ip addr') Do the four physical devices /dev/sdc1-4 also still exist after the upgrade? Created attachment 773308 [details]
output ifconfig
The br0 bridge is active
there are 2 alias used for apache2 connection (https)
Created attachment 773309 [details]
output of fdisk -l
there is a warning at the end of /dev/sdc1-> /dev/sdc4 list
Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
Created attachment 773315 [details]
ip addr output
Hello;
I tried today to recreate the VM.
I have removed the old VM , define the new VM but when I start the begin installation I receive the same error
"Unable to complete install: 'internal error: libxenlight failed to create new domain 'opensusetumbleweed''
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/create.py", line 2633, in _do_async_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 527, in start_install
doboot, transient)
File "/usr/share/virt-manager/virtinst/guest.py", line 463, in _create_guest
domain = self.conn.createXML(install_xml or final_xml, 0)
File "/usr/lib64/python3.6/site-packages/libvirt.py", line 3697, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirt.libvirtError: internal error: libxenlight failed to create new domain 'opensusetumbleweed'
"
I have done a zypper dup today so the system at snapshot VERSION="20180707"
the same error occurs if I start the build with virt-manager or with YaST
I'll link a snapshot of the VM settings
Regards
Philippe Condé
Created attachment 776588 [details]
settings for the VM
Hello, Updated Tumbleweed to snapshot 20180726 but still unable to create a Xen VM. Same error about libxenlight. in /var/log/libvirt/libxl/libxl-driver.log I have these messages "2018-07-28 09:19:15.018+0000: libxl: libxl_dm.c:2464:device_model_spawn_outcome: Domain 2:domain 2 device model: spawn failed (rc=-3) 2018-07-28 09:19:15.019+0000: libxl: libxl_create.c:1557:domcreate_devmodel_started: Domain 2:device model did not start: -3 2018-07-28 09:19:15.022+0000: libxl: libxl_dm.c:2578:kill_device_model: Device Model already exited 2018-07-28 09:20:28.495+0000: libxl: libxl_dm.c:2464:device_model_spawn_outcome: Domain 3:domain 3 device model: spawn failed (rc=-3) 2018-07-28 09:20:28.495+0000: libxl: libxl_create.c:1557:domcreate_devmodel_started: Domain 3:device model did not start: -3 2018-07-28 09:20:28.500+0000: libxl: libxl_dm.c:2578:kill_device_model: Device Model already exited " Regards Philippe hello, problem solved with snapshot 20180815 Regards Philippe |
Hello, Some month ago I created a VM; Host is tumbleweed current on a HP Proliant. After the last update (via zypper dup) i cannot 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 definition (vmsamba.xml) Regards Philippe