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
* The User Mode Linux <http://libvirt.org/drvuml.html> paravirtualized
kernel
* The VirtualBox <http://libvirt.org/drvvbox.html> hypervisor
* The VMware ESX and GSX <http://libvirt.org/drvesx.html> hypervisors
* The VMware Workstation and Player
<http://libvirt.org/drvvmware.html> hypervisors
* The Microsoft Hyper-V <http://libvirt.org/drvhyperv.html> hypervisor
/"the goal of libvirt: *to provide a common and stable layer sufficient
to securely manage domains on a node, possibly remote*."/
My question is, does redhat's libvirt team have the plan to support IBM
PowerVM hypervisor? If the answer is NO, what's the reason to make the
support for IBM PowerVM hypervisor doesn't make sense...
BRs,
Dennis
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://listman.redhat.com/archives/libvirt-users/attachments/20120704/5ef22ad7/attachment.htm>
On 07/03/2012 07:32 PM, Dennis Chen wrote:> Hi, > > I noticed that libvirt support the following hypervisors currently: >> /"the goal of libvirt: *to provide a common and stable layer sufficient > to securely manage domains on a node, possibly remote*."/ > > My question is, does redhat's libvirt team have the plan to support IBM > PowerVM hypervisor?Yes, if someone will contribute the patches, at least as far as upstream libvirt is concerned. (Do note, however, that a different question about whether some future version of RHEL will provide paid support from Red Hat for the IBM PowerVM hypervisor is something I cannot answer, and is best asked to your Red Hat sales rep if you are worried about it. Or put another way, this list only worries about the upstream direction of libvirt, while historically, Red Hat is only willing to provide paid support for a well-defined subset of what upstream is willing to package).> If the answer is NO, what's the reason to make the > support for IBM PowerVM hypervisor doesn't make sense...The only reason a hypervisor would not be supported at the moment is due to lack of volunteer contributions to support it. To some extent, Open Source software only moves as fast as people scratch their own itches. For examples of recent additions, see: HyperV (added in 0.9.5): commit 5e3b0f8b5 Parallels (on slate to be added for the next release, tentatively named 0.10.0): https://www.redhat.com/archives/libvir-list/2012-June/msg01037.html -- Eric Blake eblake at redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 620 bytes Desc: OpenPGP digital signature URL: <http://listman.redhat.com/archives/libvirt-users/attachments/20120703/7e79983b/attachment.sig>
2012/7/4 Dennis Chen <dennis.chen at tnsoft.com.cn>:> Hi, > > I noticed that libvirt support the following hypervisors currently: > > The KVM/QEMU Linux hypervisor > The Xen hypervisor on Linux and Solaris hosts. > The LXC Linux container system > The OpenVZ Linux container system > The User Mode Linux paravirtualized kernel > The VirtualBox hypervisor > The VMware ESX and GSX hypervisors > The VMware Workstation and Player hypervisors > The Microsoft Hyper-V hypervisor > > "the goal of libvirt: to provide a common and stable layer sufficient to > securely manage domains on a node, possibly remote." > > My question is, does redhat's libvirt team have the plan to support IBM > PowerVM hypervisor? If the answer is NO, what's the reason to make the > support for IBM PowerVM hypervisor doesn't make sense...Well, libvirt aleady has support for the 'IBM Power Hypervisor' for a while now, called 'phyp' internally in the codebase, see http://libvirt.org/git/?p=libvirt.git;a=tree;f=src/phyp It's just lacking documentation and for some unknown reason is not mentioned on the homepage. We should fix this. -- Matthias Bolte http://photron.blogspot.com
Hi libvirt team, I found there are very few documents to mention how to launch a libvirtd daemon when built from the source code. A moment ago, I un-install all the kvm related stuff (kvm module, libvirt, virt-manager, virsh, qemu-kvm...) from my ubuntu system. Then I built the libvirt from the source tar package: 1. #./autogen.sh --system --with-phyp --enable-debug=yes CFLAGS=-g 2. #make 3. #make install Everything is OK :), but wait a minute -- According to the instruction in libvirt.org, the option flag "--system" in above step 1 will make the environment is the same as the pre-built package installation, eg, apt-get install ... because I found that the "libvirtd" daemon is not active with "ps aux | grep libvirtd", so I try to start it manually: Method 1: root at dennis-:/home/dennis/workspace/AIX# service libvirtd start libvirtd: unrecognized service Method 2: root at dennis-:/home/dennis/workspace/AIX# /etc/init.d/libvirtd start bash: /etc/init.d/libvirtd: No such file or directory Method 3: root at dennis-:/home/dennis/workspace/AIX# /usr/sbin/libvirtd start 2012-07-05 09:20:42.225+0000: 32749: info : libvirt version: 0.9.12 2012-07-05 09:20:42.225+0000: 32749: error : virDomainDefParseXML:8303 : unknown OS type hvm I don't know if the method 3 is success or not, but I have no time to verify it now, because I have to leave the office now for the later traffic jam... Why "unknow OS type hvm"? If my experiment is useful, then please document it in the libvirt.org page... BRs, Dennis