[Xen-users] xen dom0 reboot when windows hvm started

[Ronny Wagner <r.wagner@xxxxxxxxx>]

Dear Community,

i have a problem with a new debian XEN 64bit squeeze Server, when i started
a windows hvm domU. I tested with the routed and now in the bridge network
mod.

I start the domU with xm create win.cfg and 1 or 2 second the dom0 is
reboot. I install a debian domU on the system, and this is without any
problems in routed and bridge mod.

In the logfile are no informations, in the routed mod there is a fail
message:
The first message
domid: 1
-c config qemu network with xen bridge for
tap-vif-win2k3 xenbr0
bridge xenbr0 does not exist!
/etc/xen/scripts/qemu-ifup: could not launch network script
Could not initialize device 'tap'

Then I use the bridge mod, now is a new message:
domid: 2
-c config qemu network with xen bridge for
tap-vif-win2k3 eth0
Using file /root/disk.img in read-write mode
Watching /local/domain/0/device-model/2/logdirty/cmd
Watching /local/domain/0/device-model/2/command
char device redirected to /dev/pts/2
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = 1ca7a574-8d1d-82f2-986e-48fe1ebf8ce7
Time offset set 0
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
Log-dirty: no command yet.
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
xs_read(/local/domain/2/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/2/log-throttling'
medium change watch on `/local/domain/2/log-throttling' - unknown device,
ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000

The last message before the server reboot is in syslog:
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/1/0
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/1/768
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.653456] device vif-win2k3 
entered promiscuous mode
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.655210] ADDRCONF(NETDEV_UP): 
vif-win2k3: link is not ready
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/block: Writing 
backend/vbd/1/768/node /dev/loop0 to xenstore.
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.708311] nf_conntrack version 
0.5.0 (2763 buckets, 11052 max)
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/block: Writing 
backend/vbd/1/768/physical-device 7:0 to xenstore.
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/block: Writing 
backend/vbd/1/768/hotplug-status connected to xenstore.
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.770812] xt_physdev: 
using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for 
non-bridged traffic is not supported anymore.
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.794340] xt_physdev: 
using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for 
non-bridged traffic is not supported anymore.
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.796160] xt_physdev: 
using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for 
non-bridged traffic is not supported anymore.
Jun 20 11:48:09 lic-srv-xen-02 kernel: [57683.796163] xt_physdev: 
using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for 
non-bridged traffic is not supported anymore.
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/vif-bridge: Successful 
vif-bridge online for vif-win2k3, bridge eth0.
Jun 20 11:48:09 lic-srv-xen-02 logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/1/0/hotplug-status connected to xenstore.
Jun 20 11:48:10 lic-srv-xen-02 kernel: [57683.909332] tun: Universal TUN/TAP 
device driver, 1.6
Jun 20 11:48:10 lic-srv-xen-02 kernel: [57683.909335] tun: (C) 1999-2004 Max 
Krasnyansky <maxk@xxxxxxxxxxxx>
Jun 20 11:48:10 lic-srv-xen-02 kernel: [57683.923229] device tap-vif-win2k3 
entered promiscuous mode
Jun 20 11:48:10 lic-srv-xen-02 kernel: [57683.923254] eth0: port 
3(tap-vif-win2k3) entered forwarding state
Jun 20 11:48:10 lic-srv-xen-02 kernel: [57683.923257] eth0: port 
3(tap-vif-win2k3) entered forwarding state

Have anybody a idea what is here the problem?

Thank you very much

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users