I run Debian linux.
I want to make a virtual machine in virtualbox, wich boots from a server via drbl.
The server will be my laptop.
The virtual machine start booting, but fall into infifite boot-loop.
It load one part of the OS from the server, then stop loading, start it again...
Have anyone seen this error?
Related
My friend and I have downloaded some discountinued videogames from Old Games Download - Retrogaming and Abandonware (which I warmly recommend to any CD-ROM aficionado!). We managed to run two of them after downloading them, mounting their .ISO file and installing them on a Windows 10 machine. The process was fairly smooth.
We are struggling to run the other two. They’re only compatible with Windows XP, so we created a virtual box with XP as the OS, but still no luck. We can’t get the virtual box to connect to Wi-Fi in any way, even after following several tutorials found online. We have tried mounting the games’s ISOs in the following ways:
Using Virtual Clone Drive
Using WinCDEmu
Using Win XP Virtual CD Control Panel
And we think we have managed to actually mount the ISO and install the programme on the virtual machine, but the game won’t start anyway. When we try to run it, this window opens:
Monsters & Co CDROM initial window, with title, play button, exit button
But when we click ‘play’ nothing happens. We have checked the “Insert Guest Addition CD Image” setting that triggers Autoplay and it seems to be up and running. What can we try next?
VirtualBox access internet by connecting to your real machine (the host machine) as if it was a router of some kind. There is no need to make the virtual machine (guest machine) use your wifi adapter directly to get internet connection, just add a virtual network adapter to your guest machine and VirtualBox takes care of everything else (but make sure you have checked the appropriated options during installation process so drivers are installed in your host machine).
Now, the game not launching is hard to say, as we don't have any message or other info about what is causing the falling. Yet, this is a 3D game and VirtualBox is not good enough to hand this kind of computation.
The broadcast stops working 5 seconds after the start. All ports are open. Why can this error still occur?
If you run Ant Media Server on Ubuntu virtual machine on Windows host and run browser (as WebRTC peer) on host (Windows) side, then you can encounter with such a problem.
As a solution, you can start browser on virtual machine side. Or better run AMS on a real machine or VPS.
I am running FreeNAS 11.1-U5 at home. I have everything configured and have created VM's for Windows Server, Ubuntu, pfSense, FreePBX. I was able to install Windows and Ubuntu, but shortly after (a few hours after installing them), and after turning them off through the FreeNAS GUI, they have stopped turning on. FreeNAS reports at the top of the GUI that the start was successful, but the VM details still read "stopped".
I have run the VM's before and have the required settings in my CMOS configured for the Host (FreeNAS machine). Restarting the host will fix the problem for a while and it will let me work with the VM's, but I cannot keep restarting FreeNAS. Can anyone tell me why this happens and how to fix it please?
I am using Ubuntu 14.04 on VmWare-Player 10. My host system is Windows 7. It worked fine, but since I restarted my host system (I have done this often and it was working without any problems) it stucks at the ubuntu boot up:
I have restarted my host system and it locked again:
Do I have to change something in the log files or how can I fix this?
Thanks in advance,
clax
I use Virtual Machine Manager to run several Guest OSs with QEMU-KVM. I read it somewhere that by inputting ctrl+alt+2 should pop up monitor console. It is not working or disabled. Is there any way I can turn it on?
What I am trying to do is to dump physical memory of GuestOS.
With this command,
pmemsave 0 0x20000000 /tmp/dumpfile
If you use Virtual Machine Manager, you most likely also have "virsh" tools installed. You can use it to transmit qemu-monitor commands to your VM:
virsh# qemu-monitor-command vm-name --hmp "pmemsave 0 0x20000000 /tmp/dumpfile"