From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: KVM mailing list <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
QEMU devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>,
Cleber Rosa <crosa@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] qemu/qemu-kvm floppy regression brought by 212ec7baa28cc9d819234fed1541fc1423cfe3d8
Date: Wed, 26 Oct 2011 15:19:17 -0200 [thread overview]
Message-ID: <4EA84115.9090707@redhat.com> (raw)
In-Reply-To: <4EA82BAA.10207@redhat.com>
On 10/26/2011 01:47 PM, Kevin Wolf wrote:
> Am 26.10.2011 16:41, schrieb Lucas Meneghel Rodrigues:
>> Hi folks:
>>
>> We've captured a regression with floppy disk on recent qemu (and
>> qemu-kvm, after a code merge). We bisected it to be caused by:
>>
>> commit 212ec7baa28cc9d819234fed1541fc1423cfe3d8
>> Author: Richard Henderson<rth@twiddle.net>
>> Date: Mon Aug 15 15:08:45 2011 -0700
>>
>> fdc: Convert to isa_register_portio_list
>>
>> Signed-off-by: Richard Henderson<rth@twiddle.net>
>> Signed-off-by: Avi Kivity<avi@redhat.com>
>>
>> Since this commit, the guest doesn't see a floppy disk attached to it
>> anymore, blocking kvm autotest ability to install windows guests
>> automatically. This is a big deal for kvm autotest (ruins our automated
>> regression jobs), so please take a look at it.
>
> Can you please try again with the latest block branch? I think there is
> a patch queued that will fix it.
Kevin, I did try with HEAD of your repo:
git://repo.or.cz/qemu/kevin.git
[lmr@freedom qemu-kwolf]$ git branch -r
origin/HEAD -> origin/master
origin/blkqueue
origin/blkqueue-v1
origin/block
origin/coroutine
origin/coroutine-block
origin/coroutine-devel
origin/devel
origin/ehci
origin/for-anthony
origin/for-stable-0.14
origin/inplace-conversion
origin/master
With this repo, master branch, the problem persists. With the block
branch, the problem persists.
Now, with the blkqueue branch the problem is resolved. Cleber had the
same results booting a FreeDOS floppy. So the fix is indeed in blkqueue.
Oh, you might want to check the blkqueue branch, it does have quite a
bunch of set but unused variables, which will cause compilation errors
unless --disable-werror is passed to the configure script.
Please merge the fixes with qemu master as soon as you can, we are
probably leave windows installs from the upstream daily jobs until the
fixes get to master.
Thanks,
Lucas
next prev parent reply other threads:[~2011-10-26 17:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 14:41 [Qemu-devel] qemu/qemu-kvm floppy regression brought by 212ec7baa28cc9d819234fed1541fc1423cfe3d8 Lucas Meneghel Rodrigues
2011-10-26 15:47 ` Kevin Wolf
2011-10-26 16:30 ` Cleber Rosa
2011-10-26 16:47 ` Cleber Rosa
2011-10-26 17:19 ` Lucas Meneghel Rodrigues [this message]
2011-10-27 7:17 ` Stefan Hajnoczi
2011-10-27 18:57 ` Lucas Meneghel Rodrigues
2011-10-28 1:17 ` Zhi Yong Wu
2011-10-28 2:20 ` Lucas Meneghel Rodrigues
2011-10-28 10:24 ` Zhi Yong Wu
2011-10-28 10:28 ` Zhi Yong Wu
2011-10-28 11:46 ` Lucas Meneghel Rodrigues
2011-10-28 12:10 ` Gleb Natapov
2011-10-31 2:38 ` Zhi Yong Wu
2011-11-02 7:48 ` Zhi Yong Wu
2011-11-03 2:01 ` Lucas Meneghel Rodrigues
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=4EA84115.9090707@redhat.com \
--to=lmr@redhat.com \
--cc=avi@redhat.com \
--cc=crosa@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).