[workspace-user] virtual workspace cannot boot using WorkspaceService

[Tim Freeman]

On Thu, 31 Aug 2006 11:13:36 +0100
"Dharanikota, Sai Srinivas" <sai.srinivas.dharanikota at intel.com> wrote:

[...]
> vmlinuz-2.6-xenU is a link to vmlinuz-2.6.12.6-xenU, so both are same. I
> hardcoded extra="3" in xen_v2.py and tried to start the VW.
> Unfortunately the run-level doesn't help. The VW boots only with
> fastboot option when it is started using Workspace Service. According to
> this information, I don't see the problem in one of those differences.

OK. I may have to look at this particular distribution.  At this point
I would like to look a the debug logs and investigate, this should not be the
case since we also call xm, I'd like to understand the reason.

If you want to try yourself, the --loglevel DEBUG option to the backend is
triggered in TP1.x if you enable 'exe' extra DEBUG logging in the service's
jndi-config (changes to 'trace' in TP2) (you need to enable DEBUG level in
container-log4j.properties).  

That will also give you the full syntax the service sending to the backend
program.  If you had that, rerunning it with --dryrun added to the invocation
will show you the exact SXP that would have been sent to the domain builder.
The first place to start is to compare that to when you use the "-n" flag with
xm create + config file from a shell.

Tim