qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] Reproducible crash on PCIe hotplug


From: Stefan Hajnoczi
Subject: Re: [Qemu-devel] Reproducible crash on PCIe hotplug
Date: Mon, 12 Dec 2016 18:27:21 +0000

On Mon, Dec 12, 2016 at 5:32 PM, Eduardo Habkost <address@hidden> wrote:
> On Mon, Dec 12, 2016 at 05:29:15PM +0000, Stefan Hajnoczi wrote:
>> On Mon, Dec 12, 2016 at 01:34:05PM +0800, Cao jin wrote:
>> >
>> >
>> > On 12/10/2016 04:39 AM, Eduardo Habkost wrote:
>> > > Using latest qemu.git master:
>> > >
>> > >   $ qemu-system-x86_64 -machine q35 -readconfig docs/q35-chipset.cfg 
>> > > -monitor stdio
>> > >   QEMU 2.7.93 monitor - type 'help' for more information
>> > >   (qemu) device_add e1000e,bus=ich9-pcie-port-4,addr=00
>> > >   (qemu) device_add e1000e,bus=ich9-pcie-port-4,addr=08
>> > >   Segmentation fault (core dumped)
>> > >
>> > > It crashes at:
>> > >
>> > >   #7  0x000055555598d7dc in do_pci_register_device (errp=0x7fffffffbfd0, 
>> > > devfn=64, name=0x5555565df340 "e1000e", bus=0x555558487380, 
>> > > pci_dev=0x5555589cd000)
>> > >       at /home/ehabkost/rh/proj/virt/qemu/hw/pci/pci.c:983
>> > >   983             error_setg(errp, "PCI: slot %d function 0 already 
>> > > ocuppied by %s,"
>> > >   (gdb) l
>> > >   978                        PCI_SLOT(devfn), PCI_FUNC(devfn), name,
>> > >   979                        bus->devices[devfn]->name);
>> > >   980             return NULL;
>> > >   981         } else if (dev->hotplugged &&
>> > >   982                    pci_get_function_0(pci_dev)) {
>> > >   983             error_setg(errp, "PCI: slot %d function 0 already 
>> > > ocuppied by %s,"
>> > >   984                        " new func %s cannot be exposed to guest.",
>> > >   985                        PCI_SLOT(devfn),
>> > >   986                        bus->devices[PCI_DEVFN(PCI_SLOT(devfn), 
>> > > 0)]->name,
>> > >   987                        name);
>> > >
>> >
>> > Thanks for informing me. I am kind of busy for now, so I suppose I will
>> > investigate it after 2.8 release.
>>
>> Please let me know if this should be considered a release blocker.
>>
>> The proposed QEMU 2.8 release date is tomorrow (December 13th)!
>
> The bug went undetected since QEMU 2.5, and the crash happens
> only on cases where hotplug was already going to return an error.
> I don't think it should be a release blocker.

Excellent, thanks for clarifying.

Stefan



reply via email to

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