creating process for virtual machine vmname (GUI/Qt)

[westdude]

Hi all.

I have used Vbox for quite sometime but I've never seen this problem before. Out of the blue when I started a vm, this screen pop out and it never completed the session.

creating process for virtual machine vmname (GUI/Qt)

When I force closed the windows, it gave me the error and the Vbox gui shown my vm is down eventhough the vm is running just fine. Any thought?

FYI, the host machine is a CentOS 5.7 and the guest machine is also CentOS 5.7. Please help?

[Perryg]

It happens. Don't beat yourself up too much. It's always the obvious that eludes us.

Edit: what happened to your reply where you said you found the cause?

[westdude]

Thanks Perry.

Sorry for jumping the gun but apparently that problems showed up again. I thought I resolved it. Apparently not. Any suggestion?

[Perryg]

When I force closed the windows, it gave me the error and the Vbox gui shown my vm is down eventhough the vm is running just fine. Any thought?

The VBox com has lost contact with the guest process. You need to shut down the process that is running the guest, close all VirtualBox processes and see if they come back in sync. I have seen a host reboot being needed though not always.

[westdude]

Thanks Perry.

That's what I'm afraid of. Let me reboot and I'll give you all an update.

[westdude]

Like you predicted Perry.

That solved the problem. Many thanks again.

[Falstaff1141]

I've spent many hours trying to get VB running on either Fedora or CentOS; I'm now at the point where I have finally successfully? installed VB 4.3 with all required packages (on CentOS 6.4), but when I attempt to start a guest (Whonix-Gateway) it just hangs forever on "Creating process for virtual machine...(GUI/Qt)...(1/2)" I've shut down the processes, rebooted the CentOS host (6.4) and

Any thoughts?

[Perryg]

Post the guests log file ( as an attachment )

[Falstaff1141]

If I try to show the guest log, VB simply closes. When reopened, it shows the guest startup process as aborted (because I had closed it), and then anything I try to do instantly closes VB. So without having actually started up (at 0% completion and then hanging) I don't see where there would even be a log. And the VB 4.3 install log appears to show that all was well there. This is all still farther than I ever got with Fedora 19, though.

[Perryg]

The guests log file is a simple text file that is stored in the VirtualBox VMs -> guests folder -> logs. One is created each time you start the boot process even if there is no guest actually installed.

[Falstaff1141]

No guests folder in VirtualBox VMs directory, and since I only tried to start the Whonix Gateway there is only the .vbox, .vbox-prev, and disk1.vmdk there for that attempted start. No log files to be found. Perhaps I am missing something?

[Falstaff1141]

I switched the machine to Linux Mint 16 Mate and got VB working fine and my vm's are working now, too. The log files did not appear in the Home directory until the guests had been fully booted and up and running; simply running the Import Appliance and having it hang at 0 did not produce any logs. Thanks for the suggestions and tips, though.

[jasmine]

I had the same issue. I solved that by repair Virtual Box. reboot the server and remote connect the vm to start.

[kcuf]

same problem, attachment is error log.

[NG]

For this issue I did reinstall my Windows 7, and reproduce this problem:
Step1: Install Windows 7
Step2: Install VirtualBox 4.3.20, create VM and runing is normal.
Step3: Install Chrome
Step4: Create VM succesful, BUT can NOT start any VM, handle in "Create Process for Virtual Machine XXX (GUI/Qt)"
Step5: uninstall Chrome, and repair or reinstall VirtualBox, issue still exists.
CAN NOT solve this problem in addition to reinstall the operating system