I have installed SuSE 10.1 Xen and try to install Windows XP.
xm create myxm.hvm brings up three lines (only):
Using config file "myxm.hvm"
Started domain Windows_XP
/var/lib/xen/images/windisk.img was created with seek=8192k
myxm.hvm:
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
kernel = "/usr/lib/xen/boot/hvmloader"
builder=''hvm''
memory = 512
name = "Windows_XP"
vif = [ ''type=ioemu, bridge=xenbr0'' ]
disk = [ ''file:/var/lib/xen/images/windisk.img,ioemu:hda,w'' ]
on_poweroff = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
cdrom=''/dev/cdrom''
boot=''d''
sdl=1
vnc=0
vncviewer=0
stdvga=0
serial=''pty''
ne2000=0
the log file shows:
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/1/0
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/1/768
Jun 6 15:13:16 CS-Ronald-VT ifup: Service network not started and mode
''auto'' -> skipping
Jun 6 15:13:16 CS-Ronald-VT kernel: tun: Universal TUN/TAP device driver, 1.6
Jun 6 15:13:16 CS-Ronald-VT kernel: tun: (C) 1999-2004 Max Krasnyansky
<maxk@qualcomm.com>
Jun 6 15:13:16 CS-Ronald-VT kernel: device tun0 entered promiscuous mode
Jun 6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(tun0) entering disabled
state
Jun 6 15:13:16 CS-Ronald-VT kernel: device tun0 left promiscuous mode
Jun 6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(tun0) entering disabled
state
Jun 6 15:13:16 CS-Ronald-VT kernel: device vif1.0 entered promiscuous mode
Jun 6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering learning
state
Jun 6 15:13:16 CS-Ronald-VT kernel: xenbr0: topology change detected,
propagating
Jun 6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering forwarding
state
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing
backend/vbd/1/768/node /dev/loop0 to xenstore.
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing
backend/vbd/1/768/physical-device 7:0 to xenstore.
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing
backend/vbd/1/768/hotplug-status connected to xenstore.
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif1.0, bridge xenbr0.
Jun 6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/1/0/hotplug-status connected to xenstore.
Jun 6 15:13:17 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering disabled
state
Jun 6 15:13:17 CS-Ronald-VT kernel: device vif1.0 left promiscuous mode
Jun 6 15:13:17 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering disabled
state
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: offline
XENBUS_PATH=backend/vif/1/0
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/1/768
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: brctl delif
xenbr0 vif1.0 failed
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: ifconfig
vif1.0 down failed
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge offline for vif1.0, bridge xenbr0.
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/1/0
Jun 6 15:13:17 CS-Ronald-VT ifdown: vif1.0
Jun 6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/1/768
Jun 6 15:13:17 CS-Ronald-VT ifdown: Interface not available and no
configuration found.
What do I miss?
bye
Ronald
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi,> xm create myxm.hvm brings up three lines (only): > Using config file "myxm.hvm" > Started domain Windows_XPIn my case, after these three lines, a little window of Windows setup comes up... Seems like your computer itself doesn''t freeze? my hvm file is as below(Sorry it''s long, but I''m afraid of a miseditting) I see no difference with yours in the effective setting.... # -*- 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 = 384 # A name for your domain. All domains must have different names. name = "WindowsXP" #----------------------------------------------------------------------------- # 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:/var/lib/xen/images/windisk.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 = ''destroy'' # on_crash = ''destroy'' # # 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=''/dev/sr0'' #----------------------------------------------------------------------------- # boot on floppy (a), hard disk (c) or CD-ROM (d) boot=''d'' #----------------------------------------------------------------------------- # write to temporary files instead of disk image files #snapshot=1 #---------------------------------------------------------------------------- # enable SDL library for graphics, default = 0 sdl=1 #---------------------------------------------------------------------------- # enable VNC library for graphics, default = 1 vnc=0 #---------------------------------------------------------------------------- # enable spawning vncviewer(only valid when vnc=1), default = 1 vncviewer=0 #---------------------------------------------------------------------------- # 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I followed the instructions at http://mccune.ece.cmu.edu/wordpress/?page_id=145 and it worked fine. The caveat is that the memmap entry that they posted is not applicable to SUSE Linux. I removed that line and everything worked. Another caveat: The installation process does "reboot" a couple of times. The last time, I did get a Blue Screen. At that time, I changed the boot = ''d'' to boot = ''c'' and everything completed correctly. If you want to test ping connectivity, remember to disable the firewall within Windows XP. Hope this helps. Jose Betancourt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
CS - Ronald Wiplinger
2006-Jun-07 04:13 UTC
Re: [Xen-users] SuSE 10.1 and Windows XP guest
Noniko wrote:> Hi, > >> xm create myxm.hvm brings up three lines (only): >> Using config file "myxm.hvm" >> Started domain Windows_XP > > In my case, after these three lines, a little window of Windows setup > comes up... > Seems like your computer itself doesn''t freeze? > >I used now exactly your script and get this into my /var/log/messages. Can anybody tell me what I am doing wrong? Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/1/768 Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/1/0 Jun 7 12:03:59 CS-Ronald-VT ifup: Service network not started and mode ''auto'' -> skipping Jun 7 12:03:59 CS-Ronald-VT kernel: tun: Universal TUN/TAP device driver, 1.6 Jun 7 12:03:59 CS-Ronald-VT kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Jun 7 12:03:59 CS-Ronald-VT kernel: device tun0 entered promiscuous mode Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: port 1(tun0) entering disabled state Jun 7 12:03:59 CS-Ronald-VT kernel: device tun0 left promiscuous mode Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: port 1(tun0) entering disabled state Jun 7 12:03:59 CS-Ronald-VT kernel: device vif1.0 entered promiscuous mode Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering learning state Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: topology change detected, propagating Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering forwarding state Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif1.0, bridge xenbr0. Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/1/0/hotplug-status connected to xenstore. Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing backend/vbd/1/768/node /dev/loop0 to xenstore. Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing backend/vbd/1/768/physical-device 7:0 to xenstore. Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing backend/vbd/1/768/hotplug-status connected to xenstore. Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering disabled state Jun 7 12:03:59 CS-Ronald-VT kernel: device vif1.0 left promiscuous mode Jun 7 12:03:59 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering disabled state Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/1/0 Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/1/768 Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: brctl delif xenbr0 vif1.0 failed Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: ifconfig vif1.0 down failed Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif1.0, bridge xenbr0. Jun 7 12:03:59 CS-Ronald-VT logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/768 Jun 7 12:04:00 CS-Ronald-VT ifdown: vif1.0 Jun 7 12:04:00 CS-Ronald-VT logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/1/0 Jun 7 12:04:00 CS-Ronald-VT ifdown: Interface not available and no configuration found.> my hvm file is as below(Sorry it''s long, but I''m afraid of a miseditting) > I see no difference with yours in the effective setting.... > > # -*- 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 = 384 > > # A name for your domain. All domains must have different names. > name = "WindowsXP" > > #----------------------------------------------------------------------------- > > # 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:/var/lib/xen/images/windisk.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 = ''destroy'' > # on_crash = ''destroy'' > # > # 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=''/dev/sr0'' > > #----------------------------------------------------------------------------- > > # boot on floppy (a), hard disk (c) or CD-ROM (d) > boot=''d'' > #----------------------------------------------------------------------------- > > # write to temporary files instead of disk image files > #snapshot=1 > > #---------------------------------------------------------------------------- > > # enable SDL library for graphics, default = 0 > sdl=1 > > #---------------------------------------------------------------------------- > > # enable VNC library for graphics, default = 1 > vnc=0 > > #---------------------------------------------------------------------------- > > # enable spawning vncviewer(only valid when vnc=1), default = 1 > vncviewer=0 > > #---------------------------------------------------------------------------- > > # 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 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users