Fedora xen - Nov 2006 - problems installing winxp with full virtualization on FC6

My notebook has a Turion 64 x2 processor, 2GB  of RAM, FC 6 x86-64, and booting
the WinXP VM off the CD works fine (setup copies over all the files to the
virtual HDD), but when the VM attempts to reboot off the hard drive, it
fails/hangs.  Running "xm dmesg" gives:

(XEN) (GUEST: 3) 
(XEN) (GUEST: 3) ata0-0: PCHS=8322/16/63 translation=lba LCHS=522/255/63
(XEN) (GUEST: 3) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (4096 MBytes)
(XEN) (GUEST: 3) ata0  slave: Unknown device
(XEN) (GUEST: 3) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 3) ata1  slave: Unknown device
(XEN) (GUEST: 3) 
(XEN) (GUEST: 3) Booting from Hard Disk...
(XEN) (GUEST: 3) unsupported PCI BIOS function 0x0E
(XEN) (GUEST: 3) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 3) *** int 15h function AX=E980, BX=00F2 not yet supported!
(XEN) hvm_vioapic_write_indirect: version register read only
(XEN) hvm_vioapic_write_indirect: version register read only
(XEN) hvm_vioapic_write_indirect: version register read only
(XEN) This hvm_vlapic is for P4, no work for De-assert init

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 and specify the computer as not having APIC
but the version of VNC or whatever console emulator that comes with Virtual
Machine Manager doesn''t seem to pass function keys thru (F2, F5, or F6
don''t appear to work).  I''m at a loss on where to go from
here, except to perhaps start compiling everything from latest sources (which
would be alot of trouble).

Advice???

Below is my winxp VM config file:

name = "winxp"
builder = "hvm"
memory = "256"
disk = [ ''phy:/dev/vg0/domuwinxp,hda,w'',
''phy:/dev/hdb,hdc:cdrom,r'' ]
boot = ''c''
vif = [ ''type=ioemu, mac=00:16:3e:45:71:31, bridge=xenbr0'', ]
uuid = "fd2e0fd5-c586-0127-4d3d-0e272a5894d2"
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=1
serial = "pty" # enable serial console
on_reboot   = ''restart''
on_crash    = ''restart''

On Thu, Nov 02, 2006 at 04:52:48PM -0600, Jeff Stockett
wrote:
> 
> 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 
> and specify the computer as not having APIC but the version of VNC 
> or whatever console emulator that comes with Virtual Machine Manager
> doesn''t seem to pass function keys thru (F2, F5, or F6
don''t appear
> to work).  I''m at a loss on where to go from here, except to
perhaps
> start compiling everything from latest sources (which would be alot 
> of trouble).
> 
> builder = "hvm"
> memory = "256"
> disk = [ ''phy:/dev/vg0/domuwinxp,hda,w'',
''phy:/dev/hdb,hdc:cdrom,r'' ]
> boot = ''c''
> vif = [ ''type=ioemu, mac=00:16:3e:45:71:31,
bridge=xenbr0'', ]
> uuid = "fd2e0fd5-c586-0127-4d3d-0e272a5894d2"
> device_model = "/usr/lib64/xen/bin/qemu-dm"
> kernel = "/usr/lib/xen/boot/hvmloader"
> vnc=1
> vncunused=1
> apic=1
> acpi=1
Try toggling these last two settings here - one of the 4 different combos
of acpi & apic may well help.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

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@redhat.com>