Virt-manager: IDE disks
- 
 @FATeknollogee said in Virt-manager: IDE disks: I tried using virt-v2v to convert, for some odd reason, virt-v2v thinks the disks are virtio!! VirtIO is what you would want. I assume that the V2V process is failing, though? 
- 
 @scottalanmiller said in Virt-manager: IDE disks: @FATeknollogee said in Virt-manager: IDE disks: I tried using virt-v2v to convert, for some odd reason, virt-v2v thinks the disks are virtio!! VirtIO is what you would want. I assume that the V2V process is failing, though? Funny enough, v2v does not fail! 
- 
 virt-v2v: This guest has virtio drivers installed.
- 
 @FATeknollogee said in Virt-manager: IDE disks: @scottalanmiller said in Virt-manager: IDE disks: @FATeknollogee said in Virt-manager: IDE disks: I tried using virt-v2v to convert, for some odd reason, virt-v2v thinks the disks are virtio!! VirtIO is what you would want. I assume that the V2V process is failing, though? Funny enough, v2v does not fail! So you get a working VM? What's the issue then? 
- 
 @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: I tried using virt-v2v to convert, for some odd reason, virt-v2v thinks the disks are virtio!! VirtIO is what you would want. I assume that the V2V process is failing, though? Funny enough, v2v does not fail! So you get a working VM? What's the issue then? No working vm, vm will not boot, says it can't find the disks 
- 
  
- 
 xml file shows the disks as IDE. 
- 
 @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: I tried using virt-v2v to convert, for some odd reason, virt-v2v thinks the disks are virtio!! VirtIO is what you would want. I assume that the V2V process is failing, though? Funny enough, v2v does not fail! So you get a working VM? What's the issue then? No working vm, vm will not boot, says it can't find the disks Oh, so the V2V process fails then. That's what I meant. It didn't result in a working system. 
- 
 @FATeknollogee in theory you can remap the drives manually  
- 
 # virt-v2v -i ova vProtect-Generic.ova -o libvirt -of qcow2 -os VirtualMachines [ 0.0] Opening the source -i ova vProtect-Generic.ova virt-v2v: warning: making OVA directory public readable to work around libvirt bug https://bugzilla.redhat.com/1045069 [ 3.5] Creating an overlay to protect the source from being modified [ 3.7] Opening the overlay [ 7.6] Inspecting the overlay [ 23.7] Checking for sufficient free disk space in the guest [ 23.7] Estimating space required on target for each disk [ 23.7] Converting CentOS Linux release 7.6.1810 (Core) to run on KVM virt-v2v: This guest has virtio drivers installed. [ 88.9] Mapping filesystem data to avoid copying unused and blank areas [ 89.8] Closing the overlay [ 90.0] Assigning disks to buses [ 90.0] Checking if the guest needs BIOS or UEFI to boot [ 90.0] Initializing the target -o libvirt -os VirtualMachines [ 90.1] Copying disk 1/2 to /vm/vProtect-sda (qcow2) (100.00/100%) [ 108.3] Copying disk 2/2 to /vm/vProtect-sdb (qcow2) (100.00/100%) [ 126.1] Creating output metadata Pool VirtualMachines refreshed Domain vProtect defined from /tmp/v2vlibvirtc251bd.xml [ 126.3] Finishing off
- 
 You are trying to install vProtect the agentless backup product for KVM? 
- 
 @scottalanmiller said in Virt-manager: IDE disks: You are trying to install vProtect the agentless backup product for KVM? Kinda, they have an appliance (prepackaged ova exported from ESXi), I was going to test it. 
 Trying to convert the ova to qcow2
 Quicker than installing the app from scratch.
- 
 @FATeknollogee said in Virt-manager: IDE disks: Kinda, they have an appliance (prepackaged ova exported from ESXi), I was going to test it. Crash consistent only, I'd not use that. Why are you looking at it? 
- 
 @scottalanmiller said in Virt-manager: IDE disks: @FATeknollogee said in Virt-manager: IDE disks: Kinda, they have an appliance (prepackaged ova exported from ESXi), I was going to test it. Crash consistent only, I'd not use that. Why are you looking at it? Why am I looking at the application? 
- 
 @FATeknollogee said in Virt-manager: IDE disks: Quicker than installing the app from scratch. Is it? You still need to get to VirtIO in the end. And you want a reliable method for the future. I would not want to do it this way unless there was no other choice. 
- 
 @FATeknollogee said in Virt-manager: IDE disks: @scottalanmiller said in Virt-manager: IDE disks: @FATeknollogee said in Virt-manager: IDE disks: Kinda, they have an appliance (prepackaged ova exported from ESXi), I was going to test it. Crash consistent only, I'd not use that. Why are you looking at it? Why am I looking at the application? Yes, why are you looking at a crash-consistent "backup" tool? 
- 
 @scottalanmiller said in Virt-manager: IDE disks: @FATeknollogee said in Virt-manager: IDE disks: Quicker than installing the app from scratch. Is it? You still need to get to VirtIO in the end. And you want a reliable method for the future. I would not want to do it this way unless there was no other choice. For lab testing, this method "should" have been faster! 
- 
 @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: Kinda, they have an appliance (prepackaged ova exported from ESXi), I was going to test it. Crash consistent only, I'd not use that. Why are you looking at it? Why am I looking at the application? Yes, why are you looking at a crash-consistent "backup" tool? Not too many other choices out there! 
- 
 @FATeknollogee said in Virt-manager: IDE disks: @scottalanmiller said in Virt-manager: IDE disks: @FATeknollogee said in Virt-manager: IDE disks: Quicker than installing the app from scratch. Is it? You still need to get to VirtIO in the end. And you want a reliable method for the future. I would not want to do it this way unless there was no other choice. For lab testing, this method "should" have been faster! I'm not sure that I agree. Pre-built appliances are nearly always a massive pain and they aren't a good process for testing end to end. So more work up front, more work later. I generally dislike them a lot. Faster they never seem to be. 
- 
 @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: Kinda, they have an appliance (prepackaged ova exported from ESXi), I was going to test it. Crash consistent only, I'd not use that. Why are you looking at it? Why am I looking at the application? Yes, why are you looking at a crash-consistent "backup" tool? Not too many other choices out there! What do you mean? There are endless awesome choices. This just isn't one of them. Why do you perceive a shortage of backup options? 
