VM Windows Failed to start when Import from Virtualbox vdi
Closed this issue · 8 comments
Hello!
I have following this in documentation :
https://ravada.readthedocs.io/en/latest/docs/convert_from_virtualbox.html
It successfully booting up the windows in ravada vdi, but always showing like this :
https://ibb.co/c8trJTY
I am new in VDI so it make me confuse..
Thank You!
Ok @AKA9124 , thanks for your question. It looks like Windows is detecting new hardware. You could try installing Windows guest tools and the VirtIO drivers. Follow the links from here https://ravada.readthedocs.io/en/latest/docs/install_guest_windows10.html#setup .
It may work booting Windows in maintenance mode and repair the newly created virtual machine. I think the best could be installing those packages in VirtualBox before converting. If you can confirm it works we will review the documentation.
Good luck !
Thanks for your reply!
After read your reply, i try it again, actually i am using Windows7, but because VirtIO drivers can't install in Windows7
https://ibb.co/Jy9Cw6L
So now i change to Windows 10
-
Then when i am trying following this :
https://pve.proxmox.com/wiki/Qemu-guest-agent#Windows
https://ibb.co/HN71J4j -
The PCI Simple Communications Controller not showing in my Windows 10 VM at Virtualbox :
https://ibb.co/VSQVjyG
So i skip this step because i dont know why not showing
Then next, i install qemu-guest agent
https://ibb.co/vctyxqy
And it is running :
https://ibb.co/fvdnbD8
Also the VirtIO guest tools
https://ibb.co/rZ8v1Cs
and Spice guest tools
https://ibb.co/yRZZhNf
after that i restart the VM, then shutdown the VM
And here, i following this tutorial :
https://ravada.readthedocs.io/en/latest/docs/convert_from_virtualbox.html
I have upload the VM.vdi of windows 10 to the Server which have ravada vdi inside too.
https://ibb.co/tXVFYz4 - https://ibb.co/87Vm3yV
Following the tutorial, now i creating the windows 10 VM in ravada web admin :
With setup like this https://ibb.co/Dr21r6y based the same set VM in virtualbox https://ibb.co/z2YV5X8
After creating the VM in ravada web, in terminal i am going to /var/lib/libvirt/images :
https://ibb.co/LCjGcTv
Then use virsh edit Windows10 like in the documentation, and Remove the swap, cdrom and other disk volumes. :
https://ibb.co/Sv1t3XB > https://ibb.co/xHV4K6R
Also remove the swap image file :
https://ibb.co/s2LvDtY
Then i go back where i upload the VM.vdi file, and directly convert vdi to qcow2 :
https://ibb.co/QYy747w
Here, documentation not clear after convert vdi what should we do next, so i delete file with same name in /var/lib/libvirt/images :
https://ibb.co/mCvjJH4
Then move the VM file that i have converted before to /var/lib/libvirt/images :
https://ibb.co/mzkSvJB
So after that, i start the VM via web admin. it's boot like normal :
https://ibb.co/KytLkPs
But then this happen :
https://ibb.co/ZHCfWYf
And the VM ended here at Windows repair :
https://ibb.co/1q4sc96
Sorry for the long explanation, but here i dont know what should i do next
Are this because the Driver of PCI Communciation controller ?
Or it is possible because the VirtualBox.vdi i create running in windows ? And it's cannot run in linux ?
Thank You!
@AKA9124 your answer is complete and it looks like you are doing the right thing.
First of all Windows virtual machines can perfectly run on Linux. Though the easiest way to install them is using an ISO file.
Now I guess you need to use VirtualBox first for some reason. We have used this method when importing virtual machines created by some user that need porting to one of our servers. So it should work, but sometimes the operating system may need some tweaking. You should definitely use the "Startup Repair". Have you managed to repair the virtual machine ?
Now if you only want to install a Windows virtual machine, drop the installer ISO file in the server at /var/lib/libvirt/images. Then in the frontend, you must go to Admin Tools -> Machines , and click on "New Virtual Machine". Select a Windows template and choose the ISO file for Windows below.
Hope this helps.
Now I recall we have received reports of old Windows machine running fine, even legacy Windows XP. One thing you can try is change the bus type of the volumes. Click on the machine name to go the the settings page. Select the "Hardware" tab and choose the disk drive. There change the bus model to SATA, or maybe SCSI. For older machines you can even select IDE if you want to. I attach a screenshot to help you find it.
Good luck
Thank you! Now it's working properly
Sorry for the late reply, i am part timer so only in Monday and Tuesday i can access the server to try
When change the bus, only ide and sata is working
The rest is not working....
But i kinda feel a little VM slow response here when using ide or sata, idk why
Low performance can be caused by many factors. Make sure the virtual machine has enogh memory and CPUs. You may try installing drivers anyway after you have it working. Also, setting the cache to writeback or unsafe should speed up the disk access.
Thanks for your Reply, after I add more CPU and Memory in VM, it is more smooth than before