 
	
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] SuSE 10.1 and Windows XP guest
 
I have installed SuSE 10.1 Xen and try to install Windows XP.
xm create myxm.hvm   brings up three lines (only):
   Using config file "myxm.hvm"
   Started domain Windows_XP
/var/lib/xen/images/windisk.img was created with seek=8192k
myxm.hvm:
import os, re
arch = os.uname()[4]
if re.search('64', arch):
   arch_libdir = 'lib64'
else:
   arch_libdir = 'lib'
kernel = "/usr/lib/xen/boot/hvmloader"
builder='hvm'
memory = 512
name = "Windows_XP"
vif = [ 'type=ioemu, bridge=xenbr0' ]
disk = [ 'file:/var/lib/xen/images/windisk.img,ioemu:hda,w' ]
on_poweroff = 'destroy'
on_reboot   = 'destroy'
on_crash    = 'destroy'
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
cdrom='/dev/cdrom'
boot='d'
sdl=1
vnc=0
vncviewer=0
stdvga=0
serial='pty'
ne2000=0
the log file shows:
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: online 
XENBUS_PATH=backend/vif/1/0
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/1/768
Jun  6 15:13:16 CS-Ronald-VT ifup: Service network not started and mode 'auto' 
-> skipping
Jun  6 15:13:16 CS-Ronald-VT kernel: tun: Universal TUN/TAP device driver, 1.6
Jun  6 15:13:16 CS-Ronald-VT kernel: tun: (C) 1999-2004 Max Krasnyansky 
<maxk@xxxxxxxxxxxx>
Jun  6 15:13:16 CS-Ronald-VT kernel: device tun0 entered promiscuous mode
Jun  6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(tun0) entering disabled 
state
Jun  6 15:13:16 CS-Ronald-VT kernel: device tun0 left promiscuous mode
Jun  6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(tun0) entering disabled 
state
Jun  6 15:13:16 CS-Ronald-VT kernel: device vif1.0 entered promiscuous mode
Jun  6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering learning 
state
Jun  6 15:13:16 CS-Ronald-VT kernel: xenbr0: topology change detected, 
propagating
Jun  6 15:13:16 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering forwarding 
state
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing 
backend/vbd/1/768/node /dev/loop0 to xenstore.
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing 
backend/vbd/1/768/physical-device 7:0 to xenstore.
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/block: Writing 
backend/vbd/1/768/hotplug-status connected to xenstore.
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Successful 
vif-bridge online for vif1.0, bridge xenbr0.
Jun  6 15:13:16 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Writing 
backend/vif/1/0/hotplug-status connected to xenstore.
Jun  6 15:13:17 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering disabled 
state
Jun  6 15:13:17 CS-Ronald-VT kernel: device vif1.0 left promiscuous mode
Jun  6 15:13:17 CS-Ronald-VT kernel: xenbr0: port 1(vif1.0) entering disabled 
state
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: offline 
XENBUS_PATH=backend/vif/1/0
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/block: remove 
XENBUS_PATH=backend/vbd/1/768
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: brctl delif 
xenbr0 vif1.0 failed
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: ifconfig 
vif1.0 down failed
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/vif-bridge: Successful 
vif-bridge offline for vif1.0, bridge xenbr0.
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/xen-hotplug-cleanup: 
XENBUS_PATH=backend/vif/1/0
Jun  6 15:13:17 CS-Ronald-VT ifdown:     vif1.0    
Jun  6 15:13:17 CS-Ronald-VT logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/1/768Jun 6 15:13:17 CS-Ronald-VT ifdown: Interface not available and no configuration found. What do I miss? bye Ronald _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users 
 
 | 
|  | Lists.xenproject.org is hosted with RackSpace, monitoring our |