Re: Xen 4.2 added to pkgsrc

[jnemeth%victoria.tc.ca@localhost (John Nemeth)]

On Oct 11,  4:03am, David Brownlee wrote:
}  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 xen box from 4.1 to 4.2,
} and may have picked up some possible xentools42 issues.

     Nice.

} 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

     Fixed.

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

     Not sure what this is, or why it was needed?

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

     I turned oxenstored.conf into a proper config file.  The xen build
system was just stuffing it into PKG_SYSCONFDIR.

} 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...190
} s...185s...180s...175s...170s...165s...160s...155s...150s...145s...140s...1
} 35s...130s...125s...120s...115s...110s...105s...100s...95s...90s...85s...80
} s...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@redha=
} t.com
} 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

     Nothing useful here.

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

     Why are you using a hexadecimal number for your disk device?  For
an PV linux domU, my disks look like:

#disk = [ 'phy:/dev/mapper/vg0-domu--fedora,xvda,w' ]
#disk = [ 'phy:/dev/mapper/vg0-domu--fedora,xvda,w', 
'file:/usr/local/isos/Fedora-17-x86_64-DVD.iso,xvdb,r' ]
disk = [ 'phy:/dev/mapper/vg0-domu--fedora,xvda,w', 
'file:/usr/local/isos/Fedora-18-Beta-x86_64-DVD.iso,xvdb,r' ]
#disk = [ 'file:/mnt/fedora,xvda,w' ]

And, for an HVM linux domU, my disks look like:

disk = [ 'phy:/dev/mapper/vg0-domu--hvmlinux,ioemu:hda,w' ]
#disk = [ 'phy:/dev/mapper/vg0-domu--hvmlinux,ioemu:hda,w',
#         'file:/usr/local/isos/hvmlinux-6.0rc12.iso,ioemu:hdc:cdrom,r' ]

Notice that I use xvda and xvdb, or hda and hdc, depending on the type
of client.  Also, do you have enough vnds (i.e. does vnconfig -l show
any empty slots).  When I setup a Xen system with a bunch of domUs
using file based disks, I found that I had manually MAKEDEV a bunch of
vnds.  The problem symptom was that the domU couldn't get a disk.  I'm
assuming that jira.img isn't in use by anything else.

} Rolling back to 41 for now :)

     That's too bad.  Maybe this update will smooth out some of the issues.

}-- End of excerpt from David Brownlee