[ovirt-users] Re: Hosted Engine stuck in bios
> On Jan 22, 2021, at 10:11, Arik Hadas wrote:
>
> On Thu, Jan 21, 2021 at 9:27 PM Joseph Gelinas wrote:
> I found `engine-setup
> --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1]
> and now have the ovirt-engine web interface reachable again. But do have one
> more question; when I try to change the Custom Chipset/Firmware Type to Q35
> Chipset with BIOS, I get the error; HostedEngine: There was an attempt to
> change the Hosted Engine VM values that are locked.
>
> How do I make the removal of the loader/nvram lines permanent?
>
> Can you please check the output of:
> select custom_bios_type from vm_static where origin=6;
>
> If it returns 0 then you can change the custom bios type to Q35 + BIOS with:
> update vm_static set custom_bios_type = 2, db_generation = db_generation + 1
> where origin = 6;
>
> If it returns 2 as it is supposed to, you can change any field of the hosted
> engine VM (e.g., "comment") via the UI to trigger an update of the OVF_STORE.
That did indeed return 0. Thanks for your help Arik.
>
> [1]
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/2AC57LTHFKJBU6OYZPYSCMTBF6NE3QO2/
>
> > On Jan 21, 2021, at 10:15, Joseph Gelinas wrote:
> >
> > Removing those two lines got the hosted engine vm booting again, so that is
> > a great help. Thank you.
> >
> > Now I just need the web interface of ovirt-engine to work again. I feel
> > like I might have run things out of order and forgot to do `engine-setup`
> > as part of the update of hosted engine. Though when I try to do that now it
> > bails out claiming the cluster isn't in global maintenance yet it is.
> >
> > [ INFO ] Stage: Setup validation
> > [ ERROR ] It seems that you are running your engine inside of the
> > hosted-engine VM and are not in "Global Maintenance" mode.
> > In that case you should put the system into the "Global
> > Maintenance" mode before running engine-setup, or the hosted-engine HA
> > agent might kill the machine, which might corrupt your data.
> >
> > [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup
> > detected, but Global Maintenance is not set.
> >
> >
> > I see engine.log says it can't contact the database but I certainly see
> > Postgres processes running.
> >
> > /var/log/ovirt-engine/engine.log
> >
> > 2021-01-21 14:47:31,502Z ERROR
> > [org.ovirt.engine.core.services.HealthStatus] (default task-15) [] Failed
> > to run Health Status.
> > 2021-01-21 14:47:31,502Z ERROR
> > [org.ovirt.engine.core.services.HealthStatus] (default task-14) [] Unable
> > to contact Database!: java.lang.InterruptedException
> >
> >
> >
> >
> >> On Jan 21, 2021, at 03:19, Arik Hadas wrote:
> >>
> >>
> >>
> >> On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas wrote:
> >> Hi,
> >>
> >> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> >> setting the default datacenter from 4.4 to 4.5 and making the default bios
> >> q35+eufi. Unfortunately quite a few things. Now however hosted engine
> >> doesn't boot up anymore and `hosted-engine --console` just shows the
> >> below bios/firmware output:
> >>
> >> RHEL
> >>
> >> RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
> >>
> >> 0.0.0 16384 MB RAM
> >>
> >>
> >>
> >>
> >> Select Language This is the option
> >>
> >> one adjusts to
> >> change
> >>> Device Managerthe language for
> >>> the
> >>> Boot Manager current system
> >>>
> >>> Boot Maintenance Manager
> >>>
> >>
> >> Continue
> >>
> >> Reset
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> ^v=Move Highlight =Select Entry
> >>
> >>
> >>
> >> When in this state `hosted-engine --vm-status` says it is up but failed
> >> liveliness check
> >>
> >> hosted-engine --vm-status | grep -i engine\ status
> >> Engine status : {"vm": "down", "health": "bad",
> >> "detail": "unknown", "reason": "vm not running on this host"}
> >> Engine status : {"vm": "up", "health": "bad",
> >> "detail": "Up", "reason": "failed liveliness check"}
> >> Engine status : {"vm": "down", "health": "bad",
> >> "detail": "Down", "reason": "bad vm status"}
> >>
> >> I assume I am running into https://access.redhat.com/solutions/5341561
> >> (RHV: Hosted-Engine VM fails to start after changing the cluster to
> >> Q35/UEFI) however how to fix that isn't real
[ovirt-users] Re: Hosted Engine stuck in bios
On Thu, Jan 21, 2021 at 9:27 PM Joseph Gelinas wrote:
> I found `engine-setup
> --otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1]
> and now have the ovirt-engine web interface reachable again. But do have
> one more question; when I try to change the Custom Chipset/Firmware Type to
> Q35 Chipset with BIOS, I get the error; HostedEngine: There was an attempt
> to change the Hosted Engine VM values that are locked.
>
> How do I make the removal of the loader/nvram lines permanent?
>
Can you please check the output of:
select custom_bios_type from vm_static where origin=6;
If it returns 0 then you can change the custom bios type to Q35 + BIOS with:
update vm_static set custom_bios_type = 2, db_generation = db_generation +
1 where origin = 6;
If it returns 2 as it is supposed to, you can change any field of the
hosted engine VM (e.g., "comment") via the UI to trigger an update of the
OVF_STORE.
>
> [1]
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/2AC57LTHFKJBU6OYZPYSCMTBF6NE3QO2/
>
> > On Jan 21, 2021, at 10:15, Joseph Gelinas wrote:
> >
> > Removing those two lines got the hosted engine vm booting again, so that
> is a great help. Thank you.
> >
> > Now I just need the web interface of ovirt-engine to work again. I feel
> like I might have run things out of order and forgot to do `engine-setup`
> as part of the update of hosted engine. Though when I try to do that now it
> bails out claiming the cluster isn't in global maintenance yet it is.
> >
> > [ INFO ] Stage: Setup validation
> > [ ERROR ] It seems that you are running your engine inside of the
> hosted-engine VM and are not in "Global Maintenance" mode.
> > In that case you should put the system into the "Global
> Maintenance" mode before running engine-setup, or the hosted-engine HA
> agent might kill the machine, which might corrupt your data.
> >
> > [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine
> setup detected, but Global Maintenance is not set.
> >
> >
> > I see engine.log says it can't contact the database but I certainly see
> Postgres processes running.
> >
> > /var/log/ovirt-engine/engine.log
> >
> > 2021-01-21 14:47:31,502Z ERROR
> [org.ovirt.engine.core.services.HealthStatus] (default task-15) [] Failed
> to run Health Status.
> > 2021-01-21 14:47:31,502Z ERROR
> [org.ovirt.engine.core.services.HealthStatus] (default task-14) [] Unable
> to contact Database!: java.lang.InterruptedException
> >
> >
> >
> >
> >> On Jan 21, 2021, at 03:19, Arik Hadas wrote:
> >>
> >>
> >>
> >> On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas
> wrote:
> >> Hi,
> >>
> >> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> setting the default datacenter from 4.4 to 4.5 and making the default bios
> q35+eufi. Unfortunately quite a few things. Now however hosted engine
> doesn't boot up anymore and `hosted-engine --console` just shows the below
> bios/firmware output:
> >>
> >> RHEL
>
> >> RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
>
> >> 0.0.0 16384 MB RAM
>
> >>
> >>
> >>
> >> Select Language This is the
> option
> >> one adjusts to
> change
> >>> Device Managerthe language for
> the
> >>> Boot Manager current system
>
> >>> Boot Maintenance Manager
>
> >>
> >> Continue
>
> >> Reset
>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> ^v=Move Highlight =Select Entry
>
> >>
> >>
> >> When in this state `hosted-engine --vm-status` says it is up but failed
> liveliness check
> >>
> >> hosted-engine --vm-status | grep -i engine\ status
> >> Engine status : {"vm": "down", "health": "bad",
> "detail": "unknown", "reason": "vm not running on this host"}
> >> Engine status : {"vm": "up", "health": "bad",
> "detail": "Up", "reason": "failed liveliness check"}
> >> Engine status : {"vm": "down", "health": "bad",
> "detail": "Down", "reason": "bad vm status"}
> >>
> >> I assume I am running into https://access.redhat.com/solutions/5341561
> (RHV: Hosted-Engine VM fails to start after changing the cluster to
> Q35/UEFI) however how to fix that isn't really described. I have tried
> starting hosted engine paused (`hosted-engine --vm-start-paused`) and
> editing the config (`virsh -c
> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit
> HostedEngine`) to have pc-i440fx instead and removing a bunch of pcie lines
> etc until it will accept the config and then resuming hosted engine (`virsh
> -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume
> HostedEngine`) but haven't come up with something that is able to start.
> >>
> >> Anyone know how to resolve this? Am I even chasing the right path?
> >>
> >> Let's start with the negative - this should have
[ovirt-users] Re: Hosted Engine stuck in bios
I found `engine-setup
--otopi-environment=OVESETUP_CONFIG/continueSetupOnHEVM=bool:True` from [1] and
now have the ovirt-engine web interface reachable again. But do have one more
question; when I try to change the Custom Chipset/Firmware Type to Q35 Chipset
with BIOS, I get the error; HostedEngine: There was an attempt to change the
Hosted Engine VM values that are locked.
How do I make the removal of the loader/nvram lines permanent?
[1]
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/2AC57LTHFKJBU6OYZPYSCMTBF6NE3QO2/
> On Jan 21, 2021, at 10:15, Joseph Gelinas wrote:
>
> Removing those two lines got the hosted engine vm booting again, so that is a
> great help. Thank you.
>
> Now I just need the web interface of ovirt-engine to work again. I feel like
> I might have run things out of order and forgot to do `engine-setup` as part
> of the update of hosted engine. Though when I try to do that now it bails out
> claiming the cluster isn't in global maintenance yet it is.
>
> [ INFO ] Stage: Setup validation
> [ ERROR ] It seems that you are running your engine inside of the
> hosted-engine VM and are not in "Global Maintenance" mode.
> In that case you should put the system into the "Global Maintenance"
> mode before running engine-setup, or the hosted-engine HA agent might kill
> the machine, which might corrupt your data.
>
> [ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup
> detected, but Global Maintenance is not set.
>
>
> I see engine.log says it can't contact the database but I certainly see
> Postgres processes running.
>
> /var/log/ovirt-engine/engine.log
>
> 2021-01-21 14:47:31,502Z ERROR [org.ovirt.engine.core.services.HealthStatus]
> (default task-15) [] Failed to run Health Status.
> 2021-01-21 14:47:31,502Z ERROR [org.ovirt.engine.core.services.HealthStatus]
> (default task-14) [] Unable to contact Database!:
> java.lang.InterruptedException
>
>
>
>
>> On Jan 21, 2021, at 03:19, Arik Hadas wrote:
>>
>>
>>
>> On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas wrote:
>> Hi,
>>
>> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
>> setting the default datacenter from 4.4 to 4.5 and making the default bios
>> q35+eufi. Unfortunately quite a few things. Now however hosted engine
>> doesn't boot up anymore and `hosted-engine --console` just shows the below
>> bios/firmware output:
>>
>> RHEL
>>
>> RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
>>
>> 0.0.0 16384 MB RAM
>>
>>
>>
>>
>> Select Language This is the option
>>
>> one adjusts to
>> change
>>> Device Managerthe language for the
>>>
>>> Boot Manager current system
>>>
>>> Boot Maintenance Manager
>>>
>>
>> Continue
>>
>> Reset
>>
>>
>>
>>
>>
>>
>>
>>
>> ^v=Move Highlight =Select Entry
>>
>>
>>
>> When in this state `hosted-engine --vm-status` says it is up but failed
>> liveliness check
>>
>> hosted-engine --vm-status | grep -i engine\ status
>> Engine status : {"vm": "down", "health": "bad",
>> "detail": "unknown", "reason": "vm not running on this host"}
>> Engine status : {"vm": "up", "health": "bad", "detail":
>> "Up", "reason": "failed liveliness check"}
>> Engine status : {"vm": "down", "health": "bad",
>> "detail": "Down", "reason": "bad vm status"}
>>
>> I assume I am running into https://access.redhat.com/solutions/5341561 (RHV:
>> Hosted-Engine VM fails to start after changing the cluster to Q35/UEFI)
>> however how to fix that isn't really described. I have tried starting hosted
>> engine paused (`hosted-engine --vm-start-paused`) and editing the config
>> (`virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
>> edit HostedEngine`) to have pc-i440fx instead and removing a bunch of pcie
>> lines etc until it will accept the config and then resuming hosted engine
>> (`virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
>> resume HostedEngine`) but haven't come up with something that is able to
>> start.
>>
>> Anyone know how to resolve this? Am I even chasing the right path?
>>
>> Let's start with the negative - this should have been prevented by [1].
>> Can it be that the custom bios type that the hosted engine VM was set with
>> was manually dropped in this environment?
>>
>> The positive is that th
[ovirt-users] Re: Hosted Engine stuck in bios
Removing those two lines got the hosted engine vm booting again, so that is a
great help. Thank you.
Now I just need the web interface of ovirt-engine to work again. I feel like I
might have run things out of order and forgot to do `engine-setup` as part of
the update of hosted engine. Though when I try to do that now it bails out
claiming the cluster isn't in global maintenance yet it is.
[ INFO ] Stage: Setup validation
[ ERROR ] It seems that you are running your engine inside of the hosted-engine
VM and are not in "Global Maintenance" mode.
In that case you should put the system into the "Global Maintenance"
mode before running engine-setup, or the hosted-engine HA agent might kill the
machine, which might corrupt your data.
[ ERROR ] Failed to execute stage 'Setup validation': Hosted Engine setup
detected, but Global Maintenance is not set.
I see engine.log says it can't contact the database but I certainly see
Postgres processes running.
/var/log/ovirt-engine/engine.log
2021-01-21 14:47:31,502Z ERROR [org.ovirt.engine.core.services.HealthStatus]
(default task-15) [] Failed to run Health Status.
2021-01-21 14:47:31,502Z ERROR [org.ovirt.engine.core.services.HealthStatus]
(default task-14) [] Unable to contact Database!: java.lang.InterruptedException
> On Jan 21, 2021, at 03:19, Arik Hadas wrote:
>
>
>
> On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas wrote:
> Hi,
>
> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> setting the default datacenter from 4.4 to 4.5 and making the default bios
> q35+eufi. Unfortunately quite a few things. Now however hosted engine doesn't
> boot up anymore and `hosted-engine --console` just shows the below
> bios/firmware output:
>
> RHEL
>
> RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
>
> 0.0.0 16384 MB RAM
>
>
>
>
>Select Language This is the option
>
> one adjusts to
> change
> > Device Managerthe language for the
>
> > Boot Manager current system
>
> > Boot Maintenance Manager
>
>
>Continue
>
>Reset
>
>
>
>
>
>
>
>
> ^v=Move Highlight =Select Entry
>
>
>
> When in this state `hosted-engine --vm-status` says it is up but failed
> liveliness check
>
> hosted-engine --vm-status | grep -i engine\ status
> Engine status : {"vm": "down", "health": "bad",
> "detail": "unknown", "reason": "vm not running on this host"}
> Engine status : {"vm": "up", "health": "bad", "detail":
> "Up", "reason": "failed liveliness check"}
> Engine status : {"vm": "down", "health": "bad",
> "detail": "Down", "reason": "bad vm status"}
>
> I assume I am running into https://access.redhat.com/solutions/5341561 (RHV:
> Hosted-Engine VM fails to start after changing the cluster to Q35/UEFI)
> however how to fix that isn't really described. I have tried starting hosted
> engine paused (`hosted-engine --vm-start-paused`) and editing the config
> (`virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
> edit HostedEngine`) to have pc-i440fx instead and removing a bunch of pcie
> lines etc until it will accept the config and then resuming hosted engine
> (`virsh -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf
> resume HostedEngine`) but haven't come up with something that is able to
> start.
>
> Anyone know how to resolve this? Am I even chasing the right path?
>
> Let's start with the negative - this should have been prevented by [1].
> Can it be that the custom bios type that the hosted engine VM was set with
> was manually dropped in this environment?
>
> The positive is that the VM starts. This means that from the chipset
> perspective, the configuration is valid.
> So I wouldn't try to change it to i440fx, but only to switch the firmware to
> BIOS.
> I think that removing the following lines from the domain xml should do it:
> type='pflash'>/usr/share/OVMF/OVMF_CODE.secboot.fd
> template='/usr/share/OVMF/OVMF_VARS.fd'>/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd
> Can you give this a try?
>
> [1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/59/
>
>
>
> /var/log/libvirt/qemu/HostedEngine.log
>
> 2021-01-20 15:31:56.500+: starting up libvirt version: 6.6.0, package:
> 7.1.el8 (CBS , 2020-12-10-14:05:40, ), qemu version:
> 5.1.0qemu-kvm-5.1.0-14.el8
[ovirt-users] Re: Hosted Engine stuck in bios
On Thu, Jan 21, 2021 at 8:57 AM Joseph Gelinas wrote:
> Hi,
>
> I recently did some updates of ovirt from 4.4.1 or 4.4.3 to 4.4.4, also
> setting the default datacenter from 4.4 to 4.5 and making the default bios
> q35+eufi. Unfortunately quite a few things. Now however hosted engine
> doesn't boot up anymore and `hosted-engine --console` just shows the below
> bios/firmware output:
>
> RHEL
>
> RHEL-8.1.0 PC (Q35 + ICH9, 2009)2.00 GHz
>
> 0.0.0 16384 MB RAM
>
>
>
>
>Select Language This is the
> option
> one adjusts to
> change
> > Device Managerthe language for
> the
> > Boot Manager current system
>
> > Boot Maintenance Manager
>
>
>Continue
>
>Reset
>
>
>
>
>
>
>
>
> ^v=Move Highlight =Select Entry
>
>
>
> When in this state `hosted-engine --vm-status` says it is up but failed
> liveliness check
>
> hosted-engine --vm-status | grep -i engine\ status
> Engine status : {"vm": "down", "health": "bad",
> "detail": "unknown", "reason": "vm not running on this host"}
> Engine status : {"vm": "up", "health": "bad",
> "detail": "Up", "reason": "failed liveliness check"}
> Engine status : {"vm": "down", "health": "bad",
> "detail": "Down", "reason": "bad vm status"}
>
> I assume I am running into https://access.redhat.com/solutions/5341561
> (RHV: Hosted-Engine VM fails to start after changing the cluster to
> Q35/UEFI) however how to fix that isn't really described. I have tried
> starting hosted engine paused (`hosted-engine --vm-start-paused`) and
> editing the config (`virsh -c
> qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf edit
> HostedEngine`) to have pc-i440fx instead and removing a bunch of pcie lines
> etc until it will accept the config and then resuming hosted engine (`virsh
> -c qemu:///system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf resume
> HostedEngine`) but haven't come up with something that is able to start.
>
> Anyone know how to resolve this? Am I even chasing the right path?
>
Let's start with the negative - this should have been prevented by [1].
Can it be that the custom bios type that the hosted engine VM was set with
was manually dropped in this environment?
The positive is that the VM starts. This means that from the chipset
perspective, the configuration is valid.
So I wouldn't try to change it to i440fx, but only to switch the firmware
to BIOS.
I think that removing the following lines from the domain xml should do it:
/usr/share/OVMF/OVMF_CODE.secboot.fd
/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd
Can you give this a try?
[1] https://gerrit.ovirt.org/#/c/ovirt-engine/+/59/
>
>
> /var/log/libvirt/qemu/HostedEngine.log
>
> 2021-01-20 15:31:56.500+: starting up libvirt version: 6.6.0, package:
> 7.1.el8 (CBS , 2020-12-10-14:05:40, ), qemu version:
> 5.1.0qemu-kvm-5.1.0-14.el8.1, kernel: 4.18.0-240.1.1.el8_3.x86_64,
> hostname: ovirt-3
> LC_ALL=C \
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin \
> HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine \
> XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.local/share \
> XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.cache \
> XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-25-HostedEngine/.config \
> QEMU_AUDIO_DRV=spice \
> /usr/libexec/qemu-kvm \
> -name guest=HostedEngine,debug-threads=on \
> -S \
> -object
> secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-25-HostedEngine/master-key.aes
> \
> -blockdev
> '{"driver":"file","filename":"/usr/share/OVMF/OVMF_CODE.secboot.fd","node-name":"libvirt-pflash0-storage","auto-read-only":true,"discard":"unmap"}'
> \
> -blockdev
> '{"node-name":"libvirt-pflash0-format","read-only":true,"driver":"raw","file":"libvirt-pflash0-storage"}'
> \
> -blockdev
> '{"driver":"file","filename":"/var/lib/libvirt/qemu/nvram/81816cd3-5816-4185-b553-b5a636156fbd.fd","node-name":"libvirt-pflash1-storage","auto-read-only":true,"discard":"unmap"}'
> \
> -blockdev
> '{"node-name":"libvirt-pflash1-format","read-only":false,"driver":"raw","file":"libvirt-pflash1-storage"}'
> \
> -machine
> pc-q35-rhel8.1.0,accel=kvm,usb=off,dump-guest-core=off,pflash0=libvirt-pflash0-format,pflash1=libvirt-pflash1-format
> \
> -cpu Cascadelake-Server-noTSX,mpx=off \
> -m size=16777216k,slots=16,maxmem=67108864k \
> -overcommit mem-lock=off \
> -smp 4,maxcpus=64,sockets=16,dies=1,cores=4,threads=1 \
> -object iothread,id=iothread1 \
> -numa node,nodeid=0,cpus=0-63,mem=16384 \
> -uuid 81816cd3-5816-4185-b553-b5a636156fbd \
> -smbios
> type=1,manufacturer=oVirt,product=RHEL,version=8-1.2011.el8,serial=4c4c4544-0051-3710-8032-c8c04f483633,uuid=81816cd3-5816-4185-b553-b5a636156fbd,family=oVirt
> \
> -no-user-config \
> -no
