From: Antony T Curtis <antony.t.curtis@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: qemu-img, BSD (was: Re: [Qemu-devel] new block layer)
Date: Thu, 05 Aug 2004 01:39:03 +0100 [thread overview]
Message-ID: <1091666342.61926.68.camel@pcgem.rdg.cyberkinetica.com> (raw)
In-Reply-To: <20040804201117.A19539@saturn.kn-bremen.de>
On Wed, 2004-08-04 at 19:11, Juergen Lock wrote:
> On Tue, Aug 03, 2004 at 10:19:08PM +0000, Fabrice Bellard wrote:
> > Hi,
> >
> > I commited the new disk image layer of QEMU which adds the following
> > features:
> >
> >...
>
> First: How do you use qemu-img? If i try
> qemu-img create -b /dev/ad0 -f qcow testcow 10M
> I only get the usage back.
>
> Second question: Has anyone patched the new block layer for BSD already?
> At least FreeBSD can't access cdroms in 512 byte blocks, everything
> has to be done in the cd blocksize which is 2048. (A patch for this
> from the list for the old block layer is in the port; It also needs
> to use DIOCGMEDIASIZE but that was quick to re-add.)
I have a new patch for the new block layer - it defines a new block type
(imaginately called 'dev') and the probe checks the DIOCGMEDIASIZE and
DIOCGSECTORSIZE ioctls... It also ensures that I/O is done in multiples
of the device sector size.
I'll have a new patch together for this soon...
On my machine (FreeBSD 5-NOT_SO_CURRENT), the slirp code causes a
SIGBUS... I might investigate - it looks like it occurs near
constructing the ethernet header... poor backtraces prevents me from
finding exactly where.
> Here is an update for the port, I send it here because I dont
> think it should be committed until the cdrom issue is fixed...
>
> If you want to look at the patches in the port and don't have a
> FreeBSD ports tree on your system: you can check out the port from
> cvs by (for example) doing
>
> CVSROOT=:pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs cvs co ports/emulators/qemu
>
> (login with password anoncvs)
>
> the FreeBSD patches are in the files/ dir; patch-aa and -ab are from
> the list, patch-ac, patch-bd and patch-bf are FreeBSD only
>
> (apply this on top of the port in cvs, then remove files/patch-ba,
> files/patch-bb, files/patch-bg)
>
> Oh and if you try this after today 2340 (iirc) Jerusalem time
> you need to adjust the date in DISTNAME (and maybe more depending
> on what Fabrice commits...)
>
> Index: Makefile
<snip - variant of old block patch which I originally hacked >
--
Antony T Curtis, BSc. UNIX, Linux, *BSD, Networking
antony.t.curtis@ntlworld.com C++, J2EE, Perl, MySQL, Apache
IT Consultancy.
next prev parent reply other threads:[~2004-08-05 0:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 21:41 [Qemu-devel] new block layer Fabrice Bellard
2004-08-03 23:03 ` [Qemu-devel] " Ronald
2004-08-04 18:11 ` qemu-img, BSD (was: Re: [Qemu-devel] new block layer) Juergen Lock
2004-08-05 0:39 ` Antony T Curtis [this message]
2004-08-10 20:22 ` Juergen Lock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1091666342.61926.68.camel@pcgem.rdg.cyberkinetica.com \
--to=antony.t.curtis@ntlworld.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).