Search results

Got it: https://forum.proxmox.com/threads/as-soon-as-all-containers-and-vms-shut-down-proxmox-loses-all-internet-connection-including-to-the-router-is-this-a-bug.128822/ Not a bug, but somehow an expected behavior. Setup a dedicated host interface that is not VLAN aware, and everything worked...

So, I poked around a little, and it seems when an interface no longer has any VM's using it, Proxmox shuts that particular interface down. For instance: 10.69.118.2 interface on Proxmox is used by our Windows VM exclusively. When that Windows VM is shut down, that interface stops working...

That I'm not sure of, it's a network we use to clone machines from. But the 172.22.118.0/23 stops working for sure.

Also found this in the logs: Jul 18 14:44:16 proxmox1 kernel: vmbr0: port 2(fwpr501p0) entered blocking state Jul 18 14:44:16 proxmox1 kernel: vmbr0: port 2(fwpr501p0) entered disabled state Jul 18 14:44:16 proxmox1 kernel: fwpr501p0: entered allmulticast mode Jul 18 14:44:16 proxmox1 kernel...

Got it, the 172.22.118.88 address is the one that goes down: 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 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever...

So, while I was remote, I tried pinging the server as I shut down the VMs and containers, and it stopped responding. Also, from the host, I could not ping our firewall's gateway IP while they were shut down, it certainly couldn't get to the internet. So no pings out or in, either way. I will...

Hypervisor is running the latest version of 7, and was working on upgrading to 8. I shut down all of the VMs to prepare for the upgrade. In doing so, the Proxmox host itself stops responding through the web interface, stops responding via SSH, doesn't reply to pings, and the console itself...

We currently have an on-premise e-mail server we are trying to migrate away from, and we found our PBS machine is it. I've been scouring the config files and cannot see where this e-mail server is configured. Any help is appreciated.

Can we get a status update? Was I right?

100% it's the cable. That's an FS brand and I've always had trouble out of them. Intel has a compatibility chart that lists the DAC's that will work with their cards. I'm sure you can find one that will work outside of the compatibility chart, but it's a crapshoot at best and it may cause you...

The configuration looks fine. My configuration is somewhat similar, except my PBS install is virtual and is accessing a SAN and has a dedicated NIC for it - nothing I can add there. I'm starting to bank on some incompatibility in the hardware - especially since you're using twinax. Look over...

Can I see the /etc/network/interfaces files from both servers? Also, what models are these SFP+ cards? How are they connected? Twinax? Fiber? If fiber, what models are the modules? What kind of fiber is being used? I can see the OS is detecting a link, but in the world of SFP+ I've seen...

Enabled the CONFIG_VIRTIO_CONSOLE option in the kernel and the issue is resolved.

Is it possible to schedule a backup job to run right after another backup job finishes?

The proxmox hypervisor is reporting this upon boot?

I've done passthru with my Nvidia Quadro P900 to my Plex VM using this walkthru: https://youtu.be/-HCzLhnNf-A?t=679 Relevant info starts at about the 11:19 mark. On an initial glance, there's some grub config that has to happen on the proxmox hypervisor, probably more missing. While the end...

If you want a dedicated connection, I'd personally use a network that leaves no room for guesswork. PVE: 128.50.50.1 / 255.255.255.252 PBS: 128.50.50.2 / 255.255.255.252 No gateway necessary.

I'm fairly certain the issue has something to do with the serial device not populating, I think the driver is in place, so I don't know quite what to do at this point. Trying to list the socket: # ls -la /dev/virtio-ports/org.qemu.guest_agent.0 ls: cannot access...

Ok, I think I figured out my own issue, I had to delete the volume group before I could reuse the iSCSI device. Everything seems to be working now.

Ok, I used the old volume group name (SAN_VG), now the storage I had removed previous to the reconfiguration, is now back. With the files I destroyed still listed. Some very weird things are going on.