Bug 763663 (GLUSTER-1931)

Summary: Using the new GA 3.1.0 Platform ISO, X-Windows doesn't auto start
Product: [Retired] GlusterSP Reporter: Jacob Shucart <jacob>
Component: coreAssignee: Timothy Asir <timothyasir>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: urgent    
Version: 3.1.0CC: fharshav, platform, rahulcs, shireesh
Target Milestone: 3.1.2   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Harshavardhana 2010-10-12 13:57:33 UTC
(In reply to comment #0)
> I created a brand new VM and went to do the install using the ISO.  X-Windows
> didn't start.  I had to login and run startx to get it to a point where I could
> install the product...

Jacob, 

   I think we saw this issue too when using with Craig and Allen, i think it could be a xorg config issue, since the init levels have not changed since 3.0.x releases.

Comment 1 Jacob Shucart 2010-10-12 14:34:03 UTC
I marked it as urgent because anybody who tries to use the ISO for installation will run into the issue, and ISO would be the first thing I would try myself.

Comment 2 Balamurugan Arumugam 2010-10-12 14:45:34 UTC
I checked it locally which worked fine on VM Player.  I will try to reproduce it to find the problem.

Comment 3 Jacob Shucart 2010-10-12 14:50:34 UTC
Using KVM on CentOS if that helps...

Comment 4 Jacob Shucart 2010-10-12 16:48:25 UTC
I created a brand new VM and went to do the install using the ISO.  X-Windows didn't start.  I had to login and run startx to get it to a point where I could install the product...

Comment 5 Balamurugan Arumugam 2010-10-20 09:25:05 UTC
The problem has been seen in VMPlayer.  Strangely the problem disappears if VM is power-reset.

Comment 6 Harshavardhana 2010-10-20 09:31:31 UTC
Could be related to video card of VMware itself and the drivers we have with splash enabled. 

Also we might need to edit the "vmx" file to check if there are certain video adapters which might not work with platform and vmware.

Comment 7 Jacob Shucart 2010-10-27 20:09:11 UTC
volume set mirror performance.quick-read off
 figured it out looking at:

gluster src/xlators/mgmt/glusterd/src/glusterd-volgen.c

in the:

static struct volopt_map_entry glusterd_volopt_map[] = {

Comment 8 Jacob Shucart 2010-10-28 12:55:56 UTC
Ignore comment #7... that was for bug 763759.

Comment 9 Rahul C S 2010-11-11 10:11:38 UTC
This seems to be the difference between the Xorg logs of a VM booted unsuccessfully and another VM booted successfully.

[root@test log]# diff Xorg.0.log /home/gluster/Xorg.0.log 
6,7c6,7
< Current Operating System: Linux test 2.6.30.10-105.2.4.fc11.x86_64 #1 SMP Tue Jan 19 22:46:59 UTC 2010 x86_64
< Kernel command line: ro root=UUID=b50b36aa-9e61-4317-8671-c34b8010a18b roottypefs=ext3 blacklist=floppy rhgb nomodeset quiet
---
> Current Operating System: Linux ctdb2 2.6.30.10-105.2.4.fc11.x86_64 #1 SMP Tue Jan 19 22:46:59 UTC 2010 x86_64
> Kernel command line: ro root=UUID=22225465-0453-4fd2-bdf3-c584f4bc62c9 roottypefs=ext3 blacklist=floppy rhgb nomodeset quiet
15c15
< (==) Log file: "/var/log/Xorg.0.log", Time: Thu Nov  4 15:21:14 2010
---
> (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 10 18:52:38 2010
442,450c442,448
< (II) VMWARE(0): VMMOUSE DEVICE_OFF/CLOSE
< (II) VMWARE(0): VMMouseUnInit
< (II) Macintosh mouse button emulation: Close
< (II) UnloadModule: "evdev"
< (II) AT Translated Set 2 keyboard: Close
< (II) UnloadModule: "evdev"
< (II) Power Button: Close
< (II) UnloadModule: "evdev"
< (II) VMWARE(0): Terminating Xv video-stream id:0
---
> (II) No APM support in BIOS or kernel
> (II) VMWARE(0): VMMOUSE DEVICE_ON
> (II) VMWARE(0): vmmouse enabled
> (II) Macintosh mouse button emulation: Device reopened after 1 attempts.
> (II) AT Translated Set 2 keyboard: Device reopened after 1 attempts.
> (II) Power Button: Device reopened after 1 attempts.
> (II) VMWARE(0): vmmouse enable absolute mode


/var/log/slim.log contains,
slim: unexpected signal 13
which is a SIGPIPE.

Will try to reproduce the issue again and check if there's any kind of pattern in the logs.

Comment 10 Timothy Asir 2010-12-15 03:54:57 UTC
*** Bug 2224 has been marked as a duplicate of this bug. ***