[libvirt] Re: BUG REPORT: -net tap, fd=X does not work correctly in kvm-86

2009-05-22 Thread Anthony Liguori
Josh Wilsdon wrote: We are doing work with libvirt 0.6.3 through which we have started virtual machines. Using the same "create" command with the same storage, the same everything else this configuration works with both kvm-84 and kvm-85. When I built a fresh version of kvm-86 this stopped work

[libvirt] error: failed to connect to the hypervisor

2009-05-22 Thread Erkan Unal
Hi, I installed the libvirt with the following configure options as an unprivileged user, I am planning to use it just for qemu/kvm: ./configure --without-xen --without-lxc --without-uml --without-openvz --without-vbox --without-numactl --prefix=/some/nonstandard/dir make make install --

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-22 Thread Matthias Bolte
2009/5/22 Daniel P. Berrange : > Actually QEMU, KVM, Xen PV, Xen FV all  follow the same model, providing > you have the balloon driver available in the guest. 'maxmem', confusingly > calling in the XML sets the maximum possible memory  for the > guest, as exposed in e820 maps. When the guest runs

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-22 Thread Daniel P. Berrange
On Thu, May 21, 2009 at 08:37:18PM +0200, Chris Lalancette wrote: > Matthias Bolte wrote: > > Hello, > > > > I just took a look at the driver functions for SetMaxMemory and > > SetMemory, as they are not implemented yet for the ESX driver and > > Daniel Veillard was a bit surprised that they are m

Re: [libvirt] SetMaxMemory vs. SetMemory

2009-05-22 Thread Daniel Veillard
On Thu, May 21, 2009 at 10:39:03PM +0200, Matthias Bolte wrote: > 2009/5/21 Chris Lalancette : > > Well, this is because of a peculiarity with Xen PV domains.  In Xen PV > > guests, > > you specify a "maxmem" and a "memory" parameter in the configuration file.   > > The > > "maxmem" parameter is p

Re: [libvirt] PATCH: Ensure filename/funcname/linenr gets passed to error func

2009-05-22 Thread Daniel Veillard
On Thu, May 21, 2009 at 04:16:31PM +0100, Daniel P. Berrange wrote: > The current virRaiseError() function does not accept any information about > these source location of the error. The various virReportSystemError and > virReportOOMError wrappers all collect this info, but then discard it. Ah,

Re: [libvirt] storage: inconsistent in 'format' scheme between document and implementation

2009-05-22 Thread Daniel Veillard
On Thu, May 21, 2009 at 11:05:15AM +0100, Daniel P. Berrange wrote: > On Thu, May 21, 2009 at 10:46:11AM +0200, Daniel Veillard wrote: > > On Thu, May 21, 2009 at 05:25:35PM +0900, Ryota Ozaki wrote: > > > Yes, I also checked that. > > > > > > BTW, is the schema file used by libvirtd or drivers? T