5:24 p.m.
my desktop system is running centos6 with downloaded firefox 10. i
downloaded and compiled spice-xpi 2.7. i can interact with the console
one time, then i have to log out of the portal and back in again in
order to get the icon and popup menu to not be greyed out anymore.
so i have a few questions:
1. is this just an issue of using an unsupported browser?
2. ie9 seems to be supported, but i obviously need something more to be
able to view the console. i don't get an error, so i'm not sure what i
should install. the spice viewer i find at spice-space needs libraries
and the libraries there are just a zip file. does something need to go
on the server to auto-download code?
3. i figured i'd try vnc, but in that case the icon and menu option are
always greyed out. just trying vnc to the appropriate host requires a
password and none of the ones i'd suspect seem to work. is there a
default? or some way to find the password?
4. i saw some vague discussion of display networks in the manual, but
nothing in the interface seems to jump out at me. it seems like for most
uses, a simple web based console is what is needed. java or active-x
(or javascript/canvas magic). is this something that is in the
commercial version, but not the free one?
5. or am i just missing something painfully obvious?
1:22 a.m.
On 03/08/2012 01:24 AM, Joe Pruett wrote:
my desktop system is running centos6 with downloaded firefox 10. i
downloaded and compiled spice-xpi 2.7. i can interact with the console
one time, then i have to log out of the portal and back in again in
order to get the icon and popup menu to not be greyed out anymore.
cc-ing spice-devel for hints on logs you should look at
so i have a few questions:
1. is this just an issue of using an unsupported browser?
FF10 would be the long term stable firefox release, so most likely it
will be the focus for support actually.
2. ie9 seems to be supported, but i obviously need something more to be
able to view the console. i don't get an error, so i'm not sure what i
should install. the spice viewer i find at spice-space needs libraries
and the libraries there are just a zip file. does something need to go
on the server to auto-download code?
you need to place an activex of spice.
spice-devel - any status on availability of source or binary form of it
for community?
3. i figured i'd try vnc, but in that case the icon and menu option are
always greyed out. just trying vnc to the appropriate host requires a
password and none of the ones i'd suspect seem to work. is there a
default? or some way to find the password?
currently only to set it via the API/SDK/CLI.
4. i saw some vague discussion of display networks in the manual, but
nothing in the interface seems to jump out at me. it seems like for most
uses, a simple web based console is what is needed. java or active-x
(or javascript/canvas magic). is this something that is in the
commercial version, but not the free one?
display network is to choose which network on the host should be used.
it is a cluster level option on the network.
only relevant if you configure multiple logical networks at DC/Cluster
level.
5. or am i just missing something painfully obvious?
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
3:21 a.m.
Ask yourself this: what's the first thing *anyone* is going to want to do after the
initial install/setup? Yes, that's right - create a VM and connect to the console to
do an install.
Switching to a new protocol (spice) is all very well, but only if clients are easily
available for all common platforms. As I understand things, it's only available as a
package on F16?
Now, the non-availability of spice clients should not be a problem as oVirt also supports
VNC which has always been perfectly adequate as a remote client for me in the past (esp.
for headless, console-based servers). But, there is no easy way to find the VNC port that
a given VM is using or to set the VNC password. I figured it out, and could probably
script something to do it automatically, but that should be necessary for such a
fundamental task!
Please forgive my rant, but I'd just like to say that, as someone coming new to oVirt,
I think the whole console issue is a bit of a mess and should be made a priority to sort
out.
R.
3:53 a.m.
----- Original Message -----
From: "Robin Bowes" <robin.bowes(a)yo61.com>
To: users(a)ovirt.org
Sent: Thursday, March 8, 2012 4:21:45 AM
Subject: Re: [Users] console confusion
Ask yourself this: what's the first thing *anyone* is going to want
to do after the initial install/setup? Yes, that's right - create a
VM and connect to the console to do an install.
Switching to a new protocol (spice) is all very well, but only if
clients are easily available for all common platforms. As I
understand things, it's only available as a package on F16?
We are packing it now for Windows, we have this packaged downstream (RHEV), now we're
re-working that for upstream.
The work is ongoing we need to add to the matrix. Other distributions are starting to
package spice now.
After that we need to look at other platforms such as Mac OS.
Now, the non-availability of spice clients should not be a problem as
oVirt also supports VNC which has always been perfectly adequate as
a remote client for me in the past (esp. for headless, console-based
servers). But, there is no easy way to find the VNC port that a
given VM is using or to set the VNC password. I figured it out, and
could probably script something to do it automatically, but that
should be necessary for such a fundamental task!
Please forgive my rant, but I'd just like to say that, as someone
coming new to oVirt, I think the whole console issue is a bit of a
mess and should be made a priority to sort out.
Agree, but remember with oVirt you're working with a community project not an end-user
product where you can make feature requests.
There are interesting options for VNC, most notably NoVNC that could be integrated - but
it needs someone to drive this.
In the mean time there's a relatively straightforward way to launch a VNC client for a
VM by using the API.
Dan's working on an example of that now that we'll post on the wiki,
Aic
R.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
4:05 a.m.
On 8 Mar 2012, at 09:53, Andrew Cathrow wrote:
We are packing it now for Windows, we have this packaged downstream
(RHEV), now we're re-working that for upstream.
The work is ongoing we need to add to the matrix. Other distributions are starting to
package spice now.
After that we need to look at other platforms such as Mac OS.
An OS-X client would be great!
Agree, but remember with oVirt you're working with a community
project not an end-user product where you can make feature requests.
There are interesting options for VNC, most notably NoVNC that could be integrated - but
it needs someone to drive this.
Yes, I do realise that - I will help out wherever I can (possibly EL6 port?).
In the mean time there's a relatively straightforward way to
launch a VNC client for a VM by using the API.
Dan's working on an example of that now that we'll post on the wiki,
I look forward to seeing that.
Thanks,
R.
9:43 a.m.
----- Original Message -----
From: "Robin Bowes" <robin.bowes(a)yo61.com>
To: users(a)ovirt.org
Cc: "Dan Yasny" <dyasny(a)redhat.com>, "Andrew Cathrow"
<acathrow(a)redhat.com>
Sent: Thursday, 8 March, 2012 12:05:51 PM
Subject: Re: [Users] console confusion
On 8 Mar 2012, at 09:53, Andrew Cathrow wrote:
> We are packing it now for Windows, we have this packaged downstream
> (RHEV), now we're re-working that for upstream.
> The work is ongoing we need to add to the matrix. Other
> distributions are starting to package spice now.
> After that we need to look at other platforms such as Mac OS.
An OS-X client would be great!
> Agree, but remember with oVirt you're working with a community
> project not an end-user product where you can make feature
> requests.
> There are interesting options for VNC, most notably NoVNC that
> could be integrated - but it needs someone to drive this.
Yes, I do realise that - I will help out wherever I can (possibly EL6
port?).
> In the mean time there's a relatively straightforward way to launch
> a VNC client for a VM by using the API.
> Dan's working on an example of that now that we'll post on the
> wiki,
I look forward to seeing that.
Already works fine with vncviewer/tigervnc, need to make some adjustments for additional
VNC clients, and I'll post it to oVirt wiki
Thanks,
R.
--
Regards,
Dan Yasny
Red Hat Israel
+972 9769 2280
7:40 a.m.
----- Original Message -----
From: "Robin Bowes" <robin.bowes(a)yo61.com>
To: users(a)ovirt.org
Cc: "Dan Yasny" <dyasny(a)redhat.com>, "Andrew Cathrow"
<acathrow(a)redhat.com>
Sent: Thursday, 8 March, 2012 12:05:51 PM
Subject: Re: [Users] console confusion
On 8 Mar 2012, at 09:53, Andrew Cathrow wrote:
> We are packing it now for Windows, we have this packaged downstream
> (RHEV), now we're re-working that for upstream.
> The work is ongoing we need to add to the matrix. Other
> distributions are starting to package spice now.
> After that we need to look at other platforms such as Mac OS.
An OS-X client would be great!
> Agree, but remember with oVirt you're working with a community
> project not an end-user product where you can make feature
> requests.
> There are interesting options for VNC, most notably NoVNC that
> could be integrated - but it needs someone to drive this.
Yes, I do realise that - I will help out wherever I can (possibly EL6
port?).
> In the mean time there's a relatively straightforward way to launch
> a VNC client for a VM by using the API.
> Dan's working on an example of that now that we'll post on the
> wiki,
I look forward to seeing that.
Sorry it took a while, been busy with other things. Anyhow, I have a script working for
tigervnc client under fedora and RHEL, looking for a Mac to test this on
Thanks,
R.
--
Regards,
Dan Yasny
Red Hat Israel
+972 9769 2280
3:41 p.m.
On 03/23/2012 02:40 PM, Dan Yasny wrote:
----- Original Message -----
> From: "Robin Bowes"<robin.bowes(a)yo61.com>
> To: users(a)ovirt.org
> Cc: "Dan Yasny"<dyasny(a)redhat.com>, "Andrew
Cathrow"<acathrow(a)redhat.com>
> Sent: Thursday, 8 March, 2012 12:05:51 PM
> Subject: Re: [Users] console confusion
>
> On 8 Mar 2012, at 09:53, Andrew Cathrow wrote:
>> We are packing it now for Windows, we have this packaged downstream
>> (RHEV), now we're re-working that for upstream.
>> The work is ongoing we need to add to the matrix. Other
>> distributions are starting to package spice now.
>> After that we need to look at other platforms such as Mac OS.
>
> An OS-X client would be great!
>
>> Agree, but remember with oVirt you're working with a community
>> project not an end-user product where you can make feature
>> requests.
>> There are interesting options for VNC, most notably NoVNC that
>> could be integrated - but it needs someone to drive this.
>
> Yes, I do realise that - I will help out wherever I can (possibly EL6
> port?).
>
>> In the mean time there's a relatively straightforward way to launch
>> a VNC client for a VM by using the API.
>> Dan's working on an example of that now that we'll post on the
>> wiki,
>
> I look forward to seeing that.
Sorry it took a while, been busy with other things. Anyhow, I have a script working for
tigervnc client under fedora and RHEL, looking for a Mac to test this on
did you check the ovirt shell support of console command?
3:46 a.m.
New subject: [Users] [Spice-devel] console confusion
----- Original Message -----
From: "Itamar Heim" <iheim(a)redhat.com>
To: "Joe Pruett" <joey(a)q7.com>
Cc: spice-devel(a)lists.freedesktop.org, users(a)ovirt.org
Sent: Thursday, March 8, 2012 8:22:11 AM
Subject: Re: [Spice-devel] [Users] console confusion
On 03/08/2012 01:24 AM, Joe Pruett wrote:
> my desktop system is running centos6 with downloaded firefox 10.
> i
> downloaded and compiled spice-xpi 2.7. i can interact with the
> console
> one time, then i have to log out of the portal and back in again in
> order to get the icon and popup menu to not be greyed out anymore.
cc-ing spice-devel for hints on logs you should look at
It should be fixed by
commit made today (a while ago) Could you recompiled/apply patch?
>
> so i have a few questions:
>
> 1. is this just an issue of using an unsupported browser?
FF10 would be the long term stable firefox release, so most likely it
will be the focus for support actually.
>
> 2. ie9 seems to be supported, but i obviously need something more
> to be
> able to view the console. i don't get an error, so i'm not sure
> what i
> should install. the spice viewer i find at spice-space needs
> libraries
> and the libraries there are just a zip file. does something need
> to go
> on the server to auto-download code?
you need to place an activex of spice.
spice-devel - any status on availability of source or binary form of
it
for community?
>
> 3. i figured i'd try vnc, but in that case the icon and menu option
> are
> always greyed out. just trying vnc to the appropriate host
> requires a
> password and none of the ones i'd suspect seem to work. is there a
> default? or some way to find the password?
currently only to set it via the API/SDK/CLI.
>
> 4. i saw some vague discussion of display networks in the manual,
> but
> nothing in the interface seems to jump out at me. it seems like for
> most
> uses, a simple web based console is what is needed. java or
> active-x
> (or javascript/canvas magic). is this something that is in the
> commercial version, but not the free one?
display network is to choose which network on the host should be
used.
it is a cluster level option on the network.
only relevant if you configure multiple logical networks at
DC/Cluster
level.
>
> 5. or am i just missing something painfully obvious?
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
_______________________________________________
Spice-devel mailing list
Spice-devel(a)lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/spice-devel
4654
days inactive
4672
days old
8 comments
6 participants
participants (6)
-
Andrew Cathrow -
Dan Yasny -
Itamar Heim -
Joe Pruett -
Marian Krcmarik -
Robin Bowes