search for: nestedhvm

...* shadow-on-shadow. */ if ( cpu_has_svm && !paging_mode_hap(d) && a.value ) rc = -EINVAL; /* Set up NHVM state for any vcpus that are already up */ - if ( !d->arch.hvm_domain.params[HVM_PARAM_NESTEDHVM] ) + if ( a.value && + !d->arch.hvm_domain.params[HVM_PARAM_NESTEDHVM] ) for_each_vcpu(d, v) if ( rc == 0 ) rc = nestedhvm_vcpu_initialise(v); + if ( !a.value || r...

...0 deletions(-) diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c index a3868f9..51311fc 100644 --- a/xen/arch/x86/domain.c +++ b/xen/arch/x86/domain.c @@ -51,6 +51,7 @@ #include <asm/fixmap.h> #include <asm/hvm/hvm.h> #include <asm/hvm/support.h> +#include <asm/hvm/nestedhvm.h> #include <asm/debugreg.h> #include <asm/msr.h> #include <asm/traps.h> @@ -704,9 +705,13 @@ int arch_set_info_guest( /* PVH 32bitfixme */ ASSERT(!compat); - if ( c(ctrlreg[1]) || c(ldt_base) || c(ldt_ents) || + if ( (c(ctrlreg[0]) & HV...

...be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ changeset: 25705:983ea7521bad tag: tip user: Tim Deegan <tim@xen.org> date: Thu Aug 02 14:44:53 2012 +0100 nestedhvm: return the pfec from the pagetable walk. Don''t clobber it with the pfec from teh p2m walk behind it; the guest will not expect (or be able to handle) error codes that come from the p2m table, which it can''t see or control. Signed-off-by: Tim Deegan <t...

This patch introduces support for two new parameters in libxl: smbios_firmware=<path_to_smbios_structures_file> acpi_firmware=<path_to_acpi_tables_file> The changes are primarily in the domain building code where the firmware files are read and passed to libxc for loading into the new guest. After the domain building call to libxc, the addresses for the loaded blobs are returned and

This patch series tidies up a few bits ofthe nested p2m code. The main thing it does is reorganize the locking so that most of the changes to nested p2m tables happen only under the p2m lock, and the nestedp2m lock is only needed to reassign p2m tables to new cr3 values. Changes since v1: - a few minor fixes - more sensible flushing policy in p2m_get_nestedp2m() - smoke-tested this time!

while doing "while xm migrate --live domU localhost;do sleep 1;done" I just got the crash shown below. And it can be reproduced. The guest has 2 vcpus and 512mb, it runs pvops 3.7.9 (XEN) ----[ Xen-4.3.26579-20130219.172714 x86_64 debug=n Not tainted ]---- (XEN) CPU: 14 (XEN) RIP: e008:[<ffff82c4c01dd197>] nvmx_vcpu_destroy+0xb7/0x150 (XEN) RFLAGS: 0000000000010282

Dom0: Wheezy 64 bit with kernel from package linux-image-3.2.0-4-amd64 version 3.2.41-2+deb7u2, package blktap-dkms and all dependency packages for xen, spice and usb redirection. Seabios 1.7.2-3 and latest spice and usbredir compiled from debian unstable sources. ------------------------- /etc/modules ------------ loop max_loop=64 xenfs xen-evtchn blktap ------------------------- git clone

...;'fdb'', ''''], [''guest_os_type'', ''default''], [''hap'', 1], [''hpet'', 0], [''isa'', 0], [''keymap'', ''''], [''localtime'', 0], [''nestedhvm'', 0], [''nographic'', 0], [''opengl'', 1], [''oos'', 1], [''pae'', 1], [''pci'', []], [''pci_msitranslate'', 1], [''pci_power_mgmt'', 0], [''rtc_timeoffset'', 0],...

Hi! Recently got a Via VE-900 board from Fry''s. It has a via nano x2 chip on it, and suggests that it has Intel-compatible virtualization extensions. Has anyone worked with this board yet? I thought it would be nice to have a lower-powered, nearly silent Xen machine sitting on my desk. I tried booting into Xen, but it said it didn''t recognize the processor. I can post

Hi! Recently got a Via VE-900 board from Fry''s. It has a via nano x2 chip on it, and suggests that it has Intel-compatible virtualization extensions. Has anyone worked with this board yet? I thought it would be nice to have a lower-powered, nearly silent Xen machine sitting on my desk. I tried booting into Xen, but it said it didn''t recognize the processor. I can post

...| 2 +- xen/arch/x86/mm/p2m-ept.c | 96 +++++++-- xen/arch/x86/mm/p2m.c | 44 +++-- xen/arch/x86/mm/shadow/multi.c | 2 +- xen/include/asm-x86/guest_pt.h | 8 + xen/include/asm-x86/hvm/hvm.h | 9 +- xen/include/asm-x86/hvm/nestedhvm.h | 1 + xen/include/asm-x86/hvm/svm/nestedsvm.h | 3 + xen/include/asm-x86/hvm/vmx/vmcs.h | 31 ++- xen/include/asm-x86/hvm/vmx/vmx.h | 6 +- xen/include/asm-x86/hvm/vmx/vvmx.h | 29 +++- xen/include/asm-x86/p2m.h | 17 +- 22 files changed, 859 inse...

Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- ---to satisfy European Law for business letters: Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach b. Muenchen Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen Registergericht Muenchen, HRB Nr. 43632 _______________________________________________ Xen-devel mailing list

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

In blkback driver, after I/O requests are submitted to Dom-0 block I/O subsystem, blkback goes to ''sleep'' effectively without letting blkfront know about it (req_event isn''t set appropriately). Hence blkfront doesn''t notify blkback when it submits a new I/O thus delaying the ''dispatch'' of the new I/O to Dom-0 block I/O subsystem. The new I/O is

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. Patch 1 modifies the guest ro and rw node creation to an open coding style and cleans up some extraneous node creation. Patch 2 modifies creation of the hvmloader key in xenstore and adds

The following is a revised patch series to add support for a VM generation ID virtual device for HVM guests. The basic requirements of this device are as follows: - It must be exposed somewhere in ACPI namespace with a _CID of "VM_Gen_Counter". - It must also include a _DDN of "VM_Gen_Counter". - It must contain a _HID object but no particular value is required. - It must

...rvisor to do any real work. > You are likely the > first to try this with the Debian packaging, and nested virt generally > is considered tech preview upstream, so I'd expect there to be some > wrinkles in doing this. > > By "with vmx enabled" I guess you mean with nestedhvm=1 in the guest > cfg? Are you running this in a PV or HVM guest (I think HVM)? Can you > post the dmesg from the kernel please, along with the guest cfg file. root at intel:/home/sydney# cat xencfg/xen.cfg name='xen' builder="hvm" vnc=1 vncdisplay=84 vncpasswd="test&qu...

This patch series adds support for preservation of the VM generation ID buffer address in xenstore across save/restore and migrate, and also code to increment the value in all cases except for migration. The first patch modifies creation of the hvmloader key in xenstore and adds creation of a new read/write hvmloader/generation-id-addr key. The second patch changes hvmloader to use the new key (as

...gt; >> You are likely the >> first to try this with the Debian packaging, and nested virt generally >> is considered tech preview upstream, so I'd expect there to be some >> wrinkles in doing this. >> >> By "with vmx enabled" I guess you mean with nestedhvm=1 in the guest >> cfg? Are you running this in a PV or HVM guest (I think HVM)? Can you >> post the dmesg from the kernel please, along with the guest cfg file. > > root at intel:/home/sydney# cat xencfg/xen.cfg > name='xen' > builder="hvm" > vnc=1 >...