There's gotta be a way to utilize QEMU 2.3's IvyBridge support under SolusVM rather than just starting the VM with --cpu-host. Seems like I could build QEMU prior to SolusVM and set it's emulator path accordingly. Just seems like, as with OpenVZ, SolusVM's idea of performance is, well, a couple years behind, at least. Not surprised to find myself using the "custom config" option more and more...
[ 0.012925] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.012926] smpboot: CPU0: Intel(R) Xeon(R) CPU E3-1290 V2 @ 3.70GHz (fam: 06, model: 3a, stepping: 09)
[ 0.012936] TSC deadline timer enabled
[ 0.012948] Performance Events: 16-deep LBR, IvyBridge events, Intel PMU driver.
[ 0.013000] ... version: 2
[ 0.013000] ... bit width: 48
[ 0.013000] ... generic registers: 4
[ 0.013000] ... value mask: 0000ffffffffffff
[ 0.013000] ... max period: 000000007fffffff
[ 0.013000] ... fixed-purpose events: 3
[ 0.013000] ... event mask: 000000070000000f
[ 0.013803] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
----------------------------
Code:
[ 0.029793] CPU0: Intel(R) Xeon(R) CPU E5-2650 v2 @ 2.60GHz stepping 04
[ 0.029997] Performance Events: 16-deep LBR, IvyBridge events, Intel PMU driver.
[ 0.029997] ... version: 2
[ 0.029997] ... bit width: 48
[ 0.029997] ... generic registers: 4
[ 0.029997] ... value mask: 0000ffffffffffff
[ 0.029997] ... max period: 000000007fffffff
[ 0.029997] ... fixed-purpose events: 3
[ 0.029997] ... event mask: 000000070000000f
[ 0.034036] NMI watchdog enabled, takes one hw-pmu counter.
[ 0.034207] Booting Node 0, Processors #1
That or it's newer kernel time...