Libguestfs - Mar 2019 - few things I found about virt-p2v

Hi,

I spent the last few hours playing with virt-p2v, and here are few things
that I found, please tell me on which to submit a bug report:

   1. I created a boot image (without any parameters) and tested it using
   virt-manager. With QXL driver, when it loads the Xorg, it shows .. a blank
   screen (I tried it tens of times). With VirtIO it works.
   2. RHV-Upload -  I see that the functionality is there, but there is a
   missing field for password. Since I don't have oVirt installed at the
   moment, does it asks for the password from the user? could someone please
   add a box for this if the user chooses RHV-Upload?
   3. There network to connect to - I think GUI wise, that it's not
   understandable that you need to click the word "default" and change
the
   name manually. Perhaps change the name from "default" to something
like
   "Type Network Name"?
   4. Looks like there is no way to type a pool name to export to (if I
   select libvirt) or am I missing something? (let's say I have a pool
called
   NAS-10G). In the -os field I'm trying to put the NAS-10G (as the virt-v2v
   man page suggests), but this seems not work.
   5. Is there a way to access the ncurses mode? (for some really old
   machines who don't respect VESA).

Thanks,
Hetz

On Sat, Mar 30, 2019 at 02:56:10AM +0300, Hetz Ben Hamo
wrote:
> Hi,
> 
> I spent the last few hours playing with virt-p2v, and here are few things
> that I found, please tell me on which to submit a bug report:
> 
>    1. I created a boot image (without any parameters) and tested it using
>    virt-manager. With QXL driver, when it loads the Xorg, it shows .. a
blank
>    screen (I tried it tens of times). With VirtIO it works.
Unclear, you'd probably need to look at the logs from the virtual
machine to see what's going on.
>    2. RHV-Upload -  I see that the functionality is there, but there is a
>    missing field for password. Since I don't have oVirt installed at
the
>    moment, does it asks for the password from the user? could someone
please
>    add a box for this if the user chooses RHV-Upload?
rhv-upload from p2v is currently known to be broken:
https://bugzilla.redhat.com/show_bug.cgi?id=1603149

It may work using the kernel command line, but it's not really been
tested.
>    3. There network to connect to - I think GUI wise, that it's not
>    understandable that you need to click the word "default" and
change the
>    name manually. Perhaps change the name from "default" to
something like
>    "Type Network Name"?
Where exactly is this in the UI?
>    4. Looks like there is no way to type a pool name to export to (if I
>    select libvirt) or am I missing something? (let's say I have a pool
called
>    NAS-10G). In the -os field I'm trying to put the NAS-10G (as the
virt-v2v
>    man page suggests), but this seems not work.
Put the pool name into the storage (-os) field.
>    5. Is there a way to access the ncurses mode? (for some really old
>    machines who don't respect VESA).
No, but you can run virt-p2v automatically from the kernel command
line.  See the manual for an explanation.  There is no text UI mode,
nor is it ever planned.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top

[Please keep replies on the list]

On Sat, Mar 30, 2019 at 02:24:36PM +0300, Hetz Ben Hamo
wrote:
> > > I spent the last few hours playing with virt-p2v, and here are
few things
> > > that I found, please tell me on which to submit a bug report:
> > >
> > >    1. I created a boot image (without any parameters) and tested
it using
> > >    virt-manager. With QXL driver, when it loads the Xorg, it
shows .. a
> > blank
> > >    screen (I tried it tens of times). With VirtIO it works.
> >
> > Unclear, you'd probably need to look at the logs from the virtual
> > machine to see what's going on.
> >
> 
> I mean the screen is totally blank after it boots and tries to go to X. You
> cannot type or see anything. if you want, I can record a video and show it
> to you.
A video is not going to help.  Press the key to get to the console
after boot ([Alt]+[Ctrl]+[F2] or something similar) and have a look at
the journalctl output.
> > >    3. There network to connect to - I think GUI wise, that
it's not
> > >    understandable that you need to click the word
"default" and change
> > the
> > >    name manually. Perhaps change the name from
"default" to something
> > like
> > >    "Type Network Name"?
> >
> > Where exactly is this in the UI?
> >
> 
> In the right bottom side, where you see the nic MAC address and near it by
> default you see the word "Default".
I'm not exactly sure, but if it's the "Network interfaces"
section of
the second page of the wizard then that is the network that we try to
connect to.
> > >    4. Looks like there is no way to type a pool name to export to
(if I
> > >    select libvirt) or am I missing something? (let's say I
have a pool
> > called
> > >    NAS-10G). In the -os field I'm trying to put the NAS-10G
(as the
> > virt-v2v
> > >    man page suggests), but this seems not work.
> >
> > Put the pool name into the storage (-os) field.
> >
> 
> that's the problem. Once I remove the default "/var/tmp" and
try to put my
> pool name and starts the conversion, it thinks that I'm using the Local
> mode (and I selected the libvirt  mode) and when it finishes and it fails,
> the end of the log shows:
> 
> virt-v2v: error: -o libvirt: output pool ‘NAS-10G’ is not a directory
> (type='dir').  See virt-v2v-output-local(1)
It could well be a bug, but take a look at the virt-p2v logs which are
saved under /tmp/virt-p2v-* on the conversion server.  That will tell
you what exact command line was used.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html

On Sat, Mar 30, 2019 at 4:23 PM Richard W.M. Jones <rjones@redhat.com>
wrote:
> [Please keep replies on the list]
>
I wasn't approved yet by moderator ;)

> > > >    4. Looks like there is no way to type a pool name to
export to
> (if I
> > > >    select libvirt) or am I missing something? (let's say
I have a
> pool
> > > called
> > > >    NAS-10G). In the -os field I'm trying to put the
NAS-10G (as the
> > > virt-v2v
> > > >    man page suggests), but this seems not work.
> > >
> > > Put the pool name into the storage (-os) field.
> > >
> >
> > that's the problem. Once I remove the default "/var/tmp"
and try to put
> my
> > pool name and starts the conversion, it thinks that I'm using the
Local
> > mode (and I selected the libvirt  mode) and when it finishes and it
> fails,
> > the end of the log shows:
> >
> > virt-v2v: error: -o libvirt: output pool ‘NAS-10G’ is not a directory
> > (type='dir').  See virt-v2v-output-local(1)
>
> It could well be a bug, but take a look at the virt-p2v logs which are
> saved under /tmp/virt-p2v-* on the conversion server.  That will tell
> you what exact command line was used.
>
I did, and I'm enclosing gzipped copy of the file. Line 4197 clearly shows
it got the correct parameter:
Initializing the target -o libvirt -os NAS-10G

>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat
> http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-builder quickly builds VMs from scratch
> http://libguestfs.org/virt-builder.1.html
>