Search results

  1. S

    Stuck immediately after Bootloader / start of Kernel Boot

    Alright, Fingers crossed :). I think I added a debug Parameter too (also used to debug Initramfs), but it might well be that there is quiet Parameter that I missed. Thanks for the Tip. Let me check that :). That's surely NOT an Issue in my Case :). It's always GRUB2. For how "bad" everybody...
  2. S

    Stuck immediately after Bootloader / start of Kernel Boot

    Thank you for your Reply :) . When I was in BIOS the other Day, I am pretty sure it was under the Advanced Features Submenu, NOT the IPMI one. COM1 was set to COM by Default, whereas COM2 was set to SOL by Default. Logically COM1 would be the DB9 Serial Port in the Back whereas COM2 (if NOT...
  3. S

    Stuck immediately after Bootloader / start of Kernel Boot

    Any Idea ? EDIT 1: back several Months for a similar Issue (digging through my Emails since Forum Search is quite Bad), @t.lamprecht suggested adding Options earlyprintk=vga,keep to Kernel Command Line, so I might as well try that. Weird that Serial Debugging don't work though. Is the Freeze /...
  4. S

    lxc_init: 845 Failed to run lxc.hook.pre-start for container "200"

    Sorry for the late Reply, but I'm facing the Issue now on another System. I tried both the Null Modem Cable and using Supermicrom SOL (Serial over LAN) but in both Cases, probably due to misconfiguration, it won't do anything at all. I described the Issue in...
  5. S

    Stuck immediately after Bootloader / start of Kernel Boot

    I tried both with SOL (Serial over LAN) and a local Null-Modem Cable connected between the DB9 Serial Port of one Host and the DB9 Serial Port of the other Host. Nothing is working :( . I tried with: minicom --device /dev/ttyX --baudrate 115200 for X equal to: ttyS0 ttyS1 ttyS2 tty0 tty1 tty2...
  6. S

    Stuck immediately after Bootloader / start of Kernel Boot

    I can observe several Issues (NOT only related to Proxmox VE 9 / Debian Trixie) but rather also e.g. Kernel 6.8 or even Kernel 6.5 on multiple Xeon E3 v3 Systems based on Supermicro X10SLL-F / X10SLM-F Platforms. This is what it looks like immediately after the Bootloader is exited and the...
  7. S

    Problem backing up unprivileged container - permission denied, but only for docker files

    I don't think you can really convert them. The Conversion, if any, might be done the other Way around (VM -> CT), but also in that Case it's probably easier to just install from Scratch and restore/migrate from Backup. You need to DEPLOY a new VM using your preferred Linux Distro (e.g. Debian...
  8. S

    Podman in rootless mode on LXC container

    That's what I usually do indeed. However I cannot do that for some Hosts because of these **** IOMMU Groups: I CANNOT pass only the Hailo PCIe Accelerator to the VM, but instead it would pass the entire Chipset PCIe Devices (NIC, SATA controller, etc), thus crashing the entire Host System...
  9. S

    Podman in rootless mode on LXC container

    To be honest it never worked for me, I had to build Podman from source and install it directly on the Proxmox VE Host :( . It might be related to Podman requiring Access to the Hailo PCIe Accelerator (for Frigate), thus the Permissions & UID/GID Mappings are even weirder compared to "just" Bind...
  10. S

    Proxmox Kernel 6.8.12-2 Freezes (again)

    To be fair, I feel like the only way to troubleshoot these kind of Issues would be to connect a Serial Null-Modem Cable (DB9) and then log via e.g. minicom what's going on. Obviously making sure that the BIOS configured the Serial Port correctly first and do a test on the "Client" System. You...
  11. S

    Proxmox Kernel 6.8.12-2 Freezes (again)

    You didn't specify the Supermicro Motherboard you are using at all. I have zero Experience with AMD EPYC Systems, but if you say that they have Identical Hardware, did you also check the Hardware Revision of the Motherboard (e.g. 1.01 vs 1.20 or whatever) and/or the other Hardware (e.g. NIC) to...
  12. S

    Scrub won't complete on degraded ZFS pool

    One Important Thing (I don't see it mentioned by the OP): **IF** Cooling is an Issue in the Server, running a LONG Smart Test can basically cook the Drive (in Terms of Temperature !). We agree that it should NOT happen if the Fans are correctly spinning and have enough static Pressure, but just...
  13. S

    [TUTORIAL] Virtual Pendrive on VM

    Has anybody experienced Issues related to Hotplug / VM Configuration Changes ? My VM will crash and the virtual USB gets disconnected if I add/change a Network Interface or if I create a new Hard Drive when the VM is Running off the Pendrive :rolleyes: . EDIT 1: if you disable Hotplug in VM...
  14. S

    Setting hard drive serial number

    I posted my UDEV Rule Solution at https://forum.proxmox.com/threads/set-fixed-uuid-for-all-disks-in-a-vm.151701/#post-776728. Somewhat this Topic of Serial Numbers got spread quite across different Threads. That of course requires that you set the serial (and Potentially the wwn as well) from...
  15. S

    Unique device ID for virtual hard disks?

    @gurubert, @Stoiko Ivanov, @illustris, @Dzung: I posted my UDEV Rule Solution at https://forum.proxmox.com/threads/set-fixed-uuid-for-all-disks-in-a-vm.151701/#post-776728. That of course requires that you set the serial (and Potentially the wwn as well) from the CLI though, e.g.: qm set <vmid>...
  16. S

    Set fixed UUID for all disks in a VM

    You can also set serial=<max-20-characters> accoring to the Documentation (in the same Way as @fiona explained), but it will require a custom UDEV Rule in your VM ;) . I played a bit around with the different Bus Types (SATA, IDE, SCSI, VIRTIO, USB) and I think this covers most Cases (although...
  17. S

    Disable TLS for spice connections?

    Did you ever managed to solve this ? I also was just attempting to setup Remmina to use SPICE over SSH Tunnel but it just doesn't work (Connection to the SPICE Server dropped) :(
  18. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    And as I said, most likely People around here will tell you that is a Feature and not a Bug ;) . Proxmox VE is not meant to be used with Wireless Interfaces as I said. It's in the Name ;). lsxxx as in "list" for xxx so to Speak ;). - ls lists Files - lspci lists PCI/PCIe Devices - lsusb...
  19. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    And if you bothered to have a look at the Manufacturer Website for that Adapter in the first Place, you would have your Answer clear as Day:
  20. S

    Supported MediaTek WiFi Module not Showing in Proxmox lspci

    Yeah, and there's your Answer: bus info: usb@2:1 The Adapter is getting detected as USB .... And maybe your "M.2" is just a stupid PCIe to USB3 Adapter/Chip and then a standard Mediatek USB Adapter. Try lsusb or lsusb -t instead then. Or maybe lspci -tv if you want to Troubleshoot which PCIe...