[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Which qemu change corresponds to RedHat bug 1655408

From: Jakob Bohm
Subject: Which qemu change corresponds to RedHat bug 1655408
Date: Thu, 8 Oct 2020 18:32:59 +0200
User-agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.1

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

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,

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 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]