Ralf Hornik Mailings
2010-May-15 19:13 UTC
[Xen-users] Upgrade to xen 4 Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Dear list, I''m running Debian Lenny with xen build from source completely. After upgrading xen to 4 with 2.6.32.12 kernel any paravirtualized domU hangs and after some minutes it breaks with: Error: Device 0 (vif) could not be connected. Hotplug scripts not working. There isn''t any log entry regarding this error. When I switch back to 3.4.2 with 2.6.18 kernel anything boots fine. Any Ideas? Thank you and best regards Ralf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ralf Hornik Mailings
2010-May-16 12:20 UTC
Re: [Xen-users] Upgrade to xen 4 Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi Mark, Mark Pryor schrieb:> Your config may have some xen objects built as modules, so your system > hangs unless they are loaded separately. > > $ sudo ls -b /sys/class/misc/ > blktap-control device-mapper evtchn gntdev network_latency pktcdvd rfkill tun > cpu_dma_latency ecryptfs fuse hpet network_throughput psaux snapshot vga_arbiter >Any of the above modules listed (xen related) exists in /sys/class/misc on my System: 2.6.32.12: # blktap-control cpu_dma_latency device-mapper evtchn gntdev mcelog microcode network_latency network_throughput nvram psaux vga_arbiter 2.6.18.8: # blktap-control device-mapper evtchn mcelog microcode nvram pci_iomul psaux The only different between the working kernel and non-working kernel is "pci_iomul" that doesn''t exist in the 2.6.32 kernel. However, I only overwrite the xen-3.4.2 with xen-4.0 userland, so can there exist some conflicting files, that need to be removed? Regards Ralf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nerijus Narmontas
2010-May-16 23:06 UTC
Re: [Xen-users] Upgrade to xen 4 Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
I had the same problem with ubuntu. Upgrading udev packaged solved the problem. On Sun, May 16, 2010 at 3:20 PM, Ralf Hornik Mailings <ralf@best.homeunix.org> wrote:> Hi Mark, > > Mark Pryor schrieb: >> >> Your config may have some xen objects built as modules, so your system >> hangs unless they are loaded separately. >> $ sudo ls -b /sys/class/misc/ >> blktap-control device-mapper evtchn gntdev network_latency >> pktcdvd rfkill tun >> cpu_dma_latency ecryptfs fuse hpet network_throughput psaux >> snapshot vga_arbiter >> > > Any of the above modules listed (xen related) exists in /sys/class/misc on > my System: > > 2.6.32.12: > # blktap-control cpu_dma_latency device-mapper evtchn gntdev mcelog > microcode network_latency network_throughput nvram psaux vga_arbiter > > 2.6.18.8: > # blktap-control device-mapper evtchn mcelog microcode nvram pci_iomul > psaux > > The only different between the working kernel and non-working kernel is > "pci_iomul" that doesn''t exist in the 2.6.32 kernel. > > However, I only overwrite the xen-3.4.2 with xen-4.0 userland, so can there > exist some conflicting files, that need to be removed? > Regards > > Ralf > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users