I will be updating my Xen hosting machine tomorrow .. if there are any gotchas I'll let you know!

Steve

I upgraded my dom0 from sarge (with a few extra packages from backports.org) to etch and it was completely painless.

I had to review a number of configuration files, but otherwise it was all ok.

I have finally migrated a minor (i.e. not critical) Xen server. No real problems, just minor ones :

• the migration installed the xen-hypervisor package with PAE installed. I thought PAE was for high-memory systems, so I removed it and installed the non-PAE one. Xen never boot, complaining about PAE not on Xen, but on dom0. I didn't search a lot about this problem, but the reinstallation of the package solved it
• domUs can't boot because of the vmlinuz and initrd versions specified in their conf files!! easily solved :)
• don't forget to enable your network in the Xen configuration file ;-)

So, apart from 'custom' errors, no real problems, I just followed the guidelines from the debian.org site. Now, I can work on another Xen dom0 migration, and on my domU sarge installations.

:eric:
http://blog.sietch-tabr.com

For the dom0, it's very easy. Just apt-get dist-upgrade with the good source.list. But, after reboot, your domU will not start ! You have to shutdown them, mount their root filesystem in the dom0 and rsync the new /lib/modules... For example, the dom1 use the partition /dev/vg1/vm1-disk

 xm shutdown vm1

 mkdir /tmp/vm1
 mount /dev/vg1/vm1-dis /tmp/vm1

 rsync -av /lib/modules/*xen* /tmp/vm1/lib/modules/

 umout /tmp/vm1

 reboot

I had a problem with the network for two domU because I let the domU on Sarge, without upgrading their /lib/modules, and I just upgrade the dom0 to Etch.