On Fri, Nov 14, 2008 at 2:46 AM, Peter Privat <peter.privat@xxxxxxxxxxxx> wrote:
> I finally managed to make the Xen to not complain about Windows guest
> configuration, devices, loops etc. But now there's another problem. The
> Guest doesn't turn up. It looks like it's been started fine when executing,
> but then doesn't show up in the XM list.
something went wrong during boot, check /var/log/xen/qemu*.log
(a qemu*.log is created for each Windows/HVM guest)
I would also try file: instead of tap:aio for the disks, even though
file: is supposed to be deprecated, sometimes it still works
better in some situations.
> I'm using this configuration file:
> import os, re
> arch = os.uname()
> if re.search('64', arch):
> arch_libdir = 'lib64'
> arch_libdir = 'lib'
> kernel = "/usr/lib/xen/boot/hvmloader"
> memory = 1024
> shadow_memory = 8
> name = "xenhvm"
> vif = [ 'type=ioemu, bridge=xenbr0' ]
> disk = [ 'tap:aio:/home/xen/domains/windows/xenwin.img,hda,w',
> 'tap:aio:/home/xen/domains/windows/win2k3.iso,hdc:cdrom,r' ]
> device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
> #device_model = '/usr/lib64/xen/bin/qemu-dm'
> # boot on floppy (a), hard disk (c) or CD-ROM (d)
> # default: hard disk, cd-rom, floppy
What version of Xen are you working with?
setting the vnc options to 0 and sdl to 1 might be something
Also if it happens to be Xen 3.3, replacing the vncconsole
line with vncviewer="yes" would be another thing to try.
Most of the time, when it quits write away it is a problem
with either the disk image or the cdrom.
Hope that helps.
Xen-users mailing list