Re: NetBSD 5.1.2 under Xen 4 HVM

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

On 9 March 2012 14:20, Stephen Borrill <netbsd%precedence.co.uk@localhost> 
wrote:
> On Fri, 9 Mar 2012, Chavdar Ivanov wrote:
>>
>> I am repeating myself as of a few weeks ago - the best as far as
>> NetBSD under XenServer is concerned is to run it on PV mode with
>> XEN3_DOMU kernel. Of course you need to copy your kernel to
>> /boot/guest directory on the server and change the OS-boot-parameters
>> to "boot_verbose=1,vfs.root.mountfrom=ffs:/dev/xbd0s1a,kern.hz=100",
>> have the PV-kernel parameter set to the kernel (  xe vm-param-get
>> uuid=db74941f-2ccc-9c01-ecb2-bc2e26ffce19 param-name=PV-kernel returns
>> for me /boot/guest/netxen ).
>
>
> No, you don't need go through the complexity of copying kernels to the dom0
> as you can use pygrub to load the kernel from the domU's filesystem (only
> FFSv1 is supported, so watch out if using NetBSD 6 or -current).
>
> http://wiki.precedence.co.uk/Support-KB-NetBSD/XenServer
>
> Or download a .xva from:
> ftp://ftp.netbsd.org/pub/NetBSD/misc/XenServer/
>
> When there is finally a NetBSD release with the required support in xennet,
> I'll update those .xva files.


Thanks for that; I'll go through the motions to test it for myself.
What I did in this case was to stumble upon the FreeBSD instructions
at http://forums.freebsd.org/showthread.php?t=24936 and interpret them
for NetBSD-current. It worked fine for me.

The wiki needs a little edit now that MULTIPROCESSOR is default for
-current (and works well as far as I can see, networking as well ...

xci@support6 ~ % uname -a
NetBSD support6 6.99.3 NetBSD 6.99.3 (MYDOMU) #4: Sun Mar  4 22:36:05
GMT 2012  root@support6:/usr/src/sys/arch/amd64/compile/MYDOMU amd64
xci@support6 ~ % ifconfig -a
xennet0: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 16:b0:8c:76:8a:80
        inet 10.1.32.6 netmask 0xff000000 broadcast 10.255.255.255
        inet6 fe80::14b0:8cff:fe76:8a80%xennet0 prefixlen 64 scopeid 0x1
xennet1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
        enabled=0
        address: 9e:ff:36:b8:77:85
        inet 172.16.200.6 netmask 0xffffff00 broadcast 172.16.200.255
        inet6 fe80::9cff:36ff:feb8:7785%xennet1 prefixlen 64 scopeid 0x2
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
xci@support6 ~ % dmesg | grep CPU
vcpu0 at hypervisor0: Intel(R) Xeon(R) CPU           X5450  @ 3.00GHz,
id 0x1067a
vcpu1 at hypervisor0: Intel(R) Xeon(R) CPU           X5450  @ 3.00GHz,
id 0x1067a
vcpu2 at hypervisor0: Intel(R) Xeon(R) CPU           X5450  @ 3.00GHz,
id 0x1067a
vcpu3 at hypervisor0: Intel(R) Xeon(R) CPU           X5450  @ 3.00GHz,
id 0x1067a
....

>
> --
> Stephen
>

Chavdar

-- 
----