Hi, why does my ovirt hypervisor node crash when i pull the hypervisor boot drive? The following thread claims that the oVirt node hypervisor should lodad into memory, so boot disk failure shouldn't have any impact on a running node. https://lists.ovirt.org/pipermail/users/2014-December/029771.html Only memory failure should have a impact, and if RAM fails there is a possibility that the hypervisor OS would have crashed regardless. If you load the hypervisor OS into memory there will be moved/combined a point of failure (the boot disk) with another(the RAM). RAM=memory
On Tue, Sep 8, 2020 at 9:50 AM <harryo.dk@gmail.com> wrote:
Hi, why does my ovirt hypervisor node crash when i pull the hypervisor boot drive? The following thread claims that the oVirt node hypervisor should lodad into memory, so boot disk failure shouldn't have any impact on a running node. https://lists.ovirt.org/pipermail/users/2014-December/029771.html
Because the above link is old, and refers to what is now called "oVirt node Legacy" (or in some places "vintage"). In 4.0 we moved to what's now called "oVirt node Next Generation", or "NG" for short. Search the net for e.g. "ovirt node ng" "slides" to find some presentations about this change.
Only memory failure should have a impact, and if RAM fails there is a possibility that the hypervisor OS would have crashed regardless. If you load the hypervisor OS into memory there will be moved/combined a point of failure (the boot disk) with another(the RAM).
You are welcome to file an RFE in bugzilla for this. AFAIK this is not supported in ovirt-node currently. If you want a diskless ovirt host/hypervisor, you are more than welcome to try any of the existing methods you can find on the net for installing and using CentOS diskless, and then use that as an oVirt host. Relevant methods might include SAN boot (if your hardware supports that), NFS root, etc. Not sure about root on tmpfs, that might be possible as well. Best regards, -- Didi
I really don't understand why oVirt would remove/trade the diskless(load into RAM) feature away in oVirt node NG, this is a key point that makes some people choose something like ESXi(that loads into RAM and therefor is not dependent of the boot disk for running) over oVirt node NG. Do you think it is possible to get this back in oVirt node NG?
On Tue, Sep 8, 2020 at 12:18 PM <harryo.dk@gmail.com> wrote:
I really don't understand why oVirt would remove/trade the diskless(load into RAM) feature away in oVirt node NG,
oVirt node legacy was never fully diskless in the sense that you refer to. It used an ISO image loaded to a RAM disk and a readwrite filesystem on disk for stuff we wanted/needed to change/keep. I wasn't part of the design process for node, but I do not think that "running diskless" was considered as a feature we want - neither in legacy nor in NG.
this is a key point that makes some people choose something like ESXi(that loads into RAM and therefor is not dependent of the boot disk for running) over oVirt node NG.
Perhaps.
Do you think it is possible to get this back in oVirt node NG?
I think it's possible, but obviously requires work. I have no idea how much work. As I suggested before, you can file an RFE. If enough people want this, and/or if someone provides patches, it's more likely to be added eventually. Best regards, -- Didi
It would be nice. Initially when I was setting my lab I wanted to boot from USB and be able to host Vms properly but due to speed limitations - it failed to work normally. Maybe in-memory mode could be nice where booting from USB is possible. Best Regards, Strahil Nikolov В вторник, 8 септември 2020 г., 12:35:15 Гринуич+3, Yedidyah Bar David <didi@redhat.com> написа: On Tue, Sep 8, 2020 at 12:18 PM <harryo.dk@gmail.com> wrote:
I really don't understand why oVirt would remove/trade the diskless(load into RAM) feature away in oVirt node NG,
oVirt node legacy was never fully diskless in the sense that you refer to. It used an ISO image loaded to a RAM disk and a readwrite filesystem on disk for stuff we wanted/needed to change/keep. I wasn't part of the design process for node, but I do not think that "running diskless" was considered as a feature we want - neither in legacy nor in NG.
this is a key point that makes some people choose something like ESXi(that loads into RAM and therefor is not dependent of the boot disk for running) over oVirt node NG.
Perhaps.
Do you think it is possible to get this back in oVirt node NG?
I think it's possible, but obviously requires work. I have no idea how much work. As I suggested before, you can file an RFE. If enough people want this, and/or if someone provides patches, it's more likely to be added eventually. Best regards, -- Didi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KCX3XTG6NRQONH...
On Thu, Sep 10, 2020 at 10:41 AM <harryo.dk@gmail.com> wrote:
How can we file an RFE?
By opening a new bug: https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt And writing '[RFE]' in the start of the summary line for it. Best regard, -- Didi
participants (3)
-
harryo.dk＠gmail.com -
Strahil Nikolov -
Yedidyah Bar David