On Wed, Nov 15, 2006 at 05:53:20PM -0500, Michael Richardson wrote:
> Jed Davis wrote:
> >Michael Richardson <mcr@sandelman.ca> writes:
> >As I understand it, an old kernel won't run on a new hypervisor, but a
> >new kernel (at least for NetBSD) can run on an old Xen.  I don't think
> >whether it's dom0 or domU has anything to do with it -- the change was
> 
>   okay, I have a FC5-2239 kernel:
> 
> [root@grouper xen]# uname -a
> Linux grouper.sandelman.ca 2.6.18-1.2239.fc5xen0 #1 SMP Fri Nov 10 13:58:27 
> EST 2006 i686 i686 i386 GNU/Linux
> 
> and I have a NetBSD-current compilation from Nov. 6, 2006.

What does
xm info
reports ?

> 
> 
> [root@grouper xen]# cat merry
> name = "merry"
> memory = "16"
> disk = [ 'phy:/dev/VolGroup00/MerryRoot,0x03,w' ]
> root = "/dev/wd0d"
> vif = [ 'mac=00:16:3e:00:a0:30' ]
> kernel = "/guests/kernel/netbsd.XEN3_DOMU.current"
> #cpu = -1
> 
> #on_reboot   = 'restart'
> #on_crash    = 'restart'
> 
> [root@grouper xen]# xm create -c merry
> Using config file "merry".
> Started domain merry
> [root@grouper xen]#
> 
> I don't get any errors that I can find.

Did you check /var/log/xen/ ?

> (I'm very unimpressed with the error recover of these python scripts)

Yes, it's very bad. It doesn't always print and error message and when it
does it doesn't containt the complete informations to fix the problem
(e.g. "no such file or directory" without saying which file is tried
to open). ktrace is your friend :)

-- 
Manuel Bouyer <bouyer@antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--