Re: NetBSD vs Linux

[Victor Dorneanu <victor%dornea.nu@localhost>]

Manuel Bouyer wrote:
>> Where do I see that? After booting the dom0 I wasnt able to see the
>> device I used in "pciback.hide=".
>>     
>
> in dmesg of the dom0 (or /var/run/dmesg.boot)
>
>   
>> Hmmm... Is it possible to use xentools3 + xenkernel33 and vice versa?!
>>     
>
> I'm not sure this will work.
>
>   

This whole issue is driving me nuts... Today I reinstalled xentools3 +
xenkernel3 after having noticed that the pciback support in 3.3.x 
wasn't ported yet to NetBSD. I used the same config as I did before and
got a strange error message:

---------------------------------------------

$ head -n 3 /usr/pkg/etc/xen/linux
#----------------------------------------------------------------------------
# Kernel image file. This kernel will be loaded in the new domain.
kernel = "/vmlinuz-2.6.30-amd64"

$ xm create -c linux
Using config file "/usr/pkg/etc/xen/linux".
Error: (2, 'Invalid kernel', 'xc_dom_find_loader: no loader found\n')

$ file /vmlinuz-2.6.30-amd64
vmlinuz-2.6.30-amd64: Linux kernel x86 boot executable RO-rootFS,
root_dev 0x901, swap_dev 0x2, Normal VGA

$ file /vmlinuz-2.6.18-xen
vmlinuz-2.6.18-xen: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
statically linked, stripped (<-- STRANGE ?!)

---------------------------------------------

The standard Xen Linux domU kernel (vmlinuz-2.6.18-xen) differs from
previously installed Linux image "vmlinuz-2.6.30-amd64". Why does Xen
not recognize the 2.6.30 kernel image? Am I missing something?

-- 
Victor Dorneanu