Skip to content
This repository has been archived by the owner on May 4, 2024. It is now read-only.

Conflicts with VMware Fusion #7

Closed
AkihiroSuda opened this issue Jul 29, 2021 · 0 comments · Fixed by #8
Closed

Conflicts with VMware Fusion #7

AkihiroSuda opened this issue Jul 29, 2021 · 0 comments · Fixed by #8
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@AkihiroSuda
Copy link
Member

AkihiroSuda commented Jul 29, 2021 •
edited
Loading

VMware Fusion 12.1.2 on macOS 11.5.1 cannot use vmnet when vde_vmnet is running

vmware.log:

2021-07-29T15:58:30.456+09:00| vmx| I005: VNET: MACVNetMacosGetRealAdapterType: network type for adapter 0: 8
2021-07-29T15:58:30.456+09:00| vmx| I005: VNET: MACVNetMacosGetVnetProperties: vnet properties: vnet=vmnet8, nat=yes, dhcp=yes (ignored), subnet=192.168.60.0, mask=255.255.255.0, firstAddr=192.168.60.1, lastAddr=192.168.60.127, isIPv6=no, IPv6Prefix=fd15:4ba5:5a2b:1008::, IPv6PrefixLen=64
2021-07-29T15:58:30.456+09:00| vmx| I005: VNET: MACVNetPortVirtApiStartInterface: Waiting on semaphore for adapter: 0
2021-07-29T15:58:30.505+09:00| host-28146| I005: VNET: MACVNetPortVirtApiStartHandler: starting interface for adapter: 0, status: 1001
2021-07-29T15:58:30.505+09:00| host-28146| W003: VNET: MACVNetPortVirtApiStartHandler: unable to create virtual intrface for device: 0, status: 1001
2021-07-29T15:58:30.505+09:00| vmx| I005: VNET: Semaphore signalled for adapter: 0, timeoutMs=5000, waitMs=49
2021-07-29T15:58:30.505+09:00| vmx| W003: VNET: MACVNetPortVirtApiStartInterface: Failed to create interface for adapter: 0, handlerStatus: 1001
2021-07-29T15:58:30.509+09:00| vmx| I005: VNET: MACVNetPort_Connect: Ethernet0: can't start virtual interface
2021-07-29T15:58:30.511+09:00| vmx| I005: Msg_Post: Error
2021-07-29T15:58:30.511+09:00| vmx| I005: [msg.vnet.connectvnet] Could not connect 'Ethernet0' to virtual network '/dev/vmnet8'. More information can be found in the vmware.log file.
2021-07-29T15:58:30.511+09:00| vmx| I005: [msg.device.badconnect] Failed to connect virtual device 'Ethernet0'.
2021-07-29T15:58:30.511+09:00| vmx| I005: ----------------------------------------
@AkihiroSuda AkihiroSuda added bug Something isn't working help wanted Extra attention is needed labels Jul 29, 2021
AkihiroSuda added a commit that referenced this issue Jul 29, 2021
@AkihiroSuda
README.md: add a note about issue #7
97a1ef6 
Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
AkihiroSuda added a commit that referenced this issue Jul 29, 2021
@AkihiroSuda
support --vmnet-gateway=IP, e.g., 192.168.105.1
046d346 
`vde_vmnet` binary itself does not have any default value,
but the launchd plist file is updated to use 192.168.105.1
as the default, so as to avoid conflicting with VMware Fusion.

Fix #7

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
@AkihiroSuda AkihiroSuda mentioned this issue Jul 29, 2021
Merged
AkihiroSuda added a commit that referenced this issue Jul 29, 2021
@AkihiroSuda
support --vmnet-gateway=IP, e.g., 192.168.105.1
5c15182 
`vde_vmnet` binary itself does not have any default value,
but the launchd plist file is updated to use 192.168.105.1
as the default, so as to avoid conflicting with VMware Fusion.

Fix #7

Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

support --vmnet-gateway=IP, e.g., 192.168.105.1 + drop support for macOS 10.14 lima-vm/vde_vmnet
1 participant
@AkihiroSuda