From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sandi Romih Subject: Re: Failed to run bootloader Date: Thu, 26 Apr 2012 11:40:10 +0200 Message-ID: References: <1335170516.30700.12.camel@zakaz.uk.xensource.com> <1335180628.4347.1.camel@zakaz.uk.xensource.com> <1335371921.28015.56.camel@zakaz.uk.xensource.com> <1335425428.4881.52.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0065963226188844112==" Return-path: In-Reply-To: <1335425428.4881.52.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel List-Id: xen-devel@lists.xenproject.org --===============0065963226188844112== Content-Type: multipart/alternative; boundary=bcaec52be87d1e98a604be91c65e --bcaec52be87d1e98a604be91c65e Content-Type: text/plain; charset=ISO-8859-1 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 --bcaec52be87d1e98a604be91c65e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


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 wit= h the vif line in my config file.
I have tried two different=A0methods=A0of starti= ng 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 operati= ng as it should.

With the bo= otloader =3D "/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, ramdi= sk and extra options, the vm starts to boot. However, if the vif line is pr= esent, the install pauses and stops at=A0approximately=A028 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 with= out pausing at the 28 CPU seconds.
=A0

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

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

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.
=A0<= /div>
Are your hotplug scripts set up properly?

That I dont know, I have not dealt with these scripts yet since beginnin= g my 'adventures' with xen.
How do I know if they are cor= rect, or if they need to be modified?
=A0

What does "brctl show" say while the guest is running (with the v= if
enabled)?

What does "xenstore-ls -fp" show while the guest is sat waiting?<= br>

I will also try get these outputs to yo= u later.
=A0


I can only find oi-dev-151a-x86.iso and oi-dev-151a-text-x86.iso here
(and the usb stick equivalents).
=A0
It is t= he oi-dev-151a-x86.iso. I just renamed it to shorten the name a bit.=A0



=A0


S= o, what I am trying to determine is=A0whether=A0the 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. Bu= t I dont know what......

Thanks for your help so far in this matter, I=A0appreciate=A0the time you a= re taking to do this.

Regards

Sandi
--bcaec52be87d1e98a604be91c65e-- --===============0065963226188844112== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============0065963226188844112==--