search for: x86_energy_perf_polici

On Fri, May 12, 2017 at 8:18 AM, ken <gebser at mousecar.com> wrote: > Currently I don't actually need more speed. This is already a fairly peppy > laptop... like right now the load is about 2%. If it was any lower, I could > almost turn this machine off and still run everything. :) Ah but > seriously, I'd rather have the speed cranked down and save the battery. >

I have a physical SLES11SP2/OES11 system that I''ve converted to a domU. It''s boots ok as an HVM, but when I try to boot as a PV it gets stuck. I have the kernel-xen packages installed and confident the menu.lst is correct. If I look at xm console for the VM I get the output below: Any ideas? Thanks James [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000]

On Tue, Oct 24, 2017 at 3:09 PM, Karl Johnson <karljohnson.it at gmail.com> wrote: > On Tue, Oct 24, 2017 at 3:36 AM, Akemi Yagi <amyagi at gmail.com> wrote: > >> On Mon, Oct 23, 2017 at 11:08 PM, Akemi Yagi <amyagi at gmail.com> wrote: >> >>> On Mon, Oct 23, 2017 at 12:57 PM, Karl Johnson <karljohnson.it at gmail.com >>> > wrote:

I thought I'd chime in and say that I'm seeing the same kernel-plus boot failure that Shaun Reitan reported earlier. Is there likely to be another build 3.10 kernel build coming down the pipeline that might fix this issue? Here's the output of my failed PV domU boot: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000]

On Tue, Oct 24, 2017 at 3:36 AM, Akemi Yagi <amyagi at gmail.com> wrote: > On Mon, Oct 23, 2017 at 11:08 PM, Akemi Yagi <amyagi at gmail.com> wrote: > >> On Mon, Oct 23, 2017 at 12:57 PM, Karl Johnson <karljohnson.it at gmail.com> >> wrote: >> >>> On Sat, May 20, 2017 at 8:30 PM, Sarah Newman <srn at prgmr.com> wrote: >>>

Hi I''m putting together a Dom0 and three DomU (all Gentoo) with kernel 3.5.7 and Xen 4.1.1. Each Dom has it''s own md (md0 for Dom0, md1 for Dom1 etc). Dom0 works fine so far, however, I''m stuck trying to create DomUs. It appears the xvda1 device on DomU is not created or accessible: Parsing config file dom1 domainbuilder: detail: xc_dom_allocate:

I'm trying to set-up a ContOS 7 DomU server. I have used the PXE set-up images like I normally would for earlier versions of CentOS. Here is my config file:- name      = "centos7" memory    = 2048 disk      = ['phy:/dev/xen6/centos7,xvda,w' ] vif = [ 'mac=xx:xx:xx:xx:xx:xx' ] kernel    = "/root/xen/centos7-64/vmlinuz" ramdisk   =

On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Severity: grave Hello, I am trying to install the XEN Hypervisor on a Debian Jessie Server. When I am booting without the Hypervisor, everything works fine, but when I am Booting WITH the XEN-Hypervisor, then System crashes / reboots after the "Scrubbing Free RAM" Message without any Error-message, just a blank screen.

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Hi, I have been trying to get NIC PCI Passthrough to work on Xen 4.3.0 and have hit a wall. On attaching the NIC the domU network driver (igb) crashes. I followed the Xen PCI Passthrough wiki http://wiki.xen.org/wiki/Xen_PCI_Passthrough and am using dynamic device assignment with xl. Trying to passthrough this device: root@dom0:~# lspci|grep 82575EB 05:00.1 Ethernet controller: Intel

https://bugs.freedesktop.org/show_bug.cgi?id=83271 Priority: medium Bug ID: 83271 Assignee: nouveau at lists.freedesktop.org Summary: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

https://bugs.freedesktop.org/show_bug.cgi?id=76818 Priority: medium Bug ID: 76818 Assignee: nouveau at lists.freedesktop.org Summary: Xorg EQ overflowing lock up QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: max.snow at 4mation.com.au

Hi there, with the latest snapshot of linus tree, i see a stack trace and my system does not start X! Maybe someone finds this useful! (3.11 is working like a charm) BUG: unable to handle kernel NULL pointer dereference at (null) IP: [< (null)>] (null) PGD 24eaa0067 PUD 24e7ac067 PMD 0 Oops: 0010 [#1] PREEMPT SMP Modules linked in: bnep snd_hda_codec_hdmi

Hi, I have an Optimus-enabled laptop with a GTX 1060m. I never got it to fully work with Nouveau even after Pascal support was added. I need to run the kernel with nouveau.runpm=0 to get it to work. Unfortunately without proper power mangement support, my laptop will run out of battery after about 1h30, so I'd love to get Optimus working. What I can see is that when the extra GPU is not in

My kernel crashed for some other reason, and now I can''t mount my btrfs filesystem. I don''t care about the data, it''s backed up. I''ll compile a 3.5 kernel, but is there any info you''d like off that filesystem to see why btrfs is crashing on mount? Marc [ 313.152857] device label btrfs_pool1 devid 1 transid 20769 /dev/mapper/disk1 [ 313.171318]

dmesg output after a resume from a suspend. the device in question was /dev/sdb mounted on /home. after a device failure to resume properly, the link is then reset by the kernel but comes back as /dev/sde. /dev/sdb disappeared entirely, and is now referred to as sde. attempted to remount rw of sde, seemed to succeed, mount/mtab said that it was rw now but i couldn''t write to the volume

Hi, I took this issue to the Fedora forum initially, but no-one there has been able to offer any guidance, so I have decided to come to the nouveau community directly. I was running a KDE desktop under Fedora 21 successfully, including the ability to use a direct text login on an older card (GXT 560 Ti) with an entirely stock Fedora, fully updated. I simply replaced the old card with an