On Wed, Oct 21, 2009 at 04:59:20PM -0700, Shirley Ma wrote: > Hello Michael, > > >There was a recent bugfix in qemu-kvm I pushed. > >Could you please verify that you have cec75e39151e49cc90c849eab5d0d729667c9e68 > ? > > Yes, I cloned your qemu-kvm and kernel git. Here is "git log" output: > > commit cec75e39151e49cc90c849eab5d0d729667c9e68 > Author: Michael S. Tsirkin <mst@xxxxxxxxxx> > Date: Wed Oct 21 12:34:36 2009 +0200 > > vhost: use acked features, not all features > > >This was recently reported without vhost, did not > >reproduce it here yet. > >And you say you do not see the above without vhost? > > I saw above with and without vhost, but the network worked with the errors > without vhost. Could you please supply more information? What is the qemu command line you use? What guest do you use? How is the network configured? Please attach tcpdump to interfaces in host and guest, and run ping from guest. Do you see any traffic? Does it look sane? > Thanks > Shirley > > > Inactive hide details for "Michael S. Tsirkin" ---10/21/2009 01:24:58 PM---On > Wed, Oct 21, 2009 at 12:59:50PM -0700, Shirley Ma"Michael S. Tsirkin" ---10/21/ > 2009 01:24:58 PM---On Wed, Oct 21, 2009 at 12:59:50PM -0700, Shirley Ma wrote: > > "Michael S. [cid] * > Tsirkin" To Shirley Ma/Beaverton/IBM@IBMUS > <mst@xxxxxxxxxx> [cid] * > cc David Stevens/Beaverton/IBM@IBMUS, > 10/21/2009 01:19 kvm@xxxxxxxxxxxxxxx, sri@xxxxxxxxxxxxxxxxxx > PM [cid] * > Subject Re: vhost-net patches > * * > > On Wed, Oct 21, 2009 at 12:59:50PM -0700, Shirley Ma wrote: > > Hello Micahel, > > > > I have set up guest kernel 2.6.32-rc5 with MSI configured. Here are errors > what > > I have got: > > > > 1. First, qemu complained extboot.bin not found, I copied the file from > > optionrom/ dir to pc-bios/ dir, this problem is gone. > > > > 2. Second, when guest boot up, it has lots of errors as below. Without vhost > > support, I still saw same errors but the guest interface can communicate with > > host, but with vhost, it doesn't work. > > There was a ecent bugfix in qemu-kvm I pushed. > Could you please verify that you have cec75e39151e49cc90c849eab5d0d729667c9e68 > ? > > > > I am posting the errors from /var/log/ > > messages here: > > > > virtio-pci 0000:00:03.0: can't find IRQ for PCI INT A; probably buggy MP > table > > virtio-pci 0000:00:04.0: can't find IRQ for PCI INT A; probably buggy MP > table > > virtio-pci 0000:00:04.0: irq 24 for MSI/MSI-X > > virtio-pci 0000:00:04.0: irq 25 for MSI/MSI-X > > IRQ handler type mismatch for IRQ 1 > > current handler: i8042 > > Pid: 335, comm: modprobe Not tainted 2.6.32-rc5 #3 > > Call Trace: > > __setup_irq+0x24c/0x2ac > > request_threaded_irq+0x113/0x179 > > ? vring_interrupt+0x0/0x2f > > vp_try_to_find_vqs+0x4a3/0x4e0 [virtio_pci] > > ? blk_done+0x0/0xa7 [virtio_blk] > > vp_find_vqs+0x1b/0x62 [virtio_pci] > > virtblk_probe+0xbd/0x3d0 [virtio_blk] > > ? sysfs_do_create_link+0xbb/0xfd > > ? blk_done+0x0/0xa7 [virtio_blk] > > ? add_status+0x1f/0x24 > > virtio_dev_probe+0x91/0xb0 > > driver_probe_device+0x79/0x105 > > __driver_attach+0x43/0x5f > > bus_for_each_dev+0x3d/0x67 > > driver_attach+0x14/0x16 > > ? __driver_attach+0x0/0x5f > > bus_add_driver+0xa2/0x1c9 > > driver_register+0x8b/0xeb > > ? init+0x0/0x24 [virtio_blk] > > register_virtio_driver+0x1f/0x22 > > init+0x22/0x24 [virtio_blk] > > do_one_initcall+0x4c/0x13a > > sys_init_module+0xa7/0x1db > > syscall_call+0x7/0xb > > virtio-pci 0000:00:04.0: irq 24 for MSI/MSI-X > > virtio-pci 0000:00:04.0: irq 25 for MSI/MSI-X > > > vda: vda1 vda2 > > EXT3-fs: INFO: recovery required on readonly filesystem. > > EXT3-fs: write access will be enabled during recovery. > > kjournald starting. Commit interval 5 seconds > > EXT3-fs: recovery complete. > > EXT3-fs: mounted filesystem with writeback data mode. > > udevd version 127 started > > virtio-pci 0000:00:03.0: irq 26 for MSI/MSI-X > > virtio-pci 0000:00:03.0: irq 27 for MSI/MSI-X > > virtio-pci 0000:00:03.0: irq 28 for MSI/MSI-X > > IRQ handler type mismatch for IRQ 1 > > current handler: i8042 > > Pid: 440, comm: modprobe Not tainted 2.6.32-rc5 #3 > > Call Trace: > > __setup_irq+0x24c/0x2ac > > request_threaded_irq+0x113/0x179 > > ? vring_interrupt+0x0/0x2f > > vp_try_to_find_vqs+0x4a3/0x4e0 [virtio_pci] > > ? skb_recv_done+0x0/0x36 [virtio_net] > > vp_find_vqs+0x1b/0x62 [virtio_pci] > > virtnet_probe+0x265/0x347 [virtio_net] > > ? skb_recv_done+0x0/0x36 [virtio_net] > > ? skb_xmit_done+0x0/0x1e [virtio_net] > > ? add_status+0x1f/0x24 > > virtio_dev_probe+0x91/0xb0 > > driver_probe_device+0x79/0x105 > > __driver_attach+0x43/0x5f > > bus_for_each_dev+0x3d/0x67 > > driver_attach+0x14/0x16 > > ? __driver_attach+0x0/0x5f > > bus_add_driver+0xa2/0x1c9 > > driver_register+0x8b/0xeb > > ? init+0x0/0xf [virtio_net] > > register_virtio_driver+0x1f/0x22 > > init+0xd/0xf [virtio_net] > > do_one_initcall+0x4c/0x13a > > sys_init_module+0xa7/0x1db > > syscall_call+0x7/0xb > > virtio-pci 0000:00:03.0: irq 26 for MSI/MSI-X > > virtio-pci 0000:00:03.0: irq 27 for MSI/MSI-X > > > > 3. The guest interface is up, and cat /proc/interrupts outputs: > > > > 24: 0 PCI-MSI-edge virtio1-config > > 25: 2571 PCI-MSI-edge virtio1-virtqueues > > 26: 0 PCI-MSI-edge virtio0-config > > 27: 0 PCI-MSI-edge virtio0-virtqueues > > > > Thanks > > Shirley > -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
