Olivier Le Cam wrote:
lestat thor wrote on Apr 26, 2007:
> I'm using my dom0 on a RHLE 4.4 with xen 3.0.4-1.
> My domUs work on the same O/S, and any virtual disk is composed by 5
files :
> disk = [
'file:/hawai/domains/vm113_112/boot.img,sda2,w','file:/hawai/domains/vm113_112/racine.img,sda1,w','file:/hawai/domains/vm113_112/save.img,sda3,w','file:/hawai/domains/vm113_112/logs.img,sda4,w','file:/hawai/domains/vm113_112/swap.img,sda5,w'
]
>
>
> I created some domUs on my host and they work perfectly.
>
>
> But, when I reboot my domUs, sometimes they crash ...
>
> This is the error :
>
> XENBUS: Timeout connecting to device: device/vbd/2049 (state 3)
> XENBUS: Timeout connecting to device: device/vbd/2051 (state 3)
> XENBUS: Timeout connecting to device: device/vbd/2050 (state 3)
> ...
I'm experiencing a similar problem with a debian/etch xen host. Kernel
is 2.6.18-6-xen-amd64 with the Steve Kemp's xen-utils-3.1.3-1 backport.
Devices are LVMs partitions from a SAN FC storage.
I've try with various device names, like xvd* but this didn't help.
Part of my domU config file is:
root = '/dev/xvda2 ro'
disk = [
'phy:/dev/vg_domUs/nunki-swap,xvda1,w',
'phy:/dev/vg_domUs/nunki-root,xvda2,w',
'phy:/dev/vg_domUs/nunki-var,xvda3,w',
'phy:/dev/vg_domUs/nunki-usr,xvda4,w',
'phy:/dev/vg_domUs/nunki-tmp,xvda5,w',
'phy:/dev/vg_domUs/nunki-home,xvda6,w',
'phy:/dev/vg_domUs/nunki-var-log,xvda7,w',
'phy:/dev/vg_wdatas/www,xvdb1,w!'
]
(xvdb1 is an OCFS2 clustered partition which explains the w!)
Any idea will be greatly appreciated!
Besides upgrading to RHEL 5, as fast as you can? Or to CentOS 5?
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|