qemu-0.11.0 Released
Last weekend kvm maintainers announced the release of version qemu-0.11.0. This release is in sync with upstream qemu release 0.11.0. If you’re using Fedora virtualization rawhide repository then this release is also available to you via a yum update. To access the latest fedora rawhide virtualization repository just follow instructions here. From the end user perspective, some notable additions are http block device support, slirp host network configurations, control over boot menu and vnc acl support. Most of these end user features were already included in the kvm-xx branch. Hardware virtualization features added include SR-IOV which allows you to share direct memory access to IO devices among multiple virtual guest machines.
Changes from the qemu-kvm-0.10 series:
- merge qemu 0.11.0
- qdev device model
- qemu-io
- i386: multiboot support for -kernel
- gdbstub: vCont support
- i386: control over boot menu
- i386: pc-0.10 compatibility machine type
- qcow2: use cache=writethrough by default
- i386: MCE emulation
- i386: host cpuid support
- slirp: host network config
- virtio: MSI-x support
- pci: allow devices to specify bus address
- migration: allow down time based threshold
- virtio-net: filtering support
- http block device support
- i386: expose numa topology to guests
- native preadv/pwritev support
- kvm: guest debugging support
- vnc: support for acls and gssapi
- monitor: allow multiple monitors
- device assignment: MSI-X support (Sheng Yang)
- device assignment: SR/IOV support (Sheng Yang)
- irqfd support (Gregory Haskins)
- drop libkvm, use some of the upstream kvm support (Glauber Costa)
- device assignment: option ROM support (Alex Williamson)
- x2apic support (Gleb Natapov)
- kvm/msi integration (Michael S. Tsirkin)
- hpet/kvm integration (Beth Kon)
- mce/kvm ingration (Huang Ying)
You can download this latest version here.
- Haydn Solomon's blog
- 4500 reads
- Email this page
Comments
Strangely qemu-0.11.0 monitor
Wednesday, September 30, 2009 - 19:46 piavlo (not verified)Strangely qemu-0.11.0 monitor does not recognize the acl command although it was compiled with sasl and tls support.
While there are acl_{show,policy,add ...} commands - they do not seem to work as expected:
(qemu) acl show vnc.username
acl show vnc.username
unknown command: 'acl'
(qemu) acl_show vnc.username
acl_show vnc.username
acl: unknown list 'vnc.username'
(qemu)
Any ideas?
Release naming
Friday, October 2, 2009 - 13:05 krwi (not verified)Could someone explain releasing name scheme? How is qemu-kvm-0.11.0 to kvm-88? Does it mean that kvm-xx branch was dropped?
> Release naming
Friday, October 2, 2009 - 14:27 Haydn Solomonqemu-kvm includes features and fixes from upstream qemu and so takes its naming scheme from upstream qemu. You can think of it as qemu optimized for kvm. Note too that qemu-kvm does not include the kernel module but only the userspace and considered to be stable.
kvm-xx on the other hand is the development branch of kvm and not considered to be stable. It's naming scheme is based on a sequential release number and it also takes features from upstream qemu.
KVM kernel stable
Monday, October 5, 2009 - 10:08 Anonymous (not verified)Hi,
Then, what is the kvm kmod "stable"? Is it that kvm-kmod 2.6.30.1 thing, mentionning kvm kernel module that is considered stable on this kernel?
>kvm kernel stable
Monday, October 5, 2009 - 11:40 Haydn Solomonkvm-kmod is different to kvm-xx. You can think of kvm-kmod as a subset of the kvm-xx. KVM-xx = userspace + kernel where kvm-kmod is the kernel part of it and qemu-kvm is the userspace part (the guest process itself). You can apply the kvm-kmod to any distro version or linux version.. it's just the kernel driver. However, without the userspace part, you can't do much with it.
And to answer you question, yes the kvm-kmod is considered stable.
Post new comment