Tried to migrate a few VMs from existing system to an older host that we
threw in the rack to facilitate some server reshuffling.
Migration complained about lack of capabilities (which I expected its an
older server) but when I looked at what I should throw into the xml file
I got a core2duo when it should have been at least Penryn or something
(Xeon E5345)
Of course the VMs work fine with that cpu def so its not a bit deal at
the moment, but I am still curious
Is it some sort of lookup table bug or is the server BIOS wonky?
-----------------------------------------------------------
OS: Up to date U16 Xenial on an HP DL380 server.
Stock libraries for that distro
libvirt0/xenial-updates,now 1.3.1-1ubuntu10.8 amd64 [installed,automatic]
qemu-kvm/xenial-updates,xenial-security,now 1:2.5+dfsg-5ubuntu10.14
amd64 [installed,automatic]
QEMU Full virtualization
cat /proc/cpu shows
processor : 7
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz
stepping : 11
microcode : 0xb4
cpu MHz : 2333.361
# virsh capabilities
<capabilities>
<host>
<uuid>33393138-3335-5553-4538-31324e39414b</uuid>
<cpu>
<arch>x86_64</arch>
<model>core2duo</model>
<vendor>Intel</vendor>
<topology sockets='2' cores='4'
threads='1'/>
<feature name='lahf_lm'/>
<feature name='dca'/>
<feature name='pdcm'/>
<feature name='xtpr'/>
<feature name='cx16'/>
<feature name='tm2'/>
<feature name='est'/>
<feature name='vmx'/>
<feature name='ds_cpl'/>
<feature name='dtes64'/>
<feature name='pbe'/>
<feature name='tm'/>
<feature name='ht'/>
<feature name='ss'/>
<feature name='acpi'/>
<feature name='ds'/>
<pages unit='KiB' size='4'/>
<pages unit='KiB' size='2048'/>
</cpu>
<power_management>
<suspend_mem/>
<suspend_disk/>
<suspend_hybrid/>
</power_management>
<migration_features>
<live/>
<uri_transports>
<uri_transport>tcp</uri_transport>
<uri_transport>rdma</uri_transport>
</uri_transports>
</migration_features>
<topology>
<cells num='1'>
<cell id='0'>
<memory unit='KiB'>32945368</memory>
<pages unit='KiB'
size='4'>8236342</pages>
<pages unit='KiB' size='2048'>0</pages>
<distances>
<sibling id='0' value='10'/>
</distances>
<cpus num='8'>
<cpu id='0' socket_id='0' core_id='0'
siblings='0'/>
<cpu id='1' socket_id='1' core_id='0'
siblings='1'/>
<cpu id='2' socket_id='0' core_id='2'
siblings='2'/>
<cpu id='3' socket_id='1' core_id='2'
siblings='3'/>
<cpu id='4' socket_id='0' core_id='1'
siblings='4'/>
<cpu id='5' socket_id='1' core_id='1'
siblings='5'/>
<cpu id='6' socket_id='0' core_id='3'
siblings='6'/>
<cpu id='7' socket_id='1' core_id='3'
siblings='7'/>
</cpus>
</cell>
</cells>
</topology>
Martin Kletzander
2017-May-23 08:39 UTC
Re: [libvirt-users] Odd Virsh Capabilities response
On Mon, May 22, 2017 at 05:03:21PM -0700, W Kern wrote:>Tried to migrate a few VMs from existing system to an older host that we >threw in the rack to facilitate some server reshuffling. > >Migration complained about lack of capabilities (which I expected its an >older server) but when I looked at what I should throw into the xml file >I got a core2duo when it should have been at least Penryn or something >(Xeon E5345) >According to wikipedia: https://en.wikipedia.org/wiki/Xeon#5300-series_.22Clovertown.22 the microarchitecture is Core, not anything newer. Looking at the capabilities, it could also be Conroe, it even has the same family and model. But it has the same number of matching features for botha nd core2duo is older so it's closer to the start of the list. There was some refactoring of the CPU matching, but that's not going to be in a libvirt released 1 year and 4 months ago. Currently it should tell you 'Conroe' with the latest release (3.3.0), IIUC. However it's worth noting that this is just a string in an XML. There is no functionality depending on that model name.>Of course the VMs work fine with that cpu def so its not a bit deal at >the moment, but I am still curious > >Is it some sort of lookup table bug or is the server BIOS wonky? > >----------------------------------------------------------- > >OS: Up to date U16 Xenial on an HP DL380 server. > >Stock libraries for that distro > >libvirt0/xenial-updates,now 1.3.1-1ubuntu10.8 amd64 [installed,automatic] > >qemu-kvm/xenial-updates,xenial-security,now 1:2.5+dfsg-5ubuntu10.14 >amd64 [installed,automatic] > QEMU Full virtualization > >cat /proc/cpu shows > >processor : 7 >vendor_id : GenuineIntel >cpu family : 6 >model : 15 >model name : Intel(R) Xeon(R) CPU E5345 @ 2.33GHz >stepping : 11 >microcode : 0xb4 >cpu MHz : 2333.361 > ># virsh capabilities > ><capabilities> > > <host> > <uuid>33393138-3335-5553-4538-31324e39414b</uuid> > <cpu> > <arch>x86_64</arch> > <model>core2duo</model> > <vendor>Intel</vendor> > <topology sockets='2' cores='4' threads='1'/> > <feature name='lahf_lm'/> > <feature name='dca'/> > <feature name='pdcm'/> > <feature name='xtpr'/> > <feature name='cx16'/> > <feature name='tm2'/> > <feature name='est'/> > <feature name='vmx'/> > <feature name='ds_cpl'/> > <feature name='dtes64'/> > <feature name='pbe'/> > <feature name='tm'/> > <feature name='ht'/> > <feature name='ss'/> > <feature name='acpi'/> > <feature name='ds'/> > <pages unit='KiB' size='4'/> > <pages unit='KiB' size='2048'/> > </cpu> > <power_management> > <suspend_mem/> > <suspend_disk/> > <suspend_hybrid/> > </power_management> > <migration_features> > <live/> > <uri_transports> > <uri_transport>tcp</uri_transport> > <uri_transport>rdma</uri_transport> > </uri_transports> > </migration_features> > <topology> > <cells num='1'> > <cell id='0'> > <memory unit='KiB'>32945368</memory> > <pages unit='KiB' size='4'>8236342</pages> > <pages unit='KiB' size='2048'>0</pages> > <distances> > <sibling id='0' value='10'/> > </distances> > <cpus num='8'> > <cpu id='0' socket_id='0' core_id='0' siblings='0'/> > <cpu id='1' socket_id='1' core_id='0' siblings='1'/> > <cpu id='2' socket_id='0' core_id='2' siblings='2'/> > <cpu id='3' socket_id='1' core_id='2' siblings='3'/> > <cpu id='4' socket_id='0' core_id='1' siblings='4'/> > <cpu id='5' socket_id='1' core_id='1' siblings='5'/> > <cpu id='6' socket_id='0' core_id='3' siblings='6'/> > <cpu id='7' socket_id='1' core_id='3' siblings='7'/> > </cpus> > </cell> > </cells> > </topology> > > > >_______________________________________________ >libvirt-users mailing list >libvirt-users@redhat.com >https://www.redhat.com/mailman/listinfo/libvirt-users
On 5/23/2017 1:39 AM, Martin Kletzander wrote:> > According to wikipedia: > > https://en.wikipedia.org/wiki/Xeon#5300-series_.22Clovertown.22 > > the microarchitecture is Core, not anything newer.> > Looking at the capabilities, it could also be Conroe, it even has the > same family and model. But it has the same number of matching features > for botha nd core2duo is older so it's closer to the start of the list.OK, Mystery solved. It would be nice if it had picked Conroe to avoid confusion, but that is ancient kit and as you point out the capabilities are the same, so there would be no need to change anything Sorry for the noise <grin> -bill