Sometimes, after domU user reboots it, vif interface for that
domU is then not brought back. I must then manually bring back the
interface with ifconfig viftest0 up. This happens only sometimes.
Everything looks fine in domU itself. After I bring up the vif
manually, networking starts working fine for that domU.
Any ideas? Where can I start debugging this?
Centos 5.2
host : xy.net
release : 2.6.18-92.1.13.el5xen
version : #1 SMP Wed Sep 24 20:01:15 EDT 2008
machine : x86_64
nr_cpus : 8
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2500
hw_caps :
bfebfbff:20100800:00000000:00000140:000ce3bd:00000000:00000001
total_memory : 16382
free_memory : 6421
node_to_cpu : node0:0-7
xen_major : 3
xen_minor : 2
xen_extra : .2
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : unavailable
cc_compiler : gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)
cc_compile_by : root
cc_compile_domain : xy.net
cc_compile_date : Thu Oct 23 17:17:23 CEST 2008
xend_config_format : 4
kernel = ''/boot/xen-vmlinuz''
ramdisk = ''/boot/xen-initrd.img''
memory = 1024
name = ''zzz.vm''
vif = [''ip=w.x.y.z, vifname=viftest0, mac=aa:00:d5:0b:94:01
'']
vnc = 0
vcpus = 1
vncviewer = 0
serial = ''pty''
disk = [''phy:/dev/VGSAS/test_rootimg,sda1,w'',
''phy:/dev/VGSAS/test_vmswap,sda2,w'']
Thanks!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users