Evan Lavelle wrote:
If you're planning on any HVM DomUs, then you should go for AMD. The
real-mode issues are apparently fixed in Xen 3.2, but I haven't yet seen
any Intel success stories for 3.2 for the affected OSes (Solaris 10 and
openSUSE 10, at least). You'll also need to roll-your-own Xen for 3.2.
Hello,
I have an Intel Core 2 Quad (Q6600) system with vmx support enabled.
I've downloaded, compiled, and installed Xen 3.2.0 (and made sure to
compile hvmloader and get it installed). dom0 system is running Debian
Etch 4.0r3, and the Xen 2.6.18.8 kernel.
Yesterday I was trying to create a Xen HVM for the purposes of
installing a Debian Etch system (I've got several Debian Etch PVMs which
work fine, but I wanted to set up an HVM for some other experimenting).
After reading through several mailing list posts, web sites, FAQs,
etc. I was unable to actually perform an install. As soon as I try to
create the HVM, and connect to it via VNC, I always tend to get a
black/blank screen, and can never get it to change.
After some playing (I believe with the attempts to get information
available on the "serial port" so I could access it through xm console
(is this a correct assumption?)), I've never been able to see it display
anything, but sometimes I get what appears to be SOMETHING to spit out--
the cursor moves over several spaces, but no viewable characters are
actually printed. I wonder if I've got a kernel option set the wrong way
for this particular feature?
This morning I see the post regarding intel or amd, so at the very
least I'd like to seek some clarification on whether or not my
particular failures in getting a working Xen HVM up and running are due
to these real-mode issues (or if it is just some obvious detail I am
missing).
Again, all I'm after is to be able to install Debian off the pointed
to netinst ISO image, and get a system up and running. My previous
experience with Xen HVMs was in relation to setting up a WindowsXP HVM
back on Xen 3.0.3 (of which I referenced that config file in coming up
with my new one on this Xen 3.2 setup).
Attached are my Xen dom0 kernel .config and Xen HVM config file. If
anyone could point me in the right direction that would be fabulous.
Thanks.
-Matthew
--
Matthew Haas
Visiting Instructor
Corning Community College
Computer & Information Science
http://lab46.corning-cc.edu/haas/home/
"Writing should be like breathing;
It is one of those important things we do." -- me
config.gz
Description: GNU Zip compressed data
##########################################################################
# Xen HVM configuration file
##########################################################################
#################################################
# Kernel + memory size
#
kernel = '/usr/lib/xen/boot/hvmloader'
builder = 'hvm'
memory = 128
name = 'hvm1'
vcpus = 1
device_model = '/usr/lib/xen/bin/qemu-dm'
#################################################
# Disk device(s).
#
boot = 'dc'
disk = [ 'file:/xen/images/hvm1.disk,ioemu:hda,w',
'file:/xen/images/netinst.iso,ioemu:hdc:cdrom,r' ]
#################################################
# Networking
#
vif = [ 'type=ioemu, mac=00:16:3e:01:23:45, model=ne2k_pci' ]
#################################################
# HVM bits
#
pae = 0 # match host machine's PAE settings
apic = 1 # From reading, said it probably works
acpi = 0 # I read it might not be working
serial = 'pty'
sdl = 0
vnc = 1 # primary means of getting a console
vncconsole = 1
vncviewer = 1
vncdisplay = 0
vncunused = 1
vnclisten = '0.0.0.0'
nographic = 0
stdvga = 0
localtime = 1
#################################################
# Behavior
#
on_boot = 'restart'
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home