Opened 13 years ago
Closed 10 years ago
#9550 closed defect (obsolete)
VirtualBox can't run Windows guest (XP or 7) on a SuSE Enterprise 11 SP1 Host
| Reported by: | junaidnaseer | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.1.2 |
| Keywords: | Cc: | ||
| Guest type: | Windows | Host type: | Linux |
Description (last modified by )
Anytime, I try to run the windows (XP or 7) on a SuSE Linux Enterprise 11 SP1 host, it gives the following error and shuts down ... The same does not happen with a Linux or Solaris guest. I recently installed some applications from the SuSE repository. Maybe they have had the effect.
I have attached the VBox log. The bug report generated by the gnome bug tracker and the recent application list, I installed.
If VBox can't run windows, then that pretty much ends the story ...
Failed to open a session for the virtual machine Windows XP.
No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE) Component: ProgressProxy Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
Attachments (22)
Change History (30)
by , 13 years ago
| Attachment: | <unknown>-bugreport.txt added |
|---|
by , 13 years ago
| Attachment: | <unknown>-bugreport2_2.txt added |
|---|
The gnome bug tracker file (2nd part)
by , 13 years ago
list of recent applications installed after which the error the started
comment:1 by , 13 years ago
Sounds like the VBoxSVC daemon is crashing. Can you confirm that, i.e. when you get this error, is the VBoxSVC process still running? Is a VBox.log file for that specific VM created? If so, please attach it to this ticket.
comment:2 by , 13 years ago
Oh ... sorry ... I posted the wrong log files ... I just read that the logs are created in the .VirtualBox directory and copied those ... didn't know that machine specific logs are also created BUT inside the machine's own folder ...
I will attach those logs now too ...
yes the VboxSVC runs and I can see it in the gnome system monitor in the list of running processes ...
p.s. in case, I haven't mentioned, this, I tried installing the previous versions of VBox (between 4 and 4.1) but all of them turned up with the same error too ...
thanks ...
comment:3 by , 13 years ago
Hi! I think that I have the same problem and I found a temporary solution. First the info of the system: openSUSE 11.4 64-bit with VirtualBox 4.1.2
The problems started after an update of the openSUSE system - during this update the kernel was updated. uname -a shows: 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 x86_64 x86_64 x86_64 GNU/Linux
I have several virtual machines and some of them started to have problems (windows and linux guests). The error message was: No error info.
Result Code: NS_ERROR_CALL_FAILED (0x800706BE) Component: ProgressProxy? Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}
I have found that the problematic machines were only those which have the options enabled for 3D and 2D video acceleration. The interesting thing was that the two options were grayed out in the vbox GUI, so I wasn't able to change (disable) those settings. So I opened the config files of the problematic machines ($HOME/.VirtualBox/Machines/MyMachine/MyMachine.xml) with an text editor and changed the line where the 3D and 2D video acceleration was enabled to false: <Display VRAMSize="128" monitorCount="1" accelerate3D="false" accelerate2DVideo="false"/>
After that change the virtual machines started to work normally - except that the 3D and 2D video acceleration is now disabled!
Hope that this temporary solution work for somebody.
comment:4 by , 13 years ago
thanks for the feedback ... I had qemu installed on my host system ... I don't know if that was the reason but once I removed the qemu and kvm and xen and all their related packages, I could boot all my virtual machines in virtualbox and vmware ... (yes, earlier both vmware and virtualbox couldn't boot windows !)
(sorry for mentioning other products here ...)
and now, I see the same thing that, 2D and 3D acceleration is grayed out in virtualbox and unchecked ! I I don't know why ! but I don't care ... my virtual machines boot just fine and virtualbox is gr8 for my needs, with or without the 2D / 3D acceleration ...
there is the possibility that I have a the oracle virtualbox extended package installed ... I didn't have that before ...
cheers ...
comment:5 by , 13 years ago
and the virtualbox extended box fixed the issue ... I don't know ... maybe ... :)
comment:6 by , 12 years ago
Hi again!
Today I have found a final solution to this problem! A have noticed that after upgrading the kernel also some other programs stopped working, but with a different error output (when I started them from the terminal). On one forum I have found some info, that the problematic thing was the video driver of the graphic card (ATI) and that the solution was to first delete "x11-video-fglrxG02" and "ati-fglrxG02-kmp-desktop" packets, reboot the system, reinstall the two packets again and reboot the system. After doing this all the problematic programs started working normally and also the problematic vbox machines (with 3D enabled) started to work normally!
bye
comment:7 by , 12 years ago
@mbadalic ...
Thank you very much. That really did solve all the problems. Windows 7 running inside the SuSE Linux with 2D and 3D support enabled ...
Thank you again.
comment:8 by , 10 years ago
| Description: | modified (diff) |
|---|---|
| Resolution: | → obsolete |
| Status: | new → closed |
The gnome bug tracker file (first part)