I have Ventura OSX running on Suse when trying to save session it shows:
Requested operation is not valid: domain has 'invtsc' CPU feature but TSC frequency is not specified
I have Ventura OSX running on Suse when trying to save session it shows:
Requested operation is not valid: domain has 'invtsc' CPU feature but TSC frequency is not specified
@Abuabdellah so what cpu info in the Ventura instance? This may provide some clues: 1839095 – VM fails to migrate between identical hosts not supporting TSC scaling
You switched your system to a kvm machine, or just starting with the qemu script?
How are you ‘saving’ the qemu session?
You switched your system to a kvm machine, or just starting with the qemu script?
From KVM machine.
How are you ‘saving’ the qemu session?
@Abuabdellah can you check the host system cpu flags, run lscpu | grep Flags:
you may need to tweak the flags listed at the bottom of the xml file, there are some alternatives. But also does the system meet the requirements listed in the github page?
How that ?
tarik-mb@localhost:~> lscpu | grep Flags
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 cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm cpuid_fault pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts md_clear flush_l1d
@Abuabdellah so no avx2 flag, not sure if that would cause the issue, can you check your systems journal for tsc?
journalctl -b | grep tsc:
The flag invtsc is added by the script or xml.
دجنبر 23 08:34:44 localhost kernel: tsc: Fast TSC calibration using PIT
دجنبر 23 08:34:44 localhost kernel: tsc: Detected 2494.153 MHz processor
دجنبر 23 08:34:45 localhost kernel: tsc: Refined TSC clocksource calibration: 2494.330 MHz
دجنبر 23 08:34:45 localhost kernel: clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x23f44dae1ab, max_idle_ns: 440795269790 ns
@Abuabdellah that looks fine, I’m assuming that you have other virtual machines and can save those states?
I’m just using the qemu script here, so no saved state. And you have not changed any of the default flags?
I don’t remember but looking for a solution.
If you remove the +invtsc
option, what happens?
I don’t have big experience, where that ?
@Abuabdellah in the xml configuration file at the bottom…
<qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
Once edited, run virt-xml-validate
on the xml to make sure everything is ok.
Without success!
Error saving domain: Requested operation is not valid: domain has ‘invtsc’ CPU feature but TSC frequency is not specified
@Abuabdellah I suspect looking on the net that the Leap version is older than some of the recent patches applied for vmware-cpuid-freq=on
you could try changing that to off and see what happens…
@Abuabdellah very likely it doesn’t use the same flags (+invtsc,vmware-cpuid-freq=on)…
It doesn’t work also!