Am 03.08.2012 17:20, schrieb Peter Krempa:
On 08/03/12 16:35, Michael Beham wrote:
> Hi,
>
> I´m using libvirt version 0.9.12 under Debian Squeeze with and AMD
> Opteron 4280. Executing the virsh capabilities command only show me the
> following flags:
>
> <cpu>
> <arch>x86_64</arch>
> <model>Opteron_G4</model>
> <vendor>AMD</vendor>
> <topology sockets='1' cores='8' threads='2'/>
> <feature name='nodeid_msr'/>
> <feature name='wdt'/>
> <feature name='skinit'/>
> <feature name='ibs'/>
> <feature name='osvw'/>
> <feature name='cr8legacy'/>
> <feature name='extapic'/>
> <feature name='cmp_legacy'/>
> <feature name='fxsr_opt'/>
> <feature name='mmxext'/>
> <feature name='osxsave'/>
> <feature name='monitor'/>
> <feature name='ht'/>
> <feature name='vme'/>
> </cpu>
>
> Should not there be more flags supported by the CPU, for example the
> SVM-Flag for virtualization because executing cat /proc/cpuinfo gives me
> quite a lot of more flags and also the SVM Flag.
The output is correct as libvirt tries to find a "parent" processor
and the flags that are in your output are just flags that your
processor supports and the parent, in this case Opteron G4, doesn't.
Peter
>
> Cheers,
> Mike
>
>
> _______________________________________________
> libvirt-users mailing list
> libvirt-users(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/libvirt-users
>
Hmm sorry , I did not get the point so far!
In the XML-File of the VM I´m using the cpu passthrough attribute so
that most of the flags from the host cpu are available in the VM. So
exectuing cat /proc/cpuinfo in the VM shows exactly the same CPU-model
like on the Host, there are only some flags missing, but for example the
SVM Flag which I need for the Virtualization is listed in the VM and on
the host system too.
So I´m quite confused about the output of virsh capabilities!