Search results

Hi I just upgraded to proxmox 4 stable, and I'm trying to make a snapshot backup (backup tab) on a running LXC (filesystem LVM on ext4) As It said here that snapsnot for LVM thin pools will be available later. What does that mean ? I'll need to reinstall all my container ? Will it be...

Thank you for your answer. But in order to plan my partition layout, do you know if lxc snapshot would be possible on the same lvm volume (/dev/pave/data) ?

On proxmox 3.x I use the /dev/pve/root to make snapshot backup of openvz container (because you can't make a backup on the same lvm volume). Today I try the same thing with proxmox 4b2 and a LXC CT, but it didn't work : INFO: mode failure - some volumes does not support snapshots INFO: trying...

Hi Indeed, I don't know where was the problem but after a reboot its works ... Thank you

Hi I set up a new proxmox 4b2 server (on ext4, default partitions) but I'm unable to create a LXC container. At the end of the GUI wizard, I receive this message : Parameter verification failed. (400) disk: property is not defined in schema and the schema does not allow additional properties...

Hi I'm running the last version of promox (3.2). And for the 1st time, I tried to use spice to acces my VM (1 kvm with win7-64 and some openvz with debian 7 32/64). I installed virt-viewer on my computer, spice guest in win7, and attached .vv file to remote-viewer, but it fails every time I...

Meaning : I need a valid ssl certificat ? (the green one!)

I'm running the latest version of proxmox and java (7u45) but I still got the warning when I launch the console on the webinterface : Java warning: Java : Proxmox : pveversion --verbose proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-23-pve) pve-manager: 3.1-24 (running version...

Update: i migrate all my network interfaces to VENET. No packet have been dropped since. (the tx-drop is only increasing when the CT are starting and the network is not available immediately, after that, no more dropped packet). This is still a strange behavior, i will submit on bugzilla ;)

Little update, it looks like that tx-drop started in early July, which match with my migration to proxmox 3.0 (0 drop, collision before that date). To be confirmed, it could come from Munin which wasn't logging this information on Debian 6 / proxmox 2.3...

Hi I'm using proxmox since few months, and I just notice a lot of "TX Drop" on all my CT : Some details to help you understand my network configuration : - veth100.0 = eth0 for CT100 (public ip) = vmrb0 = eth0, - veth100.1 = eth1 for CT100 (private ip) = vmrb1 = private bridge not link to...