Virt-manager: IDE disks



  • @FATeknollogee said in Virt-manager: IDE disks:

    @scottalanmiller said in Virt-manager: IDE disks:

    @FATeknollogee said in Virt-manager: IDE disks:

    @scottalanmiller said in Virt-manager: IDE disks:

    @FATeknollogee said in Virt-manager: IDE disks:

    https://www.trilio.io/triliovault/

    This is for Nova only, from their website AFAICT. So doesn't apply to KVM. It requires an entire custom storage layer, and then can talk to the hypervisor.

    That's no different from Scale HC3.

    No...https://www.trilio.io/wp-content/uploads/2018/05/TrilioVault-for-RHV.pdf

    Interesting, maybe they've done enough work to make it work. It would be awesome if someone had done this, but vProtect is extremely open that they have not.

    Has anyone looked into Trilio enough to know if their backups are safe?

    Trilio is the co from here https://mangolassi.it/post/448935

    Ah, sounds like they never made the product. Maybe it will come soon. But from looking at their website, it appears to be something they are might be preparing to make, but don't have yet? Their RHV information definitely states that it is RHV on top of Nova (OpenStack storage layer) and that it is Nova doing the work to make it possible.

    Which if you do a KVM based OpenStack deployment, it is possible to take backups for workloads on KVM, but it's not a backup of KVM as people mean it - meaning you can't just have a KVM based system and take a backup. It's an OpenStack system and if it also has KVM, that's not a problem.



  • Why is OpenStack / Nova keep showing up in this discussion?

    Because the issue is that KVM lacks CBT (Change Block Tracking) which is the only currently working way to make an agentless backup system work. Without it, backups that don't have an agent are only crash consistent and are expected to lose data, randomly not boot, etc.

    OpenStack's Raksha layer provides CBT for the OS ecosystem. This is not done in KVM, but at the storage layer of the cloud infrastructure. Raksha is primarily available for Nova (and Cinder to a lesser extend.) So if you are using Nova, and you have the Raksha layer, then companies like Trilio can use Raksha to build a working agentless backup system.

    That backup system would work regardless of the hypervisor running on top of the stack, so Xen, KVM, whatever. So is there a specific way to make it work with KVM, yes. Is it a KVM backup, no.

    So you can have scenarios, like OpenStack or Scale HC3 where you get what you need. But it doesn't apply to RHV / oVirt scenarios.



  • This is why agentless for KVM and Xen never come up on the radar, it's essentially in the "theory" stages. But it isn't a big deal, because the whole agentless thing is really just a weird sales tactic in the VMware / Hyper-V space from the era when they were trying to convince people to go virtual and so they made up weird benefits and made them sound way more important than they were. In the Xen and KVM space (which is older, at least for Xen), no one really ever cared much as agent based backups were pre-existing, fit more general use cases, and often worked better. So the desire for CBT and agentless systems never really arose.

    That's not to say that people don't want it, they do. But they tend to see it as pretty inconsequential. Lacking it doesn't hurt those ecosystems in any way.



  • How for what vProtect does, you can just take a snapshot and you don't need any tool. Crash consistent "backups" take no effort.



  • @FATeknollogee said in Virt-manager: IDE disks:

    Am I dreaming or IDE disks are not supported any more?
    I could have sworn IDE disks used to be in Virt-manager, now I can't find them!!

    Even with the latest version, its still there. It depends on the selection when you choose a template based on the OS you are installing. Pretty much IDE bus type is for compatibility purposes now.

    If you were creating a VM, you either select "Generic default (default)" where it says, Choose the operating system you are installing, select "Generic default (default)".

    If you were importing an VM that is using IDE, when choosing the operating system you are installing, search generic and select "Generic default (default)"



  • @black3dynamite said in Virt-manager: IDE disks:

    @FATeknollogee said in Virt-manager: IDE disks:

    Am I dreaming or IDE disks are not supported any more?
    I could have sworn IDE disks used to be in Virt-manager, now I can't find them!!

    Even with the latest version, its still there. It depends on the selection when you choose a template based on the OS you are installing. Pretty much IDE bus type is for compatibility purposes now.

    If you were creating a VM, you either select "Generic default (default)" where it says, Choose the operating system you are installing, select "Generic default (default)".

    If you were importing an VM that is using IDE, when choosing the operating system you are installing, search generic and select "Generic default (default)"

    You da man, thx 👍 👍



  • Why would you even want IDE? Are you running a weird guest OS that doesn't support virtio?



  • @dyasny said in Virt-manager: IDE disks:

    Why would you even want IDE? Are you running a weird guest OS that doesn't support virtio?

    I wouldn't want IDE.
    The download (an ova file) came that way, the vendor exported it from ESXi



  • @dyasny said in Virt-manager: IDE disks:

    Why would you even want IDE? Are you running a weird guest OS that doesn't support virtio?

    It's for testing only. I pushed on that, too.



  • @FATeknollogee said in Virt-manager: IDE disks:

    @dyasny said in Virt-manager: IDE disks:

    Why would you even want IDE? Are you running a weird guest OS that doesn't support virtio?

    I wouldn't want IDE.
    The download (an ova file) came that way, the vendor exported it from ESXi

    I see, well, I just started a VM with a SATA disk:

     -drive file=/var/lib/libvirt/images/rhel8-unknown.qcow2,format=qcow2,if=none,id=drive-sata0-0-0 -device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2
    

    Looks like IDE to me, they probably renamed it to SATA for the millenials not to get scared by the older term (and for QEMU, any IDE was always closer to SATA because the access to the disks was always serial, one virtual controller device per disk)



  • @dyasny said in Virt-manager: IDE disks:

    @FATeknollogee said in Virt-manager: IDE disks:

    @dyasny said in Virt-manager: IDE disks:

    Why would you even want IDE? Are you running a weird guest OS that doesn't support virtio?

    I wouldn't want IDE.
    The download (an ova file) came that way, the vendor exported it from ESXi

    I see, well, I just started a VM with a SATA disk:

     -drive file=/var/lib/libvirt/images/rhel8-unknown.qcow2,format=qcow2,if=none,id=drive-sata0-0-0 -device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=2
    

    Looks like IDE to me, they probably renamed it to SATA for the millenials not to get scared by the older term (and for QEMU, any IDE was always closer to SATA because the access to the disks was always serial, one virtual controller device per disk)

    Right, ATA basically means IDE. IDE was formalized into ATA and renamed. SATA means ATA over Serial, since the physical piece is meaningless in a VM, definitely some funky marketing to put the physical piece into the name.



  • @scottalanmiller said in Virt-manager: IDE disks:

    Right, ATA basically means IDE. IDE was formalized into ATA and renamed. SATA means ATA over Serial, since the physical piece is meaningless in a VM, definitely some funky marketing to put the physical piece into the name.

    Either someone too young became the maintainer or the PMs decided to rebrand. In any case, there was no reason to keep both IDE/PATA and SATA available as options



  • @dyasny said in Virt-manager: IDE disks:

    @scottalanmiller said in Virt-manager: IDE disks:

    Right, ATA basically means IDE. IDE was formalized into ATA and renamed. SATA means ATA over Serial, since the physical piece is meaningless in a VM, definitely some funky marketing to put the physical piece into the name.

    Either someone too young became the maintainer or the PMs decided to rebrand. In any case, there was no reason to keep both IDE/PATA and SATA available as options

    The logical choice would be just ATA, since IDE is weird (long ago deprecated) and either SATA/PATA make no sense as they specify parts that don't apply.



  • @scottalanmiller said in Virt-manager: IDE disks:

    The logical choice would be just ATA, since IDE is weird (long ago deprecated) and either SATA/PATA make no sense as they specify parts that don't apply.

    Yeah, but kids^W admins these days only ever heard of SATA, so give 'em SATA to keep them happy



  • @dyasny said in Virt-manager: IDE disks:

    @scottalanmiller said in Virt-manager: IDE disks:

    The logical choice would be just ATA, since IDE is weird (long ago deprecated) and either SATA/PATA make no sense as they specify parts that don't apply.

    Yeah, but kids^W admins these days only ever heard of SATA, so give 'em SATA to keep them happy

    They need to just get off of my lawn.



  • @scottalanmiller said in Virt-manager: IDE disks:

    They need to just get off of my lawn.

    LOL, funny how I'd never have understood the joke before moving to NA and buying a house 🙂



  • @dyasny said in Virt-manager: IDE disks:

    @scottalanmiller said in Virt-manager: IDE disks:

    They need to just get off of my lawn.

    LOL, funny how I'd never have understood the joke before moving to NA and buying a house 🙂

    HAHAHA