Hey all, here are some notes on Fedora virt happenings for May.
Fedora 19 beta was released right on time this past Tuesday. If you haven't
updated yet, now's a good time!
Here's the schedule going forward:
- Jun 18: Final change deadline
- Jul 02: GA release
So by this time next month F19 should be wrapped and waiting to be shipped :)
Fedora virt test days
Also on Tuesday we ran the F19 virt test day, and just yesterday was a Spice
specific test day. If you missed the dates but still want to help out, give
the test cases a spin and reports your results as instructed on landing page:
All in all they were pretty successful: I counted 19 related bugs filed by the
end of Tuesday, and quite a few more from the Spice test day. And thankfully
nothing too major was found :)
On Monday May 20th, QEMU 1.5 was released! Highlights from the changelog:
* KVM for ARM support
* A native GTK+ UI with internationalization support
* Experimental VFIO support for VGA passthrough
* Support for VMware PVSCSI and VMXNET3 device emulation
* CPU hot-add support
See the full human-readable changelog at:
QEMU 1.5 is currently available in rawhide and virt-preview repo for F18 and
F19. For the time being we are sticking with QEMU 1.4 in Fedora 19 though.
On Thursday May 2nd, Libvirt 1.0.5 was released! Highlights from the changelog:
* add support for NVRAM device
* Add XML config for resource partitions
* Add support for TPM
* NPIV storage migration support
This is the version we will be sticking with for F19.
And yet another major release this month: libguestfs 1.22 came out on May
24th. The big changes:
* access remote disk images over nbd, ssh, http, ftp, iscsi, ceph, and more
* syslinux and extlinux bootloader support
* full support for btrfs guests
* large performance improvements in virt-df and virt-alignment-scan tools
* new bash completions for tools
Check out the full release notes here:
Bug count on Apr 29 2013 : 260
Total bugs today : 307
Quite a large jump this month, not unexpected given the test days and F19 beta
freeze holding up some ON_QA bugs from hitting stable. But we are also do for
some house cleaning.
* Fedora 17 : 75
* Fedora 18 : 128
* Fedora 19 : 83
* Fedora rawhide : 21
* bochs : 1
* gnome-boxes : 39
* gtk-vnc : 1
* ipxe : 4
* libcacard : 1
* libguestfs : 8
* libosinfo : 7
* libseccomp : 1
* libvirt : 59
* libvirt-cim : 2
* libvirt-glib : 2
* libvirt-qmf : 1
* libvirt-sandbox : 18
* netcf : 7
* qemu : 55
* seabios : 1
* spice-gtk : 4
* spice-vdagent : 2
* usbredir : 1
* vgabios : 1
* virt-dmesg : 2
* virt-manager : 36
* virt-top : 1
* virt-v2v : 5
* virt-viewer : 7
* virt-what : 2
* virtio-win : 5
* xen : 7
* xorg-x11-drv-cirrus: 5
* xorg-x11-drv-qxl : 22
Since some time i get:
[ 0.119059] [Firmware Bug]: AMD-Vi: IOAPIC not in IVRS table
[ 0.119102] [Firmware Bug]: AMD-Vi: IOAPIC not in IVRS table
[ 0.119143] [Firmware Bug]: AMD-Vi: No southbridge IOAPIC found in IVRS table
[ 0.119184] AMD-Vi: Disabling interrupt remapping due to BIOS Bug(s)
[ 1.928705] AMD-Vi: Found IOMMU at 0000:00:00.2 cap 0x40
[ 1.928923] AMD-Vi: Initialized for Passthrough Mode
Does these messages impede "Device assignment with VFIO" testing?
My mobo is a Asus Sabertooth 990FX 1.0, there is some discussion on the forum:
I tried to assign a pcie Ethernet card about a year ago (no vfio) and
the result was a lockup.
I have not tried ever since.
I have install virt-manager, libvirtd and other package on my notebook
Then I have setup a guest (Fedora 19 beta) and configure networking to
bridge via p6p1-macvtap device.
All work fine, from guest I can connect to Internet and other machine of my
network, but I do not connect to host, on which run, and from host, I can't connect to
It's possible to resolve this issue?
Dario Lesca - sip:email@example.com
(Inviato dal mio Linux Fedora18+Gnome3)
The Fedora 19 Virt Test Day is this coming Tuesday, May 28th. Check out the
test day landing page:
If you're interested in trying out some new virt functionality, there's step
by step instructions for:
* Live migrate a VM without the need for shared storage
* Virtio RNG, a paravirtual random number generator for VMs
* PCI device assignment using VFIO
Even if you aren't interested in testing new features, we still need you! The
test day is the perfect time to make sure your virt workflow is working fine
on Fedora 19, as there will be several developers on hand to answer any
questions, help with debugging, provide patches, etc. No requirement to run
through test cases on the wiki, just show up and let us know what works (or
And while it is preferred that you have a physical machine running Fedora 19,
participating in the test day does NOT require it: you can test the latest
virt bits on Fedora 17 courtesy of the virt-preview repo. For more details, as
well as easy instructions on updating to Fedora 19, see:
If you can't make the date of the test day, adding test case results to the
wiki anytime next week is fine as well. Though if you do plan on showing up
to the test day, add your name to the participant list on the wiki, and when
the day arrives, pop into #fedora-test-day on freenode and give us a shout!
On Fri, May 24, 2013 at 08:42:37AM +0530, Kashyap Chamarthy wrote:
> On 05/23/2013 05:53 PM, Richard W.M. Jones wrote:
> > I'm pleased to announce the next stable release of libguestfs (1.22).
> Great work!
> $ ./autogen.sh && make -j 7 && \
> time make -k check LIBGUESTFS_DEBUG=1 \
> LIBGUESTFS_TRACE=1 |& tee \
> is stuck at:
> PASS: test-inspect-fstab-md.sh
> 10 seconds: ./test-list-filesystems.sh
> PASS: test-list-filesystems.sh
> 14 seconds: ./test-list-md-devices.sh
> PASS: test-list-md-devices.sh
> $ uname -r
This is caused by a kernel bug which affects the 'mdadm' command:
> Now, re-trying w/: export SKIP_TEST_MDADM_SH=1
> > - full support for btrfs guests
> Side question: /me hasn't been keeping up. Do you have any info on how "use-able" (for
> some definitions of it) is 'btrfsck' ? Did you get a chance to try it at all in your
> "copious" free time :)
You'll probably want to ask Matt about it.
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
I am trying to test the VM storage in the new Gluster 3.4 Beta. I have
enabled the virt-preview repo on Fedora 18 x86_64. When I go to create
the image using 'qemu-img create gluster://f18-test1:0/vmstore/test1',
I get an error stating: qemu-img: Unknown protocol
I am guessing that the version supplied in the virt-repo does not have
the --enable-glusterfs flag supplied at compile time. Are the src
rpm's available for this repo some place so I could add the glusterfs
flag? Or can I file a bug some place to have that feature enabled?
/-\ ndrew Niemantsverdriet
Linux System Administrator
Rocky Mountain College
1511 Poly Dr.
Billings MT, 59102
Looking for some advice before I get carried away.
Can it be used in say "Fedora 18"
to build a "Fedora 17" yum cache from a file.list as an appliance
and then pull in whatever updates are availabe for "Fedora 17"
based on the *.list
Fedora has carried flow control patches for qemu chardevs since a very
long time now. They weren't upstream, and they were required for
spice, usb-redir to work properly and not freeze the guest.
Upstream qemu has now merged an alternative implementation of the same
concept, and most of the bugs have been shaken out upstream (we don't
know of any known bugs now). So I'm of the view we should replace
the older patches in F19's qemu with the backport of the newer,
Is this fine? I can work with Cole / Hans who have been keeping the
older patches uptodate on Fedora to replace the patches.