[libvirt-users] How can I setup a privileged container
by WANG Cheng D
Dear all,
I want to setup a privileged container, which means I can set the priority of a process to SCHED_RR (real-time) dynamically by calling sched_setscheduler() in a C program running on a container.
In my system (host: fedora19, container: fedora19, libvirt 1.2.5), my C code reports "operation not permitted" when sched_setscheduler() is called.
I found a link (https://www.redhat.com/archives/libvir-list/2014-June/msg00562.html) which is talking about container capability drops and keeps, but only "nice" is mentioned and I don't know how to turn on "priority" feature on a container?
Any comments are highly appreciated.
Cheng
10 years, 4 months
[libvirt-users] all windows vm could not start because the following file is missing or corrupt
by Lucas -LandM-
Hi,
After some problems in the server I can't start windows XP virtual
machines.
- Yesterday we got full disk (100%). I deleted some files. Solved.
- I update Centos 5.6. I guess libvirt was updated from 0.9 to 0.10.
We have to use this kernel: 2.6.32-042stab079.6
because this bug is not in the release:
https://bugzilla.openvz.org/show_bug.cgi?id=2915
Now, I try to start windows XP machines and all give me same error
could not start because the following file is missing or corrupt
c:\WINDOWS\SYSTEM32\CONFIG\SYSTEM
If this error were in a particular VM I try to solve it manually, but
same error in three diferent VM is not a coincidence. I suppose it is a
upgrade issue.
What should I do?
Thanks in advanced,
Lucas
10 years, 4 months
[libvirt-users] changing the priority of a process in the container is not permitted
by WANG Cheng D
Dear all,
I want to run a process in a container with a real-time (RT) priority. When the sched_setscheduler(0, SCHED_RR, &sparam) is called in the container, an error is reported which is "operation not permitted"
I had added the following line in the file /etc/security/limits.conf for both the host and the container, which means allowing all users to change the priority of the process, but it still doesn't work.
* - rtprio 100
I wonder how to change the privilege of a container so that it has the similar privilege of the root user of the host.
Thank you in advance
Cheng
10 years, 4 months
[libvirt-users] virsh update-device issues
by Oleg Bondarev
Hi,
I faced a couple of issues with libvirt update-device function:
1. http://libvirt.org/hvsupport.html says that virDomainUpdateDeviceFlags
is supported since 0.8.0 API version in qemu driver.
However when trying to update network device (changing source bridge of the
interface) on Ubuntu with 0.9.8 libvirt version I get the following error:
"*this function is not supported by the connection driver: cannot modify
network device configuration"*
What may be the reason for such error?
2. Not able to rename target device name of an interface. For example if
have running instance with interface:
* <interface type='bridge'>*
* <mac address='fa:16:3e:80:f4:49'/>*
* <source bridge='qbre1894135-13'/>*
* <target dev='vnet0'/>*
* <model type='virtio'/>*
* <alias name='net0'/>*
* <address type='pci' domain='0x0000' bus='0x00' slot='0x03'
function='0x0'/>*
* </interface>*
and then try to update:
*$ sudo virsh update-device --persistent --config --live 1 dev.xml*
where dev.xml:
* <interface type='bridge'>*
* <mac address='fa:16:3e:80:f4:49'/>*
* <source bridge='qbre1894135-13'/>*
* <target dev='tap123'/>*
* <model type='virtio'/>*
* </interface>*
I get:
* error: Failed to update device from dev.xml*
* error: Operation not supported: cannot modify network device tap name*
This happens even if rename vnet0 to tap123 manually with *ip link set
vnet0 name tap123* before interface update.
And after instance reboot tap123 is renamed back to vnet0.
Is there a strong reason to not allow modifying network device tap name?
Will appreciate any assistance with the described issues.
Thanks,
Oleg
10 years, 4 months
[libvirt-users] libvirt error
by abhishek jain
Hi
I need to run libvirt without ebtables support as it results in following
error while running VM....
sudo virsh start instance-0000000b
error: Failed to start domain instance-0000000b
error: Error while building firewall: Some rules could not be created for
interface tapf733e054-fe: Failure to execute command '$EBT -t nat -A
libvirt-J-tapf733e054-fe -j J-tapf733e054-fe-mac' : 'Unable to update the
kernel. Two possible causes:
1. Multiple ebtables programs were executing simultaneously. The ebtables
userspace tool doesn't by default support multiple ebtables programs
running
concurrently. The ebtables option --concurrent or a tool like flock can
be
used to support concurrent scripts that update the ebtables kernel
tables.
2. The kernel doesn't support a certain ebtables extension, consider
recompiling your kernel or insmod the extension.
.'.
Please help regarding this.
Thanks
Abhishek Jain
10 years, 4 months
