I want to give my kvm guests the freedom to have an independent RTC value
I want to give my kvm guests the freedom to have independent RTC value, in a way they can set the clock value in easy, true virtualized way. I don't want to use 'localtime' or 'adjustment'(variable) of libvert.
I tried this but it goes away after a power-off, Can you make OpenNebula keep the RTC value after a power-off?
RAW = [
TYPE = "kvm",
DATA = "<clock offset='variable'>
<timer name='rtc' tickpolicy='catchup' track='guest'>
<catchup threshold='123' slew='120' limit='10000'/>
It all stems from the Windowses storing local time into the motherboards.
#2 Updated by Gunwoo Gim over 4 years ago
Ruben S. Montero wrote:
Do you mean that you are losing the RAW data when the VM is powered-off?
I'm sorry for not clarifying it enough, I meant the RTC time value is lost when the vm goes to power-off state; so after I resume the VM I see the windows' local time set to the UTC even if I have set it to the local time before the power-off.
#4 Updated by Gunwoo Gim about 4 years ago
Hi, sorry for the curt text.
I don't really know well about the libvirt and virsh but I guess virsh would keep the RTC value until it 'destorys' a VM. however I think opennebula has the virsh-on the host- destroy the VM when it gets a VM into 'power-off' state so the RTC value would be lost.
I guess opennebula would have to do something to prevent the loss of RTC value.
Wish the best,