Xen project Mailing List

RE: [Xen-devel] Help? Red Hat fails, Suse/Debian both work fine

To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>, "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>

From: Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>

Date: Fri, 03 Mar 2006 00:06:00 +0900

Cc: "yo.fujita" <yo.fujita@xxxxxxxxxxxxxxxx>, Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx

Delivery-date: Thu, 02 Mar 2006 15:08:21 +0000

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi, Anthony Sorry for my misunderstand. I understand your comment. I tried to use "warn_region0_address=1" and I had the below message. Is the message concerned with booting DomU? ========================================== *** CALLED SAL_SET_VECTORS. IGNORED... (XEN) SMP: Allowing 4 CPUs, 3 hotplug CPUs Built 1 zonelists Kernel command line: nomca nosmp console=tty0 console=ttyS1,115200,8n1 rhgb root=/dev/sda2 ro PID hash table entries: 4096 (order: 12, 131072 bytes) xen_pal_emulator: index=14 (XEN) Console: colour VGA+ 80x25 Delivering first extint to domain: isr=0x0, iip=0xa0000001004cf760 (XEN) vcpu_get_lid: WARNING: Getting cr.lid always returns zero (XEN) xen_pal_emulator: index=4 (XEN) xen_pal_emulator: index=2 (XEN) vcpu_translate: bad address 0x0, viip=0xa000000000010640, vipsr=0x121308126010, iip=0xa0000001004cfbe0, ipsr=0x101208126010 continuing ing (XEN) vcpu_translate: bad address 0x0, viip=0xa0000001004cfbe0, vipsr=0x1008126010, iip=0xa0000001004cfbe0, ipsr=0x101208126010 continuing g (XEN) vcpu_translate: bad address 0x0, viip=0xa0000001004cfbe0, vipsr=0x1008126010, iip=0xa0000001004cfbe0, ipsr=0x101208126010 continuing (XEN) vcpu_translate: bad address 0x0, viip=0xa0000001004cfbe0, vipsr=0x1008126010, iip=0xa0000001004cfbe0, ipsr=0x101208126010 continuing g (XEN) vcpu_translate: bad address 0x0, viip=0xa000000000010640, vipsr=0x121308126010, iip=0xa0000001004cfbe0, ipsr=0x101208126010 continuing ing (XEN) vcpu_translate: bad address 0x0, viip=0xa0000001004cfbe0, vipsr=0x1008126010, iip=0xa0000001004cfbe0, ipsr=0x101208126010 continuing (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... [...] (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdc0! continuing... (XEN) translate_domain_mpaddr: out-of-bounds dom0 mpaddr 0x7e6efdd0! continuing... (XEN) *** CALLED SAL_GET_STATE_INFO_SIZE. IGNORED... (XEN) vcpu_translate: bad address 0x0, viip=0x4000000000030540, vipsr=0x1308126030, iip=0x2000000000539fb0, ipsr=0x121308126030 continuing g (XEN) vcpu_translate: bad address 0x0, viip=0x2000000000539fb0, vipsr=0x213081a6010, iip=0x2000000000539fb0, ipsr=0x1213081a6010 continuing ng (XEN) vcpu_translate: bad address 0x0, viip=0x2000000000539fb0, vipsr=0x213081a6010, iip=0x2000000000539fb0, ipsr=0x1213081a6010 continuing (XEN) ###allocating rid_range, domain f000000007ff9fa0: starting_rid=80000, ending_rid=c0000 (XEN) arch_domain_create: domain=f000000007ff9fa0 (XEN) arch_set_info_guest (XEN) ACPI 2.0=0x598domain mem: type=2, attr=0x8, range=[0x0000000000000000-0x0000000000100000) (1MB) (XEN) domain mem: type=13, attr=0x8, range=[0x0000000000100000-0x0000000000200000) (1MB) (XEN) domain mem: type=7, attr=0x8, range=[0x0000000000200000-0x000000001fff4000) (509MB) (XEN) domain mem: type=0, attr=0x0, range=[0x0000000000000000-0x0000000000000000) (0MB) (XEN) domain mem: type=0, attr=0x0, range=[0x0000000000000000-0x0000000000000000) (0MB) (XEN) initrd start 0x4b28000 initrd size 0x2fa600 (XEN) Sync i/d cache for guest SUCC Best Regards, Akio Takebe >>From: Akio Takebe >>Sent: 2006ト\xF3ヤツ2ネユ 8:44 >>Thank you for your advice. >>I checked retun value of mmap(), and it is not NULL. >>I'll check vcpu_translate(). > >Sorry for not clear, we need to check if the return address of mmap is in >region0, >Current vcpu_translate may not handle all scenarios when fault address >is in region 0. > >Thanks, >Anthony _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.