Date: Wed, 27 Jul 2011 00:22:34 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Juergen Lock <nox@jelal.kn-bremen.de> Cc: Brandon Gooch <jamesbrandongooch@gmail.com>, freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org Subject: Re: wdrain vs. fuse/ggate (was: Re: mount vdi) Message-ID: <20110726212234.GP17489@deviant.kiev.zoral.com.ua> In-Reply-To: <20110726180335.GA82849@triton8.kn-bremen.de> References: <1311574719.49706.YahooMailClassic@web122313.mail.ne1.yahoo.com> <4E2D1275.8000305@yandex.ru> <CALBk6yJrHniVi8RoTGwLtqWF1nL1r8JZLKbS1mcLMw1DnxeofQ@mail.gmail.com> <20110726180335.GA82849@triton8.kn-bremen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--AfN0ITkBdUBwMG9P Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jul 26, 2011 at 08:03:35PM +0200, Juergen Lock wrote: > On Mon, Jul 25, 2011 at 06:31:36PM -0500, Brandon Gooch wrote: > > 2011/7/25 Andrey V. Elsukov <bu7cher@yandex.ru>: > > > On 25.07.2011 10:18, Joe Sciulli wrote: > > >> Is it possible to mount virtualbox vdi file on the FreeBSD host? =9A= This appears to be doable on > > >> windows and linux hosts, which basically is done in two steps: 1. fi= nd offset in the image. 2. > > >> mount the image with that offset. > > >> > > >> I'm trying to do the same thing on FreeBSD, and found the undocument= ed and deprecated command > > >> still works: > > >> > > >> VBoxManage internalcommands dumphdinfo freebsd_home.vdi > > >> > > >> I got the following for the virtual disk image holding the /home (no= root hence no MBR) disk for > > >> a FreeBSD guest: > > >> > > >> Header: offBlocks=3D4096 offData=3D28672 > > >> > > >> Then attempt to mount it: > > >> > > >> mdconfig -a -t vnode -f /tmp/freebsd_home_56.vdi -u 0 mount /dev/md0= /tmp/aaa/ mount -t cd9660 > > >> /dev/md0 /tmp/aaa/ > > >> > > >> unfortunately both the above two mount commands failed with "Invalid= argument". =9AI tried > > >> skip=3D28672 to no avail as well. =9AAnything did I do wrong? > > > > > > I have not any Vbox images with fixed size, but i tried this: > > > # mdconfig -f 10G_GPT_UFS.vdi > > > # gnop create -v -o 41472 /dev/md0 > > > > > > where 41472 is offData value. After that md0.nop was tasted and repor= ts about invalid GPT. > > > So, i think if your image is fixed size disk yout can try this method= and mount UFS (not cd9660). > > > > > > -- > > > WBR, Andrey V. Elsukov > >=20 > > There was a CFT sent out a while back about a fuse module for mounting > > vdi images: > >=20 > > http://lists.freebsd.org/pipermail/freebsd-emulation/2010-September/007= 964.html > >=20 > > Not sure about the state of this now though... >=20 > Yeah sorry I never got back to this after getting reports that > writes are stuck in wdrain... [1] I guess what happens is the > vdfuse process wants to write many(?) more blocks than the number > that got queued by the original fuse request and/or too many writes > get queued up at once before the vdfuse process gets to handle them > (trying to increase runningbufspace even more), and thus there is > deadlock. :( So my question for -hackers is, does anyone have a > clever idea how to fix this? Should the fuse requests for this be > exempted from the wdrain bookkeeping so that only the actual writes > by the vdfuse process get counted, and if yes, how would I best > accomplish this? >=20 > Thanx! :) > Juergen Excluding any buffers from runningbufspace is absolutely wrong. You will get another deadlock due to excessive pressure on the buffer space. --AfN0ITkBdUBwMG9P Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAk4vMBkACgkQC3+MBN1Mb4iB9ACgl7uXmuUfe1mmSVbQcAeWKwgd VPoAoLtD8YeHUQKqbJBWJP1fvywI8v0i =/Bak -----END PGP SIGNATURE----- --AfN0ITkBdUBwMG9P--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110726212234.GP17489>