VirtualBox

Ticket #207 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Installing guest additions on the host causes problems and should not be allowed

Reported by: ghr Owned by:
Priority: minor Component: other
Version: VirtualBox 1.3.8 Keywords: host reboot guest addition mouse
Cc: Guest type: other
Host type: other

Description

Host: WinXP SP 1 UK with KB889293 (512 MB RAM, 80 GB HDD)

Virtualbox 1.3.8 from VirtualBox_1.3.8_Win_x86

Guest VM created: DOS6.2/Win3.11 (16MB RAM; 500 MB HDD)

Guest Addition from the same install kit. After install of Guest Addition & reboot: WinXP host machine reboots on 1st mouse movement.

Workaround: Mouse disconnected; keyboard control ok. WinXP host 'repaired' with WinXP system restore point (which by the way removes VirtualBox including installer file).

Attachments

Machine_VDX486.zip Download (24.5 KB) - added by ghr 7 years ago.
Machine_VDX486 logs

Change History

comment:1 Changed 7 years ago by sandervl73

That's rather strange. Would it be possible for you to send us your VDI file?

comment:2 follow-up: ↓ 3 Changed 7 years ago by milosch

I am seeing the same thing except with a Server 2000 guest. Host reboots some time after login, and quite possibly when the mouse is moved. It didn't do this before the install of the Guest Additions. Using 1.3.8 OSE self-compiled on Ubuntu Edgy AMD64.

comment:3 in reply to: ↑ 2 Changed 7 years ago by bird

Replying to milosch:

I am seeing the same thing except with a Server 2000 guest. Host reboots some time after login, and quite possibly when the mouse is moved. It didn't do this before the install of the Guest Additions. Using 1.3.8 OSE self-compiled on Ubuntu Edgy AMD64.

The 1.3.x release series isn't supposed to be stable on AMD64. We have fixed one host reboot issue that probably is still there in the 1.3.x release series. This makes me really doubt that you are seeing the same problem as ghr here.

Bottom line: Don't use 1.3.* for AMD64, use the subversion!

comment:4 Changed 7 years ago by milosch

Thanks. I have since installed from svn and things are happy so far.

comment:5 Changed 7 years ago by frank

  • Status changed from new to closed
  • Resolution set to wontfix

Changed 7 years ago by ghr

Machine_VDX486 logs

comment:6 Changed 7 years ago by ghr

Also: .VDI retrieved... can attach if stil useful ?

comment:7 Changed 7 years ago by sandervl73

  • Status changed from closed to reopened
  • Resolution wontfix deleted

comment:8 Changed 7 years ago by sandervl73

Please do. Only the 64 bits host version (1.3.8 source only as it's experimental) is known to reset your machine.

How big is the vdi?

comment:9 Changed 7 years ago by sandervl73

  • Priority changed from major to critical

comment:10 Changed 7 years ago by ghr

Tried to upload - failed due to file size (winzipped 3943kB vs max upload 400.000B. Awaiting advice..

All details I can provide are listed below:

  • vdi in vdx486.zip (upload failed)
  • other details in machine_vdx486.zip attached earlier

Some additional info

  • i created a virtual hdd 480 MB
  • loaded dos 6.2 with defaults... (after format c: /q /u)
  • loaded win311 with mostly defaults, somewhere it recognised a ps2 mouse (i have a USB mouse connected via usb/ps2 connector)
  • detail : i recall that dos 'mem' did not (seem to) work correctly (didn't get any output from it)

comment:11 Changed 7 years ago by sandervl73

Could you email it to me? Drop the two digits from my bugtracker name and append at innotek dot de.

comment:12 Changed 7 years ago by HarryE

This happened to me when I installed guest addition on the win2000Prof host!

To regain control of the host mouse, run regedit on the host, to modify the key HKLM, System\CurrentControlSet\Control\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}, UpperFilters, 0x00010000, "VBoxMouse", "mouclass"

into HKLM, System\CurrentControlSet\Control\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318}, UpperFilters, 0x00010000, "mouclass"

(press modify, then delete to remove Vboxmouse and some zeros... Then reboot.

There should be a warning message in the addition installer on not installing on the host!

HTH

comment:13 Changed 7 years ago by sandervl73

Oh, now I get it. I couldn't quite understand how anybody would possibly install the *guest* additions on the host. You're right that the installer should refuse to do so.

comment:14 Changed 7 years ago by sandervl73

  • Summary changed from Mouse makes WinXP host reboot after installing Guest Additions to Installing guest additions on the host is allowed and causes problems

comment:15 Changed 7 years ago by sandervl73

  • Summary changed from Installing guest additions on the host is allowed and causes problems to Installing guest additions on the host causes problems and should not be allowed

comment:16 Changed 7 years ago by sandervl73

  • Priority changed from critical to minor

comment:17 Changed 7 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

The next release will contain a fix for the mouse driver. Native Windows should not complain anymore if the VBox guest additions are installed.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use