VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (511 - 513 of 16363)

Ticket Resolution Summary Owner Reporter
#20016 worksforme Problems with Windows Guest Additions on Win 10 64bit - VM crashes after Installation Goodwin
Description

After Windows Guest Additions are installed, the Windows 10 Guest (Running on Debian Buster with backports) freezes to black screen, also after longer time the state is unchanged. After the forced shutdown after new restart the VM then crashes. I had this issue also with the VirtualBox 6.1.10, seems to be related to some Debian library update. The only help is to reboot the VM, hold F8 to start Windows emergency menu, then activate the safe mode and in safe mode to deinstall the Virtual Guest additions. Then the Guest runs OK again, unfortunatelly with all drawbacks of the Windows Guest without Guest Additions, so especially with resolution 1024x708. See the Guest after the freeze with session information opened on screenshot in attached screenshot in file

#20009 duplicate MSS unexpected increase by VirtualBox Johan Mazel
Description

I setup Debian Buster64 guest OS using the VirtualBox provider in Vagrant on a Debian Testing. My VirtualBox version is 6.1.14_Debian r140239.

According to my tests, the MSS set in the SYN packet of the TCP handshake that leaves the host is the host's MTU, and not the guest's MTU. This happens even if the latter is set lower than the host MTU.

I run the following tests: 1) Guest and host default MTU

  • Settings:
    • Guest eth0 MTU: 1500
    • Host eth0 MTU: 1500
  • Network traffic capture results:
    • Guest eth0 SYN MSS: 1460
    • Host eth0 SYN MSS: 1460

2) Guest and host modified MTU

  • Settings:
    • Guest eth0 MTU: 1400
    • Host eth0 MTU: 1400
  • Network traffic capture results:
    • Guest eth0 SYN MSS: 1360
    • Host eth0 SYN MSS: 1360

3) Guest modified MTU and host default MTU

  • Settings:
    • Guest eth0 MTU: 1400
    • Host eth0 MTU: 1500
  • Network traffic capture results:
    • Guest eth0 SYN MSS: 1360
    • Host eth0 SYN MSS: 1460

4) Guest default MTU and host modified MTU

  • Settings:
    • Guest eth0 MTU: 1500
    • Host eth0 MTU: 1400
  • Network traffic capture results:
    • Guest eth0 SYN MSS: 1460
    • Host eth0 SYN MSS: 1360

For both tests 1 and 2, MTU and MSS are the same and there is no ambiguity to solve. So the observed behavior is the expected one. The MSS clamping behavior for test 4 is expected because the host cannot provide the MSS that the guest expects. I however think that the behavior of test 3 is incorrect because it increases the packet size received by the guest which may cause problems on the guest itself or in a virtualized network.

This problem seems to be related to: #15256.

#20006 fixed 6.1.16 guest additions does not build on a linux 3.2.0 kernel => fixed in svn/6.1.x x>16 BP ThatsEnough
Description

The vboxguest kernel module does not build on a 3.2.0 kernel because kmalloc_array did not appear until kernel 3.2.51 whereas the test in memobj-r0drv-linux.c tests for a 3.2.0 or higher kernel.

Thus the line (line no 60):

#if RTLNX_VER_MIN(3,2,0)
defined(DOXYGEN_RUNNING)

should be changed to

#if RTLNX_VER_MIN(3,2,51)
defined(DOXYGEN_RUNNING)
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy