Search results

I have systems with 64 GB memory in total. The VMs have 2 GB + 6 GB + 16 GB + 24 GB = 48 GB in sum. KSM show 27 GB regained. AFAIK KSM does not regain from host cache, but it does on all other memory. The effect is, that KSM is similar to ballooning.

I think the problem is not that easy. I manage a few small Proxmox environments and sometimes one of them get those OOMs. On the one hand, you have the 'regain memory out of the VM to the host again' function like ballooning or KSM. On the other hand there is a ZFS Arc Cache, which use per...

Just to give my 2 cents: I know this 'bug' not being able to stop a virtual machine since i use proxmox and i still make a lot use of a 'kill -9', because the stop never works for me in exactly those special conditions, where you normally use a 'force stop'. Mostly the 'stop' does not work if i...

It's AFAIK a simplefb (simple framebuffer) module issue. It has been corrected in Kernel 6.5.11-7, but you'll install 6.5.11-4 with Proxmox VE 8.1. Install Proxmox VE 8.0 and upgrade.

It was fixed in current 6.5.11-7 (or maybe 6.5.11-6) as far as i know. If you install 8.1 from ISO, you have to update kernel first, because ISO is shipped with 6.5.11-4. You could install 8.0 and update directly to kernel 6.5.11-7.

Saved my day. I tried another boot-tool command i do not remember which told me, the given kernel did not exist. pinning worked. # proxmox-boot-tool kernel list Manually selected kernels: None. Automatically selected kernels: 6.2.16-19-pve 6.5.11-6-pve # proxmox-boot-tool kernel pin...

How did you upgrade to zfs 2.2, if you never successfully booted the system with kernel 6.5?

That was obvious, because 6.5.11-6 -> 6.5.11-7 reactivated the simplefb (simple framebuffer) and didn't change anything about the Dell Problem. I have 4 Dells with old kernel which i cannot reboot via SSH at the moment. I am on tenterhooks. Next time if a big update is on line, i will skip the...

I remember an error with an early 5.15 Kernel which prevents booting the Dell T140 because of an 'could not import rpool' error. it was a problem with the disk controller on this device.

Ich hab ein 5 Jahre altes Notebook, was im 3. Jahr einen Displayschaden bekommen hat. Kommt tatsächlich mit 4,5 W Strom aus und hat als Laptop trotzdem eine USV integriert. 20 GB DDR4 (davon 4 GB verlötet) + Intel P Gold 4415U + neue 2 TB Crucial SSD, Display hab ich abgefrickelt, hängt an den...

Hang on 'loading initial ramdisk' also apply to Dell T140. It does not seem to be a network issue (only)

root@xxx:~# lspci -nnk | grep -i broadcom 01:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] [1000:005f] (rev 02) 05:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f] 05:00.1 Ethernet controller [0200]...

I have had lot of trouble today 3x Dell T140 doesn't come up. They only work with 6.2, but it was a mess to solve the customers at the same time. 2x Dell T30 does not come up as well. One of them suddenly works after some reboots and now works fine with 6.5.11-6 The other one only works after...

I ask myself this question. I always use q35. Later change is not that big deal.

Cool, i will try that in the future. Maybe i will build an environment that snapshot before an update and checks for network connection afterwards and automatically rollback and reboot if the system has no network connection or boots into initramfs after the upgrade.

Works for me Beware of the missing leading slash on the second path argument for the path inside the lxc container.

I do not know why i was not able to solve that ealier, but the first two commands on this page solves my problem: https://pve.proxmox.com/wiki/Storage:_LVM_Thin lvcreate -L 100G -n data pve lvconvert --type thin-pool pve/data After that i had to add a new pool under DATACENTER -> STORAGE ->...

I have a PVE installation without any machines since 2021. Its job was to serve a local samba service. I brought this to PVE 8 and now wanted to install the first lxc. This failed, because the pve-data pool was not found anymore. So i wanted to remove the rest of the old data pool (which...

Also run into the network issue on Saturday night. Rebooting 6.5.3 instead of 6.5.11-3 worked for me. It should not, if i read the thread here.

Meine Erfahrung: Business-PC Workstations laufen ziemlich gut, gerade weil es mit RAID Controllern im Server häufig Stress macht (zuletzt: Kernel 5.15 mit IOMMU), den es z.B. mit einem M.2 SSD RAID so nicht gibt. In 90 % aller Fälle mach ich ein SSH auf dem Proxmox und starte die VMs neu. In 10...