networkmanager starts second "wired connection" when virtualbox starts

On my system, network manager connects well to the LAN in all sorts of ways, wired, wireless, utms. But when virtualbox starts, it “senses” the virtual network and begins to configure it as a second wired connection, eventually messing up network mounts and maybe other things.

I can manually go in and disconnect the second wired network, and then remount some of my network drives, but this should clearly not be necessary, should it?

Sorry, forgot to mention that this is a laptop, and I am running opensuse 13.2 with qt5, plasma5 and the 3.16.6-2-desktop kernel.

just curious what type of network did you use for your VM’s? as I read but never tried it a host only adapter would make the VM’s part of the internal network and maybe you might see an extra ‘wired connection’. I will try to play around this and see what happens.

When you run virtualization on your machine, it’s normal for a variety of virtual networks to be configured in addition to your physical network. In fact, even without a Guest running, if you inspect your HostOS networking configuration, you should see your virtual network interfaces <already configured>, just not actively used to connect to another machine (until you fire up a Guest).

To inspect your HostOS networking configuration,

ifconfig

or

ip addr

After inspecting the results of the above and considering the various physical networks you connect to, you <do> need to ensure each network address space(both physical and virtual) is unique, not overlapping or same. If you have problems resolving this, post to the Virtualization forum including the virtualization technology and management application you’re using.

TSU

Thank you, but none of this is my question, nor my problem. Virtualbox sets those networks up, transparently, and they have worked nicely for me for years.

But since opensuse 13.2, the network manager somehow grabs them and creates a mess. Essentially, it considers some of the virtualbox networks a “wired connection” and tries to do something with it. A consequence of this is that perfectly mounted nfs shares suddenly get disconnected - presumably because the main PHYSICAL wired connection somehow is cut, at least temporarily.

Again, none of these problems existed before the upgrade, and I wonder why they needed to be introduced…

On 11/22/2014 10:56 AM, wolfgangcr wrote:
>
> tsu2;2677898 Wrote:
>> When you run virtualization on your machine, it’s normal for a variety
>> of virtual networks to be configured in addition to your physical
>> network. In fact, even without a Guest running, if you inspect your
>> HostOS networking configuration, you should see your virtual network
>> interfaces <already configured>, just not actively used to connect to
>> another machine (until you fire up a Guest).
>>
>> To inspect your HostOS networking configuration,
>>>
> Code:
> --------------------
> > > ifconfig
> --------------------
>>>
>> or
>>>
> Code:
> --------------------
> > > ip addr
> --------------------
>>>
>>
>> After inspecting the results of the above and considering the various
>> physical networks you connect to, you <do> need to ensure each network
>> address space(both physical and virtual) is unique, not overlapping or
>> same. If you have problems resolving this, post to the Virtualization
>> forum including the virtualization technology and management
>> application you’re using.
>>
>> TSU
>
> Thank you, but none of this is my question, nor my problem. Virtualbox
> sets those networks up, transparently, and they have worked nicely for
> me for years.
>
> But since opensuse 13.2, the network manager somehow grabs them and
> creates a mess. Essentially, it considers some of the virtualbox
> networks a “wired connection” and tries to do something with it. A
> consequence of this is that perfectly mounted nfs shares suddenly get
> disconnected - presumably because the main PHYSICAL wired connection
> somehow is cut, at least temporarily.
>
> Again, none of these problems existed before the upgrade, and I wonder
> why they needed to be introduced…
>
>

I’ve always used a bridged adapter in the guest and never had a problem.

Ken