From: Chris Friesen <chris.friesen@windriver.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] question about block size and virtual disks
Date: Thu, 20 Apr 2017 15:03:37 -0600 [thread overview]
Message-ID: <58F92229.1080402@windriver.com> (raw)
Hi,
Suppose the host has a physical disk that only supports 4KB access, with no 512B
fallback.
If we boot a guest with "cache=none", does the guest need to be able to handle
disks with 4KB blocks or is qemu able to handle guests trying to access the disk
with 512B granularity?
Also, does the 4KB block size get "passed-through" to the guest somehow so that
the guest knows it needs to use 4KB blocks, or does that need to be explicitly
specified via virtio-blk-pci.logical_block_size and/or
virtio-blk-pci.physical_block_size parameters? (Assuming I'm using virtio-blk-pci.)
Thanks,
Chris
next reply other threads:[~2017-04-20 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 21:03 Chris Friesen [this message]
2017-04-20 21:21 ` [Qemu-devel] question about block size and virtual disks Eric Blake
2017-04-21 16:26 ` Chris Friesen
2017-04-25 11:33 ` Kevin Wolf
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=58F92229.1080402@windriver.com \
--to=chris.friesen@windriver.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).