完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
您好Jamesdblea,感谢您在英特尔有线以太网社区发帖。
您目前使用的是什么以太网适配器或控制器? 请发布输出oflspci | grep以太网; ethtool -i; andethtool -k。 如果您有任何其他问题,请不要犹豫。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for posting in Intel Wired Ethernet Communities. What Ethernet adapter or controller are you currently using? Please post the output of lspci | grep Ethernet; ethtool -i Best regards, Daniel D Intel Customer Support |
|
|
|
None 以上来自于谷歌翻译 以下为原文 Here is the last two examples I have. # lspci | grep Ethernet # lspci | grep Ethernet |
|
|
|
你好Jamesdblea,谢谢你的输出。 我们会调查此问题并尽快为您更新。 如果您有任何其他问题,请告诉我们。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for the outputs. We will investigate the issue and update you as soon as possible. Please let us know if you have any other questions. Best regards, Daniel D Intel Customer Support |
|
|
|
jerry1978 发表于 2018-10-24 06:54 您好Jamesdblea,感谢您在调查此问题时的耐心等待。 Libvirt在使用前为VF分配有效的MAC地址。 由于i40e驱动程序中的安全功能,分配给VM的VF不允许从VM中更改VF MAC地址。 重复的MAC将导致通信丢失。 使用以下命令从主机手动分配MAC地址:ip link set vf 0 mac aa:bb:cc:dd:ee:ff有关详细信息,请参阅SR-IOV配置指南的第15页。 请验证VF上的MAC地址是否重复。 如果您需要进一步的帮助,请提供创建VF所采取的步骤。 如果您有任何疑问,请告诉我们。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for your patience while we investigate this issue. Libvirt assigns a valid MAC address to the VF prior to use. Due to a security feature in the i40e driver the VF assigned to the VM is not allowed to change the VF MAC address from within the VM. A duplicate MAC will cause loss of communication. Manually assign a MAC address from the host using the following command: ip link set See page 15 of the SR-IOV configuration guide for more information. Please verify that the MAC address is not duplicated on the VF. Provide the steps you take to create the VFs if you need further assistance. If you have any questions please let us know. Best regards, Daniel D Intel Customer Support |
|
|
|
|
|
|
|
此僧唯一自传 发表于 2018-10-24 07:10 地狱丹尼尔, 这是从guest虚拟机发送的数据包的输出。 我还做了一个tcpdump来匹配任何与当前MAC不匹配的数据包。 有问题的客人是VF 7。 家长: #ip link show dev ethx 6:ethx:mtu 1500 qdisc mq master br0 state UP模式DEFAULT组默认qlen 1000 link / ether 90:e2:ba:0f:cb:90 brd ff:ff:ff:ff:ff:ff vf 0 MAC 52:54:00:f7:95:ed,欺骗检查,链接状态自动,信任,query_rss关闭 vf 1 MAC 52:54:00:30:1b:67,欺骗检查,链接状态自动,信任,query_rss关闭 vf 2 MAC 52:54:00:a7:7a:45,欺骗检查,链接状态自动,信任,query_rss关闭 vf 3 MAC 52:54:00:4a:d3:cb,欺骗检查,链接状态自动,信任,查询_关闭 vf 4 MAC 52:54:00:c8:9e:57,欺骗检查,链接状态自动,信任,query_rss关闭 vf 5 MAC 52:54:00:17:44:c3,欺骗检查,链接状态自动,信任,query_rss关闭 vf 6 MAC 52:54:00:45:b3:61,欺骗检查,链接状态自动,信任,query_rss关闭 vf 7 MAC 52:54:00:fa:f7:dc,欺骗检查,链接状态自动,信任,query_rss关闭 儿童: #ip link show dev eth0 2:eth0:mtu 1500 qdisc mq master bond0 state UP模式DEFAULT组默认qlen 1000 link / ether 52:54:00:fa:f7:dc brd ff:ff:ff:ff:ff:ff #ip link show dev bond0 3:bond0:mtu 1500 qdisc noqueue state UP模式DEFAULT组默认qlen 1000 link / ether 52:54:00:fa:f7:dc brd ff:ff:ff:ff:ff:ff #tcpdump -i eth0 -Q out not ether host 52:54:00:fa:f7:dc tcpdump:详细输出被抑制,使用-v或-vv进行完整协议解码 监听eth0,链接类型EN10MB(以太网),捕获大小262144字节 捕获0个数据包 过滤器收到5837个数据包 内核丢弃4331个数据包 #tcpdump -i bond0 -Q out not ether host 52:54:00:fa:f7:dc tcpdump:详细输出被抑制,使用-v或-vv进行完整协议解码 监听bond0,链接型EN10MB(以太网),捕获大小262144字节 捕获0个数据包 过滤器收到2480个数据包 内核丢弃了595个数据包 以上来自于谷歌翻译 以下为原文 Hell Daniel, Here is the output for packets being sent from the guest. I've also done a tcpdump to match any packets exiting that don't match the current MAC. Guest with the issue is VF 7. Parent: # ip link show dev ethx Child: # ip link show dev eth0 |
|
|
|
你好Jamesdblea,谢谢你的输出。 我们会进一步调查此问题,并尽快回复您。 如果您有任何其他问题,请随时与我们联系。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for the outputs. We will investigate the issue further, and get back to you soon. If you have any other questions please do not hesitate to contact us. Best regards, Daniel D Intel Customer Support |
|
|
|
jerry1978 发表于 2018-10-24 07:54 您好Jamesdblea,感谢您等我们调查此问题。 您是否尝试将孩子更改为VF7以外的VF并查看问题是否仍然发生在另一个VF上? 您能否为我们提供您使用的一些配置? 特别是QEMU和KVM设置,以及以太网接口的配置。 我们还注意到bond0已设置,但是它用于什么? 如果您有任何问题,请告诉我们。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for waiting while we investigate this issue. Have you tried to change the child to a VF other than VF7 and see if the issue still occurs on another VF? Would you be able to provide us some of the configurations you used. Specifically QEMU and KVM settings, and configurations for the Ethernet interfaces. We also notice bond0 is set, but what is it being used for? Let us know if you have any questions. Best regards, Daniel D Intel Customer Support |
|
|
|
jerry1978 发表于 2018-10-24 08:03 丹尼尔你好, 这次使用的实际VF是7,下次它将是另一个,接下来是另一个。 我正在解决这个问题,这个问题突然出现在几十台服务器上。 VF#没有相关性。 Bond在少数情况下使用,其中客人是带有保税网络的父母,SRIOV是从两个网络到客人。 这种情况只有一个网络连接; 债券没有两个支持。 无论是否有债券,这种错误都会发生。 以下是我们用于直通的一些配置,如果您需要更具体的一些,请告诉我。 客人通过libvirt: QEMU流程: qemu 31168 246 12.7 8947996 8404636? SL10 Oct04 4024:19 / usr / libexec / qemu-kvm -name GUESTNAME -S -machine pc-i440fx-rhel7.0.0,accel = kvm,u*** = off,dump-guest-core = off -cpu IvyBridge,+ ds, + ACPI,+ SS,+ HT,+ TM,+ PBE,+ dtes64,+监视器,+ ds_cpl,+ VMX,+ SMX,+ EST,+ TM2,+ xtpr,+ PDCM,+ PCID,+ DCA,+ osxsave ,+ arat,+ xsaveopt,+ pdpe1gb,-spec-ctrl -m 8192 -realtime mlock = off -smp 4,sockets = 4,cores = 1,threads = 1 -uuid fc9c3820-a1ab-4cab-8671-717d4e2560c0 -display none -no-user-config -nodefaults -chardev socket,id = charmonitor,path = / var / lib / libvirt / qemu / domain-29-GUESTNAME / monitor.sock,server,nowait -mon chardev = charmonitor,id = monitor ,mode = control -rtc base = utc,driftfix = slew -global kvm-pit.lost_tick_policy = delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3 = 1 -global PIIX4_PM.disable_s4 = 1 -boot strict = on - 设备ich9-u***-ehci1,id = u***,bus = pci.0,addr = 0x3.0x7 -device ich9-u***-uhci1,masterbus = u***.0,firstport = 0,bus = pci.0,multifunction = on, addr = 0x3 -device ich9-u***-uhci2,masterbus = u***.0,firstport = 2,bus = pci.0,addr = 0x3.0x1 -device ich9-u***-uhci3,masterbus = u***.0 ,firstport = 4,bus = pci.0,addr = 0x3.0x2 -device ahci,id = sata0,bus = pci.0,addr = 0x4 -drive file = / imgs / GUESTNAME / guest.disk0,format = raw, if = none,id = drive-sata0-0-0,discard = unmap -device ide-hd,bus = sata0.0,drive = drive-sata0-0-0,id = sata0-0-0,bootindex = 1 -chardev pty,id = charserial0 -device isa-serial,chardev = charserial0,id = serial0 -device vfio-pci,host = 05:11.2,id = hostdev0,bus = pci.0,addr = 0x6 -device virtio-balloon -pci,id = balloon0,bus = pci.0,addr = 0x5 -msg timestamp = on 以上来自于谷歌翻译 以下为原文 Hello Daniel, The actual VF used this time was 7, next time it'll be another, next another. I'm troubleshooting this issue popping up on more than several dozen servers. No correlation on VF#. Bond is used in a few cases where guests are on parents with a bonded network and SRIOV from two nics to the guest. This case there is only one network connection; bond isn't backed up by two. Again this error can happen with or without bond. Here is some configs we use for passthrough, if you need some more specific, please let me know. Guest passthrough libvirt: QEMU process: qemu 31168 246 12.7 8947996 8404636 ? SLl Oct04 4024:19 /usr/libexec/qemu-kvm -name GUESTNAME -S -machine pc-i440fx-rhel7.0.0,accel=kvm,u***=off,dump-guest-core=off -cpu IvyBridge,+ds,+acpi,+ss,+ht,+tm,+pbe,+dtes64,+monitor,+ds_cpl,+vmx,+smx,+est,+tm2,+xtpr,+pdcm,+pcid,+dca,+osxsave,+arat,+xsaveopt,+pdpe1gb,-spec-ctrl -m 8192 -realtime mlock=off -smp 4,sockets=4,cores=1,threads=1 -uuid fc9c3820-a1ab-4cab-8671-717d4e2560c0 -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-29-GUESTNAME/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-u***-ehci1,id=u***,bus=pci.0,addr=0x3.0x7 -device ich9-u***-uhci1,masterbus=u***.0,firstport=0,bus=pci.0,multifunction=on,addr=0x3 -device ich9-u***-uhci2,masterbus=u***.0,firstport=2,bus=pci.0,addr=0x3.0x1 -device ich9-u***-uhci3,masterbus=u***.0,firstport=4,bus=pci.0,addr=0x3.0x2 -device ahci,id=sata0,bus=pci.0,addr=0x4 -drive file=/imgs/GUESTNAME/guest.disk0,format=raw,if=none,id=drive-sata0-0-0,discard=unmap -device ide-hd,bus=sata0.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device vfio-pci,host=05:11.2,id=hostdev0,bus=pci.0,addr=0x6 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 -msg timestamp=on |
|
|
|
你好Jamesdblea,谢谢你的回复。 我们将考虑Libvirt和QEMU配置。 会很快给你更新。 如果您有任何问题,请告诉我们。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for the reply. We will take the Libvirt and QEMU configurations into consideration. Will update you soon. Let us know if you have any questions. Best regards, Daniel D Intel Customer Support |
|
|
|
你好Jamesdblea,谢谢你的耐心等待。 在运行CentOS 7.5(父)和Ubuntu 15(子)的计算机上使用82599 2端口以太网控制器,我们无法复制该问题。 我们按照SR-IOV配置指南中的步骤操作,并在端口0上启用了2x VF。没有帧被丢弃到另一个主机或父节点到子节点。 您的配置中是否存在偏离指南的内容? 如果您有任何问题,请告诉我们。最好的问候,Daniel DIntel客户支持 以上来自于谷歌翻译 以下为原文 Hello Jamesdblea, Thank you for your patience. Using an 82599 2 port Ethernet controller on a machine running CentOS 7.5 (Parent) and Ubuntu 15 (Child) we could not duplicate the issue. We followed the steps in SR-IOV configuration Guide and enabled 2x VF on port 0. No frames were dropped child to another host or parent to child. Is there something in your configuration that deviates from the guide? Let us know if you have any questions. Best regards, Daniel D Intel Customer Support |
|
|
|
只有小组成员才能发言,加入小组>>
482浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-12-1 01:41 , Processed in 1.068028 second(s), Total 100, Slave 83 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号