| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] Re: block-* scripts multiple issues
On Mar 12, 2008, at 12:11 PM, Aleksandar Ivanisevic wrote:
Zakk <zakk-xenusers@xxxxxxxxx> writes:
I'm not sure why my mail server decided to suddenly push this
through,
but whatever!
Since it's out there, I'd like to follow up a bit and say I DID
manage
to work around the qemu-dm issue by wrapping it and doing some
queries
into the xenstore, but it's quite ugly. I also patched the block-drbd
scripts so that you specified the /dev/drbdX instead of the resource
name, so any external utilities (like xm) that check the block device
would work.
Migration works just fine; I think in that instance the block-*
scripts run as part of the migration process and THEN qemu-dm
starts?
Hmmm... qemu-dm is only used in fully virtualized domUs, right?
I'm having trouble with using drbd devices in xen 3.0.3, I'm wondering
if it is the same issue.
Here are my symptoms:
*snip*
Your problem is related. The issue is that there's a few things that
try to access the block device before any of the block-* scripts are
run. Pygrub is one of them. A quick fix is to specify a custom script
as your bootloader and in that script determine which drbd resource is
being used and explicitly set it primary. Then call the real pygrub.
That or don't use pygrub at all and set kernel/initrd/etc in your domU
config file.
I did a bit of digging through all they xend/xm python code; but I'm
not really sure how to solve this problem in the general case. I'm not
even 100% clear exactly how all those scripts get called; maybe when I
have more time I'll look at it again.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home