On Wed, Jan 09, 2013 at 03:31:50PM +0800, 马磊 wrote: > Hi, > >> The final effect is as follows: > >> > >> > >> *[malei@xentest-4-1 Fri Dec 28 ~/honeypot/xen/xen-4.1.2]$ qemu-img-xen > >> cat -f /1/boot.ini ~/vm-check.img * > >> *[boot loader]* > >> *timeout=30* > >> *default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS* > >> *[operating systems]* > >> *multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP > >> Professional" /noexecute=optin /fastdetect* > >> > >> [malei@xentest-4-1 Fri Dec 28 ~/honeypot/xen/xen-4.1.2]$ qemu-img-xen ls > >> -l -d /1/ ~/vm-check.img > >> *【name size(bytes) dir? date > >> create-time】* > >> *AUTOEXEC.BAT 0 file 2010-12-22 17:30:37* > >> *boot.ini 211 file 2010-12-23 > >> 01:24:41* > >> *bootfont.bin 322730 file 2004-11-23 20:00:00* > >> * > >> * > >> * > >> * > >> * > >> * > >> > >> *As you see above, the patch add two sub-commands for qemu-img-xen:cat > >> and ls.* > >> * > >> * > >> *For details in the patch, please check the attachment. * > >> > >> > >> > *Does anyone prefer this feature?!*
This is already possible with http://libguestfs.org/. Or you can use qemu-nbd to mount the image on the host as explained here: http://blog.vmsplice.net/2011/02/how-to-access-virtual-machine-image.html Although adding file system code to qemu-img integrates this feature more closely, I think the maintenance overhead and duplication of having read-only file system implementations is too much. Therefore, I'm against merge a patch like this. Stefan