Hi Trying a lot of configuration combinations, I always fail to boot a new HVM domain with empty hda1 and cdrom as hda2. My current configuration guess is below. When I try to start the domain, Using config file "./windows.conf". Xen lies to me: Started domain windows The domain is NOT started. The qemu-dm-log is below. I don''t know where to start search for the problem... Appreciating any help. (A COMPLETE guide how to setup windows on HVM would be cool. I only found a few very incomplete ones.) Regards, Steffen -- configuration -- kernel = ''/usr/lib/xen/boot/hvmloader'' builder = ''hvm'' memory = ''512'' device_model=''/usr/lib/xen/bin/qemu-dm'' #disk = [ ''phy:/dev/raid/windows,ioemu:hda,w'',''tap:aio:/root/w2k3.iso,ioemu:hdc:cdrom, r'' ] disk = [ ''phy:/dev/raid/windows,ioemu:hda,w'' ] cdrom = ''/root/w2k3.iso'' name = ''windows'' vif = [''type=ioemu,mac=00:16:3e:00:00:08,ip=78.46.250.160/32''] boot=''d'' sdl=0 vnc=1 vncviewer=0 vncpasswd=''cisco'' -- qemu-dm-log -- Watching /local/domain/0/device-model/56/logdirty/next-active Watching /local/domain/0/device-model/56/command bridge xenbr100 does not exist! shift keysym 003e keycode 86 shift keysym 00a6 keycode 86 keypad keysym ffae keycode 83 keypad keysym ffac keycode 83 keypad keysym ffb0 keycode 82 keypad keysym ffb1 keycode 79 keypad keysym ffb2 keycode 80 keypad keysym ffb3 keycode 81 keypad keysym ffb4 keycode 75 keypad keysym ffb5 keycode 76 keypad keysym ffb6 keycode 77 keypad keysym ffb7 keycode 71 keypad keysym ffb8 keycode 72 keypad keysym ffb9 keycode 73 shift keysym 0021 keycode 2 shift keysym 0040 keycode 3 shift keysym 0023 keycode 4 shift keysym 0024 keycode 5 shift keysym 0025 keycode 6 shift keysym 005e keycode 7 shift keysym 0026 keycode 8 shift keysym 002a keycode 9 shift keysym 0028 keycode 10 shift keysym 0029 keycode 11 shift keysym 005f keycode 12 shift keysym 002b keycode 13 shift keysym 007b keycode 26 shift keysym 007d keycode 27 shift keysym 003a keycode 39 shift keysym 0022 keycode 40 shift keysym 007e keycode 41 shift keysym 007c keycode 43 shift keysym 003c keycode 51 shift keysym 003e keycode 52 shift keysym 003f keycode 53 qemu_map_cache_init nr_buckets = 10000 size 3145728 shared page at pfn 1ffff buffered io page at pfn 1fffd Time offset set 0 Register xen platform. Done register platform. I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I can''t tell you anything based on the error, but I have the following
thoughts:
1) I don''t know if the cdrom= line is available in hvm config files.
2) You might try this disk line (removed ioemu):
disk = [ ''phy:/dev/raid/windows,hda,w'' ,
''tap:aio:/root/w2k3.iso,hdc:cdrom,r'' ]
you might also try replacing tap:aio with file, though I think tap:aio is
the newer way. I only mention these possibilities because I don''t know
what
you have and haven''t tried. I have never used ioemu or tap:aio, so I
don''t
know about performance ramifications regarding those settings.
3) I don''t know that you can use ip= in vif= lines. Also, you may need
to
specify the bridge with bridge= in the vif= line. Especially given that
"bridge xenbr100 does not exist!" Additionally, I don''t use
type=ioemu on
my vif.
4) I don''t know if it is important, but my hvm scripts all start with
this
(above kernel=):
import os, re
arch = os.uname()[4]
if re.search(''64'', arch):
arch_libdir = ''lib64''
else:
arch_libdir = ''lib''
5) If your xend-config.sxp has vnclisten="127.0.0.1" you will need to
either
change that to vnclisten="0.0.0.0" or put
vnclisten="0.0.0.0" in the domU
config file in order to connect to vnc from a remote machine (which you
obviously need to do since the dom0 is text only).
6) serial=''pty'' is included in my configs (it is in the
examples, but not a
default setting). You might want to use this so you can a) install Windows
Server via the "serial port" (find documentation at MS) or b) use the
"serial port" for its disaster recovery capabilities (once again, find
documentation at MS, don''t remember what this is called and it has been
a
long time since I''ve done an Windows Server stuff involving headless
machines)
I''m no expert, so all I can say in addition to this is good luck, I
mean, it
is certainly possible that you could try all of my relevant suggestions and
still have no more luck getting the domain created.
Dustin
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Steffen Heil
Sent: Wednesday, July 02, 2008 12:27
To: xen-users@lists.xensource.com
Subject: [Xen-users] Windows HVM domain, next problem
Hi
Trying a lot of configuration combinations, I always fail to boot a new HVM
domain with empty hda1 and cdrom as hda2.
My current configuration guess is below.
When I try to start the domain,
Using config file "./windows.conf".
Xen lies to me:
Started domain windows
The domain is NOT started.
The qemu-dm-log is below.
I don''t know where to start search for the problem...
Appreciating any help.
(A COMPLETE guide how to setup windows on HVM would be cool. I only found a
few very incomplete ones.)
Regards,
Steffen
-- configuration --
kernel = ''/usr/lib/xen/boot/hvmloader''
builder = ''hvm''
memory = ''512''
device_model=''/usr/lib/xen/bin/qemu-dm''
#disk = [
''phy:/dev/raid/windows,ioemu:hda,w'',''tap:aio:/root/w2k3.iso,ioemu:hdc:cdrom,
r'' ]
disk = [ ''phy:/dev/raid/windows,ioemu:hda,w'' ]
cdrom = ''/root/w2k3.iso''
name = ''windows''
vif = [''type=ioemu,mac=00:16:3e:00:00:08,ip=78.46.250.160/32'']
boot=''d''
sdl=0
vnc=1
vncviewer=0
vncpasswd=''cisco''
-- qemu-dm-log --
Watching /local/domain/0/device-model/56/logdirty/next-active
Watching /local/domain/0/device-model/56/command
bridge xenbr100 does not exist!
shift keysym 003e keycode 86
shift keysym 00a6 keycode 86
keypad keysym ffae keycode 83
keypad keysym ffac keycode 83
keypad keysym ffb0 keycode 82
keypad keysym ffb1 keycode 79
keypad keysym ffb2 keycode 80
keypad keysym ffb3 keycode 81
keypad keysym ffb4 keycode 75
keypad keysym ffb5 keycode 76
keypad keysym ffb6 keycode 77
keypad keysym ffb7 keycode 71
keypad keysym ffb8 keycode 72
keypad keysym ffb9 keycode 73
shift keysym 0021 keycode 2
shift keysym 0040 keycode 3
shift keysym 0023 keycode 4
shift keysym 0024 keycode 5
shift keysym 0025 keycode 6
shift keysym 005e keycode 7
shift keysym 0026 keycode 8
shift keysym 002a keycode 9
shift keysym 0028 keycode 10
shift keysym 0029 keycode 11
shift keysym 005f keycode 12
shift keysym 002b keycode 13
shift keysym 007b keycode 26
shift keysym 007d keycode 27
shift keysym 003a keycode 39
shift keysym 0022 keycode 40
shift keysym 007e keycode 41
shift keysym 007c keycode 43
shift keysym 003c keycode 51
shift keysym 003e keycode 52
shift keysym 003f keycode 53
qemu_map_cache_init nr_buckets = 10000 size 3145728 shared page at pfn 1ffff
buffered io page at pfn 1fffd Time offset set 0 Register xen platform.
Done register platform.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Hi> 1) I don''t know if the cdrom= line is available in hvm config files.Tried with cdrom= and with 2 devices, both don''t work.> disk = [ ''phy:/dev/raid/windows,hda,w'' , > ''tap:aio:/root/w2k3.iso,hdc:cdrom,r'' ]Still the same problem.> you might also try > replacing tap:aio with file, though I think tap:aio is the > newer way.Trying file instead of tap:aio it hangs on create.> I only mention these possibilities because I > don''t know what you have and haven''t tried. I have never > used ioemu or tap:aio, so I don''t know about performance > ramifications regarding those settings.Neither do I. Right now, performance is not a problem, I cannot get it to even boot once.> 3) I don''t know that you can use ip= in vif= lines. Also, > you may need to specify the bridge with bridge= in the vif= > line. Especially given that "bridge xenbr100 does not > exist!" Additionally, I don''t use type=ioemu on my vif.Thats what I do in my PV linux domUs, as I use routed networking instead of bridged. Therefor I have NO bridge to connect to.> 4) I don''t know if it is important, but my hvm scripts all > start with this (above kernel=): > import os, re > arch = os.uname()[4] > if re.search(''64'', arch): > arch_libdir = ''lib64'' > else: > arch_libdir = ''lib''This local variable is usually later used to compose the path to qemu like this: device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' As on my system there is only ''/usr/lib/xen/bin/qemu-dm'' though it is 64bit (ubuntu hardy) I removed that unnessessary section.> 5) If your xend-config.sxp has vnclisten="127.0.0.1" you will > need to either change that to vnclisten="0.0.0.0" or put > vnclisten="0.0.0.0" in the domU config file in order to > connect to vnc from a remote machine (which you obviously > need to do since the dom0 is text only).No. I want vnc to bind to 127.0.0.1 only, as I forward vnc through ssh.> 6) serial=''pty'' is included in my configs (it is in the > examples, but not a default setting). You might want to use > this so you can a) install Windows Server via the "serial > port" (find documentation at MS) or b) use the "serial port" > for its disaster recovery capabilities (once again, find > documentation at MS, don''t remember what this is called and > it has been a long time since I''ve done an Windows Server > stuff involving headless > machines)I tried adding this one, but it doesn''t change anything.> I''m no expert, so all I can say in addition to this is good > luck, I mean, it is certainly possible that you could try all > of my relevant suggestions and still have no more luck > getting the domain created.Could you send me one of your complete hvm config files? Regards, Steffen _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Damn, I found the problem: There is a bug in ubuntu hardy, and I cannot use file:, so I cannot use it for the cdrom-iso. losetup and then using the device works. Sorry Steffen> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Steffen Heil > Sent: Thursday, July 03, 2008 11:40 PM > To: Dustin.Henning@prd-inc.com; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Windows HVM domain, next problem > > Hi > > > 1) I don''t know if the cdrom= line is available in hvm config files. > > Tried with cdrom= and with 2 devices, both don''t work. > > > > disk = [ ''phy:/dev/raid/windows,hda,w'' , > > ''tap:aio:/root/w2k3.iso,hdc:cdrom,r'' ] > > Still the same problem. > > > > you might also try > > replacing tap:aio with file, though I think tap:aio is the > newer way. > > Trying file instead of tap:aio it hangs on create. > > > > I only mention these possibilities because I don''t know > what you have > > and haven''t tried. I have never used ioemu or tap:aio, so I don''t > > know about performance ramifications regarding those settings. > > Neither do I. > Right now, performance is not a problem, I cannot get it to > even boot once. > > > > 3) I don''t know that you can use ip= in vif= lines. Also, you may > > need to specify the bridge with bridge= in the vif= line. > Especially > > given that "bridge xenbr100 does not exist!" Additionally, I don''t > > use type=ioemu on my vif. > > Thats what I do in my PV linux domUs, as I use routed > networking instead of bridged. > Therefor I have NO bridge to connect to. > > > > 4) I don''t know if it is important, but my hvm scripts all > start with > > this (above kernel=): > > import os, re > > arch = os.uname()[4] > > if re.search(''64'', arch): > > arch_libdir = ''lib64'' > > else: > > arch_libdir = ''lib'' > > This local variable is usually later used to compose the path > to qemu like > this: > device_model = ''/usr/'' + arch_libdir + ''/xen/bin/qemu-dm'' > > As on my system there is only ''/usr/lib/xen/bin/qemu-dm'' > though it is 64bit (ubuntu hardy) I removed that unnessessary section. > > > > 5) If your xend-config.sxp has vnclisten="127.0.0.1" you > will need to > > either change that to vnclisten="0.0.0.0" or put > vnclisten="0.0.0.0" > > in the domU config file in order to connect to vnc from a remote > > machine (which you obviously need to do since the dom0 is > text only). > > No. > I want vnc to bind to 127.0.0.1 only, as I forward vnc through ssh. > > > > 6) serial=''pty'' is included in my configs (it is in the > examples, but > > not a default setting). You might want to use this so you can a) > > install Windows Server via the "serial port" (find documentation at > > MS) or b) use the "serial port" > > for its disaster recovery capabilities (once again, find > documentation > > at MS, don''t remember what this is called and it has been a > long time > > since I''ve done an Windows Server stuff involving headless > > machines) > > I tried adding this one, but it doesn''t change anything. > > > > I''m no expert, so all I can say in addition to this is good luck, I > > mean, it is certainly possible that you could try all of my > relevant > > suggestions and still have no more luck getting the domain created. > > Could you send me one of your complete hvm config files? > > > Regards, > Steffen >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users