mouse integration

[teka]

Hi

I'm running Windows 10 Pro 64 19041 and have just installed Virtual Box 6.1. This my first time trying to use Virtual Box

Trying to install Windows XP as guest. All goes well until the "found new hardware wizard" as unable to use mouse to select anything. The icon shows mouse integration is ON - has green flash

Tried several times - always the same!

All help appreciated

[scottgus1]

Start the guest from full power off, not save-state. Run until you see the problem happen, then shut down the guest from within the guest OS if possible. If not possible, close the Virtualbox window for the guest with the Power Off option set.

Please right-click the guest in the main Virtualbox window's guest list, choose Show Log. Save the far left tab's log, zip the log file, and post the zip file, using the forum's Upload Attachment tab.

Also, please right-click the guest in the main Virtualbox window's guest list, choose "Show in Explorer/Finder/File Manager". In the window that opens, zip the guest's .vbox file, and post the zip file, using the forum's Upload Attachment tab.

[teka]

Thanks Scottgus1

I have attached the zip files

win xp rev 2 june 2020-2020-07-15-06-26-36.zip

log file

(22.2 KiB) Downloaded 7 times

Hope have done this correctly!

[scottgus1]

You have no USB filters in place, that's good:

<USB>
<Controllers>
<Controller name="OHCI" type="OHCI"/>
</Controllers>
</USB>

The usual virtual simulated mouse is inserted:

00:00:03.092666 VUSB: Attached 'HidMouse' to port 1 on RootHub#0 (FullSpeed)

I have never had a Virtualbox guest OS freshly installed from the ISO ask for drivers for a mouse simulated by Virtualbox. I bring this up because There is a suspicion that this XP guest was downloaded preinstalled:

<HardDisk ... location="C:/Users/tedat/Downloads/Win XP/VirtualXP.VHD" format="VHD"

00:00:02.321151 File system of 'C:\Users\tedat\Downloads\Win XP\VirtualXP.VHD' is ntfs

It is an unusual choice for a brand-new Virtualbox user to intentionally choose to deviate on the format of the disk the guest will use, not to say it hasn't happened before. But a pre-installed XP guest, downloaded, and made by someone else, perhaps from a Windows 7 XP-mode VM, which were VHDs, might explain things.

If you got this guest as a pre-installed virtual disk, it may have problems that we cannot fix. (If you don't have a valid license for the guest, it's illegal, too.)

Please try a fresh install from a non-manufacturer-branded (ie not DELL or HP, etc.) ISO. Someone is sure to have an old XP ISO laying around that you could try. I'm sure the mouse will work there. And you should still be able to phone into Microsoft and activate it.

[scottgus1]

Also, one other thing you have that will cause you trouble later on (it is probably not causing the present mouse trouble, but one never knows).

Your log contains these lines:

{timestamp} HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
{timestamp} NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...

You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow. Or it might guru-meditate or crash. This is because a service that uses Microsoft Hyper-V is running on your host PC. Normally Hyper-V blocks Virtualbox. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This arrangement is still being developed and isn't 100% yet.

If VirtualBox is running without Hyper-V enabled, and nothing else is interfering with hardware virtualization (VT-x / AMD-V), then the usual virtualization icon () will be seen in the Status Bar.

To turn Hyper-V off completely, do this:

1. Shut down all programs. You will have to reboot your host.

2. Look into I have a 64bit host, but can't install 64bit guests, 2nd post, points 2 & 3 and ensure that none of these things are running.

3. Find the Command Prompt icon, right click it and choose Run As Administrator.

4. Enter this command:

bcdedit /set hypervisorlaunchtype off

5. Enter this command:

shutdown -s -t 2

6. When the computer turns off, unplug it for 20 seconds. Then plug it in again and boot up Windows 10.

Your Virtualbox should be running now. If the green turtle still appears and the tell-tale lines are in the log, try all the steps again. If you don't get the standard virtualization icon, post back exactly what you did and we'll try to help some more.

For further info, see https://www.tenforums.com/tutorials/139 ... puter.html

[teka]

Many thanks Scottgus1 for your time and effort in helping me

I have windows XP disk but this new laptop doesn't have a optical drive so I thought I would use a downloaded ISO. I now know this was a mistake!

I have done actions 1,3 and 4 of your msg timed 20.16 to turn Hyper-V off. I will revisit point 2 and study the linked post more thoroughly - (also need to understand a bit about Hyper-V)

I will let you know how I get on - thanks again

[scottgus1]

Sounds good, teka!

If you used to see the green turtle but don't see it now, then Hyper-V is off. Very often the 'bcdedit' command is the silver bullet.

You might be able to use a friend's computer to make your XP disk into an ISO. Free programs can be downloaded that can convert installer CDs and DVDs into ISO files. Imgburn is the one I have used for several years.

[teka]

I closed Hyper-V down using the control panel method (windows features) as described in

https://support.microsoft.com/en-gb/hel ... v-device-g

Virtual box is now updated to version 6.1.10
I'm putting Windows xP to one side for the time being. To gain experience at setting up a virtual machine I have download "freeDOS" from the official website, into my downloads folder

I'm following the instructions at

https://www.virtualbox.org/manual/ch01. ... i-createvm

I have created the virtual machine "FreeDOS".When I select it and click start I'm getting message in "starting FreeDOS VM box "creating process" and it freezes

Have closed down VB using task Manager (now have error "failed to open...) then removed (delete all files) the FreeDOS VM and tried again.

Starting VM get message about "select start up disc". Now at 1.8.1 in the instructions which say for new installation click the icon for file dialogue. When I click the icon I get "Optical Disk Selector"

Browsiing for video tutorial found advice to selct the iso file by settings-storage-contoller ide and select the iso in the download folder.

Now when I start the virtual machine I get screen identical to that at

http://wiki.freedos.org/install/

After selecting install I get repeated message "invalid Opcode at ......

Help please as I'm not sure whats happening - is VB not configured or is the isp corroupt

[scottgus1]

Your Hyper-V is off, that's good:

00:00:02.315542 HM: HMR3Init: VT-x w/ nested paging and unrestricted guest execution hw support

I have not tried FreeDOS. Generally, if the guest Virtualbox window stays open, and the installed OS is displaying messages that come from that OS, then usually Virtualbox is working, and you would troubleshoot the problem directly in the guest OS."invalid Opcode" does not sound like a Virtualbox error message.

Try a more common OS like Ubuntu. You have plenty of room on your computer for a decent guest. Use 4GB RAM and 2 processors in the guest.

[multiOS]

@teka

If, for some reason, you want to persist with the FreeDOS VM creation see the developer's guidance note at the bottom of this page: https://www.freedos.org/download/

I've tried following the developer's suggested action and it does work

[teka]

Thanks multios

That worked a treat.

annoyed with myself that I didn;t read to bottom of download page - only read the installation instructions

[teka]

Thanks scottgus1

I think my initial problem is now solved

[scottgus1]

Great! Glad you're up and running.