Xen 4.2 added to pkgsrc

     I've just committed sysutils/xenkernel42 and sysutils/xentools42.
They have had fairly extensive testing, but they are just initial
commits.  I've added them so that people can test them, break them,
improve them, etc.

     Note that xm/xend is deprecated but they do still work.  xl is
working in this version.  But, I've only tested it with file backed
vbds.  I haven't tested it with LVM or raw partitions.

     Major things that don't work yet are HVM and grant tables.  The
issue with HVM is that Qemu wasn't compiling, and I just commented it
out in order to move forward.  The issue with grant tables is that it
appears that the interface has changed and I haven't fully adapted the
code.

     So, have at it.  Let me know what breaks.  Patches would be
greatly appreciated (or just commit if you have cvs access).
Otherwise, I need enough details on what breaks in order to
duplicate/fix the problem.

     One thing to note is that Xen 4.3.0rc1 was released a week ago.
This raises the question of whether to spend a lot of time working on
improving the Xen 4.2 packages, or switch to starting work on the Xen
4.3 packages?  Any thoughts on this question?

iPod in windows domU

Hello,

So after realizing that libgpod does not support 7th gen iPods, I'm
looking for alternative ways to upload some music there.

I have a NetBSD dom0 at home. Wondering if it would be possible to xm
block-attach the iPod, make it visible in a Windows VM and use iTunes
from there? Anyone tried a similar scheme?

Regards,

Hugo

Fwd: Xen 4.2 xl - failed to create bootloader dir /var/run/xen/bootloader ...

Hi, just wanted to report that I bumped into this while creating a DomU (debian)

libxl: error: libxl_bootloader.c:364:libxl__bootloader_run: failed to
create bootloader dir /var/run/xen/bootloader.3.d: No such file or
directory
libxl: error: libxl_create.c:919:domcreate_rebuild_done: cannot
(re-)build domain: -3

Dom0 is netbsd 6.0.1, Xen 4.2 compile from source!

This is a mirror problem has the dir (/var/run/xen) can be manually
created, but I guess this should be created while installing (or not )

PS: While testing I also found that xencommons requires xend and
probably shouldn't.

Thanks for keeping improving Xen support on netbsd!

Mike

NetBSD xencommons not starting on boot

I noticed that after settings xencommons=YES on rc.conf the daemon
wasn't starting!

I looked at /var/run/rc.log and found this:

running /etc/rc.d/xencommons]
.: Can't open /etc/xen-hotplugpath.sh
/etc/rc.d/xencommons exited with code 2
[running /etc/rc.d/xend]
.: Can't open /etc/xen-hotplugpath.sh
/etc/rc.d/xend exited with code 2
[running /etc/rc.d/xen-watchdog]
.: Can't open /etc/xen-hotplugpath.sh
/etc/rc.d/xen-watchdog exited with code 2
[running /etc/rc.d/xen-hotplugpath.sh]

I had it on /etc/rc.d .... because xencommons has this lines:
DIR=$(dirname "$0")
. "${DIR}/xen-hotplugpath.sh"

In any case just for testing I move xen-hotplugpath.sh to /etc/xen...
and run /etc/rc.d/xencommons start and now I get:
# /etc/rc.d/xencommons start
.: Can't open /etc/rc.d/xen-hotplugpath.sh

What could be the reason for "dirname" to get a different result while
booting and after I'm logged in?

NOTE: Running netbsd 6.0.1, xen 4.2 compiled from source

Re: iommu hardware and vga pass through with nbsd 6 dom0

Am 29.04.2013 16:41, schrieb Sam Fourman Jr.:
> There hasn't been a update to this thread, im trying to figure out if
> NetBSD 6x or even HEAD supports AMD-Vi and vga passthrough.
I finally gave up. PCI pass through didn't work. Back in January, I 
tried to quick fix libxl_device_pci_reset(). Afterwards, I stepped into 
errors behind that procedure (mainly, because xl expected Linux style 
/sysfs etc.).
So I wasn't convinced that Xen 4.1 and NBSD 6.0 works properly in all cases.

Furthermore I own a Gigabyte 970A-UD3 which suffers from [0]. So I'm not 
sure, if the problems I encountered a board specific or not.

Regards,
Marcus

[0] http://lists.xen.org/archives/html/xen-devel/2013-03/msg01018.html

Re: iommu hardware and vga pass through with nbsd 6 dom0

On Mon, Apr 29, 2013 at 10:41:26AM -0400, Sam Fourman Jr. wrote:
> There hasn't been a update to this thread, im trying to figure out if
> NetBSD 6x or even HEAD supports AMD-Vi and vga passthrough.
> 
> can anyone confirm that they have seen or heard of this working on NetBSD?

vga passthrough, probably not. AMD-Vi is probably mostly a hypervisor
things, maybe no specific support is needed on the NetBSD side.

--

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

serial console

On a particular -current/amd64 box, NetBSD + serial console is
fine, XEN_DOM0 on pc console is fine. However with the following
incantation nothing appears on the end of the serial line, nor on
the screen:

menu=Boot Xen 4.1 debug dom0 (com0):load /netbsd-XEN3_DOM0 console=com0;multiboot /xen-debug.gz dom0_mem=512M

I can ssh in and all is OK, but I can't see console output...

BIOS and NetBSD bootblocks set baud rate to 115200. I tried 115200 and 9600
in the hope of seeing something. Is the incantation wrong?

Cheers,

Patrick

Xen GSoC 2013: Testing NetBSD

Hi,

http://wiki.xen.org/wiki/GSoC_2013#Testing_NetBSD

Christoph

HEAD/6.1_RC2 DOM0 problems?

I just tried a 6.1_RC2 dom0 kernel on a dual opteron box which was 
working fine with a pre-6.0 dom0 kernel, and which works fine with a 
6.1_RC2 GENERIC.  Things seem to start booting ok, then
really slow down once they get to wd1, and eventually hang altogether.  
I've seen it get as far as:

root file system type: ffs

... but I've also seen it hang slightly earlier (after detecting wd1, 
somewhere in the USB).

I tried a 6.0.1 dom0 kernel, and it works fine.  A -current dom0 from 
20130322, though, hangs *even earlier*:

NetBSD 6.99.18 (XEN3_DOM0) #0: Fri Mar 22 12:55:23 UTC 2013
builds <at> b8.netbsd.org:/home/builds/ab/HEAD/amd64/201303221130Z-obj/home/builds/ab/HEAD/src/sys/arch/amd64/compile/XEN3_DOM0
total memory = 256 MB
avail memory = 232 MB
mainbus0 (root)
cpu0 at mainbus0 apid 0
cpu1 at mainbus0 apid 2
cpu2 at mainbus0 apid 1
cpu3 at mainbus0 apid 3
ioapic0 at mainbus0 apid 4
(XEN) ioapic_guest_write: apic=0, pin=0, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0
(XEN) ioapic_guest_write: old_entry=00010000 pirq=0
(XEN) ioapic_guest_write: Attempt to modify IO-APIC pin for in-use IRQ!
(XEN) ioapic_guest_write: apic=0, pin=2, irq=0
(XEN) ioapic_guest_write: new_entry=000109f0

State of Stub- and Driver-Domains on NetBSD/Xen

mbuf leak on 6.0.1?

Hi

On NetBSD 6.0.1 (XEN3_DOMU) / Xen 3.1.4, the machines loose the network 
after some time. The kernel says:
WARNING: mclpool limit reached; increase kern.mbuf.nmbclusters
WARNING: mclpool limit reached; increase kern.mbuf.nmbclusters

Raising NMBCLUSTERS did not help. It is currenty set as 16384 and
this is the maximum. The reliable workaround is:
  ifconfig xennet0 down; ifconfig xennet0 up

It looks like a mbuf leak, are there known such problems? 

--

-- 
Emmanuel Dreyfus
manu <at> netbsd.org