[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Can't boot Xen 3.0 under VMWare GSX 3.2


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Sean McCombe <sean.j.mccombe@xxxxxxxxx>
  • Date: Tue, 20 Dec 2005 18:28:22 -0800
  • Delivery-date: Wed, 21 Dec 2005 02:31:16 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=umDiYtE5PJAHNlIpVazGjsE1JtbaWeuj74x8w7VjCSfa+855ETRQIh20ZEcZReJxHtgjo3K09NeMH+T5hVXu/LCzietz+EUoX+JWjx0fGUNaLu/nFILjIXsqTZEWs6i42ZnguAVWFkZP92ZCnmfk9ZGg9Ysn9QCBJtdrEKD5U2w=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi
 
I'm attempting to boot Xen 3.0/Fedora Core 4 on GSX 3.2. After a time, the boot simply hangs, and I receive the same error message as was encountered by Michael Lang back in May of this year:
 
--------------------------------------------
 
Hi to all,

upgraded to Xen 2.0.6 on VMWare 5.0 Workstation, worked fine by using
the *old* 2.0.5 Configs, i encounterd the following Error Messages on boot for 2
times, cause VMWareMachine is configured without a Floppy Drive.

With 2.0.5 same VMWareMachine the Error doesnt show up, any suggestions ?
(the Machine is working even with this error)

Kind Regards
Michael Lang

<snip>
floppy0: get result error. Fdc=0 Last status=f0 Read bytes=0

floppy driver state
-------------------
now=4294955418 last interrupt=4294955418 diff=0 last called handler=c0234cce
timeout_message=lock fdc
last output bytes:
12 80 4294938387
 0 90 4294938387
14 80 4294938387
18 80 4294938387
 8 80 4294938387
 8 80 4294938387
 8 80 4294938387
 8 80 4294938387
12 80 4294955417
 0 90 4294955417
13 80 4294955417
 0 90 4294955417
1a 90 4294955417
 0 90 4294955417
 3 80 4294955417
c1 90 4294955417
11 90 4294955417
 7 80 4294955417
 0 90 4294955417
 8 80 4294955418
last result at 4294955418
last redo_fd_request at 4294955413

status=f0
fdc_busy=1
timer_function=c0235607
expires=295
now=4294955418
cont=c04432b4
current_req=00000000
command_status=-1

</snip>
--------------------------------------------
 
I've added a floppy drive to the virtual hardware, but this did not help. Does anybody have any ideas on how to solve this problem?
 
Cheers,
Sean
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.