Search results

That's too bad. But thanks for the clear answer. /boot already is 1GiB. The kernels are probably pretty big, or I have allot. ;) This server has a separate /boot because Proxmox was installed on top of Debian. The host (Hetzner) probably uses an image for Debian that contains a separate /boot.

Yesterday I discovered my server had problems running apt upgrade. It seemed that the /boot partition was 100% full. I removed some old kernels manually since running apt autoremove didn't work either. Apt apparently needs some free space to work. Now, /boot is 98% full, which is still critical...

So that's it. And it is only working for some Windows Server editions. Thank you. I know enough.

I try to understand the VCPU setting. My host has 6 cores with 12 threads. I assign 4 cores to a Windows VM but I set VCPU to 2 (default was 4). After starting the VM I see that I have 2 virtual cores in Windows. When I stress them, no more than 2 threads on the host are used on 100%. I cannot...

And this morning my VM was unreachable again. This time with a fully updated and rebooted host. The last my VM showed in de system logs was that it had installed updates, so I guess it was an automatic reboot again. My backup for this VM fails with the following reason: VM 101 qmp command...

This morning my Windows 10 VM was stuck again after automatically installing Windows updates. Is this issue really fixed? Can it have something to do with the kernel version? I haven't rebooted my host in some time. proxmox-ve: 7.2-1 (running kernel: 5.15.53-1-pve) pve-manager: 7.2-11 (running...

My Windows 10 VM hung last night after automatic updates so I don't think the problem is fixed. It had an uptime of 7 days. I restarted the VM on the 24th of september because it was stuck on that day too. I updated to QEMU 7 before that day but I don't remember if my VM was restarted after...

I was googling for Debian 10 template problems when I found this topic. I just created a new CT with the Debian 10 template. I booted the system, logged in through the Proxmox web console and run two commands: #apt update #apt upgrade After the upgrades finished I did a #reboot and the CT never...

A BIOS update seem to have solved my problems. I hope it will be stable from here on.

After testing an Ubuntu live boot (without installing) it was obvious that the same problems occurred. My network went down very soon after booting and the logs didn't show any information about it. Rebooting the NIC in Ubuntu didn't even work. So I flashed my BIOS with a somewhat newer version...

Thank you for your input. This is on my list for testing. I'm not eager to flash the BIOS since I can't find any good changelogs for it. I also want to try an Ubuntu live cd to check if the network keeps working on that. If it's a hardware problem then I guess it should happen on any OS.

That is correct. NVMe seems to be my SSD. I have an NVMe SSD as a second drive. The same PCIe Bus Error is also reported for other "devices" which let me think that maybe there is a problem with the PCIe controller. Maybe my motherboard hardware is not supported by the Proxmox kernel? But how...

I have a newly build server with a fresh installation of Proxmox VE 6.0. I am totally new at this by the way. The installation went fine but the network of the host keeps dying randomly. I haven't even got any VM's yet, its just a fresh installation. I can force the problem by uploading a large...

I am having the same problems with my B450 chipset. I think the PCI controller is the main problem. The error message says its something with my nvme drive but I think its more global than that because my network goes down every time I receive this error. I have to ifdown and ifup the network to...