> -----Original Message----- > From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of > Anthony PERARD > Sent: 09 November 2017 17:50 > To: Roger Pau Monne <roger....@citrix.com> > Cc: Mike Reardon <m...@inso.org>; xen-devel@lists.xen.org; Stefano > Stabellini <sstabell...@kernel.org>; Jan Beulich <jbeul...@suse.com>; > Konrad Rzeszutek Wilk <konrad.w...@oracle.com> > Subject: Re: [Xen-devel] [BUG] blkback reporting incorrect number of > sectors, unable to boot > > On Thu, Nov 09, 2017 at 05:03:18PM +0000, Roger Pau Monné 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 > > :(, I never saw those error messages, maybe we should increase the > verbosity of the qemu backends. > > > 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? > > I know of the issue, I don't know what to do about it yet. > > The problem is that QEMU 4.10 have a lock on the disk image. When > booting an HVM guest with a qdisk backend, the disk is open twice, but > can only be locked once, so when the pv disk is been initialized, the > initialisation kind of fail. > Unfortunatly, OVMF will wait indefinitly until the PV disk is > initialized.
That's presumably because the OVMF frontend leaves the emulated disk plugged in despite talking via PV? Paul > > -- > Anthony PERARD > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > https://lists.xen.org/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
