Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/vm/create-vm.md
Original file line number Diff line number Diff line change
Expand Up @@ -42,6 +42,13 @@ Please refer to [this page](./create-windows-vm.md) for creating Windows virtual
1. To configure networks, go to the **Networks** tab.
1. The **Management Network** is added by default, you can remove it if the VLAN network is configured.
1. You can also add additional networks to the VMs using VLAN networks. You may configure the VLAN networks on **Advanced > Networks** first.

:::note

If the virtual machine has one interface connected to the `mgmt` network and another connected to a VLAN network, the node may be unable to reach the virtual machine's `mgmt` IP address. This connection issue occurs when the other network's gateway overrides the virtual machine's default route, resulting in routing that prefers the VLAN network for all inbound and outbound traffic, even traffic destined for the `mgmt` network.

:::

1. (Optional) Set node affinity rules on the **Node Scheduling** tab.
1. (Optional) Set workload affinity rules on the **VM Scheduling** tab.
1. Advanced options such as run strategy, os type and cloud-init data are optional. You may configure these in the **Advanced Options** section when applicable.
Expand Down
4 changes: 3 additions & 1 deletion docs/vm/edit-vm.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,8 @@ You can add additional VLAN networks to your VM instances after booting, the `ma

Additional NICs are not enabled by default unless you configure them manually in the guest OS, e.g. using [wicked for your OpenSUSE Server](https://doc.opensuse.org/documentation/leap/reference/html/book-reference/cha-network.html#sec-network-manconf) or [netplan for your Ubuntu Server](https://ubuntu.com/server/docs/network-configuration).

If the virtual machine has one interface connected to the `mgmt` network and another connected to a different network (such as a VLAN), the node may be unable to reach the virtual machine's `mgmt` IP address. This connection issue occurs when the other network's gateway overrides the virtual machine's default route, resulting in routing that prefers the VLAN network for all inbound and outbound traffic, even traffic destined for the `mgmt` network.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"resulting in routing that prefers the VLAN network for all inbound and outbound traffic, even traffic destined for the mgmt network." is missing.We can provide the same detailed statements under both create and edit vm

![edit-vm](/img/v1.2/vm/edit-vm-networks.png)

For more details about the network implementation, please refer to the [Networking](../networking/harvester-network.md) page.
Expand All @@ -61,4 +63,4 @@ If you are using external storage, ensure that the storage provider supports vol

Access Credentials allow you to inject basic auth or ssh keys dynamically at run time when your guest OS has QEMU guest agent installed.

For more details please check the page here: [Dynamic SSH Key Injection via Qemu guest agent](./access-to-the-vm.md#dynamic-ssh-key-injection-via-qemu-guest-agent).
For more information, see [Dynamic SSH Key Injection via Qemu guest agent](./access-to-the-vm.md#dynamic-ssh-key-injection-via-qemu-guest-agent).