[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen 3.3.0 + intrepid domU (2.6.27-7-server) + >4gb ram problem


  • To: xen-users@xxxxxxxxxxxxxxxxxxx, Krzysztof Chojnowski <notch@xxxxxxxxxx>
  • From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
  • Date: Mon, 27 Oct 2008 09:09:47 -0700 (PDT)
  • Cc:
  • Delivery-date: Mon, 27 Oct 2008 09:11:35 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Message-ID; b=JZ4odWS1b5VlcDXwF+NNXP7rOlMI4H9tt1ligmrQBa1jeS5hj8aSN3KCLlQRM8DeHM4Fuo0CR96IhLAOVZG4qSJ5rk+Y3jkQFeQkxM17ikv3f9FSd2smlvmpZzhpo+0wv4zmIPv95MDqbJEkr0AV55rhT3r0HWLbfO4UYzsdr/s=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Sorry, does
vmlinuz-2.6.27-7-server
support  pv_ops in DomU ?

--- On Mon, 10/27/08, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-users] xen 3.3.0 + intrepid domU (2.6.27-7-server) + >4gb ram problem
To: xen-users@xxxxxxxxxxxxxxxxxxx, "Krzysztof Chojnowski" <notch@xxxxxxxxxx>
Date: Monday, October 27, 2008, 12:05 PM



--- On Mon, 10/27/08, Krzysztof Chojnowski <notch@xxxxxxxxxx> wrote:
From: Krzysztof Chojnowski <notch@xxxxxxxxxx>
Subject: [Xen-users] xen 3.3.0 + intrepid domU (2.6.27-7-server) + >4gb ram problem
To: xen-users@xxxxxxxxxxxxxxxxxxx
Date: Monday, October 27, 2008, 9:51 AM

Hi,

we're using Xen 3.3.0 on Debian Etch with 2.6.18.8 kernel from xen.org
on dom0. We have problems starting Intrepid domU (using Intrepid's
kernel 2.6.27-7-server) if we give more than 4GB of memory to this domain.
Using memory = '4096' works perfectly, but changing it to
'4097' already
gives an error. Can anyone put some light on this?

domU
config:
*************************************************
I guess, that's not a xenified kernel and ramdisk
*************************************************
kernel = '/etc/xen/kernels/amd64/vmlinuz-2.6.27-7-server'
ramdisk = '/etc/xen/kernels/amd64/initrd.img-2.6.27-7-server'
root = '/dev/xvda3 ro'
extra = '2 console=hvc0'
memory = '4097'
disk = [ 'phy:/dev/vg0/intrepid-new,xvda,w' ]
vif = [ 'bridge=xenbr0,mac=00:16:3e:7a:52:c0' ]
vcpus = '4'
name = 'intrepid-new'





console output:
[ 0.010000] ------------[ cut here ]------------
[ 0.010000] kernel BUG at
/build/buildd/linux-2.6.27/arch/x86/xen/enlighten.c:836!
[ 0.010000] invalid opcode: 0000 [1] SMP
[ 0.010000] CPU 0
[ 0.010000] Modules linked in:
[ 0.010000] Pid: 0, comm: swapper Not tainted
2.6.27-7-server #1
[ 0.010000] RIP: e030:[<ffffffff8020b182>] [<ffffffff8020b182>]

pin_pagetable_pfn+0x52/0x70
[ 0.010000] RSP: e02b:ffffffff806f5c88 EFLAGS: 00010282
[ 0.010000] RAX: 00000000ffffffea RBX: 000000000000f000 RCX:
0000000000000000
[ 0.010000] RDX: 0000000000000000 RSI: 0000000000000001 RDI:
ffffffff806f5c88
[ 0.010000] RBP: ffffffff806f5ca8 R08: ffff880100002100 R09:
0000000000000000
[ 0.010000] R10: 0000000000007ff0 R11: 0000000000000000 R12:
0000000000000003
[ 0.010000] R13: 000000000010000f R14: ffffc20000403000 R15:
ffffffff806f5dc8
[ 0.010000] FS: 0000000000000000(0000) GS:ffffffff806e0a80(0000)
knlGS:0000000000000000
[ 0.010000] CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 0.010000] CR2: 0000000000000000 CR3: 0000000000201000 CR4:
0000000000000660
[ 0.010000] DR0: 0000000000000000 DR1: 0000000000000000 DR2:

0000000000000000
[ 0.010000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 0.010000] Process swapper (pid: 0, threadinfo ffffffff806f4000,
task ffffffff80647340)
[ 0.010000] Stack: ffff880100000000 0000000000501ee5
00000001806f5cc8 000000000000f000
[ 0.010000] ffffffff806f5cd8 ffffffff8020b22d ffffc20000401000
ffff88010000f000
[ 0.010000] ffff88010000e010 ffffc20000401000 ffffffff806f5ce8
ffffffff8020b293
[ 0.010000] Call Trace:
[ 0.010000] [<ffffffff8020b22d>] xen_alloc_ptpage+0x8d/0xa0
[ 0.010000] [<ffffffff8020b293>] xen_alloc_pte+0x13/0x20
[ 0.010000] [<ffffffff802bef21>] __pte_alloc_kernel+0x61/0xc0
[ 0.010000] [<ffffffff802cbdf4>] map_vm_area+0x2d4/0x350
[ 0.010000] [<ffffffff802cc5f0>] __vmalloc_area_node+0x140/0x1a0
[ 0.010000] [<ffffffff80740856>]
?
alloc_large_system_hash+0x24c/0x2b0
[ 0.010000] [<ffffffff802cc6f1>] __vmalloc_node+0xa1/0xb0
[ 0.010000] [<ffffffff80740856>] ?
alloc_large_system_hash+0x24c/0x2b0
[ 0.010000] [<ffffffff80740856>] ?
alloc_large_system_hash+0x24c/0x2b0
[ 0.010000] [<ffffffff802cc511>] __vmalloc_area_node+0x61/0x1a0
[ 0.010000] [<ffffffff802cb8db>] ? __get_vm_area_node+0xcb/0x220
[ 0.010000] [<ffffffff80740856>] ?
alloc_large_system_hash+0x24c/0x2b0
[ 0.010000] [<ffffffff802cc6f1>] __vmalloc_node+0xa1/0xb0
[ 0.010000] [<ffffffff80740856>] ?
alloc_large_system_hash+0x24c/0x2b0
[ 0.010000] [<ffffffff80501ffd>] ? _spin_unlock_irqrestore+0x1d/0x30
[ 0.010000] [<ffffffff802cc777>] __vmalloc+0x17/0x20
[ 0.010000] [<ffffffff80740856>] alloc_large_system_hash+0x24c/0x2b0
[ 0.010000] [<ffffffff807420be>]
vfs_caches_init+0x11d/0x16a
[ 0.010000] [<ffffffff8071eda9>] start_kernel+0x2a7/0x3b5
[ 0.010000] [<ffffffff807285e0>] ? reserve_early+0x30/0x3b
[ 0.010000] [<ffffffff8071e2b9>] x86_64_start_reservations+0x99/0xb6
[ 0.010000] [<ffffffff807256e2>] xen_start_kernel+0x493/0x4ee
[ 0.010000]
[ 0.010000]
[ 0.010000] Code: 48 b8 ff ff ff 7f ff ff ff ff 48 21 c2 48 89 55 e8
48 8d 7d e0 be 01 00 00 00 31 d2 41 ba f0 7f 00 00 e8 c2 e1 ff ff 85 c0
74 0e <0f> 0b eb fe 66 2e 0f 1f 84 00 00 00 00 00 c9 c3 66 66 66 66 66
[ 0.010000] RIP [<ffffffff8020b182>] pin_pagetable_pfn+0x52/0x70
[ 0.010000] RSP <ffffffff806f5c88>
[ 0.010016] ---[ end trace 4eaa2a86a8e2da22 ]---
[ 0.010023] Kernel panic - not syncing: Attempted to kill the idle task!



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

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

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

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.