similar to: pt_pci_read_config offset issue

The OpRegion shouldn''t be mapped 1:1 because the address in the host can''t be used in the guest directly. This patch traps read and write access to the opregion of the Intel GPU config space (offset 0xfc). To work correctly this patch needs a change in hvmloader. HVMloader will allocate 2 pages for the OpRegion and write this address on the config space of the Intel GPU. Qemu

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

Whilst looking at the 3.61 isolinux.asm file I noticed that the code uses a spec buffer size of 13h for the initial BIOS call with the drive number passed in in DL. It then uses a spec buffer size of 13 when scanning drive numbers from FFh to 81h Line 291 is mov byte [spec_packet],13h Lines 576 to 577 are mov si,spec_packet mov byte [si],13

This patchset enable support for C1 mwait entry. [PATCH 1/3] dom0-C1-FFH.patch. It gets C1 information from ACPI table and pass it to Xen. [PATCH 2/3] add-idx-field.patch. This patch adds an idx field in the ''struct acpi_processor_cx''. It can simplify some coding lines. [PATCH 3/3] xen-C1-FFH.patch. It adds support for C1 FFH (mwait) entry. Meanwhile add timing for C1. The

# HG changeset patch # User Boris Ostrovsky <boris.ostrovsky@amd.com> # Date 1330642361 -3600 # Node ID 99df5c6b2964ceaa73651d7bc02fb1ae820f7691 # Parent a7bacdc5449a2f7bb9c35b2a1334b463fe9f29a9 x86: Use deep C states for off-lined CPUs Currently when a core is taken off-line it is placed in C1 state (unless MONITOR/MWAIT is used). This patch allows a core to go to deeper C states

Hi, everyone! I am working on xen-4.2.0 with spice remote connect. My host is Fedora 14 and guest is win7. I have installed spice package and now I can connect to guest by spice client. For better graphics experience, I want to try the VGA passthrough. With spice tool, I have to create a VM by xl command, and now I am wondering if it supports VGA passghrouth? If so, how should I test it ?

Could anyone summarize what the support status of cpu frequency changes is at present. I don''t seem to recall generic changes to the hpyervisor in that respect, but the linux tree has fairly extensive changes to the powernow-k8 driver (which would make sense to me only if all other cpufreq drivers are fully supported now, too). Thanks, Jan

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

There''re basically two methods to enter a given C-state: legacy (hlt + I/O read), and native(using mwait). MWAIT is always preferred when both underlying CPU and OS support, which is a more efficient way to conduct C-state transition. Xen PM relies on Dom0 to parse ACPI Cx/Px information, which involves one step to notify BIOS about a set of capabilities supported by OSPM. One capability

Is there something that I can put on a drive's boot sector so that when booted it just reboots, and that its partition information is also intact? My application need is stateless computing. The OS loads over the network with the help of pxelinux.0, but when 1000s of nodes reboot in parallel a few fail to boot. When PXE fails it boots the next device--in most cases this is the local HD.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

Userspace patches for the pci-passthrough functionality. The major updates since the last post are: - Loop to add passthrough devices in pc_init1 - Handle errors in read/write calls - Allow invocation without irq number for in-kernel irqchip Other than this, several small things were fixed according to review comments received last time.

I was reading the Wiki page here: http://wiki.xen.org/wiki/VTd_HowTo don''t know how updated it is, BUT at the top it said: -------------------- -------------------- -------------------- -------------------- -------------------- -------------------- _Xen 4.1 xl tools notes _ * Only devices with FLR capabilities are supported. * Passing through a PCI card without FLR capability

Current xen-linux (2.6.18) not include support for Cx MWAIT entry method. Back port from latest Linux kernel (already there since 2.6.23). Without this patch, _CST method couldn''t get C states with FFH address space type. Signed-off-by: Wei Gang <gang.wei@intel.com> Jimmy _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Hello. What about driver for my UPS? I have changed the powercom driver for myself, but I have made it not absolutely correctly. However, somehow this driver works. Now i have protocol spec for powercom BNT series and attach it to this email. It can be interesting to authors? -- ? ?????????, ??????? ??????? mailto:alex@reutman.ru JID: alex@reutman.ru ICQ: 5052225 -------------- next part

Just out of annoyance more than curiosity, but ever since I started using Xen 4.2-unstable rev-25467, every time I try to run "sudo xl create <domu_config_file>", or "sudo xl reboot", or "sudo xl destroy", it always gives me this message: "*xend is running, which prevents xl from working correctly. If you still want to force the execution of xl please

Good day to you, too. No worries about the delay. I understand how busy everyone is with SYSLINUX. Gladly, the project continues to develop and improve. With that said, thanks for today's flurry of activity regarding my reported problem. Impressively, the debug version of MEMDISK that you had directed me to use appears to have done the trick. Results below. command line:

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that

I am submitting the patch which supports more Capability Structures and Device Specific Registers for passthrough device. In Xen 3.3 unstable, qemu-dm supports Configuration Header, MSI Capability Structure, and MSI-X Capability Structure. But qemu-dm does not support PCI Express Capability Structure, Device Specific Registers, etc (writing them is ignored). To support various I/O devices, I

Sensei H. Peter Anvin, I have successfully modified/enhanced memdisk so that one can chainload a local operating system after running diskless FreeDOS. I would like your advice regarding the appropriate interface for invoking this functionality. In addition, I would like to know what steps to take so that you feel comfortable considering including this in the standard syslinux distribution.