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

[Fedora-xen] Re: Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11



I removed 'xenfs' entry from /etc/fstab and it brought back to life Xen 3.4.1 (via xen-3.4.1-4.src.rpm) & Libvirt on the first F11 box, and didn't help on the second.
I would guess it's xen&pvops unrelated issue on second box.

Thanks.
Boris.

--- On Thu, 9/17/09, Gerd Hoffmann <kraxel redhat com> wrote:

From: Gerd Hoffmann <kraxel redhat com>
Subject: Re: Xend doesn't start at Xen 3.4.1 Dom(2.6.31 commit ebf47a1fe1aec22756c32fdba3dd94b05d5b8a84) on top of F11
To: "Boris Derzhavets" <bderzhavets yahoo com>
Cc: "Pasi Kärkkäinen" <pasik iki fi>, fedora-xen redhat com
Date: Thursday, September 17, 2009, 4:53 PM

  Hi,

> /etc/fstab contains 'xenfs' entry (3.4.1) in both cases

Hmm, where does that one come from?
It should not be there, it is not needed.
The xen packages never ever touch /etc/fstab.

>  mounting 'xenfs' at xend start up , what seems
> to be a default behaviour of the most recent 2.6.31 pvops enabled kernel.

Both F11 (3.3.x) and F12 (3.4.x) xen packages mount the filesystem automatically.  Very early xen packages with pv_ops kernel support didn't do that though, so maybe the /etc/fstab entry was added manually back then and was never deleted?

cheers,
  Gerd


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