Windows Network Adapter Language

Discussions related to using VirtualBox on Windows hosts.
Post Reply
bratwurst
Posts: 1
Joined: 8. Jun 2012, 22:34

Windows Network Adapter Language

Post by bratwurst »

Hello,

I'm trying to configure Virtualbox to run a VM as service with srvany. Everything works fine but I have a major problem with national language settings. I'm running a Windows 2008 r2 server (english version) with german localization. So my user account is set to german. When I define a virtual machine I can select a bridged network adapter called "Intel(R) 82574L-Gigabit-Netzwerkverbindung". The machine can be started interactively and everything works fine. The setting is reflected in the XML file too:

<BridgedInterface name="Intel(R) 82574L-Gigabit-Netzwerkverbindung"/>

When I start the machine as a service with srvany (vboxmanage.exe startvm <vm> --type headless) as system account all of a sudden the network adapter is no longer recognized. The vbox.log gives the error message:

00:00:00.477 VMSetError: Nonexistent host networking interface, name 'Intel(R) 82574L-Gigabit-Netzwerkverbindung'

Playing around with different settings all nails down to german/english adapter names. If I modify the XML file and rename the adapter to "... network connection" the service starts with network support. But afterwards I cannot start the VM interactively. Addtionally the name is reverted back to german when I edit the VM properties.

Applying the tips from Microsoft Windows infopage ...Apply-regional-and-language-settings-to-reserved-accounts... to change the system account language to german I hoped everything will work fine again. But it does not solve my problem still interface name mismatch between the two modes.

Does anyone else experience this error and has found some workaround. Or should I open a ticket?

Bratwurst
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Windows Network Adapter Language

Post by mpack »

I'm not convinced there is a VirtualBox bug to open a ticket about. It sounds like it's the OS returning a different string for different user profiles. Obviously device names for host devices do not originate within VirtualBox.
waterytowers
Posts: 2
Joined: 24. Mar 2008, 08:50

Re: Windows Network Adapter Language

Post by waterytowers »

I am having a problem with what I think is the same network card and Virtual Box 4.0.

Intel(R) 82574L Gigabit Network Connection

It can be configured within VirtualBox but when I go to run the VM interactively it complains :

'HostInterfaceNetworking-Intel(R) 82574L Gigabit Network Connection'
(VERR_INTNET_FLT_IF_NOT_FOUND)


This may be a problem with the OS? Is there anything I can check to help verify it is not a problem with Virtual Box?

Windows is quite happy to use the network card, only Virtual Box seems to not like the card.

Any help would be appreciated.

Thanks
Dave
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Windows Network Adapter Language

Post by mpack »

Reinstall VirtualBox to get rid of that one. Make sure you run the installer with elevated priveleges "Run as administrator", and don't leave out any bits of the installation.

Incidentally, your question is not related to the OPs. The OP was missing a named device. Your error message is about a missing driver.
waterytowers
Posts: 2
Joined: 24. Mar 2008, 08:50

Re: Windows Network Adapter Language

Post by waterytowers »

It appears as though my problem is something within Windows.

A standard image is being installed onto what is expected to be known hardware. However, the hardware is not as expected. Windows detects a card that is different to what it actually is, and VirtualBox is unable to use the card at all. Windows is able to limp along using the incorrectly detected driver, but VirtualBox fails completely. I am guessing that since VirtualBox has Linux roots, it requires things to be strictly correct for things to work, however, WIndows is very forgiving so is able to limp forward.

Re-installed the latest Intel drivers and re-installed VirtualBox and everything started working again. Had to re-install VirtualBox for it to work, installing Intel drivers was not enough.
Post Reply