Probems installiing windows under xen in FC6
by Ian Brown
Hello,
I am trying desperately to install windows under xen in FC6 on x86_64;
my processor has virtulaization extensions (as can be seen from flags of
/proc/cpuinfo).
The kernel I have is the one from the FC6 DVD, 2.6.18-1.2798.fc6xen.
I had prepared a configuration file , windows.hvm, which is
given fully in the end of this message.
When I ran :
xm create windows.hvm , there is some window on the screen for a second then
it is closed.
On the console I see
xm create windows.hvm
Using config file "/etc/xen/windows.hvm".
Started domain ExampleHVMDomain
and that's it.
I am not sure about this line :
disk = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]
I am not sure about something: I do indeed have a sata disk; which is sda;
but when using qemu, should it also be sda?
I see in the kernel log the following:
rh kernel: device tap0 entered promiscuous mode
rh kernel: audit(1163952063.221:41): dev=tap0 prom=256 old_prom=0
auid=4294967295
rh kernel: xenbr0: port 3(tap0) entering learning state
rh kernel: xenbr0: topology change detected, propagating
rh kernel: xenbr0: port 3(tap0) entering forwarding state
rh kernel: device vif10.0 entered promiscuous mode
rh kernel: audit(1163952063.589:42): dev=vif10.0 prom=256 old_prom=0
auid=4294967295
rh kernel: ADDRCONF(NETDEV_UP): vif10.0: link is not ready
rh kernel: xenbr0: port 4(vif10.0) entering disabled state
rh kernel: device vif10.0 left promiscuous mode
rh kernel: audit(1163952064.309:43): dev=vif10.0 prom=0 old_prom=256
auid=4294967295
rh kernel: xenbr0: port 4(vif10.0) entering disabled state
rh kernel: xenbr0: port 3(tap0) entering disabled state
rh kernel: device tap0 left promiscuous mode
rh kernel: audit(1163952064.469:44): dev=tap0 prom=0 old_prom=256
auid=4294967295
rh kernel: xenbr0: port 3(tap0) entering disabled state
and this is windows.hvm:
# -*- mode: python; -*-
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
memory = 384
# 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 = "ExampleHVMDomain"
# 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
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
vif = [ 'type=ioemu, mac=00:16:3e:00:00:11, 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 = [ 'file:/var/lib/xen/windisk.img,ioemu:sda,w' ]
cdrom='/dev/hdb'
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
#on_reboot = 'destroy'
#on_crash = 'destroy'
ne2000=0
#============================================================================
# New stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
#boot from cdrom
boot="d"
sdl=1
vnc=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'
#-----------------------------------------------------------------------------
# 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'
any ideas what can cause the problem?
Regards,
Ian
17 years, 5 months
FC6 w updates: xenguest-install.py hangs on Dell poweredge
by Paul Wouters
I again have the problem that the installer hangs while installing a
xenu. The symptoms are that the last you see is the
"Starting install process. This may take several minutes..."
I can still send a shutdown over the xm command. "xm top" shows no CPU
usage whatsoever. I gave it a GB of ram and it reports only using 25%.
It's a stock install, with all options unselected, "customize" picked,
and all options again unselected, using the default partition scheme on a
4GB diskfile. With selinux disabled on the dom0.
The hardware is a Dell poweredge (I believe an 850), with a single P4,
4GB of ram and SATA disks.
The dom0 is a i386 image install of FC6 with all updates.
Paul
17 years, 5 months
RE: [Fedora-xen] keyboard/mouse problems during win2k3 installation
by Ranganathan, Shobha
I have had keyboard/mouse problems after the install in the FC5 guest
install in x86 mode for both host/guest.
It was an Apple Intel machine and I could not find a workaround. I then
installed it with no graphics on boot up. But I had several other
problems like VNC issues plaguing me...
I do not have a workaround. I only share the same set of problems at a
different time.
Regards
Shobha Ranganathan
"The significant challenges we face cannot be resolved at the same level
of thinking we were at when we created them." Albert Einstein
-----Original Message-----
From: fedora-xen-bounces(a)redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Peter Spuhler
Sent: Saturday, November 18, 2006 2:04 PM
To: fedora-xen(a)redhat.com
Subject: [Fedora-xen] keyboard/mouse problems during win2k3 installation
I am able to install windows 2003 64-bit on FC6 64-bit Dell Precision
490 until the win2k3 installer gets to asking about name/org and product
id, then the keyboard and mouse stops working alltogether in the virtual
machine. I've tried virt-install, virt-manger and modified example.hvm
file. I've also played with using vnc or sdl and turning on/off usb
without success. Has anyone else encountered this problem and found a
workaround?
# -*- 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 = 512
# 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 = 32
# A name for your domain. All domains must have different names.
name = "win2k3"
# 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=0 (disabled)
pae=1
# enable/disable HVM guest ACPI, default=0 (disabled)
acpi=1
# enable/disable HVM guest APIC, default=0 (disabled)
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' ]
#-----------------------------------------------------------------------
-----
# 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/sda3,ioemu:hda,w','file:/root/WINDOWS_2003.iso,hdc:cdrom,r' ]
#disk = [ 'file:/var/images/min-el3-i386.img,hda,w', ',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 = 'destroy'
on_crash = 'destroy'
#=======================================================================
=====
# New stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------
------
# Disk image for
cdrom = '/root/WINDOWS_2003.iso'
#cdrom = '/dev/cdrom'
#-----------------------------------------------------------------------
------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot='c'
#-----------------------------------------------------------------------
------
# 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
vncviewer=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=1
#-----------------------------------------------------------------------
-----
# enable spawning vncviewer for domain's console
# (only valid when vnc=1), default = 0
#vncconsole=0
#-----------------------------------------------------------------------
-----
# no graphics, use serial port
#nographic=0
#-----------------------------------------------------------------------
-----
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=1
#-----------------------------------------------------------------------
------
# 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=0
# 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'
#-----------------------------------------------------------------------
------
# enable ne2000, default = 0 (use pcnet)
ne2000=1
--
Fedora-xen mailing list
Fedora-xen(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
17 years, 5 months
Re: [Fedora-xen] Probems installiing windows under xen in FC6
by Robert Thiem
Ian Brown wrote:
> I am trying desperately to install windows under xen in FC6 on x86_64;
...
> When I ran :
> xm create windows.hvm , there is some window on the screen for a second
> then it is closed.
>
> On the console I see
> xm create windows.hvm
> Using config file "/etc/xen/windows.hvm".
> Started domain ExampleHVMDomain
> and that's it.
I'm just starting to look at getting a HVM running myself (that's an "I'm
not an expert disclaimer" :> )
I didn't think that "xm create" would say anything beyond that.
If you do a "xm list" does it show up the HVM domain? Maybe it's just
sitting around running in the background waiting for a VNC connection or
somesuch.
Regards,
Robert
17 years, 5 months
xenguest-install and vif-nat
by Tomáš Kouba
Hi,
is it possible to use xenguest-install script to build up a guest if I use
NAT-ed configuration for guests?
I don't see any option like this and the network is always bridged.
--
Tomas Kouba
17 years, 5 months
DomU network doesn't start automatically
by Robin Bowes
Hi,
I'm running 2.6.17-1.2187_FC5xen0 as my host and 2.6.18-1.2200.fc5xenU
in the guest.
I'm finding that the network doesn't start when I start the guest.
If I login (through the console) and manually start it, it works fine. e.g.:
service network start
Any idea what might cause this and how to fix it?
R.
17 years, 5 months
Block device sharing
by Bertho Stultiens
Hi,
I am trying to share a GFS2 partition across multiple xen boxes to share
f.x. the /home dir (using FC6). According to the Xen 3.0 documentation
at chapter 6.1, I should be using either NFS or a clusterFS. I do not
want to use a networkFS, so GFS seems to be the sane choice. The setup:
SAN -> /dev/sdX -> [c]LVM -> vgxen -> lvbox{00-99}
-> lvswap{00-99}
-> lvhome
Each VM has mounted a unique rootfs from lvboxX and swap from lvswapX
partition and share lvhome using GFS. The SAN has a multipath FC
connection to 8 blades and the VMs run distributed over the blades.
The problem, however, is that xen does not allow me to export
blockdevices that are in use. I've tried to export the PV (/dev/sdX) and
the LV (/dev/vgxen/lvhome), but both cases fail with an error (Device
/dev/sdX is mounted in a guest domain, and so cannot be mounted now.)
Any VM started after the first fails.
Is there a way to force xen to export the same blockdevice (either the
PV or preferably the LV)?
--
Greetings Bertho
Bertho Stultiens
Senior Systems Manager
Mobilethink A/S
17 years, 5 months
keyboard/mouse problems during win2k3 installation
by Spuhler, Peter
I am able to install windows 2003 64-bit on FC6 64-bit Dell Precision
490 until the win2k3 installer gets to asking about name/org and product
id, then the keyboard and mouse stops working alltogether in the virtual
machine. I've tried virt-install, virt-manger and modified example.hvm
file. I've also played with using vnc or sdl and turning on/off usb
without success. Has anyone else encountered this problem and found a
workaround?
# -*- 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 = 512
# 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 = 32
# A name for your domain. All domains must have different names.
name = "win2k3"
# 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=0 (disabled)
pae=1
# enable/disable HVM guest ACPI, default=0 (disabled)
acpi=1
# enable/disable HVM guest APIC, default=0 (disabled)
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' ]
#----------------------------------------------------------------------------
# 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/sda3,ioemu:hda,w','file:/root/WINDOWS_2003.iso,hdc:cdrom,r' ]
#disk = [ 'file:/var/images/min-el3-i386.img,hda,w', ',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 = 'destroy'
on_crash = 'destroy'
#============================================================================
# New stuff
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
#-----------------------------------------------------------------------------
# Disk image for
cdrom = '/root/WINDOWS_2003.iso'
#cdrom = '/dev/cdrom'
#-----------------------------------------------------------------------------
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot='c'
#-----------------------------------------------------------------------------
# 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
vncviewer=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=1
#----------------------------------------------------------------------------
# enable spawning vncviewer for domain's console
# (only valid when vnc=1), default = 0
#vncconsole=0
#----------------------------------------------------------------------------
# no graphics, use serial port
#nographic=0
#----------------------------------------------------------------------------
# enable stdvga, default = 0 (use cirrus logic device model)
stdvga=1
#-----------------------------------------------------------------------------
# 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=0
# 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'
#-----------------------------------------------------------------------------
# enable ne2000, default = 0 (use pcnet)
ne2000=1
17 years, 5 months
help installing ubuntu server guest
by George Hill
When I install ubuntu server as a fully-virtualized guest the install always hangs at exactly the same place. After it installs a bunch of packages, it hangs when it tries to install zliblg...
I am running Xen/FC6 on a AMD chip.
I have tried the following, but it always hangs at the same place
I have tried both the 32-bit and 64-bit iso files
I have run md5sum on both files
I have had the installer check the iso files
I have increased the alloted disk space (10GB) and RAM (1.2GB)
When I try to do a non-graphical install with xenguest-install I get this message:
Domain installation does not appear to have been
successful. If it was, you can restart your domain
by running 'xm create -c ub.serv1'; otherwise, please
restart your installation.
As an aside, I have no problem installing fully-virtualized ubuntu desktop and FC6.
Any thoughts or suggestions would be appreciated.
17 years, 5 months
