Lenny upgrade

[neuroscr]

The url:

http://pve.proxmox.com/debian/dists/lenny/pve-upgrade-1.1-to-1.4

is 404 for me. I checked to make sure its resolved to the right IP (posted in another thread).

Any one have a copy of this script?

With 1.5 out, I'm finally ready to take the plunge and upgrade, though 1.1 has been working great for me.

 

[dietmar]

The url:

http://pve.proxmox.com/debian/dists/lenny/pve-upgrade-1.1-to-1.4

is 404 for me. I checked to make sure its resolved to the right IP (posted in another thread).

Sorry, but we do not longer support that upgrade script. If you are familiar with debian package management you can update manually using standard tools (apt, aptitude). If not consider reinstalling.

 

[neuroscr]

Of course, I get a reply right after, I do something drastic.

Dietmar, yea that's what I did:

apt-get update

but I got:

W: There is no public key available for the following key IDs:
9AA38DCD55BE302B
W: GPG error: http://ftp.us.debian.org etch Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9AA38DCD55BE302B
W: You may want to run apt-get update to correct these problems

So, I googled that and came up with this, which fixed it:

gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 9AA38DCD55BE302B
apt-key add /root/.gnupg/pubring.gpg

And I tried it again and it worked:

apt-key update
apt-get upgrade
edited /etc/apt/sources.list
replaced all etch with lenny
apt-get update
apt-get dist-upgrade
reboot

and from 1.1 to 1.5, bam. It seemed to break the virtio drivers for windows, so I had to revert that back to the normal driver. I run KVM and OpenVZ.

Dietmar, You guys do a great job. I was so paranoid, if this machine didn't come back online, it was like 20 machines don't come back online. I'm really impressed it worked (almost) flawlessly.

 

[dietmar]

What is the output of

# pveversions -v

 

[neuroscr]

Output of pveversion -v:

pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-2-pve
pve-kernel-2.6.24-1-pve: 2.6.24-4
pve-kernel-2.6.24-2-pve: 2.6.24-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve6
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

It removed the older kernel (2.6.18) looks like. And now that I take a closer look, I'm not at the latest 2.6.24 kernel.

 

[dietmar]

You should install one of the 'proxmox-ve-<KERNEL-VERSION>' packages. Those virtual packages contain dependencies to latest available kernels and other packages - this makes your live easier.

http://pve.proxmox.com/wiki/Proxmox_VE_Kernel

 

[tom]

....

and from 1.1 to 1.5, bam. It seemed to break the virtio drivers for windows, so I had to revert that back to the normal driver. I run KVM and OpenVZ.

.....

see http://www.proxmox.com/forum/showpost.php?p=17219&postcount=19

it looks that old virtio drivers aren´t working anymore.