I have been testing a handful of things exploring the performance and consistency of double nested virtual machines.
Mixed news on the networking. Yes, a macvtap on on unconfigured vfio eths work many layers down without any virt bridging and yes, the host one layer above can cause issues with 'persistent naming'. I'll keep going on that...
Yes, lower level VM's are 'nice' to the cpus and do not needlessly clock beyond duty rating (non-turbo), while performing as expected.
Yes, pipewire is a mess in this use case and can't deliver smooth audio. I already knew that, so I did revert to pulse and tried again. Using a remote machine for access to a L3 VM is needlessly pushing the extremes, but... Pulse did clean it up and deadbeef could even do visualizations cleanly. But, I concluded the scenario sub-par.
Then, as I sipped and listened to my Dove's 'whoo' in the snow filled trees I realized the L1 nested hypervisor image I used is also on pipewire...
I'll need to try again.
Mixed news on the networking. Yes, a macvtap on on unconfigured vfio eths work many layers down without any virt bridging and yes, the host one layer above can cause issues with 'persistent naming'. I'll keep going on that...
Yes, lower level VM's are 'nice' to the cpus and do not needlessly clock beyond duty rating (non-turbo), while performing as expected.
Yes, pipewire is a mess in this use case and can't deliver smooth audio. I already knew that, so I did revert to pulse and tried again. Using a remote machine for access to a L3 VM is needlessly pushing the extremes, but... Pulse did clean it up and deadbeef could even do visualizations cleanly. But, I concluded the scenario sub-par.
Then, as I sipped and listened to my Dove's 'whoo' in the snow filled trees I realized the L1 nested hypervisor image I used is also on pipewire...
I'll need to try again.
Statistics: Posted by CwF — 2024-04-20 16:50 — Replies 9 — Views 174