Re: xen-4.5 and -current/amd64

[Harry Waddell <waddell%caravaninfotech.com@localhost>]

On Fri, 19 Jun 2015 22:29:48 +0100
Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:

> On Fri, Jun 19, 2015 at 02:19:33PM -0700, Harry Waddell wrote:
> > On Fri, 19 Jun 2015 22:08:39 +0100
> > Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:
> > 
> > > I'm running a XEN3_DOM0/amd64 from today's source, with pkgsrc-current
> > > xen*45, and xenstored & xenconsoled are running.
> > > 
> > > I have a file /scratch/disk.img, in which a -current/amd64 release was
> > > unpacked. /scratch is /dev/raid6a, and also has the same files unpacked.
> > > 
> > > I don't seem to be able to find the right incantation to start a
> > > XEN3_DOMU/amd64 from today's source.
> > > 
> > > name = "leucite"
> > > kernel = "netbsd-XEN3_DOMU"
> > > vcpus = 2
> > > memory = 1024
> > > disk = ['file:/scratch/disk.img,hda,w']
> 
> > You may want to try changing "hda" to "xvda" in your disk
> > definition. 
> 
> Thanks for the suggestion - I just tried
> 
> disk = ['file:/scratch/disk.img,xvda,w']
> 
> Parsing config from leucite.cfg
> libxl: error: libxl_create.c:1153:domcreate_launch_dm: unable to add
> disk devices libxl: error:
> libxl_device.c:797:libxl__initiate_device_remove: unable to get my
> domid libxl: error: libxl.c:1640:devices_destroy_cb:
> libxl__devices_destroy failed for 24
> 
> so still no joy...
> 
> Cheers,
> 
> Patrick
> 

I assume you have xencommons=YES in your /etc/rc.conf, etc... 

Here are some things you may want to try:

1. vnconfig vnd3 /scratch/disk.img
   and set 

	disk = ['phy:/dev/vnd3d,xvda,w']

   to rule ount any problems with xen getting vnode devices for your file: based disks.

2. examine the logs in /var/logs/xen for clues. Also see "xl dmesg". 

3. Use "xl -vvvv create domname" to create the domU to get more debugging info

Good luck!

Harry Waddell