VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1258 - 1260 of 16363)

Ticket Resolution Summary Owner Reporter
#17091 obsolete USB Keyboard inoperative after Device menu selected from mini toolbar Feline
Description

Both my Windows and Linux guests run fullscreen and I have the mini toolbar set at the bottom of the screen.

If I select the Devices menu from the mini toolbar the keyboard becomes inoperative to the guest currently running. To re-create, open a terminal window in the guest and then hover over the mini toolbar to get it to display. Select the Devices drop-down (you don't actually need to select anything like USB or Insert GA). Now try and type something into the guests terminal window and nothing happens.

If you use the mouse the minimise the Guest window and select the guest again from the hosts status bar then the keyboard works again within the guest.

System Details: Host - Debian 9 with Mate desktop and 4.12.6 kernel from Stretch backports.

Guests - Windows 7 Professional 32-bit with all up-to-date service.

Mint Debian Edition 2 (Jessie based) with Mate desktop - happens with both 32-bit and 64-bit flavours.

Both keyboard and mouse are attached via a KVM device.

A very similar problem has been reported on the user forum : https://forums.virtualbox.org/viewtopic.php?f=7&t=84591

#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.

#19674 fixed VirtIO-SCSI controller fails to see disk Feline
Description

I appreciate that the VirtIO-SCSI support is currently experimental but I have been doing some testing of it. It works fine with my Debian guests, both for attaching data volumes and to boot from.

However, when using Windows 10, I cannot get any disks that are attached to the controller to be seen inside the Windows 10 guest. I have installed the RedHat drivers for Windows from the Fedora site, both the current stable version and the latest build but they both exhibit the same behaviour.

The controller shows up in Device Manager but the disk attached to it does not show in either Device Manager or Disk Management. The Event log seems to show an error when it attempts to start the device but I may have misread the entry.

My Host is Debian 10.4 running VirtualBox 6.1.10. The guest is Windows 10 (Update 2004, OS Build 19041.329) The virtio-scsi drivers are the current stable version - 100.77.104.17100

I have attached the guests machine log and .vbox file. Furthermore, I have attached prints of the Storage Controller and Disks section from Device manager, which show the drive details and the controller information within the Windows 10 guest. I have also attached the guest Event Log entries for the controller.

If there are any other troubleshooting procedures I can take, please ask.

Thank you.

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