On Fri, Oct 26, 2012 at 10:27 PM, Harsh Prateek Bora
ha...@linux.vnet.ibm.com wrote:
@@ -1624,7 +1626,15 @@
td one of the sheepdog servers (default is localhost:7000)
/td
td zero or one /td
/tr
+ tr
+td gluster /td
+td
On Wed, Sep 5, 2012 at 8:45 PM, Eric Blake ebl...@redhat.com wrote:
On 09/05/2012 09:08 AM, Bharata B Rao wrote:
On Wed, Sep 5, 2012 at 7:03 PM, Jiri Denemark jdene...@redhat.com wrote:
@@ -1042,6 +1043,13 @@
attribute name=port
ref name=unsignedInt
On Wed, Sep 5, 2012 at 7:03 PM, Jiri Denemark jdene...@redhat.com wrote:
@@ -1042,6 +1043,13 @@
attribute name=port
ref name=unsignedInt/
/attribute
+attribute name=transport
+ choice
+
Original patch by Bharata. Updated to use {1,16} in spaprvioReg based
on example from Eric Blake.
Signed-off-by: Bharata B Rao bhar...@linux.vnet.ibm.com
Signed-off-by: Prerna Saxena pre...@linux.vnet.ibm.com
Signed-off-by: Michael Ellerman mich...@ellerman.id.au
---
docs/schemas
On Wed, Dec 07, 2011 at 03:49:59PM +1100, Michael Ellerman wrote:
On Fri, 2011-11-11 at 18:21 +0530, Bharata B Rao wrote:
XML definitions for guest NUMA and parsing routines.
From: Bharata B Rao bhar...@linux.vnet.ibm.com
This patch adds XML definitions for guest NUMA specification
On Thu, Dec 01, 2011 at 01:47:47PM -0500, Stefan Berger wrote:
On 12/01/2011 01:08 PM, Prerna Saxena wrote:
From: Bharata B Raobhar...@linux.vnet.ibm.com
Date: Thu, 1 Dec 2011 21:21:34 +0530
Subject: [PATCH 5/5] Add ppc64 specific definitions to domain.rng
ppc64 as new arch type and pseries
On Fri, Nov 18, 2011 at 11:31:12AM -0700, Eric Blake wrote:
None of the callers cared if str was updated to point to the next
byte after the parsed cpuset; simplifying this results in quite
a few code simplifications. Additionally, virCPUDefParseXML was
strdup()'ing a malloc()'d string;
On Mon, Nov 07, 2011 at 11:35:27AM -0700, Eric Blake wrote:
On 11/06/2011 06:57 AM, Bharata B Rao wrote:
XML definitions for guest NUMA and parsing routines.
From: Bharata B Raobhar...@linux.vnet.ibm.com
This patch adds XML definitions for guest NUMA specification and contains
routines
On Mon, Nov 07, 2011 at 11:47:10AM -0700, Eric Blake wrote:
On 11/06/2011 06:59 AM, Bharata B Rao wrote:
qemu: Generate -numa option
From: Bharata B Raobhar...@linux.vnet.ibm.com
Add routines to generate -numa QEMU command line option based on
numa .../numa XML specifications.
Signed
qemu: Generate -numa option
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Add routines to generate -numa QEMU command line option based on
numa ... /numa XML specifications.
Signed-off-by: Bharata B Rao bhar...@linux.vnet.ibm.com
---
src/conf/cpu_conf.c|3
Hi,
This is v2 of the patchset that adds support for specifying NUMA topology
for guests.
cpu
...
topology sockets='2' cores='4' threads='2'/
numa
cell cpus='0-7' mems='512000'/
cell cpus='8-15' mems='512000'/
/numa
...
/cpu
XML definitions for guest NUMA and parsing routines.
From: Bharata B Rao bhar...@linux.vnet.ibm.com
This patch adds XML definitions for guest NUMA specification and contains
routines to parse the same. The guest NUMA specification looks like this:
cpu
...
topology sockets='2
On Mon, Nov 07, 2011 at 11:12:07AM -0700, Eric Blake wrote:
On 11/06/2011 06:58 AM, Bharata B Rao wrote:
Routine to truncate virBuffer
From: Bharata B Raobhar...@linux.vnet.ibm.com
Add a helper to truncate virBuffer.
/**
* virBufferTruncate:
+++ b/src/util/buf.c
@@ -123,6 +123,31
Routine to truncate virBuffer
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Add a helper to truncate virBuffer.
/**
* virBufferTruncate:
* @buf: the buffer
* @len: number of bytes by which the buffer is truncated
*
* Truncate the buffer by @len bytes.
*
* Returns zero on success or -1
Hi,
This patch series adds support for specifying NUMA topology for guests.
cpu
...
topology sockets='2' cores='4' threads='2'/
numa
cell cpus='0-7' mems='512000'/
cell cpus='8-15' mems='512000'/
/numa
...
/cpu
This change
XML definitions for guest NUMA and parsing routines.
From: Bharata B Rao bhar...@linux.vnet.ibm.com
This patch adds XML definitions for guest NUMA specification and contains
routines to parse the same. The guest NUMA specification looks like this:
cpu
...
topology sockets='2
qemu: Generate -numa option
From: Bharata B Rao bhar...@linux.vnet.ibm.com
Add routines to generate -numa QEMU command line option based on
numa ... /numa XML specifications.
Signed-off-by: Bharata B Rao bhar...@linux.vnet.ibm.com
---
src/qemu/qemu_command.c| 71
On Thu, Oct 13, 2011 at 12:50:00PM +0100, Daniel P. Berrange wrote:
On Mon, Oct 03, 2011 at 03:31:35PM +0530, Bharata B Rao wrote:
Routines to parse numa ... /numa
From: Bharata B Rao bhar...@linux.vnet.ibm.com
This patch adds routines to parse guest numa
XML configuration for qemu
On Thu, Oct 13, 2011 at 12:53:22PM +0100, Daniel P. Berrange wrote:
On Mon, Oct 03, 2011 at 03:28:44PM +0530, Bharata B Rao wrote:
Hi,
I discussed the possibilities of adding NUMA topology XML specification
support for guests here some time back. Since my latest proposal
(http
Add XML definitions for guest NUMA specifications.
From: Bharata B Rao bhar...@linux.vnet.ibm.com
NUMA topology for guest is specified as follows:
cpu
...
numa
node cpus='0-3' mems='1024'
node cpus='4,5,6,7' mems='1024'
node cpus='8-10',11-12^12' mems='1024'
/numa
/cpu
Signed-off-by: Bharata
Hi,
I discussed the possibilities of adding NUMA topology XML specification
support for guests here some time back. Since my latest proposal
(http://permalink.gmane.org/gmane.comp.emulators.libvirt/44626)
didn't get any response, I am posting a prototype implementation
that supports specifying
Routines to parse numa ... /numa
From: Bharata B Rao bhar...@linux.vnet.ibm.com
This patch adds routines to parse guest numa
XML configuration for qemu.
Signed-off-by: Bharata B Rao bhar...@linux.vnet.ibm.com
---
src/conf/cpu_conf.c | 48
src/conf/cpu_conf.h
Hi,
Is there a dependency b/n vcpu and topology ?
Is specifying vcpu mandatory for a SMP guest ?
Can't I skip vcpu but have topology sockets= cores= threads= to
define a SMP guest ?
I see that if I skip vcpu, libvirt generates -smp 1 on qemu command
line which results in qemu booting a VM with
On Tue, Aug 30, 2011 at 10:53 AM, Bharata B Rao bharata@gmail.com wrote:
Hi,
Here is another attempt at guest NUMA topology XML specification that
should work for different NUMA topologies.
Hi Daniel,
Do you think I should go ahead and implement this ? Any comments or concerns
Hi,
Here is another attempt at guest NUMA topology XML specification that
should work for different NUMA topologies.
We already specify the number of sockets, cores and threads a system
has by using:
cpu
topology sockets='2' cores='2' threads='2'
/cpu
For NUMA, we can add the following:
numa
On Tue, Aug 23, 2011 at 7:43 PM, Daniel P. Berrange berra...@redhat.com wrote:
On Fri, Aug 19, 2011 at 12:05:43PM +0530, Bharata B Rao wrote:
Hi,
qemu supports specification of NUMA topology on command line using -numa
option.
-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]
I see
On Fri, Aug 19, 2011 at 7:10 PM, Adam Litke a...@us.ibm.com wrote:
On 08/19/2011 01:35 AM, Bharata B Rao wrote:
...
topology sockets='1' cores='2' threads='1' nodeid='0' cpus='0-1' mem='size'
topology sockets='1' cores='2' threads='1' nodeid='1' cpus='2-3' mem='size'
...
I like the idea
Hi,
qemu supports specification of NUMA topology on command line using -numa option.
-numa node[,mem=size][,cpus=cpu[-cpu]][,nodeid=node]
I see that there is no way to specify such NUMA topology in libvirt
XML. Are there plans to add support for NUMA topology specification ?
Is anybody already
On Fri, Aug 19, 2011 at 12:55 PM, Osier Yang jy...@redhat.com wrote:
于 2011年08月19日 14:35, Bharata B Rao 写道:
How about something like this ? (OPTION 1)
cpu
...
numa nodeid='node' cpus='cpu[-cpu]' mem='size'
...
/cpu
Libvirt already supported NUMA setting (both cpu and memory)
on host
2011/8/19 Bharata B Rao bharata@gmail.com:
Hence I am not sure if if numatune is the right place for defining
host NUMA topology which btw should be independent of the host
^^guest
Sorry for the typo.
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman
2011/8/19 Osier Yang jy...@redhat.com:
Maybe something like:
numatune
guest
..
/guest
/numatune
Yes, one possible solution.
Let me wait and see what others say and what will be the consensus.
Regards,
Bharata.
--
libvir-list mailing list
libvir-list@redhat.com
31 matches
Mail list logo
