Hi there! I was trying this out, but quickly ran into an odd snag related to external network access from the tart vm - this obviously makes using claude/codex difficult 😂. (This is also probably part bug with tart networking setup) The VM is unable to access any external network, I eventually got a manual tart VM working correctly using --net-bridged=en#. This seems very specific to the bridge networking setup used.
Quick summary of my setup:
- MacOS Tahoe (latest release as of 12/17)
- macos-tahoe-base as the tart vm, pulled 12/16.
- local network dhcp space is the 192.168.2/24. My host mac will gain a 192.168.2.x IP. Let's call this 192.168.2.42 for now.
- chamber invokes tart which creates a bridge100 network device bound to 192.168.64/24.
bridge100: flags=8a63<UP,BROADCAST,SMART,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 62:3e:5f:33:c1:64
inet 192.168.64.1 netmask 0xffffff00 broadcast 192.168.64.255
inet6 fe80::603e:5fff:fe33:c164%bridge100 prefixlen 64 scopeid 0x1a
inet6 fdc5:4579:67c7:35f7:4a4:4ccc:56d4:2a69 prefixlen 64 autoconf secured
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: vmenet0 flags=20803<LEARNING,DISCOVER,PRIVATE,VIRTIO>
ifmaxaddr 0 port 25 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
- the tart VM will DHCP lease and obtain 192.168.64.2 lease usually (although sometimes it obtains a 192.168.2/24 lease somehow that is unclear to me)
admin@Manageds-Virtual-Machine ~ % arp -an
? (192.168.64.1) at 62:3e:5f:33:c1:64 on en0 ifscope [ethernet]
? (192.168.64.255) at ff:ff:ff:ff:ff:ff on en0 ifscope [ethernet]
? (224.0.0.251) at 1:0:5e:0:0:fb on en0 ifscope permanent [ethernet]
admin@Manageds-Virtual-Machine ~ % ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
Request timeout for icmp_seq 0
The workaround I can do manually with tart is to directly use the --net-bridged option, but I don't seem to be able to pass this through chamber to invoke tart with this option.
Hi there! I was trying this out, but quickly ran into an odd snag related to external network access from the tart vm - this obviously makes using claude/codex difficult 😂. (This is also probably part bug with tart networking setup) The VM is unable to access any external network, I eventually got a manual tart VM working correctly using
--net-bridged=en#. This seems very specific to the bridge networking setup used.Quick summary of my setup:
The workaround I can do manually with tart is to directly use the
--net-bridgedoption, but I don't seem to be able to pass this through chamber to invoke tart with this option.