Search results

Oh, so you're saying click on "Templates" at this point, but on the other "Create: LXC Container" > "Template" THAT is where they don't show up, you have to add them first here at your screenshot point. Thanks.

Unfortunately `Esc` is not working to show me what's going on. It literally hangs there with no other ability to get output (and ssh is dead at that point). I've used `halt` because poweroff/shutdown hasn't been working reliably. Reset seems to work more reliably, but will not even work once...

Hmm, I'm not seeing a download button anywhere oddly... Furthermore, can Docker containers run within an LXC container or would the VM path be better in this case?

The preferred method of setting up an instance of Discourse is to use Ubuntu 18.04 to install a Dockerized container for Discourse. Unfortunately Discourse developers are very particular about keeping with their configuration standards and so there's not a lot of wiggle room if you want any...

Whenever I initiate `sudo halt` in Ubuntu 18.04 I usually am met with the never ending purple shutdown screen. Any idea as to what could be done to stop this and allow the system to shutdown properly?

I also think having a consolidated option such as this available for the browser would be nice. I'm working on deploying an accounting system for some users that need access to a Windows 10 client via dedicated Epichrome Chrome instances on MacOS. The nice thing about this would be to allow them...

I found this post: https://forum.proxmox.com/threads/cannot-add-lvm-thin-storage-to-gui.50200/ Which basically says to back out of everything and do this via the Proxmox Web GUI. So I removed the /etc/pve/storage.cfg entry that I'd tried to make for the thin-lvm, I also issued the following...

So I'm still having some trouble here. I found some quite old instructions that were interesting: https://proxmoxve.blogspot.com/2013/12/how-to-add-extra-storage-in-proxmox-ve.html I deleted my LV "ssd_vg" so that I was back to just a VG of "ssd_vg", but when I went to Datacenter > Storage >...

I'm looking for a LVM Thin version of these instructions. My system won't start up after doing this so far. This forum's search and the "manual" (and wiki) on this and other topics are frequently abysmal. :(

I'm running Proxmox on a Dell PowerEdge server that takes several minutes to reboot. It's horrible, but I've found that using https://github.com/error10/kexec-reboot works AMAZINGLY well!!! I don't know the "proper" way to install it, but apt installed the kexec-tools and Ruby from Debian and...

Unfortunately I found that after reboot and having that line in /etc/fstab the system will not boot. I had to go into single user mode and comment out that line. I even tried to use the UUID insetad of the dev path. It seems that I can mount it fine manually, but automounting it doesn't work...

I guess the question is that after I create this, how do I get it to show up for storage? I can't seem to get this to show up anywhere to actually USE it now.

Please tell me if the following makes sense. I pulled this from a couple different tutorials, in this case I'm only using /dev/sdb at my 1TB SSD: fdisk -l # list disks fdisk -c -u /dev/sdb # create a partition with dos compat off and u gives sectors instead of cylinders, do the following...

I've installed a new 1 TB SSD into my Proxmox server and have become a bit confused after reviewing the instructions, wiki, etc. As far as this goes, I would like to have minimal virtual machine storage consumption (ie, I don't want to allocate an entire storage space of 200 GB for a VM...

I had a pretty serious issue where the Proxmox KVM machines didn't restart after the Proxmox server itself restarted a couple times. I do have the machines' options set to start at boot, however they still didn't start. I ended up having to execute `qm start <vmid>` to get things going again...

Thank you very much for that clarification! I guess I also missed the part about changing enterprise repo to the no-subscription repository: https://pve.proxmox.com/wiki/Package_Repositories nano /etc/apt-sourceslist.d/pve-enterprise.list # Change line to: deb...

I'd like to install the version of kernel-headers that match "pve-kernel-4.15.18-12-pve", but linux-headers-4.15.18-12-pve is not available. What do I need to do in this situation to get the proper kernel headers?

So after the update as per above and a reboot I'm unfortunately still hitting this black screen on 19.04. Hmm.

Strange, I am running Proxmox 5.3 already... but I think I just figured out the issue. Since I'm not an enterprise user I would need to disable the enterprise repository and add the non-subscription repo, is that correct? Ie, to `/etc/apt/sources.list` add: # PVE pve-no-subscription repository...

So while VMware compatible does work on 18.04, when I try Lubuntu 19.04 beta the system hangs at: [drm:vmw_driver_load.cold.19 [vmwgfx]] *ERROR* Hardware has no pitchlock