Marc Hartmayer

> > So our expectation is that an existing file is getting (silently) overwritten? > > Personally, I think it makes sense to fail in this case, but then with...

> > > > So our expectation is that an existing file is getting (silently) overwritten? > > > > > > > > > Personally, I think it makes...

> Hi [@mhartmay](https://github.com/mhartmay), > > Interesting feature. What is your motivation to add it in `virtme-ng`? It's good for testing the Linux kernel running in protected/confidential mode. It's also very...

> Hi [@mhartmay](https://github.com/mhartmay) from a testing perspective that would be really interesting! As correctly pointed out by [@matttbe](https://github.com/matttbe) the primary focus of vng is for kernel testing. But in this...

See https://github.com/mhartmay/virtme-ng/commit/bbe6268a5af06f582854bd7991f1666bf688c029 for a PoC. What currently is missing: + QEMU feautre probing? + Kernel feature probing? (+ AMD64 support)

See https://github.com/arighi/virtme-ng/pull/290 for a RFC.

@septatrix As I'm playing around with `mkosi` anyways, I thought this might be a good idea to start with: https://github.com/mhartmay/virtme-ng/commit/f40355435c801655721f0fdafdc83f7108dea938 It's still WIP and as @arighi have said, I'm also...

There are still many differences, e.g. `mount` errors are not logged to `/dev/kmsg` in the Bash implementation.

@arighi Sorry, I've reworked the whole series...

My idea is that, since the structures and function names are now very similar, it becomes easier to keep the Bash variant and the Rust implementation in sync. As you...