Hi,
I'm now blocked for 2 days on getting the network to work in my domU. Here is
the problem :
The domU refuses to start when a vif is configured. It's just staying paused
for about
1m40s, then the xm create command line give back with an
"Error: Device 0 (vif) could not be connected. Hotplug scripts not working.",
and the domU is destroyed.
Nothing particular in the xend.log, xend-debug.log or qemu-dm-domUname.log.
However, if I manually unpause the domU, and cancel (<CTRL><C>) the xm create
command to avoid the destruction of the domU after the 1m40s timeout, I get a
perfectly working domU with Network. Strangely, the vif network interfaces are
now named tap[domUid].[interface#] (ie tap2.0).
So, my questions :
- Why is there no clear log about vif-bridge script, and how can I debug this
script.
- Why are the interfaces named tapX.X instead of vifX.X ?
- Is there a default name for the bridge interface ? I'm currently using
xenbr0, but I see that some documentations are talking about eth0, should I
use eth0 as default bridge name
?
Thanks,
François.
My config :
root@UbuntuTST-Blade:~# xm info
host : UbuntuTST-Blade
release : 2.6.31-rc3
version : #8 SMP Mon Jul 20 15:01:16 CEST 2009
machine : x86_64
nr_cpus : 16
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 2
cpu_mhz : 2400
hw_caps :
bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000
virt_caps
: hvm
total_memory : 36853
free_memory : 1043
node_to_cpu : node0:0-15
node_to_memory : node0:1043
xen_major : 3
xen_minor : 4
xen_extra : .1-rc7
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 : Wed Jul 15 13:26:50 2009 +0100
19696:22ef8e900a6d
cc_compiler : gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
cc_compile_by : root
cc_compile_domain : local.modernprocessing.lu
cc_compile_date : Thu Jul 16 21:46:26 CEST 2009
xend_config_format : 4
root@UbuntuTST-Blade:~#
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-users
