- Users - libvirt List Archives

[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

[libvirt-users] virt-install creates a snapshot as the volume backend
by Ahmed Ossama 29 Apr '13

29 Apr '13

Greetings All, I was running libvirt-0.9.10 on CentOS 6.3 and it was working perfectly until yesterday when I decided to update to 6.4, which upgraded libvirt-0.9.10 to libvirt-0.10.2. I have a storage pool of type volume group, upon upgrading to libvirt-0.10.2, the disk image gets created as a snapshot on the volume group not as a regular volume. Now every time I create a vm using virt-install on a vg, the lv gets created as a snapshot not a regular lv, as a result I get the following error when I run dmesg: device-mapper: snapshots: Invalidating snapshot: Unable to allocate exception. Buffer I/O error on device dm-5, logical block 128251 Buffer I/O error on device dm-5, logical block 256 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 257 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 258 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 259 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 260 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 261 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 262 lost page write due to I/O error on dm-5 Buffer I/O error on device dm-5, logical block 263 lost page write due to I/O error on dm-5 lost page write due to I/O error on dm-5 and the following on the domain's log file: block I/O error in device 'drive-virtio-disk0': Input/output error (5) # virt-install --name="ns1" --vcpus="2" --check-cpu --ram=512 --os-variant="rhel6" --network "bridge=br0" --disk "pool=vdisks,size=22,cache=writeback" --vnc --hvm --vnclisten="0.0.0.0" --cdrom="/mnt/ISOs/centos/x86_64/CentOS-6.3-x86_64-bin-DVD1.iso" --hvm # lvs | grep ns ns1.img vm_volumes swi-aos-- 4.00m [ns1.img_vorigin] 0.00 When I try to create a volume using virt-manager on the volume group, it gets created as a snapshot. But when I create a volume using virsh, it gets created correctly; virsh # vol-create-as vdisks test 23622320128 # lvs | grep test test vm_volumes -wi-a---- 22.00g If anyone came across this issue or can provide an advice, I will appreciate it so much. -- Best Regards, Ahmed Ossama

2 2

[libvirt-users] No route to host
by digvijay chauhan 27 Apr '13

27 Apr '13

Hello, I tried to migrate the virtual machine using kvm,but it is giving me the error, "LIBVIRT ERROR NO ROUTE TO HOST" .How can i solve it. regards, DIgvijaySingh

1 0

[libvirt-users] How to tell if a hypervisor connection has died?
by Guido Winkelmann 26 Apr '13

26 Apr '13

Hi, What's the best way to tell if a virConnect object is not good to use anymore? (For example because the libvirtd on the other side crashed/has been stopped or because of some network failure) When I try this, the first API call I do on a broken connection yields an error with error number 38 (VIR_ERR_SYSTEM_ERROR) and all subsequent calls yield an error number 1 (VIR_ERR_INTERNAL_ERROR). Both of those are really unhelpful and could mean just about anything... Guido

3 3

[libvirt-users] how to control usb read write perm
by yue 25 Apr '13

25 Apr '13

hi,all i have 2 questions. both is related to spice usb redirect. 1. if i can control RW perm of usb device which is producted via spice ? in order to control user's rw operation in guestVM . 2.if user have several usbs, and plug them at the same time when using spice client. if i can control which usb(s) can be accessed by user in guestVM? thanks

1 0

[libvirt-users] 答复: libvirt_lxc start problem when selinux enbale
by Huang,Chaochang 25 Apr '13

25 Apr '13

Sorry “There is avc error messages in dmesg ……” ――should be “There is no avc error……” 发件人: Huang,Chaochang 发送时间: 2013年4月25日 15:41 收件人: 'libvir-list(a)redhat.com'; 'libvirt-users(a)redhat.com' 主题: libvirt_lxc start problem when selinux enbale Hi，all： the problem came out when selinux was enforced in targeted+MCS I start lxc through virsh――“virsh -c lxc:/// start instance-00004bd6” 1. When selinux is Permissive，lxc start is ok The result of “Ps auxZ” is： system_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 root 19218 0.0 0.0 47624 1244 ? Ss 15:26 0:00 /usr/libexec/libvirt_lxc --name system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19219 0.3 0.0 19276 1532 ? Ss 15:26 0:00 /sbin/init system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19406 0.0 0.0 177444 1332 ? Sl 15:26 0:00 /sbin/rsyslogd -i /var/run/sysl system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19420 0.0 0.0 64120 1144 ? Ss 15:26 0:00 /usr/sbin/sshd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19427 0.0 0.0 22136 956 ? Ss 15:26 0:00 xinetd -stayalive -pidfile /var system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19434 0.0 0.0 64316 832 ? Ss 15:26 0:00 /usr/sbin/saslauthd -m /var/run system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19435 0.0 0.0 64316 600 ? S 15:26 0:00 /usr/sbin/saslauthd -m /var/run system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19450 0.0 0.0 82388 2392 ? Ss 15:26 0:00 sendmail: rejecting new message system_u:system_r:svirt_lxc_net_t:s0:c192,c392 51 19459 0.0 0.0 78116 2016 ? Ss 15:26 0:00 sendmail: Queue runner@01:00:00 system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19467 0.0 0.0 175528 3672 ? Ss 15:26 0:00 /usr/sbin/httpd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 48 19470 0.0 0.0 175528 2204 ? S 15:26 0:00 /usr/sbin/httpd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19475 0.0 0.0 117212 1348 ? Ss 15:26 0:00 crond system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19491 0.0 0.0 4108 600 pts/0 Ss+ 15:26 0:00 /sbin/mingetty /dev/tty1 We can get into the lxc through “ssh” 2. When selinux is Enforcing，lxc start bad Th result of “ps auxZ” is: system_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 root 20624 0.0 0.0 47624 1244 ? Ss 15:29 0:00 /usr/libexec/libvirt_lxc --name system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 20625 0.0 0.0 17172 1036 pts/0 Ss+ 15:29 0:00 /sbin/init Only /sbin/init process started, no else. This is the real problem There is avc error messages in dmesg、/var/log/messages、/var/log/secure, and the same with selinux is Permissive Can anybody give some hints? Here are some system information: Kernel version 3.3.4 Libvirt version 0.9.13 Lxc guest image Centos 6.3 Lxc xml info is:  <domain type='lxc'> <name>instance-00004bd6</name> <uuid>96eada0e-7ea0-4865-8271-3565811c8eb0</uuid> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> <cmdline>console=ttyS0</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/home/stack/nova_state/instances/instance-00004bd6/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='fa:16:3e:09:00:a2'/> <source bridge='br100'/> <filterref filter='nova-instance-instance-00004bd6-fa163e0900a2'> <parameter name='DHCPSERVER' value='10.0.0.1'/> <parameter name='IP' value='10.0.0.11'/> <parameter name='PROJMASK' value='255.255.254.0'/> <parameter name='PROJNET' value='10.0.0.0'/> </filterref> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> <seclabel type='static' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_lxc_net_t:s0:c192,c392</label> </seclabel> </domain> Best Regard Huangchaochang

1 0

[libvirt-users] libvirt_lxc start problem when selinux enbale
by Huang,Chaochang 25 Apr '13

25 Apr '13

Hi，all： the problem came out when selinux was enforced in targeted+MCS I start lxc through virsh――“virsh -c lxc:/// start instance-00004bd6” 1. When selinux is Permissive，lxc start is ok The result of “Ps auxZ” is： system_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 root 19218 0.0 0.0 47624 1244 ? Ss 15:26 0:00 /usr/libexec/libvirt_lxc --name system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19219 0.3 0.0 19276 1532 ? Ss 15:26 0:00 /sbin/init system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19406 0.0 0.0 177444 1332 ? Sl 15:26 0:00 /sbin/rsyslogd -i /var/run/sysl system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19420 0.0 0.0 64120 1144 ? Ss 15:26 0:00 /usr/sbin/sshd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19427 0.0 0.0 22136 956 ? Ss 15:26 0:00 xinetd -stayalive -pidfile /var system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19434 0.0 0.0 64316 832 ? Ss 15:26 0:00 /usr/sbin/saslauthd -m /var/run system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19435 0.0 0.0 64316 600 ? S 15:26 0:00 /usr/sbin/saslauthd -m /var/run system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19450 0.0 0.0 82388 2392 ? Ss 15:26 0:00 sendmail: rejecting new message system_u:system_r:svirt_lxc_net_t:s0:c192,c392 51 19459 0.0 0.0 78116 2016 ? Ss 15:26 0:00 sendmail: Queue runner@01:00:00 system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19467 0.0 0.0 175528 3672 ? Ss 15:26 0:00 /usr/sbin/httpd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 48 19470 0.0 0.0 175528 2204 ? S 15:26 0:00 /usr/sbin/httpd system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19475 0.0 0.0 117212 1348 ? Ss 15:26 0:00 crond system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 19491 0.0 0.0 4108 600 pts/0 Ss+ 15:26 0:00 /sbin/mingetty /dev/tty1 We can get into the lxc through “ssh” 2. When selinux is Enforcing，lxc start bad Th result of “ps auxZ” is: system_u:system_r:virtd_lxc_t:s0-s0:c0.c1023 root 20624 0.0 0.0 47624 1244 ? Ss 15:29 0:00 /usr/libexec/libvirt_lxc --name system_u:system_r:svirt_lxc_net_t:s0:c192,c392 root 20625 0.0 0.0 17172 1036 pts/0 Ss+ 15:29 0:00 /sbin/init Only /sbin/init process started, no else. This is the real problem There is avc error messages in dmesg、/var/log/messages、/var/log/secure, and the same with selinux is Permissive Can anybody give some hints? Here are some system information: Kernel version 3.3.4 Libvirt version 0.9.13 Lxc guest image Centos 6.3 Lxc xml info is:  <domain type='lxc'> <name>instance-00004bd6</name> <uuid>96eada0e-7ea0-4865-8271-3565811c8eb0</uuid> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='x86_64'>exe</type> <init>/sbin/init</init> <cmdline>console=ttyS0</cmdline> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/libexec/libvirt_lxc</emulator> <filesystem type='mount' accessmode='passthrough'> <source dir='/home/stack/nova_state/instances/instance-00004bd6/rootfs'/> <target dir='/'/> </filesystem> <interface type='bridge'> <mac address='fa:16:3e:09:00:a2'/> <source bridge='br100'/> <filterref filter='nova-instance-instance-00004bd6-fa163e0900a2'> <parameter name='DHCPSERVER' value='10.0.0.1'/> <parameter name='IP' value='10.0.0.11'/> <parameter name='PROJMASK' value='255.255.254.0'/> <parameter name='PROJNET' value='10.0.0.0'/> </filterref> </interface> <console type='pty'> <target type='lxc' port='0'/> </console> </devices> <seclabel type='static' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_lxc_net_t:s0:c192,c392</label> </seclabel> </domain> Best Regard Huangchaochang

1 0