Fix hostresolver setting for VZ, but disable it by default#4090
Fix hostresolver setting for VZ, but disable it by default#4090jandubois wants to merge 1 commit intolima-vm:masterfrom
Conversation
3c022c5 to
af9f666
Compare
af9f666 to
211fefe
Compare
|
I believe this PR is working correctly. Unfortunately it didn't help in tracking down the DNS issue with VZ1 because it seems to happen with both HostResolver and with the gvisor-tap-vsock resolver, but that is a separate problem. Footnotes
|
211fefe to
49a83b5
Compare
Since it was implicitly disabled for VZ, we cannot simply fix the bug, but change the default to match the previous de-facto default. See lima-vm#4089 for more info. Signed-off-by: Jan Dubois <jan.dubois@suse.com>
49a83b5 to
c68049e
Compare
|
It is suspicious that the QEMU integration test with the It does pass for me locally, fwiw. |
https://github.com/lima-vm/lima/actions/runs/18024105718/job/51444457681?pr=4090 |
I can reproduce the problem even on macOS when explicitly asking for qemu: It seems like usernet configuration is different between QEMU and VZ. |
Since it was implicitly disabled for VZ, we cannot simply fix the bug, but change the default to match the previous de-facto default.
This PR now disables HostResolver by default, except for QEMU.
This implements option (1) from #4089.