(I have my doubts about these instructions.) |
m |
||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | Has anybody actually done this? VirtualBox does not virtualize the VT-x/SVM support of the hardware to the guest OS (nor does any other hypervisor, afaik). The Linux OS running under VirtualBox of the host Windows machine will never detect VT-x/SVM, and so the hardware required by QEMU, kvm, etc. won't be there, right? If so this page will lead some down a cruel dead-end path. Otherwise the details for circumventing the issue need to be given here. | + | Has anybody actually done this? VirtualBox does not virtualize the VT-x/SVM support of the hardware to the guest OS (nor does any other hypervisor, afaik). The Linux OS running under VirtualBox of the host Windows machine will never detect VT-x/SVM, and so the hardware required by QEMU, kvm, etc. won't be there, right? If so this page will lead some down a cruel dead-end path. Otherwise the details for circumventing the issue need to be given here. -Some random user |
| + | |||
| + | I tried setting things up under a virtual box under Win7 64bit with an image of ubuntu 10.04 and even with qemu-kvm nothing was happening. The command was returning instantly despite it claiming "This will take a while". Luckly I ran into this talk page before i wasted any more time trying to debug. I'm going to add a note about this issue on hte page. If it's wrong and I'm simply doing something wrong then good. Otherwise it would be best we don't waste devs' time. [[User:Danieru|Danieru]] 21:50, 17 November 2010 (UTC) | ||
| + | |||
| + | I tried this under Windows 7 32-bit with Ubuntu 10.10 Desktop running in VirtualBox and kept getting "kvm: no hardware support". So, this idea as stated will not work. It may theoretically work by running runtime in a kvm running on an actual machine and connecting to it. But at that point it might just be easier to do a dual boot solution (using Wubi installer, for example) and just forget about using VirtualBox.--[[User:Kirevse|Kirevse]] 23:30, 26 December 2010 (UTC) | ||
Has anybody actually done this? VirtualBox does not virtualize the VT-x/SVM support of the hardware to the guest OS (nor does any other hypervisor, afaik). The Linux OS running under VirtualBox of the host Windows machine will never detect VT-x/SVM, and so the hardware required by QEMU, kvm, etc. won't be there, right? If so this page will lead some down a cruel dead-end path. Otherwise the details for circumventing the issue need to be given here. -Some random user
I tried setting things up under a virtual box under Win7 64bit with an image of ubuntu 10.04 and even with qemu-kvm nothing was happening. The command was returning instantly despite it claiming "This will take a while". Luckly I ran into this talk page before i wasted any more time trying to debug. I'm going to add a note about this issue on hte page. If it's wrong and I'm simply doing something wrong then good. Otherwise it would be best we don't waste devs' time. Danieru 21:50, 17 November 2010 (UTC)
I tried this under Windows 7 32-bit with Ubuntu 10.10 Desktop running in VirtualBox and kept getting "kvm: no hardware support". So, this idea as stated will not work. It may theoretically work by running runtime in a kvm running on an actual machine and connecting to it. But at that point it might just be easier to do a dual boot solution (using Wubi installer, for example) and just forget about using VirtualBox.--Kirevse 23:30, 26 December 2010 (UTC)