No Response from any of the involved parties..
Setting to incomplete
Regards,
\sh
** Changed in: fai (Ubuntu)
Status: Triaged => Incomplete
** Changed in: xen-3.1 (Ubuntu)
Status: Opinion => Incomplete
** Changed in: fai (Ubuntu)
Status: Incomplete => Won't Fix
** Change
I don't like to have this bug report left as incomplete and rott
somewhere in the deep dark space of LP trashbin ;)
If someone could test this with latest fai on ubuntu maverick or ubuntu
lucid, that would be a plus.
I*m, on the other hand, will raise this issue with upstream
** Changed in: fai
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The version of Ubuntu your using is in End of Life
status. More information may be found at:
https://wiki.ubuntu.com/Releases As well, fai (ubuntu) is updated and
issue you reported should be reproducible with the l
On Thu, Mar 27, 2008 at 10:42 AM, Reinhard Tartler <[EMAIL PROTECTED]> wrote:
> I'm inclined to reject the bugtask for fai. It is true that fai is
> affected by this, however it seems that the hypervisor is buggy here, so
> there is not that much we can do about this from the fai side
It could b
I'm inclined to reject the bugtask for fai. It is true that fai is
affected by this, however it seems that the hypervisor is buggy here, so
there is not that much we can do about this from the fai side
** Changed in: fai (Ubuntu)
Assignee: Ubuntu FAI Developers (fai) => (unassigned)
--
dpkg
Interestingly, here is the result of "fai-setup -v" on a Feisty xendomu.
It tried to continue past the error, and aborted in a different place
than Gutsy:
Setting up file (4.19-1ubuntu2) ...
Setting up cfengine2 (2.1.20-1) ...
Making a key pair for cfengine, please wait, this could take a minute.
we had a local LUG event where I wanted to give a workshop about FAI,
were we were using Xen as well. Now I remember that I experienced a
segfault pretty similar to this one (if not the same).
TBH, I cannot imagine what the fai package could do wrong here and
therefore would suspect Xen.
** Summa
I'll look into it and let you know what I find.
On Nov 7, 2007 12:16 AM, Castang Jerome <[EMAIL PROTECTED]> wrote:
> Alvin Cura a écrit :
> > Jerome,
> >
> > What are you running for xendom0? I am beginning to suspect running
> > gutsy on a feisty xendom0 is part of the issue.
> >
> > Thanks,
>
Alvin Cura a écrit :
> Jerome,
>
> What are you running for xendom0? I am beginning to suspect running
> gutsy on a feisty xendom0 is part of the issue.
>
> Thanks,
> - alvinc
>
>
I am running a CentOS 5.0 (with last updates).
Looking a this problems shows that there is one another.
Sometimes
Jerome,
What are you running for xendom0? I am beginning to suspect running
gutsy on a feisty xendom0 is part of the issue.
Thanks,
- alvinc
--
dpkg seg-fault with fai-nfsroot
https://bugs.launchpad.net/bugs/159536
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Changed in: fai (Ubuntu)
Assignee: (unassigned) => Ubuntu FAI Developers (fai)
--
dpkg seg-fault with fai-nfsroot
https://bugs.launchpad.net/bugs/159536
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailin
Further analysis seems to point at a xen-only problem.
I have installed Gutsy Server from the CD image on a VMware VM and
installed the ppa FAI with no errors:
// * //
[EMAIL PROTECTED]:~# fai-setup -v
Using configuration files from /etc/fai
Creating FAI nfsroot in /srv/fai/nfsroot/live/file
Gutsy (Ubuntu 7.10). Host is a Dell 2970.
On Nov 6, 2007 1:03 AM, Castang Jerome <[EMAIL PROTECTED]> wrote:
> Alvin Cura a écrit :
>
> I am in the same situation.
> I reproduce the same error on a xen domU.
> Dom0 is a CentOS 5 (last updates).
>
> Which OS do you use as Dom0 ?
>
--
dpkg seg-
Alvin Cura a écrit :
> I just reproduced it.
>
> --- BEGIN CUT-N-PASTE
>
> [EMAIL PROTECTED]:/etc/fai# fai-setup -v
> Using configuration files from /etc/fai
> Creating FAI nfsroot in /srv/fai/nfsroot/live/filesystem.dir.
> By default it needs more than 330 MBytes disk space.
> This may take a lon
I just reproduced it.
--- BEGIN CUT-N-PASTE
[EMAIL PROTECTED]:/etc/fai# fai-setup -v
Using configuration files from /etc/fai
Creating FAI nfsroot in /srv/fai/nfsroot/live/filesystem.dir.
By default it needs more than 330 MBytes disk space.
This may take a long time.
Creating base system using de
I just installed a clean minimal gutsy via netinst, and first created an
nfsroot for feisty, then for gutsy. Both went without problems.
perhaps you can elaborate more about your system? how did you install
it?
perhaps you can reproduce the error in a virtualbox or vmware image?
--
dpkg seg-fau
Hi Jerome,
is this a fresh FAI install or did you upgrade from earlier versions?
Can you try to chroot to the fai NFS root directory
(the default is /srv/fai/nfsroot/live/filesystem.dir) and run
apt-get install --reinstall install fai-nfsroot
If this does not give any hint what's going wro
** Changed in: fai (Ubuntu)
Status: New => Incomplete
--
dpkg seg-fault with fai-nfsroot
https://bugs.launchpad.net/bugs/159536
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
18 matches
Mail list logo
