Menu
▾
▴
vizstack-users — Mailing list for everyone who uses VizStack
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
(3) |
Mar
(8) |
Apr
(26) |
May
(41) |
Jun
(3) |
Jul
(19) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2011 |
Jan
(17) |
Feb
(5) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Kumar, S. <shr...@hp...> - 2010-05-28 04:21:26
|
> You're arranging the blocks in rows and disabling the right-most output >of each row - explaining it like that should help . . . but I've spent > the whole evening trying to think of a good concise way to explain it, > and so far nothing. I'll think about it some more and see if I can suggest > anything, but it really is quite hard to explain clearly. I'm hoping to add some images. Can't think of anything better for now. > One question: is it possible (or meaningful) to use a value of [None,1] > or similar? It seems like it would disable the first output on the GPU > rather than the second, which might be useful in some cases . . . The first element corresponds to the clipping applied to the last column. The second element corresponds to the clipping applied to the last row. Using [None,1] would clip all displays that form the last row. E.g. if you were driving [1,2] from every GPU, this would be useful. If you were using a QuadroPlex, both would elements could be used together, since it can drive upto 4 displays as one unit. > Also, does it /have/ to be the last GPU in the row? It might be nice to be > able to set up, say, a 5x5 display with the odd monitor in each row being in > the middle. Obviously very low priority, but still possibly useful. Also, how > hard would it be to support arbitrary mixing of different types of blocks? We > have a 5x5 system (completely unrelated to the stuff I'm working on right now > - it uses CGLX as the display system) which has the fifth column made up of two > vertical pairs and a singleton, with the rest of the display made up of horizontal > pairs - as it stands I think Vizstack would have to have the whole fifth column > made up of singleton monitors. In practice it's probably not an issue, but if > supporting arbitrary mixes of blocks is easy it might be something to consider > for a future version. Good points. To me, arbitrary mixing of different types of blocks is the way to go. The current mechanism is a quick plug; it is something easier to understand and configure, but with the drawback of not handling all cases. Setting up arbitrary mixing of blocks is not difficult. However, preventing users from making mistakes, and describing arbitrary layouts is where the work is. Visualizing mix of blocks poses a problem too, perhaps a GUI is the best way to create them (and not command line tools OR handwritten config files.) Also, with arbitrary blocks, we need some more "intelligence" in scripts for applications that can't handle all types of Tiled Displays. I've never used CGLX before. However, I have asked them for a password to download. Could you describe how you've configured your CGLX tiled display ? Quite by coincidence, I did some reading about CGLX yesterday (A paper on CGLX is getting published in TCVG). Do you think it makes sense to use CGLX inside VizStack ? That way, GPUs could be used for CGLX or other purposes on demand. > And one final question: if you have a single GPU with four outputs, would > you have to make each block 4x1, or could you make them 2x2? i.e. to get > a 3x2 display would you need to have two rows of 4x1 blocks, or could you > use one row of 2x2 blocks? I doubt there's any hardware out there where > this would be an issue, but I imagine there's stuff on the horizon . . . You would be able to make each block 4x1 or 2x2, or anything in between (that's what we support for the QuadroPlex block). Do you have any GPU that supports 4 displays ? Your QuadroNVS is actually two GPUs in one, with each capable of driving 2 displays at once. Current nVidia cards support 2 displays in one, and they call that support "TwinView". They will come out with more, and configuring them will need additional options in the config file I guess. When such GPUs are available, we will handle them. Regards -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Thursday, May 27, 2010 7:47 PM To: viz...@li... Subject: Re: [vizstack-users] viz-desktop should now work with bezels > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Thursday, 27 May 2010 3:57 PM > To: viz...@li... > Subject: Re: [vizstack-users] viz-desktop should now work with bezels > > > I'm an atheist, but will take the compliments :-) > > > Aside from being caught out at first by using 'none' instead of > > 'None', and having to rearrange the cabling (thankfully > displayport is > > much nicer than DVI in that regard), it was as simple as > creating the > > tiled display and adding the clip_last_block line. Running > from the console works perfectly. > > Yeah, the cabling is irregular with this setup. Is this setup > hard to understand ? > Not too hard once I realised how it needed to be arranged. > One reason I haven't add this to the vs-manage-tiled-displays > tool is : I find it complicated to explain ! > Any hints w.r.t explaining this would be useful. > You're arranging the blocks in rows and disabling the right-most output of each row - explaining it like that should help . . . but I've spent the whole evening trying to think of a good concise way to explain it, and so far nothing. I'll think about it some more and see if I can suggest anything, but it really is quite hard to explain clearly. > > Thanks for implementing this so quickly! > > As I said, this turned out to be fairly simple in the end. > The same mechanism works with QuadroPlexes too, but nobody > seems to be using more than one QuadroPlex at the moment with > VizStack. And now others can use this too. > It's definitely a very nice feature. One question: is it possible (or meaningful) to use a value of [None,1] or similar? It seems like it would disable the first output on the GPU rather than the second, which might be useful in some cases . . . Also, does it /have/ to be the last GPU in the row? It might be nice to be able to set up, say, a 5x5 display with the odd monitor in each row being in the middle. Obviously very low priority, but still possibly useful. Also, how hard would it be to support arbitrary mixing of different types of blocks? We have a 5x5 system (completely unrelated to the stuff I'm working on right now - it uses CGLX as the display system) which has the fifth column made up of two vertical pairs and a singleton, with the rest of the display made up of horizontal pairs - as it stands I think Vizstack would have to have the whole fifth column made up of singleton monitors. In practice it's probably not an issue, but if supporting arbitrary mixes of blocks is easy it might be something to consider for a future version. And one final question: if you have a single GPU with four outputs, would you have to make each block 4x1, or could you make them 2x2? i.e. to get a 3x2 display would you need to have two rows of 4x1 blocks, or could you use one row of 2x2 blocks? I doubt there's any hardware out there where this would be an issue, but I imagine there's stuff on the horizon . . . Lots of extra questions - none of them very critical for us, since with this update you've resolved the last outstanding issue we had. Thanks, Simon ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: <Sim...@cs...> - 2010-05-27 14:16:56
|
> -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Thursday, 27 May 2010 3:57 PM > To: viz...@li... > Subject: Re: [vizstack-users] viz-desktop should now work with bezels > > > I'm an atheist, but will take the compliments :-) > > > Aside from being caught out at first by using 'none' instead of > > 'None', and having to rearrange the cabling (thankfully > displayport is > > much nicer than DVI in that regard), it was as simple as > creating the > > tiled display and adding the clip_last_block line. Running > from the console works perfectly. > > Yeah, the cabling is irregular with this setup. Is this setup > hard to understand ? > Not too hard once I realised how it needed to be arranged. > One reason I haven't add this to the vs-manage-tiled-displays > tool is : I find it complicated to explain ! > Any hints w.r.t explaining this would be useful. > You're arranging the blocks in rows and disabling the right-most output of each row - explaining it like that should help . . . but I've spent the whole evening trying to think of a good concise way to explain it, and so far nothing. I'll think about it some more and see if I can suggest anything, but it really is quite hard to explain clearly. > > Thanks for implementing this so quickly! > > As I said, this turned out to be fairly simple in the end. > The same mechanism works with QuadroPlexes too, but nobody > seems to be using more than one QuadroPlex at the moment with > VizStack. And now others can use this too. > It's definitely a very nice feature. One question: is it possible (or meaningful) to use a value of [None,1] or similar? It seems like it would disable the first output on the GPU rather than the second, which might be useful in some cases . . . Also, does it /have/ to be the last GPU in the row? It might be nice to be able to set up, say, a 5x5 display with the odd monitor in each row being in the middle. Obviously very low priority, but still possibly useful. Also, how hard would it be to support arbitrary mixing of different types of blocks? We have a 5x5 system (completely unrelated to the stuff I'm working on right now - it uses CGLX as the display system) which has the fifth column made up of two vertical pairs and a singleton, with the rest of the display made up of horizontal pairs - as it stands I think Vizstack would have to have the whole fifth column made up of singleton monitors. In practice it's probably not an issue, but if supporting arbitrary mixes of blocks is easy it might be something to consider for a future version. And one final question: if you have a single GPU with four outputs, would you have to make each block 4x1, or could you make them 2x2? i.e. to get a 3x2 display would you need to have two rows of 4x1 blocks, or could you use one row of 2x2 blocks? I doubt there's any hardware out there where this would be an issue, but I imagine there's stuff on the horizon . . . Lots of extra questions - none of them very critical for us, since with this update you've resolved the last outstanding issue we had. Thanks, Simon |
|
From: Kumar, S. <shr...@hp...> - 2010-05-27 06:00:08
|
I'm an atheist, but will take the compliments :-)
> Aside from being caught out at first by using 'none' instead of 'None', and
> having to rearrange the cabling (thankfully displayport is much nicer than DVI in that regard),
> it was as simple as creating the tiled display and adding the clip_last_block line. Running
> from the console works perfectly.
Yeah, the cabling is irregular with this setup. Is this setup hard to understand ?
One reason I haven't add this to the vs-manage-tiled-displays tool is : I find it complicated to explain !
Any hints w.r.t explaining this would be useful.
> Thanks for implementing this so quickly!
As I said, this turned out to be fairly simple in the end. The same mechanism works with QuadroPlexes too,
but nobody seems to be using more than one QuadroPlex at the moment with VizStack. And now others can use this too.
Regards
-- Shree
-----Original Message-----
From: Sim...@cs... [mailto:Sim...@cs...]
Sent: Thursday, May 27, 2010 11:18 AM
To: viz...@li...
Subject: Re: [vizstack-users] viz-desktop should now work with bezels
You are truly a god among developers - this works perfectly, straight out of the blocks. Here's the config I'm using:
</resourceGroup><resourceGroup>
<name>3x2-rearranged</name>
<handler>tiled_display</handler>
<description>Rearranged connections</description>
<handler_params>
block_type='gpu';
num_blocks=[2,2];
block_display_layout=[2, 1];
group_blocks=[2, 2];
combine_displays=True;
display_device='Dell 3008WFP';
display_mode='2560x1600_60';
remap_display_outputs=[2,3];
framelock=False;
clip_last_block=[1,None];
</handler_params>
<resources>
<reslist>
<res><server><hostname>localhost</hostname></server></res>
<res><gpu><hostname>localhost</hostname><index>0</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>1</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>2</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>3</index></gpu></res>
<res><keyboard><index>0</index><hostname>localhost</hostname></keyboard></res>
<res><mouse><index>0</index><hostname>localhost</hostname></mouse></res>
</reslist>
</resources>
</resourceGroup></resourcegroupconfig>
Aside from being caught out at first by using 'none' instead of 'None', and having to rearrange the cabling (thankfully displayport is much nicer than DVI in that regard), it was as simple as creating the tiled display and adding the clip_last_block line. Running from the console works perfectly.
Thanks for implementing this so quickly!
Simon
> -----Original Message-----
> From: Kumar, Shree [mailto:shr...@hp...]
> Sent: Thursday, 27 May 2010 2:50 PM
> To: viz...@li...
> Subject: Re: [vizstack-users] viz-desktop should now work with bezels
>
> Hi Simon,
>
> Thanks for the confirmation.
>
> And here is a last goodie (for the time being at least!) :
> I've added another property to tiled displays(TD), called
> "clip_last_block". This is a two element vector that makes
> the TD logic skip configuration of display(s) on the last row
> and/or column.
>
> With this, you will be able to create a 3x2 desktop using the
> your 4 GPUs. Here is how :
>
> - Define a 4x2 Tiled display that uses the 4 GPUs. This
> would mean a block_display_layout of [2,1]
>
> - Set clip_last_block to [1,None]. This will skip
> configuration of the second display on
> the second GPU in each row. This needs to be done
> manually in the config file.
>
> - Restart the SSM, try out the tiled display.
>
> Here is an example 3x1 desktop TD in my lab:
> ----------------
> <resourceGroup>
> <name>3x1-clipped</name>
> <handler>tiled_display</handler>
> <description>2x2</description>
> <handler_params>
> block_type='gpu';
> num_blocks=[2,1];
> block_display_layout=[2, 1];
> group_blocks=[2, 1];
> combine_displays=True;
> display_device='HP LP2065';
> display_mode='1600x1200_60';
> framelock=False;
> clip_last_block=[1,None];
> </handler_params>
> <resources>
> <reslist>
>
> <res><server><hostname>localhost</hostname></server></res>
>
> <res><gpu><hostname>localhost</hostname><index>0</index></gpu></res>
>
> <res><gpu><hostname>localhost</hostname><index>1</index></gpu></res>
>
> <res><keyboard><index>0</index><hostname>localhost</hostname><
> /keyboard></res>
>
> <res><mouse><index>0</index><hostname>localhost</hostname></mo
> use></res>
> </reslist>
> </resources>
> </resourceGroup>
> -----------------
>
> In your case, you would have num_blocks = [2,2], and two more
> GPUs in the reslist.
>
> This was surprisingly easy to implement, and quite generic -
> a tiled display can now consist of odd number of rows/columns
> with all GPU capabilities being utilized. I'm sure this
> mechanism would suit many users.
>
> To use : update svn, shree branch.
>
> ----
>
> Overall, what does this mean for you ? You can define the 3x2
> tiled display using your 4 GPUs.
> Users can run viz-desktop by logging into the console. No
> other customization required !
>
> HTH
> -- Shree
>
> -----Original Message-----
> From: Sim...@cs... [mailto:Sim...@cs...]
> Sent: Thursday, May 27, 2010 4:34 AM
> To: viz...@li...
> Subject: Re: [vizstack-users] viz-desktop should now work with bezels
>
> Tested, and it seems to be working nicely - no panning,
> everything's behaving as expected. Thanks for this!
>
> Simon
>
> > -----Original Message-----
> > From: Kumar, Shree [mailto:shr...@hp...]
> > Sent: Tuesday, 25 May 2010 9:48 PM
> > To: viz...@li...
> > Subject: [vizstack-users] viz-desktop should now work with bezels
> >
> > Hi Simon,
> >
> > I had raised an issue with nvidia about the desktop bezel problem.
> > They have come back and clarified that it is not a bug, but the
> > expected behaviour. However, good things have come out of the
> > interaction. They have suggested an alternate way of
> configuring, and
> > I have fixed my code appropriately.
> >
> > If you update the shree branch, and try the viz-desktop script with
> > -B, you should get a desktop cofigured correctly.
> > Can you try it and confirm that it works ?
> >
> > Thanks
> > -- Shree
> >
> > --------------------------------------------------------------
> > ----------------
> >
> > _______________________________________________
> > vizstack-users mailing list
> > viz...@li...
> > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> >
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
------------------------------------------------------------------------------
_______________________________________________
vizstack-users mailing list
viz...@li...
https://lists.sourceforge.net/lists/listinfo/vizstack-users
|
|
From: <Sim...@cs...> - 2010-05-27 05:48:37
|
You are truly a god among developers - this works perfectly, straight out of the blocks. Here's the config I'm using:
</resourceGroup><resourceGroup>
<name>3x2-rearranged</name>
<handler>tiled_display</handler>
<description>Rearranged connections</description>
<handler_params>
block_type='gpu';
num_blocks=[2,2];
block_display_layout=[2, 1];
group_blocks=[2, 2];
combine_displays=True;
display_device='Dell 3008WFP';
display_mode='2560x1600_60';
remap_display_outputs=[2,3];
framelock=False;
clip_last_block=[1,None];
</handler_params>
<resources>
<reslist>
<res><server><hostname>localhost</hostname></server></res>
<res><gpu><hostname>localhost</hostname><index>0</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>1</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>2</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>3</index></gpu></res>
<res><keyboard><index>0</index><hostname>localhost</hostname></keyboard></res>
<res><mouse><index>0</index><hostname>localhost</hostname></mouse></res>
</reslist>
</resources>
</resourceGroup></resourcegroupconfig>
Aside from being caught out at first by using 'none' instead of 'None', and having to rearrange the cabling (thankfully displayport is much nicer than DVI in that regard), it was as simple as creating the tiled display and adding the clip_last_block line. Running from the console works perfectly.
Thanks for implementing this so quickly!
Simon
> -----Original Message-----
> From: Kumar, Shree [mailto:shr...@hp...]
> Sent: Thursday, 27 May 2010 2:50 PM
> To: viz...@li...
> Subject: Re: [vizstack-users] viz-desktop should now work with bezels
>
> Hi Simon,
>
> Thanks for the confirmation.
>
> And here is a last goodie (for the time being at least!) :
> I've added another property to tiled displays(TD), called
> "clip_last_block". This is a two element vector that makes
> the TD logic skip configuration of display(s) on the last row
> and/or column.
>
> With this, you will be able to create a 3x2 desktop using the
> your 4 GPUs. Here is how :
>
> - Define a 4x2 Tiled display that uses the 4 GPUs. This
> would mean a block_display_layout of [2,1]
>
> - Set clip_last_block to [1,None]. This will skip
> configuration of the second display on
> the second GPU in each row. This needs to be done
> manually in the config file.
>
> - Restart the SSM, try out the tiled display.
>
> Here is an example 3x1 desktop TD in my lab:
> ----------------
> <resourceGroup>
> <name>3x1-clipped</name>
> <handler>tiled_display</handler>
> <description>2x2</description>
> <handler_params>
> block_type='gpu';
> num_blocks=[2,1];
> block_display_layout=[2, 1];
> group_blocks=[2, 1];
> combine_displays=True;
> display_device='HP LP2065';
> display_mode='1600x1200_60';
> framelock=False;
> clip_last_block=[1,None];
> </handler_params>
> <resources>
> <reslist>
>
> <res><server><hostname>localhost</hostname></server></res>
>
> <res><gpu><hostname>localhost</hostname><index>0</index></gpu></res>
>
> <res><gpu><hostname>localhost</hostname><index>1</index></gpu></res>
>
> <res><keyboard><index>0</index><hostname>localhost</hostname><
> /keyboard></res>
>
> <res><mouse><index>0</index><hostname>localhost</hostname></mo
> use></res>
> </reslist>
> </resources>
> </resourceGroup>
> -----------------
>
> In your case, you would have num_blocks = [2,2], and two more
> GPUs in the reslist.
>
> This was surprisingly easy to implement, and quite generic -
> a tiled display can now consist of odd number of rows/columns
> with all GPU capabilities being utilized. I'm sure this
> mechanism would suit many users.
>
> To use : update svn, shree branch.
>
> ----
>
> Overall, what does this mean for you ? You can define the 3x2
> tiled display using your 4 GPUs.
> Users can run viz-desktop by logging into the console. No
> other customization required !
>
> HTH
> -- Shree
>
> -----Original Message-----
> From: Sim...@cs... [mailto:Sim...@cs...]
> Sent: Thursday, May 27, 2010 4:34 AM
> To: viz...@li...
> Subject: Re: [vizstack-users] viz-desktop should now work with bezels
>
> Tested, and it seems to be working nicely - no panning,
> everything's behaving as expected. Thanks for this!
>
> Simon
>
> > -----Original Message-----
> > From: Kumar, Shree [mailto:shr...@hp...]
> > Sent: Tuesday, 25 May 2010 9:48 PM
> > To: viz...@li...
> > Subject: [vizstack-users] viz-desktop should now work with bezels
> >
> > Hi Simon,
> >
> > I had raised an issue with nvidia about the desktop bezel problem.
> > They have come back and clarified that it is not a bug, but the
> > expected behaviour. However, good things have come out of the
> > interaction. They have suggested an alternate way of
> configuring, and
> > I have fixed my code appropriately.
> >
> > If you update the shree branch, and try the viz-desktop script with
> > -B, you should get a desktop cofigured correctly.
> > Can you try it and confirm that it works ?
> >
> > Thanks
> > -- Shree
> >
> > --------------------------------------------------------------
> > ----------------
> >
> > _______________________________________________
> > vizstack-users mailing list
> > viz...@li...
> > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> >
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
|
|
From: Kumar, S. <shr...@hp...> - 2010-05-27 04:52:58
|
Hi Simon,
Thanks for the confirmation.
And here is a last goodie (for the time being at least!) : I've added another property to
tiled displays(TD), called "clip_last_block". This is a two element vector that makes the
TD logic skip configuration of display(s) on the last row and/or column.
With this, you will be able to create a 3x2 desktop using the your 4 GPUs. Here is how :
- Define a 4x2 Tiled display that uses the 4 GPUs. This would mean a block_display_layout of [2,1]
- Set clip_last_block to [1,None]. This will skip configuration of the second display on
the second GPU in each row. This needs to be done manually in the config file.
- Restart the SSM, try out the tiled display.
Here is an example 3x1 desktop TD in my lab:
----------------
<resourceGroup>
<name>3x1-clipped</name>
<handler>tiled_display</handler>
<description>2x2</description>
<handler_params>
block_type='gpu';
num_blocks=[2,1];
block_display_layout=[2, 1];
group_blocks=[2, 1];
combine_displays=True;
display_device='HP LP2065';
display_mode='1600x1200_60';
framelock=False;
clip_last_block=[1,None];
</handler_params>
<resources>
<reslist>
<res><server><hostname>localhost</hostname></server></res>
<res><gpu><hostname>localhost</hostname><index>0</index></gpu></res>
<res><gpu><hostname>localhost</hostname><index>1</index></gpu></res>
<res><keyboard><index>0</index><hostname>localhost</hostname></keyboard></res>
<res><mouse><index>0</index><hostname>localhost</hostname></mouse></res>
</reslist>
</resources>
</resourceGroup>
-----------------
In your case, you would have num_blocks = [2,2], and two more GPUs in the reslist.
This was surprisingly easy to implement, and quite generic - a tiled display can now consist
of odd number of rows/columns with all GPU capabilities being utilized. I'm sure this mechanism
would suit many users.
To use : update svn, shree branch.
----
Overall, what does this mean for you ? You can define the 3x2 tiled display using your 4 GPUs.
Users can run viz-desktop by logging into the console. No other customization required !
HTH
-- Shree
-----Original Message-----
From: Sim...@cs... [mailto:Sim...@cs...]
Sent: Thursday, May 27, 2010 4:34 AM
To: viz...@li...
Subject: Re: [vizstack-users] viz-desktop should now work with bezels
Tested, and it seems to be working nicely - no panning, everything's behaving as expected. Thanks for this!
Simon
> -----Original Message-----
> From: Kumar, Shree [mailto:shr...@hp...]
> Sent: Tuesday, 25 May 2010 9:48 PM
> To: viz...@li...
> Subject: [vizstack-users] viz-desktop should now work with bezels
>
> Hi Simon,
>
> I had raised an issue with nvidia about the desktop bezel
> problem. They have come back and clarified that it is not a
> bug, but the expected behaviour. However, good things have
> come out of the interaction. They have suggested an alternate
> way of configuring, and I have fixed my code appropriately.
>
> If you update the shree branch, and try the viz-desktop
> script with -B, you should get a desktop cofigured correctly.
> Can you try it and confirm that it works ?
>
> Thanks
> -- Shree
>
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
------------------------------------------------------------------------------
_______________________________________________
vizstack-users mailing list
viz...@li...
https://lists.sourceforge.net/lists/listinfo/vizstack-users
|
|
From: <Sim...@cs...> - 2010-05-26 23:04:16
|
Tested, and it seems to be working nicely - no panning, everything's behaving as expected. Thanks for this! Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Tuesday, 25 May 2010 9:48 PM > To: viz...@li... > Subject: [vizstack-users] viz-desktop should now work with bezels > > Hi Simon, > > I had raised an issue with nvidia about the desktop bezel > problem. They have come back and clarified that it is not a > bug, but the expected behaviour. However, good things have > come out of the interaction. They have suggested an alternate > way of configuring, and I have fixed my code appropriately. > > If you update the shree branch, and try the viz-desktop > script with -B, you should get a desktop cofigured correctly. > Can you try it and confirm that it works ? > > Thanks > -- Shree > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > |
|
From: <Sim...@cs...> - 2010-05-25 22:13:16
|
Excellent - I'll try it as soon as I can. Simon ________________________________________ From: Kumar, Shree [shr...@hp...] Sent: Tuesday, May 25, 2010 9:48 PM To: viz...@li... Subject: [vizstack-users] viz-desktop should now work with bezels Hi Simon, I had raised an issue with nvidia about the desktop bezel problem. They have come back and clarified that it is not a bug, but the expected behaviour. However, good things have come out of the interaction. They have suggested an alternate way of configuring, and I have fixed my code appropriately. If you update the shree branch, and try the viz-desktop script with -B, you should get a desktop cofigured correctly. Can you try it and confirm that it works ? Thanks -- Shree ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: Kumar, S. <shr...@hp...> - 2010-05-25 11:50:42
|
Hi Simon, I had raised an issue with nvidia about the desktop bezel problem. They have come back and clarified that it is not a bug, but the expected behaviour. However, good things have come out of the interaction. They have suggested an alternate way of configuring, and I have fixed my code appropriately. If you update the shree branch, and try the viz-desktop script with -B, you should get a desktop cofigured correctly. Can you try it and confirm that it works ? Thanks -- Shree |
|
From: Kumar, S. <shr...@hp...> - 2010-05-19 19:44:41
|
VizStack 1.1-2 is out ! Please download and try it out from the usual place http://sourceforge.net/projects/vizstack/files/. This supports multiple remote desktop sessions per GPU and many more enhancements and bug fixes. I'm pasting some text from the announcement at http://vizstack.sourceforge.net/?p=88 below ---- Support for multiple remote desktop sessions per GPU is surely the most awaited feature of this release. It is possible to control the number of users that share a GPU on a per-GPU basis. You will also find several enhancements and fixes that make like better (I'll mention only the most important ones here) * Binary packages for RHEL5, SLES11, Ubuntu 9.10 and SLES10. * VizStack now uses libxml2 for parsing - so just download and install on any Linux distro! * VizStack can compensate for bezels in Tiled Displays using "invisible pixels". Note that current nvidia drivers have issues w.r.t handling these, so this may or may not work for you. * The Remote Access Tools can allocate whole nodes for users. Since GPUs can now be shared, you can allocate a complete GPU all for yourself too. * Support for a "fast" network; this can be used by parallel applications. * The configure script can now generate templates for GPUs and display devices not known to it. This should make it easy to get those first things up and running. This also means that GPUs meant for compute purposes, e.g. Tesla series cards, should work with VizStack (hasn't been tested, though). GeForce cards should work too. * Templates for Displays(including EDID files), GPUs, Keyboards and Mice are loaded from the master node. There is no need to propagate these files to the slave nodes in a cluster. Also, the node configuration file is picked up only from the master node. These minimizes impacts of cluster management techniques like Golden Imaging. * The documentation just got better, and is now split into a User Guide, and an Admin Guide; a developer guide also makes an appearance, though admittedly it is still basic ! * Small fixes and face-lifts have been given to most user scripts (viz-*) * Some more samples scripts show usage of VizStack's Python API o Script that can run applications written using the Equalizer framework o Script that shows how to run benchmarks in parallel. Run SPECViewPerf 9 in parallel on all GPUs of a cluster. Benchmark a whole cluster in 30 mins - sweet ! Another example shows how to run the CUDA bandwidth test on all GPUs. If you are upgrading from an earlier release (e.g., 1.0-2), note that any XML template files you may have created are now invalid. Please keep backups of this. Sorry for this break from backward compatibility, but it was necessary ! I need to thank the following individuals for their contributions * Simon Fowler : found a few issues in VizStack on Ubuntu, requested support for Bezels, and generally for being the first (and very active) subscriber on the mailing list :-) Simon also contributed templates for the Dell 3008WFP monitor, and the Quadro NVS 420 card. * Paul Melis : suggested source documentation changes. --- Cheers! -- Shree VizStack : http://vizstack.sourceforge.net/ ParaComp : http://paracomp.sourceforge.net/ HP Internal Blog : http://blogs.hp.com/shree Personal Blog : http://www.shreekumar.in/ |
|
From: Kumar, S. <shr...@hp...> - 2010-05-18 11:36:24
|
Hi Simon, Can you update svn and have a look at the "share/samples/tiled_display/local-combined-desktop" script ? There are comments on the top of the file. Basically, it expects two tiled displays, <name>-LEFT and <name>-RIGHT. <name>-LEFT should have the keyboard and the mouse. It combines the two into a single tiled display and starts a desktop on them. If you ask for bezels with "-B", then beezels are appropriately configured. Run the script as "local-combined-desktop -t <name>". I have quickly tested the script on two GPUs, so YMMV :-) Let me know whatever happens. PS: I have merged the shree branch into trunk. Will be cutting out a release shortly. -- Shree -----Original Message----- From: Kumar, Shree Sent: Tuesday, May 18, 2010 12:35 PM To: viz...@li... Subject: Re: [vizstack-users] Configuring Physical Desktops( was RE: Yet another odd problem . . .) >> Ah ! 1 point to Manju and Glenn who wanted this functionality >> earlier. If only I had included this generic functionality. >> For now, I will consider this as a feature request. >> >Yeah, it's definitely a useful feature to support, since for tiled > displays you want odd numbers of rows and columns, in order to put > the center of the display in the middle of one monitor, rather than > hidden under a bezel. Until GPUs regularly support three or more outputs > that's problematic under the current model. Ok. >> That brings us to what we can do in the current >> circumstances. Not using all the GPUs in not an option in >> your case, since it triggers the console keyboard problem. >> >> Here is one solution : >> - Create two tiled displays : >> - first one with two GPUs with dual monitor blocks, and >> a keyboard and mouse (lets call this "node-LEFT") >> - one with two GPUs and single monitor blocks (lets >> call this "node-RIGHT") >> - Create another script based on "viz-desktop". This script will >> - Allocate two tiled displays (as opposed to one right now) >> - Reconfigure the X servers on the tiled display such >> that the single X server controls all the GPUs >> - during this, we have to ensure that the left bezel >> is included for the displays on "node-RIGHT" >> - Start the desktop >> >> I am hoping that this will look like a natural solution to >> your end users. You will retain the ability to switch >> resolutions as a command line option. >> >It's a bit of a kludge, but I can see how it should work. We still >have the console issue with any subdivision of the display, but > I don't think it's too much of an issue to require people to ssh > in to do anything outside the norm . . . at least for the moment. Right - the display setup is a kludge. >> Let me know if you want to go with this. Do I remember right >> that you are comfortable with a small amount of python programming ? >> > heh - more than comfortable, I'm pretty familiar with python. I'll take > a look at viz-desktop and see what I can do, but I may not have time > between other things to make much progress. I'll let you know how it goes. :-) I figured out that implementing this solution is more work that it looked like in the first case. I am also giving this a shot - mainly to check the vizstack API. Hoping to add this as an example so that it can be useful to others too ! Regards -- Shree ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: Kumar, S. <shr...@hp...> - 2010-05-18 07:07:53
|
>> Ah ! 1 point to Manju and Glenn who wanted this functionality >> earlier. If only I had included this generic functionality. >> For now, I will consider this as a feature request. >> >Yeah, it's definitely a useful feature to support, since for tiled > displays you want odd numbers of rows and columns, in order to put > the center of the display in the middle of one monitor, rather than > hidden under a bezel. Until GPUs regularly support three or more outputs > that's problematic under the current model. Ok. >> That brings us to what we can do in the current >> circumstances. Not using all the GPUs in not an option in >> your case, since it triggers the console keyboard problem. >> >> Here is one solution : >> - Create two tiled displays : >> - first one with two GPUs with dual monitor blocks, and >> a keyboard and mouse (lets call this "node-LEFT") >> - one with two GPUs and single monitor blocks (lets >> call this "node-RIGHT") >> - Create another script based on "viz-desktop". This script will >> - Allocate two tiled displays (as opposed to one right now) >> - Reconfigure the X servers on the tiled display such >> that the single X server controls all the GPUs >> - during this, we have to ensure that the left bezel >> is included for the displays on "node-RIGHT" >> - Start the desktop >> >> I am hoping that this will look like a natural solution to >> your end users. You will retain the ability to switch >> resolutions as a command line option. >> >It's a bit of a kludge, but I can see how it should work. We still >have the console issue with any subdivision of the display, but > I don't think it's too much of an issue to require people to ssh > in to do anything outside the norm . . . at least for the moment. Right - the display setup is a kludge. >> Let me know if you want to go with this. Do I remember right >> that you are comfortable with a small amount of python programming ? >> > heh - more than comfortable, I'm pretty familiar with python. I'll take > a look at viz-desktop and see what I can do, but I may not have time > between other things to make much progress. I'll let you know how it goes. :-) I figured out that implementing this solution is more work that it looked like in the first case. I am also giving this a shot - mainly to check the vizstack API. Hoping to add this as an example so that it can be useful to others too ! Regards -- Shree |
|
From: <Sim...@cs...> - 2010-05-18 06:05:21
|
> -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Tuesday, 18 May 2010 3:47 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > Ah ! 1 point to Manju and Glenn who wanted this functionality > earlier. If only I had included this generic functionality. > For now, I will consider this as a feature request. > Yeah, it's definitely a useful feature to support, since for tiled displays you want odd numbers of rows and columns, in order to put the center of the display in the middle of one monitor, rather than hidden under a bezel. Until GPUs regularly support three or more outputs that's problematic under the current model. > That brings us to what we can do in the current > circumstances. Not using all the GPUs in not an option in > your case, since it triggers the console keyboard problem. > > Here is one solution : > - Create two tiled displays : > - first one with two GPUs with dual monitor blocks, and > a keyboard and mouse (lets call this "node-LEFT") > - one with two GPUs and single monitor blocks (lets > call this "node-RIGHT") > - Create another script based on "viz-desktop". This script will > - Allocate two tiled displays (as opposed to one right now) > - Reconfigure the X servers on the tiled display such > that the single X server controls all the GPUs > - during this, we have to ensure that the left bezel > is included for the displays on "node-RIGHT" > - Start the desktop > > I am hoping that this will look like a natural solution to > your end users. You will retain the ability to switch > resolutions as a command line option. > It's a bit of a kludge, but I can see how it should work. We still have the console issue with any subdivision of the display, but I don't think it's too much of an issue to require people to ssh in to do anything outside the norm . . . at least for the moment. > Let me know if you want to go with this. Do I remember right > that you are comfortable with a small amount of python programming ? > heh - more than comfortable, I'm pretty familiar with python. I'll take a look at viz-desktop and see what I can do, but I may not have time between other things to make much progress. I'll let you know how it goes. Simon |
|
From: Kumar, S. <shr...@hp...> - 2010-05-18 05:51:20
|
Ah ! 1 point to Manju and Glenn who wanted this functionality earlier. If only I had included this generic functionality. For now, I will consider this as a feature request.
That brings us to what we can do in the current circumstances. Not using all the GPUs in not an option in your case, since it triggers the console keyboard problem.
Here is one solution :
- Create two tiled displays :
- first one with two GPUs with dual monitor blocks, and a keyboard and mouse (lets call this "node-LEFT")
- one with two GPUs and single monitor blocks (lets call this "node-RIGHT")
- Create another script based on "viz-desktop". This script will
- Allocate two tiled displays (as opposed to one right now)
- Reconfigure the X servers on the tiled display such that the single X server controls all the GPUs
- during this, we have to ensure that the left bezel is included for the displays on "node-RIGHT"
- Start the desktop
I am hoping that this will look like a natural solution to your end users. You will retain the ability to switch resolutions as a command line option.
Let me know if you want to go with this. Do I remember right that you are comfortable with a small amount of python programming ?
Cheers
-- Shree
-----Original Message-----
From: Sim...@cs... [mailto:Sim...@cs...]
Sent: Tuesday, May 18, 2010 7:34 AM
To: viz...@li...
Subject: Re: [vizstack-users] Configuring Physical Desktops( was RE: Yet another odd problem . . .)
Would there be a config using all the GPUs that I could set up? We've only got six monitors, but four dual-port GPUs - unless we could use a heterogenous mix of blocks (two GPUs with dual-monitor blocks, and two with single-monitor blocks) I don't see how we could use all of them.
Simon
> -----Original Message-----
> From: Kumar, Shree [mailto:shr...@hp...]
> Sent: Monday, 17 May 2010 6:33 PM
> To: viz...@li...
> Subject: Re: [vizstack-users] Configuring Physical Desktops(
> was RE: Yet another odd problem . . .)
>
>
> Ok. Hopefully I understand better now. Bear with me for a
> little while more while I try to figure out what can be done
> - and isn't too intrusive.
>
> Since there is only a single user on the system, you could
> configure a tiled display that uses up all the GPU on the
> node. With this, the user can login into the console and use
> "viz-desktop" to start the desktop session. Since the X
> server uses all GPUs, VizStack should now start the X server
> and switch the VT. This should work for you - does it not ?
>
> I tested this myself an hour ago on a server equipped with 2
> GPUs - Ubuntu 9.10 x86_64. Note that you will need to include
> all GPUs in the tiled display for this to work. This approach
> also doesn't need disabling of the gettys.
>
> -- Shree
>
>
> -----Original Message-----
> From: Sim...@cs... [mailto:Sim...@cs...]
> Sent: Monday, May 17, 2010 12:11 PM
> To: viz...@li...
> Subject: Re: [vizstack-users] Configuring Physical Desktops(
> was RE: Yet another odd problem . . .)
>
> VizStack has actually been far easier to get working than a
> straight X configuration on this system, and it allows us to
> subdivide the display very easily - much more easily than
> running from gdm. It also gives us a simple path to scale up
> to larger systems that won't run from a single display node
> (which is something we expect to have to build in the future).
>
> Also, switching from hidden pixels behind bezels to no hidden
> pixels would require switching around X configs with gdm,
> whereas with vizstack it's a simple command line option.
>
> So VizStack basically just makes a range of things we want to
> do quite simple - we could probably do them manually, or
> write our own automation scripts to handle it, but it would
> be a lot harder to manage . . . That's why ideally we'd be
> able to run a viz-desktop session from a console login - it's
> the simplest way to get at the flexibility on offer through VizStack.
>
> Simon
>
> > -----Original Message-----
> > From: Kumar, Shree [mailto:shr...@hp...]
> > Sent: Monday, 17 May 2010 4:28 PM
> > To: viz...@li...
> > Subject: Re: [vizstack-users] Configuring Physical
> Desktops( was RE:
> > Yet another odd problem . . .)
> >
> >
> > If you just run gdm (with an appropriate X config file),
> would that be
> > sufficient for your purposes ?
> >
> > You could configure gdm using PAM to use the same kerberos
> > authentication.
> >
> > -- Shree
> >
> > -----Original Message-----
> > From: Sim...@cs... [mailto:Sim...@cs...]
> > Sent: Monday, May 17, 2010 11:45 AM
> > To: viz...@li...
> > Subject: Re: [vizstack-users] Configuring Physical
> Desktops( was RE:
> > Yet another odd problem . . .)
> >
> > We're looking to have someone log in to the display node, get a
> > vizstack powered desktop session, then run VNC clients to access
> > remote rendering nodes and run visualisation applications.
> It'll be a
> > single login at any given time, but potentially many
> different people
> > using it over time.
> >
> > The main reason we're hoping to be able to have people log
> in, rather
> > than use a shared account, is security and auditing - some of these
> > machines will be installed in relatively open places, so we
> want to be
> > able to restrict access somewhat.
> >
> > We'd be using kerberos authentication against our corporate
> AD domain.
> >
> > If the only reasonable solution at the moment is to run
> from an init
> > script we'll cope.
> >
> > Simon
> >
> > > -----Original Message-----
> > > From: Kumar, Shree [mailto:shr...@hp...]
> > > Sent: Monday, 17 May 2010 4:07 PM
> > > To: viz...@li...
> > > Subject: Re: [vizstack-users] Configuring Physical
> > Desktops( was RE:
> > > Yet another odd problem . . .)
> > >
> > >
> > > Can you describe what kind of a setup you are aiming for ?
> > >
> > > To me, looks like it is a static kind of a setup. We may
> be able to
> > > come to a better solution for static setups.
> > >
> > > -- Shree
> > >
> > > -----Original Message-----
> > > From: Sim...@cs... [mailto:Sim...@cs...]
> > > Sent: Monday, May 17, 2010 11:24 AM
> > > To: viz...@li...
> > > Subject: Re: [vizstack-users] Configuring Physical
> > Desktops( was RE:
> > > Yet another odd problem . . .)
> > >
> > > Possibly kill gdm as part of the session startup, then bring up
> > > viz-desktop, and when you log out restart gdm?
> > >
> > > Requiring another machine that you can use to ssh in is a bit
> > > problematic - these are supposed to be standalone
> systems. I guess
> > > worst case we can just use an init script and deal with the
> > hard-coded
> > > user . . .
> > >
> > > Simon
> > >
> > > > -----Original Message-----
> > > > From: Kumar, Shree [mailto:shr...@hp...]
> > > > Sent: Monday, 17 May 2010 3:46 PM
> > > > To: viz...@li...
> > > > Subject: Re: [vizstack-users] Configuring Physical
> > > Desktops( was RE:
> > > > Yet another odd problem . . .)
> > > >
> > > >
> > > > Running it from an init script should be possible - but
> > > that hardcodes
> > > > the user to whom the session is allocated.
> > > >
> > > > It should be possible to do this via a GDM session - but on
> > > which GPU
> > > > will the GDM session run - that will waste a GPU right ?
> > > >
> > > > If they can SSH into the box to start a session, then
> > > nothing like it.
> > > >
> > > > -- Shree
> > > >
> > > > -----Original Message-----
> > > > From: Sim...@cs... [mailto:Sim...@cs...]
> > > > Sent: Monday, May 17, 2010 11:01 AM
> > > > To: viz...@li...
> > > > Subject: Re: [vizstack-users] Configuring Physical
> > > Desktops( was RE:
> > > > Yet another odd problem . . .)
> > > >
> > > > Doing away with all the gettys will be problematic - people
> > > will need
> > > > to get onto the console of this system in order to run
> > > viz-desktop . .
> > > > .
> > > >
> > > > Would it be possible to run it from an init script? Or
> > > possibly from a
> > > > gdm session?
> > > >
> > > > Simon
> > > >
> > > > > -----Original Message-----
> > > > > From: Kumar, Shree [mailto:shr...@hp...]
> > > > > Sent: Monday, 17 May 2010 3:21 PM
> > > > > To: viz...@li...
> > > > > Subject: [vizstack-users] Configuring Physical Desktops( was
> > > > > RE: Yet another odd problem . . .)
> > > > >
> > > > > Hi Simon,
> > > > >
> > > > > This is turning out to be more complicated that I had
> > > thought. The
> > > > > interaction with the console seems dependent even on the
> > > > linux distro
> > > > > in use :-(
> > > > >
> > > > > In particular, I have observed that the default console
> > > > gets all the
> > > > > keyboard data - whether it comes from PS/2 or from USB
> > keyboards.
> > > > >
> > > > > On Ubuntu (that's your OS, correct?) you can try the
> following :
> > > > >
> > > > > - Disable all the gettys. This does away with the console
> > > > entirely -
> > > > > so nobody will be around to snoop on the keyboard data.
> > > > > - Try your existing desktop (which doesn't use all GPUs).
> > > > > This should hopefully work.
> > > > >
> > > > > Regards
> > > > > -- Shree
> > > > >
> > > > > -----Original Message-----
> > > > > From: Sim...@cs... [mailto:Sim...@cs...]
> > > > > Sent: Saturday, May 15, 2010 1:10 PM
> > > > > To: viz...@li...
> > > > > Subject: Re: [vizstack-users] Yet another odd problem . . .
> > > > >
> > > > > Good to know there's a simple fix - I'll check out the doco
> > > > and see if
> > > > > I can figure it out from there, otherwise I may come back for
> > > > > assistance.
> > > > >
> > > > > Simon
> > > > > ________________________________________
> > > > > From: Kumar, Shree [shr...@hp...]
> > > > > Sent: Friday, May 14, 2010 7:52 PM
> > > > > To: viz...@li...
> > > > > Subject: Re: [vizstack-users] Yet another odd problem . . .
> > > > >
> > > > > Hi Simon,
> > > > >
> > > > > If you run a desktop which uses up _all_ the GPUs on the
> > > > system, then
> > > > > you will not face such issues.
> > > > >
> > > > > What you are noticing is a contention for input devices
> > > > between the X
> > > > > server and your console. When you run a desktop which does
> > > > not use all
> > > > > GPUs on a system, you need a dedicated keyboard and a
> > > mouse for the
> > > > > session to avoid such conflicts.
> > > > >
> > > > > Let me explain:
> > > > >
> > > > > - your console is running all the time on a VT(virtual
> > > > terminal). The
> > > > > console has access to the keyboard and mouse.
> > > > >
> > > > > - Using viz-desktop, when you start desktop on all the
> > > GPUs, the VT
> > > > > gets switched. This is similar to what happens when you run
> > > > GDM, or if
> > > > > press CTRL-ALT-F7. The VT running the X server now has
> > > > control of the
> > > > > keyboard and the mouse.
> > > > >
> > > > > - When you start a desktop on one or more (but not all)
> > > > GPUs, the VT
> > > > > does not get switched. Not switching the VT is a
> > > requirement to run
> > > > > multiple X servers, which in turn is needed to share the
> > > node with
> > > > > multiple X servers. Since the VT does not switch, your
> > > > console still
> > > > > has access to the keyboard and the mouse. That accounts
> > > for all the
> > > > > weirdness you see. In your case, the X server pops up
> > on the same
> > > > > screen where your console is, causing even more confusion.
> > > > >
> > > > > To get one or more physical desktops working the way you
> > > want, you
> > > > > will need a separate physical keyboard/mouse per user. I
> > > > have had best
> > > > > results with USB Keyboards and USB Mice. These need to be
> > > > added into
> > > > > node_config.xml. Let me know if I need to describe the
> > > nitty gritty
> > > > > involved in this !
> > > > >
> > > > > Regards
> > > > > -- Shree
> > > > >
> > > > > -----Original Message-----
> > > > > From: Sim...@cs... [mailto:Sim...@cs...]
> > > > > Sent: Friday, May 14, 2010 12:46 PM
> > > > > To: viz...@li...
> > > > > Subject: [vizstack-users] Yet another odd problem . . .
> > > > >
> > > > > A very odd problem . . .
> > > > >
> > > > > I've been running viz-desktop from an ssh session all
> the time,
> > > > > because when I run it from a console session, the first
> > > > time I try to
> > > > > enter anything via the keyboard the display locks up -
> > > the mouse is
> > > > > still rendered normally, but nothing responds to it.
> > > > >
> > > > > I just found, while doing a bit of testing, that when I'm
> > > > logged in at
> > > > > the console and I run a viz-desktop session via ssh the
> > > things that
> > > > > were typed into the session show up on the console as if
> > > they were
> > > > > typed in. So, I fire up viz-desktop, bring up a terminal,
> > > > start up a
> > > > > vnc session, type in my password, and so on, and all those
> > > > lines show
> > > > > up on the console. I just did a test where the only thing I
> > > > brought up
> > > > > was firefox - I typed in a URL, hit enter, and the URL was
> > > > in the bash
> > > > > history of the console. Just for fun I brought up a
> > terminal and
> > > > > changed the prompt - when I closed the session the
> > prompt in the
> > > > > console was also changed.
> > > > >
> > > > > Presumably this is some kind of issue with stdin/stdout
> > not being
> > > > > redirected correctly . . .
> > > > >
> > > > > Simon Fowler
> > > > > Technical Specialist eResearch Visualisation team CSIRO IM&T
> > > > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871
> > > > > --------------------------------------------------------------
> > > > > ----------------
> > > > >
> > > > > _______________________________________________
> > > > > vizstack-users mailing list
> > > > > viz...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > > > >
> > > > > --------------------------------------------------------------
> > > > > ----------------
> > > > >
> > > > > _______________________________________________
> > > > > vizstack-users mailing list
> > > > > viz...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > > > >
> > > > > --------------------------------------------------------------
> > > > > ----------------
> > > > >
> > > > > _______________________________________________
> > > > > vizstack-users mailing list
> > > > > viz...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > > > >
> > > > > --------------------------------------------------------------
> > > > > ----------------
> > > > >
> > > > > _______________________________________________
> > > > > vizstack-users mailing list
> > > > > viz...@li...
> > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > > > >
> > > > --------------------------------------------------------------
> > > > ----------------
> > > >
> > > > _______________________________________________
> > > > vizstack-users mailing list
> > > > viz...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > > >
> > > > --------------------------------------------------------------
> > > > ----------------
> > > >
> > > > _______________________________________________
> > > > vizstack-users mailing list
> > > > viz...@li...
> > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > > >
> > > --------------------------------------------------------------
> > > ----------------
> > >
> > > _______________________________________________
> > > vizstack-users mailing list
> > > viz...@li...
> > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > >
> > > --------------------------------------------------------------
> > > ----------------
> > >
> > > _______________________________________________
> > > vizstack-users mailing list
> > > viz...@li...
> > > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> > >
> > --------------------------------------------------------------
> > ----------------
> >
> > _______________________________________________
> > vizstack-users mailing list
> > viz...@li...
> > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> >
> > --------------------------------------------------------------
> > ----------------
> >
> > _______________________________________________
> > vizstack-users mailing list
> > viz...@li...
> > https://lists.sourceforge.net/lists/listinfo/vizstack-users
> >
>
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
> --------------------------------------------------------------
> ----------------
>
> _______________________________________________
> vizstack-users mailing list
> viz...@li...
> https://lists.sourceforge.net/lists/listinfo/vizstack-users
>
------------------------------------------------------------------------------
_______________________________________________
vizstack-users mailing list
viz...@li...
https://lists.sourceforge.net/lists/listinfo/vizstack-users
|
|
From: <Sim...@cs...> - 2010-05-18 02:04:37
|
Would there be a config using all the GPUs that I could set up? We've only got six monitors, but four dual-port GPUs - unless we could use a heterogenous mix of blocks (two GPUs with dual-monitor blocks, and two with single-monitor blocks) I don't see how we could use all of them. Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 6:33 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > Ok. Hopefully I understand better now. Bear with me for a > little while more while I try to figure out what can be done > - and isn't too intrusive. > > Since there is only a single user on the system, you could > configure a tiled display that uses up all the GPU on the > node. With this, the user can login into the console and use > "viz-desktop" to start the desktop session. Since the X > server uses all GPUs, VizStack should now start the X server > and switch the VT. This should work for you - does it not ? > > I tested this myself an hour ago on a server equipped with 2 > GPUs - Ubuntu 9.10 x86_64. Note that you will need to include > all GPUs in the tiled display for this to work. This approach > also doesn't need disabling of the gettys. > > -- Shree > > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 12:11 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > VizStack has actually been far easier to get working than a > straight X configuration on this system, and it allows us to > subdivide the display very easily - much more easily than > running from gdm. It also gives us a simple path to scale up > to larger systems that won't run from a single display node > (which is something we expect to have to build in the future). > > Also, switching from hidden pixels behind bezels to no hidden > pixels would require switching around X configs with gdm, > whereas with vizstack it's a simple command line option. > > So VizStack basically just makes a range of things we want to > do quite simple - we could probably do them manually, or > write our own automation scripts to handle it, but it would > be a lot harder to manage . . . That's why ideally we'd be > able to run a viz-desktop session from a console login - it's > the simplest way to get at the flexibility on offer through VizStack. > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 4:28 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > > > If you just run gdm (with an appropriate X config file), > would that be > > sufficient for your purposes ? > > > > You could configure gdm using PAM to use the same kerberos > > authentication. > > > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Monday, May 17, 2010 11:45 AM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > We're looking to have someone log in to the display node, get a > > vizstack powered desktop session, then run VNC clients to access > > remote rendering nodes and run visualisation applications. > It'll be a > > single login at any given time, but potentially many > different people > > using it over time. > > > > The main reason we're hoping to be able to have people log > in, rather > > than use a shared account, is security and auditing - some of these > > machines will be installed in relatively open places, so we > want to be > > able to restrict access somewhat. > > > > We'd be using kerberos authentication against our corporate > AD domain. > > > > If the only reasonable solution at the moment is to run > from an init > > script we'll cope. > > > > Simon > > > > > -----Original Message----- > > > From: Kumar, Shree [mailto:shr...@hp...] > > > Sent: Monday, 17 May 2010 4:07 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Configuring Physical > > Desktops( was RE: > > > Yet another odd problem . . .) > > > > > > > > > Can you describe what kind of a setup you are aiming for ? > > > > > > To me, looks like it is a static kind of a setup. We may > be able to > > > come to a better solution for static setups. > > > > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Monday, May 17, 2010 11:24 AM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Configuring Physical > > Desktops( was RE: > > > Yet another odd problem . . .) > > > > > > Possibly kill gdm as part of the session startup, then bring up > > > viz-desktop, and when you log out restart gdm? > > > > > > Requiring another machine that you can use to ssh in is a bit > > > problematic - these are supposed to be standalone > systems. I guess > > > worst case we can just use an init script and deal with the > > hard-coded > > > user . . . > > > > > > Simon > > > > > > > -----Original Message----- > > > > From: Kumar, Shree [mailto:shr...@hp...] > > > > Sent: Monday, 17 May 2010 3:46 PM > > > > To: viz...@li... > > > > Subject: Re: [vizstack-users] Configuring Physical > > > Desktops( was RE: > > > > Yet another odd problem . . .) > > > > > > > > > > > > Running it from an init script should be possible - but > > > that hardcodes > > > > the user to whom the session is allocated. > > > > > > > > It should be possible to do this via a GDM session - but on > > > which GPU > > > > will the GDM session run - that will waste a GPU right ? > > > > > > > > If they can SSH into the box to start a session, then > > > nothing like it. > > > > > > > > -- Shree > > > > > > > > -----Original Message----- > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > Sent: Monday, May 17, 2010 11:01 AM > > > > To: viz...@li... > > > > Subject: Re: [vizstack-users] Configuring Physical > > > Desktops( was RE: > > > > Yet another odd problem . . .) > > > > > > > > Doing away with all the gettys will be problematic - people > > > will need > > > > to get onto the console of this system in order to run > > > viz-desktop . . > > > > . > > > > > > > > Would it be possible to run it from an init script? Or > > > possibly from a > > > > gdm session? > > > > > > > > Simon > > > > > > > > > -----Original Message----- > > > > > From: Kumar, Shree [mailto:shr...@hp...] > > > > > Sent: Monday, 17 May 2010 3:21 PM > > > > > To: viz...@li... > > > > > Subject: [vizstack-users] Configuring Physical Desktops( was > > > > > RE: Yet another odd problem . . .) > > > > > > > > > > Hi Simon, > > > > > > > > > > This is turning out to be more complicated that I had > > > thought. The > > > > > interaction with the console seems dependent even on the > > > > linux distro > > > > > in use :-( > > > > > > > > > > In particular, I have observed that the default console > > > > gets all the > > > > > keyboard data - whether it comes from PS/2 or from USB > > keyboards. > > > > > > > > > > On Ubuntu (that's your OS, correct?) you can try the > following : > > > > > > > > > > - Disable all the gettys. This does away with the console > > > > entirely - > > > > > so nobody will be around to snoop on the keyboard data. > > > > > - Try your existing desktop (which doesn't use all GPUs). > > > > > This should hopefully work. > > > > > > > > > > Regards > > > > > -- Shree > > > > > > > > > > -----Original Message----- > > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > > Sent: Saturday, May 15, 2010 1:10 PM > > > > > To: viz...@li... > > > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > > > > > Good to know there's a simple fix - I'll check out the doco > > > > and see if > > > > > I can figure it out from there, otherwise I may come back for > > > > > assistance. > > > > > > > > > > Simon > > > > > ________________________________________ > > > > > From: Kumar, Shree [shr...@hp...] > > > > > Sent: Friday, May 14, 2010 7:52 PM > > > > > To: viz...@li... > > > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > > > > > Hi Simon, > > > > > > > > > > If you run a desktop which uses up _all_ the GPUs on the > > > > system, then > > > > > you will not face such issues. > > > > > > > > > > What you are noticing is a contention for input devices > > > > between the X > > > > > server and your console. When you run a desktop which does > > > > not use all > > > > > GPUs on a system, you need a dedicated keyboard and a > > > mouse for the > > > > > session to avoid such conflicts. > > > > > > > > > > Let me explain: > > > > > > > > > > - your console is running all the time on a VT(virtual > > > > terminal). The > > > > > console has access to the keyboard and mouse. > > > > > > > > > > - Using viz-desktop, when you start desktop on all the > > > GPUs, the VT > > > > > gets switched. This is similar to what happens when you run > > > > GDM, or if > > > > > press CTRL-ALT-F7. The VT running the X server now has > > > > control of the > > > > > keyboard and the mouse. > > > > > > > > > > - When you start a desktop on one or more (but not all) > > > > GPUs, the VT > > > > > does not get switched. Not switching the VT is a > > > requirement to run > > > > > multiple X servers, which in turn is needed to share the > > > node with > > > > > multiple X servers. Since the VT does not switch, your > > > > console still > > > > > has access to the keyboard and the mouse. That accounts > > > for all the > > > > > weirdness you see. In your case, the X server pops up > > on the same > > > > > screen where your console is, causing even more confusion. > > > > > > > > > > To get one or more physical desktops working the way you > > > want, you > > > > > will need a separate physical keyboard/mouse per user. I > > > > have had best > > > > > results with USB Keyboards and USB Mice. These need to be > > > > added into > > > > > node_config.xml. Let me know if I need to describe the > > > nitty gritty > > > > > involved in this ! > > > > > > > > > > Regards > > > > > -- Shree > > > > > > > > > > -----Original Message----- > > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > > Sent: Friday, May 14, 2010 12:46 PM > > > > > To: viz...@li... > > > > > Subject: [vizstack-users] Yet another odd problem . . . > > > > > > > > > > A very odd problem . . . > > > > > > > > > > I've been running viz-desktop from an ssh session all > the time, > > > > > because when I run it from a console session, the first > > > > time I try to > > > > > enter anything via the keyboard the display locks up - > > > the mouse is > > > > > still rendered normally, but nothing responds to it. > > > > > > > > > > I just found, while doing a bit of testing, that when I'm > > > > logged in at > > > > > the console and I run a viz-desktop session via ssh the > > > things that > > > > > were typed into the session show up on the console as if > > > they were > > > > > typed in. So, I fire up viz-desktop, bring up a terminal, > > > > start up a > > > > > vnc session, type in my password, and so on, and all those > > > > lines show > > > > > up on the console. I just did a test where the only thing I > > > > brought up > > > > > was firefox - I typed in a URL, hit enter, and the URL was > > > > in the bash > > > > > history of the console. Just for fun I brought up a > > terminal and > > > > > changed the prompt - when I closed the session the > > prompt in the > > > > > console was also changed. > > > > > > > > > > Presumably this is some kind of issue with stdin/stdout > > not being > > > > > redirected correctly . . . > > > > > > > > > > Simon Fowler > > > > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > > > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > > > > -------------------------------------------------------------- > > > > > ---------------- > > > > > > > > > > _______________________________________________ > > > > > vizstack-users mailing list > > > > > viz...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > > > -------------------------------------------------------------- > > > > > ---------------- > > > > > > > > > > _______________________________________________ > > > > > vizstack-users mailing list > > > > > viz...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > > > -------------------------------------------------------------- > > > > > ---------------- > > > > > > > > > > _______________________________________________ > > > > > vizstack-users mailing list > > > > > viz...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > > > -------------------------------------------------------------- > > > > > ---------------- > > > > > > > > > > _______________________________________________ > > > > > vizstack-users mailing list > > > > > viz...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > |
|
From: Kumar, S. <shr...@hp...> - 2010-05-17 08:34:43
|
Ok. Hopefully I understand better now. Bear with me for a little while more while I try to figure out what can be done - and isn't too intrusive. Since there is only a single user on the system, you could configure a tiled display that uses up all the GPU on the node. With this, the user can login into the console and use "viz-desktop" to start the desktop session. Since the X server uses all GPUs, VizStack should now start the X server and switch the VT. This should work for you - does it not ? I tested this myself an hour ago on a server equipped with 2 GPUs - Ubuntu 9.10 x86_64. Note that you will need to include all GPUs in the tiled display for this to work. This approach also doesn't need disabling of the gettys. -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Monday, May 17, 2010 12:11 PM To: viz...@li... Subject: Re: [vizstack-users] Configuring Physical Desktops( was RE: Yet another odd problem . . .) VizStack has actually been far easier to get working than a straight X configuration on this system, and it allows us to subdivide the display very easily - much more easily than running from gdm. It also gives us a simple path to scale up to larger systems that won't run from a single display node (which is something we expect to have to build in the future). Also, switching from hidden pixels behind bezels to no hidden pixels would require switching around X configs with gdm, whereas with vizstack it's a simple command line option. So VizStack basically just makes a range of things we want to do quite simple - we could probably do them manually, or write our own automation scripts to handle it, but it would be a lot harder to manage . . . That's why ideally we'd be able to run a viz-desktop session from a console login - it's the simplest way to get at the flexibility on offer through VizStack. Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 4:28 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > If you just run gdm (with an appropriate X config file), > would that be sufficient for your purposes ? > > You could configure gdm using PAM to use the same kerberos > authentication. > > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 11:45 AM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > We're looking to have someone log in to the display node, get > a vizstack powered desktop session, then run VNC clients to > access remote rendering nodes and run visualisation > applications. It'll be a single login at any given time, but > potentially many different people using it over time. > > The main reason we're hoping to be able to have people log > in, rather than use a shared account, is security and > auditing - some of these machines will be installed in > relatively open places, so we want to be able to restrict > access somewhat. > > We'd be using kerberos authentication against our corporate AD domain. > > If the only reasonable solution at the moment is to run from > an init script we'll cope. > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 4:07 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > > > Can you describe what kind of a setup you are aiming for ? > > > > To me, looks like it is a static kind of a setup. We may be able to > > come to a better solution for static setups. > > > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Monday, May 17, 2010 11:24 AM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > Possibly kill gdm as part of the session startup, then bring up > > viz-desktop, and when you log out restart gdm? > > > > Requiring another machine that you can use to ssh in is a bit > > problematic - these are supposed to be standalone systems. I guess > > worst case we can just use an init script and deal with the > hard-coded > > user . . . > > > > Simon > > > > > -----Original Message----- > > > From: Kumar, Shree [mailto:shr...@hp...] > > > Sent: Monday, 17 May 2010 3:46 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Configuring Physical > > Desktops( was RE: > > > Yet another odd problem . . .) > > > > > > > > > Running it from an init script should be possible - but > > that hardcodes > > > the user to whom the session is allocated. > > > > > > It should be possible to do this via a GDM session - but on > > which GPU > > > will the GDM session run - that will waste a GPU right ? > > > > > > If they can SSH into the box to start a session, then > > nothing like it. > > > > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Monday, May 17, 2010 11:01 AM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Configuring Physical > > Desktops( was RE: > > > Yet another odd problem . . .) > > > > > > Doing away with all the gettys will be problematic - people > > will need > > > to get onto the console of this system in order to run > > viz-desktop . . > > > . > > > > > > Would it be possible to run it from an init script? Or > > possibly from a > > > gdm session? > > > > > > Simon > > > > > > > -----Original Message----- > > > > From: Kumar, Shree [mailto:shr...@hp...] > > > > Sent: Monday, 17 May 2010 3:21 PM > > > > To: viz...@li... > > > > Subject: [vizstack-users] Configuring Physical Desktops( was > > > > RE: Yet another odd problem . . .) > > > > > > > > Hi Simon, > > > > > > > > This is turning out to be more complicated that I had > > thought. The > > > > interaction with the console seems dependent even on the > > > linux distro > > > > in use :-( > > > > > > > > In particular, I have observed that the default console > > > gets all the > > > > keyboard data - whether it comes from PS/2 or from USB > keyboards. > > > > > > > > On Ubuntu (that's your OS, correct?) you can try the following : > > > > > > > > - Disable all the gettys. This does away with the console > > > entirely - > > > > so nobody will be around to snoop on the keyboard data. > > > > - Try your existing desktop (which doesn't use all GPUs). > > > > This should hopefully work. > > > > > > > > Regards > > > > -- Shree > > > > > > > > -----Original Message----- > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > Sent: Saturday, May 15, 2010 1:10 PM > > > > To: viz...@li... > > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > > > Good to know there's a simple fix - I'll check out the doco > > > and see if > > > > I can figure it out from there, otherwise I may come back for > > > > assistance. > > > > > > > > Simon > > > > ________________________________________ > > > > From: Kumar, Shree [shr...@hp...] > > > > Sent: Friday, May 14, 2010 7:52 PM > > > > To: viz...@li... > > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > > > Hi Simon, > > > > > > > > If you run a desktop which uses up _all_ the GPUs on the > > > system, then > > > > you will not face such issues. > > > > > > > > What you are noticing is a contention for input devices > > > between the X > > > > server and your console. When you run a desktop which does > > > not use all > > > > GPUs on a system, you need a dedicated keyboard and a > > mouse for the > > > > session to avoid such conflicts. > > > > > > > > Let me explain: > > > > > > > > - your console is running all the time on a VT(virtual > > > terminal). The > > > > console has access to the keyboard and mouse. > > > > > > > > - Using viz-desktop, when you start desktop on all the > > GPUs, the VT > > > > gets switched. This is similar to what happens when you run > > > GDM, or if > > > > press CTRL-ALT-F7. The VT running the X server now has > > > control of the > > > > keyboard and the mouse. > > > > > > > > - When you start a desktop on one or more (but not all) > > > GPUs, the VT > > > > does not get switched. Not switching the VT is a > > requirement to run > > > > multiple X servers, which in turn is needed to share the > > node with > > > > multiple X servers. Since the VT does not switch, your > > > console still > > > > has access to the keyboard and the mouse. That accounts > > for all the > > > > weirdness you see. In your case, the X server pops up > on the same > > > > screen where your console is, causing even more confusion. > > > > > > > > To get one or more physical desktops working the way you > > want, you > > > > will need a separate physical keyboard/mouse per user. I > > > have had best > > > > results with USB Keyboards and USB Mice. These need to be > > > added into > > > > node_config.xml. Let me know if I need to describe the > > nitty gritty > > > > involved in this ! > > > > > > > > Regards > > > > -- Shree > > > > > > > > -----Original Message----- > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > Sent: Friday, May 14, 2010 12:46 PM > > > > To: viz...@li... > > > > Subject: [vizstack-users] Yet another odd problem . . . > > > > > > > > A very odd problem . . . > > > > > > > > I've been running viz-desktop from an ssh session all the time, > > > > because when I run it from a console session, the first > > > time I try to > > > > enter anything via the keyboard the display locks up - > > the mouse is > > > > still rendered normally, but nothing responds to it. > > > > > > > > I just found, while doing a bit of testing, that when I'm > > > logged in at > > > > the console and I run a viz-desktop session via ssh the > > things that > > > > were typed into the session show up on the console as if > > they were > > > > typed in. So, I fire up viz-desktop, bring up a terminal, > > > start up a > > > > vnc session, type in my password, and so on, and all those > > > lines show > > > > up on the console. I just did a test where the only thing I > > > brought up > > > > was firefox - I typed in a URL, hit enter, and the URL was > > > in the bash > > > > history of the console. Just for fun I brought up a > terminal and > > > > changed the prompt - when I closed the session the > prompt in the > > > > console was also changed. > > > > > > > > Presumably this is some kind of issue with stdin/stdout > not being > > > > redirected correctly . . . > > > > > > > > Simon Fowler > > > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: <Sim...@cs...> - 2010-05-17 06:41:30
|
VizStack has actually been far easier to get working than a straight X configuration on this system, and it allows us to subdivide the display very easily - much more easily than running from gdm. It also gives us a simple path to scale up to larger systems that won't run from a single display node (which is something we expect to have to build in the future). Also, switching from hidden pixels behind bezels to no hidden pixels would require switching around X configs with gdm, whereas with vizstack it's a simple command line option. So VizStack basically just makes a range of things we want to do quite simple - we could probably do them manually, or write our own automation scripts to handle it, but it would be a lot harder to manage . . . That's why ideally we'd be able to run a viz-desktop session from a console login - it's the simplest way to get at the flexibility on offer through VizStack. Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 4:28 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > If you just run gdm (with an appropriate X config file), > would that be sufficient for your purposes ? > > You could configure gdm using PAM to use the same kerberos > authentication. > > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 11:45 AM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > We're looking to have someone log in to the display node, get > a vizstack powered desktop session, then run VNC clients to > access remote rendering nodes and run visualisation > applications. It'll be a single login at any given time, but > potentially many different people using it over time. > > The main reason we're hoping to be able to have people log > in, rather than use a shared account, is security and > auditing - some of these machines will be installed in > relatively open places, so we want to be able to restrict > access somewhat. > > We'd be using kerberos authentication against our corporate AD domain. > > If the only reasonable solution at the moment is to run from > an init script we'll cope. > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 4:07 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > > > Can you describe what kind of a setup you are aiming for ? > > > > To me, looks like it is a static kind of a setup. We may be able to > > come to a better solution for static setups. > > > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Monday, May 17, 2010 11:24 AM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > Possibly kill gdm as part of the session startup, then bring up > > viz-desktop, and when you log out restart gdm? > > > > Requiring another machine that you can use to ssh in is a bit > > problematic - these are supposed to be standalone systems. I guess > > worst case we can just use an init script and deal with the > hard-coded > > user . . . > > > > Simon > > > > > -----Original Message----- > > > From: Kumar, Shree [mailto:shr...@hp...] > > > Sent: Monday, 17 May 2010 3:46 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Configuring Physical > > Desktops( was RE: > > > Yet another odd problem . . .) > > > > > > > > > Running it from an init script should be possible - but > > that hardcodes > > > the user to whom the session is allocated. > > > > > > It should be possible to do this via a GDM session - but on > > which GPU > > > will the GDM session run - that will waste a GPU right ? > > > > > > If they can SSH into the box to start a session, then > > nothing like it. > > > > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Monday, May 17, 2010 11:01 AM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Configuring Physical > > Desktops( was RE: > > > Yet another odd problem . . .) > > > > > > Doing away with all the gettys will be problematic - people > > will need > > > to get onto the console of this system in order to run > > viz-desktop . . > > > . > > > > > > Would it be possible to run it from an init script? Or > > possibly from a > > > gdm session? > > > > > > Simon > > > > > > > -----Original Message----- > > > > From: Kumar, Shree [mailto:shr...@hp...] > > > > Sent: Monday, 17 May 2010 3:21 PM > > > > To: viz...@li... > > > > Subject: [vizstack-users] Configuring Physical Desktops( was > > > > RE: Yet another odd problem . . .) > > > > > > > > Hi Simon, > > > > > > > > This is turning out to be more complicated that I had > > thought. The > > > > interaction with the console seems dependent even on the > > > linux distro > > > > in use :-( > > > > > > > > In particular, I have observed that the default console > > > gets all the > > > > keyboard data - whether it comes from PS/2 or from USB > keyboards. > > > > > > > > On Ubuntu (that's your OS, correct?) you can try the following : > > > > > > > > - Disable all the gettys. This does away with the console > > > entirely - > > > > so nobody will be around to snoop on the keyboard data. > > > > - Try your existing desktop (which doesn't use all GPUs). > > > > This should hopefully work. > > > > > > > > Regards > > > > -- Shree > > > > > > > > -----Original Message----- > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > Sent: Saturday, May 15, 2010 1:10 PM > > > > To: viz...@li... > > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > > > Good to know there's a simple fix - I'll check out the doco > > > and see if > > > > I can figure it out from there, otherwise I may come back for > > > > assistance. > > > > > > > > Simon > > > > ________________________________________ > > > > From: Kumar, Shree [shr...@hp...] > > > > Sent: Friday, May 14, 2010 7:52 PM > > > > To: viz...@li... > > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > > > Hi Simon, > > > > > > > > If you run a desktop which uses up _all_ the GPUs on the > > > system, then > > > > you will not face such issues. > > > > > > > > What you are noticing is a contention for input devices > > > between the X > > > > server and your console. When you run a desktop which does > > > not use all > > > > GPUs on a system, you need a dedicated keyboard and a > > mouse for the > > > > session to avoid such conflicts. > > > > > > > > Let me explain: > > > > > > > > - your console is running all the time on a VT(virtual > > > terminal). The > > > > console has access to the keyboard and mouse. > > > > > > > > - Using viz-desktop, when you start desktop on all the > > GPUs, the VT > > > > gets switched. This is similar to what happens when you run > > > GDM, or if > > > > press CTRL-ALT-F7. The VT running the X server now has > > > control of the > > > > keyboard and the mouse. > > > > > > > > - When you start a desktop on one or more (but not all) > > > GPUs, the VT > > > > does not get switched. Not switching the VT is a > > requirement to run > > > > multiple X servers, which in turn is needed to share the > > node with > > > > multiple X servers. Since the VT does not switch, your > > > console still > > > > has access to the keyboard and the mouse. That accounts > > for all the > > > > weirdness you see. In your case, the X server pops up > on the same > > > > screen where your console is, causing even more confusion. > > > > > > > > To get one or more physical desktops working the way you > > want, you > > > > will need a separate physical keyboard/mouse per user. I > > > have had best > > > > results with USB Keyboards and USB Mice. These need to be > > > added into > > > > node_config.xml. Let me know if I need to describe the > > nitty gritty > > > > involved in this ! > > > > > > > > Regards > > > > -- Shree > > > > > > > > -----Original Message----- > > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > > Sent: Friday, May 14, 2010 12:46 PM > > > > To: viz...@li... > > > > Subject: [vizstack-users] Yet another odd problem . . . > > > > > > > > A very odd problem . . . > > > > > > > > I've been running viz-desktop from an ssh session all the time, > > > > because when I run it from a console session, the first > > > time I try to > > > > enter anything via the keyboard the display locks up - > > the mouse is > > > > still rendered normally, but nothing responds to it. > > > > > > > > I just found, while doing a bit of testing, that when I'm > > > logged in at > > > > the console and I run a viz-desktop session via ssh the > > things that > > > > were typed into the session show up on the console as if > > they were > > > > typed in. So, I fire up viz-desktop, bring up a terminal, > > > start up a > > > > vnc session, type in my password, and so on, and all those > > > lines show > > > > up on the console. I just did a test where the only thing I > > > brought up > > > > was firefox - I typed in a URL, hit enter, and the URL was > > > in the bash > > > > history of the console. Just for fun I brought up a > terminal and > > > > changed the prompt - when I closed the session the > prompt in the > > > > console was also changed. > > > > > > > > Presumably this is some kind of issue with stdin/stdout > not being > > > > redirected correctly . . . > > > > > > > > Simon Fowler > > > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > > -------------------------------------------------------------- > > > > ---------------- > > > > > > > > _______________________________________________ > > > > vizstack-users mailing list > > > > viz...@li... > > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > |
|
From: Kumar, S. <shr...@hp...> - 2010-05-17 06:30:13
|
If you just run gdm (with an appropriate X config file), would that be sufficient for your purposes ? You could configure gdm using PAM to use the same kerberos authentication. -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Monday, May 17, 2010 11:45 AM To: viz...@li... Subject: Re: [vizstack-users] Configuring Physical Desktops( was RE: Yet another odd problem . . .) We're looking to have someone log in to the display node, get a vizstack powered desktop session, then run VNC clients to access remote rendering nodes and run visualisation applications. It'll be a single login at any given time, but potentially many different people using it over time. The main reason we're hoping to be able to have people log in, rather than use a shared account, is security and auditing - some of these machines will be installed in relatively open places, so we want to be able to restrict access somewhat. We'd be using kerberos authentication against our corporate AD domain. If the only reasonable solution at the moment is to run from an init script we'll cope. Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 4:07 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > Can you describe what kind of a setup you are aiming for ? > > To me, looks like it is a static kind of a setup. We may be > able to come to a better solution for static setups. > > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 11:24 AM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > Possibly kill gdm as part of the session startup, then bring > up viz-desktop, and when you log out restart gdm? > > Requiring another machine that you can use to ssh in is a bit > problematic - these are supposed to be standalone systems. I > guess worst case we can just use an init script and deal with > the hard-coded user . . . > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 3:46 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > > > Running it from an init script should be possible - but > that hardcodes > > the user to whom the session is allocated. > > > > It should be possible to do this via a GDM session - but on > which GPU > > will the GDM session run - that will waste a GPU right ? > > > > If they can SSH into the box to start a session, then > nothing like it. > > > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Monday, May 17, 2010 11:01 AM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > Doing away with all the gettys will be problematic - people > will need > > to get onto the console of this system in order to run > viz-desktop . . > > . > > > > Would it be possible to run it from an init script? Or > possibly from a > > gdm session? > > > > Simon > > > > > -----Original Message----- > > > From: Kumar, Shree [mailto:shr...@hp...] > > > Sent: Monday, 17 May 2010 3:21 PM > > > To: viz...@li... > > > Subject: [vizstack-users] Configuring Physical Desktops( was > > > RE: Yet another odd problem . . .) > > > > > > Hi Simon, > > > > > > This is turning out to be more complicated that I had > thought. The > > > interaction with the console seems dependent even on the > > linux distro > > > in use :-( > > > > > > In particular, I have observed that the default console > > gets all the > > > keyboard data - whether it comes from PS/2 or from USB keyboards. > > > > > > On Ubuntu (that's your OS, correct?) you can try the following : > > > > > > - Disable all the gettys. This does away with the console > > entirely - > > > so nobody will be around to snoop on the keyboard data. > > > - Try your existing desktop (which doesn't use all GPUs). > > > This should hopefully work. > > > > > > Regards > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Saturday, May 15, 2010 1:10 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > Good to know there's a simple fix - I'll check out the doco > > and see if > > > I can figure it out from there, otherwise I may come back for > > > assistance. > > > > > > Simon > > > ________________________________________ > > > From: Kumar, Shree [shr...@hp...] > > > Sent: Friday, May 14, 2010 7:52 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > Hi Simon, > > > > > > If you run a desktop which uses up _all_ the GPUs on the > > system, then > > > you will not face such issues. > > > > > > What you are noticing is a contention for input devices > > between the X > > > server and your console. When you run a desktop which does > > not use all > > > GPUs on a system, you need a dedicated keyboard and a > mouse for the > > > session to avoid such conflicts. > > > > > > Let me explain: > > > > > > - your console is running all the time on a VT(virtual > > terminal). The > > > console has access to the keyboard and mouse. > > > > > > - Using viz-desktop, when you start desktop on all the > GPUs, the VT > > > gets switched. This is similar to what happens when you run > > GDM, or if > > > press CTRL-ALT-F7. The VT running the X server now has > > control of the > > > keyboard and the mouse. > > > > > > - When you start a desktop on one or more (but not all) > > GPUs, the VT > > > does not get switched. Not switching the VT is a > requirement to run > > > multiple X servers, which in turn is needed to share the > node with > > > multiple X servers. Since the VT does not switch, your > > console still > > > has access to the keyboard and the mouse. That accounts > for all the > > > weirdness you see. In your case, the X server pops up on the same > > > screen where your console is, causing even more confusion. > > > > > > To get one or more physical desktops working the way you > want, you > > > will need a separate physical keyboard/mouse per user. I > > have had best > > > results with USB Keyboards and USB Mice. These need to be > > added into > > > node_config.xml. Let me know if I need to describe the > nitty gritty > > > involved in this ! > > > > > > Regards > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Friday, May 14, 2010 12:46 PM > > > To: viz...@li... > > > Subject: [vizstack-users] Yet another odd problem . . . > > > > > > A very odd problem . . . > > > > > > I've been running viz-desktop from an ssh session all the time, > > > because when I run it from a console session, the first > > time I try to > > > enter anything via the keyboard the display locks up - > the mouse is > > > still rendered normally, but nothing responds to it. > > > > > > I just found, while doing a bit of testing, that when I'm > > logged in at > > > the console and I run a viz-desktop session via ssh the > things that > > > were typed into the session show up on the console as if > they were > > > typed in. So, I fire up viz-desktop, bring up a terminal, > > start up a > > > vnc session, type in my password, and so on, and all those > > lines show > > > up on the console. I just did a test where the only thing I > > brought up > > > was firefox - I typed in a URL, hit enter, and the URL was > > in the bash > > > history of the console. Just for fun I brought up a terminal and > > > changed the prompt - when I closed the session the prompt in the > > > console was also changed. > > > > > > Presumably this is some kind of issue with stdin/stdout not being > > > redirected correctly . . . > > > > > > Simon Fowler > > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: <Sim...@cs...> - 2010-05-17 06:15:34
|
We're looking to have someone log in to the display node, get a vizstack powered desktop session, then run VNC clients to access remote rendering nodes and run visualisation applications. It'll be a single login at any given time, but potentially many different people using it over time. The main reason we're hoping to be able to have people log in, rather than use a shared account, is security and auditing - some of these machines will be installed in relatively open places, so we want to be able to restrict access somewhat. We'd be using kerberos authentication against our corporate AD domain. If the only reasonable solution at the moment is to run from an init script we'll cope. Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 4:07 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > Can you describe what kind of a setup you are aiming for ? > > To me, looks like it is a static kind of a setup. We may be > able to come to a better solution for static setups. > > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 11:24 AM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > Possibly kill gdm as part of the session startup, then bring > up viz-desktop, and when you log out restart gdm? > > Requiring another machine that you can use to ssh in is a bit > problematic - these are supposed to be standalone systems. I > guess worst case we can just use an init script and deal with > the hard-coded user . . . > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 3:46 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > > > Running it from an init script should be possible - but > that hardcodes > > the user to whom the session is allocated. > > > > It should be possible to do this via a GDM session - but on > which GPU > > will the GDM session run - that will waste a GPU right ? > > > > If they can SSH into the box to start a session, then > nothing like it. > > > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Monday, May 17, 2010 11:01 AM > > To: viz...@li... > > Subject: Re: [vizstack-users] Configuring Physical > Desktops( was RE: > > Yet another odd problem . . .) > > > > Doing away with all the gettys will be problematic - people > will need > > to get onto the console of this system in order to run > viz-desktop . . > > . > > > > Would it be possible to run it from an init script? Or > possibly from a > > gdm session? > > > > Simon > > > > > -----Original Message----- > > > From: Kumar, Shree [mailto:shr...@hp...] > > > Sent: Monday, 17 May 2010 3:21 PM > > > To: viz...@li... > > > Subject: [vizstack-users] Configuring Physical Desktops( was > > > RE: Yet another odd problem . . .) > > > > > > Hi Simon, > > > > > > This is turning out to be more complicated that I had > thought. The > > > interaction with the console seems dependent even on the > > linux distro > > > in use :-( > > > > > > In particular, I have observed that the default console > > gets all the > > > keyboard data - whether it comes from PS/2 or from USB keyboards. > > > > > > On Ubuntu (that's your OS, correct?) you can try the following : > > > > > > - Disable all the gettys. This does away with the console > > entirely - > > > so nobody will be around to snoop on the keyboard data. > > > - Try your existing desktop (which doesn't use all GPUs). > > > This should hopefully work. > > > > > > Regards > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Saturday, May 15, 2010 1:10 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > Good to know there's a simple fix - I'll check out the doco > > and see if > > > I can figure it out from there, otherwise I may come back for > > > assistance. > > > > > > Simon > > > ________________________________________ > > > From: Kumar, Shree [shr...@hp...] > > > Sent: Friday, May 14, 2010 7:52 PM > > > To: viz...@li... > > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > > > Hi Simon, > > > > > > If you run a desktop which uses up _all_ the GPUs on the > > system, then > > > you will not face such issues. > > > > > > What you are noticing is a contention for input devices > > between the X > > > server and your console. When you run a desktop which does > > not use all > > > GPUs on a system, you need a dedicated keyboard and a > mouse for the > > > session to avoid such conflicts. > > > > > > Let me explain: > > > > > > - your console is running all the time on a VT(virtual > > terminal). The > > > console has access to the keyboard and mouse. > > > > > > - Using viz-desktop, when you start desktop on all the > GPUs, the VT > > > gets switched. This is similar to what happens when you run > > GDM, or if > > > press CTRL-ALT-F7. The VT running the X server now has > > control of the > > > keyboard and the mouse. > > > > > > - When you start a desktop on one or more (but not all) > > GPUs, the VT > > > does not get switched. Not switching the VT is a > requirement to run > > > multiple X servers, which in turn is needed to share the > node with > > > multiple X servers. Since the VT does not switch, your > > console still > > > has access to the keyboard and the mouse. That accounts > for all the > > > weirdness you see. In your case, the X server pops up on the same > > > screen where your console is, causing even more confusion. > > > > > > To get one or more physical desktops working the way you > want, you > > > will need a separate physical keyboard/mouse per user. I > > have had best > > > results with USB Keyboards and USB Mice. These need to be > > added into > > > node_config.xml. Let me know if I need to describe the > nitty gritty > > > involved in this ! > > > > > > Regards > > > -- Shree > > > > > > -----Original Message----- > > > From: Sim...@cs... [mailto:Sim...@cs...] > > > Sent: Friday, May 14, 2010 12:46 PM > > > To: viz...@li... > > > Subject: [vizstack-users] Yet another odd problem . . . > > > > > > A very odd problem . . . > > > > > > I've been running viz-desktop from an ssh session all the time, > > > because when I run it from a console session, the first > > time I try to > > > enter anything via the keyboard the display locks up - > the mouse is > > > still rendered normally, but nothing responds to it. > > > > > > I just found, while doing a bit of testing, that when I'm > > logged in at > > > the console and I run a viz-desktop session via ssh the > things that > > > were typed into the session show up on the console as if > they were > > > typed in. So, I fire up viz-desktop, bring up a terminal, > > start up a > > > vnc session, type in my password, and so on, and all those > > lines show > > > up on the console. I just did a test where the only thing I > > brought up > > > was firefox - I typed in a URL, hit enter, and the URL was > > in the bash > > > history of the console. Just for fun I brought up a terminal and > > > changed the prompt - when I closed the session the prompt in the > > > console was also changed. > > > > > > Presumably this is some kind of issue with stdin/stdout not being > > > redirected correctly . . . > > > > > > Simon Fowler > > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > > -------------------------------------------------------------- > > > ---------------- > > > > > > _______________________________________________ > > > vizstack-users mailing list > > > viz...@li... > > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > |
|
From: Kumar, S. <shr...@hp...> - 2010-05-17 06:08:45
|
Can you describe what kind of a setup you are aiming for ? To me, looks like it is a static kind of a setup. We may be able to come to a better solution for static setups. -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Monday, May 17, 2010 11:24 AM To: viz...@li... Subject: Re: [vizstack-users] Configuring Physical Desktops( was RE: Yet another odd problem . . .) Possibly kill gdm as part of the session startup, then bring up viz-desktop, and when you log out restart gdm? Requiring another machine that you can use to ssh in is a bit problematic - these are supposed to be standalone systems. I guess worst case we can just use an init script and deal with the hard-coded user . . . Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 3:46 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > Running it from an init script should be possible - but that > hardcodes the user to whom the session is allocated. > > It should be possible to do this via a GDM session - but on > which GPU will the GDM session run - that will waste a GPU right ? > > If they can SSH into the box to start a session, then nothing like it. > > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 11:01 AM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > Doing away with all the gettys will be problematic - people > will need to get onto the console of this system in order to > run viz-desktop . . . > > Would it be possible to run it from an init script? Or > possibly from a gdm session? > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 3:21 PM > > To: viz...@li... > > Subject: [vizstack-users] Configuring Physical Desktops( was > > RE: Yet another odd problem . . .) > > > > Hi Simon, > > > > This is turning out to be more complicated that I had thought. The > > interaction with the console seems dependent even on the > linux distro > > in use :-( > > > > In particular, I have observed that the default console > gets all the > > keyboard data - whether it comes from PS/2 or from USB keyboards. > > > > On Ubuntu (that's your OS, correct?) you can try the following : > > > > - Disable all the gettys. This does away with the console > entirely - > > so nobody will be around to snoop on the keyboard data. > > - Try your existing desktop (which doesn't use all GPUs). > > This should hopefully work. > > > > Regards > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Saturday, May 15, 2010 1:10 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > Good to know there's a simple fix - I'll check out the doco > and see if > > I can figure it out from there, otherwise I may come back for > > assistance. > > > > Simon > > ________________________________________ > > From: Kumar, Shree [shr...@hp...] > > Sent: Friday, May 14, 2010 7:52 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > Hi Simon, > > > > If you run a desktop which uses up _all_ the GPUs on the > system, then > > you will not face such issues. > > > > What you are noticing is a contention for input devices > between the X > > server and your console. When you run a desktop which does > not use all > > GPUs on a system, you need a dedicated keyboard and a mouse for the > > session to avoid such conflicts. > > > > Let me explain: > > > > - your console is running all the time on a VT(virtual > terminal). The > > console has access to the keyboard and mouse. > > > > - Using viz-desktop, when you start desktop on all the GPUs, the VT > > gets switched. This is similar to what happens when you run > GDM, or if > > press CTRL-ALT-F7. The VT running the X server now has > control of the > > keyboard and the mouse. > > > > - When you start a desktop on one or more (but not all) > GPUs, the VT > > does not get switched. Not switching the VT is a requirement to run > > multiple X servers, which in turn is needed to share the node with > > multiple X servers. Since the VT does not switch, your > console still > > has access to the keyboard and the mouse. That accounts for all the > > weirdness you see. In your case, the X server pops up on the same > > screen where your console is, causing even more confusion. > > > > To get one or more physical desktops working the way you want, you > > will need a separate physical keyboard/mouse per user. I > have had best > > results with USB Keyboards and USB Mice. These need to be > added into > > node_config.xml. Let me know if I need to describe the nitty gritty > > involved in this ! > > > > Regards > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Friday, May 14, 2010 12:46 PM > > To: viz...@li... > > Subject: [vizstack-users] Yet another odd problem . . . > > > > A very odd problem . . . > > > > I've been running viz-desktop from an ssh session all the time, > > because when I run it from a console session, the first > time I try to > > enter anything via the keyboard the display locks up - the mouse is > > still rendered normally, but nothing responds to it. > > > > I just found, while doing a bit of testing, that when I'm > logged in at > > the console and I run a viz-desktop session via ssh the things that > > were typed into the session show up on the console as if they were > > typed in. So, I fire up viz-desktop, bring up a terminal, > start up a > > vnc session, type in my password, and so on, and all those > lines show > > up on the console. I just did a test where the only thing I > brought up > > was firefox - I typed in a URL, hit enter, and the URL was > in the bash > > history of the console. Just for fun I brought up a terminal and > > changed the prompt - when I closed the session the prompt in the > > console was also changed. > > > > Presumably this is some kind of issue with stdin/stdout not being > > redirected correctly . . . > > > > Simon Fowler > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: <Sim...@cs...> - 2010-05-17 05:54:00
|
Possibly kill gdm as part of the session startup, then bring up viz-desktop, and when you log out restart gdm? Requiring another machine that you can use to ssh in is a bit problematic - these are supposed to be standalone systems. I guess worst case we can just use an init script and deal with the hard-coded user . . . Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 3:46 PM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > > Running it from an init script should be possible - but that > hardcodes the user to whom the session is allocated. > > It should be possible to do this via a GDM session - but on > which GPU will the GDM session run - that will waste a GPU right ? > > If they can SSH into the box to start a session, then nothing like it. > > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Monday, May 17, 2010 11:01 AM > To: viz...@li... > Subject: Re: [vizstack-users] Configuring Physical Desktops( > was RE: Yet another odd problem . . .) > > Doing away with all the gettys will be problematic - people > will need to get onto the console of this system in order to > run viz-desktop . . . > > Would it be possible to run it from an init script? Or > possibly from a gdm session? > > Simon > > > -----Original Message----- > > From: Kumar, Shree [mailto:shr...@hp...] > > Sent: Monday, 17 May 2010 3:21 PM > > To: viz...@li... > > Subject: [vizstack-users] Configuring Physical Desktops( was > > RE: Yet another odd problem . . .) > > > > Hi Simon, > > > > This is turning out to be more complicated that I had thought. The > > interaction with the console seems dependent even on the > linux distro > > in use :-( > > > > In particular, I have observed that the default console > gets all the > > keyboard data - whether it comes from PS/2 or from USB keyboards. > > > > On Ubuntu (that's your OS, correct?) you can try the following : > > > > - Disable all the gettys. This does away with the console > entirely - > > so nobody will be around to snoop on the keyboard data. > > - Try your existing desktop (which doesn't use all GPUs). > > This should hopefully work. > > > > Regards > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Saturday, May 15, 2010 1:10 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > Good to know there's a simple fix - I'll check out the doco > and see if > > I can figure it out from there, otherwise I may come back for > > assistance. > > > > Simon > > ________________________________________ > > From: Kumar, Shree [shr...@hp...] > > Sent: Friday, May 14, 2010 7:52 PM > > To: viz...@li... > > Subject: Re: [vizstack-users] Yet another odd problem . . . > > > > Hi Simon, > > > > If you run a desktop which uses up _all_ the GPUs on the > system, then > > you will not face such issues. > > > > What you are noticing is a contention for input devices > between the X > > server and your console. When you run a desktop which does > not use all > > GPUs on a system, you need a dedicated keyboard and a mouse for the > > session to avoid such conflicts. > > > > Let me explain: > > > > - your console is running all the time on a VT(virtual > terminal). The > > console has access to the keyboard and mouse. > > > > - Using viz-desktop, when you start desktop on all the GPUs, the VT > > gets switched. This is similar to what happens when you run > GDM, or if > > press CTRL-ALT-F7. The VT running the X server now has > control of the > > keyboard and the mouse. > > > > - When you start a desktop on one or more (but not all) > GPUs, the VT > > does not get switched. Not switching the VT is a requirement to run > > multiple X servers, which in turn is needed to share the node with > > multiple X servers. Since the VT does not switch, your > console still > > has access to the keyboard and the mouse. That accounts for all the > > weirdness you see. In your case, the X server pops up on the same > > screen where your console is, causing even more confusion. > > > > To get one or more physical desktops working the way you want, you > > will need a separate physical keyboard/mouse per user. I > have had best > > results with USB Keyboards and USB Mice. These need to be > added into > > node_config.xml. Let me know if I need to describe the nitty gritty > > involved in this ! > > > > Regards > > -- Shree > > > > -----Original Message----- > > From: Sim...@cs... [mailto:Sim...@cs...] > > Sent: Friday, May 14, 2010 12:46 PM > > To: viz...@li... > > Subject: [vizstack-users] Yet another odd problem . . . > > > > A very odd problem . . . > > > > I've been running viz-desktop from an ssh session all the time, > > because when I run it from a console session, the first > time I try to > > enter anything via the keyboard the display locks up - the mouse is > > still rendered normally, but nothing responds to it. > > > > I just found, while doing a bit of testing, that when I'm > logged in at > > the console and I run a viz-desktop session via ssh the things that > > were typed into the session show up on the console as if they were > > typed in. So, I fire up viz-desktop, bring up a terminal, > start up a > > vnc session, type in my password, and so on, and all those > lines show > > up on the console. I just did a test where the only thing I > brought up > > was firefox - I typed in a URL, hit enter, and the URL was > in the bash > > history of the console. Just for fun I brought up a terminal and > > changed the prompt - when I closed the session the prompt in the > > console was also changed. > > > > Presumably this is some kind of issue with stdin/stdout not being > > redirected correctly . . . > > > > Simon Fowler > > Technical Specialist eResearch Visualisation team CSIRO IM&T > > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > > -------------------------------------------------------------- > > ---------------- > > > > _______________________________________________ > > vizstack-users mailing list > > viz...@li... > > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > |
|
From: Kumar, S. <shr...@hp...> - 2010-05-17 05:48:31
|
Running it from an init script should be possible - but that hardcodes the user to whom the session is allocated. It should be possible to do this via a GDM session - but on which GPU will the GDM session run - that will waste a GPU right ? If they can SSH into the box to start a session, then nothing like it. -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Monday, May 17, 2010 11:01 AM To: viz...@li... Subject: Re: [vizstack-users] Configuring Physical Desktops( was RE: Yet another odd problem . . .) Doing away with all the gettys will be problematic - people will need to get onto the console of this system in order to run viz-desktop . . . Would it be possible to run it from an init script? Or possibly from a gdm session? Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 3:21 PM > To: viz...@li... > Subject: [vizstack-users] Configuring Physical Desktops( was > RE: Yet another odd problem . . .) > > Hi Simon, > > This is turning out to be more complicated that I had > thought. The interaction with the console seems dependent > even on the linux distro in use :-( > > In particular, I have observed that the default console gets > all the keyboard data - whether it comes from PS/2 or from > USB keyboards. > > On Ubuntu (that's your OS, correct?) you can try the following : > > - Disable all the gettys. This does away with the console > entirely - so nobody will be around to snoop on the keyboard data. > - Try your existing desktop (which doesn't use all GPUs). > This should hopefully work. > > Regards > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Saturday, May 15, 2010 1:10 PM > To: viz...@li... > Subject: Re: [vizstack-users] Yet another odd problem . . . > > Good to know there's a simple fix - I'll check out the doco > and see if I can figure it out from there, otherwise I may > come back for assistance. > > Simon > ________________________________________ > From: Kumar, Shree [shr...@hp...] > Sent: Friday, May 14, 2010 7:52 PM > To: viz...@li... > Subject: Re: [vizstack-users] Yet another odd problem . . . > > Hi Simon, > > If you run a desktop which uses up _all_ the GPUs on the > system, then you will not face such issues. > > What you are noticing is a contention for input devices > between the X server and your console. When you run a desktop > which does not use all GPUs on a system, you need a dedicated > keyboard and a mouse for the session to avoid such conflicts. > > Let me explain: > > - your console is running all the time on a VT(virtual > terminal). The console has access to the keyboard and mouse. > > - Using viz-desktop, when you start desktop on all the GPUs, > the VT gets switched. This is similar to what happens when > you run GDM, or if press CTRL-ALT-F7. The VT running the X > server now has control of the keyboard and the mouse. > > - When you start a desktop on one or more (but not all) GPUs, > the VT does not get switched. Not switching the VT is a > requirement to run multiple X servers, which in turn is > needed to share the node with multiple X servers. Since the > VT does not switch, your console still has access to the > keyboard and the mouse. That accounts for all the weirdness > you see. In your case, the X server pops up on the same > screen where your console is, causing even more confusion. > > To get one or more physical desktops working the way you > want, you will need a separate physical keyboard/mouse per > user. I have had best results with USB Keyboards and USB > Mice. These need to be added into node_config.xml. Let me > know if I need to describe the nitty gritty involved in this ! > > Regards > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Friday, May 14, 2010 12:46 PM > To: viz...@li... > Subject: [vizstack-users] Yet another odd problem . . . > > A very odd problem . . . > > I've been running viz-desktop from an ssh session all the > time, because when I run it from a console session, the first > time I try to enter anything via the keyboard the display > locks up - the mouse is still rendered normally, but nothing > responds to it. > > I just found, while doing a bit of testing, that when I'm > logged in at the console and I run a viz-desktop session via > ssh the things that were typed into the session show up on > the console as if they were typed in. So, I fire up > viz-desktop, bring up a terminal, start up a vnc session, > type in my password, and so on, and all those lines show up > on the console. I just did a test where the only thing I > brought up was firefox - I typed in a URL, hit enter, and the > URL was in the bash history of the console. Just for fun I > brought up a terminal and changed the prompt - when I closed > the session the prompt in the console was also changed. > > Presumably this is some kind of issue with stdin/stdout not > being redirected correctly . . . > > Simon Fowler > Technical Specialist eResearch Visualisation team CSIRO IM&T > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: <Sim...@cs...> - 2010-05-17 05:31:11
|
Doing away with all the gettys will be problematic - people will need to get onto the console of this system in order to run viz-desktop . . . Would it be possible to run it from an init script? Or possibly from a gdm session? Simon > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Monday, 17 May 2010 3:21 PM > To: viz...@li... > Subject: [vizstack-users] Configuring Physical Desktops( was > RE: Yet another odd problem . . .) > > Hi Simon, > > This is turning out to be more complicated that I had > thought. The interaction with the console seems dependent > even on the linux distro in use :-( > > In particular, I have observed that the default console gets > all the keyboard data - whether it comes from PS/2 or from > USB keyboards. > > On Ubuntu (that's your OS, correct?) you can try the following : > > - Disable all the gettys. This does away with the console > entirely - so nobody will be around to snoop on the keyboard data. > - Try your existing desktop (which doesn't use all GPUs). > This should hopefully work. > > Regards > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Saturday, May 15, 2010 1:10 PM > To: viz...@li... > Subject: Re: [vizstack-users] Yet another odd problem . . . > > Good to know there's a simple fix - I'll check out the doco > and see if I can figure it out from there, otherwise I may > come back for assistance. > > Simon > ________________________________________ > From: Kumar, Shree [shr...@hp...] > Sent: Friday, May 14, 2010 7:52 PM > To: viz...@li... > Subject: Re: [vizstack-users] Yet another odd problem . . . > > Hi Simon, > > If you run a desktop which uses up _all_ the GPUs on the > system, then you will not face such issues. > > What you are noticing is a contention for input devices > between the X server and your console. When you run a desktop > which does not use all GPUs on a system, you need a dedicated > keyboard and a mouse for the session to avoid such conflicts. > > Let me explain: > > - your console is running all the time on a VT(virtual > terminal). The console has access to the keyboard and mouse. > > - Using viz-desktop, when you start desktop on all the GPUs, > the VT gets switched. This is similar to what happens when > you run GDM, or if press CTRL-ALT-F7. The VT running the X > server now has control of the keyboard and the mouse. > > - When you start a desktop on one or more (but not all) GPUs, > the VT does not get switched. Not switching the VT is a > requirement to run multiple X servers, which in turn is > needed to share the node with multiple X servers. Since the > VT does not switch, your console still has access to the > keyboard and the mouse. That accounts for all the weirdness > you see. In your case, the X server pops up on the same > screen where your console is, causing even more confusion. > > To get one or more physical desktops working the way you > want, you will need a separate physical keyboard/mouse per > user. I have had best results with USB Keyboards and USB > Mice. These need to be added into node_config.xml. Let me > know if I need to describe the nitty gritty involved in this ! > > Regards > -- Shree > > -----Original Message----- > From: Sim...@cs... [mailto:Sim...@cs...] > Sent: Friday, May 14, 2010 12:46 PM > To: viz...@li... > Subject: [vizstack-users] Yet another odd problem . . . > > A very odd problem . . . > > I've been running viz-desktop from an ssh session all the > time, because when I run it from a console session, the first > time I try to enter anything via the keyboard the display > locks up - the mouse is still rendered normally, but nothing > responds to it. > > I just found, while doing a bit of testing, that when I'm > logged in at the console and I run a viz-desktop session via > ssh the things that were typed into the session show up on > the console as if they were typed in. So, I fire up > viz-desktop, bring up a terminal, start up a vnc session, > type in my password, and so on, and all those lines show up > on the console. I just did a test where the only thing I > brought up was firefox - I typed in a URL, hit enter, and the > URL was in the bash history of the console. Just for fun I > brought up a terminal and changed the prompt - when I closed > the session the prompt in the console was also changed. > > Presumably this is some kind of issue with stdin/stdout not > being redirected correctly . . . > > Simon Fowler > Technical Specialist eResearch Visualisation team CSIRO IM&T > Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > > -------------------------------------------------------------- > ---------------- > > _______________________________________________ > vizstack-users mailing list > viz...@li... > https://lists.sourceforge.net/lists/listinfo/vizstack-users > |
|
From: Kumar, S. <shr...@hp...> - 2010-05-17 05:23:45
|
Hi Simon, This is turning out to be more complicated that I had thought. The interaction with the console seems dependent even on the linux distro in use :-( In particular, I have observed that the default console gets all the keyboard data - whether it comes from PS/2 or from USB keyboards. On Ubuntu (that's your OS, correct?) you can try the following : - Disable all the gettys. This does away with the console entirely - so nobody will be around to snoop on the keyboard data. - Try your existing desktop (which doesn't use all GPUs). This should hopefully work. Regards -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Saturday, May 15, 2010 1:10 PM To: viz...@li... Subject: Re: [vizstack-users] Yet another odd problem . . . Good to know there's a simple fix - I'll check out the doco and see if I can figure it out from there, otherwise I may come back for assistance. Simon ________________________________________ From: Kumar, Shree [shr...@hp...] Sent: Friday, May 14, 2010 7:52 PM To: viz...@li... Subject: Re: [vizstack-users] Yet another odd problem . . . Hi Simon, If you run a desktop which uses up _all_ the GPUs on the system, then you will not face such issues. What you are noticing is a contention for input devices between the X server and your console. When you run a desktop which does not use all GPUs on a system, you need a dedicated keyboard and a mouse for the session to avoid such conflicts. Let me explain: - your console is running all the time on a VT(virtual terminal). The console has access to the keyboard and mouse. - Using viz-desktop, when you start desktop on all the GPUs, the VT gets switched. This is similar to what happens when you run GDM, or if press CTRL-ALT-F7. The VT running the X server now has control of the keyboard and the mouse. - When you start a desktop on one or more (but not all) GPUs, the VT does not get switched. Not switching the VT is a requirement to run multiple X servers, which in turn is needed to share the node with multiple X servers. Since the VT does not switch, your console still has access to the keyboard and the mouse. That accounts for all the weirdness you see. In your case, the X server pops up on the same screen where your console is, causing even more confusion. To get one or more physical desktops working the way you want, you will need a separate physical keyboard/mouse per user. I have had best results with USB Keyboards and USB Mice. These need to be added into node_config.xml. Let me know if I need to describe the nitty gritty involved in this ! Regards -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Friday, May 14, 2010 12:46 PM To: viz...@li... Subject: [vizstack-users] Yet another odd problem . . . A very odd problem . . . I've been running viz-desktop from an ssh session all the time, because when I run it from a console session, the first time I try to enter anything via the keyboard the display locks up - the mouse is still rendered normally, but nothing responds to it. I just found, while doing a bit of testing, that when I'm logged in at the console and I run a viz-desktop session via ssh the things that were typed into the session show up on the console as if they were typed in. So, I fire up viz-desktop, bring up a terminal, start up a vnc session, type in my password, and so on, and all those lines show up on the console. I just did a test where the only thing I brought up was firefox - I typed in a URL, hit enter, and the URL was in the bash history of the console. Just for fun I brought up a terminal and changed the prompt - when I closed the session the prompt in the console was also changed. Presumably this is some kind of issue with stdin/stdout not being redirected correctly . . . Simon Fowler Technical Specialist eResearch Visualisation team CSIRO IM&T Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: Kumar, S. <shr...@hp...> - 2010-05-17 04:48:17
|
I said "YMMV" due to my experience with nvidia drivers. The same version of a driver may work on some graphics card, but fail to work on another. Since you have a Quadro NVS, might as well give it a try. -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Saturday, May 15, 2010 1:09 PM To: viz...@li... Subject: Re: [vizstack-users] [ExternalEmail] Re: Problem running vs-configure-standalone from shree branch I'll give that version a shot, but I think it's one of the ones we've tried - it may be something to do with the GLX issues, if that version has worked as intended for you before. Simon ________________________________________ From: Kumar, Shree [shr...@hp...] Sent: Saturday, May 15, 2010 5:02 PM To: viz...@li... Subject: Re: [vizstack-users] [ExternalEmail] Re: Problem running vs-configure-standalone from shree branch I checked the version of the nvidia driver on my laptop. Turns out its not old. The version number is : 195.36.15 . You may want to try with this driver, but YMMV. I tried on my machine with this, but faced some other problem. The configure script just hangs with this driver. Investigation revealed that the X server started by the configure Script had not exited. The configure script starts/stops X servers multiple times. If this driver is installed, the X server does not exit at all ! So, I have added a check in the current code - if it finds that the X server doesn't exit in 30 seconds, it flags you to change the driver ! HTH -- Shree -----Original Message----- From: Kumar, Shree Sent: Friday, May 14, 2010 3:27 PM To: viz...@li... Subject: Re: [vizstack-users] [ExternalEmail] Re: Problem running vs-configure-standalone from shree branch > Which version did you find worked? It might be okay for us to move to an older > driver version as a temporary workaround for this. My laptop is at home. I'll check the version and let you know on Monday. That driver wasn't perfect however : when extra pixels were configured, the X server would crash sometimes. > We also have some contacts at nvidia that we're going to talk to about this issue. Any influence helps :-) > Feel free to point anyone who's interested in our user experience with vizstack > at me - the more people using it, the easier it is for us to sell it as a viable > solution ;-) Thanks ! Regards -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Friday, May 14, 2010 12:00 PM To: viz...@li... Subject: Re: [vizstack-users] [ExternalEmail] Re: Problem running vs-configure-standalone from shree branch > -----Original Message----- > From: Kumar, Shree [mailto:shr...@hp...] > Sent: Friday, 14 May 2010 4:20 PM > To: viz...@li... > Subject: Re: [vizstack-users] [ExternalEmail] Re: Problem > running vs-configure-standalone from shree branch > > > > Okay. It's quite frustrating to be so close to exactly what > we want, > > but falling short on something we don't have much power over . . . > > I am not happy with this too. I checked this on my laptop, > which also has nvidia graphics. The laptop has some older > drivers installed, and the bezel compensation does seem to > work well there. Let me hope nvidia can fix this. > Which version did you find worked? It might be okay for us to move to an older driver version as a temporary workaround for this. We also have some contacts at nvidia that we're going to talk to about this issue. > > I was thinking in terms of an app that draws a cross through each > > monitor, and lets you adjust each cross until it lines up with the > > corresponding cross on adjacent monitors - that would give you the > > offsets, which you could then add to the display config > file. I think > > you'd have to assume that monitors weren't tilted - unless > you really > > want to try and apply a totally arbitrary rotation to part of the > > display (which, given that most displays will have multiple > monitors driven by a single GPU, would be a real pain). > > Seems like a workable approach for desktops. This can be made > to setup using VizStack's Python API. > I'll check out the docs and see if I can come up with something. > >>> Oh, another thing that would be nice: some way to set up the > >>> remapping of outputs in the vs-manage-tiled-displays script. > >> > >> It really should have been there. Will fix this. > > > >Cool. > > I have put this in. If you update SVN, you will find the > needed changes. I have been modifying some interfaces > (chiefly the process launching ones), so if anything that was > working two days ago stops working now, do let me know ASAP ! > Testing now - I'll let you know. > I am looking forward to pushing out release 1.1 next week, so > any feedback would be very useful. Note that the > documentation is being updated & there is a user guide and > dev guide too. > > Post release 1.1, I'm going to try giving VizStack some more > publicity. I believe users of Paraview, VirtualGL/TurboVNC, > Equalizer and OpenSG will find Vizstack very useful ! > Feel free to point anyone who's interested in our user experience with vizstack at me - the more people using it, the easier it is for us to sell it as a viable solution ;-) Simon ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
|
From: <Sim...@cs...> - 2010-05-15 07:41:16
|
Good to know there's a simple fix - I'll check out the doco and see if I can figure it out from there, otherwise I may come back for assistance. Simon ________________________________________ From: Kumar, Shree [shr...@hp...] Sent: Friday, May 14, 2010 7:52 PM To: viz...@li... Subject: Re: [vizstack-users] Yet another odd problem . . . Hi Simon, If you run a desktop which uses up _all_ the GPUs on the system, then you will not face such issues. What you are noticing is a contention for input devices between the X server and your console. When you run a desktop which does not use all GPUs on a system, you need a dedicated keyboard and a mouse for the session to avoid such conflicts. Let me explain: - your console is running all the time on a VT(virtual terminal). The console has access to the keyboard and mouse. - Using viz-desktop, when you start desktop on all the GPUs, the VT gets switched. This is similar to what happens when you run GDM, or if press CTRL-ALT-F7. The VT running the X server now has control of the keyboard and the mouse. - When you start a desktop on one or more (but not all) GPUs, the VT does not get switched. Not switching the VT is a requirement to run multiple X servers, which in turn is needed to share the node with multiple X servers. Since the VT does not switch, your console still has access to the keyboard and the mouse. That accounts for all the weirdness you see. In your case, the X server pops up on the same screen where your console is, causing even more confusion. To get one or more physical desktops working the way you want, you will need a separate physical keyboard/mouse per user. I have had best results with USB Keyboards and USB Mice. These need to be added into node_config.xml. Let me know if I need to describe the nitty gritty involved in this ! Regards -- Shree -----Original Message----- From: Sim...@cs... [mailto:Sim...@cs...] Sent: Friday, May 14, 2010 12:46 PM To: viz...@li... Subject: [vizstack-users] Yet another odd problem . . . A very odd problem . . . I've been running viz-desktop from an ssh session all the time, because when I run it from a console session, the first time I try to enter anything via the keyboard the display locks up - the mouse is still rendered normally, but nothing responds to it. I just found, while doing a bit of testing, that when I'm logged in at the console and I run a viz-desktop session via ssh the things that were typed into the session show up on the console as if they were typed in. So, I fire up viz-desktop, bring up a terminal, start up a vnc session, type in my password, and so on, and all those lines show up on the console. I just did a test where the only thing I brought up was firefox - I typed in a URL, hit enter, and the URL was in the bash history of the console. Just for fun I brought up a terminal and changed the prompt - when I closed the session the prompt in the console was also changed. Presumably this is some kind of issue with stdin/stdout not being redirected correctly . . . Simon Fowler Technical Specialist eResearch Visualisation team CSIRO IM&T Yarralumla, 2600 Desk 02 6124 1453 Mob 0409 245 871 ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users ------------------------------------------------------------------------------ _______________________________________________ vizstack-users mailing list viz...@li... https://lists.sourceforge.net/lists/listinfo/vizstack-users |
