Libvirt errors with nested backeds QCOW2 images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
virt-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This is due by an error with Apparmor profile created for the new machine. Simple get a working qcow2 image like:
- Windows7-Base.img
Do a new qcow2 image using this as backing:
- qemu-img create -f qcow2 -b Windows7-Base.qcow2 Windows7-
Now just do some things on it like running updates and then do a new image like:
- qemu-img create -f qcow2 -b Windows7-
Now try to run a MV using Final.qcow2 and you will get an error:
- backing file: Could not open '/var/lib/
The problem is the Apparmor profile inside /etc/apparmor.
HACK:
Just add to a new device with Windows7-Base.img as "read-only" and libvirt will generate properly apparmor access to it.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: virt-manager 0.9.5-1ubuntu3
ProcVersionSign
Uname: Linux 3.13.0-40-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Nov 29 10:11:28 2014
ExecutablePath: /usr/share/
InstallationDate: Installed on 2014-10-12 (47 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcEnviron:
LANGUAGE=es
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_ES.UTF-8
SHELL=/bin/bash
SourcePackage: virt-manager
UpgradeStatus: No upgrade log present (probably fresh install)
Status changed to 'Confirmed' because the bug affects multiple users.