Bugzilla – Bug 99358
unable to run sax2 on suse 10 in vmware 5.
Last modified: 2005-08-19 18:08:06 UTC
I am able to run sax2 on a regular machine just fine. However, when running sax2 in vmware, it fails to launch. It also fails to display the graphics monitor setting during the install in vmware.
Hmm, unfortunately I do not have the possibility to test that here. I don't have a license. Can you call the command: sax2 -p and tell me what it is printing on STDOUT Additionally please call sax2 -r and send me the log file /var/log/SaX.log The vmware driver must be installed in your guest system (vmware-tools) to be able to get that running. During installation this driver is part of the inst-sys but this scenario hasn't been tested for a long time
> The vmware driver must be installed in your guest system (vmware-tools) > to be able to get that running. During installation this driver is part > of the inst-sys but this scenario hasn't been tested for a long time I have never had to install the vmware-tools to run sax2. I have had to install them to get 24 bit depth, but not to run sax2. I will however get the requested information and send it to you.
Created attachment 44101 [details] output of sax2 -p
Created attachment 44102 [details] sax.log
I am also able to reproduce this on VMWare 5. I also suspect it is causing problems with the "Hardware Configuration" module while installing. See bug #100602
I had the same problem. The attachment (id=44101) is not very helpful. root should get access to the display (xhost +, xauth or the like). But then again: sax2 dies.
Created attachment 45462 [details] output of "sax -p" and "sax -r" I had no root-authentication problems after I allowed all access (xhost +).
Created attachment 45463 [details] /var/log/SaX.log of a "sax2 -r" run as root SaX2 switched the video mode multiple times. SaX2 opened the "Importing Data" window. SaX2 stops without any further info.
*** Bug 103052 has been marked as a duplicate of this bug. ***
I'm sorry i cannot manage to get that vmware thing to run on the current STABLE code: While building the vm modules I got: ---snip--- /tmp/vmware-config1/vmnet-only/bridge.c: In function ‘VNetBridgeReceiveFromVNet’ : /tmp/vmware-config1/vmnet-only/bridge.c:464: error: ‘struct sock’ has no member named ‘wmem_alloc’ /tmp/vmware-config1/vmnet-only/bridge.c: In function ‘VNetBridgeUp’: /tmp/vmware-config1/vmnet-only/bridge.c:721: warning: passing argument 3 of ‘sk_ alloc’ makes pointer from integer without a cast /tmp/vmware-config1/vmnet-only/bridge.c:721: warning: passing argument 4 of ‘sk_ alloc’ makes integer from pointer without a cast make[2]: *** [/tmp/vmware-config1/vmnet-only/bridge.o] Error 1 make[1]: *** [_module_/tmp/vmware-config1/vmnet-only] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.13-rc6-git1-2' make: *** [vmnet.ko] Error 2 make: Leaving directory `/tmp/vmware-config1/vmnet-only' Unable to build the vmnet module. For more information on how to troubleshoot module-related problems, please visit our Web site at "http://www.vmware.com/download/modules/modules.html" and "http://www.vmware.com/support/reference/linux/prebuilt_modules_linux.html". Execution aborted. ---snap--- Another problem is that I don't have a key to manage installing anything in vmware. giving up now... sorry
I have no idea, what exactly STABLE is but vmware 5 runs perfectly in SuSE 9.3. We have several OSs (even Solaris x86) running inside vmware 5 with SuSE 9.3 as host. It is mandatory for a new version of any x86 operating system to operate as a guest inside vmware. How else do you think any big customer will evaluate SL10? If you really need to compile the vmware module, look at http://www.vmware.com/community/thread.jspa?threadID=19497&start=0&tstart=0 They solved a similar problem. You run vmware, you can get a 30 day key for free from http://www.vmware.com/vmwarestore/newstore/wkst_eval_login.jsp
my test machines and even my workstation is running at the leading edge of development which is 10.0 (beta1) ... called stable. I expect vmware to run on that system as host based application first before starting to fix bugs within the guest system. If our customers arent't able to setup vmware on their host system they are not able to install any OS as guest system ;) It's nice that vmware is running on 9.3 but we are currently developing 10.0 and SLES10. as you may know vmware is emulating graphics card hardware and this emulation may be different from the host based implementation between 9.3 and 10.0. In almost all cases the problem is within the X11 vmware driver itself so in my opinion it's really important for testing purposes to have the host and the guest at the same level to recognize the defect.
we have a vmware GSX server here with SuSE. I will use this server (v3.x.x) and try to reproduce the bug, but please note this is not vmware v5 and this not a workstation installation
ok, vmware X11 configuration is working now :-)
*** Bug 104077 has been marked as a duplicate of this bug. ***
*** Bug 104144 has been marked as a duplicate of this bug. ***
*** Bug 100602 has been marked as a duplicate of this bug. ***
When VMware-tools are installed on the SuSE 10.0b1 virtual machine running under VMware GSX 3.2, everything works just fine. SaX2 still cannot be used to change resolutions, but that is managed with the vmware-tools interface. In fact, SaX2 doesn't even start..
beta1 doesn't have that fix, please test with beta2
Verified as working really fine with beta2 under VMware GSX 3.2 Both installation and SaX2 in a installed system works fine for me.
working in beta 2. Closing the bug.