- Devel - libvirt List Archives

[libvirt] VMware ESX driver announcement
by Matthias Bolte 26 May '09

26 May '09

Hello, I'm participate in a project of the Paderborn Center for Parallel Computing, an institute of the University of Paderborn: http://pc2.uni-paderborn.de The project's goal is to use virtualization in a supercomputer environment. We've decided to use libvirt to manage different hypervisor. A subgoal is to extend the driver base of libvirt. We've started an VMware ESX driver and are investigating Hyper-V support (see next mail). The ESX driver isn't complete yet, currently it supports: - domain lookup by ID, UUID and name - domain listing - domain suspend and resume - domain reboot, if the VMware tools are installed inside the domain - domain start and shutdown - domain migration The driver uses the SOAP based VMware VI API. We've tried to generate SOAP client code with gSOAP and looked at other SOAP libraries, but the VI API uses inheritance in a way that gSOAP fails to generate C code for. Because of this we wrote a minimal SOAP client based on libcurl and libxml2 that can handle this inheritance problem in C. The next item on the todo list is domain creation, because currently the driver can only deal with prior existing domains. We think this code might be useful for others and would be glad if the driver could be merged into libvirt in medium term. All of our work is licensed under LGPLv2+.

4 7

[libvirt] Koan, KVM and PXE
by Fabien Dupont 25 May '09

25 May '09

Hi all. I use Cobbler to manage my PXE boot. I would like to extend my use to manage VM deployment with Koan. But I have a problem related to network and my VM can't boot. I have already posted on Cobbler mailing-list but it's probably on kvm/libvirt side... I am on Fedora 10 with Cobbler 1.6.4 and Koan 1.6.3 (latest available from stable repos), and libvirt 0.5.1-2.fc10. I would like to create VMs using KVM thus I have imported FC10 DVD, added Everything and Updates repos and created a host using the profile created during import. The system has the following properties : root# cobbler system report vmtest system : vmtest profile : fedora-core-10-x86_64 comment : created : Fri May 8 13:43:40 2009 gateway : 192.168.1.254 hostname : vmtest image : kernel options : {} kernel options post : {} kickstart : <<inherit>> ks metadata : {} mgmt classes : [] modified : Sat May 23 18:42:59 2009 name servers : [] name servers search : [] netboot enabled? : True owners : ['admin'] redhat mgmt key : <<inherit>> redhat mgmt server : <<inherit>> server : <<inherit>> template files : {} virt cpus : <<inherit>> virt file size : <<inherit>> virt path : <<inherit>> virt ram : <<inherit>> virt type : <<inherit>> power type : ipmitool power address : power user : power password : power id : interface : eth0 mac address : ff:00:00:01:00:00 bonding : bonding_master : bonding_opts : is static? : True ip address : 192.168.1.201 subnet : 255.255.255.0 static routes : [] dns name : vmtest.local dhcp tag : virt bridge : br0 As you can see, I use a bridged network with a real bridge create with the method described on the wiki (eth0 is the real interface and br0 the bridge). Then I create the VM using : koan --server=cobbler.evenit.info --virt --system=vmtest The VM is correctly created and started : kernel and initrd are correctly set, virtual hard drive is right and network interface seems right. root# ps -edf | grep kvm root 19484 23655 67 21:54 ? 00:00:06 /usr/bin/qemu-kvm -S -M pc -m 256 -smp 1 -name vmtest -monitor pty -no-reboot -boot c -kernel /var/lib/libvirt/boot/virtinst-vmlinuz.omv9yr -initrd /var/lib/libvirt/boot/virtinst-initrd.img.Ufj-qc -append ks= http://cobbler.evenit.info/cblr/svc/op/ks/system/vmtest ksdevice=link kssendmac lang= text method= http://cobbler.evenit.info:80/cblr/links/fedora-core-10-x86_64/<http://cobbler.evenit.info/cblr/links/fedora-core-10-x86_64/>-drive file=/var/lib/libvirt/images/vmtest-disk0,if=virtio,index=0,boot=on -net nic,macaddr=ff:00:00:01:00:00,vlan=0,model=virtio -net tap,fd=14,script=,vlan=0,ifname=vnet0 -serial pty -parallel none -usb -vnc 127.0.0.1:0 -k en-us But, when I open the VM display with virt-manager, I see that installation can't start as DHCP is not answering... There's no trace of the DHCP requests on DHCP server and vnet0 seems to have no trafic : [root@lilith ~]# netstat -i Table d'interfaces noyau Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg br0 1500 0 173524 0 0 0 261005 0 0 0 BMRU eth0 1500 0 173589 0 0 0 260909 0 0 0 BMPRU lo 16436 0 29105 0 0 0 29105 0 0 0 LRU vnet0 1500 0 0 0 0 0 1 0 0 0 BMRU As far as I can see, it seems vnet0 doesn't forward its trafic to br0 like there's no link. I have also seen that the vnet0 interface seen from host (opposed to guest) doesn't have the MAC address asked for vnet0, but this may be normal. -- Fabien

1 0

[libvirt] PATCH: add support for -snapshot
by Geert Jansen 25 May '09

25 May '09

Hi, i'm working on some infrastructure to run unit tests in a virtual environment. For this, I need to be able to pass a "snapshot=on" argument to a qemu virtual disk so that I know I start with the same state all the time. The attached patch implements this. It adds a boolean <snapshot/> to the <disk> section in the XML. Please consider for inclusion. Regards, Geert Jansen

2 1

[libvirt] [PATCH 1/1] fixed the event-test.c example to check for return values
by Pritesh Kothari 25 May '09

25 May '09

Hi All, The event-test.c example doesn't check for the return values while registering for the callbacks, this patch just checks for them along with a correcting a small typo. (Unpaused => Paused) Regards, Pritesh

3 2

[libvirt] migration
by Zvi Dubitzky 25 May '09

25 May '09

Does anybody know if migration within a host from one domain to another works today It did not work for me for libvirt 0.6.1 thanks Zvi Dubitzky Virtualization and System Architecture Email:dubi@il.ibm.com IBM Haifa Research Laboratory Phone: +972-4-8296182 Haifa, 31905, ISRAEL

1 0

[libvirt] save/restore for KVM
by Christian Weyermann 24 May '09

24 May '09

Hello everybody, I try to save and restore a virtual machine, but I always get this error message: ~$ virsh save test1 test1.vm Domain test1 nach test1.vm gespeichert [german for test1 successfully saved to test1.vm] ~$ virsh restore test1.vm 17:53:10.341: error : this function is not supported by the hypervisor: STDIO migration is not supported with this QEMU binary libvir: QEMU error : this function is not supported by the hypervisor: STDIO migration is not supported with this QEMU binary 17:53:10.341: error : operation failed: failed to start VM libvir: QEMU error : operation failed: failed to start VM Fehler: Wiederherstellen der Domain aus test1.vm gescheitert [german: Restoring test1.vm failed!] Fehler: operation failed: failed to start VM I am using libvirt 0.6.3, KVM-84 with qemu 0.9.1. Does anyone have an idea, how to solve this issue? Thanks in advance and kind regards, Christian

1 0

[libvirt] libvirt native parameters
by Zvi Dubitzky 24 May '09

24 May '09

can anybody remind me where is the native qemu parameters that result from libvirt translation of an XML file stored (file path). thanks Zvi Dubitzky Virtualization and System Architecture Email:dubi@il.ibm.com IBM Haifa Research Laboratory Phone: +972-4-8296182 Haifa, 31905, ISRAEL

3 2

[libvirt] error: failed to connect to the hypervisor
by Erkan Unal 24 May '09

24 May '09

Hi, I installed the libvirt with the following configure options as an unprivileged user, I am planning to use it just for qemu/kvm: ./configure --without-xen --without-lxc --without-uml --without-openvz --without-vbox --without-numactl --prefix=/some/nonstandard/dir make make install --without-numactl is added because of a compilation error. I am not sure whether it is completely necessary or not. If you think it has effect on the error, please state the reason. After installation I got the following error when I tried to run the virsh without any options: error: failed to connect to the hypervisor With the following command line error was "Segmentation Fault": virsh -c qemu:///session. Qemu executable path: /usr/local/bin/qemu-system-x86_64 and it is defined on the path. Libvirt daemon is failing with the same error too. System ---> Scientific Linux SL release 4.7 (Beryllium), Kernel version: 2.6.28.2, libvirt version: 0.6.3 Any ideas? P.S.: Is there a way to compile static virsh executable? I tried altering make files, configure options, linker flags and compiler flags but no luck. "ldd virsh" command should say "not a dynamic executable" after compilation. Thanks, Erkan Unal

2 1

[libvirt] SetMaxMemory vs. SetMemory
by Matthias Bolte 24 May '09

24 May '09

Hello, I just took a look at the driver functions for SetMaxMemory and SetMemory, as they are not implemented yet for the ESX driver and Daniel Veillard was a bit surprised that they are missing, as he expects them to be simple to implement. The problem is that I'm not sure how the memory model of ESX maps to SetMaxMemory vs. SetMemory. An ESX virtual machine has a defined memory size. That's the size reported to the guest OS as the available "physical" memory size. Beside this ESX allows the user to control how the hypervisor satisfies this "physical" memory size. You can define a reservation and an upper limit. The hypervisor will at least use the reserved amount of real physical memory to satisfy the "physical" memory size, but will not use more than the upper limit. How does this map to SetMaxMemory and SetMemory? My first assumption was, SetMaxMemory defines the "physical" memory size and SetMemory defines the upper limit of real physical memory to satisfy the "physical" memory size. This assumption seems to be in sync with the QEMU driver from just looking at the code. But with Xen it seems to be different. If I call SetMaxMemory and SetMemory with 2GB than free inside the domain reports 2GB total memory. After I call SetMemory with 1GB, free reports 1GB of total memory. I'm confused. So, what is the intended semantic for SetMaxMemory and SetMemory? Regards, Matthias

4 6

[libvirt] Re: BUG REPORT: -net tap, fd=X does not work correctly in kvm-86
by Anthony Liguori 24 May '09

24 May '09

Josh Wilsdon wrote: > We are doing work with libvirt 0.6.3 through which we have started > virtual machines. Using the same "create" command with the same > storage, the same everything else this configuration works with both > kvm-84 and kvm-85. When I built a fresh version of kvm-86 this > stopped working with an error: > > qemu: invalid parameter '15' in 'fd=15,script=,vlan=0,ifname=vnet0' > It's a libvirt bug. script and ifname have never been valid parameters for -net tap. Historically, -net has ignored unknown options but recently, it now throws an error when encountering an unsupported option. Regards, Anthony Liguori

4 3