VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (4 - 6 of 16363)

1 2 3 4 5 6 7 8 9 10 11 12
Ticket Resolution Summary Owner Reporter
#11436 fixed No-Execute Page Protection setting not replicated in Guest VM $dave
Description

Appears to be a re-occurence of ticket #3578 ??

Extract from VBox.log: 00:00:01.295084 NX - No-Execute Page Protection = 0 (1)

Host is Ubuntu 10.04 LTS Guest is cloned Windows XP Pro SP3 and attempting to upgrade to Windows 8. VirtualBox version: virtualbox-4.2 4.2.6-82870~Ubuntu~lucid

Installation fails to complete with message: Your PC needs to restart. Please hold down the power button. Error Code: 0x0000005D

Settings -> System -> Processor for guest shows "Enable PAE/NX" checked.

#8768 fixed inaccessible virtual machine $roman
Description

I created a v.m. with Windows Server 2003 and took some snapshots. I then created another v.m. and told it to use the original drive or one of the snapshots (don't exactly remember) for its hard drive. I have done this in previous versions of VirtualBox with no problem. At one point I realized that I had named my second v.m. wrong and changed the name. Everything seemed fine until I needed to reboot the host machine for some reason. So when I restarted VirtualBox, I immediately got a warning about media not accessible. And the VM that I had created with the shared hard drive was inaccessible. It said in the right hand pane: A differencing image of snapshot {###...} could not be found. Could not find an open hard disk with UUID {###...}. Result Code: E_FAIL (0x80004005) Component: SnapshotMachine Interface: IMachine {###...} On the Warning message, there is a check option to open the Virtual Media Manager. Selecting that, I can see that under a .vdi file that I created with a machine (the one assigned to my inaccessible virtual machine) attached to it is another VDI, the last differencing VDI in the list, and it's inaccessible--{###...}.vdi. The location is C:\Documents and Settings\admin\VirtualBox VMs\pc1pepo01_tst2\Snapshots\{###...}.vdi. And below it says, Attached to: Not Attached. One thing to note is that I originally named the v.m. pc1pepo01_tst2, but then changed it to mc1pepo01_tst2 and the folder name and everything changed as it is supposed to. So, something did not get automatically changed here. I changed all the names of the files in the virtual machine's directory back to a p from an m and also changed that in the .vbox file and also in the main virtualbox.xml file. Then when I started up VirtualBox I had the same inaccessible message, but in the Virtual Media Manager there was no error, though the one disk and a couple of other .vdi's (like the one right above it) also say Not Attached. An extra data disk that I had added now also says Not Attached.

What's going on here? How can I get my virtual machine back? All of the referenced snapshots and vdi files seem to be here.

Host: Windows XP Guest: Windows Server 2003 V.B. version: 4.0.2

#15301 fixed Windows 10 VM crashing -=VR46=-
Description

Hi,

I'm running virtualbox on openSUSE 13.2 (Harlequin) (x86_64) and the windows 10 VM is "windows 10 enterprise 64bit" for no aparent reason the VM just reboots without warning and there doesnt seem to be any pattern which is causing the reboot, I have even left the VM running with nothing open and nothing running on the host PC appart from the windows 10 vm only to come back and the vm has rebooted

regards,

-=VR46=-

1 2 3 4 5 6 7 8 9 10 11 12
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