[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-users] Re: can't boot xen vm with drbd
- To: Xen-users@xxxxxxxxxxxxxxxxxxx
- From: Mike Sievers <saturngeist@xxxxxxxxxxxxxx>
- Date: Mon, 1 Nov 2010 12:22:11 +0100
- Cc:
- Delivery-date: Mon, 01 Nov 2010 04:23:37 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=ja4YGpAcrSSUnOs0BiQbB4vJu8yeQB5/NQGYpjc2/LqRkeRhwn71OyKNJon7iQb/lr yDnIKXl0+tiocdCbzzoiB0PmVO+7X61wzRQAgBFplJAvptsVvNBkHxj3bhI4jy1HYbEI iqskYenL52D2qtDpzVWMZmBFg+i3Ov0YnLXkI=
- List-id: Xen user discussion <xen-users.lists.xensource.com>
... I just read this:
disk = [ 'drbd:resource,xvda,w' ]
Under these circumstances, you must use the traditional
phy: device syntax and the DRBD device name
that is associated with your resource, not the resource name.
That, however, requires that you manage DRBD
state transitions outside Xen, which is a less flexible
approach than that provided by the drbd
resource type.
:-( any other ideas how to handle this?
2010/11/1 Mike Sievers <saturngeist@xxxxxxxxxxxxxx>
Hello List,
I need a configuration with 2 Server and live migration.
* so I need drbd ?!
I have changed the xml file to:
<disk type='block' device='disk'>
<driver name='drbd'/>
<source dev='test'/>
<target dev='xvda' bus='xen'/>
</disk>
But now I can't boot anymore.
<bootloader>/usr/bin/pygrub</bootloader>
<bootloader_args>-q</bootloader_args>
Who can help?
Mike
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
