Re: Which qemu change corresponds to RedHat bug 1655408

[Philippe Mathieu-Daudé]

Hi Jakob,

On 10/8/20 6:32 PM, Jakob Bohm wrote:
> Red Hat bugzilla bug 1655408 against qemu is listed by Red Hat as fixed in
> April 2019, but I cannot find the corresponding change on qemu.org (the
> Changelog in the wiki is not a traditional changelog and doesn't cover
> bugfix releases such as 5.0.1, the git commit log is too detailed to
> search, the Red Hat bugzilla and security advisory pages do not link
> red hat bugs back to upstream (launchpad) bugs or git changes.
> 
> Here is the bug title (which also affects my Debian packaged qemu 5.0):
> 
> VM can not boot up due to "Failed to lock byte 100" if cdrom has been
> mounted on the host
> 
> Further observation:
> 
> The basic problem is that qemu-system refuses to start with the error
> message "Failed to lock byte 100" when -drive points to a read-only
> ISO file.  For the reporter of the Red Hat bug, that was a mount-induced
> read-only condition, in my case it is an NFS mount of a read-only
> directory.
> 
> The error message itself seams meaningless, as there is no particular
> reason to request file locks on a read-only raw disk image.
> 
> my qemu-system-x86_64 invocation contains the option (on one line):
> 
> -drive if=none,id=drive-ide0-1-0,readonly=on,
> file=/mnt/someshare/path/gparted-live-1.1.0-5-amd64.iso,format=raw

https://bugzilla.redhat.com/show_bug.cgi?id=1655408 has been
closed due to lack of reproducer. Can you amend your information
to the BZ? It will likely be re-opened. Thanks!

> 
> Enjoy
> 
> Jakob
> -- 
> Jakob Bohm, CIO, Partner, WiseMo A/S.  https://www.wisemo.com
> Transformervej 29, 2860 Søborg, Denmark.  Direct +45 31 13 16 10
> This public discussion message is non-binding and may contain errors.
> WiseMo - Remote Service Management for PCs, Phones and Embedded 
>