I just upgraded from version 1.1 to 1.3 on a HP DL580 with 3 Windows Server 2003 R2 Enterprise KVMs.
1) Everything went fine, but after the reboot of the host and the reboot of the VMs, Windows detected a new network card (e1000, which was also used before the update and therefore the drivers were auto-installed) and assigned DHCP to it. I had to assign the old IP settings to the new network connection but the old network interface is still a valid (only hidden) device for Win, so it gave me a warning about dual assignment of the same IP for two network interfaces, which I ignored.
There are ways to remove the old interface, see
http://support.microsoft.com/kb/315539
IMHO it would be better to not change the guest devices in an upgrade process. Or should this be mentioned somewhere in the PVE wiki?
2) Before the upgrade I copied the firmware files for the Broadcom NetXtreme II to /lib/firmware, just to be sure I am able to use SSH after reboot, but I don't know if this was really necessary (a Debian Lenny installation on similar hardware required the firmware for the NetXtreme card after the upgrade from Etch to Lenny).
Everything else went smooth, great work, PVE team! Keep up the good work!
Mario
1) Everything went fine, but after the reboot of the host and the reboot of the VMs, Windows detected a new network card (e1000, which was also used before the update and therefore the drivers were auto-installed) and assigned DHCP to it. I had to assign the old IP settings to the new network connection but the old network interface is still a valid (only hidden) device for Win, so it gave me a warning about dual assignment of the same IP for two network interfaces, which I ignored.
There are ways to remove the old interface, see
http://support.microsoft.com/kb/315539
IMHO it would be better to not change the guest devices in an upgrade process. Or should this be mentioned somewhere in the PVE wiki?
2) Before the upgrade I copied the firmware files for the Broadcom NetXtreme II to /lib/firmware, just to be sure I am able to use SSH after reboot, but I don't know if this was really necessary (a Debian Lenny installation on similar hardware required the firmware for the NetXtreme card after the upgrade from Etch to Lenny).
Everything else went smooth, great work, PVE team! Keep up the good work!
Mario
