similar to: Bug#810070: XEN Hypervisor crashes/reboots at Startup after "Scrubbing Free Ram"

Hello, I'm looking for help figuring out why I am having problems with shutting down a machine. I have tested the machine using Fedora 19 and Ubuntu 12 Live CD's and both power down without issues. I added acpi.debug_level=1 to the grub boot as it was suggested to see more info about ACPI in the logs I found the following ACPI Errors in the /var/log/messages Oct 11

Hi, Am trying to build SMP kernel. Took kernel-2.6.18-194.src.rpm, extracted, rpmbuilded with SMP option. Successfully compile the new kernel and when using that kernel to boot up, following errors were shown up(highlighted in bold & red color): My kernel config file has ACPI and PCI configs enabled. Any pointers to what caused the problem are appreciated. ******************************

Ian Campbell <ijc at hellion.org.uk> writes: #Please boot with loglvl=all on the hypervisor command line for this too. No problem Ian, Here are some results with (now) the latest BIOS version 41. (was version 35) This is a fresh new install of Debian "Testing" non production server. Just wanted to run some test domU's. Changing USB ports, no effect. I even tried a different

Hi list, I've installed C7 1511 (kernel 3.10.x) on a skylake mother board with i3-6100. I know about skylake problems. For the iGPU I've used i915.preliminary_support and ok. Some days ago, I get different strange error on this machine. When screensaver starts or when monitor will be in energy saving, if I try to get access to the system I get different strange behaviour and can't

On Thu, 2014-05-15 at 11:01 +0100, Ian Campbell wrote: > Please can you also post Xen's own dmesg (from "xl dmesg"). Please boot with loglvl=all on the hypervisor command line for this too. Ian.

Hello, I have a server pfsense in bridge mode to function as transparent FW, the problem is that once I connect the pfsense between my router core and my core switch catalyst a few seconds begin to appear several messages like these: em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting em2: watchdog timeout - resetting And the connection falls

(copying xen-devel, full logs are at bugs.debian.org/748052, this is Debian Jessie, Xen 4.3.0 and Linux 3.13 Mike also reported that Debian Wheezy Xen 4.1.4 didn't work either, not clear which kernel that was with though, Wheezy's 3.2 or Jessie's 3.13) On Thu, 2014-05-15 at 10:11 -0700, Mike Egglestone wrote: > Here are some results with (now) the latest BIOS version 41. (was >

Hello, I just upgraded from Xen-3.3.1 to Xen-4.0.0. System is Gentoo, Hardware is DualCore AMD Athlon, 8GB RAM. The kernel was upgraded from OpenSUSE 2.6.27.29-0.1.1 to Gentoo-2.6.32-xen- r1. The first boot failed with an OOM error during kernel/initrd load, so I adjusted the dom0_mem option and had to increase it''s avalue from 256M to at least 400M until the dom0 could boot. At all

I have a 100MB internal lan. aastra's are wired. asterisk box is wired next to the switch. But look: sip show peers ........ 142/142 10.10.10.42 D A 5060 OK (137 ms) 144/144 10.10.10.44 D A 5060 OK (136 ms) 145/145 10.10.10.45 D A 5060 OK (168 ms) 150/150 10.10.10.50

hail, I have a soekris running an atom and 2GB RAM and ZFS using 7 drives, small capacity though, to test and study if I can make my home server this box and this way. It will be a simple server, three users tops. I followed the handbook and made the geli step on the disks: Geom name: label/zfs1.eli State: ACTIVE EncryptionAlgorithm: AES-XTS KeyLength: 128 Crypto: software UsedKey: 0 Flags:

Am 23.06.2020 10:07, schrieb Marek Greško: Hi > this is a correct response: > > From 62.156.246.57 (62.156.246.57) icmp_seq=1 Frag needed and DF set > (mtu = 1492) > > So PMTU discovery is working. No problem here. You got correct message > to lower the packet size from 62.156.246.57. This is probably the last > hop before your site. No, the last hop is 62.156.246.65:

Hello list, I have a problem with my new xen server wich can''t reach to start my linux hardware virtual machines which works on my old server without modifications. Here is my situation : On all xen servers (3), I use xen 3.2 for a Dom0 compiled with the linux kernel caming from http://xenbits.xensource.com/linux-2.6.18-xen.hg My 2 old xen servers are : Dual core Intel(R) Pentium(R) D

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

Hi there, I'm running an ibm xseries 345/dual Xeon 2.66GHz, 2.6.18-53.1.14.el5xen #1 SMP, and cat /proc/cpuinfo shows me only one processor. Apparently something strange happening with ACPI. What am I doing wrong? Thank you! (sorry for the cross post, didn't realize there was a virt list first time around!) Selected bits from dmesg: ------------------------- Using ACPI (MADT) for SMP

Hi there, I'm running an ibm xseries 345/dual Xeon 2.66GHz, 2.6.18-53.1.14.el5xen #1 SMP, and cat /proc/cpuinfo shows me only one processor. Apparently something strange happening with ACPI. What am I doing wrong? Thank you! Selected bits from dmesg: ------------------------- Using ACPI (MADT) for SMP configuration information SMP alternatives: switching to UP code ACPI: Core revision

What if you boot with other kernel? If you have the same result maybe BIOS update is required for your server?! >---------------------------------------------------------------------- > >Message: 1 >Date: Sat, 17 May 2008 14:51:45 -0700 >From: gen2 <gen2 at planetofidiots.com> >Subject: [CentOS-virt] xen kernel showing only one processor on SMP > machine

Am 23.06.2020 09:28, schrieb Marek Greško: Hi > if you need clampmss then it is highly probable there is a PMTU > discovery problem. The clampmss does not work for UDP. Is there a way to check if I have this problem? > I probably counted the size incorrectly. So you are able to ping with > size 1464 and not with 1466. How about trying same ping sizes from the > internet towards

https://bugs.freedesktop.org/show_bug.cgi?id=111853 Bug ID: 111853 Summary: nouveau kernel module won't load (not available) on Sony laptop with NVIDIA G86M [GeForce 8400M GT] ID: 10de:0426 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All)

Hi list, I have a problem with a new laptop (reproducable on other machines too) and the xen hypervisor. When the hypervisor gets booted with VESA mode 800x600 I see some messages and then the screen contents is switched into a pattern of vertical colored lines and never comes back. In text mode all works well, but later the pattern appears when the X servers starts. I disabled VTd in the bios

Add support for a new ACPI table that embeds other tables describing a platform's IOMMU topology. Currently the only supported base table is IORT. The VIOT contains an IORT with additional node types, that describe a virtio-iommu. Signed-off-by: Jean-Philippe Brucker <jean-philippe at linaro.org> --- drivers/acpi/Kconfig | 4 ++++ drivers/acpi/Makefile | 1 +