KVM-88 broke VirtIO Hard Disks
Hi All ! In addition to Floppy controllers KVM-88 also break VirtIO hard disks. (Windows 2003 Drivers refuse to work now) Linux (RHEL 5.3/x64) still boots off VirtIO Hard Disk. It turned out to be a Qemu merge into KVM userspace: kvm-87-119-ga8b7f95 (commit a8b7f959d1fd97c4ccaf08ce750020ecd08b4c88) Can you look into it? -Alexey, 23.7.2009. -- 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
KVM-88 broke floppy controller
Hi All ! I found a new bug in Floppy controller -- usually I report bugs to Avi, but since he is not here, I decided to report to mailing list. This bugs prevents Windows booting with Floppy inserted. Qemu command to reproduce: ./qemu-kvm -fda myfloppy.vfd -cdrom /isos/windows/Windows2003_r2_VLK.iso -boot d It won't boot from CD-ROM (black screen), and will stuck during booting from hard disk. It affects both Intel AMD systems, but not Qemu emulator. (-no-kvm works) I did bisect and found bug in KVM userspace git: kvm-87-239-gbb598da ( commit bb598da496c040d42dde564bd8ace181be52293e by Glauber Costa) on 6.7.2009. Can you look at it please ? -Alexey Eromenko -- 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-88 broke floppy controller
- Gleb Natapov g...@redhat.com wrote: On Wed, Jul 22, 2009 at 07:43:51AM -0400, Alexey Eromenko wrote: Hi All ! I found a new bug in Floppy controller -- usually I report bugs to Avi, but since he is not here, I decided to report to mailing list. This bugs prevents Windows booting with Floppy inserted. Qemu command to reproduce: ./qemu-kvm -fda myfloppy.vfd -cdrom /isos/windows/Windows2003_r2_VLK.iso -boot d It won't boot from CD-ROM (black screen), and will stuck during booting from hard disk. It affects both Intel AMD systems, but not Qemu emulator. (-no-kvm works) I did bisect and found bug in KVM userspace git: kvm-87-239-gbb598da ( commit bb598da496c040d42dde564bd8ace181be52293e by Glauber Costa) on 6.7.2009. Can you look at it please ? Can you try this patch? http://patchwork.kernel.org/patch/36661/ Thanks Gleb ! This indeed fixed my problem ! -Alexey -- 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 vs Xen/OpenVZ for VPS hosting business
- howard chen howac...@gmail.com wrote: Hello, Currently both Xen and OpenVZ are well known and mature product used in hosting companies. How about KVM? What are the advantages if I use KVM as the VPS solution? E.g. performance? Due to a difference between virtualization and containers concepts, KVM won't be faster than OpenVZ. KVM may approach similar performance to Xen, if you use VirtIO para-virtual drivers. security? KVM is a kernel module, while Xen and OpenVZ is a whole modified kernel, which means that, _theoretically_, KVM has much lower chance of having security holes. maintainity? Kernel maintainability: Here KVM has an edge again, because it is a kernel module it is much easier to port to newer versions of the Linux kernel. Xen and OpenVZ require much more significant work and code changes to keep up-to-date with newer kernels. For KVM forward-porting is natural, as it is integrated in the kernel. Distro maintainability: KVM can be very easily maintained for new and old distros alike, even those Linux distros that are not virtualization aware. Maintenance of Xen or OpenVZ support on less popular Linux distros is a big problem. -Alexey -- 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: Problem with Grub and KVM 88
- Erik Wartusch e.wartu...@mitacs.com wrote: Hi all, Following problem. I recently upgraded kvm from 7.2 (Debian Lenny repository version) to the newest 88 KVM. Since then when I first started and stopped a Debian Lenny virtual instance (guest) at the next (second) start I get the following error: Grub loading, please wait. Error 2. So the first time its booting the second not, resulting with this error. I have the Debian Lenny VM installer booting fine on KVM-88 (32 and 64-bit CD-ROM ISOs). Host is RHEL 5.3/x64. If you try if -no-kvm option, does it work? -Alexey -- 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-AUTOTEST PATCH 1/2] KVM test: add shutdown test
Michael I don't fully understand why shutdown test is needed; Shutdown is tested during reboot, where GuestOS must de-init itself. -- 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: [Autotest] [KVM-AUTOTEST PATCH 1/4] Make all programs on kvm test use /usr/bin/python
- Martin Bligh mbl...@google.com wrote: On Wed, Jun 10, 2009 at 4:01 AM, Alexey Eromenkoaerom...@redhat.com wrote: Even better would be to use /usr/bin/python2. That doesn't seem to exist, on Ubuntu at least. Red Hat systems have it. /usr/bin/python2 is a symlink to /usr/bin/python (which is python2 executable) Is there any Ubuntu-compatible way of achieving this? -Alexey -- 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
[KVM-AUTOTEST] New test module: iperf
Hello KVM-Autotest users developers, I want to present a new KVM-Autotest module here: kvm_iperf. Basically it tests networking functionality, stability and performance of guest OSes. This test is cross-platform -- i.e. it works on both Linux and Windows VMs. I was under development since some time, and now I feel it is mature for a release. The test is dependent on python and KVM-Autotest framework. Basically the module consists of kvm_iperf.py, and small modifications to kvm_runtest_2.py and kvm_tests.py. You will also need to create a new misc subdirectory inside your kvm_runtest_2/. (# mkdir kvm_runtest_2/misc) And put two files there: 1. iperf -- this one must be Linux i586 binary 2. iperf.exe -- this one must be Win32 binary optionally third file: 3. iperf64 -- this one must be Linux x64 binary On Linux platform we could compile on the fly, but I decided not to (for now), because some Linux guests do not have a compiler. Also using i586 binary ensures that it can be used on both i586 and x64 guests. But you can use both, if you modify kvm_tests.py accordingly. optional parameters: iperf_duration -- allows to specify long test durations (default = 5 sec) iperf_parallel_threads -- allows to test multiple network threads in parallel (default = 1 thread) Theoretically in future we could support other UNIXes as well (BSD and Solaris). For this you will need only to add respective binaries in misc/ folder, and modify kvm_tests.py for respective OSes. iperf: http://sourceforge.net/projects/iperf - source for latest. iperf for Windows: http://dast.nlanr.net/Projects/Iperf/iperf-1.7.0-win32.exe - stable binary. http://noc.pregi.net/iperf.html To commit this module we may need to commit iPerf binaries, which I hate to do. but I have no better idea for now. Please review it commit it. -Alexey Eromenko kvm_iperf.py Description: Binary data kvm_runtest_2.py.patch Description: Binary data kvm_tests.cfg.sample.2009-04-26 Description: Binary data kvm_tests.cfg.sample.2009-04-26.iperf.patch Description: Binary data kvm_tests.cfg.sample.2009-04-26.iperf.patched Description: Binary data
Re: [Autotest] [KVM-AUTOTEST PATCH 1/4] Make all programs on kvm test use /usr/bin/python
Even better would be to use /usr/bin/python2. This is because future distros will include python3, which is incompatible with python2 code. python will be symlink of python3. -Alexey -- 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-86 not exposing 64 bits CPU anymore, NICE
- Gilles PIETRI contact+...@gilouweb.com wrote: Hi, I'm quite pissed off. I just upgraded to kvm-86 on a host that has worked nicely on kvm-78 for quite some time. But since I was fearing the qcow2 corruption issues, I wanted to upgrade kvm-86. After testing the performance, I decided to switch. How stupid that was. That was really putting too much trust in KVM. Now I can't have 64 bits CPUs on my guests. My host is running a 2.6.27.7 kernel, and is x86_64 enabled. Until the upgrade, guests were running x86_64 fine. Now, it says long mode can't be used or something like that, and I can only have 32 bits guests. Looks really like the bug explained here: http://www.mail-archive.com/kvm@vger.kernel.org/msg09431.html If I use -no-kvm, it works, but obviously, I want to be able to have kvm support enabled. Now, I really am happy about this upgrade, and I'm gonna have to roll it back. I really would appreciate some help on this.. Gilles Hi Gilles, What are you saying is very strange, because KVM-Autotest has passed all tests for KVM-86 release, and I can say that 64-bit guests work here. (both Intel AMD, on RHEL 5.3/x64) -Alexey -- 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
