search for: accell

On 21. Aug 2020, at 11:20, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Fri, Aug 21, 2020 at 11:19:14AM +0200, Jan Walzer wrote: >> Hi Daniel, >>> On 21. Aug 2020, at 11:07, Daniel P. Berrangé <berrange@redhat.com> wrote: >>> On Fri, Aug 21, 2020 at 11:00:27AM +0200, Jan Walzer wrote: >>>> On 21. Aug 2020, at 10:38, Daniel P. Berrangé

Hi List I've experienced some problems with rsync. I'm backuping a complete machine's rootdirectory. After completion I see in the log of the output, that rsync links some files which are surely *not* the same on the source System. Or well, it says, that it makes links, using the filename1 => filename2 notation. On the source System this files are not the same and some files are

The latter is a better way to disable the qemu display output as we need to, without enabling extra devices (which are disabled already, anyway). Also, related to the change above, ban the -display parameter from the ones that can be supplied by the user. --- configure.ac | 8 ++++---- src/launch-direct.c | 12 ++++++++---- src/launch.c | 1 + 3 files changed, 13 insertions(+), 8

Previously we used (on arm): -M virt -machine accel=... After this change, we use: -machine virt,accel=... On x86 there is no change. The -M option is an abbreviation for -machine, and we can combine the two options together. (Qemu combines the two options internally, but it's more predictable if we do it ourselves). Upstream qemu has supported the -machine option for over 5 years, and in

I've done some work getting the patches from http://starcraft-wine.sourceforge.net/ working with CVS wine. Using the patch I'm including, starcraft works perfectly on my machine, run as root using DGA on a 640x480 XF86 layout. In particular the changes to event.c enable the mouse and keyboard with DGA. The changes to input.c make the mouse acceleration work the same in all directions.

Hi Daniel, > On 21. Aug 2020, at 11:07, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Fri, Aug 21, 2020 at 11:00:27AM +0200, Jan Walzer wrote: >> On 21. Aug 2020, at 10:38, Daniel P. Berrangé <berrange@redhat.com> wrote: >>> On Thu, Aug 20, 2020 at 08:11:30PM +0200, Jan Walzer wrote: >>>> Hi Lists, >>>> >>>> I currently

xf86-input-libinput 1.3.0 is now available. The main feature in this version is support for the new 'custom' pointer acceleration profile in libinput 1.23.0. This acceleration profile is quite flexible, so it is exposed via several properties: - "libinput Accel Custom Fallback Points" and "libinput Accel Custom Fallback Step" - "libinput Accel Custom Motion

On Fri, Aug 21, 2020 at 01:38:23PM +0200, Jan Walzer wrote: > On 21. Aug 2020, at 11:20, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Fri, Aug 21, 2020 at 11:19:14AM +0200, Jan Walzer wrote: > >> Hi Daniel, > >>> On 21. Aug 2020, at 11:07, Daniel P. Berrangé <berrange@redhat.com> wrote: > >>> On Fri, Aug 21, 2020 at 11:00:27AM +0200,

Hi there, I have used qemu to install FreeBSD 9.2 release, and i can boot it fine with: $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img I then made virsh aware of my brand new VM (see attached XML), but when i run it via virsh, It hangs after the bootloader whith this message: Booting... CPU doesn't support long mode From the log, here is the generated qemu command:

Hello, Been wondering why I could never resume from s2r. That's because I always use 3D accel (compiz, cairo-dock). I have tested each Arch kernel releases, hoping each time to get s2r to work. Tired of this, I decided to use 3.4 LTS... 3.4.50 ... And guess what ? I could resume from suspend to RAM 100% of the time !!! I know it may be a hard work for you, but suspend to RAM while using 3D

On Thu, Nov 14, 2013 at 12:48:51PM +1300, Christian Gagneraud wrote: > On 14/11/13 10:53, Christian Gagneraud wrote: > >Hi there, > > > >I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > >with: > >$ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > > >I then made virsh aware of my brand new VM (see attached XML),

On 14/11/13 10:53, Christian Gagneraud wrote: > Hi there, > > I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > with: > $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > I then made virsh aware of my brand new VM (see attached XML), but when > i run it via virsh, It hangs after the bootloader whith this message: > Booting... >

all, On latest tip, following symbols are unresolved when inserting modules xen_balloon: Unknown symbol totalhigh_pages xen_vnif: Unknown symbol netfront_accelerator_call_resume xen_vnif: Unknown symbol netfront_accelerator_call_suspend_cancel xen_vnif: Unknown symbol netfront_accelerator_call_stop_napi_irq xen_vnif: Unknown symbol balloon_update_driver_allowance xen_vnif: Unknown symbol

Hello, After bisection I found the first bad commit : 5e120f6e4b3f35b741c5445dfc755f50128c3c44 is the first bad commit commit 5e120f6e4b3f35b741c5445dfc755f50128c3c44 Author: Ben Skeggs <bskeggs at redhat.com> Date: Mon Apr 30 13:55:29 2012 +1000 drm/nouveau/fence: convert to exec engine, and improve channel sync Now have a somewhat simpler semaphore sync implementation for

13:57 < soko> hello. i am getting an error on launch when i set-hv to an arm system. the error appears to be caused by no default machine. here is a log https://pastebin.com/CUBcnG44 13:59 < soko> the default hv works (launch, mount, etc) but fails to emulate (sh, command, etc) the binaries on the fs 14:17 < soko> if i upload qemu-arm-static and then command it

On 21. Aug 2020, at 10:38, Daniel P. Berrangé <berrange@redhat.com> wrote: > On Thu, Aug 20, 2020 at 08:11:30PM +0200, Jan Walzer wrote: >> Hi Lists, >> >> I currently have the issue of wanting to use emu-system-x86_64 on a ppc64le platform. >> >> It is imperative to pass the "-accel tcg,thread=multi” parameter to qemu >> when starting an

https://bugs.freedesktop.org/show_bug.cgi?id=50375 Bug #: 50375 Summary: NV11: KMS/fbcon accel failing after scrolling/tty switch Classification: Unclassified Product: xorg Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority:

OK I downloaded and compiled Mesa 3.4.1, the gears demo runs at about 140 fps so thats not looking like real hw accel ;) I downloaded a prebuilt gears from the dri webpage and I get 1300 fps even after I uninstalled my Mesa because it did not work together with Quake3 (always told me no hardware accel available) So I reverted to the libGL.so that came with my X4.0.2 binary tars. My glide3 is

On 11/13/2013 02:53 PM, Christian Gagneraud wrote: > Hi there, > > I have used qemu to install FreeBSD 9.2 release, and i can boot it fine > with: > $ qemu-system-x86_64 -hda images/FreeBSD-9.2-RELEASE-amd64.img > > I then made virsh aware of my brand new VM (see attached XML), but when > i run it via virsh, It hangs after the bootloader whith this message: >

On Wed, Sep 17, 2014 at 07:59:03PM +0530, Priyanka Ranjan wrote: > libguestfs: command: run: /usr/libexec/qemu-kvm > libguestfs: command: run: \ -nographic > libguestfs: command: run: \ -machine accel=kvm:tcg > libguestfs: command: run: \ -device ? > libguestfs: error: /usr/libexec/qemu-kvm exited with error status 1, see > debug messages above > libguestfs: trace: launch = -1