Giters

Parallels / vagrant-parallels

Vagrant Parallels Provider

Home Page:https://parallels.github.io/vagrant-parallels

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

DNS highly unreliable inside guest VM

tomjn opened this issue · comments

commented

Hello! I'm the maintainer of VVV, and I have issues provisioning using Parallels + arm boxes, specifically DNS issues.

Note that these issues only occur when using the Parallels provider, the same provisioning, as well as the same boxes built for VirtualBox, and the same provisioners running in Docker all work without this issue.

These issues go away if I SSH in and configure the guest VM to ignore Parallels DNS and use Googles DNS instead. I can find no documentation on configuring DNS to avoid or solve this problem, nor have I found a way to automate replacing the DNS in the guest VM. Both boxes I've used are Ubuntu 20 Arm64 boxes, the latest being the Chef Bento box.

I've also had these issues for several years, across many versions of Parallels, and have raised support issues with the main Parallels team and sent technical information, but no progress or meaningful response has been made beyond the initial boilerplate requests.

My own tests indicate that the DNS server configured cannot reliably be pinged or connected to from within the VM

commented

@tomjn We need a bit more information on this.

First, what do you mean Parallels DNS? We do not have a DNS per say and we rely on the bridge network to provide one.

I am assuming you change the DNS servers to 8.8.8.8 when you say you are using the Google DNS server

Could you please send us:

  • What the output of ipconfig command in your host mac
  • What the output of ipconfig command in your vms with issues
  • Do you have a VPN/Router

This would help us understand the issue and see where we can fix it

commented

First, what do you mean Parallels DNS? We do not have a DNS per say and we rely on the bridge network to provide one.

That would be the DNS I was referring to, unless I manually configure custom DNS inside the VM it breaks. Updating Parallels tools usually breaks existing VMs, some VMs are broken immediatley. Provisioners run until they make their first network access attempt then fail with connection issues due to DNS resolution. Sometimes this happens a little further into the scripts resolving DNS queries for sites it's already made connections to further back in the scripts.

Do you have a VPN/Router

Inactive and not always running, I've never attempted to provision with it active though. The browser has no issues finding the parallels VM or its host names, the issue is entirely inside the VM connecting to external 3rd party hosts, e.g. pinging google.com inside the VM, running curl commands, etc.

The issue is also intermittent and inconsistent.

I'll run the ipconfig commands shortly and update here, but I suspect you meant ifconfig as ipconfig on its own requires a subcommand on MacOS

commented

Also possibly useful, digging through ifconfig in the past I found the IP the VM thinks is the DNS server from the bridge, and found it unresponsive to pings/connections

commented

Yes, I meant ifconfig in mac and in linux vms, the ipconfig for windows.

Ok, could you also let me know what is the version of Parallels Desktop you are running? we had a few issues with some VPNs when resolving bridges and that was sorted on the latest 19.3, while you do not have one, we did apply some fixes to the way ip's where assigned. So would be nice to know the version