All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandi Romih <romihs.forums@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: Failed to run bootloader
Date: Thu, 26 Apr 2012 11:40:10 +0200	[thread overview]
Message-ID: <CAFoWEVNPqez_eR2jLOu0DtbH+-qDsWJyuzfxpC1QMzgzLqQwbQ@mail.gmail.com> (raw)
In-Reply-To: <1335425428.4881.52.camel@dagon.hellion.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 2365 bytes --]

So this is now a different failure mode to the one which you originally
> reported (pygrub failed)?
>

I am not sure if it is a different fault.
It started with the bootloader: -3 error. In my search to find the possible
cause for this error, I found that there was a connection with the vif line
in my config file.
I have tried two different methods of starting the vm (one with pybrub and
the second without), and if my memory serves me right, removing the vif
from the config file resulted in the vm operating as it should.

With the bootloader = "/usr/bin/pygrub" line in the file, the vm boots if
the vif line is not there, and causes the bootloader: -3 error when the vif
line is present.
Without the bootloader line, using kernel, ramdisk and extra options, the
vm starts to boot. However, if the vif line is present, the install pauses
and stops at approximately 28 CPU seconds (in my case), which is midway
through its hardware detection procedure. The vm just stays in b state.
Without the vif line, the vm boots all the way without pausing at the 28
CPU seconds.


>
> What does your guest config look like now that you have resolved the
> pygrub issue?
>

* *I will send you the two different cfg files I have used, when I get home
later.


>
> Can you provide a full log of the failing boot with a vif enabled to the
> point of the hang?
>
>
Will do this later too.


> Are your hotplug scripts set up properly?
>

That I dont know, I have not dealt with these scripts yet since beginning
my 'adventures' with xen.
How do I know if they are correct, or if they need to be modified?


>
> What does "brctl show" say while the guest is running (with the vif
> enabled)?
>
> What does "xenstore-ls -fp" show while the guest is sat waiting?
>

I will also try get these outputs to you later.



I can only find oi-dev-151a-x86.iso and oi-dev-151a-text-x86.iso here
> (and the usb stick equivalents).
>

It is the oi-dev-151a-x86.iso. I just renamed it to shorten the name a bit.






So, what I am trying to determine is whether the vif problems I see are
related to the bootloader/pygrub error I get.

I get the feeling like there is something missing in my Debian Dom0;
libreries, some program(s) or something else. But I dont know what......

Thanks for your help so far in this matter, I appreciate the time you are
taking to do this.

Regards

Sandi

[-- Attachment #1.2: Type: text/html, Size: 4062 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2012-04-26  9:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 11:04 Failed to run bootloader Sandi Romih
2012-04-23  8:41 ` Ian Campbell
2012-04-23 11:29   ` Stefano Stabellini
2012-04-23 11:30     ` Ian Campbell
2012-04-24 20:28       ` Sandi Romih
     [not found]         ` <1335371921.28015.56.camel@zakaz.uk.xensource.com>
     [not found]           ` <CAFoWEVOkg5q9iyKcxM_LAkBgiBC_xCiVLqfFDGAtt2HzuWr9Rw@mail.gmail.com>
2012-04-26  7:30             ` Ian Campbell
2012-04-26  9:40               ` Sandi Romih [this message]
2012-04-27 18:11                 ` Sandi Romih
2012-04-27 18:19                   ` Ian Campbell
2012-04-27 23:06                     ` Sandi Romih
2012-04-28  5:45                       ` Ian Campbell
2012-04-28  6:12                       ` Ian Campbell
     [not found] ` <4F953D7B.2090608@citrix.com>
2012-04-24 20:04   ` Sandi Romih

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFoWEVNPqez_eR2jLOu0DtbH+-qDsWJyuzfxpC1QMzgzLqQwbQ@mail.gmail.com \
    --to=romihs.forums@gmail.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.