crash and guest crash (debian lenn,squeeze,wheezy,
> win2003,win2012R2,win2008R2)
>
>
> - Mail original -
>
> De: "Dietmar Maurer"
> À: "Alexandre DERUMIER"
> Cc: pve-devel@pve.proxmox.com, "i iordanov"
> Envoyé: Mercredi 20 Août 2014 2
Cc: pve-devel@pve.proxmox.com, "i iordanov"
Envoyé: Mercredi 20 Août 2014 20:18:28
Objet: RE: [pve-devel] Proxmox compatible Android client (Opaque) available for
beta testing
> (BTW, I also see bootstrap framework source inside pve-manager git, is it for
> future work ?)
Oh, this is excellent news!
Thank you Dietmar!
Cheers,
iordan
On Wed, Aug 20, 2014 at 1:19 PM, Dietmar Maurer wrote:
>> The plan is to write a Sencha Touch based GUI for small devices. But I had no
>> time to start that project.
>
> Just want to mention that we now have a Sencha Touch based GUI
> (BTW, I also see bootstrap framework source inside pve-manager git, is it for
> future work ?)
I currently use that for the default html formatter, because I am tired to do
all css hacks syself ;-) This is just for debugging.
Just try:
https://your.host-or-ip:8006/api2/html/
But using server
inal -
>
> De: "Dietmar Maurer"
> À: "i iordanov"
> Cc: "pve-devel@pve.proxmox.com"
> Envoyé: Mercredi 20 Août 2014 19:19:35
> Objet: Re: [pve-devel] Proxmox compatible Android client (Opaque) available
> for beta testing
>
>> The plan is t
.
(BTW, I also see bootstrap framework source inside pve-manager git, is it for
future work ?)
- Mail original -
De: "Dietmar Maurer"
À: "i iordanov"
Cc: "pve-devel@pve.proxmox.com"
Envoyé: Mercredi 20 Août 2014 19:19:35
Objet: Re: [pve-devel] Proxmox co
> The plan is to write a Sencha Touch based GUI for small devices. But I had no
> time to start that project.
Just want to mention that we now have a Sencha Touch based GUI. Please use the
pvetest repository for testing. Mobile interface is (hopefully) automatically
detected
when you connect wit
patch is here:
https://git.proxmox.com/?p=pve-manager.git;a=commit;h=f481098dc8db6d481a9903a1351b1d530a745e3a
> On Wed, Jan 15, 2014 at 12:04 PM, Dietmar Maurer
> wrote:
> Oh, seems this is not related to our ticket lifetime - instead this is the
> spiceterm
> timeout.
> I will increase that va
Hi Dietmar,
On Wed, Jan 15, 2014 at 12:04 PM, Dietmar Maurer wrote:
> Oh, seems this is not related to our ticket lifetime - instead this is the
> spiceterm timeout.
> I will increase that value to 60 seconds.
>
I started doubting my sanity for a while there :D, because I was sure it
was shorter
> In order to reduce initial user frustration especially on slower devices, I
> would
> make it 40 seconds if you're comfortable with such a timeout. An experienced
> user with a fast device probably needs 1/4 of that, of course.
Oh, seems this is not related to our ticket lifetime - instead this
> In order to reduce initial user frustration especially on slower devices, I
> would
> make it 40 seconds if you're comfortable with such a timeout. An experienced
> user with a fast device probably needs 1/4 of that, of course.
That is what we have now:
# use very limited lifetime - is
Hi Dietmar,
On Wed, Jan 15, 2014 at 12:43 AM, Dietmar Maurer wrote:
> What timeout woul you suggest?
>
In order to reduce initial user frustration especially on slower devices, I
would make it 40 seconds if you're comfortable with such a timeout. An
experienced user with a fast device probably n
> Thanks for confirming the functionality! Do you guys think it's warranted to
> extend the timeout a bit so that people who are not as fast at realizing they
> have to tap on the downloaded file will have time? Check how soon the ticket
> expires subjectively and tell me whether you feel in a rush
Hi Martin,
On Tue, Jan 14, 2014 at 4:38 AM, Martin Maurer wrote:
> I just got it running on my Nexus 7 (first version), running on current
> android 4.4.2 and using Chrome Browser.
>
Thanks for confirming the functionality! Do you guys think it's warranted
to extend the timeout a bit so that pe
Hi,
I just got it running on my Nexus 7 (first version), running on current android
4.4.2 and using Chrome Browser.
The Proxmox VE gui is unusable slow on this device but basically it works and
the SPICE connection opens as described in your post, great!
There is already a third party Android A
> Another thing I can say is that both the Admin portal of oVirt and Proxmox
> have
> relatively small buttons which are well suited to clicking with a mouse but
> not
> for tapping on a mobile device. Also, having one side of the (Shell) button as
> drop-down functionality looks very good and wo
Hi Dietmar,
On Tue, Jan 14, 2014 at 1:41 AM, Dietmar Maurer wrote:
>
> Thanks for the report, but I have no idea how to address that. Looks that
> some browser
> have serious bugs.
>
I'm not in a good position to give advice on this topic, but I can tell you
that UC Browser and (if I'm not mist
> A summary of my observations on the ability to download the console/vv file on
> mobile browsers. I hope you find these useful in making Proxmox easier to use
> on mobile devices.
Thanks for the report, but I have no idea how to address that. Looks that some
browser
have serious bugs.
> Andro
Hello,
A summary of my observations on the ability to download the console/vv file
on mobile browsers. I hope you find these useful in making Proxmox easier
to use on mobile devices.
Android 4.4 device:
1) Chrome works, and is fairly seamless. After downloading, one swipes the
notifications and t
Hello again,
Whoever is currently an Opaque beta-tester, please update to v1.1.6, and
you should be able to connect to your Proxmox managed VMs from your Android
device easily. The way it works for me on my Nexus 4 (Android 4.4) with
both Firefox and Chrome is that when I obtain the vv/console fil
> I got remote-viewer to work by opening the file much more quickly. It seems
> like
> the expiration period is 10 seconds or shorter!
from current code:
# use very limited lifetime - is this enough?
return undef if !(($age > -20) && ($age < 40));
maybe system time is not correc
> As mentioned previously, I can't even get a known, working remote-viewer to
> open a connection to the Shell. All I get is an error:
> (remote-viewer:3348): GSpice-WARNING **: HTTP proxy server closed
> connection unexpectedly.
The file contains a ticket, which is only valid for 30 seconds. You
> Is this a possible lead for how to set a file name for POST:
> http://stackoverflow.com/questions/93551/how-to-encode-the-filename-
> parameter-of-content-disposition-header-in-http
Looks strange to me to set a content disposition for CT application/json.
> All other browsers environments w
gt;>
>> Cheers,
>> iordan
>>
>>
>>
>> On Mon, Jan 13, 2014 at 2:26 AM, Dietmar Maurer wrote:
>>
>>> see attached screenshot
>>>
>>>
>>>
>>> *From:* i iordanov [mailto:iiorda...@gmail.com]
>>> *Sent:* M
t; Cheers,
> iordan
>
>
>
> On Mon, Jan 13, 2014 at 2:26 AM, Dietmar Maurer wrote:
>
>> see attached screenshot
>>
>>
>>
>> *From:* i iordanov [mailto:iiorda...@gmail.com]
>> *Sent:* Montag, 13. Jänner 2014 08:01
>> *To:* Dietmar Maurer
Hi Lindsay,
On Mon, Jan 13, 2014 at 2:25 AM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> I suspect you need to be register your app as a viewer for the spice
> mime type (application/x-virt-viewer)
>
> Article here:
> http://richardleggett.co.uk/blog/2013/01/26/registering_for_file_
Hi Dietmar,
Is this a possible lead for how to set a file name for POST:
http://stackoverflow.com/questions/93551/how-to-encode-the-filename-parameter-of-content-disposition-header-in-http
On Mon, Jan 13, 2014 at 2:19 AM, Dietmar Maurer wrote:
> All other browsers environments works that way.
I suspect you need to be register your app as a viewer for the spice
mime type (application/x-virt-viewer)
Article here:
http://richardleggett.co.uk/blog/2013/01/26/registering_for_file_types_in_android/
On 13 January 2014 16:42, i iordanov wrote:
> Hi Dietmar,
>
> On Mon, Jan 13, 2014 at 1:37
> We do not set any file name (that name is generated by the browser).
>
> Is there no way to work around that? I cannot declare that I handle files of a
> certain name on Android, they must have an extension.
The API is a POST action - I hav no idea how to set a filename for that.
> The alterna
Hi Dietmar,
On Mon, Jan 13, 2014 at 1:37 AM, Dietmar Maurer wrote:
> > 2) How to tweak the server to change the name of the file to
> spiceproxy.vv from
> > "spiceproxy".
>
> We do not set any file name (that name is generated by the browser).
>
Is there no way to work around that? I cannot dec
> Can you please tell me how to:
> 0) How to obtain the certificate authority in order to import it into Opaque.
We include all information in the 'vv' file, so that is not really needed.
But the CA is stored at /etc/pve/pve-root-ca.pem
> 1) How to obtain the spiceproxy ".vv" file for connecting
Hi Dietmar,
I've installed Proxmox in a VM, updated with the pvetest sources, and
installed spiceterm. However, I don't know how to proceed.
Can you please tell me how to:
0) How to obtain the certificate authority in order to import it into
Opaque.
1) How to obtain the spiceproxy ".vv" file fo
Hi Dietmar,
On Mon, Dec 16, 2013 at 2:17 AM, Dietmar Maurer wrote:
> But install from Proxmox CD inside a VM is done in 2 minutes :-)
>
> If you go that way, I suggest that you update to latest code from
> 'pvetest' repository after installation.
>
> "deb http://download.proxmox.com/debian whee
> On Mon, 16 Dec 2013 12:13:45 PM Dietmar Maurer wrote:
> > > The web client works fine, but the spice client failed to connect.
> >
> > port is 3128
>
>
> That did the trick. A simple redirect of ports 8006 & 3128 for full remote
> access.
BTW, should we use port 3128 or something else? We alr
On Mon, 16 Dec 2013 12:13:45 PM Dietmar Maurer wrote:
> > The web client works fine, but the spice client failed to connect.
>
> port is 3128
That did the trick. A simple redirect of ports 8006 & 3128 for full remote
access.
Thanks,
--
Lindsay
signature.asc
Description: This is a digitally s
> Because I just tried a simple port tunnel through our company firewall, 8006
> to
> ProxMox Server.
>
> The web client works fine, but the spice client failed to connect.
port is 3128
but the client need configuration, so you can simply start "remote-viewer
spice:/x.y.z"
(proxy, certificate
On Mon, 16 Dec 2013 12:02:13 PM Dietmar Maurer wrote:
> > Will the spice client work through a http proxy?
>
> On PVE we use our own proxy implementation (spiceproxy).
> That way all connection are handled with a single port.
Is it the same port as the webclient (8006)?
Because I just tried a si
> Will the spice client work through a http proxy?
On PVE we use our own proxy implementation (spiceproxy).
That way all connection are handled with a single port.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/
On Mon, 16 Dec 2013 11:25:59 AM Dietmar Maurer wrote:
> I also use 0.5.6 and 0.5.7.
>
> But maybe it is fast enough
Yes, if people want faster or more features then they can use a full ssh
terminal session with their favourite client.
The big advantage of spice is you don't need to know the vm
> Afraid not. I'm getting decent scrolling speed in 1920x1080. Not fast but fast
> enough.
>
> My spice client is sv 0.5.6 - whats yours?
I also use 0.5.6 and 0.5.7.
But maybe it is fast enough ;-)
___
pve-devel mailing list
pve-devel@pve.proxmox.com
On Mon, 16 Dec 2013 11:04:22 AM Dietmar Maurer wrote:
> Not sure why xterm can scroll so much faster than spiceterm.
> Any ideas?
Afraid not. I'm getting decent scrolling speed in 1920x1080. Not fast but fast
enough.
My spice client is sv 0.5.6 - whats yours?
--
Lindsay
signature.asc
Descripti
> Very nice, fast to start and responsive. And fullscreen mode etc of course
> too.
> The container console is the same of course.
Well, I am not really happy with spiceterm performance on large screens.
Scrolling
is very slow on my 2560x1440 screen when I run fullscreen.
Not sure why xterm can
On Mon, 16 Dec 2013 10:49:34 AM Dietmar Maurer wrote:
> Set Datacenter/Options/ConsoleViewer to SPICE.
D'oh! and I looked for something like that to.
Very nice, fast to start and responsive. And fullscreen mode etc of course
too. The container console is the same of course.
NB: Its impressive
> > I see some minor changes to the web ui, but no spiceterm - whereabouts
> > does it come into play? the node shell and container shell are still web
> > vnc.
>
> Set Datacenter/Options/ConsoleViewer to SPICE.
And 'reload' the GUI after that.
___
pv
> I see some minor changes to the web ui, but no spiceterm - whereabouts does it
> come into play? the node shell and container shell are still web vnc.
Set Datacenter/Options/ConsoleViewer to SPICE.
___
pve-devel mailing list
pve-devel@pve.proxmox.co
On Mon, 16 Dec 2013 07:17:23 AM Dietmar Maurer wrote:
> But install from Proxmox CD inside a VM is done in 2 minutes
>
> If you go that way, I suggest that you update to latest code from 'pvetest'
> repository after installation.
>
> "deb http://download.proxmox.com/debian wheezy pvetest"
>
> I
> I was not aware of the spiceterm project. I guess I have to install Proxmox to
> learn about it because Google searches yielded only a link to the git
> repository,
> and I couldn't find a README in the repository.
Oh, documentaion is in the .pod file:
https://git.proxmox.com/?p=spiceterm.git;
Hi Dietmar,
I was not aware of the spiceterm project. I guess I have to install Proxmox
to learn about it because Google searches yielded only a link to the git
repository, and I couldn't find a README in the repository.
Thanks,
iordan
On Mon, Dec 16, 2013 at 12:10 AM, Dietmar Maurer wrote:
>
> I had the most terrible time trying to nest an all-in-one oVirt installation
> in a VM.
> The VMs would hang on startup (qemu-kvm at 100%) and their SPICE consoles
> were not attachable. Finally, I resorted to dedicating hardware to my oVirt
> test
> rig.
> Why do you think Proxmox would be an
Hi Dietmar,
I had the most terrible time trying to nest an all-in-one oVirt
installation in a VM. The VMs would hang on startup (qemu-kvm at 100%) and
their SPICE consoles were not attachable. Finally, I resorted to dedicating
hardware to my oVirt test rig.
Why do you think Proxmox would be any b
> I agree that if I want to support Proxmox I should have a server installed,
> but
> that's something that may happen in the new year. I don't have any hardware to
> dedicate to a server at the moment.
Just want to mention that you do not need a dedicated hardware. I would be good
enough
to ins
> In v.1.1.3, Opaque no longer registers https:// URI support for .vv files.
> In addition, I've added experimental http:// support for .vv files, and
> http://
> support for the "application/x-virt-viewer" mime type. Yes, I realize that not
> having https:// support is a little useless and it may
Hi Dietmar,
Since it was a very quick change to fix what I think was your problem, I've
pushed another version to Beta. Remember that I think the issue was that
Opaque registered http:// and https:// URI support for .vv files where it
was only actually supporting file:// URIs.
In v.1.1.3, Opaque
> I agree that if I want to support Proxmox I should have a server installed,
> but
> that's something that may happen in the new year. I don't have any hardware to
> dedicate to a server at the moment.
ok
___
pve-devel mailing list
pve-devel@pve.proxm
My application is going to be open-source soon, I haven't decided whether
to integrate it into bVNC or keep it separate and the code is not ready yet.
The part of the application which establishes the SPICE connection is
already present in full in bVNC (from which aSPICE is created). The only
part
> If you would like to confirm my hypothesis, please try to *download* the file
> somehow, and then tap on it. Opaque should start and work.
I think it is extremely clumsy to debug that way. I think you should setup PVE
server
yourself. Installation takes just a few minutes.
You application is c
> > I managed to name the file correctly, but chrome does not start the app
> anyways.
> > Firefox seems to start opaque, but it crashes immediately (before contacting
> the proxy).
> >
> >
> What needs changed to name it spiceproxy.vv?
> I would like to make those changes on my system so I can tes
Hi Dietmar,
If you would like to confirm my hypothesis, please try to *download* the
file somehow, and then tap on it. Opaque should start and work.
Cheers!
iordan
On Thu, Dec 12, 2013 at 9:09 AM, i iordanov wrote:
> Hi Dietmar,
>
> I assume you made the server give you a .vv file? I think I
Hi Dietmar,
I assume you made the server give you a .vv file? I think I know what may
be at fault here. Opaque expects a file on the local filesystem, and the
intent contains a URI with http:// or https:// scheme.
I think I'm also able to handle mime types, but Firefox still downloads a
file rath
I managed to name the file correctly, but chrome does not start the app anyways.
Firefox seems to start opaque, but it crashes immediately (before contacting
the proxy).
What needs changed to name it spiceproxy.vv?
I would like to make those changes on my system so I can test this too.
_
> The file downloaded from Proxmox but is named "spiceproxy" not
> "spiceproxy.vv"
>
> This is an actual problem. Can somebody from the Proxmox developers say
> whether it can be addressed? How is the browser/OS supposed to know which
> application to use to open the file? Would you consider addin
> On Wed, Dec 11, 2013 at 3:52 PM, Eric Blevins wrote:
> 3) Obtain a .vv file for a VM, and tap it to "open" it. Opaque will launch
> automatically and use the .vv file. I've tested Firefox and UCBrowser with
> oVirt,
> and they can download the .vv files from there and open them with one tap or
Anybody who has problems accessing the graphical console of a VM and would
not mind creating an unprivileged user with access to an unimportant VM (if
that's possible in Proxmox), I would be able to try reproducing the issue
on my device as well.
Mind you, I don't know whether Proxmox allows mere
Hi Eric,
Thanks for the feedback!
On Wed, Dec 11, 2013 at 3:52 PM, Eric Blevins wrote:
> 3) Obtain a .vv file for a VM, and tap it to "open" it. Opaque will launch
>> automatically and use the .vv file. I've tested Firefox and UCBrowser with
>> oVirt, and they can download the .vv files from th
2) Login to Proxmox's web interface with a mobile browser.
Proxmox GUI worked ok in Firefox but was a bit slow and clunky to
navigate on a phone.
3) Obtain a .vv file for a VM, and tap it to "open" it. Opaque will
launch automatically and use the .vv file. I've tested Firefox and
UCBrowser
Am 11.12.2013 20:00, schrieb Dietmar Maurer:
Another problem is that the ExtJS GUI is not really usable under IPhone /
Android
at least with a few hundret VMs.
I think a special Web Portal is needed in general für such a purpose.
Some time ago someone started that:
https://code.google.com/p
> Another problem is that the ExtJS GUI is not really usable under IPhone /
> Android
> at least with a few hundret VMs.
>
> I think a special Web Portal is needed in general für such a purpose.
Some time ago someone started that:
https://code.google.com/p/quadprox-mobile/
But I do not know if
Hi guys,
>From all the discussion, it seems like we need a person with access to a
Proxmox environment to do the following:
1) Join the beta and acquire Opaque.
2) Login to Proxmox's web interface with a mobile browser.
3) Obtain a .vv file for a VM, and tap it to "open" it. Opaque will launch
au
> On an Android device, when you download a file via mobile browser, you are
> typically no more than a swipe and a tap away from opening the file. Since
> Opaque is registered to handle the file, there is absolutely no break in the
> flow,
> and there is at most a 2 - 3 second delay between downl
Hi Dietmar,
I appear to have replied only to you in the previous message, please ignore
it.
On Wed, Dec 11, 2013 at 1:43 PM, Dietmar Maurer wrote:
> Sure, we have a web portal where you can download the virt-viewer
> configuration
> values. But those values includes tickets for proxy access wit
Am 11.12.2013 19:43, schrieb Dietmar Maurer:
I do not have support for the Proxmox API at all (for the moment).
So how do you want to get the vv file (confused)?
I thought that Proxmox has a web portal where people login and can click to
obtain a console.vv file for their VM(s). I guess I was w
> > I do not have support for the Proxmox API at all (for the moment).
> So how do you want to get the vv file (confused)?
>
> I thought that Proxmox has a web portal where people login and can click to
> obtain a console.vv file for their VM(s). I guess I was wrong.
Sure, we have a web portal wh
Hi Dietmar,
On Wed, Dec 11, 2013 at 11:19 AM, Dietmar Maurer wrote:
> > I do not have support for the Proxmox API at all (for the moment).
>
> So how do you want to get the vv file (confused)?
>
I thought that Proxmox has a web portal where people login and can click to
obtain a console.vv file
> I do not have support for the Proxmox API at all (for the moment).
So how do you want to get the vv file (confused)?
> All I do is
> register support for .vv files with the Android OS. Is there no way to obtain
> a
> console.vv file through a web portal on Proxmox anymore?
No, I removed that
Hi Dietmar,
I do not have support for the Proxmox API at all (for the moment). All I do
is register support for .vv files with the Android OS. Is there no way to
obtain a console.vv file through a web portal on Proxmox anymore?
Thanks!
iordan
On Wed, Dec 11, 2013 at 2:08 AM, Dietmar Maurer wro
> I am the developer behind aSPICE, the Android SPICE client. In order to better
> support enterprise VDI environments, I decided to create a new client called
> Opaque which aims to give users the ability to attach to the graphics console
> of
> their VMs running in an oVirt, RHEV, or Proxmox in
Hello,
I am the developer behind aSPICE, the Android SPICE client. In order to
better support enterprise VDI environments, I decided to create a new
client called Opaque which aims to give users the ability to attach to the
graphics console of their VMs running in an oVirt, RHEV, or Proxmox
infras
77 matches
Mail list logo
