Re: [Xen-users] WinXP domU lockup

[Art Fore <art.fore@xxxxxxxxx>]

On Wed, 2006-11-08 at 17:42 +0800, Art Fore wrote:
> 
> 
> On 11/8/06, Steven Smith <sos22-xen@xxxxxxxxxxxxx> wrote:
>         > Set vcpus to 1 and PAE to 0. No change. This all from
>         starting with
>         > virt-manager. However, I cannot save machine, always have to
>         dor
>         > File, New machine, and fillinallof the blanks again. Gets to
>         be a
>         > real pain, but changing the winxp hvm file does affect it.
>         I've never used virt-manager, so can't speak for it's
>         idiosyncrasies.
>         
>         > When I try to execute xm create winxp, it starts up, then
>         gets to a
>         > point and asks to please install GLOBAL/DEVICES/CDROM. 
>         Just to confirm, this is a message on the window which pops up
>         after
>         you do xm create, and not something in one of the Xen logs?
>         
>         > If I modify the disk =
>         [ 'file:/home/afore/VM_images/WinXP,hda,w', ]
>         > to disk = [ 'file:/home/afore/VM_images/WinXP,hda,w',
>         ',hdc:cdrom,r'] and 
>         > remove the cdrom='/dev/hdc, windows then has a message about
>         inserting
>         > the winxp disk, so at least it is finding it, but cannot
>         read it.
>         > xm dmesg then shows the
>         > (XEN) (GUEST: 4) ata1 master: QEMU CD-ROM ATAPI-4
>         CD-Rom/DVD-Rom 
>         > (XEN) (GUEST: 4) ata1  slave: Unknown device
>         > again.
>         What if you say
>         
>         disk = [ 'file:/home/afore/VM_images/WinXP,hda,w',
>         'phy:/dev/hdc,hdc:cdrom,r']
>         
>         instead?
>         
>         Steven.
>         
>         I gave up on X86-64. I installed 32-bit x86 smp Suse 10.1 and
>         will try it. Sorry I got your message too late. Did already
>         try the 3.0.3 rpm update from xensource website, that was
>         again a disaster. Instructions wrong again. Had to reinstall
>         as it screwed up my system so bad, it was faster than
>         researching all of its problems even with the non-xen kernel.
>         If Suse 10.1 does not work, will give it one more try with
>         Fedora FC6 32-bit before I throw in the towel and get VMware
>         or try Parallels I know parallels works on 32-bit as I have it
>         on my old inspiron 8500, but it is a little too slow for cad
>         work. Will see how it works with smp. 
> 
> Art 

Same problem in 32-bit mode with Suse 10.1 default xen 3.0.2. Your
disk=[ 'file:/home/afore/VM_images/WinXP,hda,w','phy:/dev/hdc,hdc:cdrom,r']
results in invalid Disk specifier:
file:/home/afore/VM_images/WinXP,hda,w

So one last try with fedora FC6 tomorrow.

Art

Oh, forgot to mention, on the winxp install, gets to the same point as in FC6, 
x86-64 but instead of locking up just the virtual machine it locks up the 
complete machine. Only recovery is master reset or Power off.
Was following the instructions from 
http://en.opensuse.org/Xen_Full_Virtualization_Example. as the Suse Yast 
Virtual machine thingy did not work either.

Art


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users