Snapshot rollback fails with VBoxManage: error: cpum#1: X86_CPUID_FEATURE_EDX_HTT is not supported by the host but has already exposed to the guest ver=14 pass=final

[davidkarlsen]

See: ​https://github.com/jedi4ever/sahara/issues/34 . Basically snapshot rollback fails bad with the message: VBoxManage: error: cpum#1: X86_CPUID_FEATURE_EDX_HTT is not supported by the host but has already exposed to the guest ver=14 pass=final

The host in question where it fails has cpuflags: -bash-4.1$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz stepping : 7 cpu MHz : 2600.000 cache size : 20480 KB fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss syscall nx rdtscp lm constant_tsc up arch_perfmon pebs bts xtopology tsc_reliable nonstop_tsc aperfmperf unfair_spinlock pni pclmulqdq vmx ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm ida arat xsaveopt pln pts dts tpr_shadow vnmi ept vpid bogomips : 5200.00 clflush size : 64 cache_alignment : 64 address sizes : 40 bits physical, 48 bits virtual power management:

-bash-4.1$

I've tried 4.3.6r91406 and 4.3.10r93012. It's a -bash-4.1$ cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.5 (Santiago) -bash-4.1$ running on vmware.

The same functionality works fine on my laptop which has ht flags: cat /proc/cpuinfo |grep -i HT flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms

also with the same versions of virtualbox: VBoxManage --version 4.3.10r93012

[Frank Mehnert]

Please attach the complete VBox.log file of such a VM session!

[Frank Mehnert]

And did you change the number of virtual CPUs assigned to your guest?

[davidkarlsen]

BIG finding! The .ovf file had 2cpus (seems like a default when it was build with vagrant):

<Hardware version="2">

<CPU count="2" hotplug="false">

<HardwareVirtEx enabled="true"/> <HardwareVirtExNestedPaging enabled="true"/> <HardwareVirtExVPID enabled="true"/> <HardwareVirtExUX enabled="true"/> <PAE enabled="true"/> <HardwareVirtExLargePages enabled="true"/> <HardwareVirtForce enabled="false"/>

</CPU>

I went in and updated it to be CPU count="1" and now it works! I think it's still a bad bug and shouldn't fail badly but rather give a warning, or flip to one cpu when only one avail on the host. But at least there is a way to avoid failing bad.

[aeichner]

Please reopen if still relevant with a recent VirtualBox release.