VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1684 - 1686 of 16363)

Ticket Resolution Summary Owner Reporter
#8670 fixed Can't start Virtual Box on OS X 10.6.7 Derferman
Description

Problem: Launching VirtualBox causes it to crash. The icon will bounce a few times on the dock and then disappear

To Reproduce: Launch VirtualBox.

Hardware Information: Newest 13' MacBook Pro running OS X 10.6.7

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro8,1
  Processor Name:	Intel Core i5
  Processor Speed:	2.3 GHz
  Number of Processors:	1
  Total Number of Cores:	2
  L2 Cache (per Core):	256 KB
  L3 Cache:	3 MB
  Memory:	4 GB
  Boot ROM Version:	MBP81.0047.B04
  SMC Version (system):	1.68f96
  Sudden Motion Sensor:
  State:	Enabled
#14907 obsolete Can't start Virtual Machines on older Hosts kayk
Description

We use different Notebooks, and those that had Windows 7 installed longer than a year or two can't start Virtual Machines on Versions 4.3+

We need to update to 5.0.10 but can't do so with those older Laptops because they get all the same Error message. I attached a picture, translated it's something like "The instruction at XXX referenced memory at XXX. The memory could not be written"

If I reinstall a new Windows 7 on one of those Laptops, it seems to work fine but we got 20+ of them and it would be a real pain to back up everything when it's the same OS we already use.

I tried deactivating antivirus, so that doesn't seem to be the problem.

Thanks for your help.

#6460 wontfix Can't start a previously saved VM after replacing CPU, even when the new one is perfectly compatible Durval Menezes
Description

The problem:

After replacing my computer's motherboard and CPU (because the old ones died), I can't start any previously saved VMs; even discarding the current state doesn't help if the last snapshot was made with the machine running; seems discarding the full snapshot would be needed to be able to start this VM again.

More details:

Previous motherboard, CPU: Aopen i975AX-YDG, Intel Merom T5600 Replacement motherboard, CPU: Intel S3210SHLC, Intel Yorkfield Q9550 O/S: Ubuntu Hardy 8.04 LTS, all updates applied. VBox: 3.0.12 r54655 PUEL, downloaded directly from http://www.virtualbox.org/wiki/Downloads

Possible solutions:

1) Quick workaround: just tell me where I can poke on the .sav file with a binary editor so I can change VBox' idea of the old CPU to be exactly equal to the new one and so try to bypass the trouble, or else how can I restart this VM by booting it (as the snapshot was made with the machine running, it seems I have no way to simply reboot it from the snapshotted disk, or at least I can't find it in the GUI).

2) "Definitive" solution: make the "CPU checking" logic smarter so that when moving to a newer CPU that's a "proper superset" of the old one (i.e, has everything the old one has), it won't refuse to run the saved state from the old one.

3) Perhaps an even better (and easier to implement) solution: when VBox detects that the CPU has changed, instead of refusing to run the saved state just prompt the user with a dialog box where he/she is warned that the CPU has changed, and that it's possible that the saved machine won't run properly; then, offer the user the option to continue at hos/her own risk, or to abort the run.

For other cases and background, please see this VBox forum topic: http://forums.virtualbox.org/viewtopic.php?f=6&t=28750, specially my 2 posts at http://forums.virtualbox.org/viewtopic.php?f=6&t=28750#p131230 and http://forums.virtualbox.org/viewtopic.php?f=6&t=28750#p131233

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