Date: Thu, 5 Jun 2008 23:52:27 +0200 (CEST) From: Juergen Lock <nox@jelal.kn-bremen.de> To: eculp@encontacto.net Cc: freebsd-emulation@freebsd.org Subject: Re: qemu: could not open disk image /tmp/c.img that was created by qemu Message-ID: <200806052152.m55LqRlE089334@saturn.kn-bremen.de> In-Reply-To: <20080604122407.188217sdanmlq37k@intranet.encontacto.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <20080604122407.188217sdanmlq37k@intranet.encontacto.net> you write: >I'm running amd64 current-8 and am up to date on most everything. > >I'm trying to give qemu a try and am using the quick start on the qemu >site, step by step and got all the way to the second step ;) > ># qemu-img create -f qcow c.img 3G >Formatting 'c.img', fmt=qcow, size=3145728 kB > ># qemu -cdrom /dev/acd0 -hda /tmp/c.img -m 256 -boot d >qemu: could not open disk image /tmp/c.img > >acd0 was an unmounted windowsXP installation CD. > >Should the procedure be changed for FreeBSD, I obviously assumed not? Hmm, seems the CVE 2008-0928 security patch broke qcow, or at least new qcow images. qcow is also deprecated tho, you can just use qcow2 instead which still works. Or use raw images which should still be faster, only they are sparse files which some backup software like bsdtar doesn't know how to deal with properly. (dump still works tho, as should gtar or star when passed appropriate flags.) I just checked, seems that patch also has been backed out from qemu svn but no replacement committed since. Hmm... Juergen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806052152.m55LqRlE089334>