Hi,
Appologies for the delay, here is my 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]
#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/usr/lib/xen-default/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 = 256
# Shadow pagetable memory for the domain, in MB.
# Should be at least 2KB per MB of domain memory, plus a few MB per vcpu.
shadow_memory = 8
# A name for your domain. All domains must have different names.
name = "testserver"
# 128-bit UUID for the domain. The default behavior is to generate a new UUID
# on each call to 'xm create'.
#uuid = "06ed00fe-1162-4fc4-b5d8-11993ee4a8b9"
#-----------------------------------------------------------------------------
# The number of cpus guest platform has, default=1
vcpus=1
# Enable/disable HVM guest PAE, default=1 (enabled)
#pae=1
# Enable/disable HVM guest ACPI, default=1 (enabled)
#acpi=1
# Enable/disable HVM APIC mode, default=1 (enabled)
# Note that this option is ignored if vcpus > 1
#apic=1
# 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, model=ne2k_pci' ]
# type=ioemu specify the NIC is an ioemu device not netfront
#vif = [ 'type=ioemu, bridge=xenbr0' ]
#vif = ['']
vif = [ 'type=ioemu, bridge=eth0' ]
#----------------------------------------------------------------------------
# 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:/dev/XEN/testserver,ioemu:hda,w',
'file:/home/support/OES2-SP2a-i386-CD1.iso,hdc:cdrom,r' ]
#disk = [ 'phy:hda1,hda1,r' ]
#disk = [ 'file:/var/images/min-el3-i386.img,hda,w',
'file:/root/W03StdR2_SP2_d1.iso,hdc:cdrom,r' ]
#----------------------------------------------------------------------------
# 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/lib/xen-default/bin/qemu-dm'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"
#-----------------------------------------------------------------------------
# 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
#vfb = [ 'type=vnc,vnclisten=0.0.0.0,vncunused=1']
#----------------------------------------------------------------------------
# address that should be listened on for the VNC server if vnc is set.
# default is to use 'vnc-listen' setting from /etc/xen/xend-config.sxp
#vnclisten="127.0.0.1"
#----------------------------------------------------------------------------
# set VNC display number, default = domid
#vncdisplay=1
#----------------------------------------------------------------------------
# try to find an unused port for the VNC server, default = 1
#vncunused=0
#----------------------------------------------------------------------------
# enable spawning vncviewer for domain's console
# (only valid when vnc=1), default = 0
vncconsole=1
#----------------------------------------------------------------------------
# set password for domain's VNC console
# default is depents on vncpasswd in xend-config.sxp
vncpasswd=''
#----------------------------------------------------------------------------
# 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 sound card support, [sb16|es1370|all|..,..], default none
#soundhw='sb16'
#-----------------------------------------------------------------------------
# set the real time clock to local time [default=0 i.e. set to utc]
#localtime=1
#-----------------------------------------------------------------------------
# start in full screen
#full-screen=1
#-----------------------------------------------------------------------------
# Enable USB support (specific devices specified at runtime through the
# monitor window)
#usb=1
# Enable USB mouse support (only enable one of the following, `mouse' for
# PS/2 protocol relative mouse, `tablet' for
# absolute mouse)
#usbdevice='mouse'
usbdevice='tablet'
#-----------------------------------------------------------------------------
# Set keyboard layout, default is en-us keyboard.
#keymap='ja'
Many thanks
Ian
Tidyhosts UK - Server & Web Specialists
W: www.tidyhosts.com
E: enquiries@xxxxxxxxxxxxx
T: 0871 910 6732
This email and its attachments are scanned by TidyHosts UK. All emails and
attachments should also be scanned by the recipient. TidyHosts UK accept no
responsibility for any damage caused by any virus attached to this email. This
email is confidential and is intended only for the addressee(s).
From: Brent Alcorn [mailto:Brent.Alcorn@xxxxxxxxxxxx]
Sent: 23 December 2009 05:07
To: Ian Tobin
Cc: Fajar A. Nugraha; Nick Couchman; xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Netware
Yes I am. I am kind of new to Xen so I am not sure if there is a console
equivalent of the guest create gui.
Perhaps you could post your config file?
Regards,
Brent
>>> "Ian Tobin" <itobin@xxxxxxxxxxxxx> 12/22/2009 5:10 PM >>>
Hi
are you doing this via X windows? The problem is we don't have the GUI enabled
on the dom0 :(
Sent from my iPod
On 21 Dec 2009, at 18:58, "Brent Alcorn" <Brent.Alcorn@xxxxxxxxxxxx> wrote:
Hi Ian,
I am running the Netware version as a PV guest installed via the Virt-Manager
GUI.
I haven't tried it as a HVM so I can't help much with that.
Regards,
Brent
>>> "Ian Tobin" <itobin@xxxxxxxxxxxxx> 12/21/2009 6:26 AM >>>
Hi,
Ive got the ISO (OES2-SP2a-i386-CD1.iso)
How are you guys installing it? Ive created a HVM config file but as
soon as i do xm create the VNC window opens then immediately the domU
shuts down.
In the config file ive got the ISO mounted a cdrom
cheers
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Ian Tobin
Sent: 18 December 2009 18:08
To: Nick Couchman; Fajar A. Nugraha
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-users] Netware
Hi all,
Sorry for the delay.
Im using Debian Lenny with the Debian package for Dom0. Ive not tried
the suggested URLs as yet, i couldn't get into the office today because
of the snow.
I didn't realise you couldn't setup netware straight from the CD as you
can with Windows etc.
Ill be trying this out on Monday hopefully, though netware is now dated
it would be good to free up some physical boxes and build a fresh
netware box on DomU.
Cheers
Ian
-----Original Message-----
From: Nick Couchman [mailto:Nick.Couchman@xxxxxxxxx]
Sent: 18 December 2009 16:39
To: Fajar A. Nugraha; Ian Tobin
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Netware
>>> On 2009/12/18 at 06:28, "Fajar A. Nugraha" <fajar@xxxxxxxxx> wrote:
> On Thu, Dec 17, 2009 at 7:29 PM, Ian Tobin <itobin@xxxxxxxxxxxxx>
wrote:
>> H
>>
>> Is it possible to virtualise netware? I tried running an ISO for 6.5
but the
>> DomU shuts down immediately.
>
> I assume you're trying to install it as HVM domU?
>
> Googling "novell netware xen" found this
>
http://searchenterpriselinux.techtarget.com/news/article/0,289142,sid39_
gci1
> 275963,00.html
> http://en.wikipedia.org/wiki/Novell_NetWare
>
> so it should be possible to run it as PV guest. Novell guys should be
> able to help you more with this.
Ian,
What Linux distro are you using for dom0? Novell has built SLES10 and
SLES11 with specific support for NetWare. You should definitely be able
to get it to work with other dom0 distros and O/Ss, but you might start
there if this is a big concern for you.
-Nick
--------
This e-mail may contain confidential and privileged material for the
sole use of the intended recipient. If this email is not intended for
you, or you are not responsible for the delivery of this message to the
intended recipient, please note that this message may contain SEAKR
Engineering (SEAKR) Privileged/Proprietary Information. In such a case,
you are strictly prohibited from downloading, photocopying, distributing
or otherwise using this message, its contents or attachments in any way.
If you have received this message in error, please notify us immediately
by replying to this e-mail and delete the message from your mailbox.
Information contained in this message that does not relate to the
business of SEAKR is neither endorsed by nor attributable to SEAKR.
_______________________________________________
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
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home