Hey all,
I'm a happy proxmox user for my home server; working great! Now that past few months I used tailscale as my mesh/vpn solution, but that's overkill to me.
Therefore I'm now checking out a SSH jump server. Now I'm wondering what the best approach is here. I can think of many options...
See the logs here. I notice this:
Dec 02 08:40:07 pve systemd[1]: pvedaemon.service: Consumed 3min 31.155s CPU time.
Dec 02 08:41:18 pve pvescheduler[901]: server stopped
Now this isn't VERY long, I have to admit :). But it feels like this took longer than before. So basically the question is...
Well, for me it started to happen after upgrading to v7.x. Currently I'm running version 7.1-6. Is there a way to check what is causing the slow shutdown/restarts?
Found out that the installer by-default ticks this "" setting.
I don't need (and want) that for my home-server VMs.
Un-ticking gives me the full available disk space (as configured in Proxmox)
Here are the screenshots. In this case the VM config in Proxmox has a 100 GB disk. For some reason the installer doesn't "claim" all that disk space, right? Can you elaborate a bit more? (sorry, still learning here...)
I know; but I still miss GBs then, right?
VM config is 100 GB
Then, after fresh install of Ubuntu server, I still have 41 GB free.... where are the other GBs?
(and how do I debug this?)
Hey, I have a virtual machine configured like this:
Now after installation of Ubuntu server on the guest, the df -h command gives me this:
So I'm wondering, where is the other 50 gb? I would expect a bit more free space after a (fresh) installation of Ubuntu server.
I have my Synology NAS mounted as NFS share to proxmox 7.0-11. Now I'm perfectly able to backup the VMs to the synology, but I cannot backup LXC containers.
The error which I get can be found below. Please notice that backing up LXC containers to local storage works fine!
INFO: starting new...
Hey, I'm running PVE7 and I have a problem with assigning a passed-through USB port to one of my guest virtual machines. Each reboot from the PVE host itself results in "forgetting" the port sharing. Please see attached screenshot. So when I reboot the host (PVE itself), the chosen port (2-2) is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.