]> git.ipfire.org Git - thirdparty/libvirt.git/commit
bhyve: workaround for the lack of UTC clock on ARM64
authorRoman Bogorodskiy <bogorodskiy@gmail.com>
Tue, 13 Jan 2026 18:30:23 +0000 (19:30 +0100)
committerRoman Bogorodskiy <bogorodskiy@gmail.com>
Mon, 19 Jan 2026 18:27:39 +0000 (19:27 +0100)
commite0dcf278af4a605d2b1178633809c495c1880381
tree4446ee8a1b4c05e25d310b9f26e7023f820446c0
parent7b889af2d235d3fadfc172f371f02df0b74e40f2
bhyve: workaround for the lack of UTC clock on ARM64

Currently, bhyve does not support UTC clock offset on ARM64.
However, when <clock offset= > is not specified in the domain XML,
UTC offset is used by default. That results in an incorrect
configuration for the bhyve ARM64 guests by default.

Workaround is to extend bhyveDomainDefPostParse() to fall back
to the LOCALTIME clock offset when UTC clock offset is not
supported by bhyve.

Signed-off-by: Roman Bogorodskiy <bogorodskiy@gmail.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
src/bhyve/bhyve_domain.c
tests/bhyvexml2argvdata/aarch64/bhyvexml2argv-base.args
tests/bhyvexml2argvdata/aarch64/bhyvexml2argv-bootloader.args
tests/bhyvexml2argvdata/aarch64/bhyvexml2argv-console.args
tests/bhyvexml2argvtest.c
tests/bhyvexml2xmloutdata/aarch64/bhyvexml2xmlout-base.xml
tests/bhyvexml2xmloutdata/aarch64/bhyvexml2xmlout-bootloader.xml
tests/bhyvexml2xmloutdata/aarch64/bhyvexml2xmlout-console.xml
tests/bhyvexml2xmltest.c