Re: Xen 4.2 added to pkgsrc

[David Brownlee <abs%netbsd.org@localhost>]

 On 15 May 2013 08:18, John Nemeth <jnemeth%victoria.tc.ca@localhost> wrote:
>      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.

Many thanks for this. Just updated an 8 guest xn box from 4.1 to 4.2,
and may have picked up some possible xentools42 issues.

In the installed package /usr/pkg/bin/pygrub was a symlink to itself.
Manually copied work/xen-4.2.2/tools/pygrub/build/scripts-2.7/pygrub
to /usr/pkg/bin

/var/run/xen/bootloader.1.d was not present - created by hand to continue

etc/xen/oxenstored.conf was not present - I set PKG_SYSCONFBASE?=/etc
for some packages so that would be related.

On starting the guests (CentOS 6) they seemed to fire up ok but then exited.

The console had:
XENBUS: Waiting for devices to initialise:
295s...290s...285s...280s...275s...270s...265s...260s...255s...250s...245s...240s...235s...230s...225s...220s...215s...210s...205s...200s...195s...190s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...135s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80s...75s...70s...65s...60s...55s...50s...45s...40s...35s...30s...25s...20s...15s...10s...5s...0s...
XENBUS: Timeout connecting to device: device/vbd/51712 (local state 3,
remote state 2)
Loading dm-mod.ko module
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: 
dm-devel%redhat.com@localhost
Loading dm-log.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Loading dm-mem-cache.ko module
Loading dm-region_hash.ko module
Loading dm-message.ko module
Loading dm-raid45.ko module
device-mapper: dm-raid45: initialized v0.2594l
Scanning and configuring dmraid supported devices
Scanning logical volumes

[then exited]

cat xl-jira.log.2
Waiting for domain jira (domid 20) to die [pid 26919]
Domain 20 has shut down, reason code 0 0x0
Action for shutdown reason code 0 is destroy
Domain 20 needs to be cleaned up: destroying the domain
Done. Exiting now

the .cfg for that VM:
name = "jira"
memory = "1536"
disk = [ 'file:/opt/xen/img/jira.img,0xca00,w', ]
vif = [ 'mac=02:00:00:00:01:03, bridge=bridge0', ]
bootloader = "/usr/pkg/bin/pygrub"
vcpus = 3

Rolling back to 41 for now :)