WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-API] [Xen-Users] eth0 on hvm is not up on xen 4.0.1

so my config 

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'
Vcpus=2
memory = 2048
shadow_memory = 8
name = "sourcewindows"
vif = [ 'type=ioemu, mac=aa:00:b0:00:00:11, bridge=eth0' ]
disk = [ 'file:/mnt/data/xen/disks/sourcewindows.img,hda,w',
'phy:/dev/cdrom,hdc:cdrom,r' ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
boot="dc"
sdl=0
vnc=1
vncconsole=1
vncpasswd=''

logs
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/768
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/2/5632
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/vif-bridge: online
type_if=vif XENBUS_PATH=backend/vif/2/0
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/768/node /dev/loop0 to xenstore.
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/768/physical-device 7:0 to xenstore.
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.087779] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=108)
nodename:backend/vbd/2/768
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.087782] (cdrom_is_type()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95)
type:0
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/768/hotplug-status connected to xenstore.
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.097269] device vif2.0 entered
promiscuous mode
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.098960] eth0: port 2(vif2.0)
entering forwarding state
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif2.0, bridge eth0.
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/2/0/hotplug-status connected to xenstore.
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/5632/physical-device b:0 to xenstore.
Jun  7 19:06:10 vitalinkmain logger: /etc/xen/scripts/block: Writing
backend/vbd/2/5632/hotplug-status connected to xenstore.
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.158821] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=108)
nodename:backend/vbd/2/5632
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.158824] (cdrom_is_type()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95)
type:3
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.158826] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=110) is
a cdrom
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.159418] (cdrom_add_media_watch()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=112)
xenstore wrote OK
Jun  7 19:06:10 vitalinkmain kernel: [ 1429.159537] (cdrom_is_type()
file=/usr/src/linux-2.6.34-xen-r4/drivers/xen/blkback/cdrom.c, line=95)
type:3
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/console/2/0
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vfb/2/0
Jun  7 19:06:11 vitalinkmain kernel: [ 1429.506828] eth0: port 2(vif2.0)
entering disabled state
Jun  7 19:06:11 vitalinkmain kernel: [ 1429.509229] eth0: port 2(vif2.0)
entering disabled state
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/2/768
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/2/5632
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: offline
type_if=vif XENBUS_PATH=backend/vif/2/0
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/2/5632
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: brctl
delif eth0 vif2.0 failed
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/2/768
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: ifconfig
vif2.0 down failed
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge offline for vif2.0, bridge eth0.
Jun  7 19:06:11 vitalinkmain logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/2/0

any idea ?


--
View this message in context: 
http://xen.1045712.n5.nabble.com/eth0-on-hvm-is-not-up-on-xen-4-0-1-tp3390658p4462131.html
Sent from the Xen - User mailing list archive at Nabble.com.

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

<Prev in Thread] Current Thread [Next in Thread>