Re: Fwd: [Xen-users] Why creating DomU failed (seems it is due to LVM)

[TMC <tmciolek@xxxxxxxxx>]

scan DomU /etc/ for 'lvm'

Tomasz

On 11/12/06, Zhang Binbin <binbinzh@xxxxxxx> wrote:
> I've searched all "VolGroup00" in DomU /etc, and delete them, but it didn't 
> help.
> It still scaned logical volumes and failed:
>
>         Scanning logical volumes
>                 Reading all physical volumes.  This may take a while...
>                 No volume groups found
>         Activating logical volumes
>                 olume group "VolGroup00" not found
>         ERROR: /bin/lvm exited abnormally! (pid 353)
>
> Maybe a clean install is a must...
>
> Best,
> Binbin
>
> ======= 2006-12-11 14:18:01 you wrote:=======
>
> >---------- Forwarded message ----------
> >From: TMC <tmciolek@xxxxxxxxx>
> >Date: 11-Dec-2006 10:59
> >Subject: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
> >To: steven@xxxxxxxxxxxxxxxxxxx
> >Cc: Zhang Binbin <binbinzh@xxxxxxx>, xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
> >
> >
> >On 11/12/06, Steven Dugway <steven@xxxxxxxxxxxxxxxxxxx> wrote:
> >> TMC wrote:
> >> > can you please post your config here?
> >> >
> >> > I suspect that your trying to start LVM configuration from Dom0 in
> >> > DomU...
> >> >
> >> > There are two ways to do things.
> >> >
> >> > a) put all disk in Dom0 under LVM and manage disk for all DomU
> >> > instances that way..
> >> That is how I do it and then export the partitions for each domU, works
> >> fine with old FC5 packages.
> >> Here is an config file:
> >>
> >> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen"
> >> #kernel = "/boot/2.6.16-1.2122_FC5xenU"
> >> memory = 250
> >> name = "spooner"
> >> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img"
> >> vif = [ '' ]
> >> 
> disk=['phy:/dev/VolGroup00/spooner,sda1,w','phy:/dev/VolGroup00/spoonerHS,sda4,w','phy:/dev/VolGroup00/swap1,sda2,w','file:/img/tmpfiles,sda3,w']
> >> root = "/dev/sda1 ro"
> >>
> >
> >Ok.
> >
> >What I suspect is happening is that you have  copied a whole parent
> >server instance (with a running /etc and such like) instead of doing a
> >clean install to your patritions with kickstart, jump-start or
> >debootstrap.
> >
> >This means that your LVM subsystem is looking in /etc, finds configs
> >and goesa looking for disks to  manage and fails, bacuse it must. you
> >are accessing abstracted devices not raw devices in your DomU.
> >
> >I think you need to blow away (or at least rename) all LVM configs in
> >/etc/ of  your DomU. They are not needed.
> >
> >Also you need to change:
> >your networking (unless you DHCP)
> >hostname
> >edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and
> >/dev/sda4  as required instead of  lables or /dev/VolGroup** stuff.
> >
> >Also Please boot the XenU specific kernel, if your packages provide
> >it. Its safer.
> >
> >
> >Hope this helps
> >
> >Tomasz
> >
> >
> >--
> >GPG key fingerprint: 3883 B308 8256 2246 D3ED  A1FF 3A1D 0EAD 41C4 C2F0
> >GPG public key availabe on pgp.mit .edu keyserver
> >
>
> = = = = = = = = = = = = = = = = = = = =
--
GPG key fingerprint: 3883 B308 8256 2246 D3ED  A1FF 3A1D 0EAD 41C4 C2F0
GPG public key availabe on pgp.mit .edu keyserver

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