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

[Xen-users] pygrub lvm partition & grub.cfg question

To: Xen users mailing list <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] pygrub lvm partition & grub.cfg question
From: Bruce Edge <bruce.edge@xxxxxxxxx>
Date: Sat, 10 Jul 2010 16:41:23 -0700
Delivery-date: Sat, 10 Jul 2010 16:42:43 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=J3CEg/2lx8nY8/lcUdjr2kq5Z+Sm/1ujnU5NsgavS2A=; b=hg5T8m79MMtXV4bqCsM3fwdsEov+r9zRgc7mCZw5VSB1v2igZxlgG1xtJ9ynlR3DuI 3rkDdlEG1BWrkhEolzWTr6rrbnPss7tjPyaUhVuDPn2nG6PEDtTcon7iytBaOGBVoioU sUbzn9pbIHOrAME7JPMnXylV6yyxyZIPSvoCc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=phIdzDOnY31IQsqiKFS9Sd825tRGDxp9L/qjocFpBRYq1BS3AmCos8viHOeQAbRsm5 AoAvdNdIaqw3iU5Ay2+ioF8IExGpt+egRnWVvuys9RqTZEC9jfQSxqQodmbqumKTFXhd EZsSCQ59TZIpn7eBqMlTe+FDY1Ffy/tVQw7V0=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I install a domU using: 

disk        = [ 'phy:system/dpm_0,xvda:sda,w', 'file:/lucid.iso,xvdc:cdrom,r' ]

During the install I see the partition map as:

~ # sfdisk -d /dev/sda
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
# partition table of /dev/sda
unit: sectors

/dev/sda1 : start=     2048, size=  9226240, Id=83
/dev/sda2 : start=  9230334, size=   532482, Id= 5
/dev/sda3 : start=        0, size=        0, Id= 0
/dev/sda4 : start=        0, size=        0, Id= 0
/dev/sda5 : start=  9230336, size=   532480, Id=82

sda1 = /
sda5 = swap

so far so good.

After running partprobe, I see the embedded partitions:

brw-rw---- 1 root disk 250,  4 Jul 10 12:06 system-dpm_0
brw-rw---- 1 root disk 250,  8 Jul 10 09:25 system-dpm_0p1
brw-rw---- 1 root disk 250,  9 Jul 10 09:25 system-dpm_0p2
brw-rw---- 1 root disk 250, 10 Jul 10 09:25 system-dpm_0p5

Still OK.

Now it gets weird. I mount the domU / to edit grub.cfg:

# mount /dev/mapper/system-dpm_0p1 /mnt/dpm
# vi /mnt/dpm/boot/grub/grub.cfg
-- add a new boot entry --
# umount /mnt/dpm

pygrub /dev/mapper/dpm_0:


    pyGRUB  version 0.6
 ┌────────────────────────
 │ dpm-domu , with Linux 2.6.32.16         

The 2nd boot entry is missing - why is it not seeing the embedded partition?

But if I run

pygrub /dev/mapper/dpm_0p1, I see the new boot entry::

    pyGRUB  version 0.6
 ┌────────────────────────
 │ dpm-domu , with Linux 2.6.32.16 
 │ dpm-domu , with Linux 2.6.32      

Shouldn't pygrub see the 2nd boot entry when pointed at the lvm partition /dev/mapper/system-dpm_0 
as opposed to the embedded partition pygrub /dev/mapper/dpm_0p1 ?

Where is the second copy of the grub.cfg?
I thought there was no boot sector grub.cfg anymore.

Is that not the case?

-Bruce
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>