- Devel - libvirt List Archives

[libvirt] using public vir*Free() (instead of virUnref*()) from vir*FreeName() destructors.
by Laine Stump 08 May '09

08 May '09

I just noticed in datatypes.c that the vir(Network|StoragePool|StorageVol)FreeName destructors call the public API vir*Free() functions rather than the local virUnref*(). vir*Free() all clear any errors, which seems like it might not be the right thing to do (eg, if we're cleaning out the hashtables as part of some error-handling path, and haven't yet logged the error). On the other hand, the public API function does some sanity checking on the object to make sure it really is what we think it is before calling the unref. So it's got that going for it. (5 points to anyone who catches the reference without going to Google) But I don't know enough to know whether or not that's important in this case. So which is more important: the extra sanity check, or not clearing existing error codes?

2 3

[libvirt] PCI Passthrough
by Aaron Clausen 08 May '09

08 May '09

I'm having a heck of a time trying to figure out how to do PCI passthrough for a PCI SCSI controller. I need, if at all possible, to access it so that I can use a SCSI tape drive with a Windows Server 2000 guest. This is xml config I have: <domain type='kvm'> <name>testserver</name> <uuid>f75a2f63-e1bd-72a5-6134-3fcafbcdb970</uuid> <memory>524288</memory> <currentMemory>524288</currentMemory> <vcpu>1</vcpu> <os> <type arch='x86_64' machine='pc'>hvm</type> <boot dev='hd'/> </os> <features> <pae/> </features> <clock offset='localtime'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/bin/kvm</emulator> <disk type='file' device='disk'> <source file='/var/lib/libvirt/images/testserver.img'/> <target dev='hda' bus='ide'/> </disk> <disk type='block' device='cdrom'> <source dev='/dev/cdrom'/> <target dev='hdc' bus='ide'/> <readonly/> </disk> <interface type='bridge'> <mac address='54:52:00:50:03:08'/> <source bridge='br0'/> <target dev='vnet2'/> </interface> <serial type='pty'> <source path='/dev/pts/7'/> <target port='0'/> </serial> <console type='pty' tty='/dev/pts/7'> <source path='/dev/pts/7'/> <target port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/> </devices> </domain> -- Aaron Clausen mightymartianca(a)gmail.com

2 4

[libvirt] Virsh list on xen after stop/restart not working properly
by Thomas Graves 08 May '09

08 May '09

Hello, I am seeing an issue on libvirt 0.6.1 and 0.6.3 with xen3.3.1 where virsh list -all isn't reporting all vms that are active. It happens after you shutdown and then restart a vm. As a side note, it works fine on libvirt 0.3.3. It appears that the domid of the vm is changed when you shutdown/restart a vm on xen. Libvirt is checking xenstore to find domids and it is finding the old ones that are marked as cancelled and not finding the higher number ones that are active/valid. Has anyone seen this issue and have a patch for it? It looks like the old libvirt 0.3.3 went to the hypervisor and xend before the xenstore and that is working properly. Thanks, Tom

2 1

[libvirt] KVM processes -- should we be able to attach them to the libvirtd process?
by Hugh O. Brock 07 May '09

07 May '09

Not too long ago we took a patch that allowed QEMU VMs to keep running even if libvirtd died or was restarted. I was talking to Matt Farellee (cc'd) this afternoon about manageability, and he feels fairly strongly that this behavior should be optional -- in other words, it should be possible to guarantee that if libvirtd dies, it will take all the VMs with the "die-with-libvirtd" flag set down with it. I'm not sure this API is portable to Xen, but it would work on any hypervisor that represents the VM as a normal process. Does this strike anyone else as useful behavior? Thanks, --Hugh

5 6

[libvirt] Java api for libvirt migration
by Zvi Dubitzky 07 May '09

07 May '09

I am trying to do a migrate of VM with libvirt 0.6.1 and kvm-84 . I am successful in doing it many times via the C interface . I can do most of the basic libvirt activity via the libvirt JAVA library (libvirt-java-0.2.1). When it comes to a migrate the JVM fails wit a log file attached below . Can someone help. My memory consumption in my JAVA test code is small. The migrate parameters I am sending with the Java are identical to those I use in the C case and is: destDomain = localDomain.migrate (dcon, // destination host Connect object VIR_MIGRATE_LIVE, null, //const char *dname destination domain name target_uri, //"tcp:9.148.28.13:4444" 0 // unsigned long bandwidth) - do not specify ); 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] [PATCH] return a sensible error on bogus paths
by Guido Günther 07 May '09

07 May '09

Hi, attached patch makes it easier to detect bogus paths when creating/removing pidfiles. O.k. to apply? Cheers, -- Guido

2 2

[libvirt] [PATCH]: don't crash when calling libvirt_lxc without arguments
by Guido Günther 07 May '09

07 May '09

In this case we reference def with is NULL. O.k. to apply? Cheers, -- Guido

2 2

[libvirt] PATCH: Add LSB init headers
by Frederik Himpe 07 May '09

07 May '09

The following patch is needed to make sure libvirt is not started too early in the boot sequence on Mandriva. --- libvirt-0.6.1/qemud/libvirtd.init.in.orig 2009-03-05 19:34:05.000000000 +0100 +++ libvirt-0.6.1/qemud/libvirtd.init.in 2009-03-05 19:34:54.000000000 +0100 @@ -5,7 +5,11 @@ # ### BEGIN INIT INFO # Provides: libvirtd +# Required-Start: $network messagebus +# Should-Start: $named # Should-Start: xend +# Required-Stop: $network messagebus +# Should-Stop: $named # Default-Start: 3 4 5 # Short-Description: daemon for libvirt virtualization API # Description: This is a daemon for managing guest instances

4 5

[libvirt] [PATCH 2/2] support for multiple graphics devices
by Pritesh Kothari 07 May '09

07 May '09

Hi All, I have added support for multiple graphics devices, the patches are as below. I have checked them against current cvs head and works fine PATCH 1/2: contains changes in libvirt for multiple graphics devices PATCH 2/2: contains corresponding changes in qemu driver. Regards, Pritesh

3 5

[libvirt] Authentication with virConnectAuthPtr
by Eduardo Otubo 07 May '09

07 May '09

Hello all, I'll start using virConnectAuthPtr to handle the authentication proccess at the phyp driver I'm wrinting <https://www.redhat.com/archives/libvir-list/2009-April/msg00493.html> and I have some doubts in my mind: 1) What are the types of authentication that 'int *credtype' can hold? And who fills it with the information I'll need? 2) Once known the credential type, I need to use the function pointer 'virConnectAuthCallbackPtr cb' to get the information whatever it is, right? I mean, it can be a password, a pubkey or anything else, right? Is there a callback able to handle password or pubkeys? 3) And finally I'll be able to use the 'void *cbdata' to manage the authentication in my way. In my case, using libssh. In fact, in the end of the process, I'll just need a password or a key to get things working. There is no driver authenticatin agaist ssh channel, that's why I got so confused with this topic. I don't know if my thoughts are pretty clear here. But I would like to confirm the information 2 and 3, and check how 1 works. Could anyone help me? Thanks in advance, []'s -- Eduardo Otubo Software Engineer Linux Technology Center IBM Systems & Technology Group Mobile: +55 19 8135 0885 otubo(a)linux.vnet.ibm.com

2 2