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/
Home Products Support Community News


Re: [Xen-users] gentoo as dom0 on xen fails...

To: pjb@xxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] gentoo as dom0 on xen fails...
From: Molle Bestefich <molle.bestefich@xxxxxxxxx>
Date: Tue, 22 Nov 2005 17:36:32 +0100
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 22 Nov 2005 16:36:34 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=YyxFmoraIq+p6WaJRqzyISN86Khp8NZE7qw646lt5UI0rhonyxS9+6L8TntxhMruYvlPyCh0UmNejL9NmwGkhYn9RJYKj3JRsl0Q3NS7KwixUDW6tQnCw3CYGZi8Zf/0UpjBQoa5FsBFmZfOkrxNnD5mway+FPq9wTTmlJ4LA2Q=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051122033056.2C9F3889B@xxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20051122033056.2C9F3889B@xxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I have a setup very similar to yours, but mine runs the clock script
just fine.  Odd.

You can disable it with:
# rc-update del clock boot

Pascal Bourguignon wrote:
> I wanted to boot gentoo on xen, but it doesn't work.
> What can I do?
>  * Setting system clock to hardware clock [UTC] ...
> Oops: 0002 [#1]
> Modules linked in: rtc tg3 natsemi unix
> CPU:    0
> EIP is at __mod_timer+0xec/0x2b0
> Process events/0 (pid: 3, threadinfo=c1166000 task=c048d020)
> Call Trace:
>  [<c012a44b>] mod_timer+0x2b/0xa0
>  [<c02e0a26>] __netdev_watchdog_up+0x36/0x60
>  [<c02e0a74>] dev_watchdog_up+0x24/0x40
>  [<c02e1280>] dev_activate+0xc0/0x130
>  [<c02db2be>] linkwatch_run_queue+0xee/0x180
>  [<c02db379>] linkwatch_event+0x29/0x70
>  [<c0133f64>] worker_thread+0x214/0x3e0
>  [<c033890d>] schedule+0x3bd/0x790
>  [<c02db350>] linkwatch_event+0x0/0x70
>  [<c011b380>] default_wake_function+0x0/0x20
>  [<c011b380>] default_wake_function+0x0/0x20
>  [<c0133d50>] worker_thread+0x0/0x3e0
>  [<c01396b8>] kthread+0xa8/0xe0
>  [<c0139610>] kthread+0x0/0xe0
>  [<c01071e5>] kernel_thread_helper+0x5/0x10
>  <0>Kernel panic - not syncing: Fatal exception in interrupt

Xen-users mailing list

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