Marc Hartmayer
Marc Hartmayer
@arighi I guess we can close this issue since it was fixed by Ubuntu?
Won't be fixed in Ubuntu Noble - therefore closing this issue. Users of Ubuntu Noble can install `virtme-ng` via pip3 as workaround.
@shichaoyuan Do you have an idea how the vng CLI flag should be called? Something like `--paused`?
... > This immediately triggered the following error: > > ``` > thread 'vring_worker' panicked at /home/abuild/rpmbuild/BUILD/virtiofsd-1.13.2-build/virtiofsd-1.13.2/src/vhost_user.rs:271:18: > called `Result::unwrap()` on an `Err` value: QueueWriter(FindMemoryRegion) > note: run with `RUST_BACKTRACE=1`...
@chentao-kernel If your problem has been identified/fixed, could you please close this issue? Thanks.
There are still some open TODOs: - [x] check for `pvimg` - [x] Check for KVM and native run - [x] Add confidential dump support - [ ] probing qemu/kvm/hardware...
@arighi Do you know if this approach would work for AMD SEV? Or can you test it? (I do not have access to AMD SEV hardware)
Note: I'm not totally sure why the trick with the temporary file was used... Permissions? To delete the file if there was an error? 2. And what is the benefit...
> > Note: I'm not totally sure why the trick with the temporary file was used... Permissions? To delete the file if there was an error? > > > >...