To add, it was pretty clear the VM never came up just by looking at top/htop.
qemu-kvm was using negligible (0.7% of a core) CPU. I'm 99% certain this is the
cause of my woes. Using Q35 with UEFI should be fine, as most systems are fine
booting from UEFI. However, I'd like to have the option to
OK, so how will I present secure VMs (i.e. VMs that live in secure,
protected networks) at unsecure locations once SPICE is gone? VNC and RDP
connect to the VM itself. SPICE connects to a TLS port on the hypervisor
which means we never expose the VM to the end users network and we have a
small
On Tuesday, 7 December 2021 09:03:17 CET david wrote:
> hello
> i'm adding a new host into ovirt
> after the installation procces is finished I got an error: "VDSM kvm6
> command ConnectStoragePoolVDS failed: Cannot find master domain".
> on the vdsm server in /dev/disk/by-path/ i see the block
I've been trying to get oVirt working for a week now with a self-hosted engine
setup. Eventually, today, I decided to try a standalone engine and see if I
can't at least get that to work, to maybe figure out what the issue is.
It seems the default chipset type is Q35 with BIOS. But it fails to
On Wed, Dec 8, 2021 at 8:44 AM wrote:
> 1. First node that was upgraded now continuously logs this error:
> VDSM command Get Host Statistics failed: Internal JSON-RPC
> error:
> {'reason': "'str' object has no attribute 'decode'"}
> 2. During import of two virtual machines from VMware (has done
On Wed, Dec 8, 2021 at 10:40 AM Arik Hadas wrote:
>
>
> On Wed, Dec 8, 2021 at 8:44 AM wrote:
>
>> 1. First node that was upgraded now continuously logs this error:
>> VDSM command Get Host Statistics failed: Internal JSON-RPC
>> error:
>> {'reason': "'str' object has no attribute 'decode'"}
On oVirt 4.3 I use noVNC , so console is reachable as long as you can reach the
engine.
Best Regards,Strahil Nikolov
On Wed, Dec 8, 2021 at 10:36, Colin Coe wrote:
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to
Yes. It appears CentOS Stream installs QEMU 6.1.0 when installing
ovirt-hosted-engine-setup.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/privacy-policy.html
"mediocre.slacker--- via Users" writes:
> To add, it was pretty clear the VM never came up just by looking at
> top/htop. qemu-kvm was using negligible (0.7% of a core) CPU. I'm 99%
> certain this is the cause of my woes. Using Q35 with UEFI should be
> fine, as most systems are fine booting
I did the update through the admin web console as that is where it typically
reports there are updates, even on node hosts.
For now I am going to re-install the node host from the ISO and not run updates
until someone confirms that qemu-kvm is fixed.
Gary
> On Dec 8, 2021, at 9:21 AM,
On Wed, Dec 8, 2021 at 6:50 PM Gary Pedretty wrote:
>
> So even the latest updated to qemu-kvm is still broken in regards to running
> VMs in Ovirt. I thought I would try Node on a new host and the current
> install iso, installs version 6.0 of kvm, which still works, but if you do an
>
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
Installing on CentOS 8.5 brings QEMU 6.0.
Guess we use CentOS until RHEL 8.6 is released, Rocky/Alma Linux update to 8.6,
and oVirt is viable on those distros.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to
CentOS Stream will install qemu 6.1, which will likely cause VMs failing to
boot (including hosted-engine) if they use Q35 BIOS. Q35 and i440fx worked, but
Q35 BIOS is the default when setting up hosted-engine and the VM failed to
start in stage 5 for me.
To get packages to update on CentOS
HI,
On Wed, December 8, 2021 1:16 am, cameronsplaze...@gmail.com wrote:
> 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
>
You mentioned "also tried wired connection". You should always use a wired
connection. Using a wireless connection is likely to give you lots of problems.
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Hi
Thanks for your answer.
All my VM's are already using i440fx (as Chipset/Firmware Type), and the
oVirt Engine runs on bare metal.
I was wondering if either CentOS Stream or Rocky/Alma would be more
stable in the future, in the context of oVirt + Gluster.
From you response, I am
So even the latest updated to qemu-kvm is still broken in regards to running
VMs in Ovirt. I thought I would try Node on a new host and the current install
iso, installs version 6.0 of kvm, which still works, but if you do an upgrade
on the node host it sill updates to the latest 6.1 version
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
On Tue, Dec 7, 2021 at 10:04 AM david wrote:
>
> hello
> i'm adding a new host into ovirt
> after the installation procces is finished I got an error: "VDSM kvm6 command
> ConnectStoragePoolVDS failed: Cannot find master domain".
> on the vdsm server in /dev/disk/by-path/ i see the block device
Hello,
I found some informations about an upcoming ovirt 4.5 release based on
centos stream 9. Considering that Centos stream 9 will not be stable
before months, can we expect new 4.4.x releases following 4.4.9?
--
Nathanaël Blanchet
Supervision réseau
SIRE
227 avenue
On Wed, Dec 8, 2021 at 10:15 PM wrote:
>
> 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`!
Glad to
On Wed, Dec 8, 2021 at 11:28 PM Nathanaël Blanchet wrote:
>
> Hello,
>
> I found some informations about an upcoming ovirt 4.5 release based on
> centos stream 9. Considering that Centos stream 9 will not be stable
> before months, can we expect new 4.4.x releases following 4.4.9?
4.4.10 is
You may want to consider using CentOS 8 until Rocky Linux gets to 8.6. When
RHEL 8.6 is released, advanced-virtualization should become available to
downstream distros, which will make it viable to install oVirt on Rocky Linux
etc. I personally had the best luck with CentOS 8. CentOS 8 uses
24 matches
Mail list logo
