search for: phyp

...u: fix the check of virDomainObjUnref()'s return value (Wen Congyang) - Fix checking of return codes in dispatcher (Daniel P. Berrange) - qemu: avoid qemu_driver being unlocked twice when virThreadPoolNew() failed (Wen Congyang) - virsh: fix regression in parsing optional integer (Eric Blake) - phyp: avoid memory leaks in command values (Eric Blake) - phyp: avoid memory leak on failure (Eric Blake) - phyp: avoid a logic bug (Eric Blake) - free cpumask of vcpupinDef (Hu Tao) - network: Fix NULL dereference during error recovery (Michal Privoznik) - Add missing checks for QEMU domain state in tu...

Hi, Is virsh able to access the VMX config of a virtual machine running on a esxi host? I would like to take backups of my virtual machine configs and the doku section "Converting from VMware VMX config to domain XML config" (http://libvirt.org/drvesx.html) comes close to this - but does not tell how to get access to the vmx file. I would prefer a solution where ssh access to the

On Fri, Jun 03, 2016 at 02:33:47PM +1000, Benjamin Herrenschmidt wrote: > ?- For the above, can you show (or describe) where the qspinlock > ? ?improves things compared to our current locks. So currently PPC has a fairly straight forward test-and-set spinlock IIRC. You have this because LPAR/virt muck and lock holder preemption issues etc.. qspinlock is 1) a fair lock (like ticket locks)

On Fri, Jun 03, 2016 at 02:33:47PM +1000, Benjamin Herrenschmidt wrote: > ?- For the above, can you show (or describe) where the qspinlock > ? ?improves things compared to our current locks. So currently PPC has a fairly straight forward test-and-set spinlock IIRC. You have this because LPAR/virt muck and lock holder preemption issues etc.. qspinlock is 1) a fair lock (like ticket locks)

...s driver 2 2012-06-26 19:48:52.283+0000: 26051: debug : virRegisterDriver:775 : driver=0x4daec00 name=VMWARE 2012-06-26 19:48:52.283+0000: 26051: debug : virRegisterDriver:799 : registering VMWARE as driver 3 2012-06-26 19:48:52.283+0000: 26051: debug : virRegisterDriver:775 : driver=0x4dae5a0 name=PHYP 2012-06-26 19:48:52.284+0000: 26051: debug : virRegisterDriver:799 : registering PHYP as driver 4 2012-06-26 19:48:52.284+0000: 26051: debug : virRegisterStorageDriver:658 : registering PHYP as storage driver 1 2012-06-26 19:48:52.285+0000: 26051: debug : virRegisterInterfaceDriver:625 : registerin...

...ug : virRegisterDriver:791 : registering OPENVZ as driver 2 22:29:33.295: 8389: debug : virRegisterDriver:767 : driver=0x375920 name=VMWARE 22:29:33.295: 8389: debug : virRegisterDriver:791 : registering VMWARE as driver 3 22:29:33.295: 8389: debug : virRegisterDriver:767 : driver=0x375420 name=PHYP 22:29:33.295: 8389: debug : virRegisterDriver:791 : registering PHYP as driver 4 22:29:33.295: 8389: debug : virRegisterStorageDriver:650 : registering PHYP as storage driver 1 22:29:33.295: 8389: debug : virRegisterInterfaceDriver:617 : registering PHYP as interface driver 1 22:29:33.324: 8389:...

...ug : virRegisterDriver:791 : registering OPENVZ as driver 2 22:29:33.295: 8389: debug : virRegisterDriver:767 : driver=0x375920 name=VMWARE 22:29:33.295: 8389: debug : virRegisterDriver:791 : registering VMWARE as driver 3 22:29:33.295: 8389: debug : virRegisterDriver:767 : driver=0x375420 name=PHYP 22:29:33.295: 8389: debug : virRegisterDriver:791 : registering PHYP as driver 4 22:29:33.295: 8389: debug : virRegisterStorageDriver:650 : registering PHYP as storage driver 1 22:29:33.295: 8389: debug : virRegisterInterfaceDriver:617 : registering PHYP as interface driver 1 22:29:33.324: 8389:...

...nd with the QEmu debugging and hacking APIs. The release is available as usual at ftp://libvirt.org/libvirt Quite a lot of bug fixes during the two months since 0.8.1, and a few new feature. It also tagged more commits as being documentation or portability fixes, it's good :-) Features: - phyp: adding support for IVM (Eduardo Otubo) - libvirt: introduce domainCreateWithFlags API (Eric Blake) - add 802.1Qbh and 802.1Qbg switches handling (Stefan Berger) - Support for VirtualBox version 3.2 (Jean-Baptiste Rouault) - Init script for handling guests on shutdown/boot (Jiri Denemark) - qemu: l...

...U freq: No such file or directory (1) How to fix this error? The VirtualBox driver seems to be installed: s14% virsh -V Narzędzie wiersza poleceń virsh biblioteki libvirt 1.2.5 Proszę zobaczyć stronę WWW pod adresem http://libvirt.org/ Compiled with support for: Hypervisors: QEMU/KVM UML VMWare PHYP VirtualBox ESX Test Networking: Remote Bridging Storage: Dir SCSI Miscellaneous: Daemon Secrets Debug Readline Modular s14% uname -a FreeBSD s14 9.3-PRERELEASE FreeBSD 9.3-PRERELEASE #0: Fri May 16 06:45:56 CEST 2...

Hi, I noticed that libvirt support the following hypervisors currently: * The KVM/QEMU <http://libvirt.org/drvqemu.html> Linux hypervisor * The Xen <http://libvirt.org/drvxen.html> hypervisor on Linux and Solaris hosts. * The LXC <http://libvirt.org/drvlxc.html> Linux container system * The OpenVZ <http://libvirt.org/drvopenvz.html> Linux container system *

Hey guys, I'm so glad you added the new set of virConnectListAllDomains functions, it simplifies a lot our work!. I was only wondering why there is no support for PowerVM. Is it that it hasn't been developed or is there some technical hardship? Best, Camilo Aguilar

...nclude --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-runstatedir=/run --with-qemu --without-openvz --without-lxc --without-vbox --without-libxl --with-sasl --with-polkit --with-libvirtd --without-phyp --with-esx --without-hyperv --without-vmware --without-vz --without-bhyve --with-remote-default-mode=legacy --with-interface --with-network --with-storage-fs --with-storage-lvm --with-storage-iscsi --with-storage-iscsi-direct --with-storage-scsi --with-storage-disk --with-storage-mpath --with-stora...

...=no --with-netcf=no --with-numactl=no --with-openwsman=no --with-pciaccess=no --with-sanlock=no --with-sasl=no --with-selinux=no --with-selinux-mount=no --with-udev=no --with-yajl=no --with-xen=no --with-xen-inotify=no --with-qemu=no --with-uml=no --with-openvz=no--with-vmware=no --with-phyp=no --with-xenapi=no --with-libxl=no --with-vbox=no --with-gnutls=no --without-ssh2 --with-rhel5-api=yes The same library sources when compiled on RHEL6 as above, without specifying the "--with-rhel5-api=yes" compiles AND connect to the same server fine I am looking for pointers as to wh...

...e, so we just rely on Linux virtio "knowing" that it happens. It's a bit yucky but that's now history... Essentially pseries "architecturally" does not have the concept of not having an iommu in the way and qemu violates that architecture today. (Remember it comes from pHyp, our priorietary HV, which we are somewhat mimmicing here). So if we always set VIRTIO_F_IOMMU_PLATFORM, it *will* force all virtio through that iommu and performance will suffer (esp vhost I suspect), especially since adding/removing translations in the iommu is a hypercall. Now, we do have HV A...

...e, so we just rely on Linux virtio "knowing" that it happens. It's a bit yucky but that's now history... Essentially pseries "architecturally" does not have the concept of not having an iommu in the way and qemu violates that architecture today. (Remember it comes from pHyp, our priorietary HV, which we are somewhat mimmicing here). So if we always set VIRTIO_F_IOMMU_PLATFORM, it *will* force all virtio through that iommu and performance will suffer (esp vhost I suspect), especially since adding/removing translations in the iommu is a hypercall. Now, we do have HV A...

Hi, erveryone: I compiled libvirt-1.1.2.tar.gz from source. my compile step: ./configure --prefix=/usr --libdir=/usr/lib64 --without-xen --without-xen-inotify \ --without-uml --without-openvz --without-vmware --without-vbox --without-lxc \ --without-esx --without-parallels --without-phyp -- without-test --with-yajl \ --without-selinux --without-secdriver-selinux make && make install #ls -l /usr/lib64/libvirt* -rw-r--r-- 1 root root 10144610 2月 6 15:34 /usr/lib64/libvirt.a -rwxr-xr-x 1 root root 1018 5月 8 19:51 /usr/lib64/libvirt.la -rwxr-xr-x 1 root root 10...

On 2016?06?03? 09:32, Benjamin Herrenschmidt wrote: > On Fri, 2016-06-03 at 11:32 +1000, Benjamin Herrenschmidt wrote: >> On Thu, 2016-06-02 at 17:22 +0800, Pan Xinhui wrote: >>> >>> Base code to enable qspinlock on powerpc. this patch add some >>> #ifdef >>> here and there. Although there is no paravirt related code, we can >>> successfully

On 2016?06?03? 09:32, Benjamin Herrenschmidt wrote: > On Fri, 2016-06-03 at 11:32 +1000, Benjamin Herrenschmidt wrote: >> On Thu, 2016-06-02 at 17:22 +0800, Pan Xinhui wrote: >>> >>> Base code to enable qspinlock on powerpc. this patch add some >>> #ifdef >>> here and there. Although there is no paravirt related code, we can >>> successfully

...option now. rebase onto linux-next(4.9-rc7) v6 -> v7: rebase onto 4.8-rc4 v1 -> v6: too many details. snip. some benchmark result below perf bench these numbers are ops per sec, So the higher the better. ******************************************* on pSeries with 32 vcpus, 32Gb memory, pHyp. ------------------------------------------------------------------------------------ test case | pv-qspinlock | qspinlock | current-spinlock ------------------------------------------------------------------------------------ futex hash | 618572 | 552332 | 553788 futex lock-pi | 364 | 36...

...option now. rebase onto linux-next(4.9-rc7) v6 -> v7: rebase onto 4.8-rc4 v1 -> v6: too many details. snip. some benchmark result below perf bench these numbers are ops per sec, So the higher the better. ******************************************* on pSeries with 32 vcpus, 32Gb memory, pHyp. ------------------------------------------------------------------------------------ test case | pv-qspinlock | qspinlock | current-spinlock ------------------------------------------------------------------------------------ futex hash | 618572 | 552332 | 553788 futex lock-pi | 364 | 36...