Explore >> Select a destination
|
You are here 
|
manuel.kiessling.net | ||
| | | | |
mathiashueber.com
|
|
| | | | | Still in draft: - using bridge device * -> easiest, fastest and most convenient way, but requires wired connection. - using network tap - using host mode libvirt's default setup where the VM host more or less acts like a NAT router for all the virtual machines running on it. This works out of the [...] | |
| | | | |
dustymabe.com
|
|
| | | | | Recently we switched our 9p filesystem usage in CoreOS Assembler to use virtiofs. This is the technology behind a lot of new lightweight container VM technology like kata-containers and libkrun, but can also be easily used with libvirt. Running as non-root using qemu:///session Currently the virtiofs integration doesn't work as non-root via a qemu:///session connection. There is an oustanding RFE for this upstream and downstream in RHEL that can be followed for updates. | |
| | | | |
current.workingdirectory.net
|
|
| | | | | Some thoughts based on my work as a movement technologist | |
| | | | |
www.cloudninja.nu
|
|
| | | Intro In the first blog post (here), I wrote the most basic Bicep code for deploying a host pool, application groups, and a workspace. The result will be the same resources in this part, but the code will be a bit more advanced, allowing us to customize the deployment. I will keep the code simple, and the goal is to make the part we change for each deployment as simple as possible, while the Bicep modules contain the more advanced code. | ||
