> about openvswitch
> -
> I have done some tests with openvswitch, and it's work really fine.
> iperf show me 20Gb/s, I never reach more than 8gb/s with linux bridge.
> vlan work out of the box.
I cannot see a technical reason why linux bridge is slower than ovs?
Can you reproduce
> @Dietmar
>
> about openvswitch, I would like to add support to be able to plug kvm tap
> interface into it.
> (simple detection if vmbrX is a linux bridge or openvswitch through sysfs, and
> then use brctl or ovz-ctl command to plug tap interface).
>
> So advanced users could use them if they w
I get the following warnings when booting with 3.10 kernel:
---
Tue Dec 17 07:58:55 2013: Mounting local filesystems...done.
Tue Dec 17 07:58:55 2013: Activating swapfile swap...done.
Tue Dec 17 07:58:55 2013: Cleaning up temporary files
Tue Dec 17 07:58:55 2013: Setting kernel variabl
>>it just works for me with vanilla 3.10 and the additional patch. BUT
>>without VLAN filtering i don't use it.
Don't you use special setup with bridge on top of another bridge ? (It was
about gvrp support If I remember)
About vlan filtering
>>could you send me:
>>zgrep
Am 16.12.2013 16:01, schrieb Dietmar Maurer:
wouldn't it be a good idea to integrate http://kanaka.github.io/noVNC/?
It's pretty fast and there would be no need for java anymore...
Besides, we want to move from VNC to SPICE.
http://www.spice-space.org/page/Html5
But I guess this is not stabl
Am 16.12.2013 15:59, schrieb Dietmar Maurer:
wouldn't it be a good idea to integrate http://kanaka.github.io/noVNC/?
It's pretty fast and there would be no need for java anymore...
This was very slow (and crashed) last time i tested.
At least Openstack and Opennebula use it. So it should be
Hi,
it just works for me with vanilla 3.10 and the additional patch. BUT
without VLAN filtering i don't use it.
could you send me:
zgrep 'VLAN' /prof/config.gz
and
sysctl -a | grep bridge
Stefan
Am 16.12.2013 16:37, schrieb Alexandre DERUMIER:
Stefan,
you could send how you manage bridge
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
Stefan,
you could send how you manage bridge vlan on top of other bridge ?
(I would like to test with 3.10 kernel, as I had problem last year with 2.6.32
kernel)
I'm also looking at openvswitch, as it seem it's possible to mix bridge and
openvswitch.
Seem that openstack can manage this kind
>From 8118b81626a73fcb83b6b21d498b6724c4b63817 Mon Sep 17 00:00:00 2001
From: Igor Shestakov
Date: Mon, 16 Dec 2013 17:39:09 +0400
Subject: [PATCH] changed set_rootpasswd method for ploop support
Signed-off-by: Igor Shestakov
---
PVE/API2/OpenVZ.pm | 12 +++-
PVE/OpenVZ.pm | 7 ++
> wouldn't it be a good idea to integrate http://kanaka.github.io/noVNC/?
> It's pretty fast and there would be no need for java anymore...
Besides, we want to move from VNC to SPICE.
http://www.spice-space.org/page/Html5
But I guess this is not stable enough for now.
__
> wouldn't it be a good idea to integrate http://kanaka.github.io/noVNC/?
> It's pretty fast and there would be no need for java anymore...
This was very slow (and crashed) last time i tested.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://
> 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
Hi,
wouldn't it be a good idea to integrate http://kanaka.github.io/noVNC/?
It's pretty fast and there would be no need for java anymore...
Greets,
Stefan
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listin
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
26 matches
Mail list logo
