Custom Query (16363 matches)
Results (1453 - 1455 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17505 | worksforme | kernel 4.14.15 and vboxconfig | ||
| Description |
Hi, vboxconfig fails with new kernel 4.14.15 Message is: T470 kernel: vboxdrv: version magic '4.14.15-300.fc27.x86_64 SMP mod_unload ' should be '4.14.15-300.fc27.x86_64 SMP mod_unload retpoline ' No problem with previous kernel 4.14.14 |
|||
| #17502 | duplicate | Windows 98 cannot boot w/ HardwareVirtEx enabled if host is an AMD Ryzen | ||
| Description |
I just upgraded off of an Intel Ivy Bridge system to an AMD Ryzen 7 1700X, and am reloading my VM images one-by-one. When restoring my Windows 98 guest used for testing NetWare stuff, I found that it would refuse to boot, stating "Windows protection error. You need to restart your computer." Turning off settings one-by-one, I worked out that the "HardwareVirtEx" setting ('Enable VT-x/AMD-V' in the GUI) is the cause. Turning that off, along w/ "Nested Paging", allows Windows 98 to boot. So it is possibly an issue with AMD-V and this really old OS. CPU has microcode 08001129 loaded, as well, in case that matters, given how new Ryzen CPUs are. Motherboard is an Asus PRIME X370-Pro running the latest BIOS (3402). Also, the guest will boot into safe mode, so it might be one of the drivers causing the problem. I tried doing a step-by-step load, but the last driver to load was "msmouse", and given that the mouse will work under safe mode, I doubt it's that one. I'll attach a VBox.log file if that helps any. |
|||
| #17498 | duplicate | 5.2.6 Seamless issue Debian Host (Windows 7 32bit guest) | ||
| Description |
On my test machine I have Debian 9.3, Kernel 4.9, Virtualbox 5.2.6. The Windows 7 virtual machine is working nicely, BUT when I enter Seamless mode, the video inside the VM window is not updated. I click and type and don't see things happening. When I try to move the VM window, I'm mostly unsuccessful. I thought that this might be the video driver in use on the host so I replaced the open one with the Nvidia driver, but it had no effect. Another user says that they had the same issue and reverted to 5.2.0 which resolved the issue. The thread is here https://forums.virtualbox.org/viewtopic.php?f=7&t=86447 I am working on my test machine and would be happy to use alpha code to test the issue. (i.e. I will not cry if my virtual environment gets borked) |
|||

