xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: HyoCheol Kim <hchkim@gmail.com>
To: xen-devel@lists.xen.org
Subject: libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) when creating VM using upstream qemu on Xen 4.2.
Date: Wed, 14 Nov 2012 10:45:29 +0900	[thread overview]
Message-ID: <CAB8QuJ6-XMAGCU87MRsBQcm32PaUWEVX4GBTV2JYGz4-s3Hb4A@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2051 bytes --]

Hello,

I've tested Xen 4.2 on CentOS 6.3(x86_x64)
My goal is to connect to Windows VM on Xen 4.2 using SPICE client.

Installation of Xen 4.2 was successful.
Also creating Windows VM using qemu-dm and connecting to it using VNC are
OK.
But qemu-dm can't support SPICE, so I installed upstream qemu. (
http://wiki.xen.org/wiki/QEMU_Upstream)
I also installed spice-server and spice-protocol as newest version.
Configuration and installation seems like successful. But not work with
error message above.

=========================================================================================
[root@localhost xen]# xl -f create Windows2003.cfg
Parsing config from Windows2003.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019bae4
  TOTAL:         0000000000000000->000000003c000000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000001df
  1GB PAGES: 0x0000000000000000
libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device
model: spawn failed (rc=-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error: No
such file or directory
Daemon running with PID 3912
=========================================================================================

My Windows2003.cfg file is above.

builder = "hvm"
name = "Windows2003"
memory = 1024

on_poweroff="destroy"
on_reboot="restart"
on_crash="destroy"

vcpus = 2
disk = [ '/dev/VolGroup/lv_home,,hda',
'/usr/src/Windows2003.iso,,hdc,cdrom' ]

# using qemu-dm is success to work.
#device_model='qemu-dm'
device_model_version='qemu-xen'
device_model_override='/usr/src/qemu/i386-softmmu/qemu-system-i386'
#device_model_override='/usr/src/qemu/x86_64-softmmu/qemu-system-x86_64'

boot="dc"
acpi=1
xen_platform_pci=1
xiridian=1
stdvga=1

#sdl = 1
vnc =0
vncconsole=0
vncpasswd=''
vncunused=1
vnclisten='0.0.0.0'
vncdisplay=3

spice=1
spicehost='0.0.0.0'
spiceport=6000
spicedisable_ticketing=1
spicepasswd = 'password'


Thanks in advance.

Daniel.

[-- Attachment #1.2: Type: text/html, Size: 3157 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

             reply	other threads:[~2012-11-14  1:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-14  1:45 HyoCheol Kim [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-11-14 14:47 libxl: error: libxl_dm.c:1212:device_model_spawn_outcome: domain 1 device model: spawn failed (rc=-3) when creating VM using upstream qemu on Xen 4.2 Fabio Fantoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAB8QuJ6-XMAGCU87MRsBQcm32PaUWEVX4GBTV2JYGz4-s3Hb4A@mail.gmail.com \
    --to=hchkim@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).