I had a working Win2003 install on a "herited" system (xen 3.2.x), but
I
have recently made a fresh install of xen with debian lenny (i.e.
xen-3.2.1).
Now, I am not able to start the old HVM guests...
kernel = "/usr/lib/xen-default/boot/hvmloader"
builder=''hvm''
memory = 2048
shadow_memory = 64
name = "winserver"
vcpus=1
cpus = "4-7"
vif = [ ''mac=00:16:3e:00:00:02, type=ioemu, bridge=xenbr0'',
''mac=00:16:3e:00:01:02, type=ioemu, bridge=xenbr1'' ]
disk = [ ''phy:/dev/system/wintest_c,hda,w'',
''phy:/dev/system/wintest_d,hdb,w'',
''file:/tmp/2003.iso,ioemu:hdc:cdrom,r'' ]
device_model = ''/usr/lib/xen-default/bin/qemu-dm''
boot = "d"
# the same is with boot = "c"
rtc_timeoffset=7200
vnc=1
vnclisten="152.66.33.250"
stdvga=0
usbdevice=''tablet''
The vifs are created, the domU is started, but xm list shows only
"dashes".
# xm create 3_wintest.conf
Using config file "./3_wintest.conf".
Started domain winserver
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 512 1 r----- 14759.7
linserver 31 6144 4 -b---- 2584.4
winserver 41 2048 1 ------ 0.0
# xm vcpu-list
Name ID VCPU CPU State Time(s) CPU
Affinity
Domain-0 0 0 0 r-- 14606.2 0
Domain-0 0 1 - --p 37.4 1
Domain-0 0 2 - --p 18.5 2
Domain-0 0 3 - --p 14.8 3
Domain-0 0 4 - --p 20.3 4
Domain-0 0 5 - --p 20.0 5
Domain-0 0 6 - --p 21.3 6
Domain-0 0 7 - --p 21.3 7
linserver 31 0 2 -b- 2015.9 1-4
linserver 31 1 1 -b- 178.3 1-4
linserver 31 2 4 -b- 205.3 1-4
linserver 31 3 1 -b- 185.0 1-4
winserver 41 0 6 --- 0.0 4-7
And I am not even able to connect to the VNC port:
$ xvncviewer xenserver:0
xvncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server
and on xenserver:
# netstat -ptln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN
-
tcp 0 0 0.0.0.0:42598 0.0.0.0:* LISTEN
4293/rpc.mountd
tcp 0 0 0.0.0.0:52999 0.0.0.0:* LISTEN
3530/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
3517/portmap
tcp 0 0 0.0.0.0:59026 0.0.0.0:* LISTEN
-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
4589/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
4246/exim4
tcp6 0 0 :::22 :::* LISTEN
4589/sshd
What did I wrong or missed?
--
Zsolt
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
What does xend.log show when you run this?
My suggestion here would be as follows.
Open 1 ssh to server and tail -f the xend.log file to watch the output of
xen while the windows guest is starting
Open another ssh to server and issue the command to start the windows guest.
Giving us the output of the xend.log file will help us here.
-----Original Message-----
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of SZABO Zsolt
Sent: Monday, August 24, 2009 6:18 AM
To: xen-users@lists.xensource.com
Subject: [Xen-users] unable to start windows HVM guest
I had a working Win2003 install on a "herited" system (xen 3.2.x), but
I
have recently made a fresh install of xen with debian lenny (i.e.
xen-3.2.1).
Now, I am not able to start the old HVM guests...
kernel = "/usr/lib/xen-default/boot/hvmloader"
builder=''hvm''
memory = 2048
shadow_memory = 64
name = "winserver"
vcpus=1
cpus = "4-7"
vif = [ ''mac=00:16:3e:00:00:02, type=ioemu, bridge=xenbr0'',
''mac=00:16:3e:00:01:02, type=ioemu, bridge=xenbr1'' ]
disk = [ ''phy:/dev/system/wintest_c,hda,w'',
''phy:/dev/system/wintest_d,hdb,w'',
''file:/tmp/2003.iso,ioemu:hdc:cdrom,r'' ]
device_model = ''/usr/lib/xen-default/bin/qemu-dm''
boot = "d"
# the same is with boot = "c"
rtc_timeoffset=7200
vnc=1
vnclisten="152.66.33.250"
stdvga=0
usbdevice=''tablet''
The vifs are created, the domU is started, but xm list shows only
"dashes".
# xm create 3_wintest.conf
Using config file "./3_wintest.conf".
Started domain winserver
# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 512 1 r-----
14759.7
linserver 31 6144 4 -b----
2584.4
winserver 41 2048 1 ------
0.0
# xm vcpu-list
Name ID VCPU CPU State Time(s) CPU
Affinity
Domain-0 0 0 0 r-- 14606.2 0
Domain-0 0 1 - --p 37.4 1
Domain-0 0 2 - --p 18.5 2
Domain-0 0 3 - --p 14.8 3
Domain-0 0 4 - --p 20.3 4
Domain-0 0 5 - --p 20.0 5
Domain-0 0 6 - --p 21.3 6
Domain-0 0 7 - --p 21.3 7
linserver 31 0 2 -b- 2015.9 1-4
linserver 31 1 1 -b- 178.3 1-4
linserver 31 2 4 -b- 205.3 1-4
linserver 31 3 1 -b- 185.0 1-4
winserver 41 0 6 --- 0.0 4-7
And I am not even able to connect to the VNC port:
$ xvncviewer xenserver:0
xvncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server
and on xenserver:
# netstat -ptln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN
-
tcp 0 0 0.0.0.0:42598 0.0.0.0:* LISTEN
4293/rpc.mountd
tcp 0 0 0.0.0.0:52999 0.0.0.0:* LISTEN
3530/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
3517/portmap
tcp 0 0 0.0.0.0:59026 0.0.0.0:* LISTEN
-
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
4589/sshd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
4246/exim4
tcp6 0 0 :::22 :::* LISTEN
4589/sshd
What did I wrong or missed?
--
Zsolt
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Solved (I have found the /var/log/xen/qemu-dm*log... :-) The problem was about the renaming of xenbr0 (to eth0)... -- Zsolt _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users