I tried to reply and didn't noticed I wasn't logged in, so it started a new
thread. Can finally update you all!
So I have the engine installed to the node. For some reason, the node-engine
looks for certs in a different spot than the CentOS-engine. Soft linking, so
the cert is in both spots, le
> Perhaps you didn't comment-out/remove the 'includepkgs' line(s)?
Yep that did it. Thanks! It can't find dependent packages now, but I'm guessing
if I do the same for other repos, it'll find them.
> Just in case you want to have a look at the very old project I mentioned,
> it's here
I didn't
> How much? if it's just for development/testing, you can try as little as 2GB
That's still a lot for what my use-case is. I'd like the hypervisor as a whole
to take at most that much, if possible. This project is similar to QubesOS, so
I don't need to worry about moving the engine around later
I think my last reply got lost, but sorry if two appear here.
> Perhaps clarify your needs? Are you sure oVirt is the right solution?
The project I'm working on is similar to "QubesOS", so I don't need to move the
engine at all, but keeping this as light weight as possible is note-worthy. (I
wa
With this comment, I'm poking at getting the engine to run directly on the
node. I figure worst case, I might try throwing it in a container if there's
package conflicts. That'll at least give me the lighter-engine I'm looking for,
along with not having to manage it's resources.
Looks like the
Hi,
> ... You might want to check the list archives for previous discussions about
> this ...
Thanks for those links! I have an idea for a path forward, but I'm not sure
it's supported. It looks like oVirt used to have a "all-in-one" option, but the
hosted engine replaced that.
> I'd like to
Should have replied to the main thread before, my b.
Switching to centos 8 stream did the trick! I had to add the release44.rpm
again, but after the ovirt-hosted-engine-setupp.noarch install, I was able to
run `hosted-engine --deploy`!
Inside that hosted-engine command, the setup is failing at
Hi all,
The self-hosted you all provided definitely put me on the right track, thanks
for that!
> I presume you mean CentOS *8* stream??
I'm using the x86_64 CentOS 9 stream available here
https://www.centos.org/centos-stream/. Is only 8 supported? That explains the
next problem I'm having re
I'm trying to install both the oVirt engine (so I have the API), and hypervisor
on the same machine. I'm hoping I don't need cockpit, and I can write some
custom scripts to manage oVirt through the API. I tried a couple ways, and both
were blocked:
# on CentOS 9 stream, installing oVirt engine:
9 matches
Mail list logo