From: "Lynn Bendixsen" <lbendixs@novell.com>
To: Daniel Stekloff <dsteklof@us.ibm.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xm-test fails to pass sanity checks in hvm mode
Date: Tue, 11 Apr 2006 14:21:30 -0600 [thread overview]
Message-ID: <443BBB08.30F0.00FC.0@novell.com> (raw)
In-Reply-To: <1144779720.9203.6.camel@w-stekloff.beaverton.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]
>> I am attempting to run xm- test in hvm mode. I built successfully and then
> started runtests.sh. After about 30 seconds an error message appeared "Timed
> out connecting to console" or similar. I then used xmexample.hvm to manually
> try and start disk.img fully virtualized and the following was the last few
> lines on the VMs terminal:
>>
>> VFS: Cannot open root device "0301" or unknown- block(3,1)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(3,1)
>> Has anyone else seen this issue? Did I do something wrong?
>> I built on SLES 10 beta 9 using that kernel for -- with- hvm- kernel.
>
> Hi,
>
> I just built the latest tip and was able to run the disk.img manually. I
> was also able to run the _sanity tests from xm- test - all in hvm mode.
>
> Questions:
> 1) Could you provide your config file - xmexample.hvm - that you're
> using?
> 2) Is the SLES10 beta 9 kernel a non- Xen kernel?
> 3) Can you boot a non- xm- test disk image fully virtualized?
>
> Thanks,
> Dan
>
Hi Dan,
Answers:
1) attached - All I changed from my original file was the "file=" line and possibly the memory.
2) yes
3) yes
TIA, :)
Lynn
[-- Attachment #2: xmexample.hvm --]
[-- Type: application/octet-stream, Size: 5606 bytes --]
# -*- 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.
memory = 128
# A name for your domain. All domains must have different names.
name = "ExampleHVMDomain"
#-----------------------------------------------------------------------------
# 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:hda1,hda1,r' ]
disk = [ 'file:/tests/xm-test/ramdisk/disk.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=
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
#boot=[a|c|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=0
#----------------------------------------------------------------------------
# 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
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2006-04-11 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4432C3CA.30F0.00FC.0@novell.com>
[not found] ` <4433BACA.30F0.00FC.0@novell.com>
[not found] ` <443A88B5.65A5.00FC.0@novell.com>
2006-04-11 17:06 ` Xm-test fails to pass sanity checks in hvm mode Lynn Bendixsen
2006-04-11 18:21 ` Daniel Stekloff
2006-04-11 20:21 ` Lynn Bendixsen [this message]
2006-04-11 21:44 ` Daniel Stekloff
2006-04-11 21:59 Li, Xin B
2006-04-11 22:29 ` Daniel Stekloff
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 22:32 Li, Xin B
2006-04-11 22:36 ` Daniel Stekloff
2006-04-11 22:38 Li, Xin B
2006-04-11 22:59 ` Daniel Stekloff
2006-04-12 0:32 Li, Xin B
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=443BBB08.30F0.00FC.0@novell.com \
--to=lbendixs@novell.com \
--cc=dsteklof@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.