[Xen-users] Re: Setup WinXP with HVM and qemu image

[Geert Janssens <info@xxxxxxxxxxxx>]

Mark, Martin and Igor,

Thank you for your quick responses. I got a little further already.

I converted my qcow diskfile to raw as suggested by Igor, I explicitly added a 
device for the cdrom entry, I also removed the cdrom entry completely...

vncviewer localhost::5910 results in the same error message (connection 
refused). I assume this means the vnc server isn't running ?

Then I noticed that qemu-dm.<pid>.log contains this:
domid: 5
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 18dc2
buffered io page at pfn:1fffd, mfn: 18dc4
xs_read(): vncpasswd get error.
       /vm/89bf518d-a688-d763-30ba-b3755f934861/vncpasswd.
Could not read keymap file: '/usr/share/xen/qemu/keymaps/be'

I searched for the missing keymap, and indeed, "be" isn't listed. "nl-be" is, 
so I used that.

With these changes, the vnc console pops up by itself (Yay!), but after a very 
short time only shows me a black screen. The top command shows that qemu-dm 
is using 100% cpu on one of the cores. When I remove the keyboard parameter, 
it's slightly different: the vnc console pops up, it detects my primary HD, 
then prints "Booting from Hard Disk..." and then just sits there, again with 
qemu-dm taking 100% cpu on one core.

qemu-dm.<pid>.log now contains:
domid: 7
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 1cdc2
buffered io page at pfn:1fffd, mfn: 1cdc4
xs_read(): vncpasswd get error.
       /vm/430a79b5-d4d5-92a7-82ef-b8be59f62749/vncpasswd.
char device redirected to /dev/pts/5
False I/O request ... in-service already: 0, pvalid: 0, port: 0, data: 0,
                                   count: 0, size: 0

xm list gives:
[root@localhost ~]# xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0     1488     2 r-----   1639.8
WindowsXP                                  7      517     1 ------      0.2
So there seems to be slightly more activity (0.2), although this time doesn't 
increase anymore.

I have no idea how to proceed here. Any ideas ?

By the way: although I explicitly set vncdisplay, the vncserver continues to 
look for an unused port, as ps shows:
root     12440     1  0 11:27 ?        00:00:00
        /usr/lib/xen/bin/xen-vncfb --unused --listen 0.0.0.0
                                   --domid 7 --title WindowsXP

I tried to add vncunused=0, but that resulted in an error message when 
creating the domain:
Error: unsupported input type(s) for operand +: 'int' and 'str'.
But this doesn't really matter anymore for my setup, so I disabled it again.


Regards,

Geert

On Thursday 31 May 2007 23:07, you wrote:
> Hi,
>
> I am trying to accomplish the following:
> - The hardware is a recent HP workstation xw6400 with a dual core Xeon
> processor. HVM is enabled in bios. 2Gb Ram available.
> - Dom0 is Centos 5, x86 (on xen 3.0.3 with redhat's modifications)
> - I would like to migrate a Qemu Windows XP installation to a xen hvm
>
> I figured this should not be too hard, because full virtualisation uses the
> same (or allmost the same?) device model as qemu and under qemu, my Windows
> XP installation is working fine.
>
> I have created a config file (see below), and started the guest domain with
> xm create /etc/xen/WinXP.hvm
>
> xm then tells me that the domain was started succesfully, and xm list does
> show it:
> [root@localhost ~]# xm list
> Name                                      ID Mem(MiB) VCPUs State   Time(s)
> Domain-0                                   0     1488     2 r-----    185.5
> WindowsXP                                  6      517     1 ------      0.0
>
> However, I can't find a way to connect to it via vnc. I tried
> vncviewer localhost:10
>
> But this returns immediatly with
> VNC Viewer Free Edition 4.1.2 for X - built Mar 14 2007 22:51:02
> Copyright (C) 2002-2005 RealVNC Ltd.
> See http://www.realvnc.com for information on VNC.
>
> Thu May 31 22:53:15 2007
>  main:        unable to connect to host: Connection refused (111)
>
> What is happening here ?
>
> Below is my Guest domain's config. I have set the options to match the
> original qemu config as close as possible.
> #  -*- mode: python; -*-
> #==========================================================================
>== # Python configuration setup for 'xm create'.
> # This script sets the parameters used when a domain is created using 'xm
> create'.
> # You use a separate script for each domain you want to create, or
> # you can set the parameters for the domain on the xm command line.
> #==========================================================================
>== 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
> shadow_memory = 8
> name = "WindowsXP"
> vcpus=2
> #pae=0
> #acpi=0
> #apic=0
> vif = [ 'type=ioemu, mac=00:18:32:6c:00:ba, bridge=xenbr0' ]
> disk = [ 'file:/var/images/winxp.qcow,hda,w', ',hdc:cdrom,r' ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> sdl=0
> vnc=1
> vncdisplay=10
> vncconsole=0
> vncpasswd=''
> stdvga=1
> serial='pty'
> soundhw='sb16'
> usb=1
> usbdevice='tablet'
> keymap='be'
>
>
> Geert

-- 
Kobalt W.I.T.
Web & Information Technology
Brusselsesteenweg 152
1850 Grimbergen

Tel  : +32 479 339 655
Email: info@xxxxxxxxxxxx

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