Same here, using a Dell R640
Had to resort to installing Proxmox using iDRAC, which worked.
Video port still didn't work after initial install and reboot.
Running "apt update" and then "apt dist-upgrade" installed updates which fixed the video issue after another reboot.
Probably still...
Are you using Proxmox 4 or 5?
Also, are you specifying the VLAN tag in the Proxmox GUI for each guest? If you are, then you should not have the ".6" on the end of each interface (on the guests)
My hypervisor is on VLAN 5 and has an IP on VLAN 99 as well. The NICs "enp65s0f0" and "enp65s0f1" are 10G NICs used for bond0. The bond0 interface carriers all the traffic. The other Onboard NICs "eno1", "eno2", "eno3" and "eno4" are not being used in this example.
In this example I am...
Regarding the VM stealing the VLAN, that was a situation in Proxmox 4. I had a VM which needed to be on the same VLAN as the hypervisor itself. Logically this should be fine, but if you use standard Linux networking, it's not..
I would setup the VM to avoid starting on start up. Everything...
Sure, no problem :)
Openvswitch is a very powerful upgrade to standard Linux networking. It provides a ton of features, options and enhancements.
The reason I started using Openvswitch was due to a weird situation where a VM guest would share a VLAN with the hypervisor itself. In my prior...
Anytime vlans, bonding and bridging are involved I always use openvswitch right away:
The following assumes you're using Proxmox version 5
Add proxmox repo:
wget -q -O- 'http://download.proxmox.com/debian/pve/dists/stretch/proxmox-ve-release-5.x.gpg' | apt-key add -
Add Proxmox repo:
echo...
I spent a lot of time trying to get a "LACP bond + vlan + bridge" set up running using native Linux bridges, but had several issues when guest VMs shared the same VLAN as Proxmox.
I solved this using OpenVSwitch instead. In the example below, my vmbr0 is set up for VMs (as usual) and I am able...
What I mean is: in a scenario where your proxmox node is using the same vlan tag as a VM. Once the VM boots up, it seems to "steal" the vlan from the proxmox host. Using the method above with the predefined sub-interface (vmbr0.5:256) you can avoid this.
This configuration (perhaps you'll call it a work-around) took me a while to sort out, so hopefully it will save you some time.
The problem:
When you bond 2 interfaces and then want to make a "vmbr" (for example vmbr0) over them, you'll find that the moment a VM starts with the same vlan tag as...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.