On Thu, Nov 02, 2006 at 04:52:48PM -0600, Jeff Stockett wrote:
I successfully tried install WinXP last week.
$ xenguest-install -n winxp-i686-full -r 500 -f
/org/xen/winxp-i686-full.img -s 4 --vnc -v -c /dev/scd0
# rpm -q xen kernel-xen python-xeninst
xen-3.0.3-0.1.rc3
kernel-xen-2.6.18-1.2798.fc6
python-xeninst-0.93.0-1
The *final* domain config (generated by xenquest-install):
# Automatically generated xen config file
name = "winxp-i686-full"
builder = "hvm"
memory = "500"
disk = [ 'file:/xen/winxp-i686-full.img,hda,w', ]
vif = [ 'type=ioemu, mac=00:16:3e:2d:ec:27, bridge=xenbr0', ]
uuid = "42f399ce-699a-fafc-4e18-37e17f49aabd"
device_model = "/usr/lib/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
vnc=1
vncunused=1
apic=1
acpi=1
pae=1
serial = "pty" # enable serial console
on_reboot = 'restart'
on_crash = 'restart'
> I see from googling, that this bug has been reported once before
> (last month with a rawhide build) - but no answers. A little further
> googling indicates that one possible workaround might be to hit F5
> (when it is asking for F6 to load drivers) during the setup process
I've used this trick too. The key F5 works for me in vncviewer
(vnc-4.1.1-39.fc5 -- my workstation is FC5, the server with Xen is
FC6). The Windows installer allows to select some install profiles if
you press F5 -- but things probably depend on XP version, because the
menu for F5 contains different profiles in different XP versions (I've
used Czech XP edition and there was two profiles only).
> Advice???
Don't use Close Source Operation Systems :-)
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
--
Fedora-xen mailing list
Fedora-xen@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
