VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (325 - 327 of 16363)

Ticket Resolution Summary Owner Reporter
#20623 duplicate Call to NEMR0InitVMPart2 failed haraldb
Description

Call to NEMR0InitVMPart2 failed: VERR_NEM_INIT_FAILED (VERR_NEM_VM_CREATE_FAILED).

Fehlercode: E_FAIL (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

After upgrading from VB 6.1.26 to 6.1.28 starting any of my Linux guests terminates with the above message. Environment (Host): Windows 10 Pro, Version 21H1 (Build 19043.1288)

After downgrading back to VB 6.1.26 all guests start and run again without any problem ...

#20621 fixed Hyper-V doesn't work on AMD Ryzen 3800x for old VM vbicf
Description

Hi,

I have some old Windows 10 VM (VT-X) that was created when Hyper-V was not enabled in the host. After I enable Hyper-V, that old VM will not start and it will get a bluescreen. Is there a way to fix that old VM machine so that it will start with Hyper-V enabled in the host. I changed the settings in VirtualBox to use Hyper-V Paravirtualization but the blue screen happens again. See here:

If I create a VM from scratch with Hyper-V enabled in the host, the VM will boot fine.

This means something in the old VM is causing the crash. I don't want to reinstall it from scratch.

System: Ryzen 3800X

The version of VirtualBox: 6.1.26

Host: Windows 10 21H1, Guest: Windows 10 20H2

When the VM was created: VT-x/AMD-V enabled, HyperV disabled

installed Guest Additions and Host Extensions

I have another system Intel 7700k, on that system with the same VM I can start that old VM when Hyper-V is enabled!

This looks like and AMD specific issue.

I am attaching the log from my amd system when I get the blue screen.

#20615 fixed cliboard between guest linux and host Windows 10 does not work any more after recent Windows Update. => Fixed in SVN ci-zephyurus
Description

I am using VirtualBox 6.1.26 r145957 under Windows 10. My Windows 10 was updated recently and it is now (after the latest update)

Edition Windows 10 Pro Version 21H1 Installed ‎2020/‎12/‎16

OS build 19043.1288

I run Debian GNU/Linux inside virtualbox. It is Linux ip030 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64 GNU/Linux

What happened is this. Before the latest Windows Update to bring the version of Windows 10 to 21H1 (I think),

  • clipboard between the guest linux and host windows 10 worked fine.

After the Windows Update. copy&paste from linux to Windows 10: the target windows application that was supposed to receive the copied string gets hung for maybe a minute or so. (sandclock appears and even windows resize does not work during that time. Bsically the application gets hung.) After that, it came back, but no pasting occurs.

Copy&paste from Windows to linux, the copied string on the windows 10 side is not recognized in the linux application. No pasting happens from the window side. Previously selected string WITHIN linux, i.e., X11 clipboard, for example, seems to be effective as if the selection in the Windows 10 side has not happened.

I think this has been caused by windows update and seems to be the driver issue on the host Windows 10 site.

I don't think there are any relevant issues in the log, but I attach them just in case.

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