similar to: ioemu: make various functions in i386-dm/helper2.c static

Nicely terminate the device model script, to let it properly clean resources. Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -u b/tools/python/xen/xend/image.py b/tools/python/xen/xend/image.py --- b/tools/python/xen/xend/image.py Fri Jan 18 11:53:23 2008 +0000 +++ b/tools/python/xen/xend/image.py Fri Jan 18 12:42:11 2008 +0000 @@ -325,7 +325,7 @@ return

Hi all, this is the long awaited patch series to add xen device model support in qemu; the main author is Anthony Perard. Developing this series we tried to come up with the cleanest possible solution from the qemu point of view, limiting the amount of changes to common code as much as possible. The end result still requires a couple of hooks in piix_pci but overall the impact should be very

Extend the VMX intercept mechanism to include mmio as well as portio. Signed-off-by: Yunhong Jiang <yunhong.jiang@intel.com> Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r febfcd0a1a0a -r 9a43d5c12b95 xen/include/asm-x86/vmx_platform.h --- a/xen/include/asm-x86/vmx_platform.h Thu Jun 30 03:20:48 2005 +++

Hi, I've written some helper functions which are used by another function (called func()). When func() is sourced I dont want the helper function to be seen in the global namespace (as shown by ls()). Currently what I have done is: func <- function() { helper1 <- function() { ... } helper2 <- function() { ... } # some code } Is there anyway to take the functions

QEMU fixes - VMX domain owns 0xcxxxx. - guard the fprintf with a log level check Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- 1.1/tools/ioemu/hw/pc.c 2005-05-19 15:04:52 -07:00 +++ edited/tools/ioemu/hw/pc.c 2005-05-23 16:37:18 -07:00 @@ -419,11 +419,11 @@ ret = load_image(buf, phys_ram_base + vga_bios_offset); #endif +#ifndef NOBIOS /* setup basic memory access

patch revision history ---------------------- v1: Initial patch to handle this issue involving changing the hypercall interface v2:Totally handled inside hypervisor. v3:Change some logics of handling msi-x pending unmask operations. v4:Some changes related to coding style according to Andrew Cooper''s comments v5:Some changes according to Jan''s comments, including a) remove

Hi, to use the host keyboard and touchpad of my laptop while running a HVM guest with passthroughed primary gfx-card I wrote a simple emulation. To activate it change gfx_passthru=1 -> gfx_passthru=1001 in the domU config file. This was done this way to have a small footprint. Also the embedding in helper2.c is a little bit awkward. Another problem using this way is that the VT in dom0 is not

Simplified vmx_platform.c by removing obsolete code and redundant vmread''s. Signed-Off-By: Leendert van Doorn <leendert@watson.ibm.com> diff -r 9cdfcecf4968 xen/arch/x86/vmx_platform.c --- a/xen/arch/x86/vmx_platform.c Wed Nov 2 16:29:32 2005 +++ b/xen/arch/x86/vmx_platform.c Wed Nov 2 21:12:02 2005 @@ -366,20 +366,15 @@ return DECODE_success; } -static int

Memory mapped and port I/O is currently broken under VMX when the partition is running in VM8086 mode. The reason is that the instruction decoding support uses 32-bit opcode/address decodes rather 16-bit decodes. This patch fixes that. In addition, the patch adds support for the "stos" instruction decoding because this is a frequently used way to clear MMIO areas such as the screen. As

I finally decided to build 4.0.1 on my OpenSuSE box. I''ve been plodding along and resolving issues/dependencies as needed but now I''m stumped. While building I get the following message: cc1: warnings being treated as errors netfront.c:41:32: error: variably modified ‘tx_freelist’ at file scope netfront.c:44:34: error: variably modified ‘rx_buffers’ at file scope

When using a vtsc, hvm_set_guest_time changes hvm_vcpu.stime_offset, which is used in the vcpu time structure to calculate the tsc_timestamp, so after updating stime_offset we need to propagate the change to vcpu_time in order for the guest to get the right time if using the PV clock. This was not done correctly, since in context_switch update_vcpu_system_time was called before vmx_do_resume,

patch revision history ---------------------- v1: Initial patch to handle this issue involving changing the hypercall interface v2:Totally handled inside hypervisor. v3:Change some logics of handling msi-x pending unmask operations. v4:Some changes related to coding style according to Andrew Cooper''s comments From 51c5b7f1f9c8f319da8adf021b39e18fbd3bf314 Mon Sep 17 00:00:00 2001 From:

Source: xen Version: 4.1.4-4 Severity: serious Tags: jessie sid User: debian-qa at lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)

As many of us are all too painfully aware we have completely different VNC server implementations for paravirt vs fullyvirt Xen guests. The former based on libvncserver, the latter integrated into QEMU. There are many new and interesting ideas being tried out in the VNC server space in particular wrt to virtualization and having to implement them all twice is not very desirable. Also

> Hmmm... wouldn''t it be nice if we didn''t have a bespoke, > buggy & incomplete emulator for hvm mmio. ;-) In the process of solving this one, I''ve got to (another) of the blocking points... At the moment, we translate the virtual address from the guest in the page-fault-handler to guest physical address via the gva_to_gpa() function in svm.c/vmx.c:

This patch adds the ia64-specific code for new Qemu . In addition, some ia64 patches aren''t checked into xen-unstable.hg, so I reversed the related logic temporarily. Once sync with xen-ia64-unstable.hg, the logic will regain automatically. Thanks & Best Regards -Xiantao OTC,Intel Corporation _______________________________________________ Xen-devel mailing list

I ran a bisect to find out when Windows XP 32 bit becomes unusably slow. And I found the changeset that caused it. ========== The problem: ========== Windows 8 64 bit and 32 bit run fast and fine in the newest xen versions. Windows XP 32 bit runs unusably slow in anything new that I built from xen-unstable, but runs fast in 4.1.2 and 4.1.3 stable. While it is running slow, "xm top" or

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

The following 5 patches are re-submissions of the vt-d patch. This set of patches has been tested against cs# 15080 and is now much more mature and tested against more environments than the original patch. Specifically, we have successfully tested the patch with following environements: - 32/64-bit Linux HVM guest - 32-bit Windows XP/Vista (64-bit should work but did not test) -