Another question with internal snapshots. I can see the snapshot tree with:
virsh snapshot-list Win7vm --tree
However, I would like to know from what previous snapshot I'm currently
running off. Something like the "You are here" that VMware shows. Is
there a way to find that out?
I'm trying to use virt-sysprep for the first time, and getting the
[root@ian ~]# virt-sysprep -d rdo-template
Examining the guest ...
Fatal error: exception Guestfs.Error("could not create appliance through
libvirt: Unable to read from monitor: Connection reset by peer [code=38
Digging into the qemu log, I see:
could not open disk image /var/lib/libvirt/images/rdo-template.img:
qemu-img -info says this about the file:
file format: qcow2
virtual size: 8.0G (8589934592 bytes)
disk size: 1.3G
Any ideas what's going on?
Ian Pilcher arequipeno(a)gmail.com
Sometimes there's nothing left to do but crash and burn...or die trying.
I am currently utilizing the following nested solution and seeing my VMs
hanging on OS Installation, Looks like I am hitting
L0 - Lenovo Laptop T530i -
F19 - 3.11.3-201.fc19.x86_64
1) mgr - rhevm-3.1.0-43.el6ev.noarch / RHEL 6.4 - 2.6.32-358.el6.x86_64
2) rhev-h 6.4-20130815.0.el6_4 (actual VM is using VMX and is a KVM based vm not a qemu)
I am wondering if there is any work around or others experience.
Is vfio working under Fedora 19? I'm up to date and have the virt-preview
repo installed. I had to use modprobe vfio-pci so that /dev/vfio/vifo
would show up.
This is the error that I'm getting.
error: internal error: Invalid device 0000:83:00.0 driver file
/sys/bus/pci/devices/0000:83:00.0/driver is not a symlink
I would have expected iommu_group rather than driver at the end of that.
BTW, this is not generating an error message in virt-manager like it was
prior to updating to virt-preview.
I'm using the new snapshot features of virt-manager and since these are
internal snapshots I'm wondering how to figure out how much space a
given snapshot is currently using.
Previously I used base-images+overlays and I could just check the size
of the overlay file to get an idea. If I use "qemu-img info" on my
current disks (the ones with internal snapshots) there's a "VM size"
column there but it shows 0 for offline snapshots.
Is there a way to get the actual used-space for an internal snapshot?
What version do I need to support live snapshots? I'm seeing:
virsh snapshot-create-as Test123 snapshot1 "before yum upgrade"
Compiled against library: libvirt 0.10.2
Using library: libvirt 0.10.2
Using API: QEMU 0.10.2
Running hypervisor: QEMU 0.12.1
Scott Baker - Canby Telcom
System Administrator - RHCE - 503.266.8253
The Fedora 20 Virt Test Day is this coming Tuesday, October 8th. 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:
* Snapshot UI in virt-manager
* Running ARM VMs on x86 with libvirt/virt-manager
* Libvirt ACLs for granting a user access to only a single VM
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 20, 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 to be clear, while it is preferred that you have a physical machine
running Fedora 20, participating in the test day does NOT require it: you can
test the latest virt bits on the latest Fedora release courtesy of the
virt-preview repo. For more details, as well as easy instructions on updating
to Fedora 20, 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!
Hey all, here are some notes and about Fedora and virt happenings for September.
After an additional week delay, the Fedora 20 alpha was released on
get it: http://fedoraproject.org/get-prerelease
common bugs: https://fedoraproject.org/wiki/Common_F20_bugs
I upgraded with yum and there were very few hiccups. Another solid alpha :)
The remaining F20 schedule:
Oct 08: Virt Test Day
Oct 15: Beta deadline
Oct 29: Beta release
Dec 03: GA release
Fedora 20 virt test day
The virt test day is next Tuesday, October 8th! The landing page is at:
If you can spare some time, please consider helping out. We will have
an F20 live cd you can use to test inside a virtual machine on F19,
no need to update. I'll send out a more elaborate pitch later this week.
Libvirt 1.1.2 was released on September 2nd. Highlights:
- various improvements to libxl driver (Jim Fehlig, Bamvor Jian Zhang),
- systemd integration improvements (Daniel P. Berrange, Mooli Tayer),
- Add flag to BaselineCPU API to return detailed CPU features (Don Dugger),
- Introduce a virt-login-shell binary (Dan Walsh),
- conf: add startupPolicy attribute for harddisk (Guannan Ren)
Total bugs on Sep 2nd : 211
Total bugs on Oct 3rd : 223
F20 bugs are coming in fast and furious now, but quite a few are fixed
in updates-testing or waiting in POST for a build, so not much change
from last month.
* Fedora 18 : 60
* Fedora 19 : 114
* Fedora 20 : 32
* Fedora rawhide : 17
* edk2 : 2
* gnome-boxes : 33
* ipxe : 3
* libguestfs : 7
* libosinfo : 7
* libseccomp : 1
* libvirt : 42
* libvirt-sandbox : 21
* netcf : 7
* qemu : 37
* seabios : 1
* spice-gtk : 1
* usbredir : 1
* virt-dmesg : 1
* virt-manager : 17
* virt-viewer : 9
* virt-what : 2
* virtio-win : 5
* xen : 9
* xorg-x11-drv-cirrus: 2
* xorg-x11-drv-qxl : 15
* ASSIGNED : 21
* NEW : 172
* ON_QA : 18
* POST : 12
Bugs of note
Common spice crash on F20
Already seen quite a few duplicates of this crash, but a build was
done today and his heading for updates-testing.