Re: [libvirt] make install fails, missing HTML files

On Friday 13 November 2009 23:28:47 Matthias Bolte wrote: Well, I assume you still have the two rewite lines in your /etc/xml/catalog, that's why it's working without the patch. Yes, of course. Thanks for the patch you submitted today! -t -- Libvir-list mailing list Libvir-list@redhat.com

[libvirt] How to keep VM definitions in sync across hosts?

Hi, is there any best-practice how to keep VM definitions in sync across a couple of hosts? Is it reasonable to put /etc/libvirt/qemu/ on a NFS share? Or are there better ways? How does oVirt solve that? I'm asking because I'm currently setting up a four node cluster with KVM and libvirt.

[libvirt] Security driver on el5

Hi. I'm running libvirt (0.7.2) on a CentOS 5.4 host. It's working quite well, but only if I configure selinux in permissive mode. I've tried to build libvirt with selinux enabled, but no matter what I try, it's still disabled. After some searching, I've found that:

[libvirt] nested VMs

I tried nesting VM's but the hw virt flags are not passed to the next level QEMU-CPU. What version is this going to be available so we have reasonable acceleration? -Gerry -- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list

Re: [libvirt] How to keep VM definitions in sync across hosts?

2009/11/14 Thomas Treutner tho...@scripty.at: Hi, is there any best-practice how to keep VM definitions in sync across a couple of hosts? Is it reasonable to put /etc/libvirt/qemu/ on a NFS share? Or are there better ways? How does oVirt solve that? There was a similar question some weeks

[libvirt] [PATCH] esx: Fix MAC address formatting

VMware uses two MAC address prefixes: 00:0c:29 and 00:50:56. The 00:0c:29 prefix is used for ESX server generated addresses. The 00:50:56 prefix is split into two parts. MAC addresses above 00:50:56:3f:ff:ff are generated by a vCenter. The rest of the 00:50:56 prefix can be assigned manually. Any

[libvirt] [PATCH] esx: Fix memory leak in esxVI_HostCpuIdInfo_Free()

--- src/esx/esx_vi_types.c |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/src/esx/esx_vi_types.c b/src/esx/esx_vi_types.c index 73d3069..9af9f73 100644 --- a/src/esx/esx_vi_types.c +++ b/src/esx/esx_vi_types.c @@ -1496,6 +1496,7 @@ ESX_VI__TEMPLATE__FREE(HostCpuIdInfo,

[libvirt] [PATCH] esx: Fix CPU clock Hz to MHz conversion

--- src/esx/esx_driver.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/esx/esx_driver.c b/src/esx/esx_driver.c index b84250c..5737fe9 100644 --- a/src/esx/esx_driver.c +++ b/src/esx/esx_driver.c @@ -878,7 +878,7 @@ esxNodeGetInfo(virConnectPtr conn, virNodeInfoPtr

Re: [libvirt] device type 'interface' cannot be attached

Gerry Reno wrote: I'm using libvirt 0.6.2 on F11 x86_64 and CPU supports hw virtualization. When I try to do 'virsh attach-interface ...' I get an error that the function is not supported by the hypervisor device type 'interface' cannot be attached. Is this command not supported? Or is