-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timesync: Fix automatic vsock device creation #191
Conversation
so the vsock config should be part of virtualMachineConfig before calling |
I've added this to the commit log to make it clearer. |
Since we are thinking about using crc-org/crc#4341 (comment) way for timesync should we try that and drop it completely from this repo? |
After we add |
@cfergeau commit log has some file listings, that i guess got pasted while amending commit, could you please remove that |
Timesync uses a vsock port for guest/host time synchronization. When timesync is in use, if the VM has no vsock device, a new one is automatically added. However this got broken in commit a5db53d as we are generating the hypervisor configuration before adding this device. The vsock device must be part of `virtualMachineConfig` before calling `cfg.SetSocketDevicesVirtualMachineConfiguration(cfg.socketDevicesConfiguration)`, and after this commit, the vsock device is only added to `virtualMachineConfig` afterwards. This means the timesync only worked if you had another vsock device configured. This fixes crc-org#190 Signed-off-by: Christophe Fergeau <cfergeau@redhat.com>
hrm yes, happens more often than not because of some broken process on my end. Fixed now. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: anjannath The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Timesync uses a vsock port for guest/host time synchronization.
When timesync is in use, if the VM has no vsock device, a new one is
automatically added.
However this got broken in commit a5db53d as we were generating the
hypervisor configuration before adding this device.
This means timesync only worked if you had another vsock device
configured.