search for: bcc1

Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I

...48.101 - 001b.906a.bcc4 ARPA Vlan48 Internet 192.168.48.1 0 0025.6440.063f ARPA Vlan48 Internet 192.168.2.52 0 0025.6440.0547 ARPA Vlan2 Internet 192.168.3.1 - 001b.906a.bcc2 ARPA Vlan3 Internet 192.168.2.1 - 001b.906a.bcc1 ARPA Vlan2 Internet 192.168.7.1 - 001b.906a.bcc3 ARPA Vlan7 hq# The network config on the machine currently looks like this: it has nothing assigned to eth0, eth0.48 = 192.168.48.100/24, eth0.49 = 192.168.49.100/24, eth0.50 = 192.168.50.100/24. And - even though the ARP table...

...001b.906a.bcc4 ARPA Vlan48 > Internet 192.168.48.1 0 0025.6440.063f ARPA Vlan48 > Internet 192.168.2.52 0 0025.6440.0547 ARPA Vlan2 > Internet 192.168.3.1 - 001b.906a.bcc2 ARPA Vlan3 > Internet 192.168.2.1 - 001b.906a.bcc1 ARPA Vlan2 > Internet 192.168.7.1 - 001b.906a.bcc3 ARPA Vlan7 > hq# > > The network config on the machine currently looks like this: it has > nothing assigned to eth0, eth0.48 = 192.168.48.100/24, eth0.49 = > 192.168.49.100/24, eth0.50 = 192.168.50.100/24. &gt...

On 25 January 2015 at 15:12, Boris Epstein <borepstein at gmail.com> wrote: > OK... but why does it need to be a trunk port? > Because a trunk port will "trunk" the vlan. A VLAN is basically a 4 byte "tag" that gets injected into the packet header when the packet enters the VLAN network. When we trunk a VLAN we say to the switch "pass packets on VLAN x but

...ARPA Vlan48 >> Internet 192.168.48.1 0 0025.6440.063f ARPA Vlan48 >> Internet 192.168.2.52 0 0025.6440.0547 ARPA Vlan2 >> Internet 192.168.3.1 - 001b.906a.bcc2 ARPA Vlan3 >> Internet 192.168.2.1 - 001b.906a.bcc1 ARPA Vlan2 >> Internet 192.168.7.1 - 001b.906a.bcc3 ARPA Vlan7 >> hq# >> >> The network config on the machine currently looks like this: it has >> nothing assigned to eth0, eth0.48 = 192.168.48.100/24, eth0.49 = >> 192.168.49.100/24, eth0.50...