From: Max Reitz <mreitz@redhat.com>
To: Sandeep Joshi <sanjos100@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] writing a QEMU block driver
Date: Wed, 22 Oct 2014 09:12:48 +0200 [thread overview]
Message-ID: <544758F0.9080205@redhat.com> (raw)
In-Reply-To: <CAEfL3KmaVqR9G3Qn_spH8rt9o=aHUfpVAGHoe0ApqFzbxz64PQ@mail.gmail.com>
On 2014-10-22 at 05:08, Sandeep Joshi wrote:
>
> Another small question. I noticed that all block drivers call
> block_init ("module_init") and qemu_system binary has the
> "--enable-modules" command line option.
>
> But does QEMU support building block drivers outside the main source
> tree ? And can I load a new block driver module into running QEMU
> system - like the Linux kernel allows ? Or do I have to distribute
> an entire own QEMU image if I add a new driver ? I am not sure if
> what I am asking is the same as https://wiki.ubuntu.com/QemuDiskHotplug
No, this is a different question. Disk hotplug is something for the
guest, whereas you want something for the host. As far as I know, people
are aware of that issue and it may be implemented at some point in time.
But right now it's not supported in vanilla qemu (I've heard something
about at least one distribution already having implemented this).
If you add a new driver, you either have to distribute its source so
people can build qemu themselves with the driver included; or you build
qemu yourself and then distribute the binary; or you find your driver
good enough to submit it for upstream qemu.
Max
prev parent reply other threads:[~2014-10-22 7:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 14:59 [Qemu-devel] writing a QEMU block driver Sandeep Joshi
2014-10-20 7:50 ` Max Reitz
2014-10-21 7:30 ` Sandeep Joshi
2014-10-22 3:08 ` Sandeep Joshi
2014-10-22 7:12 ` Max Reitz [this message]
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=544758F0.9080205@redhat.com \
--to=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sanjos100@gmail.com \
/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).