Using the new 3.0.0 kernel equipped to host a dom0, running established vms fails due to missing network connectivity by vif devices. Reproducible: Always Steps to Reproduce: 1. Prepare a xen equipped kernel to run a gentoo dom0. 2. Boot the system 3. Boot a xen vm. Actual Results: Due to a timeout period allowed, the vm does in fact run effectively during this period. On timing out, the vm is killed. Missing vif device. Expected Results: To boot the vm. The reports from xen.org is a mixture of reports concerning this issue. It states the kernel can't yet boot vms, however the kernel did manage it until xm killed the vm upon timing out. This network vif device appears identical to one I observed around kernel 2.6.32 period when a udev update caused the misfire, and it was rectified by a patch at the time.
Created attachment 281209 [details] my emerge --info
Error starting domain: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.') Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc vm.startup() File "/usr/share/virt-manager/virtManager/domain.py", line 1118, in startup self._backend.create() File "/usr/lib64/python2.7/site-packages/libvirt.py", line 457, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: POST operation failed: xend_post: error from xen daemon: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.')
Maybe "dmesg" output could be needed
Pacho; dmesg never receives any xen error info, but instead here is the xend.log
Created attachment 281351 [details] the current xend.log
Happily fixed via upstream http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1773. The kernel is not flawed. Simply need to add a missing setting and tweak a few things. CONFIG_XEN_BLKDEV_BACKEND need be set. This is tricky. The entry under devices -------------- Block devices is actually after an entry including xen its name, but does not have xen in its name. Also needed to reset (total_available_memory 0) to (total_available_memory [MyRamValue]) and also dom0_mem=<value? in the kernel line in grub.
