VirtualBox

Changes between Initial Version and Version 15 of Ticket #9371


Ignore:
Timestamp:
08/10/11 07:25:42 (3 years ago)
Author:
frank
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9371 – Description

    initial v15  
    22 
    33Environment: 
    4 • VirtualBox 4.1.0 r73009 win.x86 
    5  Host OS Windows 7 Release: 6.1.7600 
    6  Guest OS Linux 2.6.24 
     4 * !VirtualBox 4.1.0 !r73009 win.x86 
     5 * Host OS Windows 7 Release: 6.1.7600 
     6 * Guest OS Linux 2.6.24 
    77 
    88Problem: 
    9 • All traffic from the guest OS(10.0.3.101) to the VirtualBox NAT interface (10.0.3.2) fails after a duration of time. 
    10 • Initially all traffic functions correctly, after approximately 15-20 min the guest OS is unable to contact the VirtualBox NAT interface. No ping to virtualBox or anything else on the NAT interface of the guest. The guest is configured for two adapters. adapter 1 is a Host only network that continues to function normally when adapter 2 fails. 
     9 * All traffic from the guest OS(10.0.3.101) to the !VirtualBox NAT interface (10.0.3.2) fails after a duration of time. 
     10 * Initially all traffic functions correctly, after approximately 15-20 min the guest OS is unable to contact the !VirtualBox NAT interface. No ping to !VirtualBox or anything else on the NAT interface of the guest. The guest is configured for two adapters. adapter 1 is a Host only network that continues to function normally when adapter 2 fails. 
    1111 
    1212Attempted Resolutions: 
    13 • I am able to restore traffic while the guest is running by changing the interface type to something other than NAT, and then reverting back to a NAT interface. This only leads to recreating the NAT failure again. 
    14 • Restarting the guest also recreates the failure. 
    15 • I tried changing the adapter driver types with no success. 
    16 • Down grading to VirtualBox 3.1.6 r59338 is the only solution that provides continuous NAT connectivity. 
    17  
    18 Noted several " PCNet#1: Init: ss32=1 GCRDRA=0x37553000[32] GCTDRA=0x37df4000[16]" lines the log file 
     13 * I am able to restore traffic while the guest is running by changing the interface type to something other than NAT, and then reverting back to a NAT interface. This only leads to recreating the NAT failure again. 
     14 * Restarting the guest also recreates the failure. 
     15 * I tried changing the adapter driver types with no success. 
     16 * Down grading to !VirtualBox 3.1.6 !r59338 is the only solution that provides continuous NAT connectivity. 

www.oracle.com
ContactPrivacy policyTerms of Use