[ovirt-users] unable to start VMs after upgrade

[Jim Kusznir]

Well, it turned out it was 100% of one core, percentage reported took into
account how many cores the VM had assigned.  Rebooting the node did fix the
problem.

Just to be clear, the "proper" procedure for rebooting a host in oVirt is
to put it in maintence mode, ssh to the node, issue the reboot, then after
confirming its back up, right click on the node in the web UI and select
"confirm node reboot", then take it out of maintence mode?

--Jim

On Sun, Jan 8, 2017 at 9:10 AM, Robert Story <rstory at tislabs.com> wrote:

> On Sat, 7 Jan 2017 15:02:10 -0800 Jim wrote:
> JK> I went on about the work I came in to do, and tried to start up a VM.
> It
> JK> appeared to start, but it never booted.  It did  raise the CPU usage
> for
> JK> that VM, but console was all black, no resize or anything.  Tried
> several
> JK> settings.  This was on a VM I had just powered down.  I noticed it was
> JK> starting the VM on engine3, so I did a runonce specifying the vm start
> on
> JK> engine2.  Booted up just fine.  After booting, I could migrate to
> engine3,
> JK> and all was good.
> JK>
> JK> What happened?  I get no error messages, starting any vm on engine3,
> start
> JK> paused, attaching display, then running it, I always get the same
> thing:
> JK> blank console, about 50% cpu usage reported by the web interface, no
> JK> response on any network, and by all signs available to me, no actual
> JK> booting (reminds me of a PC that doesn't POST).  Simply changing the
> engine
> JK> it starts on to one that has not been upgraded fixes the problem.
>
> I had this issue too, except I had 100% cpu usage reported on the web
> interface. have you rebooted the troublesome host since it was upgraded? I
> think that was what solved it for me.
>
>
> Robert
>
> --
> Senior Software Engineer @ Parsons
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20170108/c1ee8f46/attachment.html>