Recent content by peter

Update applied and problem fixed. Thanks.

On the following proxmox server: # pveversion -v pve-manager: 1.5-1 (pve-manager/1.5/4561) running kernel: 2.6.18-1-pve proxmox-ve-2.6.18: 1.5-3 pve-kernel-2.6.24-10-pve: 2.6.24-21 pve-kernel-2.6.18-1-pve: 2.6.18-3 qemu-server: 1.1-10 pve-firmware: 1.0-3 libpve-storage-perl: 1.0-6 vncterm...

If you look at /usr/sbin/vzdump (it's a Perl script), you'll see the following lines: # by default we set --rsyncable for gzip $ENV{GZIP} = "--rsyncable" if !$ENV{GZIP};

Depends a little on your version of vzdump and PVE. You may have a "Compress" option when defining backups on the PVE web interface. If you want to run a script after the backup has finished, and assuming you want to apply the settings to all vzdump backups, create /etc/vzdump.conf and add...

Thanks Tom. That all seems to work just fine.

I'm trying to migrate from veportal to proxmox (1.5). I did a vzdump on the veportal server and then a vzrestore on the proxmox server. The proxmox server sees the new server, but I can't make any changes. When I ran the following command it became obvious: # /usr/bin/pvectl vzset 100...

No, it has the same behaviour as 2.6.24-9-pve. I think I got mixed up when I initially said I could boot with 2.6.24-10-pve.

Finally fixed :D Thank you very much. /etc/udev/rules.d/70-persistent-net.rules had the entry # PCI device 0x8086:0x107c (e1000) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:21:4d:a1:d1", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" which I changed to eth0.

At this point, I think I'm screwed. Here's a summary of the various kernels 2.6.18-1-pve - boots, but no interfaces come up. Gets the error eth0: ERROR while getting interface flags: No such device SIOCSIFNETMASK: No such device 2.6.24-9-pve...

Setting VIRTUOZZO=no in /etc/vz/vz.conf allows apt-get install proxmox-ve-2.6.32 to complete successfully. But you're saying that 2.6.32 has no openvz support? What's the latest kernel I can use with openvz support? Alternatively, how do I downgrade to 2.6.18?

I then thought I try to do the install with 2.6.32-1-pve running, as I assumed the reason I got the "Running kernel is not OpenVZ kernel...failed" error was due to me trying to install running a vanilla Debian kernel. However, I got the same results, ie: # uname -r 2.6.32-1-pve # apt-get...

Just to expand on the above, I started from a totally clean debian system and try to install the newer kernel. # uname -r 2.6.26-2-amd64 # dpkg -l | egrep 'pve|prox|vz|qemu' # # cat /etc/apt/sources.list deb http://debian.mirror.iweb.ca/debian/ lenny main deb-src...

Given that Debian Lenny comes standard with rsyslog, I don't see the point in creating a specific syslog appliance.