Leeman Strout
2006-Jun-13 19:29 UTC
[Xen-users] Problems: Upgrading debianbase.de Xen 3.0.1 to debian Xen 3.0.2 (all on Sid)
I had some trouble with getting Xen 3.0.2 Dom0 running on my Sid box using the debian sid packages, however ironed that out. udev and initrd issues were the problem. Now I am trying to get my DomU running. So here''s the logging I get: Here''s udevmonitor interspersed with the responses from xm create -c mydomu: Using config file "mydomu". UEVENT[1150226231.809348] add@/devices/xen-backend/vbd-17-2049 UEVENT[1150226231.825436] add@/devices/xen-backend/vbd-17-2050 UEVENT[1150226231.845511] add@/devices/xen-backend/vif-17-0 UEVENT[1150226231.845577] add@/class/net/vif17.0 UEVENT[1150226231.845595] online@/devices/xen-backend/vif-17-0 UDEV [1150226231.921533] add@/devices/xen-backend/vbd-17-2049 UDEV [1150226231.928825] add@/devices/xen-backend/vbd-17-2050 UDEV [1150226231.936397] add@/devices/xen-backend/vif-17-0 UDEV [1150226231.943957] add@/class/net/vif17.0 UDEV [1150226231.966431] online@/devices/xen-backend/vif-17-0 Error: Device 0 (vif) could not be connected. Hotplug scripts not working. UEVENT[1150226242.057370] offline@/devices/xen-backend/vif-17-0 UDEV [1150226242.111061] offline@/devices/xen-backend/vif-17-0 UEVENT[1150226242.129020] remove@/class/net/vif17.0 UEVENT[1150226242.129099] remove@/devices/xen-backend/vif-17-0 UEVENT[1150226242.129118] remove@/devices/xen-backend/vbd-17-2049 UEVENT[1150226242.129137] remove@/devices/xen-backend/vbd-17-2050 UDEV [1150226242.129870] remove@/class/net/vif17.0 UDEV [1150226242.184033] remove@/devices/xen-backend/vif-17-0 UDEV [1150226242.194571] remove@/devices/xen-backend/vbd-17-2049 UDEV [1150226242.203851] remove@/devices/xen-backend/vbd-17-2050 the vif and vbd numbers are incremented every time I try to run my domU Here''s mydomu config: kernel = "/boot/vmlinuz-2.6.16-2-xen-686" memory = 512 name = "mydomu" root = "/dev/sda1 ro" vif = [''mac=00:16:3E:42:42:01, bridge=xenbr0''] disk = [ ''phy:xen_vg/mydomu-root,sda1,w'', ''phy:xen_vg/mydomu-swap,sda2,w'' ] #dhcp = "dhcp" netmask = "10.2.255.255" gateway = "10.2.10.1" This worked when I was on 3.0.1 from debianbase.de. And xend.log looks the same right up until the first hotplugStatusCallback line. There''s several similar entries in the log from a working domU boot, there''s only the first one on the broken domU boot, then the log stops. Any more info I can provide to get some help here? Leeman _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users