Search results

Hey guys I have some HP DL 560 Gen10's that have dual onboard Broadcom 10G copper network adapters which are throwing call traces on Proxmox 7.2 at every boot. Networking is still working, but not sure if this could cause other issues. It seems to only happen at boot and there are 3 of them...

I have also found that on Gen8 HP servers the only way I can get any 5.15.x kernel to boot is to disable VT-D in the bios. We have roughly 15 gen8's out in the field and so far ive had to do that to each one. Ive been around Proxmox since 2.x, so far this kernel is not giving me a very warm...

The host side logs look to be pretty clean. I will say we run a non standard mount option in our VM's with ext4 which is data=journal. I partially suspect some odd issues with io_uring and using data=journal in the 5.15 kernel. We had some filesystem errors with io_uring and data=journal...

As of late we have started having some odd crashes in our CentOS7 VM's which so far is only happening on various hosts that are on 7.2 running one of the 5.15.x kernels. I have seen it happen on 5.15.35-1-pve and 5.15.39-1-pve. Alot of the time it will happen after the VM is rebooted from...

Here it is. root@bunkproxbackup1:~# df -i /var/log/proxmox-backup Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/pbs-root 31162368 1771864 29390504 6% / This looks to be my issue, never thought about the root partition being filled on the PBS server. I had a...

root@migrateprox:/var/log# df -i /var/log/proxmox-backup df: /var/log/proxmox-backup: No such file or directory root@migrateprox:/var/log# df -i Filesystem Inodes IUsed IFree IUse% Mounted on udev 49505972 1381 49504591 1% /dev tmpfs...

Running into a issue were backups are failing and reporting out of space even though the PBS mount still has over 8TB free. ERROR: Backup of VM 102 failed - VM 102 qmp command 'backup' failed - backup connect failed: command error: mkstemp...

Sigh, I thought I had ESET totally disabled, but I left SSL filtering enabled. It was that. It was the first thing I checked this morning and not sure how I missed it. I appreciate all the input either way!

Appreciate the input. Curl and openssl look good to me. If I use the -k switch with curl it appears I get all the way to the login prompt. This is something browser specific. The openvpn server is just a simple setup running on a CentOS7 VM.

This is a interesting issue. Up until about a month ago this has worked. Basic routing and firewall rules are still the same. I can traceroute to the hosts and I can see port 8006 open via zenmap on a VPN device. Tcpdumping the traffic that looks good as well. It feels like a TLS/Browser...

Nice work guys! Definitely interested in the virtio-gl adapters. Does anyone know if windows drivers are out, and can you use a single video card for multiple VM's?

Well interestingly enough, after letting it run for a couple hours, it completed without error. Very odd issue.

Appreciate the input. Looks like GRUB_DISABLE_OS_PROBER=true is set on all of the nodes. I also gave the chmod a shot, but the below process its still scanning all lv's. /bin/bash /var/lib/dpkg/info/grub-pc.postinst configure 2.02+dfsg1-18-pve1

Just tested another 6 node cluster that is identical in hardware and configuration, but does not have LV's present. No issues going from Proxmox6 -> Proxmox7. I am not sure how to get around this other than having to log out of iscsi to get rid of all the LV's, or simply try and let grub-pc...

Doing a quick strace its almost as if grub is looking at every block device on the system. I have thousands of disks in LVM. read(8, "METAGET grub-pc/disk_description"..., 8192) = 45 write(7, "0 /dev/dm-1127 (107374 MB; Cloud"..., 60) = 60 read(8, "SUBST grub-pc/disk_description D"..., 8192)...

Just finished upgrading a 6 node cluster to Proxmox7. This cluster is on the enterprise repo's. On 4 of the 6 nodes the grub-pc package will not install, I have let it sit trying to install on all 4 servers for well over 30 minutes. Doesn't matter if I am using "apt-get dist-upgrade" or...

You could also for giggles try using socket 2 with 8 cores, or socket 4 with 4 cores.

Maybe try a different CPU model (host, kvm, etc). Or see if a linux VM boots up.

What is the guest OS. Could be AMD related as well.

I don't think so. bootdisk: virtio0 cores: 36 cpu: host,flags=+pdpe1gb memory: 2940311 name: #### net0: virtio=CE:76:8C:74:61:0A,bridge=vmbr0,firewall=1 net1: virtio=9E:F2:F5:60:CE:15,bridge=vmbr1,firewall=1 numa: 1 onboot: 1 ostype: l26 scsihw: virtio-scsi-pci smbios1...