On Thu, Mar 15, 2007 at 02:27:04PM +, Daniel P. Berrange wrote:
>
> hvm
>
> 32
> sun4m
> /usr/bin/qemu-system-sparc
>
>
>
>
>
>
>
One thing I forgot to mention is that upstream QEMU recently added a
-cpu flag to allow specifi
On Wed, Mar 14, 2007 at 11:59:57AM +, Richard W.M. Jones wrote:
>
> My thoughts are that capabilities need to return the following
> information about the underlying driver/hypervisor:
>
> * Host CPU flags (1,8)
> * List of guest architectures supported. For each of these:
>- Model of
Richard W.M. Jones wrote:
Example: Xen
vmx
pae
After some discussion with Daniel Veillard, I've evolved this into:
(This reason for this is to be consistent with the features listed in
descriptions).
Daniel P. Berrange wrote:
(4) is_kvm_capable: [Linux] kernel supports kvm? Uses Linux-specific
/dev/kvm
This is really equivalent to the 'is_hvm_capable' check but for KVM.
Just an update on this one for all on the list: We went round several
loops with this, but think we've got a way where
On Wed, Mar 14, 2007 at 11:59:57AM +, Richard W.M. Jones wrote:
> (1) is_pae_capable: host supports PAE? Uses Linux-specific /proc/cpuinfo
This is also arch specific - only relevant for i386/x86_64.
> (2) is_hvm_capable: host supports HVM & enabled in Xen? Uses
> Xen-specific /sys/hypervisor
Lots of people had various things to say about the first capabilities
patches (see thread starting here:
https://www.redhat.com/archives/libvir-list/2007-March/msg00153.html).
So I thought I'd try to pull together ideas into a single thread, and
post some information about what this is trying t
