4.1b2 issue with Host-only interface

Postings relating to old VirtualBox pre-releases

4.1b2 issue with Host-only interface

Postby bqbauer » 9. Jul 2011, 00:24

Just upgraded my Solaris Express host from beta1 to beta2, and now all guests with host interface networking return the error:

Failed to open a session for the virtual machine XP-Pro.
Failed to open/create the internal network 'HostInterfaceNetworking-e1000g0 - Intel PRO/1000 Gigabit Ethernet' (VERR_INTNET_FLT_IF_FAILED).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_FAILED).

Same results with a Debian guest. Log attached.
Attachments
VBoxSVC.log
(7.83 KiB) Downloaded 13 times
Last edited by bqbauer on 9. Jul 2011, 01:06, edited 1 time in total.
bqbauer
 
Posts: 151
Joined: 14. Dec 2008, 22:04

Re: 4.1b2 issue with Host-only interface

Postby bqbauer » 9. Jul 2011, 00:40

Even if I delete the affected interface or change it to another type (like NAT or Bridged), I get the same error. Can't boot the VMs at all. Not a problem on my Windows 7 64-bit host.

Just in case, I rebooted my Solaris host, which was never necessary before. No change.
Last edited by bqbauer on 9. Jul 2011, 01:06, edited 1 time in total.
bqbauer
 
Posts: 151
Joined: 14. Dec 2008, 22:04

Re: 4.1b2 issue with Host-only interface

Postby bqbauer » 9. Jul 2011, 01:05

It seems deleting the interface in the VM doesn't help because I have/had snapshots or differencing disks associated with each of these VMs. The one I cannot correct has a differencing disk associated with it, but no related snapshots. How can I merge them or replace the original file with the differencing file if VB doesn't see a related snapshot? I'm betting the original has something embedded in it about the host-only adapter, because the Debian VM that had one works now that I deleted the snapshot associated with it AND removed the affected interface.

That was a mouthful. Problem is: The VM has a differencing image, but no snapshots; how can I merge them?

Real problem: Why does beta2 not like the host-only adapter when beta1 did?
bqbauer
 
Posts: 151
Joined: 14. Dec 2008, 22:04

Re: 4.1b2 issue with Host-only interface

Postby bqbauer » 13. Jul 2011, 03:07

Unfortunately, I have to go back to beta1 due to this bug. It's a show stopper for me since I can't boot a VM with a differencing disk even after deleting the host-only interface.
bqbauer
 
Posts: 151
Joined: 14. Dec 2008, 22:04

Re: 4.1b2 issue with Host-only interface

Postby frank » 14. Jul 2011, 12:18

Please attach the correct log file, it is named VBox.log and can be found in the Logs directory of the machine.
frank
Oracle Corporation
 
Posts: 3363
Joined: 7. Jun 2007, 09:11
Location: Dresden, Germany
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows

Re: 4.1b2 issue with Host-only interface

Postby Ramshankar » 14. Jul 2011, 13:39

Is this vboxnet interface present in ifconfig -a output after a reboot? Are you using NWAM on the host? If so try and do an "ifconfig vboxnet0 plumb up" after a reboot in case it's not present due to NWAM interfering with it.

Also, you are mentioning e1000g but referring to host-only networking. So I'm not sure if it's really host-only issue or a bridged networking issue you're having though host-only internally uses the bridged network driver as well.
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 778
Joined: 7. Jan 2008, 16:17

Re: 4.1b2 issue with Host-only interface

Postby bqbauer » 14. Jul 2011, 19:48

Yes it's present in ifconfig -a (on the host). No, NWAM is not in use. It is most definitely the host-only interface that is the problem. The e1000g is the virtual interface type presented to the guest.

Sorry about the log. Will post a new one.
bqbauer
 
Posts: 151
Joined: 14. Dec 2008, 22:04

Re: 4.1b2 issue with Host-only interface

Postby renato.morano » 15. Jul 2011, 12:33

I have the same problem, but only if the host network device is up and running

e1000g0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 10
inet 192.168.1.244 netmask ffffff00 broadcast 192.168.1.255
ether 0:23:7d:fd:b8:f

Failed to open/create the internal network 'HostInterfaceNetworking-e1000g0 - Intel PRO/1000 Gigabit Ethernet' (VERR_INTNET_FLT_IF_FAILED).
Failed to attach the network LUN (VERR_INTNET_FLT_IF_FAILED).

If I try to start the vm with cable unlpugged there are no error then when the cable is plugged the guest is up running and network ok

Jul 15 12:19:31 marte in.ndpd[1430]: [ID 169330 daemon.error] Interface e1000g0 has been removed from kernel. in.ndpd will no longer use it
Jul 15 12:20:28 marte vboxdrv: [ID 715304 kern.notice] vboxflt:vboxNetFltSolarisAttachIp4: Warning: seems 'e1000g0' is unplumbed.
Jul 15 12:21:37 marte mac: [ID 435574 kern.info] NOTICE: e1000g0 link up, 1000 Mbps, full duplex

VBox:4.1.b3
host: SunOS marte 5.11 snv_151a i86pc i386 i86pc Solaris
guest: All
svcs: online 8:48:41 svc:/network/physical:nwam
renato.morano
 
Posts: 4
Joined: 23. Dec 2009, 10:12
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: Linux windows

Re: 4.1b2 issue with Host-only interface

Postby mpack » 15. Jul 2011, 13:38

XP Pro host here, V4.1b3, no problem with host only networking. No interference with the working host NIC either.

In the past, this sort of problem has often been caused by inappropriate attempts to use the host OS's network bridge feature to connect the host-only virtual NIC to the physical host NIC. That's on Windows hosts. I'm not a Solaris user and don't know if the same thing can happen there.
mpack
Site Moderator
 
Posts: 27706
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

Re: 4.1b2 issue with Host-only interface

Postby renato.morano » 15. Jul 2011, 16:16

i suggest some type trouble to nwam and VBoxSVC process

Jul 15 16:10:05 marte vboxdrv: [ID 251337 kern.notice] vboxflt:vboxNetFltSolarisOpenDev failed. pUser=ffffff01e6c29360 fp=ffffff01e7452e98 f_vnode=0000000000000000
Jul 15 16:10:05 marte vboxdrv: [ID 969834 kern.notice] vboxflt:vboxNetFltSolarisAttachIp4: failed to open UDP. rc=-103
Jul 15 16:10:05 marte vboxdrv: [ID 709899 kern.notice] vboxflt:vboxNetFltSolarisAttachToInterface failed. rc=-3602
renato.morano
 
Posts: 4
Joined: 23. Dec 2009, 10:12
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: Linux windows

Re: 4.1b2 issue with Host-only interface

Postby Ramshankar » 15. Jul 2011, 17:54

renato.morano wrote:i suggest some type trouble to nwam and VBoxSVC process

Jul 15 16:10:05 marte vboxdrv: [ID 251337 kern.notice] vboxflt:vboxNetFltSolarisOpenDev failed. pUser=ffffff01e6c29360 fp=ffffff01e7452e98 f_vnode=0000000000000000
Jul 15 16:10:05 marte vboxdrv: [ID 969834 kern.notice] vboxflt:vboxNetFltSolarisAttachIp4: failed to open UDP. rc=-103
Jul 15 16:10:05 marte vboxdrv: [ID 709899 kern.notice] vboxflt:vboxNetFltSolarisAttachToInterface failed. rc=-3602


I was afraid of that... but didn't see it coming till earlier today.

The problem is our trunk building was moved to an internal S11 build which changes certain offsets into the kernel structures that then fails when run on Solaris 10 and Solaris 11 Express builds. I fixed this only today and thus BETA 3 does not have it. VirtualBox 4.1 final should have a better overall solution that detects this at runtime.

Thanks for the reports!
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 778
Joined: 7. Jan 2008, 16:17

Re: 4.1b2 issue with Host-only interface

Postby gstrasser » 15. Jul 2011, 18:10

any chance for us B151 users to get a Beta 3.1 including this fix ?

regards
gstrasser
 
Posts: 5
Joined: 28. Sep 2010, 08:56
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: W2K8

Re: 4.1b2 issue with Host-only interface

Postby Ramshankar » 15. Jul 2011, 18:22

gstrasser wrote:any chance for us B151 users to get a Beta 3.1 including this fix ?

regards


Hmm, I will try upload a custom build if 4.1 final is far away.
Oracle Corp.
Ramshankar
Oracle Corporation
 
Posts: 778
Joined: 7. Jan 2008, 16:17

Re: 4.1b2 issue with Host-only interface

Postby ci4ic4 » 18. Jul 2011, 14:12

"Me also" reply - same with 4.1b3 under OpenIndiana build 148.:

Jul 18 10:58:07 uksup4 vboxdrv: [ID 303284 kern.notice] vboxflt:vboxNetFltSolarisOpenDev failed. pUser=ffffff02fb361be0 fp=ffffff02fb223090 f_vnode=0000000000000000
Jul 18 10:58:07 uksup4 vboxdrv: [ID 969834 kern.notice] vboxflt:vboxNetFltSolarisAttachIp4: failed to open UDP. rc=-103
Jul 18 10:58:07 uksup4 vboxdrv: [ID 709899 kern.notice] vboxflt:vboxNetFltSolarisAttachToInterface failed. rc=-3602

4.0.12 is fine.

Chavdar Ivanov
ci4ic4
 
Posts: 18
Joined: 16. Jun 2009, 12:55
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris

Re: 4.1b2 issue with Host-only interface

Postby ci4ic4 » 18. Jul 2011, 14:13

ci4ic4 wrote:"Me also" reply - same with 4.1b3 under OpenIndiana build 148.:

Jul 18 10:58:07 uksup4 vboxdrv: [ID 303284 kern.notice] vboxflt:vboxNetFltSolarisOpenDev failed. pUser=ffffff02fb361be0 fp=ffffff02fb223090 f_vnode=0000000000000000
Jul 18 10:58:07 uksup4 vboxdrv: [ID 969834 kern.notice] vboxflt:vboxNetFltSolarisAttachIp4: failed to open UDP. rc=-103
Jul 18 10:58:07 uksup4 vboxdrv: [ID 709899 kern.notice] vboxflt:vboxNetFltSolarisAttachToInterface failed. rc=-3602
....

Actually this was with bridged i/f , not host-only, if that is of any significance.
....


4.0.12 is fine.

Chavdar Ivanov
ci4ic4
 
Posts: 18
Joined: 16. Jun 2009, 12:55
Primary OS: OpenSolaris 11
VBox Version: PUEL
Guest OSses: Windows Server 2008 R2, Windows 7, OpenSolaris

Next

Return to Old Beta Postings

Who is online

Users browsing this forum: No registered users and 1 guest