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

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

Hi, Ewan,
        Thanks for suggestion. However nothing changed after pull your Rev 7651 
in. I still see following message:
        " Device 0 (vif) could not be connected. Hotplug scripts not working"

        However actually the hotplug works on my target system. You can see 
from following xenstore info that vbd backend has been connected successfully:

   backend = ""
    vbd = ""
     1 = ""
      769 = ""
       domain = "ExampleDomain3"
       params = "loop0"
       frontend-id = "1"
       type = "phy"
       dev = "hda1"
       frontend = "/local/domain/1/device/vbd/769"
       physical-device = "0x0700"
       node = "/dev/loop0"
       hotplug-status = "connected"     <<<<<<<
   error = ""
    backend = ""
     vbd = ""
      1 = ""
       769 = ""
        error = "2 reading /local/domain/1/device/vbd/769/ring-ref and 
event-channel"
^^^^(That error comes from that blkback watch handler tried to read before domU 
is started)
    vif = ""
   device-misc = ""
    vif = ""
     nextDeviceID = "1"

        However, since netfront/netback hasn't been ported to IA64 now, it 
always caused failure here after timout connecting to vif backend node.      
I'll try to add a hack to prevent connecting to vif backend and see whether 
forward progress. If you have simple way to do test, please help me. ;-)
        
        By the way, the loopback driver is also not compiled into xen0/xenU 
currently for XEN/IA64. Is there similar case to check vif0.0 for dom0 after 
above point? That would make another failure obviously due to same reason. In 
current stage, we only promise vbd working on IA64.

Thanks,
Kevin
>-----Original Message-----
>From: Ewan Mellor [mailto:ewan@xxxxxxxxxxxxx]
>Sent: 2005年11月8日 21:41
>To: Tian, Kevin
>Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-devel] Is it possible to disable vif completely?
>
>On Tue, Nov 08, 2005 at 09:13:45PM +0800, Tian, Kevin wrote:
>
>> 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?
>
>There is a bug here that is fixed in 7651.  You ought to be on that changeset
>at the least.  A lot of ia64 patches went in today, so you probably want to
>look at those too.
>
>Ewan.

xsls
Description: xsls

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