similar to: Xen debugging question (x86-64)

I cleaned up the top level makefile in the tools directory. No major changes. Except I have it so that ioemmu is compiled only with x86_32. Signed-off-by: Jerone Young <jyoung5@us.ibm.com> --- tools/Makefile.orig 2005-03-17 21:03:44.000000000 -0600 +++ tools/Makefile 2005-03-22 15:05:20.000000000 -0600 @@ -1,37 +1,33 @@ +XEN_ROOT = ../ +include $(XEN_ROOT)/tools/Rules.mk -all: -

Signed-off-by: Jerone Young <jyoung5@us.ibm.com> -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Variable guest_va is declared as a long* . It takes values that are cast as unsigned long* . GCC 4 picks up on this. This patch changes the declaration of guest va to be an unsigned long* and fixes the problem. Signed-off-by: Jerone Young <jyoung5@us.ibm.com> -- Jerone Young IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157)

x86 ( 32bit) is the only architecture that uses Fast trap vector offset ( fast_trap_idx ). This makes sure that x86 is the only architecture to use this variable. Signed-off-by: Jerone Young <jyoung5@us.ibm.com> Jerone Young Open Virtualization IBM Linux Technology Center jyoung5@us.ibm.com 512-838-1157 (T/L: 678-1157)

This allows tools in the python directory to properly link to libxenstore.a on x86-64. --- tools/xenstore/Makefile.orig 2005-06-09 12:56:34.000000000 -0500 +++ tools/xenstore/Makefile 2005-06-09 13:48:06.000000000 -0500 @@ -20,6 +20,9 @@ BASECFLAGS+= -I. CFLAGS+=$(BASECFLAGS) +ifeq ($(XEN_TARGET_ARCH),x86_64) +CFLAGS += -fPIC +endif LDFLAGS=$(PROFILE) -L$(XEN_LIBXC)

Fixes sign issue with gcc4. Signed-off-by: Jerone Young <jyoung5@us.ibm.com> --- xen/arch/x86/vmx_io.c.old 2005-06-24 14:40:00.000000000 -0500 +++ xen/arch/x86/vmx_io.c 2005-06-24 14:41:54.000000000 -0500 @@ -181,7 +181,7 @@ static void load_cpu_user_regs(struct cp __vmwrite(GUEST_RIP, regs->rip); } -static inline void __set_reg_value(long *reg, int size, long value)

I am not able to build the latest x86_64 xen-unstable on SLES9 SP1 x86_64. Here is the build output. Am I doing anything wrong here? Aravindh gcc -DPIC -m64 -Wall -Werror -O3 -fno-strict-aliasing -I ../../tools/libxutil -I. -Wp,-MD,.xc_ptrace.opic.d -fPIC -c -o xc_ptrace.opic xc_ptrace.c In file included from /usr/include/asm/sigcontext.h:4, from

Doing some janitorial (you cleaning the flooded toilets and such) work today. I have come across this line of code that really I''m not sure what the intent was..in xen/include/sched.h #define hypercall_preempt_check() (unlikely( \ softirq_pending(smp_processor_id()) | \ (!!current->vcpu_info->evtchn_upcall_pending & \

Can''t seem to fully boot a domU on either EM64T or Opteron with x86_64 xen-unstable. Both systems'' report this from xen: (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000100. (XEN) (file=traps.c, line=872) Non-priv domain attempted WRMSR(00000000c0000102. (XEN) (file=traps.c, line=880) Non-priv domain attempted RDMSR(00000000c0000080. They boot

I successfully installed Xen 2.0.4 from source on a Slackware 10 system. I installed grub, got that working and all. But when I boot the dom0 kernel, I get: cmd 0x5a timed out hdc: lost interrupt My hdc is my dvd burner... when I applied a kernel option of "hdc=ide-scsi" it seemed to have skipped over it but recieved the same error on hdd ... I''ve tried recompiling with

During boot of dom0, I get the following. Box is remote, so I''m now waiting for proxy power button pusher ;-) tg3 init fails doing dma_alloc_coherent (I assume this is from tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> dma_alloc_coherent). Looks like an issue with the amount of memory in dom0. Is this known? thanks, -chris root (hd0,0) Filesystem type is ext2fs,

The use of "packed" attribute is bad for PPC. PPC Xen build checks for this and will not build if this is in the code. Signed-off-by: Jerone Young <jyoung5@us.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi all, With the new vm-tools we are trying to get top like capabilities going correctly. Currently we have a program vm-list that has some of this capability but is dependent on the cpu time given by libxc calls (xc_get_dom_info & xc_domain_get_cpu_usage). These two functions give you how much time (in nanoseconds, why is this not documented) the domain has been actively used. Approaches:

I''m to porting a lightweight kernel to Xen 3.0.4-x86_64 and have run into a problem while setting the PML4. Xen complains that it has a bad type of ''PGT_writable_page'' (e8000001), while it expects 80000000. However, I''m almost certain that this is not the case. I added a routine to do a depth first search of the four page table levels looking for this machine

I''m a newbie. :) I followed the steps written by Jerone Young: http://sourceforge.net/mailarchive/message.php?msg_id=10562241 but i found an error at the 17th step: 17. mkinitrd /boot/initrd-2.6.10-xen0.img 2.6.10-xen0 it said:"No module ata_piix found for kernel 2.6.10-xen0, aborting." so I commented the line of "module /boot/initrd-2.6.10-xen0.img" in the

Fixes made in version 2: 1) Use PML4[257] for ioremap of PCI mmcfg. As full 16-bit segment support would require 44-bits. Since each slot only has 39-bits, we support 2048 PCI segments for now. This can be easily expanded if deemed necessary in the future. 2) Integrated PCI mmcfg access with existing PCI config interface for x86_64. Use MMCFG interface if offset is greater than 256.

I am seeing a problem with Dom0 crashing on x86_64 whenever I create a DomU. I''ve done some more testing, and it appears that this problem is somehow related to networking. Dom0 crashes as soon as the networking services are started when DomU is coming up. As an experiment, I brought up DomU without networking, and it stayed up. As soon as I started DomU with networking enabled, however,

Hello! I`m trying to boot a via sata machine with xen 3.0 with no sucess. It just freezes at this point: ********* ACPI: PCI Interrupt 0000:00:0f.0[B] -> Link [LNKB] -> GSI 10 (level,low) -> IRQ 10 sata_via (0000:00:0f.0): routed to hard irq line 10 ata1: SATA max UDMA/133 cmd 0xEFE0 ctl 0xEFAE bmdma 0xEF90 irq 10 ata2: SATA max UDMA/133 cmd 0xEFA0 ctl 0xEFAA bmdma 0xEF98 irq 10 ata1:

I have always needed the rm_nx_xd patch to boot Xen / Dom0 on the ES7000 x86_64 but the system boots without any issues on plain vanilla Linux 2.6. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel- > bounces@lists.xensource.com] On Behalf Of Keir Fraser > Sent: Thursday, August 18, 2005 4:49 AM > To: Nakajima, Jun > Cc: Jerone Young;

''-Wdeclaration-after-statement'' isn''t supported by gcc 3.3 which is what I am currently using. It was introduced into Config.mk in changeset 7973:c7508abc5b6b. I backed out the changes and everything appears to be building okay. > -----Original Message----- > From: xen-devel-bounces@lists.xensource.com > [mailto:xen-devel-bounces@lists.xensource.com] On