similar to: Xen-3.2.1 VT-d Support (NOT SURE WHETHER IT''S A BUG OR ...)

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to

This is the error I get while building Xen-3.2.1 when I do a make =============================================== make[2]: Entering directory `/usr/src/xen-3.2.1/tools/check'' LIBXENAPI_BINDINGS=n ACM_SECURITY=n ./chk build Xen CHECK-BUILD Fri Jul 18 11:36:34 IST 2008 Checking check_crypto_lib: OK Checking check_curl: unused, OK Checking check_openssl_devel: *** Check for openssl

On Xen-3.3.0, domain0 Megaraid SAS (SAS 1068 controller) driver is not loading correctly if vtd support in Xen is enabled. It fails at the point of initializing firmware. I wasn''t seeing this error with Xen-3.2.2-rc3 (Unstable version), though with vtd disabled in Xen-3.3.0, it is working. Looks like a degrade problem. Any clues? Thx, Venkat

I was following an email chain in the xen mailing list on HVM hypercalls on grant tables and the email chain link is below http://lists.xensource.com/archives/html/xen-devel/2007-03/msg00688.html This link says that we need not required hypercalls to share memory b/w HVM''s. But as far as my understanding of sharing memory is concerned, I think the memory is shared using grant table

Hi there, I have a Dell T3400 Workstation with CentOS5.1 as dom0. I have hidden a network interface in dom0 to pass it to domU. The domU can come up with the NIC when it''s OS is CentOS5.1 or RHEL5. But when it comes to RedHat4.5 , the NIC can not be found. As I type the command "lspci" in RHEL4.5 domU, it returned: pcilib: Cannot open /proc/bus/pci

I think we need this feature at least for debugging purpose, right? Or, do we already have this feature? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven''t the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I am trying to create a para-virtualized guest with the same kernel image and initrd image as dom0. The configuration is below ================================================================================ kernel = "/boot/vmlinuz-2.6.21.7-3.fc8xen" ramdisk = "/boot/initrd-2.6.21.7-3.fc8xen.img" memory = 428 name = "fedora.fc8" vif = [ '''' ] dhcp =

The patch moves the struct IO_APIC_route_entry to a common place. This allows us to share the struct with iosapic. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

The patch makes some pci access functions architecture independent. It only moves the 2 functions from xen/arch/x86/pci.c to xen/drivers/pci/pci.c. Thanks, -- Dexuan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Will lustre-1.5.95 build with 2.6.18-vanilla kernel? Which_patch doesn''t contain this kernel but I could see them in the series files. Do somebody have experience in building the same? I tried to do it but lot of errors after applying the patches in 2.6.18-vanilla series. Thanks, Venkat

Hi all, This is our weekly test report for Xen-unstable tree. No new issue found; P1 bug #1339 still blocks our save/restore related cases. Old Bugs: ===================================================================== 1. TSC not accurate in Windows HVM. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1291 2. SMP 32e RHEL5.1 timer would be slow,if under working pressure.

hi, I just tried the tip of the xen-unstable branch. It looks that the Xen supports 64bit BARs now? Thanks, Neo -- I would remember that if researchers were not ambitious probably today we haven''t the technology we are using! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I tried latest xen and linux-xen staging tree, but failed to run HVM domain on x86-64 environment. domU creation is OK. However the weird thing is not HVM domain itself. Instead system crashed on dom0 context. I saw once with some stack dump that xen''s page fault handler is executed on a dom0''s stack which then causes nested page fault due to unable to fetch vcpu pointer.

The datasheet is available at http://download.intel.com/design/network/datashts/82599_datasheet.pdf See 'Table 9.7. VF PCIe Configuration Space' of the datasheet, the PCI Express Capability Structure of the VF of Intel 82599 10GbE Controller looks trivial, e.g., the PCI Express Capabilities Register is 0, so the Capability Version is 0 and pt_pcie_size_init() would fail. We should not

In x64 SMP Vista HVM guest (vcpus=2 in the configuration file), the wall clock time is 50% slower than that in the real world. The attached patch fixes the issue. -- Dexuan Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Currently, Xen does not support injecting an NMI to HVM guest OS. Adding this feature is necessary for those softwares which depend on NMI to function correctly, such as KDB and oprofile. The attached patch allows NMI to be injected to guest OS in NMIP capable platforms. It also enables to queue an NMI and then inject it as soon as possible. Signed-off-by: Haitao Shan

The PCI_EXP_TYPE_PCI_BRIDGE should be PCI_EXP_FLAGS_TYPE here. Also a tiny fix to the python comment. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Changeset 15046:e527b4ff1948 breaks 32-bit HVM guest: when req->size is 4, "1UL << 32" returns 1 in IA32 system, so the mask becomes 0 wrongly. The attached patch fixes this by using 64-bit left-shift. Signed-off-by: Dexuan Cui <dexuan.cui@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hi, all, The attached patches try to improve the current FLR logic. The idea is: removing the FLR logic from hypervisor and adding the improved logic in Control Panel. The current FLR logic in hypervisor has some issues: 1) Dstate transition is not guaranteed to properly clear the device state; 2) the current code for PCIe FLR is actually buggy: PCI_EXP_DEVSTA_TRPND doesn''t mean the

This adds a boolean boot parameter to xen to allow reserved memory regions to be added to the iommu mappings for dom0. The parameter is "iommu_include_reserved" and is off by default. A warning is also traced when incorrect RMRR to system memory map values are detected. This is being added to address some incorrect BIOS''s that do not report correctly the requied reserved memory