Hello Andreas,
welcome to Genode's mailing list!
On 04.07.2018 20:04, Johannes Kliemann wrote:
Does it work with Sculpt? I don't know but I can't tell why it should make any difference to any other scenario. For this Norman can give a better answer.
I routinely test-drive sculpt in Qemu running in my Linux VM on top of Sculpt using the gems/run/sculpt_test.run script. So Sculpt should in principle come up in KVM on a native Linux system.
For reference, in my test scenario the Qemu command line looks as follows:
qemu-system-x86_64 \ -no-kvm \ -display sdl \ -cpu core2duo \ -m 768 -net nic,model=e1000 -net user \ -serial mon:stdio \ -device ahci,id=ahci \ -drive id=hdd,file=bin/sculpt-ahci.raw,format=raw,if=none \ -device ide-hd,drive=hdd,bus=ahci.1 \ -drive format=raw,file=var/run/sculpt.img \ -machine q35
Does it work in form of being usable? I don't think so but ymmv.
I agree. In Qemu without KVM, it is bearable for testing but not for using.
Regarding nested virtualization in Qemu/KVM, you'd need to enable at least the AMD Phenom CPU model (-cpu phenom) in Qemu. Our automated tests of the Seoul VMM (as used in Sculpt's 'seoul-vmm-browser package') work that way. But I have not used this configuration interactively.
Cheers Norman