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.


[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.
(I'm very unimpressed with the error recover of these python scripts)
Maybe my problem is that my config file is wrong.

With the 3.0.2 ABI, I got boot messages and then a panic.

> Also, the hypervisor (xen.gz, sysutils/xenkernel30) version has to
> match the userland xentools or else strange errors result, but that's
> a separate issue.

yes, FC5 takes care of that side of things, in theory.