Bug 1167922
| Summary: | p2v: No virtual console | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Richard W.M. Jones <rjones> |
| Component: | libguestfs | Assignee: | John Eckersberg <jeckersb> |
| Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.2 | CC: | dyuan, juzhou, mbooth, mzhan, ptoscano, rjones, tzheng, xiaodwan |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | P2V | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 06:57:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Richard W.M. Jones
2014-11-25 16:09:13 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. (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. 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. 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. 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). 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? 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. Refer to comment 9 and comment 10,move the bug to VERIFIED. 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 |