Port-xen archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: xen-4.5 and -current/amd64



Hi,

If you have updated xentools to 4.5 from 4.2, it may be worth
to try to update /etc/rc.d/xencommons with
/usr/pkg/share/exampls/rc.d/xencommons too.

https://mail-index.netbsd.org/port-xen/2015/04/24/msg008624.html
Have you updated /etc/rc.d/xencommons with new
/usr/pkg/share/examples/rc.d/xencommons ?
Old and new slightly differs in domid initialization.


BTW this problem and error messages should be added to xen howto
to be found by google bot.


On 2015/06/20 06:08, Patrick Welche 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']

gets me:

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 18

The same is true for:

disk = ['format=raw, vdev=0x1, access=rw, target=/scratch/disk.img']
disk = ['format=raw, vdev=0x1, access=rw, target=/dev/raid6a']

If I try the character device

disk = ['format=raw, vdev=0x1, access=rw, target=/dev/rraid6a']

I see:

Parsing config from leucite.cfg
Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
     2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015
     The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
     The Regents of the University of California.  All rights reserved.

NetBSD 7.99.18 (XEN3_DOMU) #1: Fri Jun 19 18:26:35 BST 2015
         prlw1@quantz:/usr/src/sys/arch/amd64/compile/XEN3_DOMU
total memory = 1024 MB
avail memory = 982 MB
mainbus0 (root)
hypervisor0 at mainbus0: Xen version 4.5.0
vcpu0 at hypervisor0
vcpu0: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, id 0x306a9
vcpu1 at hypervisor0
vcpu1: Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz, id 0x306a9
xenbus0 at hypervisor0: Xen Virtual Bus Interface
xencons0 at hypervisor0: Xen Virtual Console Driver
xenbus: can't get state for device/suspend/event-channel (2)
xbd0 at xenbus0 id 1: Xen Virtual Block Device Interface
balloon0 at xenbus0 id 0: Xen Balloon driver
balloon0: current reservation: 1048576 KiB
xenbus: can't get state for device/suspend/event-channel (2)
balloon0: current reservation: 262144 pages => target: 262144 pages
ignore shutdown request:

# xl list
Name                                        ID   Mem VCPUs      State   Time(s)
Domain-0                                     0  4096     1     r-----     118.0
leucite                                     21  1024     2     -b----       1.6

If I don't put a disk= line in at all, I am correctly prompted for a
root disk.

Is that tiny configuration really incorrect, or is something amiss?

Cheers,

Patrick


regards,
--
t-hash


Home | Main Index | Thread Index | Old Index