I put my server on the rack today and xen1.xcski.com is open for business. I’ve already moved the Rochester Flying Club and Rochester Association of Family Mediators web sites over. As the DNS changes propogate, I’ll be able to remove the ones on the linode.
It appears that mail is working on the new site as well, so I’ll move the mailman mailing lists over pretty soon. I’ll probably move this blog over there as well. Then comes the hard part – moving the navaid.com application over.
The only sour note is that when I started up the rack, one of the quarter share xens didn’t want to come up correctly. It complained about tons of fsck errors, and I decided to just wipe it and re-install it. I hope that doesn’t happen again. One thing I noticed is that the xen kernel doesn’t have the ext3 module compiled in, and so it’s mounting these file systems without journalling. I’m going to have to fix that.
Any excuse to say “Nice rack, Paul!” is good by me.
No ext3 support is interesting, fsvo “interesting”. Good luck!
xen kernels can load initrd images roughly the same way
normal ones do, and it can contain ext3.ko.
See the “ramdisk” attribute in your xen config file.
Frank, the problem is that all the instructions I’ve found for doing a “mkinitrd” say to use the “-v -f” options, and the version of mkinitrd on Debian Sarge doesn’t take those options.
Ok, to answer my own answer, it appears that Debian’s mkinitrd is much simpler – you load the modules you want, then you type “mkinitrd -o /boot/initrd-xen.img 2.6.18-xen” and it makes the ramdisk for you. I loaded the ramdisk for the domUs, and they didn’t give that warning about mounting ext3 as ext2 any more.