From: Thomas Besser <thomas.besser@kit.edu>
To: kvm@vger.kernel.org
Subject: kvm segmentation fault on pci-hotplug add/del/re-add
Date: Mon, 16 Nov 2009 15:23:31 +0100 [thread overview]
Message-ID: <hdrn97$9ah$1@ger.gmane.org> (raw)
Hi,
running kvm 0.11.0 from http://www.corpit.ru/debian/tls/ on debian lenny
host, guest also debian lenny (with virtio and pci_hotplug, 2.6.30)
Starting the guest with:
/usr/bin/kvm -name test -vnc :5 -net
nic,vlan=0,model=virtio,macaddr=00:08:15:00:09:95 -net
tap,vlan=0,ifname=tap05,script=no -m 256 -drive
file=/vsimages/test/test.raw,if=virtio,boot=on -monitor
tcp:127.0.0.1:33333,server,nowait -vga std -k de -tdf
1. Adding hdd
On qemu-console:
pci_add auto storage file=test2.raw,if=virtio
OK domain 0, bus 0, slot 6, function 0
In guest:
pci 0000:00:06.0: reg 10 io port: [0x00-0x3ff]
pci 0000:00:02.0: BAR 6: bogus alignment [0x0-0x0] flags 0x2
decode_hpp: Could not get hotplug parameters. Use defaults
virtio-pci 0000:00:06.0: enabling device (0000 -> 0001)
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
virtio-pci 0000:00:06.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, high) ->
IRQ 11
vdb: vdb1
2. Deleting hdd
On qemu-console: pci_del 0:6
In guest: virtio-pci 0000:00:06.0: PCI INT A disabled
3. Re-adding the same hdd fails
qemu-console: pci_add auto storage file=test2.raw,if=virtio
host: Segmentation fault
Running with gdb gives:
dbg:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fc15550a6e0 (LWP 9085)]
virtio_blk_init (dev=0xcb2010)
at /build/kvm/qemu-kvm-0.11.0/build/hw/virtio-blk.c:439
439 /build/kvm/qemu-kvm-0.11.0/build/hw/virtio-blk.c: No such file or
directory.
in /build/kvm/qemu-kvm-0.11.0/build/hw/virtio-blk.c
Is this problem known?
Is pci-hotplug a qemu or kvm feature?
Where to file a bug?
Regards
Thomas
reply other threads:[~2009-11-16 14:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='hdrn97$9ah$1@ger.gmane.org' \
--to=thomas.besser@kit.edu \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.