setting problem got resolved. (Is there anything we
can do to improve doc, so other users do not run in to similar problem)
/Jd
--- On Thu, 9/4/08, Marco Strullato <[EMAIL PROTECTED]> wrote:
> From: Marco Strullato <[EMAIL PROTECTED]>
> Subject: Re: [convirt-users] edit remot
- On Tue, 9/2/08, jd <[EMAIL PROTECTED]> wrote:
>
>> From: jd <[EMAIL PROTECTED]>
>> Subject: Re: [convirt-users] edit remote vm files and vnc console
>> To: "Marco Strullato" <[EMAIL PROTECTED]>
>> Cc: xenman-users@lists.sourceforge.ne
Hi
> Can you do :
> ssh -p 24 -X
> And then echo $DISPLAY.
>
> Please check your login scripts for the root user too see it eh DISPLAY is
> getting unset.
If I do ssh -p 24 -X hyp03 from the console machine to a hypervisor I
get an emply DISPLAY variable
Exactly I get
Warning: No xauth data;
VNC working from command line ?
Also, pass on convirt.log information to help out with "Edit setting not
working"
/Jd
--- On Tue, 9/2/08, jd <[EMAIL PROTECTED]> wrote:
> From: jd <[EMAIL PROTECTED]>
> Subject: Re: [convirt-users] edit remote vm files and vnc console
inline
--- On Mon, 9/1/08, Marco Strullato <[EMAIL PROTECTED]> wrote:
> From: Marco Strullato <[EMAIL PROTECTED]>
> Subject: Re: [convirt-users] edit remote vm files and vnc console
> To: [EMAIL PROTECTED]
> Cc: xenman-users@lists.sourceforge.net
> Date: Monday,
Hi, thank you for the replay:
> -- What distribution ? version ?
the software I'm using on the console server is xen 3.2 on centos 5 32
bits, convirt 0.9; into the xen servers, centos 5 with xen 3.2 32 and
64 bits, managment ssh on port 24
I verify that gnome-vfs2 is trying to connect to port 22
> Subject: [convirt-users] edit remote vm files and vnc console
> To: xenman-users@lists.sourceforge.net
> Date: Thursday, August 28, 2008, 1:37 AM
> hi all, I'm setting up convirt in a quite big
> environment.
> all hypervisors have 3 interfaces (internal, external,
> ma
hi all, I'm setting up convirt in a quite big environment.
all hypervisors have 3 interfaces (internal, external, managment). A
ssh server listens to internal interface (internal network) on port 22
and another ssh server listens to the managment network on another
port (managment network)
the cons
