WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] VMX Error 2 during "make install"

To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Subject: Re: [Xen-users] VMX Error 2 during "make install"
From: Aaron Stanford <aaron@xxxxxxxxxxx>
Date: Fri, 11 Aug 2006 11:43:28 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 11 Aug 2006 08:44:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0BA7FE30@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <907625E08839C4409CE5768403633E0BA7FE30@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.5 (Windows/20060719)
Mats et al,

Appreciate the prompt reply!  I performed a make clean, and attempted the process again with the same result.  After looking through the make file, I performed a make kclean as well, and while in each instance my make world worked appropriately, the make install died at the same point.

Thanks,
Aaron

Petersson, Mats wrote:
-----Original Message-----
From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
Aaron Stanford
Sent: 11 August 2006 15:52
To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] VMX Error 2 during "make install"

Xen gurus,

I'm trying to install Xen from source on a Dell PE 1850 under 
RHEL4U3. 
The system has two P4 Xeon processors, 4GB RAM, and I will use device
backed storage provided by a PERC controller.

Googling on the problem and searching the mail archives has 
led me to two
separate posts, one of which was unanswered, and another 
which marked it
as "resolved" without going into specifics.

I have no problem compiling with the following command:

# KERNELS="linux-2.6-xen0 linux-2.6-xenU" 
XEN_TARGET_X86_PAE=y make world

However, when I run a "make install", it proceeds merrily 
along until it
gets to the following point:
    

I'm not sure of the full resolution to your problem, but it looks like
some header-files are wrong/missing/broken or some mismatched object
files. 

Try a "make clean" before building again, in case there's just some
simple problems [that's particularly true if you've already tried to
build before without PAE enabled - as there are some macros that
rename/replace the functions involved in virtual memory handling based
on PAE or no-PAE (such as gva_to_gpa which translates a guest virtual
address to the guest's view of physical memory)].

--
Mats

  
ld   -m elf_i386 -r -o built_in.o apic.o audit.o bitops.o delay.o
dmi_scan.o dom
0_ops.o domain.o domain_build.o e820.o extable.o flushtlb.o 
i387.o i8259.o
io_ap
ic.o irq.o microcode.o mm.o mpparse.o nmi.o physdev.o rwlock.o setup.o
smp.o smp
boot.o string.o time.o trampoline.o traps.o usercopy.o x86_emulate.o
shadow32.o
acpi/built_in.o cpu/built_in.o genapic/built_in.o hvm/built_in.o
x86_32/built_in
.o
make[4]: Leaving directory `/var/tmp/xen-3.0-testing.hg/xen/arch/x86'
ld   -m elf_i386 -T xen.lds -N \
    boot/x86_32.o /var/tmp/xen-3.0-testing.hg/xen/common/built_in.o
/var/tmp/xen
-3.0-testing.hg/xen/drivers/built_in.o
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/
built_in.o -o /var/tmp/xen-3.0-testing.hg/xen/xen-syms
/var/tmp/xen-3.0-testing.hg/xen/common/built_in.o(.text+0x3fa0): In
function `gn
ttab_transfer':
/var/tmp/xen-3.0-testing.hg/xen/include/asm/shadow.h:1506: undefined
reference t
o `shadow_sync_and_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/common/built_in.o(.text+0x6e6b): In
function `gu
est_remove_page':
/var/tmp/xen-3.0-testing.hg/xen/include/asm/shadow.h:1526: undefined
reference t
o `shadow_sync_and_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/common/built_in.o(.text+0x7635): In
function `me
mory_exchange':
/var/tmp/xen-3.0-testing.hg/xen/include/asm/shadow.h:1526: undefined
reference t
o `shadow_sync_and_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/common/built_in.o(.text+0x7bed
    
):/var/tmp/xen-3.0
  
-testing.hg/xen/include/asm/shadow.h:1506: undefined reference to
`shadow_sync_a
nd_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/common/built_in.o(.text+0x87dd): In
function `do
_memory_op':
/var/tmp/xen-3.0-testing.hg/xen/include/asm/shadow.h:1506: undefined
reference t
o `shadow_sync_and_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/common/built_in.o(.text+0x9b3b): In
function `fr
ee_domheap_pages':
/var/tmp/xen-3.0-testing.hg/xen/common/page_alloc.c:672: undefined
reference to
`shadow_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0xb57b): In
function `
arch_memory_op':
/var/tmp/xen-3.0-testing.hg/xen/include/asm/shadow.h:1506: undefined
reference t
o `shadow_sync_and_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0xb6
    
79):/var/tmp/xen-3
  
.0-testing.hg/xen/include/asm/shadow.h:1526: undefined reference to
`shadow_sync
_and_drop_references'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0xedca): In
function `
do_mmu_update':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/mm.c:2172: undefined 
reference to
`shad
ow_l3_normal_pt_update'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x24e58): In
function
`hvm_copy':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/hvm.c:275: undefined
reference to `
gva_to_gpa'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x283e9): In
function
`send_pio_req':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/platform.c:705: undefined
reference
 to `gva_to_gpa'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x285e6): In
function
`send_mmio_req':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/platform.c:761: undefined
reference
 to `gva_to_gpa'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x2e3bc): In
function
`svm_set_cr0':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/svm/svm.c:1564: undefined
reference
 to `shadow_set_guest_paging_levels'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x2e
    
590):/var/tmp/xen-
  
3.0-testing.hg/xen/arch/x86/hvm/svm/svm.c:1556: undefined reference to
`shadow_s
et_guest_paging_levels'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x2f7a3): In
function
`svm_vmexit_handler':
/var/tmp/xen-3.0-testing.hg/xen/include/asm/mm.h:282: 
undefined reference
to `gv
a_to_gpa'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x2f7d6): In
function
`svm_vmexit_handler':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/svm/svm.c:2634: undefined
reference to `gva_to_gpa'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x30
    
750):/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/svm/svm.c:869:
  
undefined reference to `gva_to_gpa'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x35b3b): In
function`vmx_set_cr0':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/vmx/vmx.c:1425: undefined
reference to `shadow_set_guest_paging_levels'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x35
    
b78):/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/vmx/vmx.c:1433:
  
undefined reference to `shadow_set_guest_paging_levels'
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/built_in.o(.text+0x37114): In
function`vmx_vmexit_handler':
/var/tmp/xen-3.0-testing.hg/xen/arch/x86/hvm/vmx/vmx.c:767: undefined
referenceto `gva_to_gpa'
make[3]: *** [/var/tmp/xen-3.0-testing.hg/xen/xen-syms] Error 1
make[3]: Leaving directory `/var/tmp/xen-3.0-testing.hg/xen/arch/x86'
make[2]: *** [/var/tmp/xen-3.0-testing.hg/xen/xen] Error 2
make[2]: Leaving directory `/var/tmp/xen-3.0-testing.hg/xen'
make[1]: *** [install] Error 2

The issue seems to be related to the vmx code, which as I 
understand is
not useful on a non-VT enabled processor.  Can I exclude the 
vmx code from
the install?  Have my two days of research not turned up a proper
dependency?

Any help is appreciated.  A summary will be posted.

Cheers,
Aaron
    
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>