thr3ads.net - Xen users - [Xen-users] Paravirt VM - Second Disk not working [Sep 2009]

If this information is useful, please help other people find it:
Share via:

Robert Dunkley

2009-Sep-16 10:03 UTC

[Xen-users] Paravirt VM - Second Disk not working

Hi All,

I have a paravirt VM with two hard disks, the boot drive xvda works fine
but the data drive xvdb does not seem to detect at all. I have looked
into this and full logs are below but I cannot find what is causing the
timeout on connect. Feedback from Dom0 for both devices looks identical,
the only error I get is the timeout in DomU. Does anyone know what might
be causing this?

Thanks,

Rob


DomU Log Extract:
XENBUS: Device with no driver: device/vbd/51712
XENBUS: Device with no driver: device/vbd/51728
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/vif/1
XENBUS: Device with no driver: device/console/0
Registering block device major 202
 xvda: xvda1 xvda2
XENBUS: Timeout connecting to device: device/vbd/51728 (state 6)


Dom 0 Log extract:
[2009-09-16 10:32:07 31509] DEBUG (XendDomainInfo:89)
XendDomainInfo.create([\047vm\047, [\047name\047, \047jaczimbra\047],
[\047memory\047, 2048], [\047maxmem\047, 2048], [\047vcpus\047, 1],
[\047on_xend_start\047, \047ignore\047], [\047on_xend_stop\047,
\047ignore\047], [\047cpus\047, [\0474\047]], [\047bootloader\047,
\047/usr/bin/pygrub\047], [\047bootloader_args\047, \047-q\047],
[\047image\047, [\047linux\047]], [\047device\047, [\047vbd\047,
[\047uname\047, \047phy:/dev/drbd22\047], [\047dev\047, \047xvda\047],
[\047mode\047, \047w\047]]], [\047device\047, [\047vbd\047,
[\047uname\047, \047phy:/dev/drbd23\047], [\047dev\047, \047xvdb\047],
[\047mode\047, \047w\047]]], [\047device\047, [\047vif\047,
[\047bridge\047, \047dirtybr\047], [\047mac\047,
\04700:16:3e:44:d3:c5\047]]], [\047device\047, [\047vif\047,
[\047bridge\047, \047lanbr\047], [\047mac\047,
\04700:16:3e:44:d3:c6\047]]], [\047device\047, [\047vkbd\047]],
[\047device\047, [\047vfb\047, [\047vncpasswd\047, \047XXXXXXXX\047],
[\047type\047, \047vnc\047], [\047vncdisplay\047, \04723\047],
[\047xauthority\047, \047/root/.Xauthority\047]]]])

[2009-09-16 10:32:13 31509] INFO (XendDomainInfo:1900) createDevice: vbd
: {\047uuid\047: \047d6222ac7-c4a4-2dc2-f84d-56edc9452ea4\047,
\047bootable\047: 1, \047driver\047: \047paravirtualised\047,
\047dev\047: \047xvda\047, \047uname\047: \047phy:/dev/drbd22\047,
\047mode\047: \047w\047}
[2009-09-16 10:32:13 31509] INFO (XendDomainInfo:1900) createDevice: vbd
: {\047uuid\047: \0475b851fc7-83cb-c8ae-f9d8-d286db37ff0f\047,
\047bootable\047: 0, \047driver\047: \047paravirtualised\047,
\047dev\047: \047xvdb\047, \047uname\047: \047phy:/dev/drbd23\047,
\047mode\047: \047w\047}

[2009-09-16 10:32:13 31509] DEBUG (DevController:124) DevController:
writing {\047domain\047: \047jaczimbra\047, \047frontend\047:
\047/local/domain/2926/device/vbd/51728\047, \047uuid\047:
\0475b851fc7-83cb-c8ae-f9d8-d286db37ff0f\047, \047dev\047: \047xvdb\047,
\047state\047: \0471\047, \047params\047: \047/dev/drbd23\047,
\047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047:
\0472926\047, \047type\047: \047phy\047} to
/local/domain/0/backend/vbd/2926/51728.

[2009-09-16 10:32:13 31509] DEBUG (DevController:124) DevController:
writing {\047domain\047: \047jaczimbra\047, \047frontend\047:
\047/local/domain/2926/device/vbd/51712\047, \047uuid\047:
\047d6222ac7-c4a4-2dc2-f84d-56edc9452ea4\047, \047dev\047: \047xvda\047,
\047state\047: \0471\047, \047params\047: \047/dev/drbd22\047,
\047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047:
\0472926\047, \047type\047: \047phy\047} to
/local/domain/0/backend/vbd/2926/51712.

[2009-09-16 10:32:13 31509] DEBUG (DevController:122) DevController:
writing {\047virtual-device\047: \04751712\047, \047device-type\047:
\047disk\047, \047protocol\047: \047x86_64-abi\047, \047backend-id\047:
\0470\047, \047state\047: \0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/2926/51712\047} to
/local/domain/2926/device/vbd/51712.

[2009-09-16 10:32:13 31509] DEBUG (DevController:124) DevController:
writing {\047domain\047: \047jaczimbra\047, \047frontend\047:
\047/local/domain/2926/device/vbd/51712\047, \047uuid\047:
\047d6222ac7-c4a4-2dc2-f84d-56edc9452ea4\047, \047dev\047: \047xvda\047,
\047state\047: \0471\047, \047params\047: \047/dev/drbd22\047,
\047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047:
\0472926\047, \047type\047: \047phy\047} to
/local/domain/0/backend/vbd/2926/51712.

[2009-09-16 10:32:13 31509] DEBUG (DevController:122) DevController:
writing {\047virtual-device\047: \04751728\047, \047device-type\047:
\047disk\047, \047protocol\047: \047x86_64-abi\047, \047backend-id\047:
\0470\047, \047state\047: \0471\047, \047backend\047:
\047/local/domain/0/backend/vbd/2926/51728\047} to
/local/domain/2926/device/vbd/51728.

[2009-09-16 10:32:13 31509] DEBUG (DevController:124) DevController:
writing {\047domain\047: \047jaczimbra\047, \047frontend\047:
\047/local/domain/2926/device/vbd/51728\047, \047uuid\047:
\0475b851fc7-83cb-c8ae-f9d8-d286db37ff0f\047, \047dev\047: \047xvdb\047,
\047state\047: \0471\047, \047params\047: \047/dev/drbd23\047,
\047mode\047: \047w\047, \047online\047: \0471\047, \047frontend-id\047:
\0472926\047, \047type\047: \047phy\047} to
/local/domain/0/backend/vbd/2926/51728.

[2009-09-16 10:32:15 31509] DEBUG (DevController:171) Waiting for 51712.

[2009-09-16 10:32:15 31509] DEBUG (DevController:656)
hotplugStatusCallback
/local/domain/0/backend/vbd/2926/51712/hotplug-status.

[2009-09-16 10:32:16 31509] DEBUG (DevController:171) Waiting for 51728.

[2009-09-16 10:32:16 31509] DEBUG (DevController:656)
hotplugStatusCallback
/local/domain/0/backend/vbd/2926/51728/hotplug-status.


The SAQ Group

Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
SAQ is the trading name of SEMTEC Limited. Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219

SAQ Group Delivers high quality, honestly priced communication and I.T. services
to UK Business.

Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit :
Backups : Managed Networks : Remote Support.

ISPA Member


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Fajar A. Nugraha

2009-Sep-16 10:48 UTC

head link

Re: [Xen-users] Paravirt VM - Second Disk not working

On Wed, Sep 16, 2009 at 5:03 PM, Robert Dunkley <Robert@saq.co.uk>
wrote:> Hi All,
>
> I have a paravirt VM with two hard disks, the boot drive xvda works fine
> but the data drive xvdb does not seem to detect at all. I have looked
> into this and full logs are below but I cannot find what is causing the
> timeout on connect. Feedback from Dom0 for both devices looks identical,
> the only error I get is the timeout in DomU. Does anyone know what might
> be causing this?
> [\047image\047, [\047linux\047]], [\047device\047, [\047vbd\047,
> [\047uname\047, \047phy:/dev/drbd22\047], [\047dev\047, \047xvda\047],
> [\047mode\047, \047w\047]]], [\047device\047, [\047vbd\047,
> [\047uname\047, \047phy:/dev/drbd23\047], [\047dev\047, \047xvdb\047],
You''re using drbd? Is /dev/drbd23 primary on that node? Is it
accessible from dom0 (e.g. using fdisk, mount, etc.)?

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Robert Dunkley

2009-Sep-16 14:10 UTC

head link

RE: [Xen-users] Paravirt VM - Second Disk not working

Hi Fajar,


Thanks for the reply.

I''m actually using DRBD along with Jefferson Ogata''s wrapper
here:
http://www.antibozo.net/xen/qemu-dm.drbd

The wrapper does change both DRBD resources (DRBD22 and DRBD23) to
primary when you start the VM but the second disk never turns up in xm
top and VM complains of a timeout as stated below. 

I found removing the second disk from the VM config file and adding it
manually with hotplug immediately after starting the VM works, eg::
xm create vmname
drbdadm primary xendrbd23
xm block-attach vmname phy:/dev/drbd23 /dev/xvdb ''w''


Rob

-----Original Message-----
From: Fajar A. Nugraha [mailto:fajar@fajar.net] 
Sent: 16 September 2009 11:48
To: Robert Dunkley
Cc: Xen User-List
Subject: Re: [Xen-users] Paravirt VM - Second Disk not working

On Wed, Sep 16, 2009 at 5:03 PM, Robert Dunkley <Robert@saq.co.uk>
wrote:> Hi All,
>
> I have a paravirt VM with two hard disks, the boot drive xvda works
fine> but the data drive xvdb does not seem to detect at all. I have looked
> into this and full logs are below but I cannot find what is causing
the> timeout on connect. Feedback from Dom0 for both devices looks
identical,> the only error I get is the timeout in DomU. Does anyone know what
might> be causing this?
> [\047image\047, [\047linux\047]], [\047device\047, [\047vbd\047,
> [\047uname\047, \047phy:/dev/drbd22\047], [\047dev\047, \047xvda\047],
> [\047mode\047, \047w\047]]], [\047device\047, [\047vbd\047,
> [\047uname\047, \047phy:/dev/drbd23\047], [\047dev\047, \047xvdb\047],
You''re using drbd? Is /dev/drbd23 primary on that node? Is it
accessible from dom0 (e.g. using fdisk, mount, etc.)?

-- 
Fajar

The SAQ Group

Registered Office: 18 Chapel Street, Petersfield, Hampshire GU32 3DZ
SAQ is the trading name of SEMTEC Limited. Registered in England & Wales
Company Number: 06481952

http://www.saqnet.co.uk AS29219

SAQ Group Delivers high quality, honestly priced communication and I.T. services
to UK Business.

Broadband : Domains : Email : Hosting : CoLo : Servers : Racks : Transit :
Backups : Managed Networks : Remote Support.

ISPA Member


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Fajar A. Nugraha

2009-Sep-16 14:23 UTC

head link

Re: [Xen-users] Paravirt VM - Second Disk not working

On Wed, Sep 16, 2009 at 9:10 PM, Robert Dunkley <Robert@saq.co.uk>
wrote:> I''m actually using DRBD along with Jefferson Ogata''s
wrapper here:
> http://www.antibozo.net/xen/qemu-dm.drbd
>
> The wrapper does change both DRBD resources (DRBD22 and DRBD23) to
> primary when you start the VM but the second disk never turns up in xm
> top and VM complains of a timeout as stated below.
>
> I found removing the second disk from the VM config file and adding it
> manually with hotplug immediately after starting the VM works, eg::
> xm create vmname
> drbdadm primary xendrbd23
> xm block-attach vmname phy:/dev/drbd23 /dev/xvdb ''w''
My guess is that the wrapper script didn''t work correctly for two
disks. I actually tried something similar using RHEL5/Xen
3.4.1/drbd83, but found out drbd''s block-drbd didn''t work
properly
with pygrub. Perhaps there are more files to edit, I''m not sure. I
ended up making the resource primary on both nodes and use
phy:/dev/drbd/by-res/...

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Sep 2009 - Paravirt VM - Second Disk not working

[Xen-users] Paravirt VM - Second Disk not working

Re: [Xen-users] Paravirt VM - Second Disk not working

RE: [Xen-users] Paravirt VM - Second Disk not working

Re: [Xen-users] Paravirt VM - Second Disk not working