Hello,
I recently began a training course, and my instructor chose to hand out a very important set of practice tests on a VirtualBox guest image. This is fine, and I've enjoyed learning about VirtualBox (along with the actual course materials), but at home I have a RHEL 6.4 lab that i am using to do the work intended for the course, which uses KVM by default (it is possible to install KVM from the RHEL 6 installation DVD, which I have done). I have successfully converted the .vdi file to .qcow, but I haven't been able to figure out a way to convert the .vbox file to a format usable by KVM. Has anyone else done this, or are there any suggestions? Admins, if this is in the wrong place, please move this thread to a more appropriate place. Thanks!
Converting a .vbox file to a format readable by KVM?
-
- Posts: 1
- Joined: 18. Jun 2013, 04:04
-
- Site Moderator
- Posts: 5229
- Joined: 13. Jan 2012, 11:14
- Primary OS: Debian other
- VBox Version: OSE Debian
- Guest OSses: Debian, Win 2k8, Win 7
- Contact:
Re: Converting a .vbox file to a format readable by KVM?
I don't think you'll find anything of the like. AFAIK they don't even emulate the same devices, so there would be no way to convert from one to another.
Why not reconfiguring the VM like you want?
Why not reconfiguring the VM like you want?
Hyperbox - Virtual Infrastructure Manager - https://apps.kamax.lu/hyperbox/
Manage your VirtualBox infrastructure the free way!
Manage your VirtualBox infrastructure the free way!
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Converting a .vbox file to a format readable by KVM?
The correct place to discuss this IMHO would be a KVM discussion forum, since you are trying to get a VM working on their platform.
-
- Oracle Corporation
- Posts: 2973
- Joined: 19. Dec 2007, 15:45
- Primary OS: MS Windows 7
- VBox Version: PUEL
- Guest OSses: Any and all
- Contact:
Re: Converting a .vbox file to a format readable by KVM?
Ask KVM to do this for you. We won't.