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] Re: HVM not working with Debian

To: "xen-users@xxxxxxxxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: HVM not working with Debian
From: "Antoine Benkemoun" <antoine@xxxxxxxxxxxxx>
Date: Thu, 11 Sep 2008 16:55:29 +0200
Delivery-date: Thu, 11 Sep 2008 07:56:10 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type:references :x-google-sender-auth; bh=si7W9lBM4eNuaPHkTKEZZ6/GpeWzqaWsVtqwy76uIkI=; b=kzVgDVDiXib148MvqvqH4eaCsoM/CSiYTIpCPwWSQ8CYAL7aJJGjaZ600h6LkPMG04 tBD1rDZRGfz4Og7BIocBtpY7oaNVSgNh955O4Dvar74W1YsNpm8EH+xEP8W3hDhBjgzm V07d1d2/KKjEiE7y+3krDfHBJ970c+ymhZrxw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:references:x-google-sender-auth; b=rQpJrkgAq04IstwD3jcyhvONQ/nMOgHMpenDL9D0wZB8ETwQCc+uUSHM4UIyrcp3QG q3hER1ZtLKYz7ZFj6U2qVmUddPuU70FsiN3nipk545kwatS0cMbEcdM1tdhQdoxYP7l+ HIg11XBfXPM6VRcAtJojBsAqbztzFnZwAgj0o=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <fc1cbedb0809110735t5f32efc1i2b6a5a0701df528a@xxxxxxxxxxxxxx>
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>
References: <fc1cbedb0809110735t5f32efc1i2b6a5a0701df528a@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Found the solution myself :) Path to qemu was wrong on the second config. Dunno why the first one didn't work though...

Antoine

On Thu, Sep 11, 2008 at 4:35 PM, Antoine Benkemoun <antoine@xxxxxxxxxxxxx> wrote:
Hello,

I have installed Xen on a brand new Dell server. This install differs from the previous as I have used the apt packages. I have exactly followed this tutorial : http://www.howtoforge.com/debian_etch_xen_from_debian_repository . Also, the server is 64-bit.

PV domU's work perfectly but HVM domU's don't agree with that.

I have tried two configs, here is the first one :

-----------------------------------------------------------------------
kernel = "/usr/lib/xen-3.0.3-1/boot/hvmloader"
builder = "hvm"
memory = "512"
disk = [ 'file:/data/xen/domains/asape/disk.img,hda,w', 'file:/data/win2000.img,hdc:cdrom,r' ]
device_model = '/usr/lib/xen-3.0.3-1/bin/qemu-dm'
name = "asape2"
vif = [ 'type=ioemu, bridge=xenbr0' ]
vnc=1
vnclisten="192.168.0.1"
boot="dca"
> > >-----------------------------------------------------------------------

And here is the second one :

-----------------------------------------------------------------------
#  -*- mode: python; -*- arch = os.uname()[4]
arch_libdir = 'lib64'
#----------------------------------------------------------------
# hvmloader in place of a kernel image
kernel = "/usr/lib/xen-3.0.3-1/boot/hvmloader"
# guest domain build function (for HVM guests we use 'hvm')
builder='hvm'
device_model = '/usr/' + arch_libdir + '/usr/lib/xen-3.0.3-1/bin/qemu-dm'
# memory allocation at boot in MB
memory = 512
# shadow pagetable memory,
#should be at least 2KB per MB of memory plus a few MB per vcpu
shadow_memory = 8
name = "asape"
# name for the domain
# number of CPUs guest has available (default=1)
vcpus=1
# HVM guest PAE support (default=0 disabled)
#pae=0
# HVM guest ACPI support (default=0 disabled)
#acpi=0
# HVM guest APIC support (default=0 disabled)
#apic=0
#----------------------------------------------------------------
# 1 NIC, auto-assigned MAC address
vif = [ 'type=ioemu, bridge=xenbr0' ]
# first device is LVM partition to use as hard disk,
# second device is an image of an installation CD-ROM
disk = ['phy:/data/xen/domains/asape/disk.img,hda,w', 'file:/data/win2000.img,hdc:cdrom,r']
# boot order (a=floppy, c=hard disk, d=CD-ROM; default=cda)
boot="dc"
# function to execute when guest wishes to power off
># function to execute when guest wishes to reboot
on_reboot   = 'restart'
# function to execute if guest crashes
on_crash    = 'restart'
#----------------------------------------------------------------
# SDL library support for graphics (default=0 disabled)
# VNC library support for graphics (default=0 disabled)
vnc=1
#------------------------VNC-------------------------------------
# address for VNC server to listen on,
# (default is to use the 'vnc-listen'
# setting in /etc/xen/xend-config.sxp)
#vnclisten="10.0.0.20"
# set the VNC display number (default=domid)
#vncdisplay=1
# find an unused port for the VNC server (default=1 enabled)
vncunused=1
# spawn vncviewer for domain's console (default=0 disabled)
vncconsole=1
#------------------------VGA-------------------------------------
# no graphics, only serial (do not enable for Windows guests)
#nographic=0
# stdvga (cirrus logic model, default=0 disabled)
stdvga=0
# start in full screen (default=0 no)
#full-screen=1
#------------------------USB-------------------------------------
# USB support
#(devices may be specified through the monitor window)
#usb=1
# normal/relative mouse
#usbdevice='mouse'
# tablet/absolute mouse
#usbdevice='tablet'
#------------------------MISC------------------------------------
# serial port re-direct to pty device,
# allows xm console or minicom to connect
#serial='pty'
# sound card support (sb16, es1370, all; default none)
#soundhw='sb16'
# set real time clock to local time (default=0 UTC)
localtime=1
 -----------------------------------------------------------------------

What happens is that I start these vm's using xm create which doesn't give my any error. Yet, I cannot connect via VNC and the VM's don't seem started because no CPU time is used.

Does anyone have a tip on how to solve this ?

Thank you in advance,

--
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35



--
Antoine Benkemoun
Tel : 03.51.53.57.00
Port : 06.32.88.59.35
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>