similar to: RE: Re: mapcache broken?

This patch clean up VMX builder. Since now we have vmxloader, old code loading linux kernel directly is not needed. 1. remove linux parameters. 2. remove init ramdisk. 3. remove e820 memmap config file parse. Also e820 map handling code is changed in vmx_setup_platform. 4. remove provisional GDT, and construct_init_guest_vmcs is updated greatly. 5. remove some ugly tailing space. Thanks Keir for

Keir: This is to to make the IDE device model multithreading so that the VMX domain IO access completion (triggering DMA operation) can be asynchronize with the completion of DMA operation. With this patch we get 8%--14% performance gain for kernel build. Thanks, eddie Yang, Xiaowei wrote: > Originally in qemu when a IDE dma transfer is started which is > triggered by access to 0xc000

Keir: This patch is to remove the pit_timer when the vmx domain is inactive to save HV external IRQ caused by ac_time and some cleanup for ioapic in HV. Thx,eddie Signed-off-by: Eddie Dong <eddie.dong@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

attached is the vmx domain save/restore patch. works well for different guest/host combination W/O breaking domu save/restore according to my test. pls. first apply xiaowei''s qemu dm fix. ===know issue=== * shpage pfn * HV look for shpage pfn in an e820 entry when init. but some guest(win/em64t linux) will reuse this e820 ram, which cause losing shpage pfn when restore. so this

We saw these issues in recent ChangeSet: 1. Reboot fail in Guest OS: Reboot in guest will close current qemu windows but does not create a new qemu window to restart 32bit HV/xen0: 2. 4 LTP math cases(float_bessel, float_exp_log, float_power and float_trigo) sometime fail. (775) 3. Kernel build in VMX may meet kernel panic. It complains like: "<0> Kernel panic - not syncing:

Intercepting this MSR is pointless - The swapgs instruction does not cause a vmexit, so the cached result of this is potentially stale after the next guest instruction. It is correctly saved and restored on vcpu context switch. Furthermore, 64bit Windows writes to this MSR on every thread context switch, so interception causes a substantial performance hit. From: Paul Durrant

flight 13627 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13627/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-win-vcpus1 12 guest-localmigrate/x10 fail REGR. vs. 13625 test-amd64-amd64-win 5 xen-boot fail REGR. vs. 13625 test-i386-i386-xl-win 5 xen-boot

[VMX] Add support for Pause-Loop Exiting New NHM processors will support Pause-Loop Exiting by adding 2 VM-execution control fields: PLE_Gap - upper bound on the amount of time between two successive executions of PAUSE in a loop. PLE_Window - upper bound on the amount of time a guest is allowed to execute in a PAUSE loop If the time, between this execution of PAUSE

Hi all, This is our nightly testing report for c/s 17917; no new issue today, and bug #1286 got fixed. Fixed issue: ============================================== 1. guest cannot be created with two disks appended. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1286 Old issues: ============================================== 1. dom0 hangs with io errors printed while booting hvm

HVM balloon driver or something, that''s under development, may decrease or increase the machine memory that is taken by HVM guest; in IA32/IA32e host, now Qemu maps the physical memory of HVM guest based on little blocks of memory (the block size is 64K in IA32 host or 1M in IA32E host). When HVM balloon driver decreases the reserved machine memory of HVM guest, Qemu should unmap the

Forget to reset sum in func checksum_valid(). Update the patch again. sorry for the inconvenient. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Yu, Ke > Sent: 2005年12月31日 22:26 To: Keir Fraser > Cc: xen-devel@lists.xensource.com > Subject: RE: [Xen-devel] [PATCH][RESEND] add

I run VMWare server 1.07 on Centos 5. Last night I left a Windows 2000 virtual machine doing a ClamWin scan of drive M: when I went to bed around midnight. Drive M: is actually a volume on the Centos 5 host, mounted via Samba. It has about 40Gb of photos on it, plus a few other things. I had the VM up visible in the VMWare Server Console running under KDE on display 8 (X session #1), my

flight 8270 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/8270/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail REGR. vs. 8256 test-amd64-i386-rhel6hvm-intel 3 host-install(3) broken test-amd64-amd64-win 3 host-install(3) broken test-amd64-i386-pv

flight 12033 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12033/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-win-vcpus1 6 leak-check/basis(6) fail REGR. vs. 11853 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10

The aim of this patch is to define a stable way in which PVH is going to do AP bringup. Since we are running inside of a HVM container, PVH should only need to set flags, cr3 and user_regs in order to bring up a vCPU, the rest can be set once the vCPU is started using the bare metal methods. Additionally, the guest can also set cr0 and cr4, and those values will be appended to the default values

Hi all, This is today''s nightly testing report; no new issue found, bug #1259 got fixed. Some vt-d cases failed in first round testing, but can get pass in retesting. Fixed issue: ============================================== 1. booting windows guest causes Xen HV crash http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1259 Old issues:

Add two virtual device operations: 1.set the callback irq for event channel 2.setup the hypercall paramerter share page. Signed-off-by: Ke Yu <ke.yu@intel.com> Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> diff -r 287d36b46fa3 xen/arch/x86/vmx.c --- a/xen/arch/x86/vmx.c Tue Aug 30 20:36:49 2005 +++

flight 10626 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10626/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-multivcpu 16 guest-start.2 fail in 10623 REGR. vs. 10621 Tests which are failing intermittently (not blocking): test-amd64-i386-rhel6hvm-intel 4 xen-install fail

Keir, Ian, With PCI mmconfig option on, and with the PCI express enabled BIOS, the dom0 kernel reads the PCI config from fix-mapped PCI mmconfig space. The PCI mmconfig space is of 256MB size, and it''s access is implemented differently on i386 & x86_64. On x86_64 the whole 256MB is mapped in the Kernel virtual address space. On i386 it will consume too much of the kernels

Keir, The patch moves ACPI timer to HV, which is the last platform timer in Qemu. We found Vista polls ACPI timer very frequently (about 15 times averagely) when handling timer (RTC @ 64HZ) interrupt routine. Though the exact reason is known, it should be related to system time adjustment. When it''s in Qemu, the overhead is big. After moving, Vista''s idle overhead decreases