Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Florian Haas wrote:
>> I am trying to setup a DRBD backend for a Xen virtual machine (VM) using
>> the "block-drbd" script included in the 8.0.6 release, but find that my
>> drbd device is moved to a secondary state on both servers after I finish
>> the initial OS install of the VM on the drbd device.
>
> The fact that the device becomes Secondary after shutting down your domU is by
> design. Since a domU installation process normally shuts down your
> freshly-installed domU before firing it up again immediately afterwards, it
> is normal to see a couple of DRBD state transitions in the process.
Ah, OK. Makes sense.
>> As a result, I
>> cannot startup the VM after the OS install and instead see this error:
>>
>> [root at radm012d xen]# xm create rusr007d -c
>> Using config file "./rusr007d".
>> No handlers could be found for logger "xend"
>> Error: Disk isn't accessible
>
> I am surmising that the "Disk isn't accessible" message comes from your pygrub
> bootloader, not xend itself. Can you post your full Xen domU config for our
> reference?
Sure, here it is:
[root at radm012d ~]# cat /etc/xen/rusr007d
name = "rusr007d"
memory = "512"
disk = [ 'drbd:r0,xvda,w', ]
vif = [ 'bridge=xenbr0','bridge=xenbr1' ]
bootloader="/usr/bin/pygrub"
vcpus=2
on_reboot = 'restart'
on_crash = 'restart'
I only have one drbd resource, r0. The hosts are configured like this:
on radm012d {
device /dev/drbd0;
disk /dev/md2;
address <IPaddr>:7788;
flexible-meta-disk internal;
}
I install the domU with this command (with kickstart server URL removed)
xm create rusr007d on_reboot=restart kernel=/var/lib/xen/vmlinuz
ramdisk=/var/lib/xen/initrd.img extra="ks=http://<ksserver>/ks.cfg
ksdevice=eth0 noipv6" bootloader="" -c
Tom