serial port: failed to create named pipe

Discussions related to using VirtualBox on Windows hosts.

serial port: failed to create named pipe

Postby askb » 9. Oct 2011, 04:55

Greetings,

I am trying to setup a serial port between my VM's for kernel debugging. However, I get the failed to create a named pipe error every time the VM (RHEL6) boot is initiated .

Could not find much information googling, if its a known issue.

Following were the options:

Host OS: Win7 - x86_64
VM / Guest: RHEL6 - x86_64

Port Num: COM1 IRQ: 4 I/O Port: 0x3F8
Port Mode: Host Pipe
"Checked" the create pipe option
File Path: C:\Temp\vbox1

Appreciate and help! Please let me know if I could provide further information.

Error Message as seen on the dialog box window:

Failed to open a session for the virtual machine RHEL6_1 Clone.

NamedPipe#0 failed to create named pipe C:\Temp\vbox1 (VERR_INVALID_NAME).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {1968b7d3-e3bf-4ceb-99e0-cb7c913317bb}


LOGS ON MY WIN7 HOST:
VirtualBox (XP)COM Server 4.1.2 r73507 win.amd64 (Aug 15 2011 14:29:50) release log
00:00:00.000 main Log opened 2011-10-09T01:36:43.074970200Z
00:00:00.000 main OS Product: Windows 7
00:00:00.000 main OS Release: 6.1.7601
00:00:00.000 main Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.000 main Process ID: 5228
00:00:00.000 main Package type: WINDOWS_64BITS_GENERIC
00:00:00.016 Loading settings file "C:\Users\belura/.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.484 VDInit finished
00:00:00.484 Loading settings file "C:\Users\belura\VirtualBox VMs\RHEL6_1\RHEL6_1.vbox" with version "1.12-windows"
00:00:00.484 Loading settings file "C:\Users\belura\VirtualBox VMs\RHEL6_1 Clone\RHEL6_1 Clone.vbox" with version "1.12-windows"
00:00:05.585 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:00:05.975 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:00:42.089 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:00:42.464 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:00:58.501 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:00:58.891 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:11:59.882 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={Could not find a registered machine named '--uart1'}, preserve=false
00:12:27.354 ERROR [COM]: aRC=VBOX_E_OBJECT_NOT_FOUND (0x80bb0001) aIID={c28be65f-1a8f-43b4-81f1-eb60cb516e66} aComponent={VirtualBox} aText={Could not find a registered machine named '--uart'}, preserve=false
00:15:45.148 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:15:45.522 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:18:30.665 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:18:31.039 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:18:45.438 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:18:45.813 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false
00:24:13.446 ERROR [COM]: aRC=VBOX_E_INVALID_VM_STATE (0x80bb0002) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={Machine} aText={Machine is not locked for session (session state: Unlocked)}, preserve=false
00:24:13.805 ERROR [COM]: aRC=VBOX_E_IPRT_ERROR (0x80bb0005) aIID={5eaa9319-62fc-4b0a-843c-0cb1940f8a91} aComponent={SessionMachine} aText={Saved screenshot data is not available (VERR_NOT_SUPPORTED)}, preserve=false

Thanks in advance.
askb
 
Posts: 2
Joined: 9. Oct 2011, 04:34
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: RHEL6

Re: serial port: failed to create named pipe

Postby askb » 12. Oct 2011, 14:09

Hi Forum members and experts,

I tried upgrading to 4.1.4, and the same issue seems to persist.

Has others been facing similar issues ?

Thanks in advace, askb
askb
 
Posts: 2
Joined: 9. Oct 2011, 04:34
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: RHEL6

Re: serial port: failed to create named pipe

Postby shivesh » 28. Jan 2012, 15:06

This is an old post however, I would still post a followup comment on this one:

Have you made sure that you are specifying the pipe name in the format: \\.\pipe\<pipe_name>

PIPE name can be anything which we can associate to the vm, e.g., winxp, or anything else. You may get this error if the format is not correct, for instance, a backslash missing.
shivesh
 
Posts: 1
Joined: 28. Jan 2012, 14:59
Primary OS: MS Windows 7
VBox Version: OSE other
Guest OSses: windows xp

Re: serial port: failed to create named pipe

Postby osovitskiy » 14. Mar 2012, 13:30

shivesh wrote:Have you made sure that you are specifying the pipe name in the format: \\.\pipe\<pipe_name>
PIPE name can be anything which we can associate to the vm, e.g., winxp, or anything else. You may get this error if the format is not correct, for instance, a backslash missing.


Oh man, thank you very much! You are my hero! It works like a charm!
I spend a lot of time trying to understand how to name pipes in Windows. This info should be in the context help in GUI when one choses name for a pipe.
Yours faithfully,
Oleg Osovitskiy
osovitskiy
 
Posts: 1
Joined: 14. Mar 2012, 13:27
Location: Kaliningrad, Russia
Primary OS: Linux other
VBox Version: PUEL
Guest OSses: QNX4,QNX6,Linux,Windows,FreeBSD,Solaris


Return to VirtualBox on Windows Hosts

Who is online

Users browsing this forum: noteirak and 40 guests