summary refs log tree commit diff stats
path: root/results/classifier/gemma3:12b/kvm/1811862
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/gemma3:12b/kvm/1811862')
-rw-r--r--results/classifier/gemma3:12b/kvm/181186239
1 files changed, 39 insertions, 0 deletions
diff --git a/results/classifier/gemma3:12b/kvm/1811862 b/results/classifier/gemma3:12b/kvm/1811862
new file mode 100644
index 000000000..dea9ce4bf
--- /dev/null
+++ b/results/classifier/gemma3:12b/kvm/1811862
@@ -0,0 +1,39 @@
+
+microcode version stays 0x1 even if -cpu host is used
+
+The microcode version of my host cpu has the following version:
+
+grep microcode /proc/cpuinfo | head -1
+microcode       : 0x3d
+
+while trying to run ESXi in an nested VM, the boot bailed out with
+error message that at least microcode version 0x19 is needed. It 
+seems they have introduced such a check on certain CPU types.
+
+The VM in question is using the "host-passthrough" option in libvirt
+and the qemu command line reads as this:
+
+21172 ?        Sl     0:09 /usr/libexec/qemu-kvm -name guest=hpe-env-client1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-33-hpe-env-client1/master-key.aes -machine pc-i440fx-rhel7.6.0,accel=kvm,usb=off,dump-guest-core=off -cpu host <rest stripped>
+
+Running a regular Linux VM with `host-passthrough` shows that the
+microcode version is still reported as 0x1.
+
+Within the VM:
+
+[root@hpe-env-client1 ~]# cat /proc/cpuinfo 
+processor       : 0
+vendor_id       : GenuineIntel
+cpu family      : 6
+model           : 63
+model name      : Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
+stepping        : 2
+microcode       : 0x1
+cpu MHz         : 2397.222
+
+
+My impression is qemu should copy the hosts microcode version in this case?
+
+Running Qemu von RHEl8 beta here.
+
+[root@3parserver ~]# /usr/libexec/qemu-kvm --version
+QEMU emulator version 2.12.0 (qemu-kvm-2.12.0-41.el8+2104+3e32e6f8)
\ No newline at end of file