On 26.01.2010, at 07:49, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
KVM Hardware Inquiry Tool
One of the things I have on my todo list is a tool you can run on your machine
that tells you which virtualization features it supports. Imaginary output of
On 01/26/2010 03:09 AM, Alexander Graf wrote:
On 26.01.2010, at 07:49, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
KVM Hardware Inquiry Tool
Avi beat you to it ;-) See vmxcap in the tree.
One of the things I have on my todo list is a
On 01/26/2010 03:11 PM, Anthony Liguori wrote:
On 01/26/2010 03:09 AM, Alexander Graf wrote:
On 26.01.2010, at 07:49, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
KVM Hardware Inquiry Tool
Avi beat you to it ;-) See vmxcap in the tree.
I knew I
On 26.01.2010, at 14:11, Anthony Liguori wrote:
On 01/26/2010 03:09 AM, Alexander Graf wrote:
On 26.01.2010, at 07:49, Chris Wright wrote:
Please send in any agenda items you are interested in covering.
KVM Hardware Inquiry Tool
Avi beat you to it ;-) See vmxcap in the
On 01/26/2010 03:18 PM, Alexander Graf wrote:
The main question is where does it belong?
a) built into qemu
b) built as separate tool, but shipped with qemu
c) completely separate
I'm personally leaning towards a. That way we can reuse the detection code and
give help when an option is used
On Tue, Jan 26, 2010 at 03:24:50PM +0200, Avi Kivity wrote:
On 01/26/2010 03:18 PM, Alexander Graf wrote:
The main question is where does it belong?
a) built into qemu
b) built as separate tool, but shipped with qemu
c) completely separate
I'm personally leaning towards a. That way we
On 26.01.2010, at 14:33, Daniel P. Berrange wrote:
On Tue, Jan 26, 2010 at 03:24:50PM +0200, Avi Kivity wrote:
On 01/26/2010 03:18 PM, Alexander Graf wrote:
The main question is where does it belong?
a) built into qemu
b) built as separate tool, but shipped with qemu
c) completely
On 01/26/2010 03:33 PM, Daniel P. Berrange wrote:
Me too, especially as the whole stack is involved, and qemu is the
topmost part from our perspective (no doubt libvirt will want to
integrate that functionality as well).
FYI, libvirt already exposes this kind of functionality. The API
On 01/26/2010 07:24 AM, Avi Kivity wrote:
On 01/26/2010 03:18 PM, Alexander Graf wrote:
The main question is where does it belong?
a) built into qemu
b) built as separate tool, but shipped with qemu
c) completely separate
I'm personally leaning towards a. That way we can reuse the detection
On 01/26/2010 04:13 PM, Anthony Liguori wrote:
Me too, especially as the whole stack is involved, and qemu is the
topmost part from our perspective (no doubt libvirt will want to
integrate that functionality as well).
I'm not sure I agree. It would use no code from qemu and really
benefit
On 01/26/2010 08:15 AM, Avi Kivity wrote:
On 01/26/2010 04:13 PM, Anthony Liguori wrote:
Me too, especially as the whole stack is involved, and qemu is the
topmost part from our perspective (no doubt libvirt will want to
integrate that functionality as well).
I'm not sure I agree. It would
On 01/26/2010 04:22 PM, Anthony Liguori wrote:
On 01/26/2010 08:15 AM, Avi Kivity wrote:
On 01/26/2010 04:13 PM, Anthony Liguori wrote:
Me too, especially as the whole stack is involved, and qemu is the
topmost part from our perspective (no doubt libvirt will want to
integrate that
On 01/26/2010 08:26 AM, Avi Kivity wrote:
On 01/26/2010 04:22 PM, Anthony Liguori wrote:
On 01/26/2010 08:15 AM, Avi Kivity wrote:
On 01/26/2010 04:13 PM, Anthony Liguori wrote:
Me too, especially as the whole stack is involved, and qemu is the
topmost part from our perspective (no doubt
On 01/26/2010 04:32 PM, Anthony Liguori wrote:
It would need to know which cpuid bits qemu supports. Only qemu
knows that.
I'm not sure I understand why. Can you elaborate?
If qemu doesn't recognize -cpu qemu64,+nx, then no amount of hardware
and kvm.ko support will allow the user to
On 01/26/2010 04:42 PM, Anthony Liguori wrote:
On 01/26/2010 08:37 AM, Avi Kivity wrote:
People who use discovery tools are probably setting up a migration
cluster. They aren't going to use -cpu host.
BTW, it might be neat to introduce a qemu command line that runs a
monitor command and
On 01/26/2010 04:42 PM, Alexander Graf wrote:
That's /proc/cpuinfo, we should just extend it, maybe that's what Alex meant,
but I'd like to see something more capable.
I think we're all looking at different use-cases.
First and frontmost the one type of user I'm concerned with in this
On 26.01.2010, at 15:47, Avi Kivity wrote:
On 01/26/2010 04:42 PM, Alexander Graf wrote:
That's /proc/cpuinfo, we should just extend it, maybe that's what Alex
meant, but I'd like to see something more capable.
I think we're all looking at different use-cases.
First and frontmost
On 01/26/2010 08:50 AM, Alexander Graf wrote:
On 26.01.2010, at 15:47, Avi Kivity wrote:
On 01/26/2010 04:42 PM, Alexander Graf wrote:
That's /proc/cpuinfo, we should just extend it, maybe that's what Alex meant,
but I'd like to see something more capable.
I
18 matches
Mail list logo