Search results

I run Plex inside a container. It works very well. It is best to use a 64 bit container, because transcoding is more efficient on 64 bit.

I've just realised that they're showing zero network traffic as well.

The web UI shows "0.0% of 2CPUs" (for example) for all of my LXC VMs, except for one of them that just shows a single "-". All the VMs are working fine. Is this a known bug?

I tried that but couldn't get LXC to work (and I had to change the caching on KVM machines, IIRC). I've given up trying to get it to work, and so I'm temporarily using the "unsupported" mdadm RAID10 with LVM/ext4. I'll move to ZFS at another time. I can live without live snapshots of LXC...

Thanks Tom, that's very clear. I'll eagerly wait 4.1!!

I've read lots of threads and have been struggling since upgrading to PVE4.0 3 days ago. I am now very confused! I read in one that you are currently adding snapshot backups to LVM storage. 1. Does this mean that if I have a directory storage with ext4+LVM I will be able to do snapshot...

OK. Point taken.

No. I have a VE installation, and I use ClamAV to scan the containerised VMs.

For the last week or so I've been getting these warnings. Either my machine is broken, or it needs updating in the repositories I guess. Anyone else with the same problem? LibClamAV Warning: ************************************************** LibClamAV Warning: *** The virus database is older...

Thanks for that advice. I have now sorted out the boot inconsistency, and have opted for 2.6.32. I now feel a complete fool - I finally worked out the problem. My gateway router had an old IP address binding to an ancient physical machine (long since dead). So it was rejecting any packets...

OK, thanks, I'll try that. Any reason why I shouldn't stick with 2.6.32, (and install the proxmox-ve-2.6.32 package) or is 2.6.18 better for OpenVZ? I have a mix of OpenVZ and KVM virtual machines, although to be honest I am most concerned about the performance/stability of the KVM ones.

pveversion -v output: pve-manager: 1.8-17 (pve-manager/1.8/5948) running kernel: 2.6.32-4-pve proxmox-ve-2.6.18: 1.8-14 pve-kernel-2.6.32-4-pve: 2.6.32-32 pve-kernel-2.6.18-5-pve: 2.6.18-14 pve-kernel-2.6.18-4-pve: 2.6.18-10 qemu-server: 1.1-30 pve-firmware: 1.0-11...

Some more information. If I do a "route -n", I get the same output from both the working and non-working containers: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface...

I have a number of openvz VMs, using the Debian 6 PVE template. These use a mix of venet and vmbr networking. They are all working fine. For some inexplicable reason, if I now try to deploy a new VM, everything seems to work, except that the new machine cannot ping the network gateway. It can...

It's been running for six days now without any problems. So maybe it was indeed the memory voltage (which I've increased from 1.25 to 1.35 volts), or maybe I disturbed something else when I open the case.

Thanks for your suggestions. I've run memtest and 3 passes have been completely clean. I've also swapped the PSU (for a bigger one). The system spontaneously rebooted after about 40 minutes with a different PSU :-( I've now tried increasing the memory voltage. The system is using Kingston...

Rebooted after 24 hours with 2.6.18 :(

Every 3 or 4 days my PVE host machine will spontaneously reboot. Nothing in /var/log, and there's no set pattern as far as I can tell. It could be hardware related, but it's standard Intel, no remote storage, and the system is on a UPS. There are two OpenVZ and one KVM VMs, lightly loaded...