Port-xen archive

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

Xen won't start its device backend?

Hi folks,

I'm trying to get a NetBSD/amd64 to boot as a DomU HVM guest on a NetBSD/xen
Dom0 (amd64). The Dom0 i got booting and running with an X server.

I have xencommons=YES in my rc.conf file and `xl list' works etc.

When i start my DomU i however get:
# xl create -p netbsd-hvm
Parsing config from netbsd-hvm
  Loader:        0000000000100000->0000000000173884
  TOTAL:         0000000000000000->00000000ff800000
  ENTRY ADDRESS: 0000000000100000
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000003fb
  1GB PAGES: 0x0000000000000002
libxl: error: libxl_device.c:875:device_backend_callback: unable to connect
device with path /local/domain/0/backend/vbd/34/769
libxl: error: libxl_create.c:951:domcreate_launch_dm: unable to add disk
libxl: error: libxl_dm.c:1269:libxl__destroy_device_model: could not find
device-model's pid for dom 34
libxl: error: libxl.c:1419:libxl__destroy_domid: libxl__destroy_device_model
failed for 34
libxl: error: libxl_device.c:875:device_backend_callback: unable to disconnect
device with path /local/domain/0/backend/vbd/34/769
libxl: error: libxl.c:1455:devices_destroy_cb: libxl__devices_destroy failed
for 34

My config file is:
# =====================================================================
# Example HVM guest configuration
# =====================================================================
# This is a fairly minimal example of what is required for an
# HVM guest. For a more complete guide see xl.cfg(5)

# This configures an HVM rather than PV guest
builder = "hvm"

# Guest name
name = "netbsd-hvm"

# 128-bit UUID for the domain as a hexadecimal number.
# Use "uuidgen" to generate one if required.
# The default behavior is to generate a new UUID each time the guest is
# started.

# Enable Microsoft Hyper-V compatibile paravirtualisation /
# enlightenment interfaces. Turning this on can improve Windows guest
# performance and is therefore recommended
#viridian = 1

# Initial memory allocation (MB)
memory = 4096

# Maximum memory (MB)
# If this is greater than `memory' then the slack will start ballooned
# (this assumes guest kernel support for ballooning)
#maxmem = 512

# Number of VCPUS
vcpus = 6

# Network devices
# A list of 'vifspec' entries as described in
# docs/misc/xl-network-configuration.markdown
vif = [ 'mac=90:e6:ba:6c:6f:d3,bridge=bridge0' ]

# Disk Devices
# A list of `diskspec' entries as described in
# docs/misc/xl-disk-configuration.txt
disk = [ 'phy:/dev/wd1d,hda1,w' ] # /dev/vg/guest-volume,raw,xvda,rw'

# Guest VGA console configuration, either SDL or VNC
#sdl = 1
vnc = 1

Any idea as to what could cause this?

With regards,

Home | Main Index | Thread Index | Old Index