|
From: | Tom Sandholm |
Subject: | Re: [Qemu-devel] Mounting qemu virtual disk images from host linux os |
Date: | Mon, 17 Jan 2005 16:59:54 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2) Gecko/20040805 Netscape/7.2 |
Hi, Thanks for all the replies. The image was created with qemu-img, with a size of 4GB. I am able to fdisk image-name and see the partitions. (as follows) Just can't mount partition 1. ==================================== nixsys:/qemu# fdisk debian01_sarge_hda.img The number of cylinders for this disk is set to 8322. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk debian01_sarge_hda.img: 4294 MB, 4294967296 bytes 16 heads, 63 sectors/track, 8322 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System debian01_sarge_hda.img1 * 1 7904 3983584+ 83 Linux debian01_sarge_hda.img2 7905 8322 210672 f W95 Ext'd (LBA) debian01_sarge_hda.img5 7905 8322 210640+ 82 Linux swap Command (m for help): ======================================== Thanks! Tom Sandholm. Jim C. Brown wrote: On Mon, Jan 17, 2005 at 03:31:22AM +0000, Mark Williamson wrote:I've not used lomount before so maybe you can pass flags to lomount directly. I can tell you how to do it using losetup / mount separately: You can use losetup to bind a partition of the disk file to a /dev/loop device and then mount that. Use the -o option to specify the offset into the file where the partition is to be found. Use the -s option to specify the size of the partition. You can probably fdisk the file (or, if that doesn't work, a loop device bound to the whole file) to figure out where the partition boundaries are. HTH, Marklomount does all of this internally. You can't pass it an offset into the file, only which partition you wish to mount. It calculates the offset by looking it up in the partition table. I'm wondering if he is trying to mount a COW image or some fancy-but-qemu-supported disk image. lomount has only been tested with raw images and sparse images, and is unlikely to work w/ anything else. |
sandholm.vcf
Description: Vcard
[Prev in Thread] | Current Thread | [Next in Thread] |