similar to: S3 testing, etc

Hi, I''ve still have problems with ACPI(?) on Xen. After some system startup or resume CPU temperature goes high although all domUs (and dom0) are idle. On "good" system startup it is about 50-55C, on "bad" - above 67C (most time above 70C). I''ve noticed difference in C-states repored by Xen (attached files). On "bad" startups in addition suspend

Hi. I am using xen 4.2.2, the system runs okay. But when I suspend it, it does so, but crashes on trying to resume. Here is lsmod output: Module Size Used by xen_pciback 52011 0 xen_netback 27468 0 xen_blkback 26998 0 xen_gntalloc 13144 0 xen_gntdev 17403 1 xen_evtchn 13132 1 xenfs 12985 1 xen_privcmd 13177 5 xenfs parport_pc 28152 0 ppdev 17073 0 rfcomm 42641 12 bnep 18036 2 ext2 72837 1

Hi. I am using xen 4.2.2, the system runs okay. But when I suspend it, it does so, but crashes on trying to resume. Here is lsmod output: Module Size Used by xen_pciback 52011 0 xen_netback 27468 0 xen_blkback 26998 0 xen_gntalloc 13144 0 xen_gntdev 17403 1 xen_evtchn 13132 1 xenfs 12985 1 xen_privcmd 13177 5 xenfs parport_pc 28152 0 ppdev 17073 0 rfcomm 42641 12 bnep 18036 2 ext2 72837 1

When in SYS_STATE_suspend, and going through the cpu_disable_scheduler path, save a copy of the current cpu affinity, and mark a flag to restore it later. Later, in the resume process, when enabling nonboot cpus restore these affinities. v2: Fix formatting problems. remove early return in cpu_disable_scheduler() path. v3: Fix remaining errant tab Move restore_vcpu_affinity() to thaw_domains(),

Fix the polling section of the hvc driver to use the global "last_hvc" variable, rather than the ttys. With this change debugging a xen dom0 kernel is possible via the following kernel parameter: kgdboc=hvc0 Signed-off-by: Ben Guthro <Benjamin.Guthro@citrix.com> diff --git a/drivers/tty/hvc/hvc_console.c b/drivers/tty/hvc/hvc_console.c index 2d691eb..3750e74 100644 ---

Hi all, I''m having difficulty getting VT-d to work correctly with a new Supermicro MBD-X10SAE-O in QubesOS <http://qubes-os.org/trac>, and I''m hoping someone here might be able to help me (or at least shed some light on my situation). A Qubes developer suggested I contact this list. Here''s my HCL post from the qubes-users group

Hello, I''m facing a rather strange problem with the netback interface. My setup involves a netvm, which has some physical network interfaces assigned, and a client VM where a net front is running (exposed as eth0) and which is connected to that netvm (via vif42.0 interface, as seen in the netvm on the dumps below). Now, the netvm has two physical network interfaces assigned: 1) A

v2: - fix compile issues if no CONFIG_SMP, Konrad Rzeszutek Wilk - move inc_irq_stat after irq_work_run These 2 patches fixed the "perf top" soft lockups under Xen reported by Steven at: https://lkml.org/lkml/2012/2/9/506 Both Steven and I tested it and "perf top" works well now. The soft lockup code path is: __irq_work_queue arch_irq_work_raise

After an S3 host resume, I''m seeing: [48002.772629] ACPI: Low-level resume complete [48002.772802] PM: Restoring platform NVS memory [48002.776143] xen_acpi_processor: Uploading Xen processor PM info [48002.776691] ------------[ cut here ]------------ [48002.776712] WARNING: CPU: 0 PID: 10235 at drivers/base/syscore.c:104 syscore_resume+0x9a/0xe0() [48002.776751] Interrupts enabled after

Hey Linus, I am heading out for a week of vacation but would hate to have missed the merge window. Hence sending it out early in anticipation that you will release v3.9 on Sunday. With that said, please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.10-rc0-tag which has just a couple of features and mostly bug-fixes. Here is the

https://bugs.freedesktop.org/show_bug.cgi?id=95193 Bug ID: 95193 Summary: Nouveau not working with Quadro K2200 (NV117) and Debian Wheezy Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: blocker Priority: medium Component:

Pointer to structure array is assumed not NULL by default. It has the consequence to raise a kernel panic when it's not the case. Basically, running at least a RTX2080TI on Xen makes a bad mmio error which causes having 'mthd' pointer to be NULL in 'channv50.c'. From the code, it's assumed to be not NULL by accessing directly 'mthd->data[0]' which is the reason

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

flight 13925 xen-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13925/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail REGR. vs. 13922 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-sedf-pin 10 guest-saverestore fail

Dear Xen Developers, I installed Qubes OS using Xen Hypevisor on my PC which contains an Intel i5 750 Processor. In BIOS the VT-d support is enabled, but while booting my system xen crashes. I already tried the boot parameters iommu=pv and iommu=workaround_bios_bug, but without any improvement. The message xen shows when crashed is: Panic on CPU 0 fatal page fault error code [0000]

For about the past week (perhaps a bit longer) I have been unable to use an automated script to build xen-unstable on a 32 bit machine. The build continues to ask about the following build parameter: I2O_EXT_ADAPTEC_DMA64 Choosing the default (Y) allows the build to continue to completion. After a little research, it looks like this parameter was pulled out of linux-defconfig_xen_x86_32 in

Hi Fr?d?ric, It appears Ben made his own version of this patch (probably based on the one you added to the kernel bz), and it's already upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.6-rc2&id=0e6176c6d286316e9431b4f695940cfac4ffe6c2 Cheers, -ilia On Thu, Feb 20, 2020 at 12:19 PM Fr?d?ric Pierret <frederic.pierret at qubes-os.org>

Hi all, I have a Nvidia GeForce GTX 680 that I''d like to use in a Xen configuration. I don''t care if it''s used by dom0 or by a linux domU guest, either would be OK for my purposes. Since getting this card, I''ve experimented with Linux 3.4.6 and Xen 4.1.2 and determined the following: 1. The card works correctly under a linux kernel without Xen running. 2.

Hello, I thinking about using PCI passthrough to dedicated a domU as firewall. I understand PCI passthrough concept. When done, my domU will see network card and the dom0 won''t any more. So I''ll be able to filter all trafic from outside, since it will go through network domU. Then, how will I be able to connect other domU (and maybe dom0) to the network domU ? In a normal way,

Dear Ben Skeggs, Please find attached a patch solving a blocking issue I encountered: https://bugzilla.kernel.org/show_bug.cgi?id=206299 Basically, running at least a RTX2080TI on Xen makes a bad mmio error which causes having 'mthd' pointer to be NULL in 'channv50.c'. From the code, it's assumed to be not NULL by accessing directly 'mthd->data[0]' which is the