- Users - libvirt List Archives

[libvirt-users] monitiring cpu usage via cgroup
by Zvi Dubitzky 16 Feb '11

16 Feb '11

thanks Kame, 1) the policy of my process(test) is indeed SCHED_NORMAL . When I use sched_setscheduler() to set the pid sched policy to SCHED_FIFO then the cpu usage via cgroup rt_runtime_us and rt_period_us is affected . Still the ratio I specified is 1:10 but I see via top that my process ,that gets 1 cpu ,shows 20% usage 2) What about memory and cpuset subsystems of cgroup. Do their settings apply also only in the cases of processes with policy = SCHED_FIFO/SCHED_RR ? 3) lastly: What is the meaning of the ‘cap’ parameter in the schedinfo virsh command (what are the units and range of values ) and what is the ‘weigth’ parameter .I did not find any documentation of libvirt about it ? thanks Zvi Dubitzky Email:dubi@il.ibm.com

1 0

[libvirt-users] monitiring cpu usage via cgroup
by Zvi Dubitzky 15 Feb '11

15 Feb '11

Hi I was asking about the fedora 14 kernel if it is good enough for cgroup usage because I am trying to set a cgroup under cpu subsytem ( /dev/cgroup/cpu/group1/ ) that have /cpu.rt_runtime_us of 100000 while cpu.rt_period_us has a value of 1000000 i.e a ratio of 1/10 . still when I run a task (endless loop) in that group (cgexec -g cpu,cpuset:group1 ./test) it gets all the cpu core time that is assigned to it ( i watch via top utility) , so it seems that the quota set via the group does not take effect although I restart the cgconfig service . I also verified libcgroup is installed by: rpm -q libcgroup Am I missing something or top is not the right utility to watch the cpu usage in this case ? thanks Zvi Dubitzky Email:dubi@il.ibm.com

2 1

[libvirt-users] Xen disk device detach fails as non-root [libvirt-0.8.7 and older versions]
by Iain MacDonnell 15 Feb '11

15 Feb '11

Hi All, I find that I am able to attach a disk device do a Xen domain, using virDomainAttachDevice(), running as a non-root user, but I am unable to use virDomainDetachDevice() - it results in an "unknown failure". Using "virsh [attach|detach]-device" exhibits this behviour. $ virsh attach-device domu1 attach.xml Device attached successfully $ virsh detach-device domu1 attach.xml error: Failed to detach device from attach.xml error: Unknown failure $ With some digging, I determined that the problem arises when libvirt tries to translate the device name to a number, using the XenStore API (xenStoreDomainGetDiskID()), which requires use of the "xenstored" UNIX socket, and that socket is only accessible by root. On making that socket accessible to the user (by group), virDomainAttachDevice() starts working, but I'm then unable to list domains, because xenStoreDoListDomains() waits to verify each domain using xenHypervisorHasDomain(), and that requires access to another socket - "/proc/xen/privcmd" My question, before going down the path of trying to hack permissions for these sockets permanently ..... is this how it's supposed to be, or could, perhaps, libvirtd, which runs as root, access these sockets on behalf of the user? It seems it should at least fail more gracefully.... TIA for any pointers.... ~iain

2 1

[libvirt-users] connecting to virtualbox with libvirt
by Gary Scarborough 14 Feb '11

14 Feb '11

I am trying to connect to the virtualbox hypervisor through libvirt. If I am doing it correctly, virsh -c vbox:///session should get me connected. I am on F14 64 bit. I tried this with both vbox 3.2 and 4.02. I keep getting the following error: error: no connection driver available for vbox:///session. What am I missing? Thanks, Gary

2 1

[libvirt-users] Linux version that supports cgroup
by Zvi Dubitzky 14 Feb '11

14 Feb '11

Hi Does Fedora release 14 (Laughlin) having Linux kernel 2.6.35.6-45.fc14.x86_64 support cgroup at the kernel ? thanks Zvi Dubitzky Email:dubi@il.ibm.com

2 1

[libvirt-users] cgroup
by Zvi Dubitzky 14 Feb '11

14 Feb '11

Hi Should libvirtd be in a cgroup hierarchy rooted at /dev/cgroup or it can be rooted also at /cgroup i,e can /etc/cgconfig.conf look like his (without the /dev) : mount { cpuset = /cgroup/cpuset; cpu = /cgroup/cpu; cpuacct = /cgroup/cpuacct; memory = /cgroup/memory; devices = /cgroup/devices; freezer = /cgroup/freezer; net_cls = /cgroup/net_cls; ns = /cgroup/ns; blkio = /cgroup/blkio; } thanks Zvi Dubitzky Email:dubi@il.ibm.com

2 1

[libvirt-users] Using NFS to read image file
by Marcela Castro León 12 Feb '11

12 Feb '11

Hello: When I start the guest with an image on NFS file system, the ubuntu doesn't boot, It's remain on inittrams. I've tried to redefine the guest without <apic> <pae> configuration as I see on a blog, and I've increased the parameters of the mount to rsize=32768 and wsize=32768, but it still doesn't work. Can anyone give any advice to get it? Thank you very much. Marcela

2 2

[libvirt-users] LXC libvirt support
by Nirmal Guhan 12 Feb '11

12 Feb '11

Hi, Has anyone used libvirt to start/stop/manage LXC (linux containers) ? Is it supported at all? Last I tried, had few issues and the reply was : /// Note that libvirt lxc driver is a different implementation from lxc tools and doesn't use lxc tools internally. You may not be able to do what you are doing with lxc tools. Especially, the driver doesn't take aware of files and settings inside a container at all. You have to prepare them by yourself in advance /// Is it still the case? ~nirmal

2 1

[libvirt-users] Start domain with usable QMP connection?
by Bryan D. Payne 12 Feb '11

12 Feb '11

Is there any way to get virsh / libvirt to create a domain such that I can later connect to it via QMP (without hacking the code)? The command line that libvirt creates for my current setup looks like this: /usr/local/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name winxpsp2 -uuid ab244939-c804-1aff-68b6-9324f174c3c8 -nodefconfig -nodefaults -chardev socket,id=monitor,path=/usr/local/var/lib/libvirt/qemu/winxpsp2.monitor,server,nowait -mon chardev=monitor,mode=control -rtc base=localtime -boot c -drive file=/var/lib/libvirt/images/winxpsp2.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/home/username/iso/en_winxp_pro_with_sp2.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=16,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:4d:1d:1b,bus=pci.0,addr=0x3 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga std -device ES1370,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 The important pieces of this command line (I believe) are: -chardev socket,id=monitor,path=/usr/local/var/lib/libvirt/qemu/winxpsp2.monitor,server,nowait -mon chardev=monitor,mode=control However, I'm unable to connect using this path because -- I'm guessing -- libvirt has already connected. As a test, I added some code to src/qemu/qemu_command.c to open a second chardev. My new command line looks like this: /usr/local/bin/qemu-system-x86_64 -S -M pc-0.12 -enable-kvm -m 512 -smp 1,sockets=1,cores=1,threads=1 -name winxpsp2 -uuid ab244939-c804-1aff-68b6-9324f174c3c8 -nodefconfig -nodefaults -chardev socket,id=monitor,path=/usr/local/var/lib/libvirt/qemu/winxpsp2.monitor,server,nowait -mon chardev=monitor,mode=control -chardev socket,id=qmpmonitor,path=/usr/local/var/lib/libvirt/qemu/winxpsp2.qmpmonitor,server,nowait -mon chardev=qmpmonitor,mode=control -rtc base=localtime -boot c -drive file=/var/lib/libvirt/images/winxpsp2.img,if=none,id=drive-ide0-0-0,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -drive file=/home/username/iso/en_winxp_pro_with_sp2.iso,if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw -device ide-drive,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -netdev tap,fd=15,id=hostnet0 -device rtl8139,netdev=hostnet0,id=net0,mac=52:54:00:4d:1d:1b,bus=pci.0,addr=0x3 -chardev pty,id=serial0 -device isa-serial,chardev=serial0 -usb -device usb-tablet,id=input0 -vnc 127.0.0.1:0 -k en-us -vga std -device ES1370,id=sound0,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 Notice that there are now two chardevs: -chardev socket,id=monitor,path=/usr/local/var/lib/libvirt/qemu/winxpsp2.monitor,server,nowait -mon chardev=monitor,mode=control -chardev socket,id=qmpmonitor,path=/usr/local/var/lib/libvirt/qemu/winxpsp2.qmpmonitor,server,nowait -mon chardev=qmpmonitor,mode=control As expected, I am able to connect to this second chardev via QMP. Is there anyway that I can enable such functionality in libvirt without hacking the code? Thanks, bryan

2 3

[libvirt-users] Not able to capture detailed CPU information of the guest machine using Libvirt API.
by arpita k 12 Feb '11

12 Feb '11

Hi , I have two KVM guests in ubuntu host machine.I am using Python binding of Libvirt API to query on the hypervisor and capture the CPU , memory related information of the guest machines. I need to capture the detail information regarding CPU like : cpu_aidle, cpu_idle, cpu_speed, cpu_wio and memory like :mem_cached,mem_buffers,mem_free etc. of the guest machines. How could I get these information? Please help me. Thanks in Advance!! Arpita

3 2