Search results

@steph b, did you find a solution for this issue?

Exactly.

Right, IPv4 in hosts file.

I'm using dhcp on one proxmox node (without clustering). Mainly because I need IPv6 on that node and ifupdown2 doesn't seem to support a mix of static IPv4 and dynamic IPv6. This node is also based on Debian 12 and I just took the default (automatic) network config during install. I just adapted...

rootfs plugin is not working as mentioned https://forum.proxmox.com/threads/vm-mit-omv-erstellt-wie-den-ordnerm-mit-dateien-in-einen-lxc-mounten.102969/post-444154.

Did somebody find a solution for omv and lxc? It seems omv needs to have access to the disk at /dev itself. But for lxc, the disks are not available this ways.

Ballooning may be a good hint. I did disable it for most of my VMs because I had already issues in the past (years ago). But the currently affected VM did have ballooning enabled. Just disabled it and will have a close look to it.

I have a openmediavault VM on latest Proxmox 7.4 which also freezes from time to time (100% CPU... can't find any hint within the logs). This VM was running for years without hickups.

Einfach Debian installieren und dann Proxmox on top (siehe Proxmox wiki). Je nach Zweck ist LXC ausreichend.

Which error do you get if you try to restore a CT with "features: mknod=1"? Is it expected that restore fails for "custom" features?

A couple of days ago my VPS was also migrated to another server with a more recent kernel (netcup support didn't mention any details) and so far no unexpected restarts. But it's too early to really say that it's running stable.

No, I'm not paying for VMX. For my usecase, LXC is enough (but must be stable, of course). I don't get the logic of Netcup support, that it must be proxmox/client related, because the logs don't show any errors. My assumption is that their host must be involved somehow.

@goseph, Could you resolve your issue? I'm also using proxmox at netcup (but only with lxc containers). It also reboots without any errors in the logs. I tried also the updated kernel 5.11 without any success. Netcup support says it must be an proxmox specific issue and cannot be resolved by...

I'm also trying to get dropbear-initramfs running without luck. Was somebody able to solve this issue?

Bug was filed @ https://bugzilla.proxmox.com/show_bug.cgi?id=1293

I'm just playing around with virtio-scsi-single and noticed that it is not possible to use it when machine type is set to q35. Is this intended? vm config (extract): scsihw: virtio-scsi-single machine: q35 error when starting the vm: pveversion -v: proxmox-ve: 4.4-80 (running kernel...

I don't know why you have these issues, but if you are using a supermicro server board, you should be able to use IPMI to do further investigation and reinstall without having to drive 100 miles. I'm using the X10SLH-F by the way.

Proxmox 4.1 Installer still does not work with uefi boot. Resolution is recognized as 800x600 instead of 1024x768 (thus half side cropped). My board is Supermicro X10SLH-F.

I did some more testing with proxmox 4 install as guest vm (proxmox 3.4 host). When I passthrough the dvb card, the install fails as mentioned previously (same error like on the host itself!). I was able to blacklist the ddbridge module by passing the following parameter to grub...

Just tried to install Proxmox 4.1 with official iso. When a dvb card is installed (L4M pcie dvb card) the installer fails (see attached screenshot). It seems the installer tries to load the dvb modules and fails. Is there any possibility to prevent loading of those modules during installation?