On Thu, Nov 9, 2017 at 10:03 AM, Roger Pau Monné <roger....@citrix.com> wrote:
> On Thu, Nov 09, 2017 at 08:15:52AM -0700, Mike Reardon wrote: > > On Thu, Nov 9, 2017 at 2:30 AM, Roger Pau Monné <roger....@citrix.com> > > wrote: > > > > > Please try to avoid top-posting. > > > > > > On Wed, Nov 08, 2017 at 08:27:17PM -0700, Mike Reardon wrote: > > > > So am I correct in reading this that for at least the foreseeable > future > > > > storage using 4k sector sizes is not gonna happen? I'm just trying > to > > > > figure out if I need to get some different hardware. > > > > > > Have you tried to use qdisk instead of blkback for the storage > > > backend? > > > > > > You will have to change your disk configuration line to add > > > backendtype=qdisk. > > > > > > Roger. > > > > > > > Sorry I didn't realize my client was defaulting to top post. > > > > If I add that to the disk config line, the system just hangs on the ovmf > > bios screen. This appears in the qemu-dm log: > > > > > > xen be: qdisk-51712: xen be: qdisk-51712: error: Failed to get "write" > lock > > error: Failed to get "write" lock > > xen be: qdisk-51712: xen be: qdisk-51712: initialise() failed > > initialise() failed > > Hm, that doesn't seem related to the issue at hand. Adding Anthony and > Stefano (the QEMU maintainers). > > Is there a know issue when booting a HVM guest with qdisk and UEFI? > > Roger. > So I added the disk to a domU that was running Windows and not using UEFI and it appears to be working as expected. The disk shows up, I can read/write to the disk just fine.
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
