similar to: Bug#604160: solution found, but vmx flag is misleading

Package: xen-hypervisor-4.0-amd64 Fresh install of squeeze beta amd64 System is a Thinkpad X61s with L7500 CPU Windows 7 is on the box, the Thinkpad tools on Windows 7 say VMX is present Followed the squeeze dom0 instructions at: http://wiki.debian.org/Xen aptitude -P install xen-hypervisor-4.0-amd64 linux-image-xen-amd64 xen-tools mv -i /etc/grub.d/10_linux /etc/grub.d/50_linux update-grub2

Hi, I am using Xen 4 under Debian Squeeze. I want to use Windows 2008 x86 with HVM, but only one vcpu allocated when vm started. After increasing vcpus number (vcpus = ''4'') in cfg, at start ignored that parameter, xm list VCPUs show only 1. Why does not able to increase the vcpus? Any idea?:) p.s: if using pvm linux, then the vcpus parameter is ok, increased successfully when I

TPR shadow/threshold feature is important to speedup the boot time for Windows guest. Besides, it is a must feature for certain VMM. We map virtual APIC page address and TPR threshold from L1 VMCS, and synch it into shadow VMCS in virtual vmentry. If TPR_BELOW_THRESHOLD VM exit is triggered by L2 guest, we inject it into L1 VMM for handling. Besides, this commit fixes an issue for apic access

Hi I have Intel Core 2 Duo T9400 processor and I''m running dom0 on Gentoo 2.6.21 kernel. I also tried Gentoo 2.6.18-r12 kernel but in this two cases there was no vmx flag in: localhost ~ # grep vmx /proc/cpuinfo localhost ~ # grep flags /proc/cpuinfo flags : fpu de tsc msr pae cx8 apic sep mtrr cmov pat clflush acpi mmx fxsr sse sse2 ss ht syscall nx lm constant_tsc pni est

[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

UPDATE: This bug does not reproduce in version: 4.1.4-3 since the domU creation is shadowed by another new bug [1]. Below is my hypervisor log or "xm dmesg" output since the 706543 bug also affects my system: # xm dme (XEN) Xen version 4.1.4 (Debian 4.1.4-3) (waldi at debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) Fri Apr 19 11:34:20 UTC 2013 (XEN) Bootloader: GRUB 1.99-27+deb7u1

From: Nicu?or C??u <ncitu at bitdefender.com> This is needed in order to handle clients controlling the MSR related VM-exits. Signed-off-by: Nicu?or C??u <ncitu at bitdefender.com> Signed-off-by: Adalbert Laz?r <alazar at bitdefender.com> --- arch/x86/kvm/vmx/vmx.c | 70 +++++++++++++++++++++++------------------- 1 file changed, 38 insertions(+), 32 deletions(-) diff --git

From: Nicu?or C??u <ncitu at bitdefender.com> This is preparatory patch to mediate the MSR interception between the introspection tool and the device manager (one must not disable the interception if the other one has enabled the interception). Passing NULL during initialization is OK because a vCPU can be introspected only after initialization. Signed-off-by: Nicu?or C??u <ncitu at

Some operating systems access the local APIC TPR very frequently, and we handle that using software-based local APIC virtualization in Xen today. Such virtualization incurs a number of VM exits from the memory-access instructions against the APIC page in the guest. The attached patch enables the TPR shadow feature that provides APIC TPR virtualization in hardware. Our tests indicate it can

Finished installing CentOS 5.5 x86_64 on a new Dell tower workstation that has a quad core Intel processor and 8 GB of ram. BIOS has hardware virtualization support enabled. /proc/cpuinfo shows that all four cores have the vmx flag present. I applied a lot of the National Security Agency guide for securing Red Hat Linux 5, testing the key applications I need as I went. At the end of the process

Hi, I am having great difficulties in getting pci passthrough with VTd to work, surely I am doing something stupid but I cannot see what. "tangram" (https://www.blogger.com/profile/06588030231546523539) has been a huge help, but despite his efforts I am still stuck. Hardware: Intel S3200SHV motherboard BIOS : S3200X38.86B.00.00.0052 CPU : Intel Core 2

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

Hello all, I have a problem getting a working VNC console for HVM guests on Xen 4.1. When I start the DomU with xm create everything is fine the DomU runs and in xm list it has the running state but when I try to connect to the VNC console to install an operating system (Ubuntu and Debian I have tested) the VNC viewer only shows a black screen. So I searched in the logs and found a log entry

Hello, With kernel 2.6.32.21 (from Jeremy) : - System size : 3945 kB, gzip compressed kernel size 4051553 Bytes -> works well - System size : 3968 kB, gzip compressed kernel size 4074976 Bytes -> fault (see below) I''ve attached the 2 configurations files and xen boot error. __ __ _ _ ___ _ \ \/ /___ _ __ | || | / _ \ / | \ // _ \

> On Mon, Jul 01, 2013 at 12:12:31AM +0300, NiX wrote: >> System: >> >> CPU''s: 2 x XEON X5450 >> Motherboard: >> http://www.intel.com/p/en_US/support/highlights/server/s5000psl/ >> RAM: 16GB DDR2 ECC >> OS: Debian 7.0 64bit >> >> If I attempt to use more than 3GB of RAM to the guest below (Windows >> 2008 >> server R2

Hi, I am having some issues with xen hypervisor crashing because it could not find one of the cores in my processor. This is not consistent. It happens once in every two or three boots. Is this is xen bug or is it something related to BIOS. If it is a xen bug, has it been addressed and could you point me to the right patch. Here is the xen boot message. title CentOS (2.6.18-274.7.1.el5xen)

From: Yang Zhang <yang.z.zhang@Intel.com> The following patches fix the issue that fail to boot L2 guest on APIC-v available machine. The main problem is that with APIC-v, virtual interrupt inject L1 is totally through APIC-v. But if virtual interrupt is arrived when L2 is running, L1 will detect interrupt through vmexit with reason external interrupt. If this happens, we should update

Hi folks, currently I try to setup a new xen host v3.4.1 on top of a Asus P5E-VM DO (latest BIOS, Vt-d capable and enabled in BIOS) to migrate my extisting HVMs (Win2k3 server) running on Xen v3.3.0 to a new home. I want to switch over to 3.4.1 to (hopefully!) passthrough my ISDN board to a HVM domU. Unfortunate there seem some issue with the VT-d DMAR tables which is beyond my knowledge and

The hvm domain which is being debugged sometimes crashes with the following message: (XEN) Failed vm entry (exit reason 0x80000021) caused by invalid guest state (0). (XEN) ************* VMCS Area ************** (XEN) *** Guest State *** (XEN) CR0: actual=0x000000008005003b, shadow=0x000000008005003b, gh_mask=ffffffffffffffff ...[snip]... (XEN) DebugCtl=0000000000000000

We have tested latest xen on VT platform with Intel 915/E8500 chipset.Here is the test summary. Issues: - IA-32 VMX guest will hang when booting on IA-32PAE host with acpi=1 and apic=1.(Bug 594) - Failed to created VMX after tens of VMXs have been created & destroyed on IA-32e.(Bug593) IA-32: Build&Boot SMP xen0 without problem Can bootup unmodified IA-32 2.4/2.6 linux in VMX