#offset of 44 seconds so definitely
1 messages · Page 1 of 1 (latest)
It looks like there's an open issue for clock drift on Virtualbox
https://github.com/home-assistant/operating-system/issues/1540
and the offset seems to have settled at +1min 985.485
The workaround seems to be to turn off paravirutalization, but that's going to have a performance impact
a big one? I don't run all that much on it and this is a bigger issue so let me try that
If you're not running all that much it might not be too bad
from the sounds of it
you're using less than 10% CPU
try turning it off LOL
it seems you provisioned more than enough CPU and RAM
yeah just shutting it down now to change that
Probably good for a short to medium term solution. Long term if you stick with HAOS, I'd suggest installing to a machine you can dedicate to it, like a used PC or laptop
I recommend something like a NUC if you can
or maybe moving to something that's not virtualbox when I got time to redo and debug the whole thing could help?
but yes used PC would work
well if you move to another system, you won't have this issue
You can get great used machines in the neighborhood of $100-150
interestingly they actually recommend virtulbox?? but it doesn't work right
so the paravirtualization interface should go to none right?
that wouldn't have been a longstanding issue
and nested paging is fine right?
yeah
booting it up again now
sorry I just had to read the issue to see the sol
yeah seems KVM makes it worse ?
it's odd there's not a guest additions by now
I read that too so I just put it on none
yeah seems thats what people had the best luck with
wait KVM as in the hypervisor or KVM as in the setting?
ah, if this works I'll just keep it this way for a bit until it's either patched or I'll decide if to go new system or jump over to KVM hypervisor and see if that helps
my hypervisor experience is limited to ESXi, and Xen mostly
are those available on mac?
oh would it be plausible to move over from Vbox to that?
well i'm not sure if it's recommended or supported
but it's much better hypervisor than VBox
well I'll take a look at it
I'll have to see about converting the container. not sure if that's possible?
yeah you can, I'm pretty sure you can just import the vbox container as well
but there are ways to convert them
oh perfect, well let's see if this is working and that'll be a project if this bug isn't fixed in a sensible time
okay the 10 second automation seems to be working on time now, let's see the motion sensors 🙂
sensors seem to be working on time now
seems that was the issue.. so when in doubt blame time itself??
so it seems to be alright now. Thanks for your help ❤️
offset is now +15 ms and it's been several minutes, that's an acceptable level right?
Yeah that's fine