From: Marcel Apfelbaum <marcel@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] q35 migration broken
Date: Fri, 1 Apr 2016 19:59:24 +0300 [thread overview]
Message-ID: <56FEA8EC.4000601@redhat.com> (raw)
In-Reply-To: <20160401155457.GI2242@work-vm>
On 04/01/2016 06:54 PM, Dr. David Alan Gilbert wrote:
> * Dr. David Alan Gilbert (dgilbert@redhat.com) wrote:
>> * Dr. David Alan Gilbert (dgilbert@redhat.com) wrote:
>>> Hi,
>>> I'm seeing a breakage on q35 migration on head (and possibly older
>>> but certainly head; it's also on a 2.5.0 world I've got with a bunch
>>> of patches but I've not tried a clean 2.5.0 yet).
>>>
>>> It looks like some type of interrupt screwup; with a virtio-net device
>>> I get a:
>>> BUG: soft lockup - CPU#0 stuck for 22s!
>>> ... virtnet_config_changed_work
>>>
>>> but if I swap that out for an e1000 I get:
>>> Disabling IRQ #22
>>>
>>> and various timeouts on e1000 and cdrom (scsi).
>>> The guest kind of limps along with an existing terminal scrolling dmesg -w output.
>>>
>>> This is an f23 guest on a rhel7.2-ish host; with the guest sitting an idle
>>> (MATE) Gui.
>>
>> Also broken with 2.4.1 and 2.5.1 (with pc-q35-2.4 machine type);
>> see a screen shot attached; note:
>> a) The large count on irq 22 (enp2s1) on cpu1
>> b) The large count on virtio2-config on cpu1
>> c) The count of 'Deferred Error APIC interrupts'.
>
> OK, this seems to be the i82801b11-bridge; if I remove it from the config
> it all works.
>
> My minimum config that fails so far is:
> /opt/qemu-head/bin/qemu-system-x86_64 -nographic -machine pc-q35-2.6,accel=kvm,usb=off,vmport=off -cpu SandyBridge -m 4096 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 \
> -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e \
> -drive id=image,file=/home/vms/f23-serial.qcow2,if=none,cache=none \
> -device virtio-blk-pci,scsi=off,bus=pci.1,addr=0x5,drive=image,id=virtio-disk0,bootindex=1 \
> $*
>
> if I flip the i82801b11-bridge for a pci-bridge then it works.
Hi Dave,
That's good news. I see we don't have a vmstate for this bridge, but we do have one for the regular pci-bridge.
Maybe this is the problem?
Thanks,
Marcel
>
> Dave
>
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
next prev parent reply other threads:[~2016-04-01 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 19:03 [Qemu-devel] q35 migration broken Dr. David Alan Gilbert
[not found] ` <20160401100623.GE2242@work-vm>
2016-04-01 15:54 ` Dr. David Alan Gilbert
2016-04-01 16:59 ` Marcel Apfelbaum [this message]
2016-04-01 17:01 ` Dr. David Alan Gilbert
2016-04-01 17:05 ` Marcel Apfelbaum
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=56FEA8EC.4000601@redhat.com \
--to=marcel@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-devel@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).