Search results

I’d watch this movie. Sincerely, A soldier who began fighting this war as the 6th comment in this thread, back in 2017, before anyone had identified the solution. Never thought this would still be an issue all these years later…

I appreciate the input. Thank you for your clarifying remarks in this thread.

Pardon me if this is the incorrect forum for this question. I actually decided to post here only after finding a similar thread in this same forum regarding the QEMU guest agent in this thread. And the OP in that thread referenced another thread on this forum related to their issue. I did not...

I cannot get qemu-guest-agent installed on the debian-12-generic-amd64.qcow2 image. I'm trying to follow the instructions from this tutorial and code. Here are the steps I'm following and the outcome: First, I get the image using this script: ./bin/import-cloud-image...

The fix is to run these two commands: echo "deb http://download.proxmox.com/debian/pve buster pve-no-subscription" >> /etc/apt/sources.list apt update && apt install ifupdown2 Here's my terminal showing pre-repository, adding the repository, and then successfully installing ifupdown2, which...

Another year, another hypervisor... I'm back on PVE! And I no longer have the LXC slow start issue. Didn't change any default IPv6 settings...I don't even use IPv6 at home. It's all IPv4, and my LXC containers come up fast whether they are static or DHCP. No problems at all. I have one host on...

Can't you simply edit 8002.conf or whatever the lxc conf is called and change 'unprivileged: 1' to 'unprivileged: 0'?

Thanks for posting the solution! What a thread, eh? I'm actually mid-migration from ESXi to Ubuntu 18.04 with LXD now. I started last weekend. I've had a lot of problems trying to dedicate one of the host's two physical NICs explicitly for usage by the LXC containers and not the host, but the...

I never found the solution. I actually ditched Proxmox partly because of this. Using ESXi now. It has problems too of course, but this was a show stopper.

It is on local storage. This is what I get while the container is starting. Also, it appears that the container is pingable as soon as it is started, but the console or SSH is not functional for several minutes: root@gemini:/tmp# pveperf CPU BOGOMIPS: 70557.96 REGEX/SECOND: 1634983 HD...

That's incredible. I really want to get to the bottom of this. I'll keep researching and post back in this thread when I fix it. Here's the process, typically: 1. Click Start in WebUI 2. After 2-3 minutes from Start, the container IP is pingable (but no console access) 3. After 6+ minutes from...

Was this ever resolved? I've always had slow boot times on Proxmox. Where I've had slow boot times: - Containers hosted in ZFS on machine with P6X58D-E mobo on PVE 4.4 - Containers hosted in Linux LVM on HP ProLiant DL360 G7 on PVE 5