On Wed, Feb 25, 2009 at 9:45 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Wed, Feb 25, 2009 at 9:39 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
>> On Wed, Feb 25, 2009 at 8:49 AM, James Harper
>> <james.harper@xxxxxxxxxxxxxxxx> wrote:
>>>>
>>>> Should I try to capture some debug output using the virtual serial
>>> port
>>>> method?
>>>>
>>>
>>> It wouldn't hurt. Almost certainly it's going to be a bug in the gplpv
>>> drivers though, and given the unreleased changes since then I'm not sure
>>> how relevant the information will be.
>>>
>>> James
here we go, I restored the vm to freshly installed state, started the
debugger and installed Xen PV Drivers 0.9.12-pre15-dont-use.exe
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Opened \\.\com3
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Wed Feb 25
11:09:47.015 2009 (GMT+0)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrpamp.exe -
Windows XP Kernel Version 2600 MP (1 procs) Free x86 compatible
Built by: 2600.xpsp_sp2_rtm.040803-2158
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
System Uptime: not available
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5
XenPCI --> DriverEntry
XenPCI SystemStartOptions = N
XenPCI <-- DriverEntry
XenPCI --> XenPci_AddDevice
XenPCI IoRegisterDeviceInterface(GUID_XEN_IFACE) succeeded -
\??\PCI#VEN_5853&DEV_0001&SUBSYS_00015853&REV_01#3&267a616a&0&18#{5c568ac5-9ddf-4fa5-a94a-39d67077819c}\legacy
XenPCI IoRegisterDeviceInterface(GUID_XENBUS_IFACE) succeeded -
\??\PCI#VEN_5853&DEV_0001&SUBSYS_00015853&REV_01#3&267a616a&0&18#{14ce175a-3ee2-4fae-9252-00dbd84f018e}\xenbus
XenPCI <-- XenPci_AddDevice
XenPCI --> XenPci_Pnp_Fdo
XenPCI Unhandled Minor = 24
XenPCI <-- XenPci_Pnp_Fdo
XenPCI --> XenPci_Pnp_Fdo
XenPCI IRP_MN_FILTER_RESOURCE_REQUIREMENTS
XenPCI --> XenPci_Pnp_FilterResourceRequirements
XenPCI --> XenPci_SendAndWaitForIrp
XenPCI --> XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_SendAndWaitForIrp
XenPCI <-- XenPci_Pnp_FilterResourceRequirements
XenPCI --> XenPci_Pnp_FilterResourceRequirementsCallback
XenPCI <-- XenPci_Pnp_FilterResourceRequirementsCallback
XenPCI --> XenPci_Pnp_Fdo
XenPCI IRP_MN_START_DEVICE
XenPCI --> XenPci_Pnp_StartDevice
XenPCI --> XenPci_SendAndWaitForIrp
XenPCI --> XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_SendAndWaitForIrp
XenPCI irq_number = 01c
XenPCI IoPort Address(c000) Length: 256
XenPCI Private Data: 0x01 0x00 0x00
XenPCI Memory mapped CSR:(f2000000:0) Length:(16777216)
XenPCI Memory flags = 0004
XenPCI Private Data: 0x01 0x01 0x00
XenPCI irq_vector = 163
XenPCI irq_level = 005
XenPCI irq_mode = LevelSensitive
XenPCI ShareDisposition = CmResourceShareShared
XenPCI <-- XenPci_Pnp_StartDevice
XenPCI --> XenPci_Pnp_StartDeviceCallback
XenPCI --> XenPci_Init
XenPCI Xen Signature = Microsoft Hv, EAX = 0x40000005
XenPCI Hypercall area at 8633F148
XenPCI shared_info_area_unmapped.QuadPart = f2000000
XenPCI gpfn = f2000
*** Fatal System Error: 0x00000050
(0x8A01F311,0x00000001,0x8633F2E0,0x00000000)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrpamp.exe -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 50, {8a01f311, 1, 8633f2e0, 0}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Module load completed but symbols could not be loaded for
mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for xenpci.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : xenpci.sys ( xenpci+1ee0 )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8052a5d8 cc int 3
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: 8a01f311, memory referenced.
Arg2: 00000001, value 0 = read operation, 1 = write operation.
Arg3: 8633f2e0, If non-zero, the instruction address which referenced
the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ;
.reload' to set symbol path and load symbols.
MODULE_NAME: xenpci
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49707393
WRITE_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
8a01f311
FAULTING_IP:
+152952f00a0dfe0
8633f2e0 08ac32e1020004 or byte ptr [edx+esi+40002E1h],ch
MM_INTERNAL_CODE: 0
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x50
LAST_CONTROL_TRANSFER: from 804f96e8 to 8052a5d8
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f7a4c818 804f96e8 00000003 00000000 c04500f8 nt!DbgBreakPointWithStatus+0x4
f7a4cbf8 804f9c37 00000050 8a01f311 00000001
nt!KeRegisterBugCheckReasonCallback+0x77c
f7a4cc18 8051f478 00000050 8a01f311 00000001 nt!KeBugCheckEx+0x1b
f7a4cc80 80543568 00000001 8a01f311 00000000
nt!MmTrimAllSystemPagableMemory+0x6c2e
f7a4ccb4 80506ace 00000001 86099a30 863c1020 nt!Kei386EoiHelper+0x26cc
f7a4cd1c f60fcee0 8601f0d0 00000007 f7a4cd3c nt!MmMapIoSpace+0x18e
f7a4cd4c f60fcca4 8601f0d0 8601f0d0 00000000 xenpci+0x1ee0
f7a4cd68 805758ef 8601f018 8630d2f0 8056375c xenpci+0x1ca4
f7a4cd7c 80537757 86099a30 00000000 863c1020 nt!IoAttachDevice+0xab
f7a4cdac 805ce794 86099a30 00000000 00000000 nt!ExQueueWorkItem+0x1a3
f7a4cddc 805450ce 80537668 00000001 00000000
nt!PsRemoveCreateThreadNotifyRoutine+0x214
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x72e
STACK_COMMAND: kb
FOLLOWUP_IP:
xenpci+1ee0
f60fcee0 8945ec mov dword ptr [ebp-14h],eax
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: xenpci+1ee0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: xenpci.sys
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Interestingly this crash was error code 50, not 7E, I rebooted and
tried the install again:
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5
XenPCI --> DriverEntry
XenPCI SystemStartOptions = N
XenPCI <-- DriverEntry
XenPCI --> XenPci_AddDevice
XenPCI IoRegisterDeviceInterface(GUID_XEN_IFACE) succeeded -
\??\PCI#VEN_5853&DEV_0001&SUBSYS_00015853&REV_01#3&267a616a&0&18#{5c568ac5-9ddf-4fa5-a94a-39d67077819c}\legacy
XenPCI IoRegisterDeviceInterface(GUID_XENBUS_IFACE) succeeded -
\??\PCI#VEN_5853&DEV_0001&SUBSYS_00015853&REV_01#3&267a616a&0&18#{14ce175a-3ee2-4fae-9252-00dbd84f018e}\xenbus
XenPCI <-- XenPci_AddDevice
XenPCI --> XenPci_Pnp_Fdo
XenPCI Unhandled Minor = 24
XenPCI <-- XenPci_Pnp_Fdo
XenPCI --> XenPci_Pnp_Fdo
XenPCI IRP_MN_FILTER_RESOURCE_REQUIREMENTS
XenPCI --> XenPci_Pnp_FilterResourceRequirements
XenPCI --> XenPci_SendAndWaitForIrp
XenPCI --> XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_SendAndWaitForIrp
XenPCI <-- XenPci_Pnp_FilterResourceRequirements
XenPCI --> XenPci_Pnp_FilterResourceRequirementsCallback
XenPCI <-- XenPci_Pnp_FilterResourceRequirementsCallback
XenPCI --> XenPci_Pnp_Fdo
XenPCI IRP_MN_START_DEVICE
XenPCI --> XenPci_Pnp_StartDevice
XenPCI --> XenPci_SendAndWaitForIrp
XenPCI --> XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_Pnp_IoCompletion
XenPCI <-- XenPci_SendAndWaitForIrp
XenPCI irq_number = 01c
XenPCI IoPort Address(c000) Length: 256
XenPCI Private Data: 0x01 0x00 0x00
XenPCI Memory mapped CSR:(f2000000:0) Length:(16777216)
XenPCI Memory flags = 0004
XenPCI Private Data: 0x01 0x01 0x00
XenPCI irq_vector = 163
XenPCI irq_level = 005
XenPCI irq_mode = LevelSensitive
XenPCI ShareDisposition = CmResourceShareShared
XenPCI <-- XenPci_Pnp_StartDevice
XenPCI --> XenPci_Pnp_StartDeviceCallback
XenPCI --> XenPci_Init
XenPCI Xen Signature = Microsoft Hv, EAX = 0x40000005
XenPCI Hypercall area at 863D2CF8
XenPCI shared_info_area_unmapped.QuadPart = f2000000
XenPCI gpfn = f2000
*** Fatal System Error: 0x0000007e
(0xC0000005,0x863D2E97,0xF7A4CC44,0xF7A4C940)
Break instruction exception - code 80000003 (first chance)
A fatal system error has occurred.
Debugger entered on first try; Bugcheck callbacks have not been invoked.
A fatal system error has occurred.
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll
*** ERROR: Symbol file could not be found. Defaulted to export
symbols for ntkrpamp.exe -
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 7E, {c0000005, 863d2e97, f7a4cc44, f7a4c940}
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** ERROR: Module load completed but symbols could not be loaded for
mssmbios.sys
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
Probably caused by : xenpci.sys ( xenpci+1f55 )
Followup: MachineOwner
---------
nt!DbgBreakPointWithStatus+0x4:
8052a5d8 cc int 3
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 863d2e97, The address that the exception occurred at
Arg3: f7a4cc44, Exception Record Address
Arg4: f7a4c940, Context Record Address
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ;
.reload' to set symbol path and load symbols.
MODULE_NAME: xenpci
FAULTING_MODULE: 804d7000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 49707393
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx"
referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
+72e
863d2e97 0013 add byte ptr [ebx],dl
EXCEPTION_RECORD: f7a4cc44 -- (.exr 0xfffffffff7a4cc44)
ExceptionAddress: 863d2e97
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 00000001
Parameter[1]: 00000007
Attempt to write to address 00000007
CONTEXT: f7a4c940 -- (.cxr 0xfffffffff7a4c940)
eax=863d2e38 ebx=00000007 ecx=f7a4cd3c edx=00000018 esi=86092018 edi=860dc6f0
eip=863d2e97 esp=f7a4cd0c ebp=f7a4cd1c iopl=0 ov up ei ng nz ac pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010a96
863d2e97 0013 add byte ptr [ebx],dl ds:0023:00000007=??
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from f62b4f55 to 863d2e97
STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
f7a4cd08 f62b4f55 863c1020 0188e213 863d2cf8 0x863d2e97
f7a4cd1c f62b4ee0 860920d0 00000007 f7a4cd3c xenpci+0x1f55
f7a4cd4c f62b4ca4 860920d0 860920d0 00000000 xenpci+0x1ee0
f7a4cd68 805758ef 86092018 861f5728 8056375c xenpci+0x1ca4
f7a4cd7c 80537757 860dc6f0 00000000 863c1020 nt!IoAttachDevice+0xab
f7a4cdac 805ce794 860dc6f0 00000000 00000000 nt!ExQueueWorkItem+0x1a3
f7a4cddc 805450ce 80537668 00000001 00000000
nt!PsRemoveCreateThreadNotifyRoutine+0x214
00000000 00000000 00000000 00000000 00000000 nt!KiDispatchInterrupt+0x72e
FOLLOWUP_IP:
xenpci+1f55
f62b4f55 8945f8 mov dword ptr [ebp-8],eax
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: xenpci+1f55
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: xenpci.sys
STACK_COMMAND: .cxr 0xfffffffff7a4c940 ; kb
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
Andy
>>>
>>
>> I will give it a try, if only to get the debug tools setup ready for
>> testing your next release, I've already run into a problem as there is
>> only /dev/pts/0 on my system so xm console does not work:
>>
>> xm console xptest
>> xenconsole: Could not open tty `/dev/pts/1': No such file or directory
>>
>> ls /dev/pts/*
>> /dev/pts/0
>>
>> I will try to figure it out, just wondered if anybody else had run
>> into this problem?
>
> Fixed it, was missing legacy pty support.
>
> :)
>
> Andy
>>
>> Andy
>>
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home