Search results

I spent like 10 minutes trying to figure out why this didn't work before realizing I had a typo and put "rdb" instead of "rbd." I feel dumb. lol Thank you for posting this. Super helpful.

I have been having a consistent and incredibly frustrating issue where a single node in my datacenter being rebooted causes the entire datacenter to fail and the web GUI to malfunction and become useless. I then need to log into the node(s) over SSH and either restart cluster related services...

How would I have changed this? I suppose it's possible but I would have had to manually edit the renewal script for the built in automated ACME GUI. I didn't do anything (this time) that wasn't a GUI option. ACME didn't originally mess up the pve-ssl.pem file. It got messed up on automatic...

So unfortunately I need to open this again as the issue came back up and I think this is a problem with Proxmox's ACME script. As I stated in my last post I configured the custom cert and everything worked just fine. A few days ago however Spice stopped working again. Just as last time I went...

It seems like that is the answer. Wow now I feel kind of dumb. I updated my VM to Debian 10 and the issue is completely gone. Proxmox still throws errors if I remove the CPU, cpuunits or cpulimit fields but other than that the issue is gone. Memory hotunplug is working flawlessly now too...

I'm not getting any errors in the syslog and the console froze just like the desktop. When I do what you described the VM will start with 1 vCPU and I can add them, but I still can't removed them. The VM will hang if I try to remove a CPU at any point after this. I tested this on a second...

Not sure exactly what you mean by that. I followed what you said and the VM froze after I got the error. When I stopped it and started it again the VM only had 1 vCPU like I had told it to set itself to. This is basically the same as shutting the VM down and adding or removing cores though...

It was my understanding that hot-unplug worked which is why it surprised me when it didn't. As for kernel messages, I just checked and there are no messages as far as I can tell. The entire OS seems to hang the moment the memory or CPU are unplugged so I'm not surprised. As for the code, I'm...

I believe it was this one. It hash matches the only version I have in my NAS at the moment and I don't see why I would have deleted any other images. It has been a few months since I made this VM though. I use it to run a Minecraft server and decided to test hotplug on it because it was...

Unfortunately I have no idea on a possible timeline. I started testing out this feature the day before I made the first posting. I actually didn't know it was possible to hotplug CPU and RAM on a VM until I spoke with a friend of mine. Since I've found very little information on it other than...

Is there anything else you would like me to provide?

root@scylla:~# qm config 104 agent: 1 balloon: 0 bootdisk: scsi0 cores: 8 cpu: qemu64 hotplug: disk,network,usb,memory,cpu ide2: none,media=cdrom memory: 6144 name: TCR-Refined net0: virtio=XX:XX:XX:XX:XX:XX,bridge=vmbr0,tag=10 numa: 1 ostype: l26 parent: BeforeIBreakIt scsi0...

I just configured hotplug for CPUs and RAM on one of my VMs and have been testing it. Hotplug for the CPU and RAM work but unplug fails every time with the error: Parameter verification failed. (400) vcpus: hotplug problem - 400 Parameter verification failed. vcpus: error unplugging cpu4...

That was right on the money. I'm not sure why it was replaced though. Perhaps I did it by mistake when I was initially trying to get SSL up by manually configuring things the way the old guides said to. Everything seems to be functional now. For anyone else who might run into this, here's what...

I've been having this issue for over 6 months now but haven't put in the time to figure out what is causing it until now. I configured a custom certificate for my primary server using the web GUI based ACME script. Ever since I did this spice has completely ceased to function from that node...