Hello,
I've somehow gotten one of my VMs stuck in a state that ovirt seems to be
rather confused about its
existence of now. I'm running oVirt 4.3.10 and using oVirt Node on all the
hosts.
My engine and host event logs are now filling up very rapidly with this error:
VDSM node217 command
My engine drop dead so had to create a new one and I'm trying to recover
virtual drives from previous engine. I'm using next instructions to import
storage domain
Hi Thomas,
the difference between paid solutions and oVirt is that the latter is free and
"supported" by volunteers and people that believe in open source.
If you need documentation that is missing , you are always welcome to write it
and share it with the rest of us.
Of course , both Red Hat
I'm replying to Thomas's thread below, but am creating a new subject so as not
to hijack the original thread.
I'm sure that this topic has come up before.
I first joined this list last fall, when I began planning and testing with
oVirt, but as of the past few weeks, I'm paying closer
Hi,
I recently tried out the vm console feature on an ovirt eval environment
running 4.4.4.7-1.el8:
1.) pasted the pub-key of my local user into the web interface (User->Options)
2.) connected via ssh like so
ssh -p sevm -l ovirt-vmconsole
3.) got the list of all the vm's :)
4.) choose a vm
5 matches
Mail list logo