Search results

Squeeze is LTS and end users decide on what to do on EOL based on their technical competence and back porting fixes. My first post's /etc/apt/sources.list mods before an apt-get update && apt-get dist-upgrade still works.

Try clonezilla backup and then restore to smaller VM disk.

In order to use the newer TKL LXC templates in OpenVZ / PVE 3.x, are there any changes that need to be made to appliance info file inside the template? Please provide the openvz release file also with the lxc replaced with openvz. To prevent error on pveam update, till then, we need to comment...

Since Debian 6 (Squeeze) is now EOL and still gets LTS with the repos placed in archive, maintaining it will need the following in /etc/apt/sources.list: deb http://archive.debian.org/debian squeeze main contrib deb http://archive.debian.org/debian squeeze-proposed-updates main contrib deb...

Posted a Wiki Article on building Elastix OpenVZ container. Request feedback on PVE 4.1 / LXC for issues in using Elastix as in OpenVZ. Please post any migration of PVE 3.4 Elastix OpenVZ container to LXC in PVE 4.1 issues.

What version of Proxmox are you using and what version of noVNC. Pointing to the Git page for the said file would be useful along with before and after screenshots.

do a search for files in etch's mysql-server-5.0 package: dpkg -S mysql-server in both the new and old containers and see if you can stop mysql-server in both and copy over the files from the old to the new container and then start the mysql-server. If necessary do the same for the mysql-client...

pve-kernel 2.6.32 build 3.4-172 has been released. It addresses #896

The MySQL may be old and custom compiled. The data can be dumped out and imported into your new VM. All you might then need are the my.cnf and .my.cnf and my.ini files

Install on another hard disk and then copy over the root and other folders you need. When installing Proxmox, take a clonezilla image of each partition / lvm and you can then restore at will.

To stay within the Debian Version / PVE Version: apt-get update apt-get dist-upgrade

2 versions of pve-manager were released in the last couple of days. You may have been caught in the crossfire. You may want to "butcher" it further by doing an apt-get update && apt-get dist-upgrade again. See this post for the current versions. You can also revert to a previous kernel as well...

As PVE 3.4 is now approaching EOL, the last versions are listed here: # pveversion -v proxmox-ve-2.6.32: 3.4-171 (running kernel: 2.6.32-44-pve) pve-manager: 3.4-13 (running version: 3.4-13/4c745357) pve-kernel-2.6.32-44-pve: 2.6.32-171 lvm2: 2.02.98-pve4 clvm: 2.02.98-pve4 corosync-pve...

This bug was reported in Fedora 20 and since it was EOL and no test was reported thereafter, it was left in limbo. The kernel module fix is available for those who want to compile it themselves: https://lkml.org/lkml/2014/4/24/40 http://www.gossamer-threads.com/lists/linux/kernel/1909763...

The following config for a Prolink PRO700SFCU UPS (/etc/nut/ups.conf) works for Proxmox 3.4-13: [prolink] driver = blazer_usb subdriver = cypress port = /dev/ttyS0 vendorid = 0665 productid = 5161 desc = "Prolink UPS" protocol = mustek default.battery.voltage.high = 13.60...

Reversion to several earlier BIOSes including the one on which the Proxmox install was done and then re-installing Proxmox v3.4-6 several times resulted in the same install error. Tested out the hard disk with the WD Lifeguard Diagnostic tool and found read errors from 90% onwards. Replaced...

Attempted a re-install of PVE3.4-6 and the following error popped up at the end of the install (100%): Expect that this is a disk failure or a BIOS goofup. AHCI Mode HDD in BIOS - SATA Port 0. Disk and mainboard are SATA II (3 GBps). CTRL-ALT-F2 showed the following: An earlier Exit Code...

After install of the PVE 3.4-6 on an Atom machine (WD Green 2TB HDD, 4 GB RAM, OpenVZ only - no VT-x, no VT-d), the BIOS was updated and the machine booted into "grub rescue" mode with the following error: error: attempt to read or write outside of disk 'hd0'. Referred this page and tried the...

Thanks @dietmar. Including it in PVE 3.4x would be useful for reference while troubleshooting. I see that it is included in line 543 in PVE 4.1's APT.pm file. For those who want it in PVE 3.4, replace line 536 in it's /usr/share/perl5/API2/APT.pm: push @list, qw(lvm2 clvm corosync-pve...

Today there has been 2 releases of pve-qemu-kvm (now at v2.2-22) package along with a new pve-firewall (v1.0-22) package. The version of the latter is not available in pveversion -v command output.