From: Stephen Hemminger <stephen@networkplumber.org>
To: Chas Williams <3chas3@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Should netvsc and Debian 10 work?
Date: Tue, 30 Apr 2019 09:51:01 -0700 [thread overview]
Message-ID: <20190430095101.120c2449@hermes.lan> (raw)
In-Reply-To: <0e02ab92-aa2d-e4f8-923e-4f0748d8b670@gmail.com>
On Tue, 30 Apr 2019 10:58:36 -0400
Chas Williams <3chas3@gmail.com> wrote:
> I am trying to get netvsc to work with Debian 10. Following along in the
> instructions I have:
>
> # cat setup
> modprobe uio_hv_generic
> echo -n 57b2866a-61b8-400e-ac8f-32373f9c42a3 >
> /sys/bus/vmbus/drivers/uio_hv_generic/new_id
> echo -n 57b2866a-61b8-400e-ac8f-32373f9c42a3 >
> /sys/bus/vmbus/drivers/hv_netvsc/unbind
> echo -n 57b2866a-61b8-400e-ac8f-32373f9c42a3 >
> /sys/bus/vmbus/drivers/uio_hv_generic/bind
>
> But this fails during the bind stage with "No such device":
>
> setup: line 4: echo: write error: No such device
>
> The kernel in Debian 10 is
>
> Linux debian10 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15)
> x86_64 GNU/Linux
>
> This is a generation 1 virtual machine.
You have the wrong GUID.
The first step (writing new_id) needs the GUID used to as device type
for all nework devices. The second/third step bind/unbind need the GUID
of the ethernet device in question.
I use this script:
#! /bin/bash
if [ $# -lt 1 ]; then
echo "Usage: $0 ethN"
exit 1
fi
# Setup UIO
NET_UUID="f8615163-df3e-46c5-913f-f2d2f965ed0e"
modprobe uio_hv_generic || exit 1
echo $NET_UUID > /sys/bus/vmbus/drivers/uio_hv_generic/new_id
for ETH
do
if [ ! -h /sys/class/net/$ETH/device ]; then
echo "$ETH/device does not exist"
exit 1
fi
DEV_UUID=$(basename $(readlink /sys/class/net/$ETH/device))
echo $ETH is $DEV_UUID
echo $DEV_UUID > /sys/bus/vmbus/drivers/hv_netvsc/unbind
echo $DEV_UUID > /sys/bus/vmbus/drivers/uio_hv_generic/bind
done
prev parent reply other threads:[~2019-04-30 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 14:58 Chas Williams
2019-04-30 16:51 ` Stephen Hemminger [this message]
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=20190430095101.120c2449@hermes.lan \
--to=stephen@networkplumber.org \
--cc=3chas3@gmail.com \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).