Mounting KVM image
Tom H
tomh0665 at gmail.com
Sat Jun 12 19:30:26 UTC 2010
On Sat, Jun 12, 2010 at 1:16 PM, kalinix <calin.kalinix.cosma at gmail.com> wrote:
> On Sat, 2010-06-12 at 10:03 -0600, Greg Woods wrote:
>> On Sat, 2010-06-12 at 17:53 +0300, kalinix wrote:
>>> http://www.thegibson.org/blog/archives/467
> Thanks, I'll take a look at that.
>>> It would be useful to post the layout of your hdd, though.
>> This is a Xen image if that matters:
>> # losetup /dev/loop0 test.img
>> # fdisk -ul /dev/loop0
>> Disk /dev/loop0: 5242 MB, 5242880000 bytes
>> 255 heads, 63 sectors/track, 637 cylinders, total 10240000 sectors
>> Units = sectors of 1 * 512 = 512 bytes
>> Device Boot Start End Blocks Id System
>> /dev/loop0p1 * 63 208844 104391 83 Linux
>> /dev/loop0p2 208845 10233404 5012280 8e Linux LVM
>> I can lomount partition 1 and it is /boot. There aren't any such devices
>> as /dev/loop0p1 and /dev/loop0p2, so I presume this is just something
>> about how fdisk displays it.
> As you mounted the whole disk, the p1 and p2 are the partitions on it. What LVM scan commands did you run?
You have to run "kpartx -a /dev/loop0" for the kernel to recognize the
partitions that fdisk is displaying. You can then run "vgchange...".
More information about the users
mailing list