There has been some understandable confusion about svccfg syntax lately.

The syntax I use is to enclose the entire command in single quotes, and the 
individual parameter in double quotes.

To fix your particular config, you'll need to do this:

% svccfg -s xend 'delprop config/vnc-listen'
% svccfg -s xend 'setprop config/default-nic = astring: "nge1"'
% svccfg -s xend 'setprop config/vncpasswd = astring: ""'

Then refresh and restart xend, and you should be good to go.

- Russ

Blake Irvin wrote:
> Current values - you'll see that I was experimenting with setting a null 
> password.
> 
> Some examples enclose the listen and password strings with double quotes 
> ("), but I got errors trying to do that, so used single quotes (').
> 
> Output:
> 
> -bash-3.2# svccfg -s xend listprop
> config                              application
> config/dom0-cpus                    integer  0
> config/dom0-min-mem                 integer  196
> config/enable-dump                  boolean  true
> config/stability                    astring  Unstable
> config/xend-relocation-address      astring  127.0.0.1
> config/xend-relocation-hosts-allow  astring  ^localhost$
> config/xend-relocation-server       boolean  true
> config/xend-unix-server             boolean  true
> config/vnc-listen                   astring  \'0.0.0.0\'
> config/default-nic                  astring  'nge1'
> config/vncpasswd                    astring  \'\'
> xenstored                           dependency
> xenstored/entities                  fmri     svc:/system/xvm/store
> xenstored/grouping                  astring  require_all
> xenstored/restart_on                astring  restart
> xenstored/type                      astring  service
> general                             framework
> general/entity_stability            astring  Unstable
> general/single_instance             boolean  true
> start                               method
> start/exec                          astring  "/lib/svc/method/xend %m"
> start/timeout_seconds               count    0
> start/type                          astring  method
> stop                                method
> stop/exec                           astring  :kill
> stop/timeout_seconds                count    60
> stop/type                           astring  method
> tm_common_name                      template
> tm_common_name/C                    ustring  "Hypervisor Control Daemon"
> tm_man_xend                         template
> tm_man_xend/manpath                 astring  /usr/share/man
> tm_man_xend/section                 astring  1M
> tm_man_xend/title                   astring  xend
> 
> BLAKE IRVIN          Systems Administrator
> [EMAIL PROTECTED]
> 
> Vivisimo [Search Done Rightâ„¢]
> 1710 Murray Ave.
> Pittsburgh, PA 15217 USA
> tel: +1.412.422.2499 x153
> fax: +1.412.422.2495
> vivisimo.com    clusty.com
> 
> 
> 
> Russ Blaine wrote:
>> Can you send the output of 'svccfg -s xend listprop' ?
>>
>> If you want the VNC console accessible only from the localhost, you 
>> should delete the vnc-listen property:
>>
>> % svccfg -s xend 'delprop config/vnc-listen'
>>
>> You'll then need to refresh and restart xend:
>>
>> % svcadm refresh xend; svcadm restart xend
>>
>> (this will kill any active HVM domains)
>>
>> Blake Irvin wrote:
>>> I've set xend service properties as follows:
>>>
>>> config/vnc-listen astring \'0.0.0.0\'
>>> config/vncpasswd astring \'vnc\'
>>> config/default-nic astring 'nge1'
>>>
>>> but I get an authentication error whenever I try to connect to the 
>>> console with
>>>
>>> 'vncviewer :0' - I'm on the xvm host itself.
>>>
>>> other relevant data:
>>>
>>> SunOS xvm0 5.11 snv_83 i86pc i386 i86xpv
>>>
>>> What I really want is a way to set a null password for the VNC 
>>> console if possible, since I don't intend to allow remote 
>>> connections, but instead will launch them with X over an ssh tunnel.
>>>
>>> Any ideas?
>>>
>>> cheers,
>>> Blake
>>>
>>>
>>

-- 

-----------------------------------------------------
Russ Blaine | Solaris Kernel | [EMAIL PROTECTED]
_______________________________________________
xen-discuss mailing list
[email protected]

Reply via email to