将网络接口卡（NIC）添加到Compact 2013 Hyper V映像时出现问题 [英] Problem with adding a network interface card (NIC) to Compact 2013 Hyper V image
问题描述
Hello world：）
我添加了遗产虚拟机的网络驱动程序（如David Jones在他的博客条目中显示的
http://t.co/3HaeWtHt9y）。
启动虚拟机时，似乎网卡是已建立，但系统在显示"正在连接到桌面"后停止。有人有想法吗？ （请阅读附件日志了解更多
信息）
谢谢&问候
Microsoft Windows CE BIOS Bootloader版本2。2（2009年4月建成）
INFO：code = 0x4。
INFO：code = 0x4。
INFO：code = 0x4。
跳转到图像（地址= 0x227DA0）
Debug Serial Init
SysInit：GDTBase = 82ac0000 IDTBase = 82ac5b80 KData = 82a7d800
iB86的Windows CE内核
INFO：OALLogSetZones：dpCurSettings.ulZoneMask：0xb
SearchPciBios结束失败
InitKitlNIC：搜索PCI以太网网卡（dwIrq = 0，dwIoBase = 0，dwDfltType = 1）...
InitKitlNIC：找到PCI以太网NIC（类型= 3，IRQ = 11，IOBase = 0xEC00）。
在PCI总线上使用KITL设备，而不是传统设备。
DeviceId ................. CEPC
pArgs-> flags ............. 0x2D
pArgs-> devLoc.IfcType .... 5
pArgs-> devLoc.LogicalLoc.0xA00
pArgs-> devLoc.PhysicalLoc 0x0
pArgs-> devLoc.Pin ........ 11
pArgs-> ip4address ........ 0.0.0.0
pDevice->名称............ CEPC
pDevice-> ifcType ......... 5
pDevice-> id .............. 0x91011
pDevice-> resource ........ 0
pDevice-> type ............ 2
pDevice-> pDriver ......... 0x82A7F0A0
g_kitlLock = 0x82AA4900
DMA缓冲区[FFFFFFFF，FFFFFFFF]
NKCreateStaticMapping PA [2AAD000] UA [A0020D80,10000]偏移[D80]
DMA缓冲区[A0020D80] pa [2AADD80] UA => CA [82AADD80] CA => UA [A0020D80]
FindNICAbbrev：找不到NIC MAC的缩写：155D
x86KitlCreateName：使用设备名称'CEPC304'
OALKitlCreateName：使用设备名称'CEPC304'
KITL：***设备名称CEPC304 ***
KITL：使用sysintr 0x10
KITL将以中断模式运行
DHCP续订成功，IP = 192.168.178.42，租用时间= 432000秒
KITL：DHCP获取设备IP：192.168.178.42
VBridge ::建于[2019年2月21日]时间[14:37:53]
VBridgeInit（）... TX = [16384]字节 - Rx = [16384]字节
Tx缓冲区[0x82AA9D40]到[0x82AADD40]。
Rx缓冲区[0x82AA5D00]到[0x82AA9D00]。
VBridge :: NK add MAC：[0-15-5D-38-1-30]
连接到桌面
您好Esteban，
你确实需要从博客中设置遗产...
Integration Services
旧版网络适配器 用于Windows Embedded Compact 3013 vCEPC，以便它可以启动通过网络从开发系统接收操作系统nk.bin文件
上面的输出显示： ;
在PCI总线上使用KITL设备，而不是传统设备。
你能来吗？确认您在Hyper-V中使用的网卡是"Legacy"？
此致，
IoTGirl < /跨度>
Hello world :)
I added a legacy network driver to the virtual machine (like David Jones showed in his blog-entry http://t.co/3HaeWtHt9y).
When booting the virtual machine, it seems the NIC is founded but the system is stopping after display "Connecting to Desktop". Someone has a idea? (please read the attached log for more informations)
Thanks & Greetings
Microsoft Windows CE BIOS Bootloader Version 2.2 (Built Apr 7 2009)
INFO: code=0x4.
INFO: code=0x4.
INFO: code=0x4.
Jumping to image (address=0x227DA0)
Debug Serial Init
SysInit: GDTBase=82ac0000 IDTBase=82ac5b80 KData=82a7d800
Windows CE Kernel for i486
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
SearchPciBios end fails
InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = 0, dwIoBase = 0, dwDfltType = 1) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 3, IRQ=11, IOBase=0xEC00).
Using a KITL device on the PCI bus, not a legacy device.
DeviceId................. CEPC
pArgs->flags............. 0x2D
pArgs->devLoc.IfcType.... 5
pArgs->devLoc.LogicalLoc. 0xA00
pArgs->devLoc.PhysicalLoc 0x0
pArgs->devLoc.Pin........ 11
pArgs->ip4address........ 0.0.0.0
pDevice->Name............ CEPC
pDevice->ifcType......... 5
pDevice->id.............. 0x91011
pDevice->resource........ 0
pDevice->type............ 2
pDevice->pDriver......... 0x82A7F0A0
g_kitlLock = 0x82AA4900
DMA Buffer [FFFFFFFF, FFFFFFFF]
NKCreateStaticMapping PA[2AAD000] UA[A0020D80, 10000] offset[D80]
DMA Buffer [A0020D80] pa[2AADD80] UA=>CA[82AADD80] CA=>UA[A0020D80]
FindNICAbbrev: Can't find NIC Abbreviation for MAC: 155D
x86KitlCreateName: Using Device Name 'CEPC304'
OALKitlCreateName: Using Device Name 'CEPC304'
KITL: *** Device Name CEPC304 ***
KITL: using sysintr 0x10
KITL will run in interrupt mode
DHCP Renew successful, IP = 192.168.178.42, Lease time = 432000 seconds
KITL: DHCP get device IP: 192.168.178.42
VBridge:: built on [Feb 21 2019] time [14:37:53]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0x82AA9D40] to [0x82AADD40].
Rx buffer [0x82AA5D00] to [0x82AA9D00].
VBridge:: NK add MAC: [0-15-5D-38-1-30]
Connecting to Desktop
Hi Esteban,
You do need to set to legacy... from the blog:
Integration Services
A Legacy Network Adapter is used for Windows Embedded Compact 3013 vCEPC so that it can boot a receive an OS nk.bin file from a development system over the network
Your output above shows:
Using a KITL device on the PCI bus, not a legacy device.
Can you confirm the Network card you are using in Hyper-V is "Legacy"?
Sincerely,
IoTGirl
这篇关于将网络接口卡（NIC）添加到Compact 2013 Hyper V映像时出现问题的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
