WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Unable to start HVM guest on Xen-Unstable is this broken?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Unable to start HVM guest on Xen-Unstable is this broken?
From: Mark Hurenkamp <mark.hurenkamp@xxxxxxxxx>
Date: Wed, 3 Feb 2010 01:05:44 +0100
Delivery-date: Tue, 02 Feb 2010 16:06:22 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.12.2 (Linux/2.6.31.6mh10; KDE/4.3.2; x86_64; ; )
Hi,


I've recently moved my xen over from 3.4-testing to unstable, to try out 4.0, 
and although i got the basics working (pvm machines can boot fine), i can't 
seem to get hvm machines to work.

When i start an hvm i get the following messages on the terminal:
root@coruscant:~# xm create xp.hvm
Using config file "/etc/xen/xp.hvm".
Error: Domain 'xp' does not exist.

This is printed on the console:
(XEN) tmem: all pools frozen for all domains
(XEN) tmem: all pools thawed for all domains
(XEN) tmem: all pools frozen for all domains
(XEN) tmem: all pools thawed for all domains
(XEN) memory.c:131:d0 Could not allocate order=9 extent: id=2 memflags=0 (1 of 
3)

And in /var/log/xen/qemu-dm-xp i find the following messages:
domid: 2
qemu: the number of cpus is 1
/usr/lib/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'

Initially i thought there must be something wrong with removing/overwriting 
the old 3.4 install, however i tried installing from scratch on a Debian 
Squeeze system, using the latest xen-unstable mercurial repository, and it 
still does not seem to want to start.

When i try to execute qemu-dm from commandline, it also mentions the same 
error:
root@coruscant:~# /usr/lib/xen/bin/qemu-dm --vcpu_avail
/usr/lib/xen/bin/qemu-dm: invalid option -- '-vcpu_avail'

Can anyone shed some light on this? I'm in the dark here...
Is this hvm currently broken in xen-unstable? Surely there must be more people 
running a hvm domain on xen-unstable? Am i doing something wrong in installing 
Xen?


Regards,
Mark.


P.S.
My xp.hvm contains the following:
kernel = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = '1024'
device_model='/usr/lib/xen/bin/qemu-dm'
disk = [ 'phy:/dev/mirror/xp,hda,w' ]
name = 'xp'
vif = ['mac=aa:00:00:00:01:09, bridge=loc']
boot='c'
vnc=1
vncviewer=0
vncconsole=1
sdl=0
usb=1
usbdevice='tablet'
localtime=1
monitor=1

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>