similar to: dynamic_ownership behavior with volumes

On 09/20/2018 12:31 PM, Milan Zamazal wrote: > Michal Prívozník <mprivozn@redhat.com> writes: > >> On 09/19/2018 12:39 PM, Milan Zamazal wrote: >>> Hi, I'm playing with dynamic ownership and not all objects have their >>> owners changed. >> >>> >>> Is dynamic_ownership and its scope documented somewhere, besides the >>>

Hi, I'm playing with dynamic ownership and not all objects have their owners changed. Is dynamic_ownership and its scope documented somewhere, besides the comment in qemu.conf? And what kinds of objects are handled by dynamic ownership? While some objects seem to be handled, other objects are apparently unaffected. For instance /dev/hwrng or a USB host device keep their root owners and are

On 09/19/2018 12:39 PM, Milan Zamazal wrote: > Hi, I'm playing with dynamic ownership and not all objects have their > owners changed. > > Is dynamic_ownership and its scope documented somewhere, besides the > comment in qemu.conf? > > And what kinds of objects are handled by dynamic ownership? While some > objects seem to be handled, other objects are apparently

Michal Prívozník <mprivozn@redhat.com> writes: > On 09/19/2018 12:39 PM, Milan Zamazal wrote: >> Hi, I'm playing with dynamic ownership and not all objects have their >> owners changed. > >> >> Is dynamic_ownership and its scope documented somewhere, besides the >> comment in qemu.conf? >> >> And what kinds of objects are handled by

Hi Everyone: I am trying to create a volume using the vol-create-as command but it fails with an "Operation not permitted" error. It appears to be caused by an attempt to run chown on an NFS mounted file system but I have set dynamic_ownership to 0 in /etc/qemu.conf. Is it possible to disable the chown operation? If not, is there a guide that describes how to create storage

Hi, I am getting following 'qemu: could not load kernel' error while trying to create a new VM using virt-install or virt-manager. The software versions are as follows: CentOS 6.2, Libvirt 0.9.4, qemu-kvm 2:0.12.1.2-2.209.el6_2.1. The qemu.conf has disabled dynamic_ownership setting. The VM instantiation has worked fine before when dynamic_ownership was enabled (default). So is this

On Fri, Mar 20, 2020 at 03:38:36PM +0000, Joe Muro wrote: >Hi, > Hi, could you please configure your client to send plaintext version as well? We mainly prefer plaintext on this list ;-) >I am trying to understand libvirt dynamic ownership behavior. I have a VM that >uses a qcow2 image with the following permissions: > >$ ll t257kvxg-10-20-101-40.qcow2 >-rw-r--r-- 1 jmuro

On Fri, May 31, 2013 at 04:03:32PM +0800, Qiu Yu wrote: > Actually I'm looking into an issue with OpenStack / Libvirt manipulating > LVM as an image backend. When the logical volume is created, udev rules > will set the ownership to root:disk. After libvirt actually starting an > instance, device node ownership will change to qemu:qemu by libvirt. Then, > if you stop an

On Wed, Oct 03, 2018 at 01:04:50PM -0300, Rodrigo Siqueira wrote: >Hi, > >My colleagues and I have a set of scripts that we use to automate our >daily tasks related to the Linux Kernel. As a result, most of our code >relies on the QEMU features; and recently we decided use libvirt instead >of QEMU. However, we have some questions, and I would like to know if >someone could

Hi Martin, thanks for the explanation. Now I understand why libvirt doesn't revert the file permissions back to the original. I am running these VMs on an isolated test machine, so I'll disable dynamic file ownership and make sure libvirt has access to image files. Sorry about the message formatting. I modified settings on my client, hopefully it sends plaintext now. (I'll switch to

"Michal Prívozník" <mprivozn@redhat.com> wrote on 03/23/2020 12:26:14 PM: > From: "Michal Prívozník" <mprivozn@redhat.com> > To: Martin Kletzander <mkletzan@redhat.com>, Joe Muro <joemuro@us.ibm.com> > Cc: libvirt-users@redhat.com > Date: 03/23/2020 12:26 PM > Subject: [EXTERNAL] Re: libvirt dynamic file ownership > > On 20. 3. 2020

Hello, I'm having an issue with usage of libvirt driven qemu where I'm sharing directory with guest machine. virsh domain filesharing configuration: <filesystem type='mount' accessmode='passthrough'> <driver type='path' wrpolicy='immediate'/> <source dir='/media/share'/> <target dir='data'/>

On 20. 3. 2020 20:57, Martin Kletzander wrote: > On Fri, Mar 20, 2020 at 03:38:36PM +0000, Joe Muro wrote: >> Hi, >> > > Hi, could you please configure your client to send plaintext version as > well? > We mainly prefer plaintext on this list ;-) > >> I am trying to understand libvirt dynamic ownership behavior. I have a >> VM that >> uses a qcow2

<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10pt" ><div dir="ltr" >&nbsp;</div> <div dir="ltr" ><div dir="ltr" >Hi,</div> <div dir="ltr" >&nbsp;</div> <div dir="ltr" >I am trying to understand libvirt

Hi, I have a very strange problem with libvirt. I work on some machines with libvirt (Debian/ Arch Linux) and libvirt set the ownership of images file automatically to the qemu user / group for example on Arch Linux to nobody:kvm. So when I copy an image file with root and use I then with qemu, libvirt change the owner/ group to nobody:kvm. But I also compiled libvirt for a machine (gcc 4.9.4

Hi, First of all, thanks for your feedback :) On 10/17, Martin Kletzander wrote: > On Wed, Oct 03, 2018 at 01:04:50PM -0300, Rodrigo Siqueira wrote: > > Hi, > > > > My colleagues and I have a set of scripts that we use to automate our > > daily tasks related to the Linux Kernel. As a result, most of our code > > relies on the QEMU features; and recently we

Hi, My colleagues and I have a set of scripts that we use to automate our daily tasks related to the Linux Kernel. As a result, most of our code relies on the QEMU features; and recently we decided use libvirt instead of QEMU. However, we have some questions, and I would like to know if someone could help us. Follows: 1) Import our QEMU images with virsh Currently, we import the QEMU VMs with

Hi! I'm oVirt developer responsible for most of 'hostdev' support. While working on SCSI passthrough (that is hostdev type='scsi'), I've encountered few issues I'm not sure how to solve somewhat effectively and nicely. Just a note - oVirt by default disables 'dynamic_ownership', meaning we have to handle endpoint ownership/labeling ourselves. This is not

Hi all: I am using the libvirt version that comes with Ubuntu 18.04.3 LTS. I want to backup a virtual machine in a foolproof way: - Gracefully shutdown the VM. - Backup the disk image. - Restart the VM. I wrote the following script to do that: https://github.com/rdiez/Tools/blob/master/VirtualMachineManager/BackupVm.sh Writing that script was difficult enough because of the virsh limitations

On Fri, May 31, 2013 at 4:17 PM, Richard W.M. Jones <rjones@redhat.com>wrote: > On Fri, May 31, 2013 at 04:03:32PM +0800, Qiu Yu wrote: > > Actually I'm looking into an issue with OpenStack / Libvirt manipulating > > LVM as an image backend. When the logical volume is created, udev rules > > will set the ownership to root:disk. After libvirt actually starting an