feat: add VZVmnetNetworkDeviceAttachment support on macOS 26+
#4394
Conversation
|
Currently, both |
| # - vzNAT: true | ||
| # requires `vmType: vz` and macOS 26.0 or later. | ||
| # - vzShared: true | ||
| # - vzHost: true |
There was a problem hiding this comment.
For consistency with lima: shared, maybe we these one should be like vz: shared ?
Any advantage using them? |
As far as the API is concerned, customization that is not supported by vzNAT should be possible. |
Based on `VMNET_SHARED_MODE`, and `VMNET_HOST_MODE` ```yaml networks: - vzShared: true - vzHost: true ``` But, to sharing network between multiple VMs, `VZVmnetNetworkDeviceAttachment` requires VMs are launched by same process. It depends on Code-Hex/vz#205 Signed-off-by: Norio Nomura <[email protected]>
norio-nomura
force-pushed
the
use-vz-vmnet-network-device-attachment
branch
from
07eebec to
270556e
Compare
|
Added It shares
When the |
norio-nomura
force-pushed
the
use-vz-vmnet-network-device-attachment
branch
from
270556e to
81d4cc6
Compare
It shares `VmnetNetwork` serialization between VMs using SharedMode. - `limactl vz-vmnet-shared --enable-mach-service`: register Mach service and launch - `limactl vz-vmnet-shared --enable-mach-service=false`: unregister Mach service When the `limactl` executable file is updated due to rebuilds, etc., the VM using the serialization data held by the Mach server before the update cannot be booted. It is necessary to add a version check and restart the service as appropriate. Also, it seems that it cannot be used with an external vz driver. Signed-off-by: Norio Nomura <[email protected]>
norio-nomura
force-pushed
the
use-vz-vmnet-network-device-attachment
branch
from
81d4cc6 to
57553f8
Compare
2 participants
Based on
VMNET_SHARED_MODE, andVMNET_HOST_MODEBut, to sharing network between multiple VMs,
VZVmnetNetworkDeviceAttachmentrequires VMs are launched by same process.It depends on Code-Hex/vz#205