2009/5/27 Evan Borgstrom evan-libv...@fatbox.ca
Hi,
I have a machine running 4 OpenVZ VE's and am looking at libvirt as a
management tool.
My machine is a Sun Fire X2250 with 1 CPU and 4GB of RAM running Gentoo.
When I start libvirtd the output below appears in the dmesg output and the
On Tue, May 26, 2009 at 04:26:36PM +0200, Ruben S. Montero wrote:
Hi,
Probably the easiest way to solve this is to get rid to of the
OpenNebula client library. So we do not have the license issue and, as
Daniel said, we do not have to include the C++ dependencies.
We'll try to send the
Hi Daniel,
Right now most of us are out of the office, so we will be able to send
the patches by next week. Sorry for this delay :(
Ruben
On Wed, May 27, 2009 at 10:45 AM, Daniel Veillard veill...@redhat.com wrote:
On Tue, May 26, 2009 at 04:26:36PM +0200, Ruben S. Montero wrote:
Hi,
Currently, even though all the logging functions get given the source
function and line number, it is just discarded unless priority == DEBUG.
As an example, run virsh with logging enabled, and a bogus URI
LIBVIRT_DEBUG=1 LIBVIRT_LOG_OUTPUTS=1:stderr virsh -c foo://bar
13:12:06.252: debug :
When running QEMU with a type=bridge or type=network interface config,
we pass a pre-created TAP device file descriptor, eg
-net tap,fd=17,script=,vlan=0,ifname=vnet0
The ifname and script args have always been ignored by all QEMU versions
we support. Latest QEMU will now error out if they
When the libvirtd daemon starts up, it reads all config files from
/etc/libvirt/qemu. For each config file loaded, it then probes for
a pidfile / live status XML config in /var/run/libvirt/qemu.
In retrospect there is an obvious problem with this approach: it misses
all transient VMs which
Here is a document describing the process for extending the libvirt
API. Note that the patch includes 8 sample patches that go with the
document that should be included in and not applied to the tree.
Dave
--
Libvir-list mailing list
Libvir-list@redhat.com
On Wed, May 27, 2009 at 01:08:04PM -0400, David Allan wrote:
create mode 100644 docs/api_extension/API_implementation_guide.txt
Nice idea - how'd you actually like to turn this into HTML
and wire it into our website ? I think it'd be nice to
create a new 'libvirt internals' section in the
