----- Original Message ----- > From: "Dennis Jacobfeuerborn" <dennisml(a)conversis.de&gt; > To: "users" <users(a)ovirt.org&gt; > Sent: Wednesday, June 20, 2012 8:40:29 AM > Subject: [Users] Guest life-cycle > > Hi, > after being able to start my first guest I noticed two things: > 1) When I started the guest with the "run once" option the console > button > didn't become available. Navigating to another section of the GUI > and > back > didn't help. I was only able to make is available by closing the > browser > tab and then going to the admin portal again from scratch. there was an issue with the spice-xpi that was fixed in F17, I'd have to check to see if that made it to F16.

What OS are you on and what version of spice-xpi ? > > 2) When my guest froze (due to nested virtualization > experimentation > that > apparently doesn't work yet) I had no (obvious) way to kill the vm. > Hitting > the stop button apparently only sends a shutdown command but I > couldn't > find any way to issue a destroy command. Shutdown requires guest agent. If you right click on the VM you can do a stop - which forces it down. > After killing the qemu process on the host manually the guest in > the > portal > gui apparently went into an unknown "?" state which isn't > surprising > but > now there seems to be no way to get rid of the vm. > > What is proper way to get rid of such a misbehaving guest? > > Regards, > Dennis > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users

----- Original Message ----- > From: "Dennis Jacobfeuerborn" <dennisml(a)conversis.de&gt; > To: "users" <users(a)ovirt.org&gt; > Sent: Wednesday, June 20, 2012 8:40:29 AM > Subject: [Users] Guest life-cycle > > Hi, > after being able to start my first guest I noticed two things: > 1) When I started the guest with the "run once" option the console > button > didn't become available. Navigating to another section of the GUI and > back > didn't help. I was only able to make is available by closing the > browser > tab and then going to the admin portal again from scratch. there was an issue with the spice-xpi that was fixed in F17, I'd have to check to see if that made it to F16. What OS are you on and what version of spice-xpi ?

> > 2) When my guest froze (due to nested virtualization experimentation > that > apparently doesn't work yet) I had no (obvious) way to kill the vm. > Hitting > the stop button apparently only sends a shutdown command but I > couldn't > find any way to issue a destroy command. Shutdown requires guest agent. If you right click on the VM you can do a stop - which forces it down.

----- Original Message ----- > From: "Dennis Jacobfeuerborn" <dennisml(a)conversis.de&gt; > To: "Andrew Cathrow" <acathrow(a)redhat.com&gt; > Cc: "users" <users(a)ovirt.org&gt; > Sent: Wednesday, June 20, 2012 8:57:07 AM > Subject: Re: [Users] Guest life-cycle > > On 06/20/2012 02:45 PM, Andrew Cathrow wrote: >> >> >> ----- Original Message ----- >>> From: "Dennis Jacobfeuerborn" <dennisml(a)conversis.de&gt; >>> To: "users" <users(a)ovirt.org&gt; >>> Sent: Wednesday, June 20, 2012 8:40:29 AM >>> Subject: [Users] Guest life-cycle >>> >>> Hi, >>> after being able to start my first guest I noticed two things: >>> 1) When I started the guest with the "run once" option the console >>> button >>> didn't become available. Navigating to another section of the GUI >>> and >>> back >>> didn't help. I was only able to make is available by closing the >>> browser >>> tab and then going to the admin portal again from scratch. >> >> there was an issue with the spice-xpi that was fixed in F17, I'd >> have to check to see if that made it to F16. >> What OS are you on and what version of spice-xpi ? > > The client is on F15 with spice-xpi-2.7-1. Should this affect the > icon in > the gui though? I thought spice would only come into play once I > actually > click that button and start the console. It is an xpi issue. There's communication between the portal and the XPI regarding if a console is active. There was a bug in the older release of the XPI that meant that the status wasn't refreshed.