VirtualBox

Changes between Version 1 and Version 2 of Ticket #11483, comment 4


Ignore:
Timestamp:
Apr 1, 2013 10:35:26 PM (11 years ago)
Author:
nik.markovic

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #11483, comment 4

    v1 v2  
    11We get the same exact error with VBox 4.1.24 on our system. It is an AMD Opeteron 6176 (48 cores) with 256 GB of RAM, of which over 200GB are free and not cached.
    2 
    3 Here's the output of top (added spaces for clarity)
    4 Mem:  264 532 288k total, 25 882 364k used, 238 649 924k free,   216 464k buffers
    52
    63If we launch a machine with 8 cores and 32 GB RAM, it fails
    … …  
    107If we launch a machine with 8 cores and 24 GB RAM, it succeeds
    118
    12 Note: 8 * 32 = 256. Could that be the bug? It's trying to calculate free RAM based on allocating requested RAM to each CPU?
     9Edit: Did some more tests and concluded that there are just some odd combinations of CPU and RAM that fail:
     10
     1116 CPU, 24000 MB RAM - success
     12
     131 CPU, 110000 MB RAM - success
     14
     152 CPU, 110000 MB RAM - success
     16
     174 CPU, 110000 MB RAM - success
     18
     198 CPU, 110000 MB RAM - success
     20
     218 CPU 32000 MB RAM - success
     22
     238 CPU 34000 MB RAM - fail
     24
     258 CPU 36000 MB RAM - fail
     26
     278 CPU 38000 MB RAM - success (?)
     28
     2916 CPU 34000 MB RAM - success (?)
     30
     3116 CPU 36000 MB RAM - success (?)
     32
     338 CPU 40000 MB RAM - success
     34
     354 CPU 67000 MB RAM - success
     36
     378 CPU 67000 GB RAM - success
     38
     398 CPU 110000 GB RAM - success
     40
     4116 CPU 110000 GB RAM - success

© 2023 Oracle
Contact – Privacy policy – Terms of Use