similar to: xen acpi cpufreq driver

Dom0 uses this hypercall to pass ACPI information to Xen. It is not very uncommon for more cpus to be listed in the ACPI tables than are present on the system, particularly on systems with a common BIOS for a 2 and 4 socket server varients. As Dom0 does not control the number of entries in the ACPI tables, and is required to pass everything it finds to Xen, reduce the ERR to an INFO.

Hey guys, I am posting this again....because i didnt get any replay. Please I am doing my thesis and I am stack installing a guest machine from Yocto, a unix like machine. It boots successfully on the same host without xen. thank you again, Nas On Tue, Jun 4, 2013 at 5:37 PM, nesredin mahmud <nasmitlinux@gmail.com>wrote: > hello everyone, > > I am experiencing DomU booting

Hello Wei, On Sun, Jun 9, 2013 at 1:26 PM, Wei Liu <wei.liu2@citrix.com> wrote: > On Sun, Jun 09, 2013 at 11:58:26AM +0200, nesredin mahmud wrote: > > Hey guys, > > > > I am posting this again....because i didnt get any replay. Please I am > > doing my thesis and I am stack installing a guest machine from Yocto, a > > unix like machine. It boots

Hello there, I am using a Gigabyte H55M-UD2H (Intel H55-Chipset) together with a Core-i5-650. According to Gigabyte Support the Mainboard does support VT-d. Well, actually support says, that VT-d does work on Windows-7 in XP-Mode. They do not test and support Linux though. Did anybody here have success using VT-d on any H55-Board? Perhaps it is some misconfiguration on my side. I tried a

From: Christian Borntraeger <borntraeger at de.ibm.com> From: Carsten Otte <cotte at de.ibm.com> This patch adds functionality to detect if the kernel runs under the KVM hypervisor. A macro MACHINE_IS_KVM is exported for device drivers. This allows drivers to skip device detection if the systems runs non-virtualized. We also define a preferred console to avoid having the ttyS0, which

From: Christian Borntraeger <borntraeger at de.ibm.com> From: Carsten Otte <cotte at de.ibm.com> This patch adds functionality to detect if the kernel runs under the KVM hypervisor. A macro MACHINE_IS_KVM is exported for device drivers. This allows drivers to skip device detection if the systems runs non-virtualized. We also define a preferred console to avoid having the ttyS0, which

I''ve got a new system with Dual Quad Core Intel E5520 processors and Intel 82576 NICs built on the motherboard (this is a Supermicro Nehalem based blade). I''m running Xen 3.4.2, but I''ve also tried 3.4.1 and had the same problem. Dom0''s network works flawlessly, but the DomU systems all have network issues. Whenever they transmit large packets, it is as if

Hi, I installed Xen 4.0.1 from source on Debian 5.0.8 and when boot my computer hardware reboots at like "Scrubbing Free RAM". I tryed to find some information here but none was helpfull to me. Anyone? I have 4GB memory and a AMD Turion II X2 M500 (

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

Hi everyone, When I set CONFIG_ACPI_PROCESSOR, CONFIG_CPU_IDLE and CONFIG_INTEL_IDLE to y then I cannot boot Xen; there is a crash. If I turn CONFIG_INTEL_IDLE off then the boot goes well and, after dom0 has booted, xenpm works and gives some sane output, see below. I have tested this with kernels 3.2 to 3.4.6. Is it impossible to use INTEL_IDLE with Xen? If this is a known issue then maybe

Hi, I have a Dell T710 with 4 X 10G ethernet interfaces (2 X Dual port Intel 82599 cards). It is running FreeBSD RELENG_8 last updated on July 13. What I see is packet loss (0 - 40%) on IPv6 packets in vlans, when the machine is not the originator of the packets. Let me try to describe a little more. If a neigbouring machine ping6 it, there will be packet loss. If it act as a router for ipv6,

Dear all, here is the result of R.Version(): > R.Version() $platform [1] "powerpc-apple-darwin8.6.0" $arch [1] "powerpc" $os [1] "darwin8.6.0" $system [1] "powerpc, darwin8.6.0" $status [1] "" $major [1] "2" $minor [1] "3.1" $year [1] "2006" $month [1] "06" $day [1] "01" $`svn rev`

On Mon, 31 Jul 2023 09:25:12 +0800, "zhanghao1" <zhanghao1 at kylinos.cn> wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the

Hello, I have some diagnostic Info for you. Tried to get xen-4.0.1 working on another node of my cluster. Only difference: Newer revision of the Hardware. Exactly same Software Stack. Stack: Ubuntu Lucid 64bit, xen-4.0.1 from Source, selfbuilt linux-2.6.32.27 from xen/stable-2.6.32.x Nodes working: HP DL380G5 16GB (Intel X5460) Node not working: HP DL380G6 16GB (Intel X5550) Effect: Xen

I would also like to help as well. As KMacy knows before i asked a lot of questions for T2 types of servers but unfortunately i have no more access to those kind of hardware as well. I;m willing to participate if a team will be formated.

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU:

Hi-- On 7/30/23 18:25, zhanghao1 wrote: > A new virtio pci driver is added for listening to vcpus > inside guest. Each vcpu creates a corresponding thread to > periodically send data to qemu's back-end watchdog device. > If a vCPU is in the stall state, data cannot be sent to > back-end virtio device. As a result, the back-end device > can detect that the guest is in the

My system is a dual Xeon E5540 (Nehalem) HP Proliant DL380G6. When switching between Xen 4.0.2-rc1-pre and Xen 4.1-unstable I noticed that the NUMA info as shown by the Xen ''u'' debug-key is different. More specifically, the CPU to node mapping is alternating for 4.0.2 and grouped sequentially for 4.1. This difference affects the allocation (wrt node/socket) of pinned VCPUs to the

Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16 (XEN) VBE/DDC methods: none; EDID transfer time: 1 seconds (XEN) EDID info not

Package: xen-hypervisor-3.4-amd64 Version: 3.4.2-2 Severity: critical Justification: breaks the whole system -- Dump: (XEN) Xen version 3.4 (Debian 3.4.2-29 (XEN) Command line: com1=115200,8n1 console=com1,vga loglvl=all guest_loglvl=all noreboot (XEN) Video information: (XEN) VGA is text mode 80x25, font 8x16