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] some little problems with lenny amd64 and xen.

Subject: Re: [Xen-users] some little problems with lenny amd64 and xen.
From: Thomas Halinka <lists@xxxxxxxxx>
Date: Mon, 24 Nov 2008 00:57:22 +0100
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 23 Nov 2008 15:58:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <ab520d140811231110k1ae53117jcdeed5d4519fa3b4@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <ab520d140811231110k1ae53117jcdeed5d4519fa3b4@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi Mauro,

Am Sonntag, den 23.11.2008, 20:10 +0100 schrieb Mauro:
> I've install debian lenny amd64 with xen kernel.
> It starts and I create some domx.
> The first little problem is that I can't access via ssh to any of my
> domx.
> The problem is solved by manually installing udev package, in etch
> there's no need to manually install udev package.


> The second problem is this kernel message in my domx when it boots:
> "
> platform rtc_cmos: registered platform RTC device (no PNP device
> found)
> pnp: the driver 'rtc_cmos' has been registered
> rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
> pnp: the driver 'rtc_cmos' has been unregistered
> drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> ...
> Cannot access the Hardware Clock via any known method.
> "
> I can't resolve this last problem.
> How can it be solved?

domUs do not have any HW-Clock, so just deactivating this solves your

If running Debian/Ubuntu guest the following should fix this

  # update-rc.d -f hwclock.sh remove

after a reboot of the domU



Xen-users mailing list