kvm-79 release
This is the first release to fully support pci device assignment. You can assign a pci device to qemu on the command line, or hot-plug it in via the monitor. Note that at this time, Linux 2.6.28 is required on the host.
Upstream qemu recently gained kvm support. At this time a lot is missing in upstream (smp, performance) so this the upstream capabilities are not used yet. Over time we will switch to using qemu upstream for more functionality.
Changes from kvm-78:
- merge qemu-svn
- fix qcow2 problems with scsi
- 'info chardev' monitor command
- device assignment userspace (Amit Shah, Muli Ben Yehudah, Ben-Ami Yassour, Weidong Han, Or Sagi, Nir Peleg, Glauber Costa, Xiantao Zhang)
- multiple processor infrastructure for ppc (Hollis Blanchard)
- fix error handling in eventfd() emulation (Mark McLoughlin)
- handle large mtu with virtio-net (Mark McLoughlin)
- move x86 specific device assignment code to x86 files (Christian Ehrhardt)
- fix 'pci_add' command descriptor (Weidong Han)
- enable pci function level reset for device assignment (Sheng Yang)
- fix incorrect handling of aliases gfns (Izik Eidus)
- ppc optimizations (Hollis Blanchard, Christian Ehrhardt)
- disallow guests from setting memory type when using EPT (Sheng Yang)
- fix cpuid leaf 11 loop termination (Nitin A Kamble)
- fix cpuid multiple leaf iteration (Nitin A Kamble)
- fix ia64 uniprocessor build (Xiantao Zhang)
- fix ppc Kbuild constraints (Hollis Blanchard)
- fix pit initialization memory leak
Notes:
If you use the modules bundled with kvm-79, you can use any version
of Linux from 2.6.16 upwards. You may also use kvm-79 userspace with the kvm modules provided by Linux 2.6.25 or above. Some features may only be available in newer releases.
Signature · 2 lines
I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.
Quoted 9 lines · Avi Kivity
This is the first release to fully support pci device assignment. You can assign a pci device to qemu on the command line, or hot-plug it in via the monitor. Note that at this time, Linux 2.6.28 is required on the host.
Upstream qemu recently gained kvm support. At this time a lot is missing in upstream (smp, performance) so this the upstream capabilities are not used yet. Over time we will switch to using qemu upstream for more functionality.
hi,
- guest fedora-9 latest kernel-2.6.26.6-79.fc9.i686 still not boot,
- guest centos-5 x86_64's kernel-2.6.18-92.1.17.el5 still gives the same crash as kvm-78 (screenshot attached),
- guest mandrake-10 still can't boot
so imho still not the best release:-(
Signature · 1 line
Levente "Si vis pacem para bellum!"
Quoted 11 lines · Farkas Levente
Quoted 9 lines · Avi Kivity
This is the first release to fully support pci device assignment. You can assign a pci device to qemu on the command line, or hot-plug it in via the monitor. Note that at this time, Linux 2.6.28 is required on the host.
Upstream qemu recently gained kvm support. At this time a lot is missing in upstream (smp, performance) so this the upstream capabilities are not used yet. Over time we will switch to using qemu upstream for more functionality.
Quoted 4 lines
hi,
- guest fedora-9 latest kernel-2.6.26.6-79.fc9.i686 still not boot,
- guest centos-5 x86_64's kernel-2.6.18-92.1.17.el5 still gives the same crash as kvm-78 (screenshot attached),
Those two should be fine with this patch [1]. You are welcome to test it and be the first (mmmh...) to provide feedback on it.
Quoted 1 line
- guest mandrake-10 still can't boot
Can't help here, your test boots fine on OpenSuse's 2.6.25.18-0.2 with kvm.git for me as well.
Quoted 2 lines
so imho still not the best release:-(
Bugs happen, and some corner cases may remain unfixed for a longer time as they happen to be hard to track down.
Jan
[1] http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/24409
Quoted 7 lines · Jan Kiszka
Quoted 3 lines · Farkas Levente
- guest fedora-9 latest kernel-2.6.26.6-79.fc9.i686 still not boot,
- guest centos-5 x86_64's kernel-2.6.18-92.1.17.el5 still gives the same crash as kvm-78 (screenshot attached),Those two should be fine with this patch [1]. You are welcome to test it and be the first (mmmh...) to provide feedback on it.
I've been able to reproduce the issue on CentOS 5 x86_64 guests quite reliably; after applying the patch to kvm-79 (with the necessary filename munging), this issue does indeed appear to be resolved.