Bug 723948

Summary:	P2V debugging section
Product:	Red Hat Enterprise Linux 6	Reporter:	Matthew Booth <mbooth>
Component:	doc-V2V_Guide	Assignee:	Laura Bailey <lbailey>
Status:	CLOSED NEXTRELEASE	QA Contact:	ecs-bugs
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	thildred
Target Milestone:	rc	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-10-31 01:08:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Deadline:	2011-10-28

Description Matthew Booth 2011-07-21 15:51:11 UTC

I think it's worth adding a section on debugging.

There are 3 interesting areas where engineering/support might want to get more information from a failing P2V client:

1. The image fails to boot

I don't have a good story for this. Do we have anything similar documented elsewhere?

2. The image fails to launch the P2V client

In this case, the image will present the option to Try Again/Debug/Power Off. Debug will drop them into a shell and point them at the xinit logs.

3. The P2V client crashes

In this case, the user will be presented with the same options to Try Again/Debug/Power Off, but in this case without dropping out of X. Debug will again drop them into a shell and point them at a log file containing the output of virt-p2v. The image will include ssh and scp to assist getting log files off the box.