Search results

I have rebooted each machine a couple of times. Heres the requested details: root@TracheNodeA:~# ip -details a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 promiscuity 0 minmtu 0 maxmtu 0...

Last update for the day: Digging into the logs, I found this when I assign a VLAN tag to the VM: Dec 28 15:24:53 TracheNodeA pvedaemon[1116]: <root@pam> update VM 42069: -net0 virtio=7E:EA:78:9D:EF:1F,bridge=vmbr0,tag=3 Dec 28 15:24:53 TracheNodeA kernel: vmbr0: port 2(tap42069i0) entered...

I cut openvswitch out of the picture and still none of my tagged VMs are working correctly after the 6 to 7 upgrade: Here is the current networking with VLAN aware Linux Bridges: VM can't access it's gateway

As I was writing up this issue, I upgraded my other Node to PVE 7. Now my VMs can't reach their VLAN gateway, and I'm suspecting that the PVE 6-7 upgrade broke openvswitch. Edit: I am now certain that my VLAN tagging issue are related to my upgrade from PVE 6-7. I had a setup working perfectly...

All my VMs are configured to grab IPs via DHCP, my pfsense router runs a DHCP server for each VLAN. Here is the working config I have on my other PVE node as well as the associated VM config where traffic is sucesfully being passed to VLAN 3. The config for the node you're seeing is running...

Thanks Mira, I turned off all the other VMs on the host and ran the commands and was able to get clean data for vmbr0. I then tagged the VM with VLAN 3 and rebooted. I stopped the tcpdump at that point. I was able to run the tcpdump for eno1 once, but then I got permission denied? Sorry the...

I configure the VLAN tag in the VM hardware pane for both the OVS and Linux Bridge scenario: This is the same way I'm doing it on my other PVE node.

Hello, I can't seem to get tagged VM traffic to my router. I am successfully routing vlan traffic on another proxmox node using an OVS config, so it's a node specific issue. 192.168.1.1 is my pfsense router. I have rebooted the node multiple times in between network changes. I initially...

More troubleshooting: - I attempted to configure with only Linux bridges or OVS bridges. Didn't help at all

I'm trying to hunt down a network throughput issue I'm having in my virtualized environment. It was suggested that perhaps my OVS config could be to blame and so I wanted to get a sanity check on what I'm working with. X-post...

So far so good! Could you briefly elaborate on what's going on here? What does setting 'virtio-gpu' do?

So initially the display is fine but as soon as I proceed to install Debian, I get this chaos There is a 2nd display output on the graphics card, but I don't have an adapter on hand to try it.

I set the display to VGA and it worked! Thank you!

Cross post: https://www.reddit.com/r/Proxmox/comments/r7yi32/cant_access_console_on_new_vm_wgpu_passthrough_vm/

I'm trying to spin up a Debian VM with GPU passthrough. Everything seems to have worked correctly except I cannot connect to the console: "VM 69420 qmp command 'set_password' failed - Could not set password" I have also tried to connect a monitor directly to the VGA port of the card but didn't...

Hello, I'm running PVE 6.4-4 and cannot upgrade via the GUI any further. I have only ever upgraded through the GUI. Starting system upgrade: apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The...

I already had this issue and had it solved, oops: https://forum.proxmox.com/threads/cannot-backup-only-lxc-to-nfs-vm-works.90797/#post-396611

I recently restored this LXC container, and now I cannot back it up. I am able to backup VMs to this same directory in the same job, just cannot backup the LXC. Method 'GET /nodes/TracheNodeA/vzdump/defaults' not implemented (501) INFO: Starting Backup of VM 100 (lxc) INFO: Backup started at...

I configured 2 SSDs in RAID1 on my hardware controller. After Proxmox install, the RAID volume shows up as "degraded" (Fig. 1) on the controller. The SMART values (Fig. 2) reflect that one drive is being used but not the other. I had the RAID controller "repair" the degraded mirror, but that...