Just to say, working in Proxmox server
I am trying to start it there too. Could you please tell me, where to turn off the time syncing? While system checking in the workstation, I’ve got “kvm-clock tsc hpet acpi_pm detected”.
Unrelated to timesync.
How to turn of this check is already explained in the very message which mentions it. That however doesn’t fix the original reason for the check.
How to fix the root issue? Users won’t be able to fix this. No developers are working on this.
Does it mean, that my Whonix Workstation will have a weakness? Or it’s safe to just turn the check off?
The warning is there on purpose, is correct, not a false-positive.
So, after an year, full of events, I’m here again
And even with solution for PVClock, if someone will need it:
- Edit or create
/etc/pve/virtual-guest/cpu-models.conf
, add there a new CPU type. This simple one will work:
cpu-model: pvclockoff
flags -kvmclock;-tsc
- Then use this CPU in the VM CPU options.
-
ACPI
you can turn off in plain VM options. - I also set to
no
the optionUse local time for RTC
.
Adding flags to qm.conf doesn’t work, you need to create a custom CPU type.
Documentation used:
https://pve.proxmox.com/wiki/Manual:_cpu-models.conf
Possible flags you can find via console: qemu-system-x86_64 -cpu help
I’m open to critique. I’m not a pro in virtualization, so I could easily overlook something.
What I’d really like to see is Whonix LXC container tarballs put up on Turnkey Linux so it would show up as a template in Proxmox. I’ve messed around with OVA’s and QCOW imports and have had troubles over and over.
An LXC container is ideal for Whonix CLI gateway as a separate offering, and then maybe an ISO for the main OS. LXC containers are fast and very lightweight compared to KVM, making it ideal for the gateway at least.
Yeah thats why it needs a contributors for this feature.
Also check:
Unless you are contributing it, this is highly unlikely to happen.