[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Unable to mount LVM - backed VBD


  • To: "Christopher G. Stach II" <cgs@xxxxxxxxx>
  • From: rajarshi das <dazio_r@xxxxxxxxx>
  • Date: Wed, 15 Nov 2006 05:31:23 -0800 (PST)
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 15 Nov 2006 05:31:45 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Z1Yga3AWTArTARsAD2wWyBcvEpT3eCJaGrbHkuHW3xkWona2z3Re7FYducUTil8vuHSi2t6cdGeDBXpgvhsO+8KjCRY8t5VhX6cdDaLTUCpu9HFs+Sa14UlS2JJuUrijSBDi7fnHv8NMeKn3buYa+HYQwGOt9z/DrioRnllzNM4=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I commented the 'disk' entry, and set the 'root' entry to:
root="/dev/mapper/volgrpguest-logvol1 ro"
 
Now, I get the error 'Unable to find volume group logvol1'.
 
why does xen think that the volume group is logvol1 (which is actually the logical volume inside the volume group volgrpguest)?
 
Appreciate any suggestions.
 
- Rajarshi

"Christopher G. Stach II" <cgs@xxxxxxxxx> wrote:
rajarshi das wrote:
> All,
>
> I have a SLES10 system with the following volume groups:
>
> 1) /dev/volgrplinux :
> logvolroot (lv)
> logvolswap (lv)
>
> 2) /dev/volgrpguest :
> logvol1 (lv)
>
> I want to use the logvol1 as a lvm - backed vbd.
>
> $ xm create -c xmexample.lvm-vbd
> ....
> ......
> xvda: Loading dm-mod
> unknown partition table
> device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@xxxxxxxxxx
>
> Loading dm-snapshot
> Waiting for /dev/mapper/control to appear: ok
> Loading jbd
> Loading ext3
> Unable to find volume group "logvolroot"
> Waiting for device /dev/mapper/volgrplinux-logvolroot to appear:
> ........ not found -- exiting to /bin/sh
> $
>
>
> Following is the configuration file:
> ---------start of config file------------------------------
> # Kernel image file and (optional) ramdisk (initrd).
> kernel = "/boot/vmlinuz-xenpae"
> ramdisk = "/boot/initrd-xenpae"
>
> # Initial memory allocation (in megabytes) for the new domain.
> memory = 64
>
> # A name for your domain. All domains must have different names.
> name = "ExampleDomain1"
>
> vif = [ '' ]
>
> disk = [ 'phy:volgrpguest/logvol1,volgrplinux/logvolroot,w' ]
>
> #dhcp="dhcp"
> # Set netmask.
> #netmask=
> # Set default gateway.
> #gateway=
> # Set the hostname.
> #hostname= "vm%d" % vmid
>
> # Set root device.
> #root = "/dev/hda1 ro"
> root = "/dev/mapper/volgrplinux-logvolroot ro"
>
> # Sets runlevel 4.
> extra = "4"
> ----------------end of config file------------------------
>
> $ ls -l /dev/mapper
>
> lrwxrwxrwx 1 root root 16 nov 14 18:11 control -> ../device-mapper
> brw------- 1 root root 253,2 nov 15 9:59 volgrpguest-logvol1
> brw------- 1 root root 253,0 nov 14 18:11 volgrplinux-logvolroot
> brw------- 1 root root 253,1 nov 14 18:11 volgrplinux-logvolswap
>
>
>
>
> Is there something in the configuration that prevents the logvolroot
> from being found?
>
> Also, are there any additional modules that need to be modprobed (apart
> from dm-mod and dm-snapshot) when a domU starts up?
>
> Please suggest how to fix this.
>
> Thanks,
> Rajarshi
>

Your disk and root lines are bad, to start with.

--
Christopher G. Stach II


Sponsored Link

$420,000 Mortgage for $1,399/month - Think You Pay Too Much For Your Mortgage? Find Out!
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.