| 10 | | #1 VB v4.3.18 successfully installed |
| 11 | | #2 VM 'Win7x64_Template' (windows 7.Pro-x64 guest) successfully created and running |
| 12 | | #3 Since USB was not being recognized on the guest I reinstalled VB v4.3.18 (using 'run as administrator' option) |
| 13 | | #4 I tried to load the guest ('Win7x64_Template') but it couldn't load displaying a message loop 'Windows is loading files'. After some research, I realized that it is due VB is not supporting 64bits. Indeed, I could see VB doesn't allow to create 64 bit VM; also the 64 bit VM I previously created ('Win7x64_Template') was not being recognized as 64 bit system but 32 bit. Besides, 'acceleration' options is grayed-out on settings of VM 'Win7x64_Template' |
| 14 | | #5 I found on internet that issue w/ 64 bit support is related to Virtualization support on BIOS ('Virtualization technology' option). However, I also found this BIOS option comes deactivated by default and it is not mandatory for 64 bit support (BTW that option was deactivated on my BIOS). Notice 64 bit support issue persist with either 'Virtualization technology' BIOS option activated or deactivated. So, why 64 bit is no longer supported on my VB if I made no changes on HW nor any configuration (like BIOS level) and considering that this was working prety well prior I reinstalled VB? |
| 15 | | #6 I am using a laptop proBook 6460b |
| 16 | | #7 Per internet article, I tried to downgrade VBox from 4.3.18 to '4.2.18', so I did it and afterwards (with either 'Virtualization technology' BIOS option ativated or deactivated) I could see 64 bit system support was available again, however I couldn't load a 64bit VM ('Win7x64_Template') and an error message pops-up ('VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer.) |
| | 10 | 1. VB v4.3.18 successfully installed |
| | 11 | 2. VM 'Win7x64_Template' (windows 7.Pro-x64 guest) successfully created and running |
| | 12 | 3. Since USB was not being recognized on the guest I reinstalled VB v4.3.18 (using 'run as administrator' option) |
| | 13 | 4. I tried to load the guest ('Win7x64_Template') but it couldn't load displaying a message loop 'Windows is loading files'. After some research, I realized that it is due VB is not supporting 64bits. Indeed, I could see VB doesn't allow to create 64 bit VM; also the 64 bit VM I previously created ('Win7x64_Template') was not being recognized as 64 bit system but 32 bit. Besides, 'acceleration' options is grayed-out on settings of VM 'Win7x64_Template' |
| | 14 | 5. I found on internet that issue w/ 64 bit support is related to Virtualization support on BIOS ('Virtualization technology' option). However, I also found this BIOS option comes deactivated by default and it is not mandatory for 64 bit support (BTW that option was deactivated on my BIOS). Notice 64 bit support issue persist with either 'Virtualization technology' BIOS option activated or deactivated. So, why 64 bit is no longer supported on my VB if I made no changes on HW nor any configuration (like BIOS level) and considering that this was working prety well prior I reinstalled VB? |
| | 15 | 6. I am using a laptop proBook 6460b |
| | 16 | 7. Per internet article, I tried to downgrade VBox from 4.3.18 to '4.2.18', so I did it and afterwards (with either 'Virtualization technology' BIOS option ativated or deactivated) I could see 64 bit system support was available again, however I couldn't load a 64bit VM ('Win7x64_Template') and an error message pops-up ('VT-x/AMD-V hardware acceleration has been enabled, but is not operational. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. Please ensure that you have enabled VT-x/AMD-V properly in the BIOS of your host computer.) |
