On Fri, Oct 31, 2008 at 7:17 PM, Kenneth Tanzer ktanzer@desc.org wrote:
What I ended up doing was looking at my working CentOS PV guest, listing all the modules, and finding the ones that were not loaded in my AsteriskNow guest. That seemed to do the trick, and it booted. (Once I realized that the initrd file had to be in /boot on the _host_, not the guest!)
Unfortunately, as it turns out, there are then a bunch of additional Asterisk modules that I would need to build for the xen kernel, and I didn't have any luck finding the source, so I think I might give up on this for a while.
Thanks very much for your help!
Ken
p.s., I felt like I spent a bunch of time scratching my head on this stuff because I couldn't find good, clear documentation. Is there such documentation to be found somewhere, or is it just lacking at this point?
There really isn't good, clear, complete documentation on all of this. It is a bit scattered in READMEs, some on the xen wiki, some very good blog and sides site, there are a number of Xen books (I am a co-author on one called Running Xen), but what really needs to happen is the Xen wiki needs to be cleaned up a lot and kept up to date. Xen.org actually has documentation/the wiki in its plans to be worked on soon. I hope that that will help the documentation situation get a lot better.
See our book's website (runningxen.com) for a lot of links and resources.
Cheers, Todd
p.p.s., In case it's useful for others, this is the mkinitrd command I used within the guest, and then copied the initrd to /boot on the host:
mkinitrd --with=i2c_dev --with=ip6table_filter --with=ip6_tables --with=ip6t_REJECT --with=ip_conntrack --with=ip_conntrack_netbios_ns --with=iptable_filter --with=ip_tables --with=ipt_REJECT --with=nfnetlink --with=xenblk --with=xennet --with=x_tables --with=xt_state --with=xt_tcpudp /boot/initrd-2.6.18-92.1.13.el5xen.img.new 2.6.18-92.1.13.el5xen