https://bugzilla.novell.com/show_bug.cgi?id=865682
https://bugzilla.novell.com/show_bug.cgi?id=865682#c9
--- Comment #9 from Mike Latimer
I can save you the trouble.
With the definition disk = [ 'drbd:test.root,sda1,w', 'drbd:test.swap,sda2,w', ] The block-drbd script is never called
That's not what is happening in my environment. The block-drdb script is executing just fine. However, you do need the fix Jim mentioned in comment #1. With that in place, the block-attach is still failing - but due to drbdadm segfaulting in two places. If I replace those commands with the hard-coded correct response (in my system), the disk attaches properly and the VM is started. (At least in my environment.)
If the disk definition is this: (completely bypassing drbd) the guest starts up. But only if I make the drbd device primary before starting the guest: disk = [ 'phy:/dev/drbd/by-res/test.root/0,sda1,w', 'phy:/dev/drbd/by-res/test.swap/0,sda2,w' ]
This makes sense, as Xen would not even know about drbd with this setup.
This is the only way I can get block-drbd script to run, but the guest doesn't start up. So it looks like xl is having trouble parsing the stuff after the drbd: directive. Maybe it is expecting /some/sort/of/path instead of just the test.root drbd device.
One difference between your environment and mine is that I am not using drbd for root. This changes the startup a bit, but still leaves me in a situation where xvdb1 cannot be attached. It might be interesting to change your disk configuration to something like: disk = [ 'phy:/dev/drbd/by-res/test.root/0,sda1,w', 'drbd:test.swap,xvda2,w', ] Just to see if the system logs end up closer to mine... Either way, the key to tracking this down is a debug xen-hotpug log. Please add 'set -x' at the beginning of /etc/xen/scripts/block-drbd, try the test again (with 'drbd:test.root' syntax), and attach /var/log/xen/xen-hotplug.log after it fails. If there is nothing in this log when using the correct syntax, try it again using your /dev/drbd/... syntax and send me the debug log from that run. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.