Custom Query (16363 matches)
Results (2017 - 2019 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1849 | fixed | direct COM port connection on solaris is not working => Fixed in SVN | ||
| Description |
when enabling COM port as Host Device on Solaris host machine in any Guest it prints out the error VERR_PDM_DRIVER_NOT_FOUND output of: #VBoxManage showvminfo test VirtualBox Command Line Management Interface Version 1.6.2 (C) 2005-2008 Sun Microsystems, Inc. All rights reserved. Name: test Guest OS: OpenSolaris UUID: dae0987b-2957-4aa5-d385-d80bf105d567 Config file: /root/.VirtualBox/Machines/test/test.xml Memory size: 512MB VRAM size: 8MB Boot menu mode: message and menu ACPI: on IOAPIC: off PAE: off Time offset: 0 ms Hardw. virt.ext: off State: powered off (since 2008-07-18T00:22:01.726000000) Monitor count: 1 Floppy: empty SATA: disabled Primary master: /root/.VirtualBox/VDI/test.vdi (UUID: 30f09791-8463-4312-3a96-ac7bbc53bb49) DVD: empty NIC 1: MAC: 00144FFFFFFE, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: Am79C973, Reported speed: 0 Mbps NIC 2: disabled NIC 3: disabled NIC 4: disabled UART 1: I/O base: 0x03f8, IRQ: 4, attached to device '/devices/isa/asy@1,3f8:a' UART 2: disabled Audio: disabled (Driver: Unknown, Controller: Unknown) Clipboard Mode: Bidirectional VRDP: disabled USB: disabled USB Device Filters: <none> Shared folders: <none> Guest: Statistics update: disabled important line: UART 1: I/O base: 0x03f8, IRQ: 4, attached to device '/devices/isa/asy@1,3f8:a' changing it to /dev/term/a or /dev/ttya doesn't help running as root also didn't help. Looks like it is not recognized on solaris. |
|||
| #4543 | obsolete | df command/process killed on SLES10 when using Shared Folders | ||
| Description |
I'm running VBox 3.0.2 with OpenSUSE 11.0@x86_64 as host and SLES10SP2@x86_64 as a guest and everytime I mount a shared folder I can't use the "df" command. It stops before printing information about the mounted shared folder. The last line printed on console is: "Finished (killed)". |
|||
| #11991 | obsolete | detected INFACHE inconsistency after VirtualBox update | ||
| Description |
Hallo, it is now the second time, that I have for severals days and ongoing days an "detected INFCACHE inconsitency". This first time I have no idea why and from where it comes. But today I checked the date for the first event of this kind in file "C:\Windows\inf\setupapi.app.log". It was the date of installing / updating VirtualBox software (from version 4.2.12 to version 4.2.16). The INFCACHE inconsitency corrensponds with the driver installation of VirtualBox Network Interface(s) ([DIF_PROPERTYCHANGE - ROOT\SUN_VBOXNETFLTMP\0000]]) and the RRNETCAP driver from software "AUDIALS ONE 10" (Build Driver List - ROOT\RS_RRNETCAPMP\0005]) [code]>> [Build Driver List - ROOT\RS_RRNETCAPMP\0005]
! inf: Detected INFCACHE inconsistencycode Uninstallation of RRNETCAP driver and also VB and reinstallation of both, does not repair INFCACHE for all time, just temporarly: ! inf: Attempting INFCACHE repair 20:07:30.741 ! inf: Verify/Fix on INFCACHE complete, status(4) - Fixed 20:07:49.488 on next driver installation the error "detected INFACHE inconsistency" arises again. I think there are some dependency between drivers of VirtualBox and RRNETCAP, and if I uninstall only one of them for reinstallation, the registry settings under "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\SUN_VBOXNETFLTMP" or "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\RRNETCAPMP" becomes wrong. I saw in VBOX.log also an error for USB. May USB Driver for VB is also affected by INFCACHE inconsisteny. Symtoms in running VMs are frozen VMs and a 15 minutes work of process "SYSTEM" on startup of OS (Windows 7), which tries to repair driver installation and causes heavy CPU load at startup, so I cannot work with computer for this 15 minutes. helfrw |
|||

