From: Xin Zhao <uszhaoxin@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: How does qemu virtualize block device?
Date: Tue, 22 Sep 2009 11:07:36 -0700 [thread overview]
Message-ID: <4ae3c140909221107j1f1b8b4bq61d11b974f3a511c@mail.gmail.com> (raw)
In-Reply-To: <4ae3c140909221101t2e03b9ccy2a6e5c2f613fedd9@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 448 bytes --]
To make my question more specific:
Looks like block.c implements a block driver. How does qemu hook this block
driver with the virtual machine?
On Tue, Sep 22, 2009 at 11:01 AM, Xin Zhao <uszhaoxin@gmail.com> wrote:
> Hey qemu gurus,
>
> I am comparing different virtualization approaches and would like to know
> some rough idea on how qemu implement block devices like floppy, cdrom or
> hard drive. Any one know about it?
>
> Thanks,
> xin
>
[-- Attachment #2: Type: text/html, Size: 751 bytes --]
prev parent reply other threads:[~2009-09-22 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 18:01 [Qemu-devel] How does qemu virtualize block device? Xin Zhao
2009-09-22 18:07 ` Xin Zhao [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=4ae3c140909221107j1f1b8b4bq61d11b974f3a511c@mail.gmail.com \
--to=uszhaoxin@gmail.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).