Axel Thimm
2009-Sep-21 22:29 UTC
[Xen-users] RHEL5: Error: Device 0 (vif) could not be connected. Hotplug scripts not working.
Hi,
I''m running a RHEL5 guest in an RHEL5 host. I had to restart the guest
today for a kernel upgrade, but now it won''t boot anymore. The last
reboot was almost two months ago.
/etc/init.d/xendomains restart yields:
# /etc/init.d/xendomains restart
Shutting down Xen domains:Starting auto Xen domains: develError:
Device 0 (vif) could not be connected. Hotplug scripts not working.
and /var/log/xen/xend.log contains
[2009-09-22 00:20:06 xend.XendDomainInfo 19991] DEBUG (XendDomainInfo:200)
XendDomainInfo.create([''vm'', [''name'',
''devel''], [''memory'',
''1536''], [''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''vcpus'', 1],
[''uuid'',
''85142e29-9538-e15c-7615-42b15a0473fe''],
[''bootloader'', ''/usr/bin/pygrub''],
[''image'', [''linux'',
[''ramdisk'',
''/var/lib/xen/boot_ramdisk.t8-9Ww''],
[''kernel'',
''/var/lib/xen/boot_kernel.J185kA''], [''args'',
''ro root=/dev/systemdevel/root console=xvc0 rhgb quiet'']]],
[''device'', [''vbd'',
[''uname'', ''file:/var/lib/xen/images/devel''],
[''dev'', ''xvda''], [''mode'',
''w'']]], [''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''00:16:3e:02:4c:31'']]]])
[2009-09-22 00:20:06 xend.XendDomainInfo 19991] DEBUG (XendDomainInfo:312)
parseConfig: config is [''vm'', [''name'',
''devel''], [''memory'',
''1536''], [''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''vcpus'', 1],
[''uuid'',
''85142e29-9538-e15c-7615-42b15a0473fe''],
[''bootloader'', ''/usr/bin/pygrub''],
[''image'', [''linux'',
[''ramdisk'',
''/var/lib/xen/boot_ramdisk.t8-9Ww''],
[''kernel'',
''/var/lib/xen/boot_kernel.J185kA''], [''args'',
''ro root=/dev/systemdevel/root console=xvc0 rhgb quiet'']]],
[''device'', [''vbd'',
[''uname'', ''file:/var/lib/xen/images/devel''],
[''dev'', ''xvda''], [''mode'',
''w'']]], [''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''00:16:3e:02:4c:31'']]]]
[2009-09-22 00:20:06 xend.XendDomainInfo 19991] DEBUG (XendDomainInfo:417)
parseConfig: result is {''shadow_memory'': None,
''start_time'': None, ''uuid'':
''85142e29-9538-e15c-7615-42b15a0473fe'',
''on_crash'': ''restart'',
''on_reboot'': ''restart'',
''localtime'': None, ''image'':
[''linux'', [''ramdisk'',
''/var/lib/xen/boot_ramdisk.t8-9Ww''],
[''kernel'',
''/var/lib/xen/boot_kernel.J185kA''], [''args'',
''ro root=/dev/systemdevel/root console=xvc0 rhgb quiet'']],
''on_poweroff'': None, ''bootloader_args'':
None, ''cpus'': None, ''name'':
''devel'', ''backend'': [],
''vcpus'': 1, ''cpu_weight'': None,
''features'': None, ''vcpu_avail'': None,
''memory'': 1536, ''device'':
[(''vbd'', [''vbd'', [''uname'',
''file:/var/lib/xen/images/devel''], [''dev'',
''xvda''], [''mode'', ''w'']]),
(''vif'', [''vif'', [''bridge'',
''xenbr0''], [''mac'',
''00:16:3e:02:4c:31'']])], ''bootloader'':
''/usr/bin/pygrub'', ''cpu'': None,
''maxmem'': None}
[2009-09-22 00:20:06 xend.XendDomainInfo 19991] DEBUG (XendDomainInfo:1427)
XendDomainInfo.construct: None
[2009-09-22 00:20:06 xend 19991] DEBUG (balloon:143) Balloon: 1573772 KiB free;
need 2048; done.
[2009-09-22 00:20:06 xend.XendDomainInfo 19991] DEBUG (XendDomainInfo:1475)
XendDomainInfo.initDomain: 27 1.0
[2009-09-22 00:20:06 xend.XendDomainInfo 19991] DEBUG (XendDomainInfo:1514)
_initDomain:shadow_memory=0x0, maxmem=0x600, memory=0x600.
[2009-09-22 00:20:06 xend 19991] DEBUG (balloon:143) Balloon: 1573764 KiB free;
need 1572864; done.
[2009-09-22 00:20:06 xend 19991] INFO (image:137) buildDomain os=linux dom=27
vcpus=1
[2009-09-22 00:20:06 xend 19991] DEBUG (image:206) domid = 27
[2009-09-22 00:20:06 xend 19991] DEBUG (image:207) memsize = 1536
[2009-09-22 00:20:06 xend 19991] DEBUG (image:208) image =
/var/lib/xen/boot_kernel.J185kA
[2009-09-22 00:20:06 xend 19991] DEBUG (image:209) store_evtchn = 1
[2009-09-22 00:20:06 xend 19991] DEBUG (image:210) console_evtchn = 2
[2009-09-22 00:20:06 xend 19991] DEBUG (image:211) cmdline = ro
root=/dev/systemdevel/root console=xvc0 rhgb quiet
[2009-09-22 00:20:06 xend 19991] DEBUG (image:212) ramdisk =
/var/lib/xen/boot_ramdisk.t8-9Ww
[2009-09-22 00:20:06 xend 19991] DEBUG (image:213) vcpus = 1
[2009-09-22 00:20:06 xend 19991] DEBUG (image:214) features =
[2009-09-22 00:20:06 xend 19991] DEBUG (blkif:27) exception looking up device
number for xvda: [Errno 2] No such file or directory:
''/dev/xvda''
[2009-09-22 00:20:06 xend 19991] DEBUG (DevController:110) DevController:
writing {''virtual-device'': ''51712'',
''device-type'': ''disk'',
''protocol'': ''x86_64-abi'',
''backend-id'': ''0'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/27/51712''} to
/local/domain/27/device/vbd/51712.
[2009-09-22 00:20:06 xend 19991] DEBUG (DevController:112) DevController:
writing {''domain'': ''devel'',
''frontend'': ''/local
The config file /etc/xen/devel contains:
# Automatically generated xen config file
name = "devel"
memory = "1536"
#memory = "512"
disk = [ ''file:/var/lib/xen/images/devel,xvda,w'', ]
vif = [ ''mac=00:16:3e:02:4c:31, bridge=xenbr0'', ]
uuid = "85142e29-9538-e15c-7615-42b15a0473fe"
bootloader="/usr/bin/pygrub"
vcpus=1
on_reboot = ''restart''
on_crash = ''restart''
#kernel = "/boot/vmlinuz-2.6.18-128.el5xen"
#ramdisk = "/boot/initrd-2.6.18-128.el5xenU.img"
The relevant components are:
(running) kernel on host: 2.6.18-128.1.1.el5xen
xen on host: xen-3.0.3-80.el5_3.3.x86_64
I can''t retrieve the data on the guest, but it is the latest
kernels/xen as offered by RHEL 5.4
I tried commenting the vif line to see whether the xm create moves on,
but then it fails at some vbd error. The line with the "exception
looking up device number for xvda:" in the logs was also present when
xen was working.
Thanks!
--
Axel.Thimm at ATrpms.net
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users