VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (892 - 894 of 16363)

Ticket Resolution Summary Owner Reporter
#1273 fixed serial ports problem Iakov Kaabak
Description

I am using VirtualBox 1.5.6 (VirtualBox_1.5.6-1_Win_x86.msi) on Windows XP. Guest system is Windows Server 2003 from en_windows_server_2003_with_sp1_enterprise.iso (MSDN). I configured virtual machine to have com port on Host Pipe, but it doesn't seem to work. When I look at guest's Device Manager, it shows no ports at all; when I look at its Resources view, it doesn't show serial port resources as used (standard COM1). I added COM2 to use physical port, and result is the same. On the other hand, when I run Process Explorer on host, it shows both handles as open by VirtualBox process.

So, the question is: how to have serial ports work? I really need only pipe (to connect WinDbg).

#15188 fixed serial port using tcp socket does not work in Windows host dldall
Description

VirtualBox can not create socket for uart in windows 7 32 bit host.

00:00:02.068779 Serial#0: emulating 16550A
00:00:02.068835 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Serial\DrvTCP.cpp(389) int __cdecl drvTCPConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VINF_SUCCESS
00:00:02.068838 VMSetError: DrvTCP#0 failed to create socket

the appropriate src file

/*
     * Create/Open the socket.
     */
    int s = socket(PF_INET, SOCK_STREAM, 0);
    if (s == -1)
        return PDMDrvHlpVMSetError(pDrvIns, RTErrConvertFromErrno(errno), RT_SRC_POS,
                                   N_("DrvTCP#%d failed to create socket"), pDrvIns->iInstance);

I have never seen socket(...) failed before and do not know the error source.

Some hints:
-) According MSDN you should not use "-1" in comparison, but rather defined constant INVALID_SOCKET (must not affect)
-) You should use WSAGetLastError instead of errno to get occured error description (winsock is not posix maybe)
-) You should not use 0 as protocol, but IPPROTO_TCP (must not affect)
-) You do wrong thread creation under Windows (runtime win library is not ready to accept new thread)
-) You do wrong import of std Windows functions, that are absent in real windows systems or your compiler has wrong socket implementation for windows.

I have no ideas how to solve the bug, but with the error it is impossible to use several uarts under windows host (single uart on single VM can be used with vmwaregateway tool).

As fast solution in other way than socket, there is vmwaregateway tool for TCP<->pipe bridge, if you can create the same tool with parameters (pipe_name, TCP_port); the uarts could be accessed via pipes.

PS:
more similar reports details listed in common forum topic
http://forums.virtualbox.org/viewtopic.php?p=355780#p355780

#2752 obsolete serial port in linux guest gives "serial8250: too much work for irq4" M. Schinkel
Description

With kernel 2.6.27.6 and a serial port enabled the following error message is given many times on the kernel log:

serial8250: too much work for irq4

A similar discussion related to qemu is here: http://kerneltrap.org/mailarchive/linux-kernel/2008/2/5/735714

The port works without problems.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy