I''ve posted at Centos forums also, but thought I''d post here to reach a broader audience... I''ve read many posts on this issue. I get the dreaded "Setup is starting" screen and cannot get past this. I''ll post my details in a minute, but here''s what I''ve tried: Hitting F5 and F6, though there is no prompt for either at the bottom of the blue screen Read and tried the www.xensource.com/files/xen_install_windows.pdf document Read and tried the https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf Tried with 1 vcpu, with/without pae, vnc, sdl and also from a physical dvd or an iso I''ve been at this for a few days. I have learned much, and there are many more documents to go through, but it seems to me people must be having success because I am not finding a lot of references to this problem. Here is output from ''xm info'' host : kaasdaheen.kiksadi.com release : 2.6.18-8.1.6.el5xen version : #1 SMP Thu Jun 14 18:01:24 EDT 2007 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2612 hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000011f total_memory : 4094 free_memory : 517 xen_major : 3 xen_minor : 0 xen_extra : .3-rc5-8.1.6.el xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-52) cc_compile_by : mockbuild cc_compile_domain : cc_compile_date : Thu Jun 14 17:21:20 EDT 2007 xend_config_format : 2 Then output from ''xm dmesg'' (XEN) (file=hvm.c, line=197) Allocated port 3 for hvm. (XEN) (file=hvm.c, line=197) Allocated port 4 for hvm. (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64729 (pseudophys a0): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64728 (pseudophys a1): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64727 (pseudophys a2): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64726 (pseudophys a3): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64725 (pseudophys a4): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64724 (pseudophys a5): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64723 (pseudophys a6): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64722 (pseudophys a7): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64721 (pseudophys a8): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64720 (pseudophys a9): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471f (pseudophys aa): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471e (pseudophys ab): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471d (pseudophys ac): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471c (pseudophys ad): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471b (pseudophys ae): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471a (pseudophys af): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64719 (pseudophys b0): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64718 (pseudophys b1): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64717 (pseudophys b2): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64716 (pseudophys b3): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64715 (pseudophys b4): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64714 (pseudophys b5): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64713 (pseudophys b6): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64712 (pseudophys b7): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64711 (pseudophys b8): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64710 (pseudophys b9): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470f (pseudophys ba): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470e (pseudophys bb): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470d (pseudophys bc): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470c (pseudophys bd): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470b (pseudophys be): count=2 type=0 (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470a (pseudophys bf): count=2 type=0 (XEN) (GUEST: 29) HVM Loader (XEN) (GUEST: 29) Detected Xen v3.0.3-rc5-8.1.6.el (XEN) (GUEST: 29) Writing SMBIOS tables ... (XEN) (GUEST: 29) Loading ROMBIOS ... (XEN) (GUEST: 29) Creating MP tables ... (XEN) (GUEST: 29) Loading Cirrus VGABIOS ... (XEN) (GUEST: 29) Loading ACPI ... (XEN) (GUEST: 29) SVM go ... (XEN) (GUEST: 29) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $ (XEN) (GUEST: 29) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $ (XEN) (GUEST: 29) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15:55:26 $ (XEN) (GUEST: 29) (XEN) (GUEST: 29) ata0-0: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 (XEN) (GUEST: 29) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10000 MBytes) (XEN) (GUEST: 29) ata0 slave: Unknown device (XEN) (GUEST: 29) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom (XEN) (GUEST: 29) ata1 slave: Unknown device (XEN) (GUEST: 29) (XEN) (GUEST: 29) Booting from CD-Rom... (XEN) (GUEST: 29) unsupported PCI BIOS function 0x0E (XEN) (GUEST: 29) int13_harddisk: function 15, unmapped device for ELDL=81 (XEN) (GUEST: 29) *** int 15h function AX=E980, BX=00F2 not yet supported! (XEN) (GUEST: 29) *** int 15h function AX=EC00, BX=0002 not yet supported! (XEN) Trying to set reserved bit in EFER: 4d01 Now my config from /etc/xen/winxp64 using virt-manager: # Automatically generated xen config file name = "winxp64" builder = "hvm" memory = "500" disk = [ ''file:/srv/xen/winxp64.img,hda,w'', ] vif = [ ''type=ioemu, mac=00:16:3e:1b:72:1e, bridge=xenbr0'', ] uuid = "6a8a9359-f8c2-cf91-f338-dc3e63177d8f" device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 vcpus=2 serial = "pty" # enable serial console on_reboot = ''restart'' on_crash = ''restart'' I have an AMD Athlon 5000+ X2 (made sure I got a processor supporting hardware virtualization specifically for this task) with plenty of ram and hd space. Currently, I have two other linux guests running with full virtualization. I would like to keep the native install from Centos 5 x86_64 (i.e. I don''t want to compile my own xen from source). The reason why I am doing this is so I can take my experiences to my workplace for possible deployment on multiple machines. Does anyone have an idea of what may be preventing me from running this Windows XP 64 system in a DOMu? I have also tried a 32 bit system with the same results. Thank you. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Bob,
I am not a Xen professional, but had no problems installing WinXP (SP2
integrated and 32bit) on a 64bit Gentoo machine. Here is my config-file:
<snip>
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 = "winxp"
vcpus=1
pae=1
acpi=1
apic=1
vif = [ ''type=ioemu, mac=00:16:3e:3a:d0:6f, bridge=xenbr0'' ]
disk = [ ''phy:/dev/vgrp0/winxp,hda,w'',
''phy:/dev/hda,hdc:cdrom,r'' ]
device_model = ''/usr/'' + arch_libdir +
''/xen/bin/qemu-dm''
# boot="d" # CDROM for installation
boot="c" # HD for finishing Setup and running WinXP
sdl=0
vnc=1
vnclisten="0.0.0.0"
vncpasswd=''XXXX''
stdvga=0
serial=''pty''
</snip>
Bob Gamble schrieb:> # Automatically generated xen config file
> name = "winxp64"
> builder = "hvm"
> memory = "500"
> disk = [ ''file:/srv/xen/winxp64.img,hda,w'', ]
Only one device?? Where are you installing to?? Try to make 2 devices
like this:
disk = [ ''file:/srv/xen/winxp64.img,hda,w'',
''phy:/dev/YOURCDROMDRIVE,hdc:cdrom,r'' ]
And you need to add the boot parameter I guess:
boot="d" # CDROM for installation
#boot="c" # HD for finishing Setup and running WinXP
First run it with "d" to install from your winxp-cd, after the first
reboot, kill the machine, set it to "c" and startup again, that worked
for me. I guess you could use boot="dc" but never tried that.
> vif = [ ''type=ioemu, mac=00:16:3e:1b:72:1e,
bridge=xenbr0'', ]
> uuid = "6a8a9359-f8c2-cf91-f338-dc3e63177d8f"
> device_model = "/usr/lib64/xen/bin/qemu-dm"
> kernel = "/usr/lib/xen/boot/hvmloader"
> vnc=1
> vncunused=1
> apic=1
> acpi=1
> pae=1
> vcpus=2
> serial = "pty" # enable serial console
> on_reboot = ''restart''
> on_crash = ''restart''
>
> I have an AMD Athlon 5000+ X2 (made sure I got a processor supporting
> hardware virtualization specifically for this task) with plenty of ram
> and hd space.
I have a X2 too, works like a charme, after some Bios-related problems
:-D Hope I could help!?
Greetz Holger
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> Does anyone have an idea of what may be preventing me from > running this Windows XP 64 system in a DOMu? I have also > tried a 32 bit system with the same results. Thank you.I don''t see why 32-bit XP shouldn''t work in this setup - I''m pretty certain that it should work. I can also with almost certainty say that 3.0.3 doesn''t support 64-bit XP version. You need 3.0.4 for that (I would recommend an upgrade to 3.1, as it has a bunch of other improvements too). -- Mats _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Jun 29, 2007 at 11:47:22AM +0200, Petersson, Mats wrote:> > Does anyone have an idea of what may be preventing me from > > running this Windows XP 64 system in a DOMu? I have also > > tried a 32 bit system with the same results. Thank you. > > I don''t see why 32-bit XP shouldn''t work in this setup - I''m pretty > certain that it should work. I can also with almost certainty say that > 3.0.3 doesn''t support 64-bit XP version. You need 3.0.4 for that (I > would recommend an upgrade to 3.1, as it has a bunch of other > improvements too).I had trouble with installing 32-bit WinXP on a Debian 64-bit AMD system until I installed 3.1. Since then it''s been smooth sailing. - Ana _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jim, Thanks much for your reply and to others that have replied as well. I''ve tried more with Centos 5''s version but never got any further. I did try what you said. But maybe you can give me a bit more info on your setup. Did you run rpm -U on the 3.1 rpm or remove the Centos xen rpm first? I removed the rpm, and it took a few other packages with it such as libvirt, virt-manager gnome-session, etc. That might have been fine, but I couldn''t get xen to run after doing the above. Then when trying to revert to the original setup, I couldn''t run virt-manager. So basically, what was your approach and are you now using xen from the command line to perform all your virtualization tasks? Thanks again. On 6/28/07, Jim Burnes <jvburnes@gmail.com> wrote:> > Bob, > > I''m running a configuration similar to yours. 2.4Ghz dual-core opteron /w > 4GB of main memory. We intend to install mass-parallel Windows XP for our > lab. > > I''ve had up to 8 Windows XP images running concurrently and I''m trying for > 12. > > I''m also running Centos 5. > > Some things you need to do: > > Download the Xen 3.1 RPMS from XenSource. The default Xen install on > Centos 5 is 3.0.3 which has a number of glitches. > Get a copy of WinFLP (Windows Fundamentals for Legacy Computers). Its > basicallly a stripped down version of XP. Check with all the usual sources. > > > When you''re replacing the default Xen install with the 3.1 RPMS from > XenSource you''ll notice that one of them has a conflict with a pre-installed > RPM called xen-libs or something. Remove that (with a --nodep if necessary) > and install the new one. > > Make sure that when you run your initial install of XP (whatever version) > that you specify your CD boot image in the disk = [] line as the cdrom> parameter is deprecated / removed and won''t work. It won''t even tell you > that it doesn''t understand cdrom=, it just wont work. That threw me for a > whole day. > > Do the usual F5/F6 thing. Make sure if you have a keyboard with a Fn key > lock its pressed during boot or *suprise* they won''t work. 8-) > > Good luck... > > Jim Burnes > > > On 6/28/07, Bob Gamble <kiksadiweb@gmail.com> wrote: > > > I''ve posted at Centos forums also, but thought I''d post here to reach a > > broader audience... > > > > I''ve read many posts on this issue. I get the dreaded "Setup is > > starting" screen and cannot get past this. I''ll post my details in a minute, > > but here''s what I''ve tried: > > > > Hitting F5 and F6, though there is no prompt for either at the bottom of > > the blue screen > > Read and tried the www.xensource.com/files/xen_install_windows.pdfdocument > > Read and tried the https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf > > > > Tried with 1 vcpu, with/without pae, vnc, sdl and also from a physical > > dvd or an iso > > > > I''ve been at this for a few days. I have learned much, and there are > > many more documents to go through, but it seems to me people must be having > > success because I am not finding a lot of references to this problem. Here > > is output from ''xm info'' > > > > host : kaasdaheen.kiksadi.com > > release : 2.6.18-8.1.6.el5xen > > version : #1 SMP Thu Jun 14 18:01:24 EDT 2007 > > machine : x86_64 > > nr_cpus : 2 > > nr_nodes : 1 > > sockets_per_node : 1 > > cores_per_socket : 2 > > threads_per_core : 1 > > cpu_mhz : 2612 > > hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000011f > > total_memory : 4094 > > free_memory : 517 > > xen_major : 3 > > xen_minor : 0 > > xen_extra : .3- rc5-8.1.6.el > > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 > > xen_pagesize : 4096 > > platform_params : virt_start=0xffff800000000000 > > xen_changeset : unavailable > > cc_compiler : gcc version 4.1.1 20070105 (Red Hat 4.1.1-52) > > cc_compile_by : mockbuild > > cc_compile_domain : > > cc_compile_date : Thu Jun 14 17:21:20 EDT 2007 > > xend_config_format : 2 > > > > Then output from ''xm dmesg'' > > > > (XEN) (file=hvm.c, line=197) Allocated port 3 for hvm. > > (XEN) (file=hvm.c, line=197) Allocated port 4 for hvm. > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64729 > > (pseudophys a0): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64728 > > (pseudophys a1): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64727 > > (pseudophys a2): count=2 type=0 > > (XEN) (file=memory.c , line=188) Dom29 freeing in-use page 64726 > > (pseudophys a3): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64725 > > (pseudophys a4): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64724 > > (pseudophys a5): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64723 > > (pseudophys a6): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64722 > > (pseudophys a7): count=2 type=0 > > (XEN) (file=memory.c , line=188) Dom29 freeing in-use page 64721 > > (pseudophys a8): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64720 > > (pseudophys a9): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471f > > (pseudophys aa): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471e > > (pseudophys ab): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471d > > (pseudophys ac): count=2 type=0 > > (XEN) (file=memory.c , line=188) Dom29 freeing in-use page 6471c > > (pseudophys ad): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471b > > (pseudophys ae): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6471a > > (pseudophys af): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64719 > > (pseudophys b0): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64718 > > (pseudophys b1): count=2 type=0 > > (XEN) (file=memory.c , line=188) Dom29 freeing in-use page 64717 > > (pseudophys b2): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64716 > > (pseudophys b3): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64715 > > (pseudophys b4): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64714 > > (pseudophys b5): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64713 > > (pseudophys b6): count=2 type=0 > > (XEN) (file=memory.c , line=188) Dom29 freeing in-use page 64712 > > (pseudophys b7): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64711 > > (pseudophys b8): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 64710 > > (pseudophys b9): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470f > > (pseudophys ba): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470e > > (pseudophys bb): count=2 type=0 > > (XEN) (file=memory.c , line=188) Dom29 freeing in-use page 6470d > > (pseudophys bc): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470c > > (pseudophys bd): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470b > > (pseudophys be): count=2 type=0 > > (XEN) (file=memory.c, line=188) Dom29 freeing in-use page 6470a > > (pseudophys bf): count=2 type=0 > > (XEN) (GUEST: 29) HVM Loader > > (XEN) (GUEST: 29) Detected Xen v3.0.3-rc5-8.1.6.el > > (XEN) (GUEST: 29) Writing SMBIOS tables ... > > (XEN) (GUEST: 29) Loading ROMBIOS ... > > (XEN) (GUEST: 29) Creating MP tables ... > > (XEN) (GUEST: 29) Loading Cirrus VGABIOS ... > > (XEN) (GUEST: 29) Loading ACPI ... > > (XEN) (GUEST: 29) SVM go ... > > (XEN) (GUEST: 29) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $ > > (XEN) (GUEST: 29) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 > > vruppert Exp $ > > (XEN) (GUEST: 29) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: > > 2005/05/07 15:55:26 $ > > (XEN) (GUEST: 29) > > (XEN) (GUEST: 29) ata0-0: PCHS=16383/16/63 translation=lba > > LCHS=1024/255/63 > > (XEN) (GUEST: 29) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (10000 > > MBytes) > > (XEN) (GUEST: 29) ata0 slave: Unknown device > > (XEN) (GUEST: 29) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom > > (XEN) (GUEST: 29) ata1 slave: Unknown device > > (XEN) (GUEST: 29) > > (XEN) (GUEST: 29) Booting from CD-Rom... > > (XEN) (GUEST: 29) unsupported PCI BIOS function 0x0E > > (XEN) (GUEST: 29) int13_harddisk: function 15, unmapped device for > > ELDL=81 > > (XEN) (GUEST: 29) *** int 15h function AX=E980, BX=00F2 not yet > > supported! > > (XEN) (GUEST: 29) *** int 15h function AX=EC00, BX=0002 not yet > > supported! > > (XEN) Trying to set reserved bit in EFER: 4d01 > > > > Now my config from /etc/xen/winxp64 using virt-manager: > > > > # Automatically generated xen config file > > name = "winxp64" > > builder = "hvm" > > memory = "500" > > disk = [ ''file:/srv/xen/winxp64.img,hda,w'', ] > > vif = [ ''type=ioemu, mac=00:16:3e:1b:72:1e, bridge=xenbr0'', ] > > uuid = "6a8a9359-f8c2-cf91-f338-dc3e63177d8f" > > device_model = "/usr/lib64/xen/bin/qemu-dm" > > kernel = "/usr/lib/xen/boot/hvmloader" > > vnc=1 > > vncunused=1 > > apic=1 > > acpi=1 > > pae=1 > > vcpus=2 > > serial = "pty" # enable serial console > > on_reboot = ''restart'' > > on_crash = ''restart'' > > > > I have an AMD Athlon 5000+ X2 (made sure I got a processor supporting > > hardware virtualization specifically for this task) with plenty of ram and > > hd space. > > Currently, I have two other linux guests running with full > > virtualization. I would like to keep the native install from Centos 5 x86_64 > > (i.e. I don''t want to compile my own xen from source). The reason why I > > am doing this is so I can take my experiences to my workplace for possible > > deployment on multiple machines. > > > > Does anyone have an idea of what may be preventing me from running this > > Windows XP 64 system in a DOMu? I have also tried a 32 bit system with the > > same results. Thank you. > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thank you all for your help. For whatever reason it took me some time to get a working config for windows xp. I did end up uninstalling Centos'' version of Xen and went with xensource''s open source 3.1 version. I used http://blog.fupps.com/2007/07/05/your-computer-will-be-more-reliable/#comment-1141as a reference. Here is the config I got to work: name = "winxp" builder = "hvm" memory = "500" disk = [ ''file:/xen/win/winxp.img,hda,w'', ''file:/home/bob/WindowsXP/winxp_sp2.iso,hdc:cdrom,r'' ] boot=''c'' vif = [ ''type=ioemu, mac=00:16:3e:0e:b6:e5, bridge=xenbr0'' ] uuid = "c74d2249-9907-5c68-f7ac-314dd11ae7aa" device_model = "/usr/lib64/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=0 vncunused=0 apic=0 acpi=0 sdl=1 vcpus=2 serial = "pty" # enable serial console on_poweroff = ''destroy'' on_reboot = ''restart'' on_crash = ''restart'' usb=1 audio=1 I hope this helps someone. On 6/30/07, Ana <christiana@hipointcoffee.com> wrote:> > On Fri, Jun 29, 2007 at 11:47:22AM +0200, Petersson, Mats wrote: > > > Does anyone have an idea of what may be preventing me from > > > running this Windows XP 64 system in a DOMu? I have also > > > tried a 32 bit system with the same results. Thank you. > > > > I don''t see why 32-bit XP shouldn''t work in this setup - I''m pretty > > certain that it should work. I can also with almost certainty say that > > 3.0.3 doesn''t support 64-bit XP version. You need 3.0.4 for that (I > > would recommend an upgrade to 3.1, as it has a bunch of other > > improvements too). > > I had trouble with installing 32-bit WinXP on a Debian 64-bit AMD system > until I installed 3.1. Since then it''s been smooth sailing. > > - Ana > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users