VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1339 - 1341 of 16363)

Ticket Resolution Summary Owner Reporter
#17851 fixed VM fails to start with error VERR_LDRELF_RELOCATION_NOT_SUPPORTED when built on Debian unstable -> fixed after (not in) 5.2.14 radnaj
Description

In Debian Linux, after update to version 5.12.14 from version 5.12.12, the virtual machines fail to start due to an error "VERR_LDRELF_RELOCATION_NOT_SUPPORTED"

The Debian bug id is Bug#902897 (https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1613858.html), and has been reported by a few people.

Some VirtualBox Logs compiled from my box and posted by others can be seen attached

#17850 invalid A copy of VirtualBox is currently running Panos Kavalagios
Description

Update fails:

# dnf update                                                 
Last metadata expiration check: 0:01:03 ago on Τρι 03 Ιουλ 2018 09:42:09 πμ EEST.
Dependencies resolved.
================================================================================
 Package           Arch      Version                        Repository     Size
================================================================================
Upgrading:
 VirtualBox-5.2    x86_64    5.2.14_123301_fedora26-1       virtualbox     69 M

Transaction Summary
================================================================================
Upgrade  1 Package

Total download size: 69 M
Is this ok [y/N]: y
Downloading Packages:
VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64.  11 MB/s |  69 MB     00:06    
--------------------------------------------------------------------------------
Total                                            11 MB/s |  69 MB     00:06     
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                        1/1 
  Running scriptlet: VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64         1/2 
A copy of VirtualBox is currently running.  Please close it and try again.
Please note that it can take up to ten seconds for VirtualBox (in particular
the VBoxSVC daemon) to finish running.
error: %prein(VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64) scriptlet failed, exit status 1
Error in PREIN scriptlet in rpm package VirtualBox-5.2
Error in PREIN scriptlet in rpm package VirtualBox-5.2
VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64 was supposed to be installed but is not!
  Verifying        : VirtualBox-5.2-5.2.14_123301_fedora26-1.x86_64         1/2 
VirtualBox-5.2-5.2.12_122591_fedora26-1.x86_64 was supposed to be removed but is not!
  Verifying        : VirtualBox-5.2-5.2.12_122591_fedora26-1.x86_64         2/2 

Failed:
  VirtualBox-5.2.x86_64 5.2.14_123301_fedora26-1                                

Error: Transaction failed
#17841 invalid Virtualbox 5.2.12 causes massive swapping problems on kernel 4.16 and 4.15 Matthew Jurgens
Description

Recently I upgraded from virtualbox 5.2.6 to 5.2.12. From that point on, approximately every 3 days my system would lock up. I discovered that the system was doing huge amounts of swapping and the load average would go so high that the system was non-responsive.

My system has 16GB of RAM and normal load is around 5GB. Most of the rest of the RAM is allocated to cache. When the problem occurred the cache RAM was never released and so my system tried frantically to swap out everything running. Sometimes the OOM killer would be invoked. Once I left the system and it recovered back to normal by itself after about 4 hours. Most of the time I would reboot it using the Magic sys-alt keys as the kernel was still responsive. If I caught the problem early enough I could still use a terminal to run commands. Sometimes I would drop all caches - which worked sometimes but mostly it did not work and the system would still go crazy.

I tried kernel 4.15 and 4.16 which both behaved the same. The problem would always occur between the 3rd and 4th day since the last reboot. I reverted to virtualbox 5.2.6 on kernel 4.16 and now my system has been running for 7 days without issue.

It seems to me that there is something with virtualbox 5.2.12 where it perhaps locks RAM cache spaces and will not free it up (or allow the kernel to) when the system requires memory. I don't even know if that is technically possible, but that's what it looks like

Fedora 27 Host, 16GB RAM, Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz.

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