Bug 211624 - new vm wizard issues
Summary: new vm wizard issues
Status: CLOSED DUPLICATE of bug 220036
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Daniel Berrange
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-10-20 14:47 UTC by Matthias Clasen
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Clone Of:
Last Closed: 2006-12-19 21:22:16 UTC

Attachments (Terms of Use)

Description Matthias Clasen 2006-10-20 14:47:12 UTC
Sometimes when I press the "Finish" button, the graphical console does not come
up. The vm starts running ok though, and I can get the console by opening it
from virt-manager...

Also, I think the wizard window should close as soon as the window with the
progressbar comes up. Or at least it should become insensitive.

Comment 1 Daniel Berrange 2006-10-25 13:47:36 UTC
Change to disable sensisitivity during VM creation is upstream


Need to further investigate cause of console not always appearing.

Comment 2 Bernard Johnson 2006-12-03 05:24:41 UTC
Regarding the wizard window not closing:

I have the preference set to automatically open a new console on new domains.  I
don't get a console nor does the wizard close (in the normal failure mode - it
does work sometimes).  

I suspect that the console creation is throwing an error and it's being caught
further up (thus bypassing the window.close() statement).

Comment 3 Daniel Berrange 2006-12-03 14:46:43 UTC
Does the guest domain itself actually get created though, or has the guest
domain failed to start ? (If domain creation fails, then we delibrately don't
open the console window & leave the wizard visible)

If you can check /root/.virt-manager/virt-manager.log to see if there's any
errors that'd be helpful.

Comment 4 Bernard Johnson 2006-12-03 19:48:11 UTC
Yes, the guest is created and running.  If I double-click on the VMM display for
the host I just started, the console opens.

I should note that I first mistyped the install location and kickstart URLs the
first time I tried to create the domain.  Perhaps some status is getting left
over from that and then the next time I try it doesn't open a console.

Here is a failure to open the console when the the new domain is created.


Sun, 03 Dec 2006 12:35:18 DEBUG    Creating a VM KICKSTART
  UUID: f9a7e476-f55f-4865-8cbb-39e23df0d2e4
  Memory: 384
  # VCPUs: 1
  Filesize: 1.953125
  Disk image: /home/xen/KICKSTART.img
Sun, 03 Dec 2006 12:35:18 DEBUG    Starting background install process
Sun, 03 Dec 2006 12:35:19 DEBUG    Creating guest from '<domain type='xen'>
    <cmdline> method= 

    <disk type='file' device='disk'>
      <driver name='tap'/>
      <source file='/home/xen/KICKSTART.img'/>
      <target dev='xvda'/>

    <interface type='bridge'><source bridge='xenbr0'/><mac

    <graphics type='vnc' port='-1'/>
Sun, 03 Dec 2006 12:35:23 DEBUG    Saving XM config file '# Automatically
generated xen config file
name = "KICKSTART"
memory = "384"
disk = [ 'tap:aio:/home/xen/KICKSTART.img,xvda,w', ]
vif = [ 'mac=00:16:3e:18:6c:4c, bridge=xenbr0', ]
uuid = "f9a7e476-f55f-4865-8cbb-39e23df0d2e4"
on_reboot   = 'restart'
on_crash    = 'restart'
Sun, 03 Dec 2006 12:35:24 DEBUG    Install completed

Comment 5 Daniel Berrange 2006-12-19 21:22:16 UTC
Closing this bug a duplicate, because we've since successfully reproduced &
diagnosed this problem in bug 220036 (even though this bug was first, the other
has more details).

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

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