VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1285 - 1287 of 16363)

Ticket Resolution Summary Owner Reporter
#9641 duplicate critical error Tina
Description

Please look through my logs and let me know what I am doing wrong.

#9476 invalid clonning problem tomio
Description

hello, I have a cloning problem :

1 / My hardware is supermicro server with 2 xeon x5680 64go ram 3ware raid

2 / host OS is opensuse 11.4 with patch

3 / I have installed latest virtual box , with extensions usb

4 / Virtualbox appear to work properly

5 / i Have create Xp 32 virtual machine and when ready i have cloned this with no problem every clone work well.

6 / i do the same for suse linux server x86 64 sles 11 sp1 when ready , have cloned virtual machine but linux start and when he must start the disk he don't find it and crash.

7 / i do the same that 6 for open suse 11.4 x86 64 and after cloning same problem he crash at start don' find the disk

for 6 and 7 i have mount 4 partition as, /boot, /swap, /, /tmp,

for 6 system file is ext3

for 7 system file is ext4

have you any idee about the problem ?

best regards Patrice

#9231 fixed VirtualBox Should Have an SLIC Passthrough Mechanism => Fixed in SVN Tom Gelinas
Description

When Windows 7 or Vista are exposed to major hardware changes, their license validation ("Product Activation") is revoked. If a natively-installed Windows 7 OS is run in VirtualBox via "raw hard disk access" VMDK, the user is left with 30 days to reactivate. With Windows XP, this could be avoided by using different "hardware profiles" for either bare-metal or virtualized environments. Windows 6.0+ is better at hardware detection and has no hardware profile feature.

A workaround for this problem uses System Locked Preinstallation (SLP): https://secure.wikimedia.org/wikipedia/en/wiki/System_Locked_Preinstallation SLP is used to activate Windows on most OEM computers, and is less affected by hardware changes. Windows remains activated so long as a computer's BIOS has an SLIC string that corresponds with certain Windows license keys. This effectively binds the Windows license to a specific model of computer, similar to the method Apple uses to ensure OS X can only be run on Apple hardware.

Common Windows licenses allow the use of Windows both virtually and physically on the same hardware. Considering that VBox is able to run OS X given the presence of certain strings in BIOS ("ourhardworkbythesewordsguared..."), it would make sense for this type of feature to be extended to Windows. Windows licensing could even be afforded more protection than OS X, because there is currently no interface to to manually supply an SLIC key to VirtualBox while any string could be added to a VM's DMI.

A machine's SLIC can be read in Linux via /sys/firmware/acpi/tables/SLIC It's already possible to add it using a hex editor. Offering to relay a real SLIC seems like a fair compromise.

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