Hardw. virt. ext exclusive setting
-
Perryg
- Site Moderator
- Posts: 34369
- Joined: 6. Sep 2008, 22:55
- Primary OS: Linux other
- VBox Version: OSE self-compiled
- Guest OSses: *NIX
Re: Hardw. virt. ext exclusive setting
Probably. Try setting it to one and see.
-
Rastus
- Posts: 37
- Joined: 13. Jan 2010, 04:19
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: Windows
Re: Hardw. virt. ext exclusive setting
OK,
I tried it running on a host server with 2 processors. No Joy.
I tried running the guest with only 1 processor active. No Joy.
I was able to go into the .xml and adjust the hw virt exclusive setting to off but that didn't seem to matter.
The physical server that I am virtualizing is a newer server and might have hardware virtualization available but since it is running 32 bit Windows 2003, I wouldn't think would be a problem. Also, the image ran on my macbook which I do not think has HW virtualization.
Now I am going to do a whole new convertfromraw directly to the host and use the machine settings that I ran with on the Mac and see if that works.
Any other thoughts?
I tried it running on a host server with 2 processors. No Joy.
I tried running the guest with only 1 processor active. No Joy.
I was able to go into the .xml and adjust the hw virt exclusive setting to off but that didn't seem to matter.
The physical server that I am virtualizing is a newer server and might have hardware virtualization available but since it is running 32 bit Windows 2003, I wouldn't think would be a problem. Also, the image ran on my macbook which I do not think has HW virtualization.
Now I am going to do a whole new convertfromraw directly to the host and use the machine settings that I ran with on the Mac and see if that works.
Any other thoughts?
"Putting the FUN back in Dysfunctional"
-
Rastus
- Posts: 37
- Joined: 13. Jan 2010, 04:19
- Primary OS: Ubuntu other
- VBox Version: OSE Debian
- Guest OSses: Windows
Re: Hardw. virt. ext exclusive setting
OK,
on further review,
The server that I ma P2V migrating is running in 64 bit mode in the BIOS even though it is running Windows 2003. Since I only have licenses for he 32 bit version of windows, I have to assume that it is running that version. But since the old IT guy did the install, I can't know for sure.
This explains the problem running the .vdi file on my non-hardware virtualized older dell 1850 server. It also explains why it would run on the Mac since it has a 64 bit processor.
I am assuming that I cannot just turn off the 64 bit setting in the BIOS and have the windows 2003 still run properly. So, my goal is to install virtualbox on this machine anyway and use it to run both of our main application servers. I guess I'll just have to make great backups and bite the bullet and wipe the drive and install virtualbox on the 64 bit machine and then import the virtual machines.
Anybody have any other suggestions?
Thanks for all of your troubleshooting help.
on further review,
The server that I ma P2V migrating is running in 64 bit mode in the BIOS even though it is running Windows 2003. Since I only have licenses for he 32 bit version of windows, I have to assume that it is running that version. But since the old IT guy did the install, I can't know for sure.
This explains the problem running the .vdi file on my non-hardware virtualized older dell 1850 server. It also explains why it would run on the Mac since it has a 64 bit processor.
I am assuming that I cannot just turn off the 64 bit setting in the BIOS and have the windows 2003 still run properly. So, my goal is to install virtualbox on this machine anyway and use it to run both of our main application servers. I guess I'll just have to make great backups and bite the bullet and wipe the drive and install virtualbox on the 64 bit machine and then import the virtual machines.
Anybody have any other suggestions?
Thanks for all of your troubleshooting help.
"Putting the FUN back in Dysfunctional"