Page 2 of 3

Re: Make VirtualBox compatibility a top priority

Posted: Sat Oct 23, 2010 2:38 pm
by LaneLester
Point taken. I did a bug search and found a workaround to the Firefox problem: Bug 5574 – Firefox: in v3.6.8 can't type in the URL field unless you switch focus

So after I start Firefox, if I click on the desktop and then click back to Firefox, I can type in the URL and other fields. So at least I can move forward with some useful things.

The bug is marked as Trivial, but I would think full Firefox functionality is more important than that.

Lane

Re: Make VirtualBox compatibility a top priority

Posted: Sat Oct 23, 2010 8:54 pm
by Carlo Bramix
Some time ago I was able to use Guest Additions (GA) with trunk builds without much problems, but then they misteriously stopped to work.
Here you are what happens:
1) Sometimes a dialog box appears during installation of GA, saying that the memory could not be "write".
2) Sometimes installation works, but during the reboot a BSOD always appears. No way to overcome this. It happens also with 0.3.12 boot CD.

There is another problem that happens here, but during the second stage of installation.
When ReactOS setup is registering components, when it reaches mshtml.dll then a dialog box should appear, asking if you want to install gecko plugin.
Instead, when I reach that point, everything freezes, showing a light blue empty screen without any dialog box.
If I select to run it in DEBUG mode (in other words, with text prints to serial port), tipically that dialog box appears and I can complete the second stage of installation, but do not ask me why.
Apparently It seems that slowing down something a bit with debug messages, it helps.

Re: Make VirtualBox compatibility a top priority

Posted: Sat Oct 23, 2010 9:24 pm
by LaneLester
I guess the differences in systems is producing some different results.

With the VBox version of ReactOS, the GA executables were in drive D: in My Computer, and I successfully installed GA from there. In the .iso version I've installed in VBox, the D: drive is empty.

The Gecko download went OK for me.

Lane

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 23, 2011 9:11 am
by v_2samg
Hi All!

Anyone used ReactOS 0.3.13 with VirtualBox 4.0.4 & VirtualBox Guest Additions lately? I have been trying this for quite sometime now and still get the same bluescreen. Even tried it with the latest SVN builds. I am putting the screen shot of the BSOD here. I would be glad if I can be of any help to fix this.

[ external image ]

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 23, 2011 9:47 am
by EmuandCo
Hi, check this link: http://www.reactos.org/wiki/Debugging

We need the Serial Debug Output to be able to really help ya.

Strange... We tried the same with 0.3.13 and VBox 4.0.4 on CLT2011 and it worked flawless... except the locked resolution.

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 23, 2011 10:41 am
by Sof_T
I used to get bluescreens all the time with Additions. For a while now this has stopped happening for me, I've since upgraded to the latest vBox and still not experiencing this anymore. It used to happen after installation and then opening up a new window.

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 23, 2011 4:15 pm
by Haos
I am using guest addons all the time and dont have any issues, possibly its because i have VT-x enabled. Could you please confirm if your cpu supports it and if you enable it?

Re: Make VirtualBox compatibility a top priority

Posted: Sun Mar 27, 2011 7:56 am
by v_2samg
Sorry for the delayed response. But here are are couple of things that might be interesting.

@ Haos: It does not have VT-x, but it sure does have AMD-V. I believe VirtualBox supports both.

[ external image ]

As far as the settings are concerned, here it is...

General
Name: ReactOS
OS Type: Other Windows

System
Base Memory: 1024 MB
Processor(s): 1
Boot Order: Hard Disk, CD/DVD-ROM
VT-x/AMD-V: Enabled
Nested Paging: Enabled

Display
Video Memory: 128 MB
3D Acceleration: Enabled
2D Video Acceleration: Enabled
Remote Desktop Server: Disabled

Storage
IDE Controller
IDE Primary Master: ReactOS.vdi (Normal, 20.00 GB)
IDE Secondary Master (CD/DVD): VBoxGuestAdditions.iso (36.63 MB)

Audio
Host Driver: Windows DirectSound
Controller: ICH AC97

Network
Adapter 1: PCnet-FAST III (NAT)

Serial Ports
Disabled

USB
Device Filters: 0 (0 active)

Shared Folders
None

Runtime Attributes
Screen Resolution
640x480

VT-x/AMD-V
Enabled

Nested Paging
Enabled

Guest Additions
4.0.4 r70112

Guest OS Type
Windows 2003

Remote Desktop Server Port
Not Available

Storage Statistics
IDE Controller
IDE Primary Master:
DMA Transfers 589
PIO Transfers 19,697
Data Read 44,910,080 B
Data Written 0 B
IDE Secondary Master:
DMA Transfers 0
PIO Transfers 6
Data Read 0 B
Data Written 0 B

Network Statistics
Adapter 1
Data Transmitted 0 B
Data Received 0 B

Hope that helps.

Re: Make VirtualBox compatibility a top priority

Posted: Sun Mar 27, 2011 8:15 am
by v_2samg
@ EmuandCo: Ok. Here is the debug info I got off the COM1 port. Had to redirect VBOX COM1 to a raw file.

Code: Select all

(ntoskrnl\kd\kdio.c:298) -----------------------------------------------------
(ntoskrnl\kd\kdio.c:299) ReactOS 0.3.13 (Build 20110316-r51070)
(ntoskrnl\kd\kdio.c:300) Command Line: /DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS /KDSERIAL
(ntoskrnl\kd\kdio.c:304) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ multi(0)disk(0)rdisk(0)partition(1) \ReactOS\
(ntoskrnl\ke\i386\cpu.c:508) Supported CPU features : KF_V86_VIS KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE KF_MTRR KF_CMPXCHG8B KF_MMX KF_WORKING_PTE KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI KF_3DNOW  KF_XMMI64  KF_NX_BIT  
(ntoskrnl\ke\i386\cpu.c:815) Prefetch Cache: 64 bytes	L2 Cache: 524288 bytes	L2 Cache Line: 64 bytes	L2 Cache Associativity: 16
(ntoskrnl\mm\ARM3\mminit.c:1224) HAL I/O Mapping at FFFE0000 is unsafe
(ntoskrnl\ke\i386\kiinit.c:54) Large Page support detected but not yet taken advantage of
(ntoskrnl\ke\i386\patpge.c:46) Global page support detected but not yet taken advantage of
(ntoskrnl\ke\i386\patpge.c:60) PAT support detected but not yet taken advantage of
(ntoskrnl\ke\i386\cpu.c:1088) Support for SYSENTER detected.
(ntoskrnl\ke\i386\mtrr.c:25) MTRR support detected but not yet taken advantage of
(ntoskrnl\mm\mminit.c:243)           0x80000000 - 0x81000000	Boot Loaded Image
(ntoskrnl\mm\mminit.c:247)           0xB0000000 - 0xB0600000	PFN Database
(ntoskrnl\mm\mminit.c:251)           0xB0600000 - 0xB25B0000	ARM³ Non Paged Pool
(ntoskrnl\mm\mminit.c:255)           0xBC000000 - 0xBD000000	System View Space
(ntoskrnl\mm\mminit.c:259)           0xBD000000 - 0xC0000000	Session Space
(ntoskrnl\mm\mminit.c:262)           0xC0000000 - 0xC0300000	Page Tables
(ntoskrnl\mm\mminit.c:265)           0xC0300000 - 0xC0400000	Page Directories
(ntoskrnl\mm\mminit.c:268)           0xC0400000 - 0xC0800000	Hyperspace
(ntoskrnl\mm\mminit.c:272)           0xE1000000 - 0xF2400000	ARM³ Paged Pool
(ntoskrnl\mm\mminit.c:275)           0xF2400000 - 0xF7BE0000	System PTE Space
(ntoskrnl\mm\mminit.c:278)           0xF7BE0000 - 0xFFBE0000	Non Paged Pool Expansion PTE Space
(hal\halx86\generic\legacy\bussupp.c:620) Found parent bus (indicating PCI Bridge). PCI devices may fail!

====== PCI BUS HARDWARE DETECTION =======

00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
	Subsystem: Unknown [0000:0000]
	Flags: latency 0
	Device has Extended Address Decoding. It may fail to work on older BIOSes!

00:01.0 ISA bridge [0601]:  82371SB PIIX3 ISA [Natoma/Triton [8086:7000] (rev 00)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, medium devsel, latency 0

00:01.1 IDE interface [0101]:  82371SB PIIX3 IDE [Natoma/Triton [8086:7010] (rev 00)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, latency 0
	I/O ports at d000 [size=4K]

00:02.0 VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (rev 00)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, latency 0, IRQ 11
	Memory at e0000000 (32-bit, prefetchable) [size=512M]
	Device is using IRQ 11! ISA Cards using that IRQ may fail!

00:03.0 Ethernet controller [0200]: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] [1022:2000] (rev 40)
	Subsystem: PCnet - Fast 79C971 [1022:2000]
	Flags: bus master, medium devsel, latency 0, IRQ 10
	I/O ports at d020 [size=32]
	Memory at f0000000 (32-bit, non-prefetchable) [size=256M]
	Memory at f0080000 (32-bit, non-prefetchable) [size=512K]
	Device is using IRQ 10! ISA Cards using that IRQ may fail!

00:04.0 System peripheral [0880]: InnoTek Systemberatung GmbH VirtualBox Guest Service [80ee:cafe] (rev 00)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, latency 0, IRQ 09
	I/O ports at d040 [size=64]
	Memory at f0400000 (32-bit, non-prefetchable) [size=4M]
	Memory at f0800000 (32-bit, prefetchable) [size=8M]
	Device is using IRQ 9! ISA Cards using that IRQ may fail!

00:05.0 Multimedia audio controller [0401]: Intel Corporation 82801AA AC'97 Audio Controller [8086:2415] (rev 01)
	Subsystem: Terminator 2x/i [8086:0000]
	Flags: bus master, medium devsel, latency 0, IRQ 05
	I/O ports at d100 [size=256]
	I/O ports at d200 [size=512]
	Device is using IRQ 5! ISA Cards using that IRQ may fail!

00:06.0 USB Controller [0c03]: Apple Computer Inc. KeyLargo/Intrepid USB [106b:003f] (rev 00)
	Subsystem: GLoria L [0000:0000]
	Flags: bus master, latency 0, IRQ 11
	Memory at f0804000 (32-bit, non-prefetchable) [size=16K]
	Device is using IRQ 11! ISA Cards using that IRQ may fail!
	Device is an OHCI (USB) PCI Expansion Card. Turn off Legacy USB in your BIOS!

00:07.0 Secondary bus towards host CPU [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 08)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, medium devsel, latency 0, IRQ 09
	Device is using IRQ 9! ISA Cards using that IRQ may fail!

00:0b.0 USB Controller [0c03]:  82801FB/FBM/FR/FW/FRW (ICH6 Fami [8086:265c] (rev 00)
	Subsystem: Unknown [0000:0000]
	Flags: bus master, latency 0, IRQ 10
	Memory at f0805000 (32-bit, non-prefetchable) [size=4K]
	Device is using IRQ 10! ISA Cards using that IRQ may fail!
	Device is an Intel UHCI (USB) Controller. Turn off Legacy USB in your BIOS!

====== PCI BUS DETECTION COMPLETE =======

PC Compatible Eisa/Isa HAL Detected
(ntoskrnl\io\iomgr\iorsrce.c:882) IoReportResourceUsage is halfplemented!
(ntoskrnl\io\iomgr\iorsrce.c:882) IoReportResourceUsage is halfplemented!
(ntoskrnl\io\iomgr\driver.c:1540) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
(ntoskrnl\io\iomgr\iorsrce.c:725) Failed opening given symbolic link!
(ntoskrnl\io\pnpmgr\pnpmgr.c:1821) Root\*PNP0A00\0000 is using NULL driver
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\drivers\i8042prt.sys at F7A10000 with 11 pages
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\drivers\VBoxMouse.sys at F79FE000 with 12 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\mouclass.sys at F79F3000 with b pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\DRIVERS\pci.sys at F79E8000 with b pages
(ntoskrnl\io\pnpmgr\pnpmgr.c:1821) PCI\VEN_8086&DEV_7113&SUBSYS_00000000&REV_08\1&f103bba4&07 is using NULL driver
(ntoskrnl\io\pnpmgr\pnpmgr.c:1821) PCI\VEN_8086&DEV_7000&SUBSYS_00000000&REV_00\1&f103bba4&01 is using NULL driver
(ntoskrnl\io\pnpmgr\pnpmgr.c:1821) PCI\VEN_8086&DEV_1237&SUBSYS_00000000&REV_02\1&f103bba4&00 is using NULL driver
(ntoskrnl\io\pnpmgr\pnpmgr.c:1949) IopLoadServiceModule(usbehci) failed with status 0xc0000034
(ntoskrnl\io\pnpmgr\pnpmgr.c:1949) IopLoadServiceModule(usbohci) failed with status 0xc0000034
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\ALCXWDM.SYS at F79D0000 with 18 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\WMILIB.SYS at F79C9000 with 7 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\portcls.sys at F79A9000 with 20 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\ks.sys at F7986000 with 23 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\drmk.sys at F797F000 with 7 pages
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(drivers\bus\pci\pdo.c:1220) Assigning IRQ 5 to PCI device (5, 0)
(ntoskrnl\wmi\wmi.c:26) IoWMIRegistrationControl() called for DO B22E6278, requesting 1 action, returning success
(drivers\wdm\audio\backpln\portcls\interrupt.cpp:235) Vector 53 Level 22 Flags 0 Affinity 1
(drivers\wdm\audio\backpln\portcls\interrupt.cpp:249) CInterruptSync::Connect result 0
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(drivers\bus\pci\pdo.c:1220) Assigning IRQ 9 to PCI device (4, 0)
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\drivers\pcnet.sys at F6564000 with 9 pages
(drivers\network\ndis\ndis\miniport.c:2481)(NdisMRegisterMiniport) Initializing an NDIS 5.1 miniport
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(drivers\bus\pci\pdo.c:1220) Assigning IRQ a to PCI device (3, 0)
(drivers\network\ndis\ndis\config.c:485)(NdisReadConfiguration) ZwQueryValueKey #1 failed for NetworkAddress, status 0xc0000034
(drivers\network\ndis\ndis\config.c:700)(NdisReadNetworkAddress) NdisReadConfiguration failed (c0000001)
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\drivers\VBoxVideo.sys at F652D000 with 1c pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\drivers\VIDEOPRT.SYS at F651B000 with 12 pages
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(drivers\bus\pci\pdo.c:1220) Assigning IRQ b to PCI device (2, 0)
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(ntoskrnl\io\pnpmgr\pnpmgr.c:1949) IopLoadServiceModule(usbehci) failed with status 0xc0000034
(ntoskrnl\io\pnpmgr\pnpmgr.c:1949) IopLoadServiceModule(usbohci) failed with status 0xc0000034
(ntoskrnl\io\pnpmgr\pnpinit.c:318) IopOpenRegistryKeyEx() failed with Status C0000034
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\kbdclass.sys at F64FC000 with b pages
(ntoskrnl\io\pnpmgr\pnpmgr.c:1949) IopLoadServiceModule(usbehci) failed with status 0xc0000034
(ntoskrnl\io\pnpmgr\pnpmgr.c:1949) IopLoadServiceModule(usbohci) failed with status 0xc0000034
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\floppy.sys at F64EA000 with 12 pages
(ntoskrnl\io\iomgr\driver.c:1540) '\Driver\FLOPPY' initialization failed, status (0xc000000e)
(ntoskrnl\mm\ARM3\sysldr.c:929) Leaking driver: floppy.sys
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\cdrom.sys at F64D7000 with f pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\fs_rec.sys at F64CE000 with 9 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\usbdriver.sys at F64A0000 with 2e pages
wood_uhci: Entering DriverEntry(), RegistryPath=
    \Registry\Machine\System\CurrentControlSet\Services\USBDRIVER
ehci_alloc(): reg_path=0xf7a8c950, 
 			ehci_alloc(): PCIBus=0x5, bus=0x0, bus_addr=0x58 
 			ehci_alloc(): slot_num=0xb, &res_list=0xb21f8114 
 			ehci_alloc(): adapter=0xb21f8408 
ehci_alloc(): about to assign slot res
(hal\halx86\generic\legacy\bussupp.c:1149) Slot assignment for 5 on bus 0
(hal\halx86\generic\legacy\bus\pcibus.c:719) WARNING: PCI Slot Resource Assignment is FOOBAR
ehci_alloc(): address space=0x0
, reg_base=0xf0805000
ehci_alloc(): the int=0x3a
Found 1 EHCI controllers
Found 0 UHCI controllers
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\null.sys at F6487000 with 7 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\beep.sys at F6480000 with 7 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\blue.sys at F6478000 with 8 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\vbemp.sys at F6470000 with 8 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\npfs.sys at F6465000 with b pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\msfs.sys at F645E000 with 7 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\drivers\tcpip.sys at F6427000 with 37 pages
(drivers\network\ndis\ndis\protocol.c:1055)(ndisBindMiniportsToProtocol) TCPIP's BindAdapter handler returned 0x0 for \Device\{d31e2a80-5548-11e0-5f93-35d09cdd22c3}
Unhandled event type: 6
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\afd.sys at F640E000 with 15 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\system32\drivers\VBoxSF.sys at F63D6000 with 38 pages
(ntoskrnl\io\iomgr\file.c:420) Using IopParseDevice() hack. Requested invalid attributes: 1
(ntoskrnl\ex\init.c:1917) Free non-cache pages: 3c3b7
(./base/system/smss/initwkdll.c:195) NtOpenFile failed (Status c000003a)
(./base/system/smss/init.c:55) SM: InitSessionManager: failed to preload system DLLs (Status=c000003a)
Boot took 23691570728 cycles!
Interrupts: 705 System Calls: 6577 Context Switches: 446
(dll\ntdll\ldr\utils.c:2365) Relocating (400000 -> 00101000) C:\ReactOS\system32\csrsrv.dll
(ntoskrnl\ps\query.c:1163) Not implemented: ProcessBasePriority
(subsystems\win32\csrss\csrsrv\init.c:593) SM: CsrpLoadKernelModeDriver called
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SYSTEMROOT\system32\win32k.sys at F62C2000 with f8 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SYSTEMROOT\system32\ftfd.dll at F6261000 with 61 pages
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\kbdus.dll at F6259000 with 8 pages
(subsystems\win32\csrss\csrsrv\api\wapi.c:99) CSR: Unknown request type 0x10004
(dll\win32\kernel32\misc\dllmain.c:216) CSR Failed to give us a console
(subsystems\win32\win32k\main\dllmain.c:265) No Desktop handle for this Thread!
(subsystems\win32\win32k\ntuser\sysparams.c:1497) UserSystemParametersInfo called without active windowstation.
(subsystems\win32\win32k\ntuser\ntuser.c:144) Enter NtUserInitialize(0, 00000000, 00000000)
(subsystems\win32\win32k\ntuser\display.c:85) InitDisplayDriver(\Device\Video0, \Registry\Machine\System\CurrentControlSet\Services\VBoxVideo\Device0);
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\VBoxDisp.dll at F6228000 with 11 pages
(subsystems\win32\win32k\ntuser\display.c:85) InitDisplayDriver(\Device\Video1, \Registry\Machine\System\CurrentControlSet\Hardware Profiles\Current\System\CurrentControlSet\Services\VBE\Device0);
(ntoskrnl\mm\ARM3\sysldr.c:168) Loading: \SystemRoot\System32\framebuf.dll at F6220000 with 8 pages
err:(dll\win32\user32\misc\dllmain.c:369) GetConnected
(subsystems\win32\win32k\ntuser\hook.c:875) Kill Thread Hooks pti 0xb1dd3100 pdo 0x0
(subsystems\win32\win32k\main\dllmain.c:265) No Desktop handle for this Thread!
(subsystems\win32\win32k\ntuser\sysparams.c:1497) UserSystemParametersInfo called without active windowstation.
(dll\ntdll\ldr\utils.c:2365) Relocating (10000000 -> 01520000) C:\ReactOS\System32\VBoxMRXNP.dll
(ntoskrnl\mm\ARM3\syspte.c:257) MiReserveSystemPtes: Failed to reserve 32748 PTE(s)!
[7hEntered debugger on last-chance exception (Exception Code: 0xc0000005) (Page Fault)
Memory at 0x07FDC024 could not be written: Page not present.
kdb:> 

Re: Make VirtualBox compatibility a top priority

Posted: Sun Mar 27, 2011 12:23 pm
by Haos
Try decrasing video ram to a value below 64MB.

Re: Make VirtualBox compatibility a top priority

Posted: Mon Mar 28, 2011 4:00 am
by v_2samg
Try decrasing video ram to a value below 64MB.
Amazing. That helped. I set the video memory to 32 MB and now it works fine. Why didn't I think of that?!!! ;) But here is the thing... If i increase the video memory anywhere close to 60 MB or above, then the results are unpredictable. ReacOS may boot but freeze or go to a black screen. Setting the video memory anywhere >= 63 MB tiggers the blue screen that I posted earlier.

Re: Make VirtualBox compatibility a top priority

Posted: Mon Mar 28, 2011 11:11 pm
by Haos
63 MB should work fine, at least with VT-x enabled.

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 30, 2011 12:35 pm
by Technologov
+1.

I coming from VirtualBox community over here, and I hope that ReactOS will have closer cooperation with VirtualBox community.

I tried React OS 0.3.12 on VBox 4.0.4 on Windows 7 x64. (using VT-x)

What doesn't work:
1. Guest Additions Installer GUI is distorted (rendered incorrectly)
2. Shared Folder: ReactOS has necessary functionality for this?
What lacking? Network redirectors in ReactOS Explorer?
3. Seamless mode: Doesn't renders correctly. What is lacking ?
Answer: Dynamic resolution resizing. It is the basic building block for seamless mode.
3.a. Dynamic resolution resizing doesn't work either. ReactOS can support this ?
4. 3D Acceleration: OpenGL
4.a. TuxRacer doesn't even run giving me some error "The Memory could not be read"...
This is a pure ReactOS bug, and it happens even if no GuestAdditions installed.
4.b. Celestia - nothing rendered if 3D is enabled in VBox, giving error message if 3D is disabled in VBox saying that "VBoxOGL" cannot be loaded. In real Windows, this automatically fallbacks to software renderer.
4.c. Really Slick Screensaver:
Some don't work, even if no additions are installed: SkyRocket
With additions this locks up ReactOS, so I don't continue testing.

What works?
0. Guest Additions installer
1. Mouse integration

If you, dear ReactOS community, can fix the issues mentioned above, I will start testing ReactOS more seriously for every major VirtualBox version, and your ReactOS will be included into my OS coverage.

For now, you can see my work on VirtualBox, and enjoy test results with other OSes here.

-Technologov

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 30, 2011 12:57 pm
by gabrielilardi
Technologov wrote:I coming from VirtualBox community over here, and I hope that ReactOS will have closer cooperation with VirtualBox community.
Hi and welcome! I'm hoping that too. ;)
I tried React OS 0.3.12 on VBox 4.0.4 on Windows 7 x64. (using VT-x)
That's an old version, we have had several fixes after that (0.3.13, or even better: trunk (daily) revisions).

As for your points, I'll answer those I know something about:
1. Guest Additions Installer GUI is distorted (rendered incorrectly)
Every now and then there are graphic glitches, in general not only vbox related, they could be fixed by now, don't know for sure.
2. Shared Folder: ReactOS has necessary functionality for this?
What lacking? Network redirectors in ReactOS Explorer?
The only network support available in ReactOS is TCP/IP, the rest is lacking. It will take some time for this to happen.
3.a. Dynamic resolution resizing doesn't work either. ReactOS can support this ?
This has been implemented after the revision you tested. It's working now.
4.a. TuxRacer doesn't even run giving me some error "The Memory could not be read"...
This is a pure ReactOS bug, and it happens even if no GuestAdditions installed.
Indeed, this game was working, now it is not. It's a known issue (a regression), it's filed here.
4.b. Celestia - nothing rendered if 3D is enabled in VBox, giving error message if 3D is disabled in VBox saying that "VBoxOGL" cannot be loaded. In real Windows, this automatically fallbacks to software renderer.
4.c. Really Slick Screensaver:
Some don't work, even if no additions are installed: SkyRocket
With additions this locks up ReactOS, so I don't continue testing.
Don't know about this, perhaps one of our guys in win32k can enlighten us.
If you, dear ReactOS community, can fix the issues mentioned above, I will start testing ReactOS more seriously for every major VirtualBox version, and your ReactOS will be included into my OS coverage.
Thanks for testing ReactOS, I expect a lot of those issues to be fixed more or less "soon".

Re: Make VirtualBox compatibility a top priority

Posted: Wed Mar 30, 2011 12:59 pm
by Technologov
Is there "edit" button on this forum ? I *really* need it.

What doesn't work: (continued...)
5. Copy-paste (Host<->Guest):
Paste work, copy doesn't. I.e. you can paste data from host to ReactOS guest, but not vice-versa.
If one direction is working, making the other direction should be easy for a developer.
Can someone look into it?
6. Multi-Monitor: Not recognized. Is it even supported by ReactOS ?

-Technologov