Recent content by pmlearner

Hello, I have old openvz ve's (base os centos 5 and 6 - don't ask). What is the best way to move these to lxc (or anything else you recommend). They are located on a server running openvz (not proxmox). Is there a way to transfer the (/vz/private/ve_number) and conver to lxc? Thanks in advance.

It is my understanding that virsh, etc. do not work with proxmox but instead one should only use the qm tools. Is there a way with qm or other tools to learn the IP of a kvm server on my proxmox node? Thanks!

on lxc it seems all containers share the same load average, dmesg, etc. I have found a way to lock out dmesg but still not ideal (now there is just no dmesg at all for containers). I need full separation for my containers. Let me know if I'm missing something to make lxc more isolated. I'm not...

Thanks for the reply. I'm not using zfs though. Very good idea though as full disks can indeed cause all sorts of problems. I've checked and all disks look good.

journalctl -xe shows: Jun 11 15:19:22 Proxmox-VE pct[6404]: <root@pam> starting task UPID: Proxmox-VE:00001905:00F83B11:5EE22F5A:vzstart:114:root@pam: Jun 11 15:19:22 Proxmox-VE pct[6405]: starting CT 114: UPID: Proxmox-VE:00001905:00F83B11:5EE22F5A:vzstart:114:root@pam: Jun 11 15:20:52...

perhaps this is a systemd issue as : systemctl status pve-container@114.service times out : Failed to get properties: Connection timed out I tried to restart systemd without a reboot : systemctl daemon-reexec but the containers still will not start

pct mount and unmount works correctly for the containers

Thanks for your help, pvesm status returns : root@Proxmox-VE ~ # pvesm status Name Type Status Total Used Available % local dir active 2077376896 209124764 1762657356 10.07% It takes a good while for the start...

After many days of both containers and vm's running fine, I suddenly cannot start any containers (vm's still start). Fails from both command line and gui with : Failed to start pve-container@126.service: Connection timed out See system logs and 'systemctl status pve-container@126.service' for...

I'm coming from an openvz background (pre-ploop) where all files were in /vz/private/VEID. All my hosts and containers/VMs are Linux. The advantages for me are : - easily copy files in and out of container. - mass update containers (outside of a normal package) - if security required a...

Is it possible to create (and/or convert) a virtual machine (kvm) that uses a local directory instead of disk image such as qcow2, etc.? For containers I can do : -rootfs /vz/private/$VEID,size=20G Thanks!

I've stopped the webgui at some point in the past and now want to restart it. I tried: systemctl start pveproxy but get in the logs: pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset: enabled) Active: failed (Result...

Sorry, I thought I was being a "good" forum member by NOT starting a new thread for which an existing very similiar thread existed. The most logical subject for my new thread will be "Proxmox start / restart command?" which is the same title as this thread. I specifically made sure I searched...

Following up with a similiar issue. I've stopped the webgui at some point in the past and now want to restart it. I tried: systemctl start pveproxy but get in the logs: pveproxy.service - PVE API Proxy Server Loaded: loaded (/lib/systemd/system/pveproxy.service; enabled; vendor preset...

Has this changed any? My lxc instances can read dmesg from the host and also clear dmesg. I need to have lxc such that a compromised lxc cannot clear dmesg on the host. Any ideas?