similar to: svm vmexit action sequence

The self_nmi() code cause''s an NMI to be triggered by sending an APIC message to the local processor. However, NMIs are blocked by the VMEXIT, until the next iret or VMENTER. Volume 3 Chapter 27 Section 1 of the Intel SDM states: An NMI causes subsequent NMIs to be blocked, but only after the VM exit completes. As a result, as soon as the VMENTER happens, an immediate VMEXIT happens

This set of patches converts the way frames gets created from using PUSHes/POPs to using MOVes, thus allowing (in certain cases) to avoid saving/restoring part of the register set. While the place where the (small) win from this comes from varies between CPUs, the net effect is a 1 to 2% reduction on a combined interruption entry and exit when the full state save can be avoided. 1: use MOV

Hi all, Please can anybody explain how communication(direct or indirect) happens between xen and guest os(windows) in full virtualization mode. Both from VMM to guest and from guest to VMM. Thanks and regards, Aditya. __________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/

This was set to zero immediately before the #GP injection code, since SYSENTER doesn''t really have a return address. Reported-by: Ian Campbell <Ian.Campbell@citrix.com> Furthermore, UREGS_cs and UREGS_rip don''t need to be written a second time, as the PUSHes above already can/do take care of putting in place the intended values. Signed-off-by: Jan Beulich

I''m not seeing the problem that Fan Zhao is reporting, instead I get this one. Not sure if ti''s the same one or a different problem... This happens with my simple-guest [i.e. not using hvmloader, as I described before]. This worked fine yesterday. (XEN) event_channel.c:178:d0 EVTCHNOP failure: domain 0, error -22, line 178 (XEN) bad shared page: 0 (XEN) domain_crash_sync called

Hi, I know this may be very basic question but I need some help . Actually I installed VM using the Xen Administrative console. Now I need to change the configuration file as I need to passthrough (using the pci-hide) a SCSI contoller from Dom0 to DomU. But I couldnot find the configuration file. Where can I find the Configuration file for this DomU? Actually I added the

Hi All, I am trying to provide services to guest VMs where I wish to run guest VMs in a loop. I wish to use a core to schedule a guest VM, service it eg. execute an ISR etc and then return to the context of Xen on that core, so that I can then schedule the next VM on that core. In doing all this, the goal is to avoid the calls to VMEntry and VMExit. Is there a workaround for this to be done or

From: Yang Zhang <yang.z.zhang@Intel.com> The follwoing patches are adding the Posted Interrupt supporting to Xen: Posted Interrupt allows vAPIC interrupts to inject into guest directly without any vmexit. - When delivering a interrupt to guest, if target vcpu is running, update Posted-interrupt requests bitmap and send a notification event to the vcpu. Then the vcpu will handle this

Keir, is there a particular reason you chose to use slightly different special mode numbers than Linux, ignoring VIDEO_CURRENT_MODE altogether? I think it wouldn''t be bad to be in sync with Linux here, and I independently think that having a way to avoid mode switching altogether is good to have in case of possible problems on exotic hardware. Jan

Cleanup vmx vmexit handler. Current code doesn''t handle vmexits caused by triple fault, INIT, SIPI, etc, which are listed in IA32 Architecture System Programming Guide 2, Appendix I VMX Basic Exit Reasons, and calls __hvm_bug() when not handling such cases, actually domain crash should be good enough. Also various coding style cleanups. Signed-off-by: Xin Li <xin.b.li@intel.com>

Hi, Lately I was puzzled by a vmexit reason 31 which was defined as EXIT_REASON_MSR_READ I allocated an array in xen data section and assigned its MFN to an EPT entry of a domainU, I thought the domU could access this array but after that the domainU crashed and xen gave me this exit reason "Bad vmexit (reason 31)" But there is nothing to do with MSR READ, so I''m confused...

Hi, I am currently working on hypercalls from HVM guests. I started with a set of Intel patches posted to xen-devel last September. I currently have code running for both 32-bit and 64-bit HVM guests running on a 64-bit hypervisor. I am curious why none of the original patches were accepted, and what I might need to do to make them acceptable. Is other work being done in this area that

This patch enables tracing VMEXIT/ENTRY for 64-bit systems (are there any 32-bit VT enabled systems out there?) Signed-off by Himanshu Raj (rhim.list@nosuchaddr.com) -- ------------------------------------------------------------------------- Himanshu Raj PhD Student, GaTech (www.cc.gatech.edu/~rhim) I prefer to receive attachments in an open, non-proprietary format.

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

about VIRQ &amp; PIRQ what is VIRQ  ?How VIRQ is different from PIRQ ?How VIRQ &amp; PIRQ are related each other ? DISCLAIMER: ----------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any

Hi: we have following setup: 1. 2.6.16-33-based Xen 3.0.3/Xen-3.0.4 DOM-0 kernels. 2. Using LILO-mbootpack from USB we boot Xen-->DOM-0 setup 3. We mount harddisk and try to install xp.hvm While,we are successful with FCs as DOM-U, for XP we get, VBD (768) could not be connected. We do have max_loop count to 64 and enough loop devices. Note that above error is consistent on both 3.0.3

> 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:

I can boot a 64-bit HVM image on my SVM-system, and it goes quite a long way before it crashes (due to not finding the hard-disk image and thus no root FS - which I think may well be the configuration file). But if I set debug=y in the Rules.mk, I don''t get very far at all - it crashes well before it gets to any user-mode (Ring3) - in fact, I think it''s crashing pretty much as

Hi all, I manage to create a VM (slackware image) and hide the PCI device (qlogic HBA) from Dom0 to DomainU. Now the Dom0 cant see this HBA and the ''xm list -l'' shows this pci device under the DomainU. But how can I do some scsi inquiry or check if this PCI device is visible to the DomainU from the DomainU''s console. Any help? Thanks and regards Ashit

What are methods to debug domU when it hangs? Using xen 3.1 compiled from sources I could not manage to launch no domU. Fot instance, I run something like this: =====8<===================== disk = [ ''file:/oradata-act/sles.disk,hda1,w'', '',hdc:cdrom,r'' ] kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen" cpus =