Re: QEMU's now on Google+
On Wed, Nov 09, 2011 at 11:25:10AM -0600, Anthony Liguori wrote: On 11/09/2011 11:14 AM, Rodrigo Campos wrote: On Wed, Nov 09, 2011 at 09:24:37AM -0600, Anthony Liguori wrote: Hi, I've created a Google+ page for QEMU[1]. You'll also notice a button on the qemu.org wiki that links to the Google+ page. I'll be posting release information to this page along with any QEMU news. If you find qemu-devel too busy to follow, then following the G+ page might be a good option for you. By any chance do you know if is it possible to subscribe via RSS or something like that ? There are third party gateways. For instance, the following URL will give you an Atom feed for QEMU's G+ page: http://plusfeed2.appspot.com/101344524535025574253 Thanks a lot! -- 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's now on Google+
On Wed, Nov 09, 2011 at 09:24:37AM -0600, Anthony Liguori wrote: Hi, I've created a Google+ page for QEMU[1]. You'll also notice a button on the qemu.org wiki that links to the Google+ page. I'll be posting release information to this page along with any QEMU news. If you find qemu-devel too busy to follow, then following the G+ page might be a good option for you. By any chance do you know if is it possible to subscribe via RSS or something like that ? Thanks, Rodrigo -- 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: Network available but no network connectivity
On Mon, Aug 08, 2011 at 07:17:47AM +0200, Satz Klauer wrote: Hi, currently I fail with a problem that I already had (and never could solve) with QNX 6.4.1, now I tried again with QNX 6.5 but still don't get it working. I start qemu with qemu-system-x86_64 -hda qnx.img -m 512 -net nic -net user (brain-attritional simple and well-working with all other operating systems). QNX comes up without problems and it detects the network card successfully. But with that network interface nearly nothing is possible: DHCP does not work, assigning a fixed IP 10.0.2.15 / netmask 255.255.255.0 works but I can't reach anything outside of this qemu-envorinment. The default gateway is set to 10.0.2.2. Within the QNX-forum nobody could help, so may be here somebody has some hints what I could try? Yes, I have QNX (although I only tried QNX 6.3.2) as guest with working network. As I posted on [1], I needed -net nic,model=ne2k_pci and to follow the instructions in [2], the part that says: If this is not done, networking will not work, so we have to manually start it every time. To do this, type. Although I've only done this the first time and when I re-start the guest it just works. I don't know if this would work on QNX 6.5, but I suspect it does. Thanks a lot, Rodrigo [1]: http://www.linux-kvm.org/page/Guest_Support_Status [2]: http://community.qnx.com/sf/wiki/do/viewPage/projects.qemu/wiki/NeutrinoAsGuestInQEMU;jsessionid=82CAC3EC7E4C62A6DC51A1E021618862 -- 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: [PATCH] kvm tools: Enable earlyprintk=serial by default
On Sun, May 08, 2011 at 09:39:34AM +0200, Ingo Molnar wrote: diff --git a/tools/kvm/kvm-run.c b/tools/kvm/kvm-run.c index 764a242..eb50b6a 100644 --- a/tools/kvm/kvm-run.c +++ b/tools/kvm/kvm-run.c @@ -409,7 +409,7 @@ int kvm_cmd_run(int argc, const char **argv, const char *prefix) kvm-nrcpus = nrcpus; memset(real_cmdline, 0, sizeof(real_cmdline)); - strcpy(real_cmdline, notsc noapic noacpi pci=conf1 console=ttyS0 ); + strcpy(real_cmdline, notsc noapic noacpi pci=conf1 console=ttyS0 earlyprintk=serial); I think the space at the end of the string that you delete, squashes the early printk option with the next one (root= in your case), like in the output you show: [0.00] Command line: notsc noapic noacpi pci=conf1 console=ttyS0 earlyprintk=serialroot=/dev/vda1 rw I mean here ^ Thanks, Rodrigo -- 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: PCI Device Assignment status
On Sun, Sep 05, 2010 at 07:00:08PM +0200, Joerg Roedel wrote: On Fri, Sep 03, 2010 at 04:38:00PM -0600, Alex Williamson wrote: On Fri, Sep 3, 2010 at 9:54 AM, Rodrigo Campos rodr...@sdfg.com.ar wrote: Hi! I wanted to know the status of PCI device assignment. As far as I can see in the webpage and in the mailing list, it seems to be working ok if you have VT-d support on the motherboard and cpu. But if it isn't too much trouble, I wanted some confirmation about this, since I'm not sure and I don't want to buy hardware to test this when there is no way it's going to work :) Yes, it works if you have VT-d support (Intel) or AMD IOMMU (note this is different than the AMD GART that's often used as an IOMMU). The Intel boxes are a lot easier to find. For an AMD IOMMU you just need to buy a Mainboard with the AMD 890FX chipset. As far as I know all available boards support IOMMU with the latest BIOS. On the server-side, look for an AMD SR56x0 chipset [where x=(5|7|9)]. Great, thanks a lot! -- 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: PCI Device Assignment status
On Mon, Sep 06, 2010 at 03:11:32PM +0400, Konstantin Khlebnikov wrote: On Fri, 3 Sep 2010 19:54:00 +0400 Rodrigo Campos rodr...@sdfg.com.ar wrote: I wanted to know the status of PCI device assignment. I successfully use kvm for assignment second GPU in my notebook (Thinkpad T500) into guest OS, two months ago. But it require several hacks for correct vga-bios passthrough and it work only for linux guests -- all windows guests hung whole system at early boot. Currently I haven't enough free time to finish this investigation. Thanks, its good to know. Luckily I don't need to assign a second GPU, so I won't need those hacks :) Thanks a lot, Rodrigo -- 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: PCI Device Assignment status
On Fri, Sep 03, 2010 at 04:38:00PM -0600, Alex Williamson wrote: On Fri, Sep 3, 2010 at 9:54 AM, Rodrigo Campos rodr...@sdfg.com.ar wrote: Also, I wanted to confirm that there is no limit in the maximun PCI cards that could be given to a guest (like VMWare which only lets you give at most 2 cards to a guest, if I'm not wrong) and which version of qemu-kvm/Linux kernel I need for propper support. The only limit I'm aware of is the number of slots on a bus (32), a few of which are used by qemu emulated devices and can't be removed. Great, so it shouldn't be a problem I guess =) Any of the 0.12 releases should work fine. Also note that there are Cool, thanks! also device and driver dependencies that can be far more subtle in whether the device can work with passthrough or not. Things like whether it has device dependent registers in pci config space, if the driver expects specific capabilities at certain offsets, if it's a multi-function device that shares nvram and uses the function as an index offset, drivers that assume a bridge topology for a given vid/did, etc... SR-IOV devices are designed for this, so should work, otherwise you might also post the cards you'd like to use and see if anyone has experience with them. Ahh, I see. Thanks a lot for the information :) I will need, for sure, at least this card: http://www.dialogic.com/products/serial_protocol_adapters/Eiconcard_C_Series.htm?techspec=1regID=4599 But I don't really know what the driver does. I will use it on QNX (yeah, I know it wouldn't be hard real-time :)), so it's not the driver/software it says there. It's this one, in case it matters/gives anyone some idea: http://www.gandacar.ca/index.php?option=com_contentview=articleid=60Itemid=89 I think that this card does almost everything in hardware and the driver only does some communication (although I don't know how) Have anyone used this card with passthrough or have some intuition if it should work ? :) Thanks a lot, Rodrigo -- 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: PCI Device Assignment status
On Sat, Sep 04, 2010 at 02:48:46AM +0200, Kenni Lund wrote: 2010/9/3 Rodrigo Campos rodr...@sdfg.com.ar: Hi! I wanted to know the status of PCI device assignment. As far as I can see in the webpage and in the mailing list, it seems to be working ok if you have VT-d support on the motherboard and cpu. But if it isn't too much trouble, I wanted some confirmation about this, since I'm not sure and I don't want to buy hardware to test this when there is no way it's going to work :) It highly depends on what you want to passthrough...if it's some well-known SR-IOV server NIC, then sure, it will probably work. If you want to passthrough various PCI devices in a regular desktop system or workstation, then forget it. It's none of this. It's an X.25 card (there are more details on the mail I've just sent to Alex) I've been playing that various PCI devices in a regular desktop system game for the last 8 months on my HTPC. I've been running with both stable versions of KVM as well as self-compiled versions from git during this time. The tests I have performed were done on two different VT-d capable boards (a Gigabyte EQ45M-S2 and a Intel DQ57TM). I've tried to passthrough 2 PCI TV tuners (Hauppauge 500 + Hauppauge 1300), 2 PCI USB 2.0 cards (can't remember the brands), 1 onboard USB controller (on a Gigabyte EQ45M-S2), and finally a PCI Express USB 3.0 card (Asrock). The only device which works correctly, is the Hauppauge 500 card. I bought the USB 3.0 card ONLY to see if it would help with a PCI Express card instead of the regular PCI cards I had tested...but no, it didn't change anything. In my tests the cards almost works in some cases - eg. the card gets correctly initialized in the guest and you can start to use it, but then you'll have timing issues, driver crashes, client program crashes, etc. etc. Ahhh, thanks for sharing your experience. I guess I will have to try then :) Thanks, Rodrigo -- 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: Question on stopping KVM start at boot
On Wed, Mar 10, 2010 at 04:07:09PM +0800, sati...@pacific.net.hk wrote: Hi folks. Host - ubuntu 9.10 64bit Virtualizer - KVM I need to stop KVM starting at boot. I added following 2 lines at the bottom of /etc/modprobe.d/blacklist.conf blacklist kvm blacklist kvm-amd Reboot PC It doesn't work. $ lsmod | grep kvm kvm_amd41556 0 kvm 190648 1 kvm_amd Please what further command I have to run in order to activate the new blacklist.conf ? /etc/init.d/qemu-kvm loads the module. So you probably must not run it on start up or teach it how to read the blacklist. Perhaps this is more appropriate to ask on an ubuntu-specific mailing list, since this is an ubuntu problem. Thanks, Rodrigo -- 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: Question on stopping KVM start at boot
On Thu, Mar 11, 2010 at 11:59:45AM +0800, sati...@pacific.net.hk wrote: Hi Dustin, Or you can edit the /etc/init.d/kvm or /etc/init.d/qemu-kvm init script and add the -b option to the modprobe calls in there. $ cat /etc/init.d/qemu-kvm | grep modprobe if modprobe $module Where shall I add -b option? Thanks If I'm not wrong, there. That if is loading the module and sees the return code to give an error if it fails to load. Thanks, Rodrigo -- 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: KVM compilation
On Wed, Feb 10, 2010 at 02:48:41PM +0530, Puja Gupta wrote: Hello friends, I have downloaded package qemu-kvm_0.11.0-0ubuntu6_i386.deb and when i double click it,it tells 'Error: Dependency is not satisfiable: bridge-utils'.i tried by downloading the package again but still problem exists. Any help would be of great use.Thanks . So try installing bridge-utils too. Or download them from a debian repo using apt. That way it will download all needed deps. Thanks, Rodrigo -- 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: Serial Port Driver does not handle interrupt
On Tue, Nov 17, 2009 at 07:00:56PM +0100, Erik Rull wrote: Rodrigo Campos wrote: On Tue, Nov 17, 2009 at 12:01:08AM +0100, Erik Rull wrote: Erik Rull wrote: Any Ideas? I also tested other IRQ lines and other ttyS* on the system - same behaviour. fixed, apic on host side was disabled, kvm / qemu seems to need it. I think I hit the same issue. What did you do exactly to solve it ? Enable a kernel option ? May I ask which one ? :) Sorry, I dont have the hardware right now (so I can't play with apic options). I will have it in a few weeks, so that's why I am asking :) I enabled the APIC stuff in Kernel and removed my lapic noapic boot parameters. APIC is enabled if you look into /proc/interrupts and the IRQ type is something with apic and not pc / xt. Ahh, thanks :) Also ensure that the IRQ line of the serial port matches those of your linux drivers! Otherwise the interrupt gets lost and you'll see some strange behaviours (Chars missing, delayed responses,...). I will check that too. Thanks a lot, Rodrigo -- 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: Serial Port Driver does not handle interrupt
On Tue, Nov 17, 2009 at 12:01:08AM +0100, Erik Rull wrote: Erik Rull wrote: Any Ideas? I also tested other IRQ lines and other ttyS* on the system - same behaviour. fixed, apic on host side was disabled, kvm / qemu seems to need it. I think I hit the same issue. What did you do exactly to solve it ? Enable a kernel option ? May I ask which one ? :) Sorry, I dont have the hardware right now (so I can't play with apic options). I will have it in a few weeks, so that's why I am asking :) Thanks a lot, Rodrigo -- 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: Poor Write I/O Performance on KVM-79
On Sun, Jan 4, 2009 at 11:24 AM, Avi Kivity a...@redhat.com wrote: Alexander Atticus wrote: Hello! I have been experimenting with KVM and have been experiencing poor write I/O performance. I'm not sure whether I'm doing something wrong or if this is just the current state of things. While writing to the local array on the node running the guests I get about 200MB/s from dd (bs=1M count=1000) or about 90MB/s write performance from iozone (sequencial) when I write to a 2G file with a 16M record length. The node is an 8 disk system using 3ware in a RAID50 configuration. It has 8GB of RAM. The guests get much slower disk access. The guests are using file based backends (tried both qcow2 and raw) with virtio support. With no other activity on the machine, I get about 6 to 7MB/s write performance from iozone with the same test. Guests are running Debian lenny/sid with 2.6.26-1-686. qcow2 will surely lead to miserable performance. raw files are better. best is to use lvm. What do you mean with best is to use lvm ? You just say to use raw images on an lvm partition because you can easily resize it ? Or somehow images only use the used space of the raw file when used with lvm ? Or there's some trick to make it ? Thanks a lot, Rodrigo -- 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: Poor Write I/O Performance on KVM-79
On Sun, Jan 4, 2009 at 5:48 PM, Avi Kivity a...@redhat.com wrote: Rodrigo Campos wrote: qcow2 will surely lead to miserable performance. raw files are better. best is to use lvm. What do you mean with best is to use lvm ? You just say to use raw images on an lvm partition because you can easily resize it ? Or somehow images only use the used space of the raw file when used with lvm ? Or there's some trick to make it ? Using lvm directly (-drive file=/dev/vg/volume) is both most efficient and most reliable, as there are only a small amount of layers involved. However, you need to commit space in advance (you can grow your volume, but that takes guest involvement and cannot be done online at the moment). Using a raw file over a filesystem will be slow since the host filesystem will be exercised, and due to fragmentation. Raw files only occupy storage as they are used, but they are difficult to manage compared to qcow2 files. Qcow2 files are most flexible, but the least performing. Ahhh. Thanks a lot for the explanation :) Rodrigo -- 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: KVM rpm/deb packages for recent releases.
On Wed, Oct 8, 2008 at 4:06 PM, jd [EMAIL PROTECTED] wrote: Hi - I am looking for installable packages (both rpms and deb) for recent versions of KVM (kvm-70 and above). kvm-72 is in debian testing/unstable. You say for etch and a half ? I didn't find it in backports.org, but you could try downloading the source package from testing and compile it (you need to add a deb-src line to the sources.list), something like: apt-get build-dep kvm; apt-get source kvm; cd kvm-*; debuild -us -uc (I didn't test it, but it shouldn't be too different, perhaps you could not have some dependency you can install from testing or compile this way too:) Thanks, Rodrigo -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
