From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Novotny Subject: Re: Xen-4.1-unstable hypervisor booting error Date: Mon, 27 Sep 2010 12:46:46 +0200 Message-ID: <4CA07616.6030903@redhat.com> References: <770918.29614.qm@web56101.mail.re3.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <770918.29614.qm@web56101.mail.re3.yahoo.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Boris Derzhavets Cc: "'xen-devel@lists.xensource.com'" List-Id: xen-devel@lists.xenproject.org Thanks a lot Boris, adding dom0_mem setting to 1G (1024M respectively) made it working fine so I guess there's a wrong default setting for dom0_mem, at least for x86_64 architecture. Thanks again Boris! Michal On 09/27/2010 11:05 AM, Boris Derzhavets wrote: > Could you try:- > > /boot/xen.gz dom0_mem=1024M > . . . . . . . . . . . > > Boris. > P.S. I had the same issue. > > > --- On *Mon, 9/27/10, Michal Novotny //* wrote: > > > From: Michal Novotny > Subject: [Xen-devel] Xen-4.1-unstable hypervisor booting error > To: "'xen-devel@lists.xensource.com'" > Date: Monday, September 27, 2010, 3:47 AM > > Hi, > I've installed latest PVops kernel 2.6.32.21 (upgraded from > 2.6.32.15 using the very same kernel build configuration - i.e. > copied the config-2.6.32.15 file to the kernel source directory) > and I can boot without hypervisor (using the standard > kernel/initrd directives in grub) but not with the hypervisor > since it fails. > > Call trace is: > [ ] ? check_events+0x12/0x20 > [ ] ? lock_acquire+0xe3/0xf2 > [ ] ? balloon_process+0x0/0x555 > [ ] worker_thread+0x1b2/0x2b1 > [ ] ? worker_thread+0x159/0x2b1 > [ ] ? autoremove_wake_function+0x0/0x3d > [ ] ? worker_thread+0x0/0x2b1 > [ ] kthread+0x6e/0x76 > [ ] child_rip+0xa/0x20 > [ ] ? restore_args+0x0/0x30 > [ ] ? kthreadd+x0ed/0x10f > [ ] ? xen_restore_fl_direct_end+0x0/0x1 > [ ] ? child_rip+0x0/0x20 > > Code: 49 c1 fd 03 4c 8b 34 d5 e0 a6 61 82 4c 0f af e8 80 3d 3b 65 > 5a 00 00 75 0d 4c 89 ef e8 32 fa d3 ff 48 ff c0 75 05 45 31 ff eb > 5a <0f> 0b eb fe 4c 89 f6 48 89 df e8 4b 03 d4 ff 48 3b 1d 97 f7 1c > > RIP [ ] balloon_process+0x1a8/0x555 > RSP [ ] > --- [ end trace e93713a9d40cd06c ] --- > events/0 used greatest stack depth: 4664 bytes left > > And the host is stuck and can't boot. > > Was it OK to use the config from 2.6.32.15 for 2.6.32.21 build or > any pointers what may be going on? The kernel/system is x86_64 > system running on RHEL-5 with the PVops kernel now but as I said, > it can't boot with the hypervisor but everything is fine (except > Xen) when booting without the hypervisor. > > Thanks, > Michal > > -- Michal Novotny >, RHCE > Virtualization Team (xen userspace), Red Hat > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > > http://lists.xensource.com/xen-devel > > -- Michal Novotny, RHCE Virtualization Team (xen userspace), Red Hat