I am new in Virtualbox and I unfortunatelly have problem at the beginning.
I have created new machine and configured it with default options. When I want ot start my machine I got green screeen:
I have no idea what can be wrong. Have you any ideas guys?
It actually happens if you create 32 bit Windows machine and try to install 64 bit image on it. I set the machine to be 64 bit and it works fine now
Related
VT-x option is missing Surface Laptop 3 BIOS menu(Intel i7-1065G7 procesor), without this VT-x enabled, I cannot run any virtualization on Windows. Anyone encountered the same problem and know how to fix?
Bit late on the response so I dont know if you have worked this out already, but it might help someone else. I also have a Surface Laptop 3 but with an AMD CPU etc. Virtualisation was also missing on my BIOS. My issue was that when using Oracle VirtualBox, the 'Start' opting to begin installing Ubuntu was 'grayed out' or unable to be selected. After searching around, all I needed to proceed with installing Ubuntu was to do what this guide says.
Essentially I just searched in the Windows taskbar 'Turn Windows features on our off'. Here I was able to enable 'Virtual Machines Platform'. I also enabled Windows Hypervisor Platform although I am not sure if this is necessary. Restarted the system and I was able to proceed and install Ubuntu through VirtualBox! Hope this helps!
I found a little option using the Oracle Virtual Box for the Intel version of your Surface!
In the Task Manager, under Performance, you can check that virtualization is disabled. Just follow my easy steps:
Run VirtualBox as an administrator
Create new virtual machine (it doesn't matter what you choose)
Run it for the first time
Go to Machine Settings > System > Processor—as you can see, it is set to a default of 1
Change the number from one core to more than one and somewhere on the bottom side of the GUI you could see an attention icon that says something like
virtualization off. If you save these setting it will be automatically turned on
Just press OK and voila! It will be turned on!
Now when I type this response I checked too if it is enabled in Task Manager and it was, so yeah!
I am trying to find a way to programatically detect that my program runs on a virtual machine, as far as I know there is no common way for parallels to do that.
Windows 8 task manager performance tab displays a "Virtaulization" option, what does it mean? When i run windows 8 in a virtual machine it changes to virtual processors and virtual machine: yes, so some how windows 8 detects that it is running inside a virtual machine, how does windows 8 detect that it is running in a virtual machine? Is it possible to get this information programatically? I tried both on parallels and vm ware and both works fine.
You should take a look at this interesting article Red Pill... or how to detect VMM using (almost) one CPU instruction by Joanna Rutkowska which used to be here but is now dead and can only be viewed with the waybackmachine here and Virtualization: Red Pill or Blue? by Steven McElwee which also used to be here but can now only be viewed here.
Heres the code:
int swallow_redpill()
{
unsigned char m[2+4], rpill[] = "\x0f\x01\x0d\x00\x00\x00\x00\xc3";
*((unsigned*)&rpill[3]) = (unsigned)m;
((void(*)())&rpill)();
return (m[5]>0xd0) ? 1 : 0;
}
It should return 1 if running in a virtual machine and 0 if not.
Edit: It may return false-positives on modern cpus and its apparently better to combine a couple of tests together to make sure the result is real.
On VMware you could check for the CD drive vendor- should be "VMware" or "VMware, Inc." or something like this.
I don't know about VMware workstation but on ESXi your MAC address generally starts with "00:50:56". You could make use of this, too.
Have a look at virt-what. Maybe you can port it to Windows.
And maybe How to detect install is running on a VM? can help you.
I'm currently running a 64-bit version of WAMPSERVER (on Win7 Pro 64).
I've always been able to get anything I needed up and running except for SQLSRV, and have finally hit the point where I need sqlsrv, so I need to switch to a 32-bit wamp stack. :(
Since I'm a bit uncertain on the best plan-of-attack, I was planning to install a second wamp server (32bit) for testing, but that leaves me with two questions.
If I stop all my wamp services, and do a second installation of the
32bit version, would that cause any problems (that'll end up being an even bigger time-sink) ?
Is there a better (already proven) way to migrate all the configs from a
64bit to 32bit stack?
My whole reason for this plan is to test- migrate all my installed and
enabled ext's to the 32 bit stack and see if they work (as well as
my projects, of course).
Ultimately, I'd prefer to not have to go though the hassle, so if anyone magically came up with a solution to connecting to MS SQL Server from 64-bit PHP, please advise.
Other than that, would two installations of WAMP Server cause any glitches?
Or, is there already an easy/proven way to migrate from the 64bit to the 32bit vers?
Read this question, i hope it will help you to reach to your solution
Wampserver - mssql - 64 bit to 32 bit
I have a Kubuntu 12.10 64bit as host and CentOS 6 32bit as guest system on VMware player 5 on a Dell Latitude E6510.
Despite the installation of VMware tools, the clipboard exchange is not working.
I use a very similar guest system within VirtualBox and there cliboard exchange works fine.
Has someone experienced the same with a configuration similar to mine?
And is it possible, that the guest system causes the problem instead of the player?
I've found thaht suspending and then re-playing the VM will re-enable clipboard exchange.
Clipboard exchange will then work both between VMs and the Host machine as well as between VMs themselves.
(VMWare Player 5.0, Windows 7)
After having installed several constellations like that, I experienced, that in general it works, I can exchange the clipboard in both ways and even the desktop size adapts to the size of the VM window, but still from time to time having a situation, where it doesn't work and also heard of many other people who experienced that.
So, if someone can enlighten me on that point, I'll be happy, but I'm closing my question hereby.
We get an app that was working fine until update Windows from Vista Home Basic to 7 Home Premium. We use mscomm32.ocx to control serial port, but it seems it's not supported for 64 bits OS.
Each time we try to read the port: Thisform.msCommControl.Input We got the following:
OLE IDispath exception code 0 from MSComm: Error reading comm devide
We've made a lot of unsuccessful tests. Does any one know how to fix this problem?
The solution is to use an updated control that is contantly under development so newer Windows are also supported. ADONTEC's SuperCom ActiveX is a MSComm compatible ActiveX that developers use for many years in order to replace the MSComm. It is compatible with 32 and 64 bit of Windows 2000/XP/7/8 and Windows 10. You are almost done in few minutes. In many cases the application runs not only faster but is by far more stable and it also offers by far more functionality. See more info here.
that MSCOMM32.OCX will not work with Windows 7 64 bit machines. However, strange as it may seem I have a VB6 program controlling equipment from a virtual comm port (USB ~ serial converter)
It works fine on windows 8.64 bit machine.
The only thing is that the converter driver had to be modified to run on 64 bit.
If you are using a real com port that doesn't matter.
Try it on a 64 bit machine with Windows 8