From: "Glaza, Jan" <jan.glaza@intel.com>
To: Faicker Mo <faicker.mo@zenlayer.com>
Cc: "intel-wired-lan@osuosl.org" <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [EXTERNAL] Re: [bug report]iavf: deadlock on detach/attach vf to VM with net_failover
Date: Fri, 13 Sep 2024 16:50:34 +0200 [thread overview]
Message-ID: <ef41438c-b311-4922-a6bb-3073f69bfa96@intel.com> (raw)
In-Reply-To: <SJ0PR20MB60797AE7B7293BB912545B37FA962@SJ0PR20MB6079.namprd20.prod.outlook.com>
We were unable to reproduce it using the following configuration and steps:
HOST:
PF Intel Corporation Ethernet Controller X710 for 10GbE SFP+ [8086:1572]
OS: Ubuntu 22.04.4 LTS 6.11.0-061100rc4-generic
FW firmware-version: 9.50 0x8000f177 1.3597.0
PF version: 6.11.0-061100rc4-generic
VM:
PF Intel Corporation Ethernet Virtual Function 700 Series [8086:154c]
OS: Ubuntu 22.04.2 LTS 6.11.0-061100rc4-generic
PF version: 6.11.0-061100rc4-generic
Steps:
1. Spawn 1 VF
2. Use script in order to get xml of the vf, it should spawn in /tmp/temp_vf_config/
#!/bin/bash
temp_dir="/tmp/temp_vf_config"
if [ -z "$temp_dir" ];
then
echo "temp_dir variable is empty, aborting to avoid destroying filesystem"
exit 1
else
rm -rf $temp_dir/*
mkdir -p $temp_dir >/dev/null 2>&1
fi
for VF in $(lspci | grep -i "virtual function" | cut -f 1 -d \ );
do
busid=$(echo $VF | cut -f 1 -d \:);
slotid=$(echo $VF | cut -f 2 -d \: | cut -f 1 -d \.);
functionid=$(echo $VF | cut -f 2 -d \: | cut -f 2 -d \.);
echo "BUS: $busid, SLOT: $slotid, FUNCTION: $functionid"
echo -e "<hostdev mode='subsystem' type='pci' managed='yes'>\n<source>\n<address domain='0x0000' bus='0x$busid' slot='0x$slotid' function='0x$functionid'/>\n</source>\n</hostdev>" > $temp_dir/$busid-$slotid-$functionid
done
3. Create VM
4. Attach VF to VM while VM is disabled, then enable VM
5. Hot detach VF
6. Hot attach VF
Expected result:
VF detaches and attaches successfully
Actual result:
VF does not detach/attach at all.
Possible to set down/up VF when it's detached.
No error in dmesg, actually nothing appear in dmesg.
We had to replace the XML file provided as it would not produce a working configuration. Can you advise us on any setup inconsistencies or changes that would be required to reproduce it?
Best regards,
Jan
next prev parent reply other threads:[~2024-09-13 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 3:19 [Intel-wired-lan] [bug report]iavf: deadlock on detach/attach vf to VM with net_failover Faicker Mo
2024-08-28 11:48 ` Glaza, Jan
2024-08-29 3:27 ` [Intel-wired-lan] [EXTERNAL] " Faicker Mo
2024-09-13 14:50 ` Glaza, Jan [this message]
2024-09-18 3:43 ` [Intel-wired-lan] [EXTERNAL] " Faicker Mo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef41438c-b311-4922-a6bb-3073f69bfa96@intel.com \
--to=jan.glaza@intel.com \
--cc=faicker.mo@zenlayer.com \
--cc=intel-wired-lan@osuosl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox