(In reply to comment #0)
> When picking an ISO which is not known to libosinfo (this means autoinstall is
> not possible), the wizard goes straight from the iso selection step (I pick my
> isos from the file chooser) to starting the VM. It took me a bit of time to
> understand what was happening, and I'm wondering if we should have a "Summary"
> step in there before starting such images.

So you mean the VM didn't launch in fullscreen? That would be a bug/regression.

I mean it started right away, I didn't get the summary screen explaining me what was going to happen. As for going to fullscreen, I'd have to retest, at some point during my tests the screen just blinked but didn't end up in fullscreen, but I'm not positive this was with this particular test, nor with latest git.

(In reply to comment #2)
> I mean it started right away, I didn't get the summary screen explaining me
> what was going to happen.

If you choose an a live (unknown is treated the same) ISO, thats what is supposed to happen. This has been discussed to death already.


> As for going to fullscreen, I'd have to retest, at
> some point during my tests the screen just blinked but didn't end up in
> fullscreen, but I'm not positive this was with this particular test, nor with
> latest git.

Sure, please do file a bug when you manage to reproduce that.

(In reply to comment #3)
> (In reply to comment #2)
> > I mean it started right away, I didn't get the summary screen explaining me
> > what was going to happen.
> 
> If you choose an a live (unknown is treated the same) ISO, thats what is
> supposed to happen. This has been discussed to death already.

Although, I don't recall explicitely that live image should start right-away when they are selected in the wizard by hand.

(In reply to comment #4)
> (In reply to comment #3)
> > (In reply to comment #2)
> > > I mean it started right away, I didn't get the summary screen explaining me
> > > what was going to happen.
> > 
> > If you choose an a live (unknown is treated the same) ISO, thats what is
> > supposed to happen. This has been discussed to death already.
> 
> Although, I don't recall explicitely that live image should start right-away
> when they are selected in the wizard by hand.

Because we didn't think of 'selecting manually in wizard' as different case?

(In reply to comment #3)
> (In reply to comment #2)
> > I mean it started right away, I didn't get the summary screen explaining me
> > what was going to happen.
> 
> If you choose an a live (unknown is treated the same) ISO

For live images, I'd tend to think that a screen explaining what is going to happen (ie a review-like screen) before booting the image would be less surprising. You don't even get a chance to cancel the startup if you clicked on the wrong image. But if designers said it should be this way, fine with me

For unknown images (unknown == libosinfo only said the image is bootable), I strongly disagree for starting right away. Unknown means the image can be booted so it may be an installer, but we have absolutely no idea what this is. This means that we probably need user input about the size of the disk and the memory to use, at least we should give him a chance to tweak that before starting the VM, it will be very frustrating otherwise.

(In reply to comment #6)
> For unknown images (unknown == libosinfo only said the image is bootable), I
> strongly disagree for starting right away. Unknown means the image can be
> booted so it may be an installer, but we have absolutely no idea what this is.
> This means that we probably need user input about the size of the disk and the
> memory to use, at least we should give him a chance to tweak that before
> starting the VM, it will be very frustrating otherwise.

When its actually possible to tweak those props in summary page, we can discuss it then. :)

Yeah of course, instead of doing it now and getting this automatically when this is possible, let's not do anything, and then forget about it.

(In reply to comment #8)
> Yeah of course, instead of doing it now and getting this automatically when
> this is possible, let's not do anything, and then forget about it.

1. Its NOT possible at the moment.
2. Nobody has stopped you from providing patches if you think this is very easy.

(In reply to comment #9)
> (In reply to comment #8)
> > Yeah of course, instead of doing it now and getting this automatically when
> > this is possible, let's not do anything, and then forget about it.
> 
> 1. Its NOT possible at the moment.
> 2. Nobody has stopped you from providing patches if you think this is very
> easy.

3. Filing a bug about it would be a very easy way for us to not easily forget about this later.

*** This bug has been marked as a duplicate of bug 676676 ***