VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1375 - 1377 of 16363)

Ticket Resolution Summary Owner Reporter
#17764 invalid Fedora 28 guest -> invalid pepco
Description

Hi,

I'm not able to start Fedora 28 guest on Windows 10 host. In the past 2 weeks, some times it was working sometimes not. Not sure what is wrong

#17762 wontfix Virtualbox not supported on ARM addi
Description

Hi,

Please check Virtualbox is currently not supported on ARM. Kindly let me know if there is any supported planned in future and if any support is required for the same

#17759 fixed Kernel error messages (fixed in svn) Feline
Description

Both VirtualBox 5.2.10 and 5.2.12 produce the following error messages in the kernel log

kernel: [ 92.635587] AssertLogRel /home/vbox/vbox-5.2.12/src/VBox/VMM/VMMAll/PGMAllPhys.cpp(2345) VBOXSTRICTRC pgmPhysReadHandler(PVM, PPGMPAGE, RTGCPHYS, void*, size_t, PGMACCESSORIGIN): PGM_HANDLER_PHYS_IS_VALID_STATUS(rcStrict, false) kernel: [ 92.635592] rcStrict=2624 GCPhys=00000000f0804030

These are repeated hundreds of times over a five second period. They appear after the guest has started but not actually at initialisation of the virtual machine. Attached is kernel log showing the messages starting at 14:19:41 which was nineteen seconds after starting the virtual machine and once the desktop was displayed within the guest.

It happens on both a self-built machine (Asus motherboard) and a ThinkCentre M91p. Hosts on both machines are running Debian 9 with the 4.16.5 kernel from backports. Guests affected are both Windows 7 Professional (32 bit) and various Debian distros.

I've tried running the kernels with both KPI (Kernel Page Table Isolation) off and on with the same result. I have also switched off Large Page Tables within the VM guest config but still get the same error.

I have attached both the kernel log (edited to remove the vast majority of repeated error messages) and the VM guest release log. The release log includes the wall clock time so as to make it easier to match activity with the kernel log.

Problem did not occur with 5.2.8 and below.

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