On Wed, May 09, 2012 at 11:08:13PM -0600, Jim Fehlig wrote:
Hi,
I've been tinkering with improving Xen support in the libvirt driver and
wanted to discuss a few issues before submitting patches.
Even the latest upstream release of Xen (4.1.x) contains a rather old
qemu, version 0.10.2,
Il 10/05/2012 07:08, Jim Fehlig ha scritto:
Hi,
I've been tinkering with improving Xen support in the libvirt driver and
wanted to discuss a few issues before submitting patches.
Even the latest upstream release of Xen (4.1.x) contains a rather old
qemu, version 0.10.2, which rejects qcow2
On Thu, May 10, 2012 at 09:06:58AM +0100, Daniel P. Berrange wrote:
On Wed, May 09, 2012 at 11:08:13PM -0600, Jim Fehlig wrote:
Hi,
I've been tinkering with improving Xen support in the libvirt driver and
wanted to discuss a few issues before submitting patches.
Even the latest
On Thu 10 May 2012 (10:41), Muriel wrote:
If I remember correctly, the qcow images are not the only problem
with xen, but I'm far from the code for too long time. In the past
(diablo), the method for counting the ram (and cpu perhaps?) did not
work with xen and this affected the choices of the
Il 10/05/2012 11:48, Alvaro Lopez ha scritto:
On Thu 10 May 2012 (10:41), Muriel wrote:
If I remember correctly, the qcow images are not the only problem
with xen, but I'm far from the code for too long time. In the past
(diablo), the method for counting the ram (and cpu perhaps?) did not
work
On Thu, May 10, 2012 at 03:17:59PM +0200, Muriel wrote:
Il 10/05/2012 11:48, Alvaro Lopez ha scritto:
On Thu 10 May 2012 (10:41), Muriel wrote:
If I remember correctly, the qcow images are not the only problem
with xen, but I'm far from the code for too long time. In the past
(diablo), the
On Thu 10 May 2012 (15:17), Muriel wrote:
Great! But there is a reason if are you using /proc/meminfo instead
of getInfo when calculating the memory used?
You know if there is a way to get, using libvirt, the reserved
memory for dom0? Or the only solution is to read the configuration
file of
Il 10/05/2012 16:08, Alvaro Lopez ha scritto:
On Thu 10 May 2012 (15:17), Muriel wrote:
Great! But there is a reason if are you using /proc/meminfo instead
of getInfo when calculating the memory used?
You know if there is a way to get, using libvirt, the reserved
memory for dom0? Or the only
On Thu 10 May 2012 (17:33), Muriel wrote:
I messed up the question: if you consider the case where the memory
is limited (dom0_mem) the value of MemTotal in meminfo is wrong. Do
you think it makes sense to take the total memory value from libvirt
and from meminfo the rest?
Thus it should work
On May 10, 2012, at 1:56 AM, Daniel P. Berrange wrote:
On Thu, May 10, 2012 at 09:06:58AM +0100, Daniel P. Berrange wrote:
I had a quick chat with Kevin Wolf who's the upstream QEMU qcow2 maintainer
and he said that 64k is the current recommended cluster size for qcow2.
Above this size,
On May 9, 2012, at 10:08 PM, Jim Fehlig wrote:
Hi,
I've been tinkering with improving Xen support in the libvirt driver and
wanted to discuss a few issues before submitting patches.
Awesome!
Even the latest upstream release of Xen (4.1.x) contains a rather old
qemu, version 0.10.2,
Hi,
I've been tinkering with improving Xen support in the libvirt driver and
wanted to discuss a few issues before submitting patches.
Even the latest upstream release of Xen (4.1.x) contains a rather old
qemu, version 0.10.2, which rejects qcow2 images with cluster size
64K. The libvirt
12 matches
Mail list logo
