RE: [Xen-devel] Is it possible to disable vif completely?

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

Ooops, I also saw "Device (vbd) could not be connected" warning. So seems that 
this issue can't be bypassed. After looking in the list, seems that some people 
are claiming udevd is a must now, is that right? (Anything more?) If yes, why 
is there no check upon udevd when installing tools, like for brctrl, etc? I 
think it's better to check whether all required tools installed before running 
xend/xm...

Thanks,
Kevin

>-----Original Message-----
>From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tian, Kevin
>Sent: 2005年11月8日 21:14
>To: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: [Xen-devel] Is it possible to disable vif completely?
>
>Now I'm enabling multiple domain support on IA64 (Once again, though
>working one month ago). The issue what I'm seeing now is:
>       "xm create -c" doesn't return with error in createDevices() and
>thus all subsequent xm commands don't return.
>
>My work based on xen-ia64-unstable identical to Rev 7646 on
>xen-unstable.hg ("Fix pagetable pinning logic for xen/i386 kernels.").
>However xend/xm works well two weeks ago identical to Rev 7483 on
>xen-unstable ("Added a timestamp to the logging output by trace_io").
>
>After killing above thread and check /var/log/xend.log, which warns
>"Device (vif) could not be connected. Hotplug scripts not working".
>What's the necessary environmental setting to support said hotplug
>scripts? Any special requirement happens between these two weeks?
>
>Actually I saw that "xm create -c" thread pending on select() when
>createDevices() and seems the issue coming from synchronization issue
>between main thread and device controller thread. Current the vnif
>backend/frontend doesn't work for ia64 yet, so is there easy way to
>disable vnif setup completely, thus to let us bypass this issue now?
>Then we can focus on vbd stuff first...
>
>Thanks,
>Kevin
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel

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