Search results

Ok, that was a bit weird ... I restored it through the GUI and it chooses CT itself. I just tried again and this time it went through. When I tried yesterday it threw a whole bunch of errors so I'm not sure whats different today. For the "unpriviliged" error, it was because of my misspelling...

I was in a similar situation and backed up the CT, however on restore I get the error vm 0 - unable to parse value of 'unpriviliged' - unknown setting 'unpriviliged' Any chance of recovering this CT ?

I can only answer for myself. The Proxmox ISO provided by my DC installs Proxmox with LVM and RAID-0 instead of ZFS.

Actually the explanation in https://ubuntuforums.org/showthread.php?t=2343595 also works for Debian. Problem is it has a lot of funny characters in it like [ ] which doesn't work with VNC, at least not with a danish keyboard. Luckily all you need to do is login to VNC and start the process...

So am I, and I don't see any stability problems so I dont' think that's the problem. ECC memory?

For Debian, I think all you need to do is hit esc, then add ":install console=ttyS0" at the boot prompt. Problem is I don't see the boot prompt in proxmox.

There is a special place in ....

I use this when I need to connect to a VM through the console for whatever reason. What I'd like to know, is possible to use this to install VM's? Normally when I create a VM, it opens up in VNC, and I can't find any way to get it to open in the serial console - even if I create the serial...

After many hours of trial an error.... By adding a serial port to the VM (vm > hardware > add > serial port) I was able to connect through the xterm.js console instead, which supports copy paste, and was able to add my public key. That in itself didn't help anything though, as I still need to...

Part of installing RancherOS you need to add your public key to a cloud-init file, and that is a lot of keys to type in the VNC terminal that doesn't allow copy/paste - and you can't ssh in until this has been done. Catch-22. Now I see that Proxmox supports Cloud-init, which as far as I...

Having the same problem here. Ran the "modprobe overlay" on the host, verified presense in the container, but docker still fails with a not-very-helpful error message: Oct 18 22:57:31 docker2 systemd[1]: Starting Docker Socket for the API. Oct 18 22:57:31 docker2 systemd[1]: Listening on...

That was easy, thanks! (PVE: Datacenter > Server > VM > Hardware > Hard Disk)

I created a VM on storage:local instead of storage:vmdata by mistake. Is there a way to move it? I guess it also needs to be changed/converted from qcow2 to raw? # pvesm status Name Type Status Total Used Available % local dir...

Thanks, good idea. Setting Reservations on ZFS File Systems

Awesome! Perfect!

My Proxmox install is on ZFS, and I have a couple of zvols: Unfortunately I didn't realize at the time that it would be a good idea to limit the space for /var/lib/vz so snapshots don't accidentally take up all the diskspace. This now happened, and after having cleaned up, I was wonder if it...

Unfortunately migrating to a newer OS is not possible at this time, so if it is not possible to create a working template from an ISO I guess I will just have to keep it in an OpenVZ system in a VM. Not optimal but works.

Sorry, I mean Centos 6 - is the oldest one. I need to get it running on the original version. At the moment I do it by running an OpenVZ server in a VM, but it's kind of a clunky solution.

The oldest template I have been able to find is Centos 5, I'd need Centos 4.

No, the problem is not solved. The container didn't work the way I did it first. I suppose I need to make a template out of the RHEL 4 iso I have, but I don't know how? What do you mean "could have cloned the RHEL container" ?