Re:
help -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE:
help OK, I'll bite... What do you need help with? Neil -- Neil Aggarwal, (281)846-8957, http://www.JAMMConsulting.com CentOS 5.4 KVM VPS $55/mo, no setup fee, no contract, dedicated 64bit CPU 1GB dedicated RAM, 40GB RAID storage, 500GB/mo premium BW, Zero downtime -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Recording interrupted instruction on ioapic_set_irq
Hi guys, I'm trying to record the instruction pointer at the exact time a guest was delivered an IOAPIC interrupt. Take for example a PS2 keyboard press. Clearly, when I read IP during the subsequent exit for IO_INSTRUCTION I'm just recording the IP of io_read in the handler, and not the IP at actual interrupt delivery. Maybe I'm missing something fundamental. It doesn't look like exits for EXTERNAL_INTERRUPT (shouldn't it?) or INTERRUPT_WINDOW correspond one-to-one with delivery of these PS2 interrupts. Just setting request_interrupt_window for these IRQs didn't give me an INTERRUPT_WINDOW for each key. I guess since the guest doesn't usually have interrupts masked when I press a key means delivery won't wait for the window. Could I record during delivery? I figure I could look at the stack during the IO_INSTRUCTION exit and figure out what instruction was actually interrupted, but this would be a Linux-specific solution. Any other ideas? I think even a simple description of how these interrupts are being delivered to the guest would help me out a lot. Thanks, Kurt -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Hot-adding disk on VM
Hi, Dustin. On Sunday, 11 October 2009 21:25:19 -0500, Dustin Kirkland wrote: According to I see in this document [1], is necessary that is loaded two modules in the guest: acpiphp and pci_hotplug. The pci_hotplug module is loaded. Nevertheless, in spite of existing the acpiphp module, cannot be loaded: chandra:~# lsmod|grep pci_hotplug pci_hotplug 23460 0 chandra:~# modprobe acpiphp FATAL: Error inserting acpiphp (/lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko): No such device chandra:~# locate acpiphp | grep 686 /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp.ko /lib/modules/2.6.26-2-686/kernel/drivers/pci/hotplug/acpiphp_ibm.ko Which could be being the problem? I was doing other tests this time with Linux 2.6.31.2 compiled by myself from the sources of kernel.org. This time with loading the acpiphp module, the pci_hotplug module was loaded automatically without I get some type of error message. central:~# lsmod | grep acpiphp central:~# central:~# modprobe acpiphp central:~# central:~# lsmod | grep acpiphp acpiphp 22140 0 pci_hotplug 29024 1 acpiphp Then, I tried to add a disk of the following way in host: (qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio OK domain 0, bus 0, slot 5, function 0 In the guest: Oct 11 18:09:01 central kernel: [ 833.403875] pci :00:02.0: BAR 6: bogus alignment [0x0-0x0] flags 0x2 Oct 11 18:09:01 central kernel: [ 833.406337] decode_hpp: Could not get hotplug parameters. Use defaults Oct 11 18:09:01 central kernel: [ 833.430492] virtio-pci :00:05.0: enabling device ( - 0001) Oct 11 18:09:01 central kernel: [ 833.452268] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 Oct 11 18:09:01 central kernel: [ 833.454668] virtio-pci :00:05.0: PCI INT A - Link[LNKA] - GSI 10 (level, high) - IRQ 10 Oct 11 18:09:01 central kernel: [ 833.500051] Clocksource tsc unstable (delta = -148257950 ns) Oct 11 18:09:01 central kernel: [ 833.566755] vda: vda1 Then I attempt to remove the device assuring previously that it is not being used in guest: (qemu) pci_del 5 In the guest: Oct 11 18:13:32 central kernel: [ 1104.144179] virtio-pci :00:05.0: PCI INT A disabled But if I want to add the device again, I get a segmentation fault of the process that handles this virtual machine: (qemu) pci_add auto storage file=/dev/vm/central-test,if=virtio Connection closed by foreign host. I can actually confirm this behavior. I've been struggling with this for a couple of days now. CC'ing QEMU, as I've discussed this a bit with Anthony Liguori. There's at least two related bugs we've been tracking: * https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/432154 * https://bugs.edge.launchpad.net/ubuntu/+source/qemu-kvm/+bug/419590 According to I see in Launchpad, there is a fix released for Qemu and qemu-kvm (Ubuntu). I'm using KVM-88 compiled from the source code obtained of the KVM official site. How I could apply these fix? There is some KVM version that includes these corrections in the official site? Thanks for your reply. Regards, Daniel -- Fingerprint: BFB3 08D6 B4D1 31B2 72B9 29CE 6696 BF1B 14E6 1D37 Powered by Debian GNU/Linux Squeeze - Linux user #188.598 signature.asc Description: Digital signature
Re: Hot-adding disk on VM
On Sat, Nov 7, 2009 at 7:01 PM, Daniel Bareiro daniel-lis...@gmx.net wrote: According to I see in Launchpad, there is a fix released for Qemu and qemu-kvm (Ubuntu). It's fix committed in QEMU, and Fix Released in Ubuntu's qemu-kvm. We in Ubuntu have released version of qemu-kvm-0.11.0 that includes an extra patch from Anthony, which he posted on the mailing list, and committed to QEMU's git tree. He hasn't officially released an upstream QEMU with the fix yet, though. I'm using KVM-88 compiled from the source code obtained of the KVM official site. How I could apply these fix? There is some KVM version that includes these corrections in the official site? Not that I know of, yet. You can pull the patch [1] we're carrying in Ubuntu, and apply it to qemu-kvm-0.11.0 [2] from the kvm website, if you like. [1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/karmic/qemu-kvm/karmic/annotate/head%3A/debian/patches/11_fix_virtio-blk_hot_add_after_remove.patch [2] http://sourceforge.net/projects/kvm/files/ :-Dustin -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCHv7 3/3] vhost_net: a kernel-level virtio server
On Sat, 7 Nov 2009 03:00:07 am Paul E. McKenney wrote: On Fri, Nov 06, 2009 at 03:31:20PM +1030, Rusty Russell wrote: But it's still nasty to use half an API. If it were a few places I would have open-coded it with a comment, or wrapped it. As it is, I don't think that would be a win. So would it help to have a rcu_read_lock_workqueue() and rcu_read_unlock_workqueue() that checked nesting and whether they were actually running in the context of a workqueue item? Or did you have something else in mind? Or am I misjudging the level of sarcasm in your reply? ;-) You read correctly. If we get a second user, creating an API makes sense. Thanks, Rusty. -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Qemu-devel] Re: [PATCH] Add VirtIO Frame Buffer Support
On Tue November 3 2009, Avi Kivity wrote: On 11/03/2009 01:25 PM, Vincent Hanquez wrote: not sure if i'm missing the point here, but couldn't it be hypothetically extended to stuff 3d (or video more 2d accel ?) commands too ? I can't imagine the cirrus or stdvga driver be able to do that ever ;) cirrus has pretty good 2d acceleration. 3D is a mega-project though. You're kidding right? Why do I have to switch to vmware-vga so dmesg in a guest doesn't take a couple minutes to scroll by? Maybe a configuration issue? -- Thomas Fjellstrom tfjellst...@shaw.ca -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
