[BitVisor-devel:68] Re: device addition(BCM5720) and cannot link-up (like as PRO/1000)

Hideki EIRAKU hdk @ igel.co.jp
2015年 12月 4日 (金) 15:44:08 JST


Hi,

From: Hideki EIRAKU <hdk @ igel.co.jp>
Subject: Re: [BitVisor-devel:64] device addition(BCM5720) and cannot link-up (like as PRO/1000)
Date: Wed, 02 Dec 2015 10:34:25 +0900 (JST)

>> By "ip" command, the NIC state are printed as UNKNOWN.
> 
> I can reproduce the behavior.  If the driver is working properly, the
> state is still UNKNOWN but the guest operating system can communicate
> via the interface.  I will investigate the cause of the problem.

The NIC state UNKNOWN is correct.  The current virtio-net device
implementation in BitVisor does not support the VIRTIO_NET_F_STATUS
feature.  Therefore the virtio-net driver in the guest operating
system cannot get link-up/down status from the device.

If the bnx driver in BitVisor is enabled, the Broadcom Gigabit
Ethernet Driver in the EFI/UEFI firmware must be unloaded before
starting the BitVisor.  The firmware driver may conflict with the
BitVisor driver and the confliction causes unexpected behavior like
below:

- System hang up during BitVisor initialization.
- The NIC device stops working when ExitBootServices() is called.

To unload the firmware driver, please use EFI shell commands "drivers"
and "unload".

-- 
Hideki EIRAKU <hdk @ igel.co.jp>


BitVisor-devel メーリングリストの案内