> For the complete documentation index, see [llms.txt](https://docs.verge.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verge.io/knowledge-base/networking/vm-network-connectivity-issues.md).

# VM Network Connectivity Issues

Troubleshooting guide for common VM network connectivity problems including missing NIC configuration, incorrect network assignment, improper IP settings, and missing Virtio drivers.

Before you begin, verify if other virtual machines in the environment can access the internet. If no other machines can, there may be a network issue upstream of the VergeOS platform that is preventing access to the outside world. If other VMs are still able to access the internet, the most likely cause is that a configuration step was missed.

The following are the most common configuration mistakes that cause network issues:

* **Missing NIC Configuration**: The newly created VM may not have a NIC configured. To verify this, review the **NICs** section of the VM dashboard. Ensure at least one NIC is present. If not, add one.
* **Incorrect Network Assignment**: The VM's NIC may be connected to the wrong network. In the **NICs** section, ensure at least one NIC is present with the status set to **Up**, and verify that the correct network is listed. If not, edit the NIC and assign the correct network (one used by a VM with internet access).
* **Improper IP Configuration**: The VM might not have a properly configured IP address. Typically, this is resolved at the guest level. Refer to the guest operating system’s documentation to ensure the NIC is detected, installed (with drivers), and configured correctly.
* **Virtio Drivers Not Installed**: If the Virtio drivers are not installed, the NIC may not function properly. For instructions on installing Virtio drivers, refer to the [Product Guide](/run-the-platform/virtual-machines/vm-guest-agent.md).

***

{% hint style="info" %}
**Document Information**

* Last Updated: 2024-09-03
* VergeOS Version: 4.12.6
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verge.io/knowledge-base/networking/vm-network-connectivity-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.