RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1167922 - p2v: No virtual console
Summary: p2v: No virtual console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libguestfs
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: John Eckersberg
QA Contact: Virtualization Bugs
URL:
Whiteboard: P2V
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-25 16:09 UTC by Richard W.M. Jones
Modified: 2015-11-19 06:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 06:57:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2183 0 normal SHIPPED_LIVE libguestfs bug fix and enhancement update 2015-11-19 08:18:42 UTC

Description Richard W.M. Jones 2014-11-25 16:09:13 UTC
Description of problem:

There is no virtual console in the virt-p2v ISO.  One
consequence of this is that you cannot debug complex
problems because you can't get to a shell.

Version-Release number of selected component (if applicable):

virt-v2v 1.28.1

Comment 2 Richard W.M. Jones 2014-11-25 16:29:12 UTC
Background:

We have two scripts for building a bootable virt-p2v environment:

(1) https://github.com/libguestfs/libguestfs/blob/master/p2v/virt-p2v-make-disk.in

(2) https://github.com/libguestfs/libguestfs/blob/master/p2v/virt-p2v-make-kickstart.in
which uses https://github.com/libguestfs/libguestfs/blob/master/p2v/p2v.ks.in

Possibly (1) works (I didn't check), but definitely (2) doesn't work.
Somehow one or both need to be adjusted to create an extra virtual
console with a root bash prompt.

Comment 3 John Eckersberg 2014-12-16 21:15:10 UTC
(In reply to Richard W.M. Jones from comment #2)
> Background:
> 
> We have two scripts for building a bootable virt-p2v environment:
> 
> (1)
> https://github.com/libguestfs/libguestfs/blob/master/p2v/virt-p2v-make-disk.
> in
> 
> (2)
> https://github.com/libguestfs/libguestfs/blob/master/p2v/virt-p2v-make-
> kickstart.in
> which uses https://github.com/libguestfs/libguestfs/blob/master/p2v/p2v.ks.in
> 
> Possibly (1) works (I didn't check), but definitely (2) doesn't work.
> Somehow one or both need to be adjusted to create an extra virtual
> console with a root bash prompt.

This seems to be fixed upstream.

Building the ISO from source (or using http://oirase.annexia.org/virt-p2v/livecd-p2v-201412160442.iso), (2) works just fine for me.  On boot, virt-v2v is running on vt2, and switching over to vt1 (or any other) spawns a tty logged in as root.

Same thing if I build the disk image from (1) and boot it in qemu-kvm.

Comment 4 Richard W.M. Jones 2014-12-16 21:50:46 UTC
It may well be that I was trying to press [F2] ... [F7], but
I didn't think to try [F1].

I have just tried this with livecd-p2v-201412160442.iso (based
on Fedora 21, virt-p2v 1.29.17, built using kickstart) and
as you say [F1] works to give me a root shell.

Given that I'd say this bug is probably fixed, although the fact
that it's not obvious that the shell is on VC #1 might also count
as a usability bug.

What I'm going to do is push this bug to RHEL 7.2.  If no customer
complains within that timeframe then we're all good and can close
it upstream.

Comment 5 John Eckersberg 2014-12-16 22:05:50 UTC
I saw it come up on 3-7 as well, but for some reason there was a bit of a lag to it before it spawned.  Not more than 5-10 seconds, though.

Comment 7 Richard W.M. Jones 2015-05-19 16:16:20 UTC
This is working for me.

Unfortunately I'm still waiting on rel-eng to do something
about packaging P2V in RHEL 7.2 (engineering ticket 349453).

Comment 9 tingting zheng 2015-06-01 05:55:48 UTC
Tested with:
libguestfs-1.28.1-1.36.el7.x86_64
virt-v2v-1.28.1-1.36.el7.x86_64
livecd-p2v-201505191242.iso

Boot host from virt-p2v iso,after the virt-p2v client launched,press "Ctrl+Alt+F1,F3,F4,F5,F6" can enter console with root shell,when press "Ctrl+Alt+F2" can back to virt-p2v client GUI.

Is the above comments enough to move the bug to VERIFIED?

Comment 10 Richard W.M. Jones 2015-06-01 08:46:53 UTC
Yes as long as there are some virtual consoles, it can be
VERIFIED.

Unfortunately the precise virtual console that virt-p2v appears
on seems to be different depending on how we build the ISO (eg.
if we use virt-builder or build an ISO), making it difficult
to document this for users.

Comment 11 tingting zheng 2015-06-01 09:28:49 UTC
Refer to comment 9 and comment 10,move the bug to VERIFIED.

Comment 13 errata-xmlrpc 2015-11-19 06:57:56 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2183.html


Note You need to log in before you can comment on or make changes to this bug.