From: Jakob Bohm <jb-gnumlists@wisemo.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-discuss@nongnu.org, qemu-devel <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>,
"John Snow" <jsnow@redhat.com>
Subject: Re: Which qemu change corresponds to RedHat bug 1655408
Date: Thu, 8 Oct 2020 18:49:14 +0200 [thread overview]
Message-ID: <43072820-c04f-b706-4b37-2d2e37e8499f@wisemo.com> (raw)
In-Reply-To: <653b9595-ae60-181a-2975-2e351ade9788@redhat.com>
(Top posting because previous reply did so):
If the bug was closed as "can't reproduce", why was a very similar bug
listed as fixed in RHSA-2019:2553-01 ?
On 2020-10-08 18:41, Philippe Mathieu-Daudé wrote:
> 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
>>
>
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
next prev parent reply other threads:[~2020-10-08 20:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2d9c8525-470f-a4e5-5d71-895046e2d782@wisemo.com>
2020-10-08 16:41 ` Which qemu change corresponds to RedHat bug 1655408 Philippe Mathieu-Daudé
2020-10-08 16:49 ` Jakob Bohm [this message]
2020-10-08 16:59 ` Philippe Mathieu-Daudé
2020-10-09 8:48 ` Max Reitz
2020-10-09 12:55 ` Jakob Bohm
2020-10-09 13:56 ` Max Reitz
2020-10-09 22:54 ` Jakob Bohm
2020-10-12 7:22 ` Max Reitz
2020-10-12 11:47 ` Max Reitz
2020-10-13 1:01 ` Jakob Bohm
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=43072820-c04f-b706-4b37-2d2e37e8499f@wisemo.com \
--to=jb-gnumlists@wisemo.com \
--cc=jsnow@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).