On Thu, Mar 22, 2012 at 03:01:17PM -0500, Anthony Liguori wrote:
On 03/22/2012 12:14 PM, Eduardo Habkost wrote:
On Thu, Mar 22, 2012 at 11:37:39AM -0500, Anthony Liguori wrote:
On 03/22/2012 04:32 AM, Gleb Natapov wrote:
On Tue, Mar 13, 2012 at 11:53:19AM -0300, Eduardo Habkost wrote:
So,
On Thu, Mar 22, 2012 at 12:50:18PM -0300, Eduardo Habkost wrote:
On Thu, Mar 22, 2012 at 04:30:55PM +0200, Gleb Natapov wrote:
On Thu, Mar 22, 2012 at 10:31:21AM -0300, Eduardo Habkost wrote:
On Thu, Mar 22, 2012 at 11:32:44AM +0200, Gleb Natapov wrote:
What does this mean? Will
On 03/25/2012 04:49 AM, Gleb Natapov wrote:
On Thu, Mar 22, 2012 at 03:01:17PM -0500, Anthony Liguori wrote:
So let's avoid that and start by having a positive configuration
mechanism that the user can use to change the path and exclude it.
My suggestion eliminate the need for two future
On 03/25/2012 02:55 PM, Anthony Liguori wrote:
If cpu models are not part of configuration they should not be affected
by configuration mechanism. You are just avoiding addressing the real
question that if asked above.
I think you're just refusing to listen.
The stated direction of QEMU,
On 03/25/2012 08:08 AM, Avi Kivity wrote:
On 03/25/2012 02:55 PM, Anthony Liguori wrote:
If cpu models are not part of configuration they should not be affected
by configuration mechanism. You are just avoiding addressing the real
question that if asked above.
I think you're just refusing to
On 03/25/2012 03:12 PM, Anthony Liguori wrote:
qemu -M pc
Would effectively be short hand for -readconfig
/usr/share/qemu/machines/pc.cfg
In that case
qemu -cpu westmere
is shorthand for -readconfig /usr/share/qemu/cpus/westmere.cfg.
This is not a bad suggestion, although it would
On 03/11/2012 04:12 PM, Anthony Liguori wrote:
Let me elaborate about the later. Suppose host CPU has kill_guest
feature and at the time a guest was installed it was not implemented by
kvm. Since it was not implemented by kvm it was not present in vcpu
during installation and the guest didn't
On 03/25/2012 08:14 AM, Avi Kivity wrote:
On 03/25/2012 03:12 PM, Anthony Liguori wrote:
qemu -M pc
Would effectively be short hand for -readconfig
/usr/share/qemu/machines/pc.cfg
In that case
qemu -cpu westmere
is shorthand for -readconfig /usr/share/qemu/cpus/westmere.cfg.
This is
On 03/25/2012 08:21 AM, Avi Kivity wrote:
On 03/11/2012 04:12 PM, Anthony Liguori wrote:
This discussion isn't about whether QEMU should have a Westmere
processor definition. In fact, I think I already applied that patch.
It's a discussion about how we handle this up and down the stack.
The
On 03/25/2012 03:22 PM, Anthony Liguori wrote:
In that case
qemu -cpu westmere
is shorthand for -readconfig /usr/share/qemu/cpus/westmere.cfg.
This is not a bad suggestion, although it would make -cpu ? a bit
awkward. Do you see an advantage to this over having
On 03/23/2012 12:29 PM, Li Zhang wrote:
On Fedora16 or above, qemu is supported now. So it is added
in rpm packaging.
Signed-off-by: Li Zhangzhlci...@linux.vnet.ibm.com
---
libvirt.spec.in |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libvirt.spec.in
On 03/25/2012 10:10 AM, Li Zhang wrote:
On 03/23/2012 12:29 PM, Li Zhang wrote:
On Fedora16 or above, qemu is supported now. So it is added
in rpm packaging.
Signed-off-by: Li Zhangzhlci...@linux.vnet.ibm.com
---
libvirt.spec.in |4 ++--
1 files changed, 2 insertions(+), 2
On 03/25/2012 08:34 AM, Avi Kivity wrote:
On 03/25/2012 03:22 PM, Anthony Liguori wrote:
In that case
qemu -cpu westmere
is shorthand for -readconfig /usr/share/qemu/cpus/westmere.cfg.
This is not a bad suggestion, although it would make -cpu ? a bit
awkward. Do you see an advantage
On 03/25/2012 10:24 PM, Laine Stump wrote:
On 03/25/2012 10:10 AM, Li Zhang wrote:
On 03/23/2012 12:29 PM, Li Zhang wrote:
On Fedora16 or above, qemu is supported now. So it is added
in rpm packaging.
Signed-off-by: Li Zhangzhlci...@linux.vnet.ibm.com
---
libvirt.spec.in |4 ++--
1
On 03/25/2012 04:36 PM, Anthony Liguori wrote:
Apart from the command line length, it confuses configuration with
definition.
There is no distinction with what we have today. Our configuration
file basically corresponds to command line options and as there is no
distinction in command line
On Sun, Mar 25, 2012 at 03:14:56PM +0200, Avi Kivity wrote:
On 03/25/2012 03:12 PM, Anthony Liguori wrote:
qemu -M pc
Would effectively be short hand for -readconfig
/usr/share/qemu/machines/pc.cfg
In that case
qemu -cpu westmere
is shorthand for -readconfig
On 03/25/2012 09:46 AM, Avi Kivity wrote:
On 03/25/2012 04:36 PM, Anthony Liguori wrote:
Apart from the command line length, it confuses configuration with
definition.
There is no distinction with what we have today. Our configuration
file basically corresponds to command line options and
On 03/25/2012 09:58 AM, Gleb Natapov wrote:
On Sun, Mar 25, 2012 at 03:14:56PM +0200, Avi Kivity wrote:
On 03/25/2012 03:12 PM, Anthony Liguori wrote:
qemu -M pc
Would effectively be short hand for -readconfig
/usr/share/qemu/machines/pc.cfg
In that case
qemu -cpu westmere
is shorthand
On 03/25/2012 04:59 PM, Anthony Liguori wrote:
On 03/25/2012 09:46 AM, Avi Kivity wrote:
On 03/25/2012 04:36 PM, Anthony Liguori wrote:
Apart from the command line length, it confuses configuration with
definition.
There is no distinction with what we have today. Our configuration
file
On 03/25/2012 05:07 PM, Anthony Liguori wrote:
As log as qemu -nodefconfig -cpu westmere -M pc1.1
-nodefconfig is going to eventually mean that -cpu westmere and -M
pc-1.1 will not work.
This is where QEMU is going. There is no reason that a normal user
should ever use -nodefconfig.
I
On 03/25/2012 10:16 AM, Avi Kivity wrote:
On 03/25/2012 04:59 PM, Anthony Liguori wrote:
On 03/25/2012 09:46 AM, Avi Kivity wrote:
On 03/25/2012 04:36 PM, Anthony Liguori wrote:
Apart from the command line length, it confuses configuration with
definition.
There is no distinction with what
On 03/25/2012 10:18 AM, Avi Kivity wrote:
On 03/25/2012 05:07 PM, Anthony Liguori wrote:
As log as qemu -nodefconfig -cpu westmere -M pc1.1
-nodefconfig is going to eventually mean that -cpu westmere and -M
pc-1.1 will not work.
This is where QEMU is going. There is no reason that a normal
On 03/25/2012 05:26 PM, Anthony Liguori wrote:
Put the emphasis around *configuration*.
So how about:
1) Load ['@SYSCONFDIR@/qemu/qemu.cfg',
'@SYSCONFDIR@/qemu/target-@ARCH@.cfg',
'@DATADIR@/system.cfg', '@DATADIR@/system-@ARCH@.cfg']
2) system-@ARCH@.cfg will contain:
On 03/25/2012 05:30 PM, Anthony Liguori wrote:
On 03/25/2012 10:18 AM, Avi Kivity wrote:
On 03/25/2012 05:07 PM, Anthony Liguori wrote:
As log as qemu -nodefconfig -cpu westmere -M pc1.1
-nodefconfig is going to eventually mean that -cpu westmere and -M
pc-1.1 will not work.
This is where
On 03/25/2012 03:26 PM, Anthony Liguori wrote:
We would continue to have Westmere/etc in QEMU exposed as part of the
user configuration. But I don't think it makes a lot of sense to have
to modify QEMU any time a new CPU comes out.
We have to. New features often come with new MSRs which
On 03/25/2012 10:45 AM, Avi Kivity wrote:
On 03/25/2012 05:30 PM, Anthony Liguori wrote:
On 03/25/2012 10:18 AM, Avi Kivity wrote:
On 03/25/2012 05:07 PM, Anthony Liguori wrote:
As log as qemu -nodefconfig -cpu westmere -M pc1.1
-nodefconfig is going to eventually mean that -cpu westmere
On 03/25/2012 10:40 AM, Avi Kivity wrote:
On 03/25/2012 05:26 PM, Anthony Liguori wrote:
Put the emphasis around *configuration*.
So how about:
1) Load ['@SYSCONFDIR@/qemu/qemu.cfg',
'@SYSCONFDIR@/qemu/target-@ARCH@.cfg',
'@DATADIR@/system.cfg', '@DATADIR@/system-@ARCH@.cfg']
2)
On 03/25/2012 08:01 PM, Anthony Liguori wrote:
I don't think this came out of happiness, but despair. Seriously,
keeping compatibility is one of the things we work hardest to achieve,
and we can't manage it for our command line?
I hate to burst your bubble, but we struggle and rarely
As scheduled, we are entering the freeze for 0.9.11.
I think most API additions are now commited to git upstream (please
raise your voice quickly if you see something missing !)
I have made a release candidate 1 tarball (and associated rpms) at
On 2012年03月23日 15:34, Martin Kletzander wrote:
After cleanup introduced with previous commit, there is a need for
syntax-check rule taking care of return(). Regexp used in 'prohibit'
parameter is taken from the cleanup commit and modified so it fits
'grep -E' format. Semicolon at the end is
Hi all,
I have a query regarding the external snapshot in qcow2 also known as
backing file.
In qemu I created a external snapshot and then create its xml in order
to boot it from VIRSH. But that is complex process.
I want to know whether there is any command in LIBVIRT which can create
31 matches
Mail list logo
