Hi List,
I receive the following error while starting some of our VMs after the
upgrade to 4.4.10.
VM v4-probe is down with error. Exit message: internal error: process
exited while connecting to monitor: 2022-03-24T11:27:23.098838Z
qemu-kvm: -blockdev
On Sun, 8 Jan 2017 18:15:27 -0800 Jim wrote:
JK> Just to be clear, the "proper" procedure for rebooting a host in oVirt is
JK> to put it in maintence mode, ssh to the node, issue the reboot, then after
JK> confirming its back up, right click on the node in the web UI and select
JK> "confirm node
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,
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
Hello:
I'm still fairly new to ovirt. I'm running a 3-node cluster largely built
by Jason Brooks' howto for ovirt+gluster on the contributed docs section of
the ovirt webpage.
I had everything mostly working, and this morning when I logged in, I saw a
new symbol attached to all three of my
5 matches
Mail list logo