qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: ~vlaomao <vlaomao@gmail.com>
Cc: qemu-trivial@nongnu.org, QEMU Developers <qemu-devel@nongnu.org>,
	Dmitry Fleytman <dmitry.fleytman@gmail.com>,
	Jason Wang <jasowang@redhat.com>
Subject: Re: [PATCH qemu 0/1] MAC address falls to permanent
Date: Mon, 30 Jan 2023 19:09:01 +0100	[thread overview]
Message-ID: <2cc505db-517e-4129-9c9a-7a41637b75f2@vivier.eu> (raw)
In-Reply-To: <167510125533.6740.18222174398575558338-0@git.sr.ht>

CC: maintainers and qemu-devel

Use ./scripts/get_maintainer.pl to have the list of the maintainers.

Always send your patches to qemu-devel&nongnu.org

Thanks,
Laurent

Le 30/01/2023 à 18:54, ~vlaomao a écrit :
> A bug was found with the vmxnet3 driver, after changing the MAC address
> and rebooting, it falls into the category of a permanent address until
> the VM is turned off. Here is log output:
> 
> -bash-4.4# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
>      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>      inet 127.0.0.1/8 scope host lo
>         valid_lft forever preferred_lft forever
> 2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
>      link/ether 52:54:00:12:34:56 brd ff:ff:ff:ff:ff:ff
> 
> -bash-4.4# ip link set dev ens3 address 33:33:33:33:33:33
> -bash-4.4# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
>      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>      inet 127.0.0.1/8 scope host lo
>         valid_lft forever preferred_lft forever
> 2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
>      link/ether 33:33:33:33:33:33 brd ff:ff:ff:ff:ff:ff
> -bash-4.4# ethtool -P ens3
> Permanent address: 52:54:00:12:34:56
> -bash-4.4# reboot
> 
> //rebooting
> 
> 
> -bash-4.4# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
>      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>      inet 127.0.0.1/8 scope host lo
>         valid_lft forever preferred_lft forever
> 2: ens3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group
> default qlen 1000
>      link/ether 33:33:33:33:33:33 brd ff:ff:ff:ff:ff:ff
> -bash-4.4# ethtool -P ens3
> Permanent address: 33:33:33:33:33:33
> -bash-4.4#
> 
> VlaoMao (1):
>    vmxnet3: add mac address restore upon reset
> 
>   hw/net/vmxnet3.c | 2 ++
>   1 file changed, 2 insertions(+)
> 



       reply	other threads:[~2023-01-30 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167510125533.6740.18222174398575558338-0@git.sr.ht>
2023-01-30 18:09 ` Laurent Vivier [this message]
2023-01-31 18:20 [PATCH qemu 0/1] MAC address falls to permanent Vlao Mao
2023-01-31 18:48 ` Peter Maydell
2023-01-31 19:08   ` Влад Мао
  -- strict thread matches above, loose matches on Subject: below --
2023-01-31 18:23 Vlao Mao

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=2cc505db-517e-4129-9c9a-7a41637b75f2@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=dmitry.fleytman@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=vlaomao@gmail.com \
    /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).