qemu 2.0.0 has been released! It's built for rawhide now, should show up in
I haven't enabled a qemu-system-aarch64 sub package yet: as the announcement
says, it only works on aarch64 hosts which fedora is still in the process of
supporting. My guess is that next qemu release will have something useable for
aarch64 CPU emulation which will allow use of qemu-system-aarch64 on x86,
which is what most people are looking for at the moment.
-------- Original Message --------
On behalf of the QEMU Team, I'd like to announce the availability of
the QEMU 2.0.0 release. This is one of our most extensive releases ever, with
2,500+ commmits from 179 authors.
The full list of changes are available at:
* Initial support for KVM on AArch64 systems (some features such as migration
are not yet implemented)
* Support for all 64-bit mode ARMV8 user-accessible instructions except for
the optional CRC and crypto extensions
* Support for new 32-bit mode ARMv8 instructions in TCG
* Support for the allwinner-a10-based board "-M cubieboard"
* Support for POWER Altivec 2.07 and VSX instructions when running under TCG
* Support for boot order in pSeries emulation
* The Q35 x86 machine-type now supports CPU hotplug.
* On the PIIX x86 machine-type, PCI hotplug now supports devices behind a
bridge (for bridges not added by hotplug; hot-plugged bridges can still use
the PCI Standard Hot-Plug Controller)
* Support for the Hyper-V reference time counter via the "hv-time" suboption
of "-cpu". This can improve performance of Windows guests substantially for
applications that do many floating-point or SIMD operations. (Requires KVM
and Linux 3.14).
* ACPI tables generated by QEMU can now be used by OVMF
(https://wiki.ubuntu.com/UEFI/OVMF) firmware. OVMF starting with SVN r15420
is needed. In particular hotplug, pvpanic device and other ACPI based
features now work for OVMF
* PCI passthrough of devices with a ROM now work on Xen
* support for suspend-to-RAM in the XHCI USB controller
* GTK UI is now supported on Windows hosts
* New management interfaces for CPU and virtio-rng hotplug
* Improved reliability for live migration when using qcow2 images
* Live snapshot merging
* Experimental support in virtio-blk for M:N threading model: if you specify
x-dataplane=on, you can also create I/O threads with "-object iothread" and
point virtio-blk devices to the desired iothread with the "x-iothread"
property. Properties of the running iothreads can be queried with the QMP
* Network block drivers (curl, iscsi, rbd, ssh, glusterfs) can be built as
shared library modules with "--enable-modules" configure option.
* QEMU is now able to operate even if the underlying storage requires the
buffer size to be a 4K multiple. This is the case for 4K-native disks (with
cache=none or when accessed through iscsi:// URLs) and some raw devices
* QEMU can access NFSv3 shares directly from userspace using libnfs.
* Improvements to the TCG optimizer make it produce faster code
* Tracing QEMU via LTTng 2.x is now supported
* And lots more...
Thank you to everyone involved!
I've made virtual guest on Fedora 20 (x86_64) within qcow2 image file
but after migration to CentOS 6.5 I've got this error:
qemu-kvm: -drive file=/var/lib/libvirt/images/questfile.qcow2,if=none,id=drive-virtio-disk0,format=qcow2: 'drive-virtio-disk0' uses a qcow2 feature which is not supported by this qemu version: QCOW version 3
similar error I've got for qemu-img:
# qemu-img info /var/lib/libvirt/images/questfile.qcow2
'image' uses a qcow2 feature which is not supported by this qemu version: QCOW version 3
On F20 it returns:
# qemu-img info /var/lib/libvirt/images/questfile.qcow2
file format: qcow2
virtual size: 32G (34359738368 bytes)
disk size: 4.7G
Have I missed something?
Is it qcow2 on Fedora different from CentOS6? Is there any possibility
(on Fedora 20) to convert it to backward compatible format?
Pavel Lisý <pavel(a)element.cx>
Hey all, here are some virt and fedora status bits for March.
The Fedora 21 schedule was finalized last month.
- 2014-04-08 Change Proposal Submission Deadline
- 2014-07-08 Changes Freeze--Planning & Development Ends
- 2014-07-22 Alpha Change Deadline
- 2014-08-05 Alpha Release
- 2014-08-26 Beta Change Deadline
- 2014-09-09 Beta Release
- 2014-09-30 Final Change Deadline
- 2014-10-14 Fedora 21 Final Release
There's quite a large window between the change submission deadline (next
week) and the alpha freeze, 3 months total. I've proposed one change:
That's basically about qemu-system-aarch64 being usable. This is under
heavy development in upstream qemu, but there's a good chance that
something will be useful in time for Fedora 21, and that page is about
tracking the progress, getting it documented, wired up in libvirt, etc.
libvirt 1.2.2 was released on March 2nd. New features include:
- bhyve: add a basic driver (Roman Bogorodskiy)
- add LXC from native conversion tool (Cédric Bosdonnat)
- vbox: add support for v4.2.20+ and v4.3.4+ (Jean-Baptiste Rouault)
- Introduce Libvirt Wireshark dissector (Yuto KAWAMURA)
virt-manager-1.0.1 was releaed on March 22nd. Highlights:
- virt-install/virt-xml: New --memorybacking option (Chen Hanxiao)
- virt-install/virt-xml: New --memtune option (Chen Hanxiao)
- virt-manager: UI for LXC <idmap> (Chen Hanxiao)
- virt-manager: gsettings key to disable keygrab (Kjö Hansi Glaz)
- virt-manager: Show domain state reason in the UI (Giuseppe Scrivano)
- Fix a number of bugs found since the 1.0.0 release
Total bugs on 2014-03-03 : 176
Total bugs on 2014-04-01 : 163
* Fedora 19 : 65
* Fedora 20 : 86
* Fedora rawhide : 12
* edk2 : 1
* gtk-vnc : 1
* kvm : 1
* libguestfs : 7
* libosinfo : 1
* libseccomp : 1
* libvirt : 49
* libvirt-sandbox : 10
* netcf : 6
* qemu : 30
* seabios : 1
* spice : 13
* spice-gtk : 5
* spice-vdagent : 1
* usbredir : 1
* virt-manager : 5
* virt-viewer : 8
* virtio-win : 2
* xen : 9
* xorg-x11-drv-qxl : 11
* ASSIGNED : 8
* NEW : 145
* ON_QA : 2
* POST : 8