[Xen-users] stubdom not working

["Ralf Hornik Mailings" <ralf@xxxxxxxxxxxxxxxxx>]

Dear List,

I tried several howtos, wikis, and readmes but I do not get a WinXP  
HVM working with stubdom.
I use xen-3.4 unstable.

cat winxp:
---------------------------------------
kernel = "/usr/lib/xen/boot/hvmloader"
builder = 'hvm'
memory = 512
name = "winxp"
vcpus = 1
cpu = 3
pae = 0
acpi = 1
apic = 1
usb = 1
audio = 1
vif = [ 'bridge=br0' ]
device_model = '/usr/lib/xen/bin/stubdom-dm'
boot = 'c'
vnc = 1
vnclisten = '10.0.0.99'
sdl = 0
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"

cat winxp-dm:
--------------------------------
kernel = '/usr/lib/xen/boot/ioemu-stubdom.gz'
disk = [ 'phy:/dev/xen_vol/xen_winxp,hda,w' ]
vif = [ 'ip=10.0.0.99', 'bridge=br0' ]

qemu-dm-winxp.log:
--------------------------------------------
Using config file "/etc/xen/winxp-dm".
Started domain winxp-dm (id=23)
Xen Minimal OS!
start_info:   0x528000
  nr_pages:   8192  shared_inf: 7cf9e000
  pt_base:    0x52b000  mod_start:  0x0
  mod_len:    0
  flags:      0x0
  cmd_line:    -d 22
  stack:      0x4d74c0-0x4f74c0
MM: Init
  _text:        0x0
  _etext:       0xda5b6
  _erodata:     0x11e000
  _edata:       0x12d7a4
  stack start:  0x4d74c0
  _end:         0x517dd0
  start_pfn:    535
  max_pfn:      2000
Mapping memory range 0x800000 - 0x2000000
setting 0x0-0x11e000 readonly
skipped 0x1000
MM: Initialise page allocator for 541000(541000)-2000000(2000000)
MM: done
Demand map pfns at 2001000-2002001000.
Heap resides at 2002002000-4002002000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x2001000.
Initialising scheduler
Thread "Idle": pointer: 0x2002002010, stack: 0x560000
Initialising xenbus
Thread "xenstore": pointer: 0x20020027c0, stack: 0x570000
Dummy main: start_info=0x4f75c0
Thread "main": pointer: 0x2002002f70, stack: 0x580000
[main] Waiting for network.
************************ NETFRONT for device/vif/0 **********


net TX ring size 256
net RX ring size 256
backend at /local/domain/0/backend/vif/24/0
mac is 00:16:3e:76:9a:fb
**************************
[main] IP a000063 netmask ff000000 gateway 0.
[main] TCP/IP bringup begins.
Thread "tcpip_thread": pointer: 0x2002005cb0, stack: 0x690000
[tcpip_thread] TCP/IP bringup ends.
[main] Network is ready.
Initing FS fronend(s).
FS export [dom=0, id=0] found
Initialising FS fortend to backend dom 0
Allocating request array for import 0, nr_entries = 128.
Our own id is 24
Backend found at /local/domain/0/backend/vfs/7
Backend ready.
dom vm is at /vm/760db735-56f2-6c68-d4d2-ffe78b5a06d4
"main" "-d" "22" "-domain-name" "winxp" "-k" "de" "-vnc" "10.0.0.99:0"  
"-vncunused" "-vcpus" "1" "-boot" "c" "-acpi" "-usb" "-net"  
"nic,vlan=1,macaddr=00:16:3e:5c:69:6c,model=rtl8139" "-net"  
"tap,vlan=1,ifname=tap22.0,bridge=br0"
domid: 22
qemu: the number of cpus is 1
************************ NETFRONT for device/vif/1 **********


net TX ring size 256
net RX ring size 256
backend at /local/domain/0/backend/vif/24/1
mac is 00:16:3e:6a:d5:a7
**************************
tap_open(device/vif/1) -> 3
xs_daemon_open -> 5, 0x129a78
******************* BLKFRONT for /local/domain/24/device/vbd/768 **********


backend at /local/domain/0/backend/vbd/24/768
Failed to read /local/domain/0/backend/vbd/24/768/feature-flush-cache.
20971520 sectors of 512 bytes
**************************
blk_open(/local/domain/24/device/vbd/768) -> 6
xs_directory(/local/domain/24/device/vkbd): ENOENT
xs_directory(/local/domain/24/device/vfb): ENOENT
xs_watch(/local/domain/0/device-model/22/logdirty/next-active, logdirty)
Watching /local/domain/0/device-model/22/logdirty/next-active
xs_watch(/local/domain/0/device-model/22/command, dm-command)

qemu-dm-winxp-dm.log
---------------------------------------------------------
domid: 20
Warning: vlan 0 is not connected to host network
Watching /local/domain/0/device-model/20/logdirty/next-active
Watching /local/domain/0/device-model/20/command
xs_read(): vncpasswd get error.  
/vm/5bcea42a-536f-d4c8-3cf2-a02fc4f4831b/vncpasswd.
char device redirected to /dev/pts/3
/opt/install/xen/xen-unstable.hg/tools/ioemu-dir/hw/xen_blktap.c:630:  
Init blktap pipes
Console: prepared domain, waiting for ringref at  
/local/domain/20/console or /local/domain/20/serial/0
FB: Waiting for KBD backend creation
Doing backend watch on /local/domain/0/backend/vkbd/20/0
FB: Waiting for FB backend creation
Doing backend watch on /local/domain/0/backend/vfb/20/0
Console: got watch
Console: failed to find ring-ref/port yet
FB: Waiting for KBD frontend initialization
Doing frontend watch on /local/domain/20/device/vkbd/0
Console: got watch
Console: failed to find ring-ref/port yet
FB: Carry on waiting
Console: got watch
Console: got ring-ref 103917 port 2 limit 1048576
Console: connected to guest frontend


xm list:
------------
Name                                        ID   Mem VCPUs      State   
 Time(s)
Domain-0                                     0   256     4     r-----   1108.7
winxp                                       22   512     1     ------      0.0

Finally, no vnc, no ping or any other communication is possible  
neither to stubdom nor to hvm itself.
What am I doing wrong??
Thanx for any hints and help

Ralf


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