Rob Bradford
Rob Bradford
Otherwise we are left with the e.g. vCPU and VMM threads running but no disk threads. The correct thing happens if there is a `panic!()` but not with errors propagated...
The `test_windows_snapshot_restore` test now seems to be timing out after either the refactoring for enabling unified binary or (more likely in my opinion) the upgrade of the Azure VM guest...
Some situations require multiple payloads to be loaded by the VMM in order for the guest to be usable. These are the current payloads i'm aware of: "Direct booting" use...
``` [ 32.823268] bash[1423]: cloud-hypervisor: 124.188929ms: ERROR:vmm/src/cpu.rs:1040 -- VCPU generated error: VcpuRun(Failed to run vcpu: Unexpected exit reason on vcpu run: FailEntry(7, 3) [ 32.823336] bash[1423]: Caused by: [ 32.823401]...
With the switch to 5.18.8 boot time regressed by 83%.
Like vhost-user the vfio-user spec covers support for live migration: https://github.com/nutanix/libvfio-user/blob/master/docs/vfio-user.rst
We're proposing to make 23.0 or 24.0 an LTS release. We're currently proposing to support the LTS release for 18 months from release. The LTS would include security fixes for...
- [ ] Manually check data structures for migration are sufficient and flexible enough - [x] Add integration test for testing upgrade across versions (#3949)
Boot a VM with the last released stable binary and then migrate it to the version under test. This will help us work towards supporting live upgrades between major releases....
Looks like the KVM AMX patches are merged in the upstream Linux tree so I think we can remove the feature gate. @bryteise WDYT?