Search results

I have a scenario where I need to have an LXC container operate with a network connection through a local SOCKS5 server on our network. Is there a simple or clean way to do this?

Running Proxmox 7.1. Just installed SME Server 10 (see: https://wiki.koozali.org/SME_Server:10.0) based on CentOS 7 and with its main filesystem using XFS (by its choice). When I reboot the system I receive some errors and when I attempt to type in a username to login, it goes a bit bonkers as...

I was able to import a hyper-v image with a simple qm importdisk 102 OldServerName.vhdx local-zfs, but I have not been able to figure out how to import an EFI disk yet. I think it is in the exported path of ~/OldServerName/Virtual Machines/<UUID>.vmgs that was created by the hyper-v exportation...

Is this a better (more comprehensive) way https://forum.proxmox.com/threads/is-this-the-optimal-way-to-run-docker-on-proxmox.96005/ ?

Found a curious blog post about using Docker on Proxmox: https://joshspicer.com/docker-proxmox It seems Rancher has some Proxmox integration functionality that seems interesting. I thought Photon (OS) from Vmware might be the optimal solution before this..... What do you good folks think?

Wow, just took another look and I can feel the acid dripping from that Spice thread. So sad.

Unfortunately I had to move on for the moment - unhappy and using crappy Ubuntu - and will move to Void when we get some love.

You have got to be kidding me! Sounds like spicytown is jut an extension of the rest of the insanity of current society. What a horrible thing to hear. Can you chime in on the points here? I can't help but wonder if, instead of Proxmox Staff chiming in, community members can innocuously post...

With all of the news and discussion surrounding Hyper-V's free tier being killed off, the relevance of Proxmox and KVM seem to be rising. I was doing a little searching in trying to find some info and thought this thread might be of interest to Proxmox developers and users alike...

Any news on this?

For what it's worth, here is the request submission as you suggested: https://bugzilla.proxmox.com/show_bug.cgi?id=3579 Uploading the container templates is presently counterintuitive. I renamed the rootfs.tar.xz to something more descriptive, but still with the extensions present and the...

Meh, I went ahead and did it against my fears of buggering something up. I simply did a "Detatch" from the Hardware tab for the guest vm and then back in terminal I remapped it again with qm set 102 -scsi2 /dev/disk/by-id/ata-ST4000VN008-421156_ZAV43AS. Did the job and no apparent problems.

I have a guest Windows virtual machine that has a passthrough mapped hard drive and I want to clone this virtual machine without the passthrough drive. When I attempt to clone the guest vm I get an error: unable to parse volume ID '/dev/disk/by-id/ata-ST4000VN008-421156_ZAV43AS' (500) Clearly...

Could we please have the containers listed here, such as Void Linux, made available? https://us.images.linuxcontainers.org/ Additionally, is there a way to add these manually?

Could the OpenMediaVault halt-hang issue be related to the PCI Passthrough HBA PCI card?

SOLUTION: By default this can be perceived as a problem with Proxmox 7, however there is a solution: Change your in the Hardware tab of your guest VM, change the Display type to VirtIO-GPU, then start up the guest VM again and if your VirtIO drivers are not installed, then install them and try...

In this latter situation of just getting into the BIOS (UEFI specifically), which must not be related to the originally reported (and still remaining issue) "Stop" was used and failed. A direct command into the UEFI was sought, but I could only find a restart option, which didn't halt the guest...

I ended up having 20 minutes free so I set up another guest as a test to see if I could install it alright. During the process (before install) I decided to stop the system and change it from UEFI to BIOS. Oddly I found I couldn't kill the OS or get it to halt from the UEFI loader even. It was...

$ qm config 111 agent: 1 balloon: 1024 bios: ovmf boot: order=virtio0;ide2;net0 cores: 6 efidisk0: local-zfs:vm-111-disk-1,size=1M hostpci0: 0000:04:00.0 hostpci1: 0000:09:00.0 hostpci2: 0000:0c:00.0 ide2: none,media=cdrom localtime: 0 machine: q35 memory: 32768 name: server-omv net0...

Again, thank you for your suggestion. There are no other guests running (or installed at this time on this server). During the hang I executed journalctl -e, but there was nothing eventful therein. Only the repeating: Aug 03 16:42:00 server systemd[1]: Starting Proxmox VE replication runner...