similar to: MMCFG Problem

Fixes made in version 2: 1) Use PML4[257] for ioremap of PCI mmcfg. As full 16-bit segment support would require 44-bits. Since each slot only has 39-bits, we support 2048 PCI segments for now. This can be easily expanded if deemed necessary in the future. 2) Integrated PCI mmcfg access with existing PCI config interface for x86_64. Use MMCFG interface if offset is greater than 256.

Forcibly enabling the MMCFG space on AMD Fam10 CPUs cannot be expected to work since with the firmware not being aware of the address range used it cannot possibly reserve the space in E820 or ACPI resources. Hence we need to manually insert the range into the E820 table, and enable the range only when the insertion actually works without conflict. Further, the actual enabling of the space is

Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/x86_64/mmconfig_64.c +++ b/xen/arch/x86/x86_64/mmconfig_64.c @@ -23,7 +23,7 @@ struct mmcfg_virt { char __iomem *virt; }; static struct mmcfg_virt *pci_mmcfg_virt; -static int __initdata mmcfg_pci_segment_shift; +static unsigned int mmcfg_pci_segment_shift; static char __iomem *get_virt(unsigned int seg, unsigned

Hi, First of all, thanks for your help. I have made some test with this results debian testing with xen 4.4 can run if we add mmcfg=0 as boot options to kernel boot parameters !!! Remember that with xen kernel <=4.0 works perfect without to add mmcfg=0 I have tried to install citrix xenserver 5.6 and works perfect (remember that this is xen 3 branch) Also we have tried to install xenserver

On Fri, 2014-09-05 at 13:39 +0200, trenta wrote: > Additional information: > http://lists.xen.org/archives/html/xen-devel/2013-09/msg00584.html This thread suggests that mmconfig might be the issue, in which case does adding "mmcfg=0" to your hypervisor command line help? I'd recommend continuing to pursue this upstream, there are far more experts on the low level aspect of

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

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)

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

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal After giving xen a shoot with the fresh lenny packages, an annoying bug comes up right after trying to boot into the new system. I'll provide further informations if needed. Please see serial debug output below and here http://plzk.de/xen-lenny (maxlines got extended for comfortable reading) XEN) Xen version 3.2-1

Hello, I''m using Xen 4.0.0 compiled from source with the 2.6.31.13 kernel that it pulls down on its own. I added support for the aacraid driver to the kernel using ''make menuconfig'' from the build-linux-2.6-pvops_x86_64 subdirectory, and then built and installed the whole thing using ''make install'' from the xen-4.0.0 directory. I compiled this

Package: xen-hypervisor-4.4-amd64 Version: 4.4.0-4 Severity: normal -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash

I'm trying to pass-through my VGA card to a guest session. I found: http://www.linux-kvm.org/page/How_to_assign_devices_with_VT-d_in_KVM - which is very frustrating because there's no date on the documentation. I suspect it's old. It does clearly say that you must have VT-d support for pci pass-through. It then goes on to say "Some work towards allowing this ["software

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I followed the instructions here: http://nixcraft.com/file-servers/14803-how-centos-5-pxe-linux-installation-server.html, along with a few other sources that were less successful, and I finally got a pxe boot going. I'm using CentOS 5.3 x86_64 media as the source. The server boots, but keeps hanging. Here is my boot line:

OK, here's the info Bastian asked for. Transcript: rob at thismachine:~$ dmesg Bootdata ok (command line is root=/dev/sda1 ro ) Linux version 2.6.18-5-amd64 (Debian 2.6.18.dfsg.1-13) (dannf at debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu May 31 23:51:05 UTC 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009c800 (usable)

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important On a machine with 2 dual-core Opterons and 16GB of memory, only about 3GB is detected by the hypervisor. Transcript: root at thismachine:~# xm dmesg Xen version 3.0.3-1 (Debian 3.0.3-0-2) (ultrotter at debian.org) (gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)) Fri Nov 3 00:21:27 CET 2006 Latest

Hi, I have problem installing or running domU OS (Windows XP or Redhat 7.3). The machine runs CentOS 4.4 X86_64, Xen-3.0.3. Paravirtual domU works without problem. The problem is that when I run command "xm create <config>", nothing would happen. hvmloader does not seem get started at all. I''ve tried installing both 64bit and 32bit vnc, sdl but did not see any

when I run dmesg PE2950 Dell Server I see the following line Linux version 2.6.18-92.1.6.el5 (mockbuild at builder15.centos.org) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)) #1 SMP Wed J un 25 13:45:47 EDT 2008 Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 0000000000100000 -

Hi, I'm geting this message from virt-manager. Server: SuperMicro X8SIL with INTEL X3440 Here is my logs /var/log/dmesg: Bootdata ok (command line is ro root=/dev/md2) Linux version 2.6.18-194.3.1.el5xen (mockbuild at builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:49:53 EDT 2010 BIOS-provided physical RAM map: Xen: 0000000000000000 -

I have a single VM (of 11) that has a recurring problem. This image has moved from machine to machine, with the problem following it. This image has been rebuilt from scratch, and the problem recurred. It would appear that there is something in the behaviour of this VM which causes it to crash and causes Xend to become unhappy. The problem presents as: Domain crashes, becomes zombie. xm

Package: xen-hypervisor-3.0.3-1-amd64 Version: 3.0.3-0-2 Severity: important about every 1 in 10 boots I am getting the following error: (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This seems to happen in the CPU detection