- Users - libvirt List Archives

[libvirt-users] Best filesystem/nfs options for shared storage?
by Scott Baker 13 Dec '10

13 Dec '10

Is there a guide, or some suggestions for what filesystem to use for VM storage? I chose the standard ext3 on CentOS but I'm wondering if it makes more sense to look at ext4 or XFS for performance reasons? Does anyone tweak the ext3 journaling options for libvirt to speed things up? What about NFS export/mount options? What do your fstab mount lines look like? Is there a better rsize/wsize than the default? -- Scott Baker - Canby Telcom System Administrator - RHCE - 503.266.8253

1 0

[libvirt-users] libvirt printing to stderr
by Albert Hopkins 13 Dec '10

13 Dec '10

I'm writing an app and using the Python bindings for libvirt. Everything is fine but, in some cases I need to call lookupByName(). There are a lot of times when the name will not exist, I trap the exception, however I still get this message printed to stderr: libvir: QEMU error : Domain not found: no domain with matching name 'foo' Is there any way to turn this off? This is a command-line program so the extra output makes the interface confusing. I've tried re-assigning sys.stderr before calling lookupByName(), but that doesn't seem to have any affect. tia, -albert

3 4

[libvirt-users] LXC Live Migration possible?
by Dan Lüdtke 13 Dec '10

13 Dec '10

Hallo everyone, in March 2010 there was a discussion[1] about live migration of LXC Containers using libvirt. I was just wondering if there are any updates to this? regards, Dan Luedtke [1] http://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg00198.html -- https://www.danrl.de/ GPG Key ID: 0xF8504F3E

3 2

[libvirt-users] ANNOUNCE: ruby-libvirt bindings 0.3.0
by Chris Lalancette 13 Dec '10

13 Dec '10

All, I'm pleased to announce the release of 0.3.0 of the ruby-libvirt bindings. This release has a number of updates: * Implementation of Libvirt::open_auth, Libvirt::event_register_impl * Updated Connect class, implementing conn.compare_cpu, conn.baseline_cpu, conn.domain_event_register_any, conn.domain_event_deregister_any, conn.domain_event_register, conn.domain_event_deregister, and conn.create_domain_xml. * Updated Domain class, implementing dom.get_vcpus, dom.update_device, dom.scheduler_type, dom.scheduler_parameters, dom.scheduler_parameters=, dom.num_vcpus, dom.vcpus_flags=, and dom.qemu_monitor_command. * Updated Interface class, implementing interface.free * Many potential memory leaks have been fixed. * Many bugfixes. * Documentation update of many methods, including all of the lookup methods that were missing before. With the above list, almost all of the APIs up to and including libvirt 0.8.6 are covered. There are a few that I have not yet had time to implement; you can look at the list in the README file in the source tree to see which ones are missing. The tarballs and source RPMs are here: http://libvirt.org/ruby/download/ The git repository is here: http://libvirt.org/git/?p=ruby-libvirt.git;a=summary The documentation for all of the APIs are here: http://libvirt.org/ruby/api/index.html I've uploaded some examples on how to use the bindings: http://libvirt.org/ruby/documentation.html I've also pushed a new gem to rubygems.org; you should be able to use 'gem install ruby-libvirt' (if you haven't installed them before) or 'gem update ruby-libvirt' (if you have them installed already). If you have time, and are interested in the bindings, please give these new ones a whirl and let me know if they work for you. Note that release 0.3.0 is intended to be fully backwards compatible with release 0.2.0 and 0.1.0. If you find that they are not, or find any other problems with the ruby bindings, please report it to the libvirt development mailing list (and CC me) so that I can take a look at them. Thanks, -- Chris Lalancette

1 0

[libvirt-users] error: Failed to disconnect from the hypervisor, 1 leaked reference(s)
by Albert Hopkins 12 Dec '10

12 Dec '10

I've been getting this error ever since upgrading to libvirt 0.8.6. It happens when i use "virsh console <domain>" and then manually shut down from within the virtual serial console. Is anyone else experiencing this? -a

1 0

[libvirt-users] Create VMWare ESXi domain via virsh error(error: this function is not supported by the connection driver: virDomainCreateXML)
by mop amg 06 Dec '10

06 Dec '10

Hi, Dear Mr/Mrs. I have two questions ask for help: my virt-manager and libvirt version is : linux-vaan:~ # rpm -q libvirt libvirt-0.8.5-1.2.i586 linux-vaan:~ # uname -a Linux linux-vaan 2.6.34-12-desktop #1 SMP PREEMPT 2010-06-29 02:39:08 +0200 i686 i386 GNU/Linux linux-vaan:~ # rpm -q virt-manager virt-manager-0.8.5-3.1.i586 linux-vaan:~ # cat /etc/SuSE-release openSUSE 11.3 (i586) VERSION = 11.3 virsh # version Compiled against library: libvir 0.8.5 Using library: libvir 0.8.5 Using API: ESX 0.8.5 Running hypervisor: ESX 4.1.0 *question 1 : * When I try to create a vmware esxi domain from virsh like this : create --file /work/dom1.x there is a error message : error: Failed to create domain from /work/dom1.xml error: this function is not supported by the connection driver: virDomainCreateXML it seems dosen't support create esxi domain, but the http://libvirt.org/hvsupport.html show that is supported after ≥ 0.7.0 or create via virt-install linux-vaan:~ # virt-install --connect=esx:// root(a)192.168.8.162/?no_verify=1 -n rhel5 -r 512 --vcpus=1 --nodisks bridge=vmk0 --network bridge=vmk0 --pxe Enter root's password for 192.168.8.162: Starting install... ERROR this function is not supported by the connection driver: virDomainCreateXML how to fix it ? *dom1.xml* <domain type='vmware'> <name>dom1</name> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='i686'>hvm</type> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <disk type='file' device='disk'> <source file='[datastore1] rhel5/rhel5_2.vmdk'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' unit='0'/> </disk> <controller type='scsi' index='0' model='lsilogic'/> <interface type='bridge'> <mac address='00:0c:29:51:f1:1c'/> <source bridge='VM Network'/> </interface> </devices> </domain> *question 2:* vol-clone failed virsh # vol-clone --pool datastore1 rhel5/rhel5.vmdk rhel5/rhel5_2.vmdk error: Failed to clone vol from rhel5/rhel5.vmdk error: this function is not supported by the connection driver: virStorageVolCreateXMLFrom thanks for help! best regards!

2 1

[libvirt-users] How to set image format to 'qcow2'
by 姜晓东 05 Dec '10

05 Dec '10

Hi, all My xml 'dom1.xml' is as following: <domain type='kvm' id='1'> <name>kvm-xp</name> <description>xp kvm</description> <memory>524288</memory> <currentMemory>524288</currentMemory> <os> <type>hvm</type>  <boot dev="hd"/> </os> <devices> <disk type='file'> <source file='/home/eucalyptus/imgs/xp.img'/> <target dev='hda' bus='ide'/> </disk> <driver name='qemu' type='qcow2'/>   <graphics type='vnc' port='5904'/> </devices> </domain> In this xml file, I don't know how to set disk file format to 'qcow2'. When I create domain using this command: virsh create dom1.xml I cannot boot the image file. The log file /var/log/libvirt/qemu/kvm-xp.log is as following: LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.4.3 HOME=/root USER=root QEMU_AUDIO_DRV=none /usr/bin/kvm -S -M pc -m 512 -smp 1 -name kvm-xp -uuid a8cbae31-59a0-0bc5-4416-65ba63aa4231 -monitor unix:/var/lib/libvirt/qemu/kvm-xp.monitor,server,nowait -no-acpi -boot c -drive file=/home/eucalyptus/imgs/xp.img,if=ide,bus=0,unit=0,format=raw -net none -serial none -parallel none -usb -vnc 127.0.0.1:4 -vga cirrus -balloon virtio I don't know how to set format argument to 'qcow2' ---------------- Xiaodong Jiang jxd431(a)gmail.com

2 1

[libvirt-users] added second virtio-disk: disk order detected wrong
by Stefan G. Weichinger 03 Dec '10

03 Dec '10

Greets, I am unsure if it's a linux- or libvirt-issue: I added a 2nd virtio-disk to a kvm-based VM. The xml shows a correct "target": # first disk vda <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/r0/vm1_vda-clone.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> # second disk vdb <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/mnt/r0/www3_var.img'/> <target dev='vdb' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </disk> The VM contains Gentoo Linux, grub comes up fine, but then it flips the devices: The unpartitioned new disk is vda, therefore there is no root-fs etc ... I know my way to fix this via Live-CD or so, but I would really like to understand what happened! I'd like to keep vda as root etc. Could someone explain? libvirt-0.8.6 and qemu-kvm-0.13.0-r2 on a gentoo-host, btw. Thanks, Stefan

1 2

[libvirt-users] pool and VM disk/image connection
by Zdenek Styblik 29 Nov '10

29 Nov '10

Dear list, I had a need to migrate pool resp. images in pool from /some/where/ to /some/where/else/. To my surprise, I just found out editing pool wasn't enough as each and every VM has full path to disk image not just "link" or "connection" to pool. I don't want to say this is bug or wrong doing; I don't want to say it isn't my fault, because it is and I should have study more carefully. What I'm asking for is an explanation of connection between images in pool, pool and VMs (or something like that). Just 1+1=? You see, my expectation was just to edit pool and it's all going to work-out. It didn't :) Thank you, Zdenek -- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla(a)turnovfree.net jabber: stybla(a)jabber.turnovfree.net

1 0

[libvirt-users] Anyone knows when is the next release for libvirt java bindings?
by Ravi Pawar 25 Nov '10

25 Nov '10

-- Thanks & Regards Ravi Pawar

1 1