WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] drbd and xen problem: disk not accessible

To: "Marco Strullato" <marco.strullato@xxxxxxxxx>, "xen-users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] drbd and xen problem: disk not accessible
From: "Ross S. W. Walker" <rwalker@xxxxxxxxxxxxx>
Date: Wed, 23 Apr 2008 10:26:01 -0400
Delivery-date: Wed, 23 Apr 2008 07:26:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
Importance: normal
In-reply-to: <b9f669850804230710n4f13dab2hd965d8ecf52cce42@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Priority: normal
References: <b9f669850804230710n4f13dab2hd965d8ecf52cce42@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcilS82eHhY9hop9Rt6ZluBHNEjZTwAAMrjQ
Thread-topic: [Xen-users] drbd and xen problem: disk not accessible
Marco Strullato wrote:
> 
> Hi all, I have a problem with drbd and xen.
> After setting up drbd and after I installed a new linux vm, I 
> can not create the vm because of a problem accessing the disk.
> I read that a solution could be setting the kernel and 
> ramdisk and root parameter into the vm config file but it 
> doesn't work for me.
> 
> What do you suggest me?
> 
> I get:
> Using config file "/etc/xen/VMNAME".
> No handlers could be found for logger "xend"
> Error: Disk isn't accessible
> Usage: xm create <ConfigFile> [options] [vars]
> ...
> 
> I'm using this packages:
> xen-3.0.3-41.el5
> kernel-xen-2.6.18-8.el5
> kmod-drbd82-xen-8.2.5-1.2.6.18_53.1.14.el5
> xen-libs-3.0.3-41.el5
> xen-libs-3.0.3-41.el5
> kernel-xen-2.6.18-53.1.14.el5
> drbd82-8.2.5-1.el5.centos
> kmod-drbd82-xen-8.2.5-1.2.6.18_53.1.14.el5
> 
> my drbd.conf is:
> global {
>         usage-count yes;
>  }
> common {
>         protocol C;
>         startup {
>                 become-primary-on both;
>         }
>         net {
>                 allow-two-primaries;
>         }
>         disk {
>                 on-io-error detach;
>         }
>         syncer {
>                 verify-alg md5;
>                 rate 50M;
>         }
> 
> }
> resource r0 { 
>         on hyp11.infolan {
>                 device     /dev/drbd0;
>                 disk       /dev/HYP11VM/INT;
>                 address    10.100.0.2:7788;
>                 meta-disk  internal;
>         }
>         on hyp10.infolan {
>                 device    /dev/drbd0;
>                 disk      /dev/HYP10VM/INT;
>                 address   10.100.0.1:7788;
>                 meta-disk internal;
>         }
> }
> 
> and the vm configuration file is:
> name = "VMNAME"
> uuid = "8f1e2a13-f0c1-fbf5-a1f2-2a71f8c7c144"
> maxmem = 512
> memory = 512
> vcpus = 1
> bootloader = "/usr/bin/pygrub"
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
> vfb = [  ]
> disk = [ "drbd:r0,xvda,w" ]
            ^^^^^^^
Where did you get this config info from, as far as I
know it should be:

disk = [ "phy:drbd0,xvda,w" ]

> vif = [ "mac=00:16:3e:60:7d:41,bridge=xenbr0" ]
> kernel='/boot/vmlinuz-2.6.9-67.0.7.ELxenU'
> ramdisk='/boot/initrd-2.6.9-67.0.7.ELxenU.img'  
> root='/dev/VolGroup00/LogVol00 ro'

Setting drbd resources per-lv will become very messy
over time as the number of guests increase. I advise
replicating PVs between hosts and adding the drbdX
resources to shared VGs. If you maintain all your
VMs in xenstore then the VM config should migrate
between machines so you don't need to have the VM
config present on both machines beforehand and
therefore you will not be able to start the same
VM on 2 machines at once and therefore shouldn't
need to run CLVM which would get in the way of VM
migration.


-Ross

______________________________________________________________________
This e-mail, and any attachments thereto, is intended only for use by
the addressee(s) named herein and may contain legally privileged
and/or confidential information. If you are not the intended recipient
of this e-mail, you are hereby notified that any dissemination,
distribution or copying of this e-mail, and any attachments thereto,
is strictly prohibited. If you have received this e-mail in error,
please immediately notify the sender and permanently delete the
original and any copy or printout thereof.


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