Problems installing VirtualBox

[Robot]

I did some investigating regarding drivers in a virtualbox I rang some companies regarding the drivers I wanted to download and run in virtualbox and they tell me that most downloads won't run in Virtualbox is that true or they just spinning me a line.

[mpack]

You normally don't need to download any drivers for VirtualBox. VirtualBox is designed so that it emulates hardware that the OS already has native drivers for. That does indeed get complicated if you try to use a royalty OEM edition of Windows, particularly from Dell, as those don't necessarily ship with the same set of legacy drivers as Windows does. In any case the needed drivers were written by Microsoft, you'd be taking a punt trying to get mfr drivers to work and be as stable.

[mpack]

Taking another look at your log, I notice :-

00:00:02.690399 HMEnabled <integer> = 0x0000000000000001 (1) (VT-x selected in recipe)
...
00:00:03.557122 Full Name: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
...
00:00:02.690805 HMR3Init: Falling back to raw-mode: VT-x is not available.

The Intel website page for the i3-4160 says that VT-x is implemented in this chip, so "not available" must mean either that it must be disabled on your host, or something else is using it (like Hyper-v). You should check that Virtualization Technology is enabled in your host BIOS, and disable the Hyper-v service or any other VM platform that is running at the same time.

[Robot]

I have entered into UEFI (Bios) and though you cannot enable or disable Virtualization it states that it is supported.
VT-X is supported but not VT-D I know that VT-X is a must but VT-D is nice to have how does VT-D fit into the picture.
How do I access the DVd drive in the host PC and the usb ports.
I have disabled Hyper-v where ever I have been able too.
What did work was a program I copied into the virtual share folder in the host and managed to run it in the virtual machine which I had not been able to do with other software which looks as though some software will run but others won't.
Also can you access a PCI card from the virtualbox.

[mpack]

VT-d allows PCI passthrough to the guest: the VM would have exclusive ownership of redirected devices. Ownership cannot be shared. VT-d is unsupported and therefore irrelevant on Windows hosts, and even on Linux hosts nobody has ever reported using it successfully.

This question has made me aware that you have a vague topic title, and seem to be using it for a variety of questions. We don't normally like that: one issue per topic is preferred.

[Robot]

Thanks for the reply.
I have installed a PCI serial card in the host pc and would like to access this card from the virtualbox is this possible if so how.

[mpack]

VT-d is unsupported and therefore irrelevant on Windows hosts

Additional serial ports, provided by a plugin card on the host, would be used like any other Windows host serial port. See section 3.9 of the user manual.

[Robot]

Can the driver for the pci card be installed in virtualbox or does the driver have to be supported by the host and installed through the host.

[mpack]

The latter.

[Robot]

Thanks for the reply.
After trying to set up serial port I now find that whenever virtualbox is clicked on via the desktop and I click start to power up XP I loose my mouse and I regain the use of the mouse when I shut down so if Xp in virtualbox is started I loose my mouse.
I returned everything back to normal settings (usb & serial port ) but I still loose mouse and keyboard.

[mpack]

That sounds like an additional problem, that you have a blank USB filter defined which is grabbing your USB mouse. If you need to grab a USB device then don't use a blank filter unless your PC only has one USB device.

As I said above, we do not permit vague topics on these forums. Keep to one issue per topic, and make sure that the topic title suggests that issue.

In fact, I just changed your topic title - "VirtualBox General Problems" is too non-specific.

[Robot]

Thanks for the reply.
I have got my mouse & keyboard back but not the serial port which I can access from the host but not the virtualbox.

[mpack]

Serial port configuration is off topic relative to the first post. Locking this topic, since the message about one issue per topic is clearly not getting through.