similar to: Hardware requirements for SPICEd desktops

Hello all. I posted here a few days ago about the support of dynamic selection of the port to forward (ssh -R 0:host:port), which refers to section 7.1 of http://www.ietf.org/internet-drafts/draft-ietf-secsh-connect-24.txt . My posts were from lcml at pixel.it, while this is from lucio at sulweb.org. Nevermind, It's always me. Here is the patch that adds support for that thing. It's

On Wed, Mar 15, 2017 at 10:26:20AM +0000, Daniel Pocock wrote: > >Can anybody comment on how to host virtual desktops on a headless server >using libvirt and KVM on the server and a SPICE client to access the >virtual desktop? Is there a standard way of doing this? > >I've seen many fragments of information about how to do this but I >didn't come across a single guide

Lukasz Sokol wrote: > but have you considered a web-managed config-builder such as FreePBX? > Instead of building your dialplan from scratch ? I've never used FreePBX, but, after having looked at its website, I think I have a general understanding of what it can do. What I don't understand is how FreePBX answers my question about the Linksys SPA3102 being good for a mission

Can anybody comment on how to host virtual desktops on a headless server using libvirt and KVM on the server and a SPICE client to access the virtual desktop? Is there a standard way of doing this? I've seen many fragments of information about how to do this but I didn't come across a single guide describing the entire solution. Search engines also return a lot of information about

Hello *, I've rc3 on Debian Lenny compiled from source. $ wine --version wine-1.0-rc3 However I typoed that command by mistake: $ wine -version and wine went looking for -version.exe. The strange behavior is the output. Is the folloing normal? $ wine -version wine: Unhandled page fault on write access to 0x00452000 at address 0x7efa04f4 (thread 0019), starting debugger... Unhandled

I think you are mixing up answers and general advice. FreePBX was intended to get you over the dialplan creation hurdle (the biggest challenge for people new to Asterisk). In regards to the LinkSys they are compatible and you do find them in enterprises, but admins are trying to get rid of adapters/converters so if possible you may wish to invest in SIP devices directly instead of an adapter.

This is probably a really stupid question, but what happens if you have more memory allocated to domU''s than your physical RAM? Will that cause dom0 to crash? DomU''s to crash? Or just slow performance due to swap use on dom0? I ask this because we''ve got high availability clusters running domU''s, and I want to know how much memory is safe to allocate to

Hello all, I'm new here and I'm interested in building a small PBX with asterisk at home. I have one single PSTN line and ethernet cabling in place. I already have fairly decent PC that I can use (AMD FX 8350 16GB of RAM and RAID 10 SATA disks). I make and receive 10 calls a day on average. I want 4 IP phones connected to the ethernet network. When there is a incoming call, all

+pcc, who had some other ideas/patch out for improving memory usage of debug info +Reid, who's responsible for the windows/CodeView/PDB debug info which is motivating some of the ideas about changes to type emission So how does this relate, or not, to Peter's (pcc) work trying to reduce the DIE overhead during code gen? Are you folks chasing different memory bottlenecks? Are they both

On Feb 7, 2013, at 10:58 PM, Hal Finkel <hfinkel at anl.gov> wrote: >> As long as this is brainstorming time, I actually like the idea of an >> llvm.invariant intrinsic that the optimizers know to ignore. I like >> it for other purposes, but would happen to work for you as a >> temporary workaround. It could take one or two IR values (as >> metadata operands)

I have some ideas to allow the BitcodeReader to lazy-load debug info metadata, and wanted to air this on llvm-dev before getting too deep into the code. Motivation ========== Based on some analysis Mehdi ran (ping him for details), there are three (related) compile-time bottlenecks we're seeing with `-flto=thin -g`: a) Reading the large number of Metadata bitcode records in the global

----- Original Message ----- > From: "Andrew Trick" <atrick at apple.com> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "llvmdev at cs.uiuc.edu List" <llvmdev at cs.uiuc.edu>, "Michele Scandale" <michele.scandale at gmail.com> > Sent: Friday, February 8, 2013 1:52:55 PM > Subject: llvm.meta (was Rotated loop

> On Mar 22, 2016, at 8:04 PM, David Blaikie <dblaikie at gmail.com> wrote: > > +pcc, who had some other ideas/patch out for improving memory usage of debug info > +Reid, who's responsible for the windows/CodeView/PDB debug info which is motivating some of the ideas about changes to type emission > > So how does this relate, or not, to Peter's (pcc) work trying to

Hi! Some vnc clients has '-via ssh_gateway' option to simplify the setup of ssh port forwarding. Basically the option implements the following 3 steps: 1. Find local port available for listening. 2. Fork/exec ssh -L found_port:vnc_host:vnc_port ssh_gateway sleep some_delay 3. Connect to the found_port Although convenient the setup has its problems. First, it exposes the remote vnc

On Thu, Dec 06, 2018 at 09:39:54AM -0500, Frediano Ziglio wrote: > > > > On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote: > > > > > > > qxl surfaces (used for framebuffers and gem objects) can live in both > > > > VRAM and PRIV ttm domains. Update placement setup to include both. Put > > > > PRIV first in the list so it

Setting spice display if we know the libvirt guest doesn't have QXL capabilities will only make the guest slower for the user. Fallback to VNC in such a case. A typical use case is when v2v-ing a windows guest without having the windows QXL driver at hand. --- v2v/output_libvirt.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/v2v/output_libvirt.ml

Setting spice display if we know the libvirt guest doesn't have QXL capabilities will only make the guest slower for the user. Fallback to VNC in such a case. A typical use case is when v2v-ing a windows guest without having the windows QXL driver at hand. --- v2v/output_libvirt.ml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/v2v/output_libvirt.ml

On Thu, Dec 06, 2018 at 05:55:58AM -0500, Frediano Ziglio wrote: > > > qxl surfaces (used for framebuffers and gem objects) can live in both > > VRAM and PRIV ttm domains. Update placement setup to include both. Put > > PRIV first in the list so it is preferred, so VRAM will have more room > > for objects which must be allocated there. > > > >

On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote: > > > > Just use qxl_num_crtc directly everywhere instead of using > > qdev->monitors_config->max_allowed. Drops pointless indirection > > and also is less confusing. > > > > To me is MORE confusing, why comparing number of something with > another number? Previously code was comparing

On Thu, Dec 06, 2018 at 07:53:10AM -0500, Frediano Ziglio wrote: > > > > On Thu, Dec 06, 2018 at 05:59:25AM -0500, Frediano Ziglio wrote: > > > > > > > > Just use qxl_num_crtc directly everywhere instead of using > > > > qdev->monitors_config->max_allowed. Drops pointless indirection > > > > and also is less confusing. > >