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

[Xen-bugs] [Bug 903] New: Xen Guest fails to boot when physical memory i

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 903] New: Xen Guest fails to boot when physical memory is not limited to less than 4 GB.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Fri, 16 Feb 2007 11:17:21 -0800
Delivery-date: Fri, 16 Feb 2007 11:19:01 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx
http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=903

           Summary: Xen Guest fails to boot when physical memory is not
                    limited to less than 4 GB.
           Product: Xen
           Version: unstable
          Platform: x86
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: hawklan@xxxxxxxxxxx


I am using Xen 3.0.3 on Fedora Core 6 32-bit.
The hardware is a Dell PowerEdge 2950, Xeon 5110 dual-processor, dual-core with
8GB of RAM.

If I limit the memory available using mem=4000M in grub.conf, the guest OS will
boot without a problem.  If I use more than 4GB of RAM, the guest OS will not
boot up.  This is 100% reproducable, and has been verified with numberous guest
OS images, although all of the guest images are Fedora Core 6 based and
constucted with xenguest-install and virt-install on the Dom0.

The information provided by the guest OS follows:

------------[ cut here ]------------
kernel BUG at arch/i386/mm/hypervisor.c:70!
invalid opcode: 0000 [#1]
SMP 
last sysfs file: /block/ram0/dev
Modules linked in: dm_snapshot dm_zero dm_mirror dm_mod xenblk ext3 jbd
ehci_hcd ohci_hcd uhci_hcd
CPU:    0
EIP:    0061:[<c0414625>]    Not tainted VLI
EFLAGS: 00010282   (2.6.18-1.2798.fc6xen #1) 
EIP is at xen_l2_entry_update+0x7c/0x8b
eax: ffffffea   ebx: c0920d10   ecx: 00000001   edx: 00000000
esi: 00007ff0   edi: 00000000   ebp: 00000aed   esp: c0920d08
ds: 007b   es: 007b   ss: 0069
Process lvm (pid: 248, ti=c0920000 task=c0923870 task.ti=c0920000)
Stack: c7d84067 00000000 170c9df8 00000002 c7d84067 00000000 00000000 c7d84067 
       00000000 c045356c ffffffff ffffffff c09a8df8 c0764840 00000061 80000000 
       000009a8 00000000 00000000 00000001 c04537ad c115d365 c0cf6f40 00000063 
Call Trace:
 [<c045356c>] __pte_alloc+0x1a2/0x21d
 [<c04537ad>] __handle_mm_fault+0x1c6/0x10bf
 [<c060a17f>] do_page_fault+0x6f6/0xc3c
 [<c040502b>] error_code+0x2b/0x30
DWARF2 unwinder stuck at error_code+0x2b/0x30

Leftover inexact backtrace:

 [<c041007b>] do_sys_vm86+0x26d/0x38b
 [<c04df660>] __copy_to_user_ll+0xcf/0xda
 [<c0482119>] seq_read+0x1e4/0x277
 [<c0481f35>] seq_read+0x0/0x277
 [<c04665ec>] vfs_read+0xa6/0x157
 [<c0466a5b>] sys_read+0x41/0x67
 [<c0404ea7>] syscall_call+0x7/0xb
 =======================
Code: 01 00 00 00 89 44 24 0c 8b 04 24 8d 5c 24 08 89 74 24 08 be f0 7f 00 00
89 54 24 14 31 d2 89 44 24 10 e8 ff c9 fe ff 85 c0 79 08 <0f> 0b 46 00 58 41 62
c0 83 c4 18 5b 5e 5f c3 57 05 00 00 00 40 
EIP: [<c0414625>] xen_l2_entry_update+0x7c/0x8b SS:ESP 0069:c0920d08
 <3>BUG: soft lockup detected on CPU#0!
 [<c040571a>] dump_trace+0x69/0x1af
 [<c0405878>] show_trace_log_lvl+0x18/0x2c
 [<c0405e18>] show_trace+0xf/0x11
 [<c0405e47>] dump_stack+0x15/0x17
 [<c0441961>] softlockup_tick+0xad/0xc4
 [<c0409290>] timer_interrupt+0x54b/0x593
 [<c0441be6>] handle_IRQ_event+0x27/0x51
 [<c0441ca6>] __do_IRQ+0x96/0xf2
 [<c0406ca8>] do_IRQ+0x9e/0xbc
 =======================
BUG: spinlock lockup on CPU#0, lvm/248, c0764894 (Not tainted)
 [<c040571a>] dump_trace+0x69/0x1af
 [<c0405878>] show_trace_log_lvl+0x18/0x2c
 [<c0405e18>] show_trace+0xf/0x11
 [<c0405e47>] dump_stack+0x15/0x17
 [<c04e04a7>] _raw_spin_lock+0xbf/0xdc
 [<c041195d>] mm_unpin+0x17/0x2b
 [<c0411adc>] _arch_exit_mmap+0x16b/0x173
 [<c0457436>] exit_mmap+0x1c/0xf6
 [<c041a441>] mmput+0x34/0x7a
 [<c041ee6d>] do_exit+0x20b/0x776
 [<c0405db9>] die+0x289/0x2ae
 [<c04063c2>] do_invalid_op+0xa2/0xab
 [<c040502b>] error_code+0x2b/0x30
DWARF2 unwinder stuck at error_code+0x2b/0x30

Leftover inexact backtrace:

 [<c0414625>] xen_l2_entry_update+0x7c/0x8b
 [<c045356c>] __pte_alloc+0x1a2/0x21d
 [<c04537ad>] __handle_mm_fault+0x1c6/0x10bf
 [<c0608c2a>] _read_unlock_irq+0x5/0xa
 [<c044722f>] find_get_page+0x36/0x3b
 [<c0449d44>] filemap_nopage+0x19a/0x33e
 [<c060a17f>] do_page_fault+0x6f6/0xc3c
 [<c04b714a>] avc_has_perm+0x4e/0x58
 [<c04b77cb>] inode_has_perm+0x5b/0x63
 [<c047a3be>] __d_path+0xc5/0x156
 [<c0609a89>] do_page_fault+0x0/0xc3c
 [<c040502b>] error_code+0x2b/0x30
 [<c041007b>] do_sys_vm86+0x26d/0x38b
 [<c04df660>] __copy_to_user_ll+0xcf/0xda
 [<c0482119>] seq_read+0x1e4/0x277
 [<c0481f35>] seq_read+0x0/0x277
 [<c04665ec>] vfs_read+0xa6/0x157
 [<c0466a5b>] sys_read+0x41/0x67
 [<c0404ea7>] syscall_call+0x7/0xb
 =======================


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs

<Prev in Thread] Current Thread [Next in Thread>