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

RE: [Xen-users] Error: Not an HVM capable platform, we stop creating!


  • To: "Luke" <secureboot@xxxxxxxxx>, <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "You, Yongkang" <yongkang.you@xxxxxxxxx>
  • Date: Wed, 10 May 2006 21:38:58 +0800
  • Delivery-date: Wed, 10 May 2006 06:39:46 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcZzrqFvzDXtglduQTqSKs30m8X2xAAiEP8A
  • Thread-topic: [Xen-users] Error: Not an HVM capable platform, we stop creating!

Hi Luke,

Could you please double check if your BIOS enabled VT option and use "xm dmesg" 
to see if there is "VMXON" string when Xen boots. :)

Best Regards,
Yongkang (Kangkang) 永康
>-----Original Message-----
>From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Luke
>Sent: 2006年5月10日 5:21
>To: xen-users@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-users] Error: Not an HVM capable platform, we stop creating!
>
>I'm getting this error:
>Error: Not an HVM capable platform, we stop creating!
>
>when trying to start an unmodified guest domain.
>
>This is after getting the latest xen-unstable, running make install, and
>booting into the domain.  I've verified that xend is running.  I'm using
> Ubuntu Beta 2.
>
>When I try to create an HVM domain.  I see that hvmloader is in the
>correct place.
>
>cat /proc/cpuinfo shows vmx as an extension.  This is a Dell 380n
>machine, with the latest BIOS (should work, with VT-X).
>
>Any ideas on where to start?
>
>Nothing written in either /var/log/xend.log or /var/log/xend-debug.log
>about it either.
>
>
>Thanks -
>
>
>
>I'm using this config:
>#  -*- mode: python; -*-
>#==========================================================
>==================
># Python configuration setup for 'xm create'.
># This script sets the parameters used when a domain is created using
>'xm create'.
># You use a separate script for each domain you want to create, or
># you can set the parameters for the domain on the xm command line.
>#==========================================================
>==================
>
>import os, re
>arch = os.uname()[4]
>if re.search('64', arch):
>    arch_libdir = 'lib64'
>else:
>    arch_libdir = 'lib'
>
>#----------------------------------------------------------------------------
># Kernel image file.
>kernel = "/usr/lib/xen/boot/hvmloader"
>
># The domain build function. HVM domain uses 'hvm'.
>builder='hvm'
>
># Initial memory allocation (in megabytes) for the new domain.
>#
># WARNING: Creating a domain with insufficient memory may cause out of
>#          memory errors. The domain needs enough memory to boot kernel
>#          and modules. Allocating less than 32MBs is not recommended.
>memory = 128
>
># A name for your domain. All domains must have different names.
>name = "ubuntuvmx"
>
>#-----------------------------------------------------------------------------
># the number of cpus guest platform has, default=1
>#vcpus=1
>
># enable/disable HVM guest PAE, default=0 (disabled)
>#pae=0
>
># enable/disable HVM guest ACPI, default=0 (disabled)
>#acpi=0
>
># enable/disable HVM guest APIC, default=0 (disabled)
>#apic=0
>
># List of which CPUS this domain is allowed to use, default Xen picks
>#cpus = ""         # leave to Xen to pick
>#cpus = "0"        # all vcpus run on CPU0
>#cpus = "0-3,5,^1" # run on cpus 0,2,3,5
>
># Optionally define mac and/or bridge for the network interfaces.
># Random MACs are assigned if not given.
>#vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, bridge=xenbr0' ]
># type=ioemu specify the NIC is an ioemu device not netfront
>vif = [ 'type=ioemu, bridge=xenbr0' ]
>#----------------------------------------------------------------------------
># Define the disk devices you want the domain to have access to, and
># what you want them accessible as.
># Each disk entry is of the form phy:UNAME,DEV,MODE
># where UNAME is the device, DEV is the device name the domain will see,
># and MODE is r for read-only, w for read-write.
>
>disk = [ 'phy:sda5,hda1,w' ]
>#disk = [ 'file:/var/images/min-el3-i386.img,ioemu:hda,w' ]
>
>#----------------------------------------------------------------------------
># Configure the behaviour when a domain exits.  There are three 'reasons'
># for a domain to stop: poweroff, reboot, and crash.  For each of these you
># may specify:
>#
>#   "destroy",        meaning that the domain is cleaned up as normal;
>#   "restart",        meaning that a new domain is started in place of
>the old
>#                     one;
>#   "preserve",       meaning that no clean-up is done until the domain is
>#                     manually destroyed (using xm destroy, for example);
>or
>#   "rename-restart", meaning that the old domain is not cleaned up, but is
>#                     renamed and a new domain started in its place.
>#
># The default is
>#
>#   on_poweroff = 'destroy'
>#   on_reboot   = 'restart'
>#   on_crash    = 'restart'
>#
># For backwards compatibility we also support the deprecated option restart
>#
># restart = 'onreboot' means on_poweroff = 'destroy'
>#                            on_reboot   = 'restart'
>#                            on_crash    = 'destroy'
>#
># restart = 'always'   means on_poweroff = 'restart'
>#                            on_reboot   = 'restart'
>#                            on_crash    = 'restart'
>#
># restart = 'never'    means on_poweroff = 'destroy'
>#                            on_reboot   = 'destroy'
>#                            on_crash    = 'destroy'
>
>#on_poweroff = 'destroy'
>#on_reboot   = 'restart'
>#on_crash    = 'restart'
>
>#==========================================================
>==================
>
># New stuff
>device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
>
>#-----------------------------------------------------------------------------
># Disk image for
>cdrom='/home/user/ubuntu-6.06-beta2-live-i386.iso'
>
>#-----------------------------------------------------------------------------
># boot on floppy (a), hard disk (c) or CD-ROM (d)
>boot='d'
>#-----------------------------------------------------------------------------
>#  write to temporary files instead of disk image files
>#snapshot=1
>
>#----------------------------------------------------------------------------
># enable SDL library for graphics, default = 0
>sdl=0
>
>#----------------------------------------------------------------------------
># enable VNC library for graphics, default = 1
>vnc=1
>
>#----------------------------------------------------------------------------
># enable spawning vncviewer(only valid when vnc=1), default = 1
>vncviewer=1
>
>#----------------------------------------------------------------------------
># no graphics, use serial port
>#nographic=0
>
>#----------------------------------------------------------------------------
># enable stdvga, default = 0 (use cirrus logic device model)
>stdvga=0
>
>#-----------------------------------------------------------------------------
>#   serial port re-direct to pty deivce, /dev/pts/n
>#   then xm console or minicom can connect
>serial='pty'
>
>#----------------------------------------------------------------------------
># enable ne2000, default = 0(use pcnet)
>ne2000=0
>
>
>#-----------------------------------------------------------------------------
>#   enable audio support
>#audio=1
>
>
>#-----------------------------------------------------------------------------
>#    set the real time clock to local time [default=0 i.e. set to utc]
>#localtime=1
>
>
>#-----------------------------------------------------------------------------
>#    start in full screen
>#full-screen=1
>
>_______________________________________________
>Xen-users mailing list
>Xen-users@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-users

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.