similar to: libvirt 1.19: could not open drive file (permission denied)

@requillart Don't get me wrong. It's no problem to use other partitions. Only, you have to add the location to the storage pool of libvirt... Sorry, no experience with gnome-boxes. @crequill Add a new storage pool with the destination /home/crequill/VM You can't fool apparmour with a link... Also with adding the storage pool, it's easier to get a clear picture of the usage of your

Indeed, I have a link between /var/lib/libvirt/images and my home directory on an another partition. # ls -al /var/lib/libvirt/images lrwxrwxrwx 1 root root 17 3 sept. 09:29 /var/lib/libvirt/images -> /home/crequill/VM 2015-09-15 17:45 GMT+02:00 Dominique Ramaekers <dominique.ramaekers@cometal.be>: > A while ago, I had the same problem. It was a apparmor issue. Maybe your image is

For gnome boxes, a pool already exists: $ virsh pool-list Name State Autostart -------------------------------------------------- default active yes gnome-boxes active no $ virsh vol-list gnome-boxes Name Path ------------------------------------------------------------------------------ win7

If we cannot use anymore another partitions, for me it's a bug. Not for you? For information, I get this error with gnome boxes. With it, images are in /home/crequill/.local/share/gnome-boxes/images/. How run it? 2015-09-15 17:53 GMT+02:00 crequill <crequill@worldonline.fr>: > Indeed, I have a link between /var/lib/libvirt/images and my home > directory on an another partition.

A while ago, I had the same problem. It was a apparmor issue. Maybe your image is on a location outside your storage pools? -----Oorspronkelijk bericht----- Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] Namens crequill Verzonden: dinsdag 15 september 2015 17:29 Aan: libvirt-users@redhat.com Onderwerp: [libvirt-users] libvirt 1.19: could not open drive file

This is not a libvirt/redhat question… With your method you can only revert to versions which are available in the standard repositories. You’ll have to download the packages manually to force a different version. Use with caution. There is a reason why the version isn’t in the standard repositories. Van: libvirt-users-bounces@redhat.com [mailto:libvirt-users-bounces@redhat.com] Namens Keyur

Hi, I have tried usb and it doesn’t work. I don’t know if the filesystem tag could work… I find in the formatdomain docs about the filesystem: <filesystem type='mount' accessmode='passthrough'> <driver type='path' wrpolicy='immediate'/> <source dir='/export/to/guest'/> <target

Yes, my modification is like you. I doubt that if the mount operation on the host is reasonable… And what is p9? Best Regards From Jiaping LI 发件人: Dominique Ramaekers [mailto:dominique.ramaekers@cometal.be] 发送时间: 2015年11月9日 15:08 收件人: 李笳平; 'libvirt-users@redhat.com' 主题: RE: [libvirt-users] How could I do the guest mount operation from the host? For usb I meant something like: <disk

Hi, Thanks for your response! But when I use the ssh, I need to know the guest password, and actually it belongs to network communication. I don’t know if the libvirt has some means just like to control the domain to implement the operation? Best Regards From Jiaping LI 发件人: Dominique Ramaekers [mailto:dominique.ramaekers@cometal.be] 发送时间: 2015年11月6日 15:41 收件人: 李笳平;

Hi there! I have installed a new VM with Win2k8 and the serial virtio driver works fine. I don´t know why the other VM the BSOD happen! About the performance, I had the impression that only one core is used.....PID 8301 is a linux VM with 4 VCPU and 2 GB of RAM... ​ 2016-05-25 3:39 GMT-03:00 Dominique Ramaekers < dominique.ramaekers@cometal.be>: > > > *Van:* Thiago

Hi there! Although the guest has 2GB memory, the windows guest was adjusted to support this. I guess that the LVM is the best choice! I will save all images to other disk and re-build the partition with LVM. Do you recomend to use ext4 or zfs ? - About the apparmor, I have my doubts, I will try to disable and see what will happen! - About the tablet input device, I removed! Some forums say that

Hi there! I will do soon the disk config, but first I will do some labs. I´m trying to install the virtio driver to comunicate using qemu-agent but when the driver is installed, the BSOD happens (win2k8 R2). I tried with virtio-drivers version 100, 110 and 117, both happens BSOD. Do you has a tip ? :) Thanks buddy! 2016-05-20 10:23 GMT-03:00 Dominique Ramaekers <

Hi Dominique, You’ll have to convert the qcow to raw, create a LVM-volume (don’t create a file system on the volume), and dd the raw tot he LVM volume… Convert the qcow to raw, Ok Create a LVM-Volume, OK Don´t create a file system on the volume ?? Is not clear why... DD the raw to the LVM? How ? I don´t understand this point.... Thanks a lot! 2016-05-20 10:23 GMT-03:00 Dominique

Yeah, Dominique, your wiki was one of the many docs I read through before/during/after starting down this primrose path... thanks for writing it. I'm an Arch user, and I couldn't find anything to indicate qemu, as its compiled for Arch, will look in /etc/default/qemu-kvm. And now that I've got the right page size, the instances are starting... The reason I want to use the page element

Hi, i'd like to create snapshots of my running vm's. I have several hosts with SLES11 SP4 64bit. I use libvirt 1.2.5-7.1 . VM's are Windows 7, SLES, Ubuntu, Opensuse. I use raw files for the vm's. I try to orientate myself by http://wiki.libvirt.org/page/Live-disk-backup-with-active-blockcommit . The hosts are backuped every night by a network based backup solution (Legato). My

On 4/14/2015 4:58 PM, Daniel P. Berrange wrote: > On Tue, Apr 14, 2015 at 04:53:52PM +0530, Jatin Davey wrote: >> On 4/14/2015 4:42 PM, Dominique Ramaekers wrote: >>> About Spice: I think it’s good practice to use spice because it improves >>> the performance of the VM in general by improving screen performance. If >>> your VM is constantly displaying output,

Hi there! Sure......see below. # virsh version Compiled against library: libvirt 1.3.1 Using library: libvirt 1.3.1 Using API: QEMU 1.3.1 Running hypervisor: QEMU 2.5.0 # uname -a Linux 4.4.0-22-generic #40-Ubuntu 16 <domain type='kvm' id='8'> <name>W2k8</name> <uuid>a148a0b7-eefb-9a5b-8e83-8efaf19f9899</uuid>

Hi all, When I attach a disk like this: <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/kvmdata/disk/dk389_581.img'/> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/>

Thanks Dominique & Daniel. Looks like i need to upgrade my VMs kernel to make it aware of virtio. Found this information from this link: http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver I tried without upgrading the Kernel and as soon as i start my VM it got into Kernel Panic. I will try using virtio after upgrading my VMs kernel. Thanks for all the responses and

Hello All, I think I have seen this in previous bugs. Trying to live backup qcow2 images. I am able to virsh snapshot-create-as and virsh domblklist shows correct new source, but I am unable to commit back changes to qcow base. I get the above error. Libvirt at 1.2.2-0ubuntu13.1.17 Qemu is (2.0.0+dfsg-2ubuntu1.22) I tried compiling latest libvirt, but cannot get it to connect to socket on