Re: [Xen-users] Re: can't boot xen vm with drbd

[Bart Coninckx <bart.coninckx@xxxxxxxxxx>]

On Monday 01 November 2010 12:22:11 Mike Sievers wrote:
> ... I just read this:
> 
> disk = [ 'drbd:*resource*,xvda,w' ]
> 
> 
>    -
> 
>    pygrub from Xen 3.3 forward, and the domUloader.py version that ships
>    with SLES 11 *do* support this syntax.
> 
> 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

Mike, don't get it: the DRBD syntax is supported yet you need another way? 
Anyway, Pacemaker or Heartbeat can take care of this. If you create a resource 
for DRBD and then one for Xen and the collocate and order them, the DRBD 
resource is activated on the resource you want the Xen guest to start on or 
migrate to.

B.

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