Depends on how you configured your "interface." The following command
should display its details

brctl show vig10

You should also describe how you created your interface...
When you configure virtual networks (for your virtual networking) you
should not configure and assign physical interfaces for your Guests.
You should instead create Linux Bridge Devices as virtual devices
which can be assigned to a physical interface.
A variety of tools can be used to create Linux Bridge Devices
including YAST, libvirt (vm manager), brctl, virsh, even GUI managers
from other virtualization technologies like VMware, VBox, etc because
once a LBD has been created in any way, the LBD can be used by any
Guest using any virtualization, and any number of Guests.

And, if you're using LBD the name is irrelevant.
If you're configuring a real, physical interface then like practically
any other use of a real, physical device the device most likely can be
used by only one OS (Guest, Host, whatever).

Tony

On Tue, Feb 3, 2015 at 2:41 AM, Per Jessen <[email protected]> wrote:
> Per Jessen wrote:
>
>> My xen host is openSUSE 13.2.
>>
>> I have one guest running currently. I created a second guest to
>> install 13.2 and ran "xl create".
>>
>> This appears to have brought down the interface (vif10) for the
>> existing guest ??
>>
>> 9: vif10: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast state DOWN
>> group default qlen 512
>>     link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
>>
>
> I'm not certain but this seems to be related to me having chosen "vif10"
> and "vif11" as the interface names.  On a second try, when I omitted
> the interface name for the new guest, the new interface was
> named "vif11.0" and did not interfere with vif10.
>
>
>
> --
> Per Jessen, Zürich (-0.1°C)
> http://www.dns24.ch/ - your free DNS host, made in Switzerland.
>
> --
> To unsubscribe, e-mail: [email protected]
> To contact the owner, e-mail: [email protected]
>
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to