[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v2 13/15] net: Remove obsolete vlan info

From: Jan Kiszka
Subject: Re: [Qemu-devel] [PATCH v2 13/15] net: Remove obsolete vlan info
Date: Thu, 24 May 2012 11:31:56 -0300
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv: Gecko/20080226 SUSE/ Thunderbird/ Mnenhy/

On 2012-05-24 11:27, Zhi Yong Wu wrote:
> On Thu, May 24, 2012 at 10:25 PM, Jan Kiszka <address@hidden> wrote:
>> Something mangled your reply and made it unreadable. Please retry.
> Sorry. let it look like below. Do you think of it? typ=hubport
> (qemu) info network
>   virtio-net-pci.0: type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:56
>    \ hub0port0: type=hubport,
>   virtio-net-pci.1: type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:57
>    \ hub1port0: type=hubport,
>   virtio-net-pci.2: type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:58
>    \ u: type=user,net=,restrict=off
>   e1000.0: type=nic,model=e1000,macaddr=52:54:00:12:34:59
>    \ ur: type=user,net=,restrict=off
> hub 1
>     port 1 peer user.1
>     port 0 peer virtio-net-pci.1
> hub 0
>     port 1 peer user.0
>     port 0 peer virtio-net-pci.0

My question remains: What added value we get from listing the hubs with
its ports separately from the port connections? Also, how would this be

    -net user -net dump -net nic

The user should only be interested in the fact that user.0, dump.0 and
<some_nic>.0 are attached to the same hub, not to which port of that hub.


Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

reply via email to

[Prev in Thread] Current Thread [Next in Thread]