- Users - libvirt List Archives

[libvirt-users] libvirt-snmp on Ubuntu
by george john 07 May '13

07 May '13

Hi, Are there packages of "libvirt-snmp" for Ubuntu? Or instructions to compile libvirt-snmp on Ubuntu? Looks like the instructions given at http://wiki.libvirt.org/page/Libvirt-snmp are for RedHat. Thank you, George

3 4

[libvirt-users] libvirt API reference disappeared from website
by Ulrich Hochholdinger 07 May '13

07 May '13

Hi, I think the API Reference for libvirt disappeared from libvirt.org: browsing to http://libvirt.org/html/libvirt-libvirt.html delivers no content. The content is still available via google cache http://webcache.googleusercontent.com/search?q=cache:libvirt.org/html/libvi… So, is this removed on purpose? Or is this some bluff from my browser (but I checked this from different sites with different browsers ;-/ )? Cheers, Ulli -- Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. (calvin)

3 2

[libvirt-users] hyperv connection failing with libvirt 1.0.4 virsh.
by D e e p a k 07 May '13

07 May '13

Trying to use virsh for hyperv and getting this. virsh # connect hyperv://172.168.1.111:5985/?transport=http Enter username for 172.168.1.111 [administrator]: administrator Enter administrator's password for 172.168.1.111: 2013-04-29 10:36:48.690+0000: 13991: error : hypervDebugHandler:1444 : openwsman error: NULL response error: Failed to connect to the hypervisor error: internal error Transport error during enumeration: User, password or similar was not accepted (26) Using libvirt 1.0.4 from source code. What is going wrong in this hyperv connection ? Regards, Deepak

2 6

[libvirt-users] Location of 64 bit libvirt dlls (Windows)?
by george john 06 May '13

06 May '13

I have written a Java client (64 bit JVM) that uses libvirt APIs on a remote KVM for KVM management. Since the JVM is 64 bit, the client needs 64 bit libvirt dlls and I could not find them (I found 32 bit libvirt dlls on http://libvirt.org/windows.html) Could someone point to where I could find 64 bit libvirt dlls? Thank you, George

2 2

[libvirt-users] virtlockd, init script and kill signals
by Franky Van Liedekerke 06 May '13

06 May '13

Hi, I've read in the documentation that virtlockd uses SIGUSR1 to dump its state and then re-execs itself. Now I tried it and this seems to fail because virtlockd is being launched without a full path (when using the init script), thus re-exec fails with the error: error : virLockDaemonPreExecRestart:1092 : Unable to restart self: No such file or directory Changing in the init script the PROCESS variable to PROCESS=/usr/sbin/virtlockd fixes this. Also, concerning the init script: - HUP seems to crash the daemon, so maybe it's better to be replaced by SIGUSR1 or removed - path to process pid file (variable PIDFILE) needed to be changed to /var/run/$SERVICE.pid - the path to the config file needed to be changed (/etc/sysconfig/virtlockd) to contain VIRTLOCKD_ARGS="-f /etc/libvirt/qemu-lockd.conf" Hope this helps someone :-) Franky

1 1

[libvirt-users] Requested operation is not valid: domain is not running but exactly vm is running
by yue 05 May '13

05 May '13

hi,all requested operation is not valid: domain is not running but exactly vm is running when call getCPUStats,interfaceStats... system: centos6.3 libvirt-0.9.10-21.el6_3.7.x86_64 libvirt-python-0.9.10-21.el6_3.7.x86_64 thanks

1 0

[libvirt-users] sanlockd, virtlock and GFS2
by Franky Van Liedekerke 03 May '13

03 May '13

Hi, I'm trying to put in place a KVM cluster (using clvm and gfs2), but I'm running into some issues with either sanlock or virtlockd. All virtual machines are handled via the cluster (in /etc/cluser/cluster.conf) but I want some kind of locking to be in place as extra security measurement. Sanlock ======= At first I tried sanlock, but it seems if one node goes down unexpectedly, sanlock sometimes blocks everything on the other node. So I can't start any VM's there, so cluster failover is not working for the VM's. The locking dir for sanlock is on a shared dir (GFS2), so this might be the problem: sanlock recommends using a shared device (doing everything yourself) and don't recommend the locking dir to be on GFS2, but libvirt config suggest using a shared dir. Redhat even suggests that GFS2 is a good solution there, So: is there a hint on how to format/mount the GFS2 partition for sanlock usage? This thread (http://web.archiveorange.com/archive/v/fZfKniEdO4ZFyIhhNbzU ) recommends against GFS2+sanlock, but maybe using the "no_lock" gfs2 option might help? Any kind of advice? Virtlockd ========= Since sanlock was not working as expected, I tried virtlockd. This seems to be working well, but: live migration fails because the file on the shared disk (used for locking) is being locked by the original server running the VM. So when trying to do live migration, this fails and leaves the VM paused on the original server. Trying to migrate a paused server then works ok, but that's of course not live migration. So: is there a hint on how to format/mount the GFS2 partition for virtlock usage? Of course: since every VM is being started/stopped via the cluster, I could just leave out locking all together and trust on the cluster software ... Any insights/tips are greatly appreciated! Franky

2 6

[libvirt-users] domain disk io throttling
by Edoardo Comar 01 May '13

01 May '13

Hi Currently <blkiotune> in domain xml allows only to set cgroups weights blkio.weight or blkio.weight_device I see from https://www.kernel.org/doc/Documentation/cgroups/blkio-controller.txt that cgroups also allows throttling policies settable via blkio.throttle.read_bps_device - blkio.throttle.write_bps_device - blkio.throttle.read_iops_device - blkio.throttle.write_iops_device these AFAIK are not the ones set via <blkdeviotune> which need to be applied to individual virtual disks. are there any plans to allow libvirt to make use of the cgroup throttling? it looks to me it could make life simpler by assigning a bandwitdh limit to a domain without having to partition it among its multiple virtual disks. Assigning a limit to the domain is useful from a host resource management perspective, while having to dictate how guests use their individual disks is not, I think. -------------------------------------------------- regards, Edoardo Comar WebSphere Application Service Platform for Networks (ASPN) ecomar(a)uk.ibm.com +44 (0)1962 81 5576 IBM UK Ltd, Hursley Park, SO21 2JN Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

1 0

[libvirt-users] Basic Network Connections
by Slater, Joseph 01 May '13

01 May '13

Hi, If I have these fragments in a domain definition, the guest will start with "eth0" assigned by dhcp to an address on my lan. Things seem to work according to the documentation I can find. <network> <name>direct-macvtap</name> <forward mode='bridge'> <interface dev='eth0' /> </forward> </network> <devices> <interface type='direct'> <mac address='00:15:17:A6:BC:C9' /> <source dev='eth0' mode='bridge' /> <model type='virtio' /> </interface> </devices> I don't understand the <network> part here. It doesn't seem to be documented. I inherited these pieces so I do not know why they are as they are. If, instead, I have the following, the guest comes up with no network interface at all (except lo). On the host, interfaces vnet0 and virbr0 exist and virbr0 is 192.168.122.1. <devices> <interface type='network'> <source network='default'/> </interface> </devices> Adding in <model type='virtio' /> makes it start with "eth0", but no address has been assigned. I can manually do that and then I can communicate with the host but it's kind of a pain to add the address and routing manually. Oddly enough, though, ping from host to guest works normally, but ping guest to host seems to succeed once then hang (with no timeout). It is not at all obvious to me how virtio magically creates eth0. Am I doing something wrong, here? And, if anyone could advise how to use openvswitch I'd appreciate it. I've seen adding <virtualport type='openvswitch/> might be enough, presumably with an appropriate name for the source network. Joe

3 3

[libvirt-users] Libvirt and Glusterfs
by Pierre-Gilles Mialon 30 Apr '13

30 Apr '13

Hi, On a Fedora 18, I try to launch a VM with QEMU-GlusterFS native integration. I have enable fedora-virt-preview repo, and gluster-alpha3 repo. Below the list of installed package : glusterfs-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-devel-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-fuse-3.4.0-0.3.alpha3.fc18.x86_64 glusterfs-server-3.4.0-0.3.alpha3.fc18.x86_64 ipxe-roms-qemu-20130103-2.git717279a.fc18.noarch libvirt-1.0.4-1.fc18.x86_64 libvirt-client-1.0.4-1.fc18.x86_64 libvirt-daemon-1.0.4-1.fc18.x86_64 libvirt-daemon-config-network-1.0.4-1.fc18.x86_64 libvirt-daemon-config-nwfilter-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-interface-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-libxl-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-lxc-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-network-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-nodedev-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-nwfilter-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-qemu-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-secret-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-storage-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-uml-1.0.4-1.fc18.x86_64 libvirt-daemon-driver-xen-1.0.4-1.fc18.x86_64 libvirt-python-1.0.4-1.fc18.x86_64 qemu-common-1.4.1-2.fc18.x86_64 qemu-img-1.4.1-2.fc18.x86_64 qemu-kvm-1.4.1-2.fc18.x86_64 qemu-system-arm-1.4.1-2.fc18.x86_64 qemu-system-x86-1.4.1-2.fc18.x86_64 I have recompiled Qemu with –enable-glusterfs . Here the content of my /etc/glusterfs/glusterd.vol volume management type mgmt/glusterd option working-directory /var/lib/glusterd option transport-type socket option transport.socket.nodelay on option transport.socket.keepalive-time 10 option transport.socket.keepalive-interval 2 option transport.socket.read-fail-log off option rpc-auth.ports.insecure yes option rpc-auth-allow-insecure on end-volume I have defined the following line in my domain.xml <disk type='network' device='disk'> <driver name='qemu' cache='none'/> <source protocol='gluster' name='gv1/test.img'> <host name='127.0.0.1' transport='tcp' /> </source> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> # virsh start test LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name test -S -M pc-i440fx-1.4 -m 1024 -smp 1,sockets=1,cores=1,threads=1 -uuid 4c8686bc-9da9-c61d-cd85-8b2865ea4124 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/test.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=dc,menu=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 -drive file=gluster:// 127.0.0.1:24007/gv1/test.img,if=none,id=drive-virtio-disk0,cache=none-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=26,id=hostnet0,vhost=on,vhostfd=27 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:cf:d2:62,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,seamless-migration=on -vga qxl -global qxl-vga.ram_size=67108864 -global qxl-vga.vram_size=67108864 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 char device redirected to /dev/pts/4 (label charserial0) qemu-system-x86_64: -drive file=gluster:// 127.0.0.1:24007/gv1/test.img,if=none,id=drive-virtio-disk0,cache=none: Gluster connection failed for server=127.0.0.1 port=24007 volume=gv1 image=test.img transport=tcp qemu-system-x86_64: -drive file=gluster:// 127.0.0.1:24007/gv1/test.img,if=none,id=drive-virtio-disk0,cache=none: could not open disk image gluster://127.0.0.1:24007/gv1/test.img: No data available 2013-04-30 10:39:44.466+0000: shutting down but launching qemu with commant line work great : # qemu-system-x86_64 -name test -M pc-i440fx-1.4 -m 1024 -smp 1 -drive file=gluster:// 127.0.0.1:24007/gv1/test.img,if=none,id=drive-virtio-disk0,cache=none-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 Am I missing something ? Regards, -- Pierre-Gilles Mialon

1 0