January 2014 - Users - libvirt List Archives

[libvirt-users] some problem with snapshot by libvirt
by xingxing gao 21 Nov '14

21 Nov '14

Hi,all,i am using libvirt to manage my vm,in these days i am testing the libvirt snapshot ,but meet some problem: the snapshot was created from this command: snapshot-create-as win7 --disk-only --diskspec vda,snapshot=external --diskspec hda,snapshot=no but when i tried to revert from the snapshot which created from the above command ,i got error below: virsh # snapshot-revert win7 1338041515 --force error: unsupported configuration: revert to external disk snapshot not supported yet version: virsh # version Compiled against library: libvir 0.9.4 Using library: libvir 0.9.4 Using API: QEMU 0.9.4 Running hypervisor: QEMU 1.0.93

4 8

[libvirt-users] libvirt-1.2.0
by cool dharma06 04 Feb '14

04 Feb '14

hi, i am using libvirt-1.2.0 which is installed from source. Which i am using to launch instance on xen. its working fine when i am launching vm from the root user. But i am entered as another user means its throwing the error. And libvirt is working fine in that user except the creating vm: Please refer the following things: eucalyptus@cooldharma06:/opt/i-47FD0798$ virsh -c xen:/// WARNING: gnome-keyring:: couldn't connect to: /home/dharmalingams/.cache/keyring-r004e7/pkcs11: Permission denied Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # version Compiled against library: libvirt 1.2.0 Using library: libvirt 1.2.0 Using API: Xen 1.2.0 Running hypervisor: Xen 4.3.0 virsh # list Id Name State ---------------------------------------------------- *virsh # create libvirt_sec.xml * *error: Failed to create domain from libvirt_sec.xml* *error: access denied* >From the libvirtd.log: 2014-01-31 09:46:16.329+0000: 27937: error : virAccessDriverPolkitCheck:176 : access denied: Policy kit denied action org.libvirt.api.domain.write from 28281,1877379: exit status 1 2014-01-31 09:46:16.329+0000: 27937: error : virAccessManagerSanitizeError:203 : access denied 2014-01-31 09:46:16.329+0000: 27937: error : virAccessManagerSanitizeError:203 : access denied Suggest me some solution to solve this one. Thanks & Regards, cooldharma06.

2 1

[libvirt-users] Trouble configuring with macvtap passthrough on Debian Wheezy / Jessie
by Richard Gomes 02 Feb '14

02 Feb '14

( Posting again. Correct subject line now! ) Hello, I'm trying to use macvtap on Debian Wheezy. Actually, I've installed a recent version of libvirt and qemu from Jessie, using wheezy-backports. $ virsh version Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 I'm trying to configure a macvtap interface like this: <interface type='direct'> <mac address='52:54:00:7b:05:cd'/> <source dev='eth1' mode='passthrough'/> <model type='rtl8139'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </interface> The interface eth1 is used exclusively by this VM, so as far as I understand, mode 'passthrough' is enough since I'd like to "plug" the VM straight onto a public static IP. On my /etc/networks/interfaces, I have this: # start :: define eth1 iface eth1 inet manual # end :: define eth1 It does not matter whether eth1 is up or down, when I try to start the VM, I get the following error: Error starting domain: Cannot create macvlan devices on this platform: Function not implemented Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 66, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup self._backend.create() File "/usr/lib/python2.7/dist-packages/libvirt.py", line 866, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: Cannot create macvlan devices on this platform: Function not implemented Trying to solve the issue, I found this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=737097 I've tried to rebuild the package from Debian sources, but apparently, macvtap is already defined, as I've reported to another mailing list. For your information: > I'm new to building packages from Debian sources, so I followed > instructions from > > https://wiki.debian.org/HowToPackageForDebian#Building_Debian_packages > > $ apt-get -t wheezy-backports source libvirt > $ cd libvirt-0.9.12.3/ > $ sudo apt-get build-dep libvirt > $ debuild -i -us -uc -b > > So... yes, it works and builds without any errors. > > Next step now is applying the changes mentioned. > But I'm confused because /apparently/ debian/rules is already the way > it should be. > > ifneq (,$(findstring $(DEB_HOST_ARCH_OS), linux)) > WITH_STORAGE_LVM = --with-storage-lvm > WITH_STORAGE_ISCSI = --with-storage-iscsi > WITH_STORAGE_DISK = --with-storage-disk > WITH_UDEV = --with-udev --without-hal > WITH_CAPNG = --with-capng > WITH_POLKIT = --with-polkit > * WITH_MACVTAP = --with-macvtap** > ** WITH_NETWORK = --with-network** > * WITH_QEMU = --with-qemu > WITH_OPENVZ = --with-openvz > WITH_NETCF = --with-netcf > ifneq (,$(findstring $(DEB_HOST_ARCH), amd64 i386 ia64 mips mipsel powerpc)) > WITH_NUMA = --with-numactl > else > WITH_NUMA = --without-numactl > endif > ifneq (,$(findstring $(DEB_HOST_ARCH), ia64)) > WITH_LXC = --without-lxc > else > WITH_LXC = --with-lxc > endif > else > WITH_STORAGE_LVM = --without-storage-lvm > WITH_STORAGE_ISCSI = --without-storage-iscsi > WITH_STORAGE_DISK = --without-storage-disk > WITH_UDEV = --without-udev --with-hal > WITH_CAPNG = --without-capng > WITH_POLKIT = --without-polkit > * WITH_MACVTAP = --without-macvtap** > ** WITH_NETWORK = --without-network** > * WITH_QEMU = --without-qemu > WITH_LXC = --without-lxc > WITH_NUMA = --without-numactl > WITH_NETCF = --without-netcf > endif > > > I suppose that nothing has to be changed, correct? ... since the > _/then/_ branch already has the change mentioned and the _/else/_ > branch probably means that nothing related to networking would be > enabled anyway. > > Am I missing something ? Thoughts? Thanks a lot :) -- Richard Gomes http://rgomes.info http://www.linkedin.com/in/rgomes mobile: +44(77)9955-6813 inum <http://www.inum.net/>: +883(5100)0800-9804 sip:rgomes@ippi.fr

1 1

[libvirt-users] intel quad gigabit nic and pci passthrough
by Ivan Kabaivanov 02 Feb '14

02 Feb '14

Hi all I have a very weird case of pci passthrough. I have a machine with 7 network interfaces, all of them intel. Four of them are on one quad giga ethernet device. If I manually unbind the devices and allow qemu to use them, with intel IOMMU working, everything works like a charm. Here's how I do it manually: root@kybrat (x86_64) ~]$ lspci -nn | grep net 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 06) 02:00.0 Ethernet controller [0200]: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) [8086:107d] (rev 06) 05:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) 05:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) 06:00.0 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) 06:00.1 Ethernet controller [0200]: Intel Corporation 82571EB Gigabit Ethernet Controller [8086:10a4] (rev 06) 0c:00.0 Ethernet controller [0200]: Intel Corporation 82572EI Gigabit Ethernet Controller (Copper) [8086:107d] (rev 06) echo "8086 10a4" > /sys/bus/pci/drivers/pci-stub/new_id echo "8086 107d" > /sys/bus/pci/drivers/pci-stub/new_id echo "0000:05:00.0" > /sys/bus/pci/devices/0000\:05\:00.0/driver/unbind echo "0000:05:00.0" > /sys/bus/pci/drivers/pci-stub/bind echo "0000:05:00.1" > /sys/bus/pci/devices/0000\:05\:00.1/driver/unbind echo "0000:05:00.1" > /sys/bus/pci/drivers/pci-stub/bind echo "0000:06:00.0" > /sys/bus/pci/devices/0000\:06\:00.0/driver/unbind echo "0000:06:00.0" > /sys/bus/pci/drivers/pci-stub/bind echo "0000:06:00.1" > /sys/bus/pci/devices/0000\:06\:00.1/driver/unbind echo "0000:06:00.1" > /sys/bus/pci/drivers/pci-stub/bind echo "0000:0c:00.0" > /sys/bus/pci/devices/0000\:0c\:00.0/driver/unbind echo "0000:0c:00.0" > /sys/bus/pci/drivers/pci-stub/bind qemu-system-i386 -enable-kvm \ -m 2048 \ -cpu host \ -machine pc-q35-1.6 \ -drive file=/media/virtual/krym.qcow2,if=virtio \ -net none \ -device pci-assign,host=06:00.1,rombar=0 \ -device pci-assign,host=05:00.0,rombar=0 \ -device pci-assign,host=06:00.0,rombar=0 \ -device pci-assign,host=05:00.1,rombar=0 \ -device pci-assign,host=0c:00.0,rombar=0 \ -cdrom /media/virtual/asg-9.107-33.1.iso \ -boot c \ -vnc :0 \ -runas virtual \ -monitor unix:/media/virtual/control/krym/monitor,server,nowait \ -rtc base=localtime,clock=host,driftfix=none This starts qemu and pci passthrough works nicely. Now, if I try to do the same thing through libvirt, virt-install doesn't like the quad ethernet device pci passthrough and I get the error below: virt-install --name=krym --ram=2048 --vcpus=1 --cpu=host --import --os-type=linux --disk path=/media/virtual/krym.qcow2,format=qcow2,bus=virtio --nonetworks --graphics vnc,port=5900 --virt-type=kvm --machine=q35 --accelerate --host-device=pci_0000_06_00_1 --host-device=pci_0000_05_00_0 --host-device=pci_0000_06_00_0 --host-device=pci_0000_05_00_1 --host-device=pci_0000_0c_00_0 Starting install... ERROR Requested operation is not valid: PCI device 0000:06:00.1 is not assignable Domain installation does not appear to have been successful. If it was, you can restart your domain by running: virsh --connect qemu:///system start krym otherwise, please restart your installation. If I try to use just one NIC (any NIC, as long as it's not the quad NIC), things do work: virt-install --name=krym --ram=2048 --vcpus=1 --cpu=host --import --os-type=linux --disk path=/media/virtual/krym.qcow2,format=qcow2,bus=virtio --nonetworks --graphics vnc,port=5900 --virt-type=kvm --machine=q35 --accelerate --host-device=pci_0000_0c_00_0 Starting install... Creating domain... | 0 B 00:00:01 Cannot open display: Run 'virt-viewer --help' to see a full list of available command line options Domain creation completed. You can restart your domain by running: virsh --connect qemu:///system start krym So I guess libvirt has some problem with the intel quad NIC. I will appreciate any help. Thanks, IvanK.

2 2

[libvirt-users] Libvirt Error Creating VMs for Nimbus Cloud
by Joshua McKee 01 Feb '14

01 Feb '14

Hello, I am having an issue with libvirt in my Nimbus cloud setup. When I use the Nimbus VM creation test scripts on a VMM node (using libvirt), the VM is created without a problem. However, when I attempt to create a new VM using Nimbus (which then tries to create the VM on the VMM node), I encounter the following error: --------------------------------------------------------------------------------------------------------------------------------------------- $ ./nimbus-cloud-client-022/bin/cloud-client.sh --run --name testimage --hours 1 Launching workspace. Workspace Factory Service: https://yellow:8443/wsrf/services/WorkspaceFactoryService Creating workspace "vm-035"... done. IP address: 172.29.99.20 Hostname: pub02 Start time: Fri Jan 31 13:48:57 MST 2014 Shutdown time: Fri Jan 31 14:48:57 MST 2014 Termination time: Fri Jan 31 14:50:57 MST 2014 Waiting for updates. Problem with vm-035: Unexpected issue STDERR: 2014-01-31 13:48:44,412 - WARNING - no qemu_img configuration, copy-on-write support is disabled libvir: QEMU error : Domain not found: no domain with matching name 'wrksp-33' libvir: error : An error occurred, but the cause is unknown 2014-01-31 13:48:45,587 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,587 - ERROR - An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/defaults/lvrt/lvrt_common.py", line 123, in create newvm = self._vmm().createXML(xml, 0) File "/usr/lib/python2.7/dist-packages/libvirt.py", line 2189, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: An error occurred, but the cause is unknown 2014-01-31 13:48:45,589 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 155, in _common_withnetsecurity _common_withtmplease(nic_set, kernel, local_file_set, c, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 174, in _common_withtmplease platform.create(local_file_set, nic_set, kernel) File "/opt/nimbus/src/python/workspacecontrol/defaults/lvrt/lvrt_common.py", line 128, in create raise UnexpectedError(shorterr) UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,589 - ERROR - Creation problem: going to back out tmp space lease 2014-01-31 13:48:45,589 - ERROR - Backed out tmp space lease 2014-01-31 13:48:45,589 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 137, in _common_withnetbootstrap _common_withnetsecurity(vm_name, nic_set, kernel, local_file_set, p, c, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 164, in _common_withnetsecurity raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,589 - ERROR - Creation problem: going to back out net security 2014-01-31 13:48:45,606 - ERROR - Backed out net security 2014-01-31 13:48:45,606 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 119, in _common_withnics _common_withnetbootstrap(vm_name, nic_set, kernel, local_file_set, p, c, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 146, in _common_withnetbootstrap raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,607 - ERROR - Creation problem: going to back out net bootstrap 2014-01-31 13:48:45,607 - ERROR - Backed out net bootstrap 2014-01-31 13:48:45,607 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 96, in _common _common_withnics(vm_name, nic_set, kernel, local_file_set, p, c, localnet, netbootstrap, netsecurity, platform, justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 128, in _common_withnics raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown 2014-01-31 13:48:45,607 - ERROR - Creation problem: going to back out net leases 2014-01-31 13:48:45,607 - ERROR - Backed out net leases 2014-01-31 13:48:45,608 - ERROR - Problem creating the VM: An error occurred, but the cause is unknown Traceback (most recent call last): File "/opt/nimbus/src/python/workspacecontrol/main/wc_core.py", line 79, in core _core(vm_name, action, p, c) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core.py", line 168, in _core wc_core_creation.create(vm_name, p, c, async, editing, images, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 16, in create _create_local(vm_name, p, c, async, editing, images, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 31, in _create_local _common(local_file_set, vm_name, p, c, editing, kernels, localnet, netbootstrap, netlease, netsecurity, persistence, platform, justprint=justprint) File "/opt/nimbus/src/python/workspacecontrol/main/wc_core_creation.py", line 107, in _common raise e UnexpectedError: Problem creating the VM: An error occurred, but the cause is unknown Problem executing: Problem creating the VM: An error occurred, but the cause is unknown Exiting with error code: 4 Workspace "vm-035" did NOT reach target state "Running" Problem running 'vm-035'. --------------------------------------------------------------------------------------------------------------------------------------------- I checked /var/log/libvirtd.log, and found the following: --------------------------------------------------------------------------------------------------------------------------------------------- 2014-01-31 20:48:39.311+0000: 2888: info : libvirt version: 0.9.8 2014-01-31 20:48:39.311+0000: 2888: error : virNetSocketReadWire:1006 : End of file while reading data: Input/output error --------------------------------------------------------------------------------------------------------------------------------------------- I don't know if this is relevant, but I also noticed this warning when creating the VM through the test scripts mentioned above: --------------------------------------------------------------------------------------------------------------------------------------------- 2014-01-31 05:41:44.018+0000: 1351: warning : qemuDomainObjTaint:1134 : Domain id=1 name='control-test' uuid=95f2d398-6b98-5359-7597-b0f596aae996 is tainted: high-privileges --------------------------------------------------------------------------------------------------------------------------------------------- I assumed this was a permissions issue, but I double checked and everything seems in order. I did not have this issue on my previous Nimbus cloud setup. Thanks, Josh

1 1

[libvirt-users] Looks like blockpull does not accept a subset of the entire chain of backing files
by Richard Gomes 01 Feb '14

01 Feb '14

Hello If I'm not terribly mistaken, looks like libvirt 1.2.1 does not provide ability of merging only a subset of the entire chain of backing files. So, if I have a chain like this: root <- a <-b <- c <- d <- active ... and I'd like to obtain a chain like this: root <- c <- d <- active ... looks like it's not supported, since I'm trying the command / //virsh blockpull domain --path /path/to/c --bandwidth 30 --base /path/to/root// (1) / ... but it complains because /--path /path/to/c/ is not recognized, since only /--path /path/to/active/ is acceptable: / //virsh blockpull domain --path /path/to/active --bandwidth 30 --base /path/to/root// (2) / So, command (1) fails but command (2) succeeds. The point is: How could I obtain the results I'm trying to achieve via command (1) ? I'm new to libvirt, but the article below made me think that what I'm trying to do would be possible: http://kashyapc.fedorapeople.org/virt/lc-2012/snapshots-handout.html ( see section on /blockpull/ ) Thoughts? For your information, my environment is: Compiled against library: libvirt 1.2.1 Using library: libvirt 1.2.1 Using API: QEMU 1.2.1 Running hypervisor: QEMU 1.7.0 Running against daemon: 1.2.1 Thanks -- Richard Gomes http://rgomes.info http://www.linkedin.com/in/rgomes mobile: +44(77)9955-6813 inum <http://www.inum.net/>: +883(5100)0800-9804 sip:rgomes@ippi.fr

5 6

[libvirt-users] Dynamically setting permanent memory libvirt-lxc
by mallu mallu 31 Jan '14

31 Jan '14

I'm trying to permanently change memory allocation for a libvirt-lxc domain. So far I tried changing memory in memory.limit_in_bytes under /cgroup/memory/libvirt/lxc/<container>/. This didn't help. It appears that libvirt is not reading changes in cgroup. My requirements are 1) Be able to dynamically change memory of a LXC domain without reboot 2) The memory change must survive LXC domain reboot. Any help would be greatly appreciated

2 5

[libvirt-users] libvirt-sandbox question.
by Christopher Stone 29 Jan '14

29 Jan '14

I hope this question isn't considered too off topic for this list, I am trying to reach the libvirt-sandbox developers, but I could not find a libvirt-sandbox specific mailing list, and it seemed to me that libvirt-sandbox was a part of libvirt itself. I am trying to port libvirt-sandbox to run on a CentOS 6.5 system. This wasn't too hard but, I had to do the following: I have used the CentOS repo addon ElRepo to upgrade the kernel to 3.10.28. CentOS normally runs a 2.6.32 kernel. I upgraded glib2 from 2.36 to 2.38.2. I did this by building 2.38.2 from source and installing it into /usr/local. Thus, the 2.36 version still exists in /lib64 and the normal CentOS applications use this version. I built libvirt 1.2.1 from source and installed it into /usr/local. I used: ./configure --with-lxc --with-selinux --with-secdriver-selinux --prefix=/usr/local I built libvirt-glib 0.1.7 from source and installed it into /usr/local. I used: PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --prefix=/usr/local I build libvirt-sandbox 0.5.1 from source and installed it into /usr/local. I used: PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure As a test, I am able to run the libvirt lxc helloworld example: [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// define helloworld.xml Domain helloworld defined from helloworld.xml [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// start helloworld Domain helloworld started [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// list Id Name State ---------------------------------------------------- 9819 helloworld running [root@scwnet1 lxc_helloworld]# virsh -c lxc:/// console helloworld Connected to domain helloworld Escape character is ^] sh-4.1# exit exit Next, I try to use libvirt-sandbox, and I get the following error: [root@scwnet1 tests]# /usr/local/bin/virt-sandbox -c lxc:/// /bin/sh Unable to start sandbox: Failed to create domain: unsupported configuration: Unable to find security driver for label selinux My libvirt config.log shows the SELinux security driver as yes: configure:71172: Configuration summary configure:71174: ===================== configure:71176: configure:71178: Drivers configure:71180: configure:71182: Xen: no configure:71184: QEMU: yes configure:71186: UML: yes configure:71188: OpenVZ: yes configure:71190: VMware: yes configure:71192: VBox: yes configure:71194: XenAPI: no configure:71196: xenlight: no configure:71198: LXC: yes configure:71200: PHYP: no configure:71202: ESX: yes configure:71204: Hyper-V: no configure:71206: Parallels: yes configure:71208: Test: yes configure:71210: Remote: yes configure:71212: Network: yes configure:71214: Libvirtd: yes configure:71216: Interface: yes configure:71218: macvtap: yes configure:71220: virtport: yes configure:71222: configure:71224: Storage Drivers configure:71226: configure:71228: Dir: yes configure:71230: FS: yes configure:71232: NetFS: yes configure:71234: LVM: yes configure:71236: iSCSI: yes configure:71238: SCSI: yes configure:71240: mpath: yes configure:71242: Disk: yes configure:71244: RBD: no configure:71246: Sheepdog: no configure:71248: Gluster: no configure:71250: configure:71252: Security Drivers configure:71254: configure:71256: SELinux: yes (/sys/fs/selinux) configure:71258: AppArmor: no (install profiles: no) configure:71260: configure:71262: Driver Loadable Modules configure:71264: configure:71267: dlopen: -ldl configure:71273: configure:71275: Libraries configure:71277: configure:71296: apparmor: no configure:71326: attr: yes (CFLAGS='' LIBS='-lattr') configure:71356: audit: yes (CFLAGS='' LIBS='-laudit') configure:71386: avahi: yes (CFLAGS='-D_REENTRANT ' LIBS='-lavahi-common -lavahi-client ') configure:71416: blkid: yes (CFLAGS='-I/usr/include/blkid -I/usr/include/uuid ' LIBS='-lblkid ') configure:71446: capng: yes (CFLAGS='' LIBS='-lcap-ng') configure:71476: curl: yes (CFLAGS='-DCURL_DISABLE_TYPECHECK ' LIBS='-lcurl ') configure:71506: dbus: no configure:71536: fuse: no configure:71566: glusterfs: no configure:71596: hal: no configure:71626: netcf: yes (CFLAGS=' ' LIBS='-lnetcf ') configure:71656: numactl: yes (CFLAGS='' LIBS='-lnuma') configure:71686: openwsman: no configure:71716: pciaccess: yes (CFLAGS=' ' LIBS='-lpciaccess ') configure:71746: readline: yes (CFLAGS='' LIBS='-lreadline') configure:71776: sanlock: yes (CFLAGS='' LIBS='-lsanlock_client') configure:71806: sasl: yes (CFLAGS='' LIBS='-lsasl2') configure:71836: selinux: yes (CFLAGS='' LIBS='-lselinux') configure:71866: ssh2: no configure:71897: udev: yes (CFLAGS=' ' LIBS='-ludev ') configure:71927: yajl: yes (CFLAGS='' LIBS='-lyajl') configure:71940: libxml: -I/usr/include/libxml2 -lxml2 configure:71942: dlopen: -ldl configure:71948: openwsman: no configure:71952: gnutls: -DGCRYPT_NO_DEPRECATED -lgnutls -lgcrypt configure:71958: firewalld: no configure:71965: polkit: /usr/bin/pkcheck (version 1) configure:71976: xen: no configure:71983: xenapi: no configure:71990: xenlight: no configure:71994: pcap: -lpcap configure:72001: nl: -lnl configure:72011: mscom: no configure:72015: xdr: configure:72025: rbd: no configure:72029: configure:72031: Test suite configure:72033: configure:72035: Coverage: no configure:72037: Alloc OOM: no configure:72039: configure:72041: Miscellaneous configure:72043: configure:72045: Debug: yes configure:72047: Use -Werror: no My libvirt capabilites shows this: [root@scwnet1 tests]# virsh -c lxc:/// capabilities <capabilities> <host> <uuid>20b4e77c-3fb8-dc11-968d-c8600070189e</uuid> <cpu> <arch>x86_64</arch> </cpu> <power_management> <suspend_mem/> <suspend_disk/> </power_management> <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>8334880</memory> <cpus num='4'> <cpu id='0' socket_id='0' core_id='0' siblings='0-1'/> <cpu id='1' socket_id='0' core_id='1' siblings='0-1'/> <cpu id='2' socket_id='0' core_id='2' siblings='2-3'/> <cpu id='3' socket_id='0' core_id='3' siblings='2-3'/> </cpus> </cell> </cells> </topology> <secmodel> <model>none</model> <doi>0</doi> </secmodel> </host> <guest> <os_type>exe</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/local/libexec/libvirt_lxc</emulator> <domain type='lxc'> </domain> </arch> </guest> <guest> <os_type>exe</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/local/libexec/libvirt_lxc</emulator> <domain type='lxc'> </domain> </arch> </guest> </capabilities> I am not sure if secmodel none is the problem. Can someone give me some direction on how to fix this? Cheers, Chris.

2 1

[libvirt-users] dropping capabilities in lxc containers
by Thierry Parmentelat 29 Jan '14

29 Jan '14

Hi there I’m not quite proficient with libvirt yet, and have been using it so far primarily to manage lxc containers I was hoping to find a means to configure the set of capabilities that guests should drop, but came across a few web pages suggesting these were set in stone in the code is this correct, or is there a means to tweak this set from the host via the xml config or a virsh command ? any hint / pointer to documentation in this respect would be most appreciated — Thierry

2 3

[libvirt-users] Libvirt-LXC + systemd + user namespace
by Jan Olszak 29 Jan '14

29 Jan '14

Hi there! I am trying to turn on user namespace by adding following lines to the config: <idmap> <uid start='0' target='0' count='100000'/> <gid start='0' target='0' count='100000'/> </idmap> As you can see the root in container is mapped to the root outside. I was expected to see no difference after adding this lines, but unfortunately there are some (see details below). Am I missing something or is there a problem with system, libvirt or kernel? Full libvirt config: <domain type='lxc'> <name>test_with_idmap</name> <memory>102400</memory> <os> <type>exe</type> <init>/usr/lib/systemd/systemd</init> </os> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <idmap> <uid start='0' target='0' count='100000'/> <gid start='0' target='0' count='100000'/> </idmap> <devices> <console type='pty'/> <filesystem type='mount'> <source dir='/guest'/> <target dir='/'/> </filesystem> </devices> </domain> root:~> uname -a Linux localhost 3.10.19-01077-g4a19d28-dirty #5 SMP PREEMPT Mon Jan 13 12:56:09 CET 2014 armv7l GNU/Linux root:~> libvirtd --version libvirtd (libvirt) 1.2.1 root:~> systemd --version systemd 204 After adding idmap to config systemd can't start many of its services, in particular: Failed to mount Debug File System. Failed to mount Configuration File System. Failed to mount FUSE Control File System. Failed to start udev Kernel Device Manager. Failed to start Remount Root and Kernel File Systems. Failed to start Journal Service. systemctl status says: ExecMount=/bin/mount debugfs /sys/kernel/debug -t debugfs (code=exited, status=32) ExecMount=/bin/mount configfs /sys/kernel/config -t configfs (code=exited, status=32) ExecMount=/bin/mount fusectl /sys/fs/fuse/connections -t fusectl (code=exited, status=32) ExecStart=/usr/lib/systemd/systemd-udevd (code=exited,status=206/OOM_ADJUST) ExecStart=/usr/lib/systemd/systemd-remount-fs (code=exited,status=1/FAILURE) ExecStart=/usr/lib/systemd/systemd-journald (code=exited, status=218/CAPABILITIES) Thanks!

3 3

Re: [libvirt-users] How to find domain os type and ip address
by Rathidevi 29 Jan '14

29 Jan '14

Hi All, I am using the libvirt-0.5.1.jar and downloaded from this link ftp://libvirt.org/libvirt/java. 1) To find the os type of domain I use this method getOSType(). But it returns the kvm or hvm instead of windows and linux. Is the any way to find the original os type of domain? 2) Please give is there any option or method available to find the ipaddress of domain? Thanks & Regards Rathidevi

2 1

[libvirt-users] Does libvirt support attach volume to linux container now?
by Du Jun 29 Jan '14

29 Jan '14

Hi all, I am playing with linux container and using libvirt to manage linux container. I find I fail to attach volume to linux container via libvirt and I got the following error message: Failed to attach volume: data-111 to VM: lxc-111; org.libvirt.LibvirtException: unsupported configuration: Can't setup disk for non-block device. My question is that does libvirt support attaching volume to linux container? If it supports, what version should I use? Thanks, DuJun

1 0

[libvirt-users] Problems with pmsuspend/wakeup
by Alex 26 Jan '14

26 Jan '14

Hi, I've migrated a Windows7 vm from F17 to F20 and it appears to be working okay. Apparently when it's left idle for some period, it automatically goes into a pmsuspend state, and I'm unable to wake it. I've figured out the virsh dompmwakeup command, which then virsh shows it's running, but the vm is still unresponsive. It doesn't respond to ping and the display is just black when accessing it through virt-manager. Is there something I need to do in the guest for it to wake up properly? How can I just prevent it from ever suspending in the first place? Thanks, Alex

1 0

[libvirt-users] Libvirt support for VEB
by Padmanabhan Krishnan 24 Jan '14

24 Jan '14

Hello, I have a setup of virtual machines and wherein my virtual switch (OVS) takes care of switching locally and it uses the network for talking to VM's outside the server (like a VEB scenario I guess). I want Netlink messages to be sent to LLDPAD. I understand that i had to modify the XML files and start the VM. But, i see from the XML that it supports only VEPA, not VEB. But, irrespective of VEB or VEPA, those VM information should be known to the upstream switch through VDP. 802.1QBG seem to support this (both VEPA and VEB) http://www.ieee802.org/1/files/private/bg-drafts/d2/802-1qbg-d2-2.pdf But, for VEB, no net link messages are sent by libvirt. Why is that? From the XML example, I see that: <interface type=’direct’> <mac address=’d0:0f:d0:0f:02:01’/> <source dev=’eth2.20’ mode=’vepa’/> <source network=’default’/> <virtualport type=’802.1Qbg’> <parameters managerid=’12’ typeid=’0x123456’ typeidversion=’1’ instanceid=’09b00c53-8b5c-4eeb-8f00-d847aa05191b’ /> </virtualport> I tried different combinations by changing the interface type to bridge and and trying Qbg as in below, I find that it doesn't send a Netlink message to LLDPAD. There's no "mode=veb". </controller> <interface type='bridge'> <mac address='00:54:00:4e:46:04'/> <source bridge='xml_br'/> <virtualport type='802.1Qbg'> <parameters managerid='12' typeid='1193046' typeidversion='1' instanceid='09b00c53-8b5c-4eeb-8f00-d847aa05191b'/> </virtualport> <target dev='tap_xml'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> How do i get this to work? Is this a limitation? Thanks, KP

1 0

Re: [libvirt-users] PCI Passthrough
by The PowerTool 23 Jan '14

23 Jan '14

Oops! I blame Microsoft. I use Hotmail and am very, very unhappy that MS bought them out which leaves me stuck with Outlook, which sucks. I've always just hit reply in the past and it's worked. Now I'm going to have to be careful to make sure my replies go where I expect them. Thank you very much for the information. I was really hoping to consolidate systems but that apparently won't happen in the near future. So that means I'll be focusing my efforts on getting my Spacewalk server updated and then upgrading from F18 to F20 or 21. Yep, I was very aware of F18 dropping and thankful for the one brief delay. I'll be taking a look at it again once I upgrade to the current Fedora. If that doesn't work I'll wait and keep an eye on posts and when things look better probably get new hardware (which will likely be the requirement). Thanks, again! Date: Thu, 23 Jan 2014 11:37:02 +0200 From: laine(a)laine.org To: thepowertool_sc(a)hotmail.com Subject: Re: [libvirt-users] PCI Passthrough On 01/21/2014 05:32 PM, The PowerTool wrote: Laine, Thank you very much for your response. I took a look at the first link you provide (archlinux). Key items that caught my attention (in order): 1. "Intel IGDs won't work"--I have Intel integrated video 2. "NOTE: THIS IS EXPERIMENTAL SO IT MIGHT NOT WORK FOR YOU" (self-explanatory) One additional note: When I received the "permission denied" error I had the same thought as you. I was unaware of the issue you outlined with libvirt needing to be configured to run as root on some versions of Fedora. Still, as root I did successfully detach my video card... at least that's how it appeared given the monitor went no-signal and then displayed a strange pattern. The system wouldn't ping and failed to respond to ssh attempts. I had to reboot to recover. I tried a second experiment where I first started a ssh session and then detached (from the host). Going back to the 2nd system the ssh session stopped responding. Actually that's probably more of an indication that your kernel just doesn't properly handle having the primary video device disappear midstream. You may have different results if you connected two video cards to a system, and tried to passthrough the secondary (it still probably wouldn't work, but it would likely fail in a different way). That leads me to believe it's not fully baked, something critically fails, and it's not going to work for me at-least at my current levels. Alex Williamson gave a talk at this year's KVM Forum (in October) about the difficulties of making VGA passthrough work, and it was truly frightening; there are just too many strange, undocumented backdoors in the devices that are required by the drivers for proper operation. In my mind this whole area just has too great of a likelihood of total failure without possibility of making it work in a reasonable time frame. To answer your question: I'm running Fedora 18. F18 was definitely one of the releases that was broken wrt PCI passthrough requiring qemu to be run as root. I don't recall if the kernel guys ever fixed it in that version or not. I pestered them about it for months, then finally gave up. BTW, you know that F18 has just gone end-of-life, right? This means no more updates of any type, even security updates. You can actually upgrade your F18 machine to F19, and F19 to F20, using the "fedup" package (I haven't tried using fedup to go directly from F18 to F20, but I suppose you could look into it). *A lot* has changed in virtualization in the last year, and as a bonus, you'll be covered for security fixes for another year. Is there a place where I can follow updates and see PCI pass-through mature so I'll know when next to try? Well, you could try the qemu-devel mailing list, but it's pretty high traffic, and very few of the messages would be on this particular topic. That *is* the place where any discussion would take place, though. Thank you, again, for your help! BTW, it's best to keep all messages on the list rather than private replies. That way someone else with better information may reply (and people very often get busy and disappear for several days/weeks at a time, so it's better to not rely on a response from a single person)

1 0

[libvirt-users] Newbie question about network setup
by hubert depesz lubaczewski 23 Jan '14

23 Jan '14

Hi, I've read some docs, and have some ideas, but before I'll go any further, I'd like to get confirmation if I'm understanding it right. Let's assume that on my host I want to have 5 different guests, but they shouldn't be able to communicate with each other. Is the solution to it addition of 5 separate "networks" in libvirt, and then connecting each guest to its own "network"? Looks sensible, but perhaps I'm overlooking something. Best regards, depesz -- The best thing about modern society is how easy it is to avoid contact with it. http://depesz.com/

3 4

[libvirt-users] Using Java bindings to event callback
by Howie 23 Jan '14

23 Jan '14

Hi My test environment : CentOS 6.3 6.4 Ubuntu 13.10 For CentOS 6.4 libvirt-java-0.4.9-1.el6.noarch libvirt-python-0.10.2-29.el6.x86_64 libvirt-client-0.10.2-29.el6.x86_64 libvirt-0.10.2-29.el6.x86_64 I am try to use java bindings to event callback. int register = conn.domainEventRegisterAny(null, 0, cb); But always get the following error message: libvirt: Remote Driver error : adding cb to list exception caught:org.libvirt.LibvirtException: adding cb to list level:VIR_ERR_ERROR code:VIR_ERR_RPC domain:VIR_FROM_REMOTE hasConn:false hasDom:false hasNet:false message:adding cb to list str1:%s str2:adding cb to list str3:null int1:-1 int2:-1 By the way I also trace the mail list *[libvirt] [PATCH] Java bindings for domain events* (2008 Nov 07) *[libvirt] [PATCH 1/2] Java bindings for domain events**[libvirt] [PATCH 2/2] Java bindings for domain events* (2008 Nov 18) --> Reject patch*Re: [libvirt] [PATCH 1/2] Java bindings for domain events* (2008 Dec) —>No Result*[libvirt-users] Using Java bindings to event callback * (2010 Jul) —>No Result *[libvirt] [PATCH 0/2] Libvirt-java event handling (2011Jul)* —> I think most drivers don't support that. We have a custom driver for our hypervisor and it works. *[libvirt] [libvirt-java] [PATCH 00/12] event support* (2013 Jan) —> *Re: [libvirt] [libvirt-java] [PATCH 00/12] event support (2013 Mar)* --> No Result Any suggestions? Thanks, Howie

2 1

[libvirt-users] running LXC hello world example
by Jacob Everist 23 Jan '14

23 Jan '14

Hello, I am having difficulty getting any sort of LXC container running. I am trying to use the following tutorial to run the hello world example: https://www.berrange.com/posts/2011/09/27/getting-started-with-lxc-using-li… Here are the results of my running the tutorial: [root@terraria ~]# virsh list Id Name State ---------------------------------------------------- [root@terraria ~]# virsh uri lxc:/// [root@terraria ~]# cat helloworld.xml <domain type='lxc'> <name>helloworld</name> <memory>102400</memory> <os> <type>exe</type> <init>/bin/sh</init> </os> <devices> <console type='pty'/> </devices> </domain> [root@terraria ~]# virsh define helloworld.xml Domain helloworld defined from helloworld.xml [root@terraria ~]# virsh start helloworld error: Failed to start domain helloworld error: internal error guest failed to start: PATH=/bin:/sbin TERM=linux container=lxc-libvirt container_uuid=791640de-95a9-082c-7292-c55106bcdca9 LIBVIRT_LXC_UUID=791640de-95a9-082c-7292-c55106bcdca9 LIBVIRT_LXC_NAME=helloworld /bin/sh error receiving signal from container: Input/output error --- As you can see, I am getting an error. How do I go about diagnosing this error? This is a fresh install so the only thing I have been using this machine for is for LXC/libvirt testing. -- Jacob Everist cell: 310-425-9732 email: jacob.everist(a)gmail.com

3 4

[libvirt-users] LXC configuration for Systemd in the user namespace.
by Jan Olszak 23 Jan '14

23 Jan '14

Hi there! Does anyone have a config file for libvirt-LXC, that makes it possible to: 1. Use all namespaces (user namespace in particular) 2. Run systemd inside a container. Thanks! Jan

3 2

[libvirt-users] If it's possible for a third-party PCIe card to be shared by multiple containers
by WANG Cheng D 23 Jan '14

23 Jan '14

Dear all, I have a thirty-party PCIe card in my host which can work properly in native mode. I wonder if this card can be shared by multiple containers. As far as the network interface is concerned, too many efforts have been made for it. Two dedicated cgroup resource schedulers/subsystem(net_cls, net_prio) have been provided at the kernel level, and libvirt has also done a lot of work on virtual networking to enable network interface sharing between containers. As it's difficult for me to implement all these things that have been done for network interface, I should find other way to enable sharing of this card. Do you have any idea? Any comments will be high appreciated. Cheng Wang

2 6

[libvirt-users] How to change virtfs/9p/v9fs umask
by Javi Legido 22 Jan '14

22 Jan '14

Hi there. My question is regarding virtfs/9p/v9fs [1], not sure what's the appropiate name :) Basically I have a KVM + libvirt server sharing a directory with a guest in mapped mode. It works fine, but the only issue is with the file permissions of the files created by the guest inside the host: -They are 0700 for dirs and 0400 for files -The files belongs to the same user that runs the "qemu-system-x86_64" process, which is "libvirt-qemu" Questions: 1. There's a way to change the umask of this user (I'm almost sure that I already tried this and it didn't worked) or to change any setting to force the permissions to be wider? 2. It's acceptable to run the "qemu-system-x86_64" as root, and switch to "passthrough" mode? Below some details of my environment. ==== Host ==== $ uname -r 3.12-1-amd64 $ cat /etc/issue Debian GNU/Linux jessie/sid \n \l $ sudo dpkg -l | grep libvirt ii libvirt-bin 1.2.0-2 amd64 programs for the libvirt library ii libvirt0 1.2.0-2 amd64 library for interfacing with different virtualization systems ii python-libvirt 1.2.0-2 amd64 libvirt Python bindings $ ps ax | grep vm_name 23307 ? Sl 0:40 qemu-system-x86_64 -enable-kvm -name vm_name -S -machine pc-1.1,accel=kvm,usb=off -cpu core2duo,+lahf_lm,+pdcm,+xtpr,+cx16,+tm2,+est,+smx,+vmx,+ds_cpl,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds -m 1024 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 2387f160-ffa2-3463-1aa3-771594779df3 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vm_name.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/dev/vg/lv_vm_name,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -fsdev local,security_model=mapped,id=fsdev-fs0,path=/srv/share -device virtio-9p-pci,id=fs0,fsdev=fsdev-fs0,mount_tag=virtfs_share,bus=pci.0,addr=0x3 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:68:90:d8,bus=pci.0,addr=0x4 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device usb-tablet,id=input0 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x7 Guest XML snippet: <filesystem type='mount' accessmode='mapped'> <source dir='/srv/share/> <target dir='virtfs_share'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </filesystem> Thanks. Javier [1] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/plain/Docume…

1 0

[libvirt-users] PCI Passthrough
by The PowerTool 21 Jan '14

21 Jan '14

I'm trying to pass-through my VGA card to a guest session. I found: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM - which is very frustrating because there's no date on the documentation. I suspect it's old. It does clearly say that you must have VT-d support for pci pass-through. It then goes on to say "Some work towards allowing this ["software pass-through"] were done, but the code never made it into KVM". If this is old is there now support for PCI pass-through on hardware that doesn't support VT-d? I have a HP p7-1456c which has: Intel Core i5-3330 Processor (VT-x=yes, VT-d=yes) http://ark.intel.com/products/65509/Intel-Core-i5-3330-Processor-6M-Cache-u… on a MB: H-Joshua-H61-UATX (with specs that say *nothing* about virtualization) http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03135925#N… and the H-Joshua-H61-UATX uses the Intel H61 Express Chipset (VT-d=No) http://ark.intel.com/products/52806/Intel-BD82H61-PCH?q=intel%20h61%20expre… On the KVM how to assign devices page it provides a way to verify IOMMU support on Intel: ]# dmesg | grep -e DMAR -e IOMMU [ 0.000000] ACPI: DMAR 00000000d8d29460 000B0 (v01 HPQOEM SLIC-CPC 00000001 INTL 00000001) [ 0.023074] dmar: IOMMU 0: reg_base_addr fed90000 ver 1:0 cap c0000020e60262 ecap f0101a [ 0.023078] dmar: IOMMU 1: reg_base_addr fed91000 ver 1:0 cap c9008020660262 ecap f0105a [ 0.023151] IOAPIC id 2 under DRHD base 0xfed91000 IOMMU 1 Does this mean I do have VT-d/IOMMU support??? I attempted to follow the basic instructions to pass through my VGA card: ]$ lspci -nn | grep VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) Then added to my domain definition: <hostdev mode='subsystem' type='pci' managed='yes'> <source> <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> With that added code I consistently get "Connection to guest failed" messages and the guest fails to start. /var/log/libvirt/qemu is empty. No log. So my 1st question is can I do this given my hardware? If the answer is "yes" then this is where I'm stuck. Additionally, I tried: ]$ virsh nodedev-detach pci_0000_00_02_0 error: Failed to detach device pci_0000_00_02_0 error: Failed to add PCI device ID '8086 0152' to pci-stub: Permission denied My thinking was simply to verify if I could manually detach the device. I couldn't find a reference searching for this error. Any help would be greatly appreciated! Thank you!

2 1

[libvirt-users] Will virsh command setvcpus/vcpupin be supported by lxc driver in the future?
by WANG Cheng D 21 Jan '14

21 Jan '14

Dear member of libvirt team, I hope the lxc could be dynamically reconfigured, such as the number of vcpu or vcpu pinning. According to http://libvirt.org/hvsupport.html , at present, setvcpus(virDomainSetVcpus) and vcpupin (virDomainGetVcpuPinInfo) are not supported by lxc driver. I wonder if these commands will be supported by libvirt in the future? Best wishes, Cheng Wang

1 0

[libvirt-users] Yet another disk I/O performance issue
by Matteo Lanati 20 Jan '14

20 Jan '14

Hi all, I'm running a VM using libvirt+KVM and I have a disk performance issue. The host is the following: 4 cores Intel Xeon 5140(a)2.33 GHz, 16 GB of RAM, SATA HDD, OS Debian Wheezy, libvirt 0.9.12-11, QEMU-KVM 1.1.2+dfsg-2. The guest: 1 CPU, 2 GB RAM running Debian 7.0, image in compressed qcow2 format. When I try do run "dd if=/dev/zero of=io.test bs=32768k count=40" I get around 500 MB/s on bare metal, while only around 30 MB/s inside the VM. I'm trying to get something more out of the virtualization layer, I hope that there's room for improvement. I'm using virtio, I aready set cache='none' and io='native' in the domain definition. Both host and guest are using deadline as I/O scheduler. The VM uses an ext4 filesystem, while the image is saved on an ext3 disk. I mounted the host and guest filesystems specifying nodiratime and noatime options. Even if I convert the image to raw format nothing changes. I didn't mess with iotune nor blockio. Is there something that I overlooked or any other suggestion? Thanks in advance for your help. Matteo -- A refund for defective software might be nice, except it would bankrupt the entire software industry in the first year. Andrew S. Tanenbaum, Computer Networks, 2003, Introduction, page 14 Linux registered user #463400

3 3

[libvirt-users] Retry reboots in xmls files for libvirt
by Fernando Porro 20 Jan '14

20 Jan '14

Hi, I have a virtual machine defined by xml that start from pxe (network boot), my problem is that sometimes the dhcp server is not ready when the virtual machine try to boot. I need that the virtual machine keep asking for dhcp (network reboot) many times, until dhcp is ready and can start the virtual machine with a valid ip. How can I configure that in the xml file? BR //Fernando

2 3

[libvirt-users] Should domain be undefined after migration, or not?
by Brian Candler 20 Jan '14

20 Jan '14

I have been running a lab using libvirt under Debian Wheezy (libvirt 0.9.12.3-1, qemu-kvm 1.1.2+dfsg-6, virt-manager 0.9.1-4). There are a number of machines as front-end servers and an nbd shared storage backend. When I live-migrate a domain from one machine to another, normally I observe that afterwards the domain remains on the source host (but in "shutdown" state), as well as on the target host (in "running" state). But occasionally I have observed the domain being removed from the source host. The trouble with the domain remaining on the source host is that it is all too easy to double-click on the shutdown domain in virt-manager and start it there accidentally, in addition to the copy on the target host - resulting in disaster. (I know this can be prevented using the sanlock plugin) Furthermore, there could be stale copies of the XML lying around on some machines where the domain had been running at some point in the past. My question is, what is the expected behaviour? Is not removing the domain definition from the source host a bug? Has this been changed in a newer version of libvirt? Thanks, Brian.

3 3

[libvirt-users] jumbo frame
by Anton Gorlov 20 Jan '14

20 Jan '14

I would like to use jumbo frame for local interfaces, but I am not sure in which order to set it up. Should it be set on the physical interface first, then on the bridge and on the guest, or in another way? On some servers there are configurations with vlan on the bridge

2 1

[libvirt-users] How to configure MacVtap passthrough mode to SR-IOV VF?
by opendaylight 20 Jan '14

20 Jan '14

Hi guys. These days I'm doing research on SR-IOV & Live migration. As we all know there is big problem that SR-IOV & Live migration can not exist at the same time. I heard that KVM + SRIOV + MacVtap can solve this problem. So I want to try. My environment: Host: Dell R610, OS: RHEL 6.4 ( kernel 2.6.32) NIC: intel 82599 I follow a document from intel guy, it said that I should write xml like below: ============================ <network> <name>macvtap_passthrough’</name> <forward mode=’passthrough> <interface dev=’vf0’ /> <interface dev=’vf1’ /> .. .. </forward> </network> ============================ I guess here the vf0 & vf1 should be the VFs of Intel 82599. What make me confused is that we know we can not see the vf 0 & vf 1 directly from the host server with "ifconfig", that is to say, vf 0 & vf1 are not a real physical interface. I try #: virsh net-define macvtap_passthrough.xml #: virsh net-start macvtap_passthrough When I try to configure macvtap_passthrough for a VNIC of a VM, the virt-manager told : "Can't get vf 0, no such a device". When I try from virt-manager: add hardware--->network--->host device (macvtap_passthrough:pass_through network), I got error like : "Error adding device: xmlParseDoc() failed". I guess I can not write like this " <interface dev=’vf0’ />" in the xml. I try to change as below, but the result is same. ============================ <network> <name>macvtap_passthrough’</name> <forward mode=’passthrough> <pf dev=’p2p1’ /> // p2p1 is intel sriov physical nic </forward> </network> ============================ I don't know how to write correctly. Please help me. You can refer to intel document as below. Many thanks. ==========document from intel======================== Linux/KVM VM Live Migration (SRIOV And MacVtap) By Waseem Ahmad (waseem.ahmad(a)intel.com In this scenario we are using 3 machines:  Server 1: DNS/NFS – nfs.vtt.priv  Server 2: Hv1  Server3: Hv2 HV1 and HV2 are Linux/KVM machines. We will get to them in a minute however we first must address kvm and nfs. NFS:  Create a storage area, where both HV1, and HV2 can access it. There are several methods available for this (FCOE/ISCSI/NFS). For this write-up use nfs. Configure NFS:  Create a directory on nfs.vtt.priv where you want your storage to be. In this case used /home/vmstorage  Edit /etc/exports and add the following /home/vmstorage 172.0.0.0/1(rw,no_root_squash,sync)  Now to /etc/sysconfig/nfs Uncomment RPCNFSDARGS=”-N 4” This will disable nfs v4. If you don’t do this you will have issues with not being able to access the share from within VirtManager.  Add all three machines ip addresses to each machines /hosts file. MIGRATION WILL NOT WORK WITHOUT FULLY QUALIFIED DOMAIN NAMES. KVM: On both HV1, and HV2 servers:  Edit /etc/selinux/config SELINUX=disabled  Edit /etc/libvirt/qemu.conf Change security_driver=none  On HV1 and HV2 start Virtual Machine Manager  Double click on localhost(QEMU)  Then click on the storage tab at the top of the window that pops up  Down in the left hand corner is a box with a + sign in it, click on that. A new window will appear entitled Add a New Storage Pool  In the name box type vmstorage, then click on the type box and select netfs: Network Exported Directory, now click next.  You will see the last step of the network Storage Pool Dialog. The first option is the target path. This is the path where we will mount our storage on the local server. I have chosen to leave this alone.  The next option is format, leave this set on auto: Host name: nfs.vtt.priv Source path: /home/vmstorage  Click on finish  Repeat the above steps on HV2 server Create vms  On HV1 server go back to the connection details screen, (this is the one that showed up when you double clicked on localhost (qemu), and click on the storage tab again.  Click on vmstorage then click on new volume at the bottom.  A new dialog will appear entitled add a storage volume.  In the Name box type vm1  In the Max Capacity box type 20000  And do the same in the allocation box then click finish.  Now you can close the connection details box by click on the x in the corner.  Now click on the terminal in the corner, right underneath file, and type the name of our vm in the box that is entitled Name, vm1 choose how your installation media, probably local install media, and click forward. Click on use cdrom or dvd, and place a rh6.2 dvd in the dvd player on HV1. Select Linux, for the OS type, and Red Hat Enterprise Linux 6 for the version. Memory I chose to leave this at its default of 1024, and assigned 1 cpu to the guest. Click forward, select “select managed or other existing storage” and click the browse button. Click on vmstoarge, and select vm1.img then click forward. Then click on finish.  We will configure network after we make sure migration between the two servers works properly.  Now go ahead and install the operating system as you would normally. Create networks Create a file that looks like the following < there is no support for adding a macvtap interface from the gui as of yet, this is the only manual step in the process. Create a file named macvtap_passthrough.xml with the following contents. <network> <name>macvtap_passthrough’</name> <forward mode=’passthrough> <interface dev=’vf0’ /> <interface dev=’vf1’ /> .. .. </forward> </network> <network> <name>’macvtap_bridge’</name> <forward mode=’bridge’> <interface dev=’p3p1’/> </forward> </network> Save it and run the following commands:  virsh net-define macvtap_passthrough.xml  virsh net-start macvtap_passthrough Make sure all of your virtual interfaces that you used in the xml file are up. for i in $(ifconfig –a | awk ‘/eth/ {print $1}’); do ifconfig $i up; done Then double click on your vm and click on the big blue i On the next screen click on add hardware, then on network, then select Virtual network “macvtap_passthrough” Then click on finish. Start your vm and make sure that the macvtap was created on the host by doing ip link | grep ‘macvtap’ In the vm configure the ip information for the virtio adapter. In the virtual machine manager click on file, add connection. Then check the connect to remote host fill in the username and hostname, then click on connect Right click on your VM and select Migrate, select the host you want to migrate the machine to, then click on advanced options, check the address box, and type the ip address of the machine you want to migrate to, and click the migrate button.

2 1

[libvirt-users] How to update filterref of a vm on the fly?
by Gao Yongwei 17 Jan '14

17 Jan '14

Hello, I defined a vm with filterref like: <filterref filter='clean-traffic'> <parameter name='IP' value='192.168.1.161'/> </filterref> and now I need to add another IP parameter for this vm,is there any way to achieve this? thanks.

4 4

[libvirt-users] blockcopy, userspace iSCSI support?
by Scott Sullivan 17 Jan '14

17 Jan '14

Right now, on a virsh blockcopy, I know you can do something like this: # Connect DEST target iscsiadm -m node -p ${DESTINATION}:3260 -T ${VOLNAME} -o new iscsiadm -m node -p ${DESTINATION}:3260 -T ${VOLNAME} --login # Copy to connected iSCSI target virsh blockcopy ${DOMAIN} vda /dev/sdc --raw --bandwidth 300 However I have libiscsi compiled into my QEMU. So I can do this with the monitor directly (and avoid the need to call out to external iscsiadm): virsh qemu-monitor-command ${DOMAIN} '{"execute":"drive-mirror", "arguments": { "device": "drive-virtio-disk0", "target": "iscsi://${TARGET_IP}:3260/${DOMAIN}/1", "mode": "existing", "sync": "full", "on-source-error": "stop", "on-target-error": "stop" } }' Is there a way to use the libiscsi compiled into my QEMU with virsh blockcopy command? I haven't been able to find any examples of using blockcopy with iSCSI compiled into QEMU.

1 0

[libvirt-users] Ceph RBD locking for libvirt-managed LXC (someday) live migrations
by Joshua Dotson 16 Jan '14

16 Jan '14

Hi, I'm trying to build an active/active virtualization cluster using a Ceph RBD as backing for each libvirt-managed LXC. I know live migration for LXC isn't yet possible, but I'd like to build my infrastructure as if it were. That is, I would like to be sure proper locking is in place for live migrations to someday take place. In other words, I'm building things as if I were using KVM and live migration via libvirt. I've been looking at corosync, pacemaker, virtlock, sanlock, gfs2, ocfs2, glusterfs, cephfs, ceph RBD and other solutions. I admit that I'm quite confused. If oVirt, with its embedded GlusterFS and its planned self-hosted engine option, supported LXC, I'd use that. However the stars have not yet aligned for that. It seems that the most elegant and scalable approach may be to utilize Ceph's RBD with its native locking mechanism plus corosync and pacemaker for fencing, for a number of reasons out of scope for this email. *My question now is in regards to proper locking. Please see the following links. The libvirt hook looks good, but is there any expectation that this arrangement will become a patch to libvirt itself, as is suggested by the second link?* http://www.wogri.at/en/linux/ceph-libvirt-locking/ http://lists.ceph.com/pipermail/ceph-users-ceph.com/2013-August/003887.html Can anyone guide me on how to theoretically build a very "lock" safe 5-node active-active KVM cluster atop Ceph RBD? Must I use sanlock with its NFS or GFS2 with its performance bottlenecks? Does your answer work for LXC (sans the current state of live migration)? Thanks, Joshua -- Joshua Dotson Founder, Wrale Ltd

2 2

[libvirt-users] Live migration finish threshold
by Joaquim Barrera 16 Jan '14

16 Jan '14

Hello everyone, Can somebody point where I can find the code where libvirt makes the decision to complete a live migration? I mean, at some point syncronising the VM state, it has to decide that the delta left to be migrate is low enough to achieve downtime 0, so libvirt finishes the migration. This "low enough" must be defined somewhere in the code, but I am unable to find it. Thank you very much.

2 1

[libvirt-users] vnc port/listen address ignored when setting machine?
by hubert depesz lubaczewski 16 Jan '14

16 Jan '14

Hi, First of all, I hope it's not a big problem - I'm running on Debian, not Redhat. To my problem: I'm starting to learn virtualization, libvirt, and decided to create some test machine. I did it with: virt-install --name debian-test \ --os-type=linux \ --os-variant=debianwheezy \ --cdrom /media/media/software/iso/debian-testing-amd64-netinst-2014-01-16.iso \ --graphics vnc,listen=0.0.0.0,port=20001 \ --disk pool=default,format=raw,size=20 \ --ram 2048 \ --vcpus=2 \ --network bridge=virbr0 \ --hvm \ --virt-type=kvm Machine starts, but domdisplay shows: =# virsh domdisplay debian-test vnc://localhost:14101 When I tried setting it with --grpahics=vnc,...port=40001, I got it to listen on port 34101 (which is weird anyway, but at least I can change it). But whatever I do - I can't make it to listen on 0.0.0.0. I know I can use ssh port forwarding to get to this VNC, but I would very much prefer to be able to set VNC listen to 0.0.0.0 for at least some of my test domains. What am I doing wrong? Best regards, depesz -- The best thing about modern society is how easy it is to avoid contact with it. http://depesz.com/

2 3

[libvirt-users] Does libvirt lxc driver support "cpuset" attribute?
by WANG Cheng D 16 Jan '14

16 Jan '14

Dear all I allocate only one vcpu for the container by the following statement, that is, I want to pin the vcpu to physical core "2". <vcpu placement='static' cpuset="2" >1</vcpu> My host has 4 physical cores. Before test, all the 4 cores are idle. After I run 4 processes in the container, I found all the 4 cores in the host are 100% used. That is, the container is pinned to all the available physical CPUs. This is not what I want. My libvirt version is 1.0.3. Although "vcpupin" element also can be used to pin vcpu, according to http://libvirt.org/formatdomain.html , "vcpupin" element is not supported by lxc driver. I wonder if it is the older version of libvirt that causes the problem? Thank you in advance. Cheng Wang

2 2

[libvirt-users] Fake Network Interface
by Andrew Martin 15 Jan '14

15 Jan '14

Hello, Is there a supported method for creating a fake network interface in a VM's configuration file? I was using the below construct, however it is no longer working for me in recent versions of libvirt (libvirt 1.0.2 with qemu-kvm 1.4.0). Is there a different, preferred method for creating a fake virtual interface on the guest which does not exist on the host? <interface type='network'> <mac address='aa:aa:aa:aa:aa:aa'/> <source network='fake'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> Thanks, Andrew

2 3

[libvirt-users] virDBusCallMethod:1173 : Launch helper exited with unknown return code
by Karoline Haus 15 Jan '14

15 Jan '14

Good morning, I'm using libvirtd on Gentoo. This is libvirt version: 1.1.3.1 I have trouble starting a VM using virsh start $vm. I do this as root, because as non-root user it did not work at all (especially it failed attaching to the networks). So, when I run the command (with sudo), I get the following error in libvirtd.log: 2014-01-15 07:51:00.423+0000: 16158: warning : qemuDomainObjTaint:1573 : Domain id=5 name='vader' uuid=f5b8c05b-9c7a-3211-49b9-2bd635f7e2aa is tainted: high-privileges 2014-01-15 07:51:00.428+0000: 16158: error : virDBusCallMethod:1173 : Launch helper exited with unknown return code 1 At the same time I get an error in /var/log/messages which seems related: Jan 15 07:51:00 dbus[15845]: [system] Activating service name='org.freedesktop.machine1' (using servicehelper) Jan 15 07:51:00 dbus[15845]: [system] Activated service 'org.freedesktop.machine1' failed: Launch helper exited with unknown return code 1 Anyone ever seen this issue? I have no idea where to look for errors because the message don't really tell me much. I have tried to execute the qemu-kvm command on the command line directly and that worked immediately. So the problem must be in libvirt. Thanks for any pointers.

3 3

[libvirt-users] Best practice for custom iptables rules
by ZeroUno 15 Jan '14

15 Jan '14

Hi, I'm using libvirt to manage some VMs on a CentOS host, and I need some custom iptables rules to always be in place for some communications to happen, e.g. between the VMs and the outside world in both directions. Some of these rules need to be at the top of the iptables chain, otherwise the default rules added by libvirt would block the communications I need. So I cannot just add the rules in /etc/sysconfig/iptables, because libvirt adds its own rules _before_ the rules contained in this config file. I was looking at filters, but maybe not every rule can be made into a filter? Specifically, I need a rule for the POSTROUTING chain in the "nat" table. Can it be added through filters? Also, regarding the "iptables restart problem" described in the last paragraph at <http://libvirt.org/firewall.html>, is there really no acceptable way to make libvirt add its rules back automatically upon iptables/network restart? Thanks for any info. Marco -- 01

4 12

[libvirt-users] how to detect if qemu supports live disk snapshot
by Francesco Romani 15 Jan '14

15 Jan '14

Hi everyone, Using the QEMU hypervisor, when a live disk snapshot is requested through libvirt, the request can fail if the underyling qemu binary lacks the snapshotting support. In python, we have something like libvirtError: Operation not supported: live disk snapshot not supported with this QEMU binary I'd like to detect ahead of time if the underlying QEMU can or cannot do snapshotting, and disable right from the start the snapshotting support in my application, avoiding to throw errors to the user. After reading from the docs, it seems that libvirt doesn't reports yet this information about the hypervisor in the capabilities XML: http://libvirt.org/formatcaps.html a quick test against libvirt 1.1.3 (qemu 1.6.1) on Fedora 20 seems to confirm (see XML dump below[1]). So, if I'm not mistaken, looks like the only way to test for the support in QEMU is to actually request a snapshot and see what happens. Is this right? If this is correct, I would like to craft and propose a patch to libvirt to export this information, maybe into a form of some kind of warning list/blacklist: disk snapshotting it is supposed to be available, but this particular QEMU doesn't support it. What would be the best form to export such information? the options I see are * enhance the capabilities XML * add a new API: something like (very rough first draft) int virDomainIsSnapshotSupported(virConnectPtr conn, unsigned int flags); Thoughts? Any suggestion is welcome. Best regards, +++ [1] # virsh -c qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # capabilities <capabilities> <host> <uuid>01c4dc83-b652-cb11-9e6d-f3bf03b35d26</uuid> <cpu> <arch>x86_64</arch> <model>SandyBridge</model> <vendor>Intel</vendor> <topology sockets='1' cores='2' threads='2'/> <feature name='erms'/> <feature name='smep'/> <feature name='fsgsbase'/> <feature name='rdrand'/> <feature name='f16c'/> <feature name='osxsave'/> <feature name='pcid'/> <feature name='pdcm'/> <feature name='xtpr'/> <feature name='tm2'/> <feature name='est'/> <feature name='smx'/> <feature name='vmx'/> <feature name='ds_cpl'/> <feature name='monitor'/> <feature name='dtes64'/> <feature name='pbe'/> <feature name='tm'/> <feature name='ht'/> <feature name='ss'/> <feature name='acpi'/> <feature name='ds'/> <feature name='vme'/> </cpu> <power_management> <suspend_mem/> <suspend_disk/> <suspend_hybrid/> </power_management> <migration_features> <live/> <uri_transports> <uri_transport>tcp</uri_transport> </uri_transports> </migration_features> <topology> <cells num='1'> <cell id='0'> <memory unit='KiB'>7871524</memory> <cpus num='4'> <cpu id='0' socket_id='0' core_id='0' siblings='0-1'/> <cpu id='1' socket_id='0' core_id='0' siblings='0-1'/> <cpu id='2' socket_id='0' core_id='1' siblings='2-3'/> <cpu id='3' socket_id='0' core_id='1' siblings='2-3'/> </cpus> </cell> </cells> </topology> <secmodel> <model>selinux</model> <doi>0</doi> </secmodel> <secmodel> <model>dac</model> <doi>0</doi> </secmodel> </host> <guest> <os_type>hvm</os_type> <arch name='i686'> <wordsize>32</wordsize> <emulator>/usr/bin/qemu-system-i386</emulator> <machine canonical='pc-i440fx-1.6' maxCpus='255'>pc</machine> <machine maxCpus='255'>pc-q35-1.4</machine> <machine maxCpus='255'>pc-q35-1.5</machine> <machine canonical='pc-q35-1.6' maxCpus='255'>q35</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255'>pc-0.10</machine> <machine maxCpus='255'>pc-0.11</machine> <machine maxCpus='255'>pc-0.12</machine> <machine maxCpus='255'>pc-0.13</machine> <machine maxCpus='255'>pc-0.14</machine> <machine maxCpus='255'>pc-0.15</machine> <machine maxCpus='255'>pc-1.0</machine> <machine maxCpus='255'>pc-1.1</machine> <machine maxCpus='255'>pc-1.2</machine> <machine maxCpus='255'>pc-1.3</machine> <machine maxCpus='255'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-i440fx-1.5</machine> <machine maxCpus='1'>none</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-kvm</emulator> <machine canonical='pc-i440fx-1.6' maxCpus='255'>pc</machine> <machine maxCpus='255'>pc-q35-1.4</machine> <machine maxCpus='255'>pc-q35-1.5</machine> <machine canonical='pc-q35-1.6' maxCpus='255'>q35</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255'>pc-0.10</machine> <machine maxCpus='255'>pc-0.11</machine> <machine maxCpus='255'>pc-0.12</machine> <machine maxCpus='255'>pc-0.13</machine> <machine maxCpus='255'>pc-0.14</machine> <machine maxCpus='255'>pc-0.15</machine> <machine maxCpus='255'>pc-1.0</machine> <machine maxCpus='255'>pc-1.1</machine> <machine maxCpus='255'>pc-1.2</machine> <machine maxCpus='255'>pc-1.3</machine> <machine maxCpus='255'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-i440fx-1.5</machine> <machine maxCpus='1'>none</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> <pae/> <nonpae/> </features> </guest> <guest> <os_type>hvm</os_type> <arch name='x86_64'> <wordsize>64</wordsize> <emulator>/usr/bin/qemu-system-x86_64</emulator> <machine canonical='pc-i440fx-1.6' maxCpus='255'>pc</machine> <machine maxCpus='255'>pc-q35-1.4</machine> <machine maxCpus='255'>pc-q35-1.5</machine> <machine canonical='pc-q35-1.6' maxCpus='255'>q35</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255'>pc-0.10</machine> <machine maxCpus='255'>pc-0.11</machine> <machine maxCpus='255'>pc-0.12</machine> <machine maxCpus='255'>pc-0.13</machine> <machine maxCpus='255'>pc-0.14</machine> <machine maxCpus='255'>pc-0.15</machine> <machine maxCpus='255'>pc-1.0</machine> <machine maxCpus='255'>pc-1.1</machine> <machine maxCpus='255'>pc-1.2</machine> <machine maxCpus='255'>pc-1.3</machine> <machine maxCpus='255'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-i440fx-1.5</machine> <machine maxCpus='1'>none</machine> <domain type='qemu'> </domain> <domain type='kvm'> <emulator>/usr/bin/qemu-kvm</emulator> <machine canonical='pc-i440fx-1.6' maxCpus='255'>pc</machine> <machine maxCpus='255'>pc-q35-1.4</machine> <machine maxCpus='255'>pc-q35-1.5</machine> <machine canonical='pc-q35-1.6' maxCpus='255'>q35</machine> <machine maxCpus='1'>isapc</machine> <machine maxCpus='255'>pc-0.10</machine> <machine maxCpus='255'>pc-0.11</machine> <machine maxCpus='255'>pc-0.12</machine> <machine maxCpus='255'>pc-0.13</machine> <machine maxCpus='255'>pc-0.14</machine> <machine maxCpus='255'>pc-0.15</machine> <machine maxCpus='255'>pc-1.0</machine> <machine maxCpus='255'>pc-1.1</machine> <machine maxCpus='255'>pc-1.2</machine> <machine maxCpus='255'>pc-1.3</machine> <machine maxCpus='255'>pc-i440fx-1.4</machine> <machine maxCpus='255'>pc-i440fx-1.5</machine> <machine maxCpus='1'>none</machine> </domain> </arch> <features> <cpuselection/> <deviceboot/> <acpi default='on' toggle='yes'/> <apic default='on' toggle='no'/> </features> </guest> </capabilities> -- Francesco Romani

3 4

[libvirt-users] --persistent/--config confusion
by Dennis Jacobfeuerborn 15 Jan '14

15 Jan '14

Hi, I'm wondering how to attach a network device properly to a domain. According to the man page without "--config" a device created with "attach-device" will be added to the domain yet with "--config" it will only be added to the config and only be available after a restart of the guest. Is there no way to attach the device immediately *and* also make that change persistent? Regards, Dennis

2 2

[libvirt-users] Dedicated GDM session for a virt-manager virtual machine?
by Alex GS 15 Jan '14

15 Jan '14

Dear list, Something has been perplexing me lately. I have a bunch of Windows 7 virtual machines running on top of Fedora 20 in KVM using virt-manager. One of the big problems is that users who need the Windows VM's don't know how to user virt-manager and when they accidentally reboot a machine I have to manually setup the virt-manager session for them and make it full-screen. That means if I'm not physically there the users are unable to use the Windows sessions and cannot do their work. Is there a way to create a GDM desktop session that just launches a virtual machine via virsh and then logs directly into a full-screen virt-viewer instance of that virtual machine? Best, AGS

1 0

[libvirt-users] libvirt on armhf with selinux driver
by Ivan Gooten 14 Jan '14

14 Jan '14

hi, recently i've been busy with libvirt(d) v1.2.0 on armhf and i see, even if selinux sec driver is enabled on the configure stage, the driver is not finally created. these configure parameters are: --with-selinux --with-secdriver-selinux --with-selinux-mount=/sys/fs/selinux the /sys/fs/selinux is valid, selinux is running in permissive mode, got also libselinux DEV package installed, so no missing req. headers here. when trying to run libvirtd, i'm getting: error : virSecurityDriverLookup:78 : unsupported configuration: Security driver selinux not enabled error : lxcSecurityInit:1461 : Failed to initialise security drivers error : virStateInitialize:854 : Initialisation of LXC state driver failed: unsupported configuration: Security driver selinux not enabled error : daemonRunStateInit:909 : Driver state initialisation failed someone got any clue what may be causing this? thanks, ivan gooten

3 5

[libvirt-users] Migration: default value for maxdowntime? (QEMU/KVM)
by Scott Sullivan 10 Jan '14

10 Jan '14

I am wondering what the default value for migrate-setmaxdowntime is when using QEMU/KVM. http://builder.virt-tools.org/artifacts/libvirt-virshcmdref/html/sect-migra… Is the default the same as QEMU's default in this case? I was looking at libvirts source and it appears there is no default set within libvirt, unless I missed it. I do see qemuDomainMigrateSetMaxDowntime() directly enters the monitor to change the value when set with that command. Any insight/confirmation is appreciated.

1 0

[libvirt-users] migrate interrupted but cannot continue
by leocup 09 Jan '14

09 Jan '14

Hello, I have 2 hosts A and B,the settings of libvirtd are A: Compiled against library: libvirt 0.10.2 Using library: libvirt 0.10.2 Using API: QEMU 0.10.2 Running hypervisor: QEMU 0.12.1 B: Compiled against library: libvir 0.9.4 Using library: libvir 0.9.4 Using API: QEMU 0.9.4 Running hypervisor: QEMU 0.12.1 when I migrate a guest from A to B without storage,I used the command "virsh migrate --live --copy-storage-all --verbose vm qemu+ssh://kvm/system".The first time I succeed and I wantto to emulate the local network is down when I migrate,so I close the terminal (Xshell) when migrating, when I reconnect to the terminal ,use the migration command again,it failed.The libvirtd.log says: error : qemuMonitorIORead:514 : Unable to read from monitor: Connection reset by peer warning : qemuMonitorMigrateToFd:1941 : failed to close migration handle It seems that the migration process has not finished normally and so migration cannot go on. I want to know how to resolve it. thanks.

1 0

[libvirt-users] ANNOUNCE: ruby-libvirt 0.5.2
by Chris Lalancette 09 Jan '14

09 Jan '14

All, This is a release notification for ruby-libvirt 0.5.2. ruby-libvirt is a ruby wrapper around the libvirt API. The changelog between 0.5.1 and 0.5.2 is: * Fix to make sure we don't free more entries than retrieved (potential crash) Version 0.5.2 is available from http://libvirt.org/ruby: Tarball: http://libvirt.org/ruby/download/ruby-libvirt-0.5.2.tgz Gem: http://libvirt.org/ruby/download/ruby-libvirt-0.5.2.gem It is also available from rubygems.org; to get the latest version, run: $ gem install ruby-libvirt As usual, if you run into questions, problems, or bugs, please feel free to mail me (clalancette gmail com) and the libvirt mailing list. Thanks to Guido Günther for the patch to fix this problem.

1 0

[libvirt-users] Canceling a live migration via virsh? (QEMU/KVM)
by Scott Sullivan 08 Jan '14

08 Jan '14

I am using QEMU/KVM, using Live Migrations like this: virsh migrate --live ${name} qemu+ssh://${DESTINATION}/system My question, running this command makes it hang in the foreground. Is there a way for this to return immediately, so I can just poll for the migration status? Also, is there a way to _cancel_ a migration? I see the --timeout option, however if a given timeout is reached I would rather have the ability to cancel the migration than force the suspend. I do see there is a QEMU api migrate_cancel..eg: virsh qemu-monitor-command ${name} --pretty '{"execute":"migrate_cancel"}' Is that the only way to cancel a migration using libvirt?

2 2

[libvirt-users] Ownerships of VMs and Image files
by Christoph Pleger 07 Jan '14

07 Jan '14

Hello, I installed libvirt and qemu/kvm on a machine. I testet a little with those and found out that all users having an account on that machine can start every VM of every other user on the machine, in some conditions even directly access the image file on the real host. What I would like to have is that every user can only access the VMs and image files he or she created himself/herself, as long as he/she does not explicitly set other permissions. Is it possible to achieve that? Regards Christoph

2 1

[libvirt-users] How to start the linux container's network interface automatically
by WANG Cheng D 06 Jan '14

06 Jan '14

Dear all, I failed to start the linux container's network interface automatically. I have to start it manually each time after the container finishes booting. I know that in a native fedora, if we want the network interface to start automatically, we should edit "/etc/sysconfig/network-script/ifcfg-eth0 and add the string "ONBOOT=yes". My host is fedora 16. I used "yum --installroot=/root/fedoralxc --releasever=16 install -y openssh, bridge-utils" to setup the rootfs for my container (Laine thought that my fedora version is a little bit older, I wonder if the newer version fedora container can automatically start its network interface ) After rootfs installation, in the container's file system, there is no sub-directory named "network-scripts" in "/etc/sysconfig" . So, I created this directory manually and added a file named "ifcfg-eth0", but the container's network interface still cannot start automatically. I tried to add files ".bash_profile" and ".bashrc" in which I added the "ifconfig" in the shell script to try to configure eth0 automatically, but it still doesn't work. I wonder if there is a ".bashrc" for the root of a container? If there is, where should this file be located? Any comments will be highly appreciated. Cheng

1 0

[libvirt-users] How to start the container's network interface automatically
by WANG Cheng D 06 Jan '14

06 Jan '14

Dear all, I failed to start the container's network interface automatically. I have to start it manually each time after the container finishes booting. I know that in a native fedora, if we want the network interface to start automatically, we should edit "/etc/sysconfig/network-script/ifcfg-eth0 and add the string "ONBOOT=yes". My host is fedora. I used "yum --installroot=/root/fedoralxc --releasever=16 install -y openssh, bridge-utils" to setup the rootfs for my container After rootfs installation, in the container's file system, there is no sub-directory named "network-scripts" in "/etc/sysconfig" . So, I created this directory manually and added a file named "ifcfg-eth0", but the container's network interface still cannot start automatically. I tried to add files ".bash_profile" and ".bashrc" in which I added the "ifconfig" in the shell script to try to configure eth0 automatically, but it still doesn't work. I wonder if there is a ".bashrc" for the root of a container? If there is, where should this file be located? Any comments will be highly appreciated. Cheng

1 0

[libvirt-users] ANNOUNCE: Oz 0.12.0 release
by Chris Lalancette 03 Jan '14

03 Jan '14

All, I'm pleased to announce release 0.12.0 of Oz. Oz is a program for doing automated installation of guest operating systems with limited input from the user. Release 0.12.0 is a bugfix and feature release for Oz. Some of the highlights between Oz 0.11.0 and 0.12.0 are: * Fixes to concurrent oz-install invocations * Python 3 compatibility in the test suites * Support for Ubuntu 12.04.3 * Support for Mageia * Allow a MAC address to be passed in (instead of auto-generated) * Support for RHEL5.10 * Support for Ubuntu 13.10 * Use lxml instead of libxml2 for XML document processing (it has much better error messages) * Remove the unused "tunnels" functionality * Support FreeBSD 10.0 * Remove deprecated functions from the Guest class * Speed up guest customization on guests that support NetworkManager * Follow subprocess commands as they are executed (makes debugging easier) * Ensure that any paths from the user are absolute, otherwise things don't work properly * Add support for OpenSUSE 13.1 * Add support for Fedora 20 * Add support for RHEL-7 A tarball and zipfile of this release is available on the Github releases page: https://github.com/clalancette/oz/releases . Packages for Fedora-19, Fedora-20, and EPEL-6 have been built in Koji and will eventually make their way to stable. Instructions on how to get and use Oz are available at http://github.com/clalancette/oz/wiki . If you have questions or comments about Oz, please feel free to contact me at clalancette at gmail.com, or open up an issue on the github page: http://github.com/clalancette/oz/issues . Thanks to everyone who contributed to this release through bug reports, patches, and suggestions for improvement. Chris Lalancette

1 0

Re: [libvirt-users] [libvirt] [RFC] Implementing ftrace support for libvirt
by Mauricio Tavares 03 Jan '14

03 Jan '14

On Fri, Jan 3, 2014 at 6:46 AM, yuxh <yuxinghai(a)cn.fujitsu.com> wrote: > Hi all, > > Happy new year! > > The existing trace mechanism in libvirt is dtrace. Although the dtrace > can work, it's not work well enough. Every time we want get information > from the trace point we must write a systemtap script and run it > together with libvirt. > > That's really unpractical on some occasion, especially on production > server since the systemtap script can't be executed automatically. > And some problems may be not easy to reproduce, then it will cost a > lot of time to get the trace information again. > > So I think it is essential to add supporting for record the trace > information automatically in libvirt to satisfy the user's requirement. > That's why I'm currently implementing ftrace support in libvirt. > > How do you think about my idea? Any comment will be appreciated! > How hard/painless it would be to implement it? And, can you have both and then select which one to use? > Thanks, > Yu > > -- > libvir-list mailing list > libvir-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/libvir-list

1 0