can't boot xen vm with drbd

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

can't boot xen vm with drbd

Mike Sievers
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
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: can't boot xen vm with drbd

Mike Sievers
... 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 <[hidden email]>
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
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: can't boot xen vm with drbd

Bart Coninckx
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 <[hidden email]>
>
> > 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
[hidden email]
http://lists.xensource.com/xen-users
Reply | Threaded
Open this post in threaded view
|

Re: can't boot xen vm with drbd

khris4
In order to get it work correctly you must use the kernel & ramdisk directive in the domU config like this

name = "atmail"
memory = "1024"
vcpus=1
cpus = ["2-3"] # VCPU0 runs on CPU2, VCPU1 runs on CPU3
-------------------------------------------------------Start Here ---------------------------------------------------------------------
kernel = '/boot/test/vmlinuz-2.6.18-194.8.1.el5xen'
ramdisk = '/boot/test/initrd-2.6.18-194.8.1.el5xen.img'
root    = '/dev/VolGroup00/LogVol02'
disk = [ 'drbd:atmail,xvda,w' ]
-------------------------------------------------------End Here  ---------------------------------------------------------------------
vif = [ 'mac=00:16:3E:29:13:AE,bridge=xenbr0' ]
vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncdisplay=1' ]
on_reboot = 'restart'
on_crash = 'restart'