Recent content by ivenae

I do not have an answer to this question, but this happend already during the upgrade from kernel 5.13 to 5.15, where iommu was activated per default. This only affects this Dell T140 and none of the other hardware i use (e.g. Dell T30 / Dell T40, misc. Fujitsu...). Maybe it is related to the...

Setting intel_iommu=off for Kernel 6.8 solved my "cannot import rpool" on Dell T140. https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#sysboot_edit_kernel_cmdline

Dann ist das der gleiche Fehler wie damals von 5.13 auf 5.15. Die hat damals wegen dem iommu Probleme gemacht und das macht offensichtlich wieder Probleme. Schade, dass ich nicht vorher davon gelesen hab. Hätte mir Ärger erspart.

Bei mir ein Dell T140. Nachdem der Kernel 6.5 Probleme mit der X2API gemacht hat und ich das überall umgestellt hab, hab ich jetzt ein Fehler beim rpool import. Auf allen günstigeren Kisten besteht das Problem nicht. Warum kauf ich den teuren Mist eigentlich?

Ich gebe zu bedenken, dass der Aufwand einer Neuinstallation mit vorherigem vzdump aller Maschinen ein verhältnismäßig kleiner Aufwand ist. Darüber hinaus besteht sogar die Möglichkeit eines Fallbacks (einbau der alten SSD), falls etwas schief geht. Ich persönlich würde mir den Aufwand nicht...

I'm unlucky, too. To activate the firewall: - Activate Firewall under datacenter -> Firewall -> Options - Activate Firewall under <node name> -> Firewall -> Options (NOT neccessary as stated in the following post) - Activate Firewall under lxc/VM > Firewall -> Options - Activate Firewall under...

Kernel 6.5.11-8 does NOT solve the x2api issue.

Shutdown will only work, if you have installed and activated the Guest Agent. The Agent is normally installed in any Linux distribution (but you have to activate is in VM options), but you have to install it by yourself on a windows machine.

is it possible to fix that in the kernel instead of changing the bios, because this is a regression.

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...