- Devel - libvirt List Archives

Re: [libvirt] [Libguestfs] get virtual machine`s ip address
by Richard W.M. Jones 11 May '12

11 May '12

On Thu, May 10, 2012 at 08:24:31AM -0700, THO HUYNH wrote: > I`m writing 2 simple socket programs: Client program runs on guest, > server program runs on host machine. > > The server need the dom xml name of the guest which is running the > client program and the only information the server program has is > the guest`s ip address. [...] Is there another way to get the dom > xml name of a guest from an ip address (if the ip address belongs to > that guest). CC'd to libvir-list, since this is really a libvirt question. The trouble with the architecture you've described is that it relies on the IP source address for authentication, one of those things you should never do if you care about security: https://en.wikipedia.org/wiki/IP_address_spoofing Maybe because it's TCP, and it's a closed system with a firewall, you can get away with it. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v

4 3

[libvirt] [PATCH 0/3] Fix output of virsh vcpuinfo after cpu hotplug
by Peter Krempa 11 May '12

11 May '12

The informations about virtual processors stored by libvirt were not updated after a cpu hotplug. Peter Krempa (3): qemu: Refactor qemuDomainSetVcpusFlags qemu: Re-detect virtual cpu threads after cpu hot (un)plug. qemu: Don't skip detection of virtual cpu's on non KVM targets src/qemu/qemu_driver.c | 48 +++++++++++++++++++++++++++++++--------------- src/qemu/qemu_process.c | 12 ----------- 2 files changed, 32 insertions(+), 28 deletions(-) -- 1.7.3.4

2 8

Re: [libvirt] [Qemu-devel] [PATCH v12 0/4] support to migrate with IPv6 address
by Eric Blake 11 May '12

11 May '12

[adding libvirt] On 05/11/2012 12:46 AM, Amos Kong wrote: > On 05/11/2012 02:12 AM, Michael Roth wrote: >> On Thu, May 10, 2012 at 11:29:48AM -0600, Eric Blake wrote: >>> On 05/10/2012 10:27 AM, Amos Kong wrote: >>>> Those patches updated help functions in qemu-socket.c, >>>> and used them in migrate-tcp.c to supporting IPv6 migration. >> addr parsing now relies on qemu-sockets.c:inet_parse(), which has supported >> [ip6addr]:port for a while, as opposed to net.c:parse_host_port(), which >> didn't. > > yeah. > > I didn't change qemu monitor cmd interface in this patchset, > and the transport of data is done by qemu, not libvirt. > > I guess libvirt only needs to update addr string parse, > for example: > > ---- GOOD > start a VM: > # qemu-kvm --enable-kvm -boot n -incoming tcp:ipv6alias:16514 -vnc :1 > -monitor stdio -name qemu-vm1 > > try to migrate vm by virsh with addr alias > # virsh migrate libivrt-vm2 tcp:ipv6alias > (connection can establish) > > --- FAIL > start a VM: > # qemu-kvm-apply-my-patches --enable-kvm -boot n -incoming > tcp:[2002::3:4]:16514 -vnc :1 -monitor stdio -name qemu-vm1 > > try to migrate vm by virsh with ipv6 addr: > # virsh migrate libvirt-vm2 tcp:[2002::3:4] > error: invalid argument: could not parse connection URI tcp:[2002::3:4] Thanks for researching that. Looks like it should be fixed in libvirt to match, then. -- Eric Blake eblake(a)redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

1 0

[libvirt] Problem of host CPU topology parsing
by Osier Yang 11 May '12

11 May '12

Hi, We have problem of host CPU topology parsing on special platforms (general platforms are fine). E.g. On a AMD machine with 48 CPUs [1] (4 sockets, 6 cores indeed [2]), VIR_NODEINFO_MAXCPUS [3] will always return 24 as the total CPU number. As a result, a domain without "cpuset" or "placement='auto'" (which drives numad) will only be pinned to part of the host CPUs (in the case of the 48 CPUS AMD machine, domain process will be pinned to only the first 24 CPUs), which cause the performance lost. And actually it's also functional bug, as the "cpuset" specified by user could be truncated. If a domain uses "placement='auto'", and the advisory nodeset returned from numad has node(s) exceeds the wrong max CPU number, the domain will fail to start, as the bitmask passed to sched_setaffinity is fully filled with zero. "nodeinfo.cpus" has the right number though, but I'm not sure if it should be used as the max CPU number. VIR_NODEINFO_MAXCPUS is used in many places, and I'd never want to fix something here, but break other things there. Anyone has thought on how to sort the fucky topology out? [1] http://fpaste.org/MTtz/ [2] http://fpaste.org/mtoA/, http://fpaste.org/EPLd/ [3] #define VIR_NODEINFO_MAXCPUS(nodeinfo) ((nodeinfo).nodes*(nodeinfo).sockets*(nodeinfo).cores*(nodeinfo).threads) Regards, Osier

4 13

[libvirt] Fwd: Supporting native USB in oVirt
by Oved Ourfalli 11 May '12

11 May '12

Hey, We are now working on adding the support for native USB devices on oVirt, and we have some difficulties. Please see the details/discussion below. Thank you for your help, Oved ----- Forwarded Message ----- From: "Itamar Heim" <iheim(a)redhat.com> To: "Michal Privoznik" <mprivozn(a)redhat.com> Cc: "Oved Ourfalli" <ovedo(a)redhat.com>, "Dave Allan" <dallan(a)redhat.com>, "Jiri Denemark" <jdenemar(a)redhat.com>, "Igor Lvovsky" <ilvovsky(a)redhat.com>, "Eli Mesika" <emesika(a)redhat.com>, "Hans de Goede" <hdegoede(a)redhat.com>, "Dan Kenigsberg" <danken(a)redhat.com>, "Andrew Cathrow" <acathrow(a)redhat.com> Sent: Wednesday, May 9, 2012 1:18:40 PM Subject: Re: Supporting native USB in oVirt On 05/09/2012 01:12 PM, Michal Privoznik wrote: > On 08.05.2012 09:19, Oved Ourfalli wrote: >> Hi, >> >> We are now working on adding the support for native USB devices on oVirt. >> As far as we understand, in order to use it we need to pass the following devices with the following restrictions (according to the EHCI spec): >> 1. EHCI USB controller - with the highest function number, #7. >> >> devices='{type:controller,device:usb,model:ich9-ehci1,address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x7}}' >> >> 2. 3 UHCI USB controllers, on the same bus and PCI slot as the EHCI controller. Set the multifunction bit to on, on the controller with function #0. >> >> devices='{type:controller,device:usb,model:ich9-uhci1,master:{startport:0},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x0,multifunction:on}}' >> devices='{type:controller,device:usb,model:ich9-uhci2,master:{startport:2},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x1}}' >> devices='{type:controller,device:usb,model:ich9-uhci3,master:{startport:4},address:{type:pci,domain:0x0000,bus:0x00,slot:0x04,function:0x2}}' >> >> 3. USB redirect devices (according to the needed number of USB slots, maximum 6) on the same bus, each one having a different port. >> >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:1}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:2}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:3}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:4}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:5}}' >> devices='{type:redir,device:spicevmc,bus:usb,address:{type:usb,bus:0,port:6}}' >> >> 4. If we want more than 6 USB slots, we need to have 2 EHCI controllers, and 6 UHCI controllers, that are consistent with the restrictions above, on different bus. >> (we need them to be on different bus, since the connection between the redirect devices and the controllers is the bus). >> >> According to Hans (cc-ed), if we let libvirt pick its own addresses, it will put each controller of the composite USB controller device on its own pci slot, which is a violation of the EHCI spec. > >> >> The problem is that the oVirt engine is not aware of addresses. They aren't managed by it. >> They are chosen automatically by libvirt, returned to the engine, and they saved in the engine database in order to provide the ability to retain the same PCI addresses after VM restart. >> >> So, in order to support the EHCI spec, oVirt will have to be aware of addresses, manage them (allocate them, check for collisions, update on every libvirt change regarding that, etc...). Obviously, it doesn't feel right, and in fact it is also not feasible, to manage these addresses in the oVirt domain. >> >> Is all the above correct, or are we missing something? >> If so, can you address the issues above, and provide the ability to manage these devices in libvirt? > > Let's have this conversation upstream (libvirt-list(a)redhat.com) Many > developers are there so if there's anything libvirt can do, we should > agree on concept there.

5 9

[libvirt] [PATCH] usb: fix crash when failing to attach a second usb device
by Guannan Ren 11 May '12

11 May '12

when failing to attach another usb device to a domain for some reason which has one use device attached before, the libvirtd crashed. The crash is caused by null-pointer dereference error in invoking usbDeviceListSteal passed in NULL value usb variable. commit 05abd1507d66aabb6cad12eeafeb4c4d1911c585 introduces the bug. --- src/qemu/qemu_hotplug.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/src/qemu/qemu_hotplug.c b/src/qemu/qemu_hotplug.c index ad31eba..9b60816 100644 --- a/src/qemu/qemu_hotplug.c +++ b/src/qemu/qemu_hotplug.c @@ -1213,7 +1213,8 @@ error: cleanup: usbDeviceListFree(list); - usbDeviceListSteal(driver->activeUsbHostdevs, usb); + if (usb) + usbDeviceListSteal(driver->activeUsbHostdevs, usb); return -1; } -- 1.7.7.5

2 2

[libvirt] [Patch] Libvirt - Fix locking for readonly devices
by David Weber 11 May '12

11 May '12

Hi, I'm currently working on getting sanlock into Debian/Ubuntu. While testing, I noticed that I wasn't able to add a readonly or shared device: "internal error unsupported configuration: Readonly leases are not supported". After looking into the source, it seems to be the following situation: - Libvirt passes every device to the sanlock plugin, even if it is readonly - The sanlock plugin rejects to add a lease for the readonly device, returning an error so the machine starts to fail The attached patch rejects passing readonly and shared devices to the lock-plugin so they shouldn't be a problem anymore. Would this be an appropriated way to fix this problem? (I'm neither experienced in libvirt nor C) What seems odd to me is that Fedora either doesn't hit this or nobody has ever reported it. I'm not member of this list so please CC me. Thanks! Cheers, David

3 2

[libvirt] In libxl_driver, how to lock/unlock objects while doing an operation that runs for a long time?
by Oscar Ben 10 May '12

10 May '12

In the discussion : http://thread.gmane.org/gmane.comp.emulators.libvirt/53534 People mentioned about long-term operations' LOCKs there. It seems that, in libxl_driver, certain opeations may hold a lock for too long, thus other operations, even those just do query jobs, would be blocked. In qemu_driver, there seems to be a more complexy way to solve this problem, by employing a condition variable. My question is : Is "Fixing such problem in libxl_driver" in our todo-list? If yes, what's the detailed solution? Will that be similar to qemu's CONDITION VARIABLE method?

3 2

[libvirt] Libvirt java binding crash Tomcat
by Hubert Zhang 10 May '12

10 May '12

Running on linux and libvirt 0.9.11. Using libvirt java 0.4.7. Notice that the Tomcat server crashes and shows the dump like this: *** glibc detected *** jsvc.exec: double free or corruption (out): 0x086f14a8 *** ======= Backtrace: ========= /lib/libc.so.6[0xc03745] /lib/libc.so.6(cfree+0x59)[0xc03b89] /tmp/jna/jna486823639517928939.tmp(Java_com_sun_jna_Native_free+0x1d)[0x430c4c] [0xb46de240] [0xb46d218d] [0xb46d218d] [0xb46d218d] [0xb46cf3e6] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bdb21] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x15b3478] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bd94f] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13f0ef7] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13d4aee] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjava.so(Java_java_lang_ref_Finalizer_invokeFinalizeMethod+0x6e)[0x11cb3e] [0xb46de240] [0xb46d218d] [0xb46d218d] [0xb46d218d] [0xb46cf3e6] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bdb21] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x15b3478] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bd395] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x13bd458] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x143fbe7] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x16b404f] /usr/lib/jvm/sun-java-6u24/jre/lib/i386/server/libjvm.so[0x15b4a6e] /lib/libpthread.so.0[0x8fa842] /lib/libc.so.6(clone+0x5e)[0xc6c4ce] ======= Memory map: ======== 00110000-00133000 r-xp 00000000 08:01 106948 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjava.so 00133000-00135000 rw-p 00023000 08:01 106948 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjava.so 00135000-00148000 r-xp 00000000 08:01 74629 /lib/libnsl-2.5.so 00148000-00149000 r--p 00012000 08:01 74629 /lib/libnsl-2.5.so 00149000-0014a000 rw-p 00013000 08:01 74629 /lib/libnsl-2.5.so 0014a000-0014c000 rw-p 00000000 00:00 0 0014c000-0014f000 ---p 00000000 00:00 0 0014f000-0019d000 rwxp 00000000 00:00 0 0019d000-001d7000 r-xp 00000000 08:01 106944 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjdwp.so 001d7000-001d8000 rw-p 00039000 08:01 106944 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libjdwp.so 001d8000-001d9000 ---p 00000000 00:00 0 001d9000-00259000 rwxp 00000000 00:00 0 00259000-0026d000 r-xp 00000000 08:01 106885 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libnet.so 0026d000-0026e000 rw-p 00013000 08:01 106885 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/libnet.so 0026e000-00273000 r-xp 00000000 08:01 106769 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/headless/libmawt.so 00273000-00274000 rw-p 00004000 08:01 106769 /usr/lib/jvm/sun-java-6u24/jre/lib/i386/headless/libmawt.so 00276000-00290000 r-xp 00000000 08:01 74651 /lib/ld-2.5.so 00290000-00291000 r--p 00019000 08:01 74651 /lib/ld-2.5.so 00291000-00292000 rw-p 0001a000 08:01 74651 /lib/ld-2.5.so 00292000-00295000 ---p 00000000 00:00 0 00295000-002e3000 rwxp 00000000 00:00 0 002e3000-002e8000 r-xp 00000000 08:01 212038 /usr/lib/libwsman_curl_client_transport.so.1.0.0 002e8000-002e9000 rw-p 00004000 08:01 212038 /usr/lib/libwsman_curl_client_transport.so.1.0.0 ...................................... Sometimes I see "invalid pointer" as well. It seems a bug to the libvirt java API. Has anyone seen this error before? Thanks.

2 3

[libvirt] oVirt workshop at LinuxCon Japan
by Dave Allan 10 May '12

10 May '12

I got this notice today about an oVirt workshop coming up June 8 at LinuxCon Japan, and I thought it might be of interest. Details below... Hello everyone, As part of our efforts to raise awareness of and educate more developers about the oVirt project, we will be holding an oVirt workshop at LinuxCon Japan, taking place on June 8, 2012. You can find full details of the workshop agenda on the LinuxCon Japan site. [0] Registration for the workshop is now open and is free of charge for the first 50 participants. We will also look at adding additional participant slots to the workshop based on demand. Attendees who register for LinuxCon Japan via the workshop registration link [1] will also be eligible for a discount on their LinuxCon Japan registration. Please spread the word to folks you think would find the workshop useful. If they have already registered for LinuxCon Japan, they can simply edit their existing registration to include the workshop. [0] https://events.linuxfoundation.org/events/linuxcon-japan/ovirt-gluster-work… [1] http://www.regonline.com/Register/Checkin.aspx?EventID=1099949 Cheers, LH -- Leslie Hawthorn Community Action and Impact Open Source and Standards @ Red Hat identi.ca/lh twitter.com/lhawthorn

1 0