Thanks for the reply.
I'm actually using DRBD along with Jefferson Ogata's wrapper here:
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'
From: Fajar A. Nugraha [mailto:fajar@xxxxxxxxx]
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@xxxxxxxxx>
> Hi All,
> I have a paravirt VM with two hard disks, the boot drive xvda works
> 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
> timeout on connect. Feedback from Dom0 for both devices looks
> the only error I get is the timeout in DomU. Does anyone know what
> 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.)?
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
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.
Xen-users mailing list