similar to: VT vmx-domain usb support and vnc connection through qemu-dm.

This patch removes the ignored "Unconditional I/O exiting" setting in VMCS for the vmx guest since "Use I/O bitmaps" setting is being used. Signed-off by Himanshu Raj (rhim@cc.gatech.edu) diff -r 19c55935580f xen/include/asm-x86/hvm/vmx/vmx.h --- a/xen/include/asm-x86/hvm/vmx/vmx.h Wed Apr 12 17:53:38 2006 +++ b/xen/include/asm-x86/hvm/vmx/vmx.h Thu Apr 13 02:31:25 2006 @@

Fix config file parsing for VMX domains. If we define "vif" in the config file, image.py will raise error "vmx: missing vbd configuration". The reason is "vif" is dealt with as a "vbd" device. This patch fixes this issue by dealing with "vbd" and "vif " separately, removing "macaddr" arg and parsing mac address from

This patch does 3 things to the new device model, qemu-dm: 1) Add `vncviewer'' as an option to `qemu-dm'' to spawn a `vncviewer'' process. 2) Have the `vncviewer'' config parameter translate to the `vncviewer'' flag to `qemu-dm''. 3) Add a new config parameter, `vncconnect'', that spawns a `vncviewer'' process that looks for a

VT is enabled in BIOS and ''xm info'' shows that hvm can be created like below: xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm -3.0-x86_64 Several Windows VMs have been created on this server and running perfectly. However, I wonder that it does not show anything when commands show VT-x availability such as ''xm dmesg | grep VMX(or

Ian, Keir, This patch is to boot 32-bit VMX guest on the 64-bit host. Double-compile is used to make both 64-bit guest and 32-bit guest can work, the shadow page-table uses current 64-bit shadow code''s structure to simulate 32-bit guest''s 2-level page-table. Signed-off-by: Chengyuan Li <chengyuan.li@intel.com> Signed-off-by: Xiaohui Xin <xiaohui.xin@intel.com>

Jun suggested to use another elegant way, pls ignore this one. -Xin >SMP VMX guest AP bring up need call do_boot_vcpu in hypervisor. >Current call to do_boot_vcpu always from domain, however, for SMP VMX >guest AP bring up, it is called from xen hypervisor. >Signed-off-by: Xin Li <xin.b.li@intel.com> > >diff -r f069a06e650f xen/common/domain.c >--- a/xen/common/domain.c

Hi Keir, this patch changes common code of xen hypervisor, but seems we have to, because current call to do_boot_vcpu is always from domains, however, for SMP VMX guest AP bring up, we need call it from xen hypervisor, so we''d like to split it. What''s your opinion? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

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

> -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of > Thorolf Godawa > Sent: 02 February 2006 16:33 > To: Charles Coffing > Cc: xen-devel@lists.xensource.com > Subject: Re: [Xen-devel] No VMX-guests on Intel Xeon/VT > > Hi Chuck and all others, > > > yeah, its going

Hi. I can''t use the vnc option (VNC=1 in my xmexample.hvm file), when I use RedHat or Fedora on 64 bits. The qemu log, say /usr/lib64/xen/bin/qemu-dm: invalid option -- ''-vncconnect'' But when I use RedHat or Fedora 32 bits, works fine. There is a problem or incompatibility in the 64 bits Xen kernel and the VNC option ? Best regards Luis

> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Thorolf Godawa > Sent: 02 February 2006 02:30 > To: xen-devel@lists.xensource.com > Cc: xen-users@lists.xensource.com > Subject: [Xen-users] Re: No VMX-guests on Intel Xeon/VT > > Hi all, > > OK, I''ve installed

> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Thorolf Godawa > Sent: 02 February 2006 02:30 > To: xen-devel@lists.xensource.com > Cc: xen-users@lists.xensource.com > Subject: [Xen-users] Re: No VMX-guests on Intel Xeon/VT > > Hi all, > > OK, I''ve installed

Passthrough the LBR stack to the guest, and auto switch the stack MSRs upon VMEntry and VMExit. Signed-off-by: Wei Wang <wei.w.wang at intel.com> --- arch/x86/kvm/vmx.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 50 insertions(+) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index 5f5c2f1..35e02a7 100644 --- a/arch/x86/kvm/vmx.c +++ b/arch/x86/kvm/vmx.c

Passthrough the MSR_IA32_DEBUGCTLMSR to the guest, and take advantage of the hardware VT-x feature to auto switch the msr upon VMExit and VMEntry. Signed-off-by: Wei Wang <wei.w.wang at intel.com> --- arch/x86/kvm/vmx.c | 13 ++++--------- 1 file changed, 4 insertions(+), 9 deletions(-) diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c index 8434fc8..5f5c2f1 100644 ---

We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Cannot boot Windows 2000 - Only one CPU is detected in SMP dom0 - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: + Build&Boot UP xen0 without problem + Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain + Can bootup unmodified IA-32 WindowsXP SP1/SP2 in

This patch clarifies a vague statement in the SDM: the recommended maximum number of MSRs that can be automically switched by CPU during VMExit and VMEntry is 512, rather than 512 Bytes of MSRs. Depending on the CPU implementations, it may also support more than 512 MSRs to be auto switched. This can be calculated by (MSR_IA32_VMX_MISC[27:25] + 1) * 512. Signed-off-by: Wei Wang <wei.w.wang at

We have tested the latest xen on VT platform with Intel 915/E8500 chipset. Here is the test summary: Issues: - Only one CPU is detected in SMP dom0 - Destroying VMX with 4G memory may make xend hang on IA-32e IA-32: + Build&Boot UP xen0 without problem + Can bootup unmodified IA-32 2.4/2.6 linux in VMX domain + Can bootup unmodified IA-32 WindowsXP SP1/SP2 in VMX domain + Can bootup

This enhances the existing VMX input support allowing it to be used over SSH to the ESXi server. The original command (for local .vmx files) was: $ virt-v2v -i vmx guest.vmx -o local -os /var/tmp Adding ‘-it ssh’ and using an SSH remote path gives the new syntax: $ virt-v2v \ -i vmx -it ssh \ "root@esxi.example.com:/vmfs/volumes/datastore1/guest/guest.vmx" \ -o local

On 25/09/2017 06:44, Wei Wang wrote: > Passthrough the LBR stack to the guest, and auto switch the stack MSRs > upon VMEntry and VMExit. > > Signed-off-by: Wei Wang <wei.w.wang at intel.com> This has to be enabled separately for each guest, because it may prevent live migration to hosts with a different family/model. Paolo > --- > arch/x86/kvm/vmx.c | 50

On 25/09/2017 06:44, Wei Wang wrote: > Passthrough the LBR stack to the guest, and auto switch the stack MSRs > upon VMEntry and VMExit. > > Signed-off-by: Wei Wang <wei.w.wang at intel.com> This has to be enabled separately for each guest, because it may prevent live migration to hosts with a different family/model. Paolo > --- > arch/x86/kvm/vmx.c | 50