[PATCH 0/4] RFC: grant KVM guest rawio capability

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 
This patch is as a result of the following dispute:
 
  http://www.redhat.com/archives/libvir-list/2011-December/msg00857.html
  http://www.redhat.com/archives/libvir-list/2011-December/msg00950.html
  http://www.redhat.com/archives/libvir-list/2012-January/msg00449.html
  
 This patchset achieves #1 and #2 of the following tasks:
  
> 1. rawio="yes|nmo"  on the <disk> element somewhere
> 2. Give the QEMU process CAP_SYS_RAWIO
> 3. Use the devices cgroup to specify which individual disks
> can use rawio.

 In short, if you specify the following XML:
 
   <disk type='block' device='lun' rawio='yes'>
   
 the domain will be granted CAP_SYS_RAWIO.
 
 # virsh start VM
 # cat /proc/<VM's PID>/status
...
CapInh: 0000000000000000
CapPrm: fffffffc00020000
CapEff: fffffffc00020000
CapBnd: fffffffc00020000
...
 
  *[PATCH 1/4] conf: add rawio attribute to disk element of domain XML
  *[PATCH 2/4] util: add functions to keep capabilities
  *[PATCH 3/4] util: extend virExecWithHook()
  *[PATCH 4/4] qemu: make qemu processes to retain capabilities

-
Best regards,
Taku Izumi

-- 
Taku Izumi <izumi.taku@xxxxxxxxxxxxxx>

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list


[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]