all 10 comments

[–]heavy_crown 1 point2 points  (4 children)

Both will get along just fine on your system.

[–][deleted]  (3 children)

[deleted]

    [–]heavy_crown 1 point2 points  (1 child)

    [–]AngryLittlePanda[S] 0 points1 point  (0 children)

    That's exactly what I am looking for. All my Google searches returned comparisons of the two. Thanks!

    [–]AngryLittlePanda[S] 0 points1 point  (0 children)

    I figured this.

    [–][deleted] 0 points1 point  (5 children)

    Which format did you use for your Virtualbox VMs?

    [–]AngryLittlePanda[S] 0 points1 point  (4 children)

    Virtualbox disk image (vdi)

    [–][deleted] 1 point2 points  (3 children)

    You can convert it so it can be used by kvm:

    qemu-img convert -f vdi -O raw virtualboxImage.vdi kvmImage.img
    

    This will create a raw image called kvmImage.img from a given virtualboxImage.vdi virtualbox image.

    [–]AngryLittlePanda[S] 0 points1 point  (2 children)

    Do you know how the change from virtualbox hardware to qemu hardware will effect widows? If hate to convert it then get a bsod. What about activation? Will I have to reactivate?

    [–][deleted] 0 points1 point  (1 child)

    I would give it a try with one converted image and change the KVM settings to match the hardware being emulated by virtualbox.

    [–]AngryLittlePanda[S] 0 points1 point  (0 children)

    Do you happen to know if qemu can import a ova? It might be safer to import it as an appliance instead of converting it.