From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sandi Romih Subject: Re: Failed to run bootloader Date: Tue, 24 Apr 2012 22:28:59 +0200 Message-ID: References: <1335170516.30700.12.camel@zakaz.uk.xensource.com> <1335180628.4347.1.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7000308292207593199==" Return-path: In-Reply-To: <1335180628.4347.1.camel@zakaz.uk.xensource.com> 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@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org --===============7000308292207593199== Content-Type: multipart/alternative; boundary=0015174c1234cbcf8504be729aa6 --0015174c1234cbcf8504be729aa6 Content-Type: text/plain; charset=ISO-8859-1 On Mon, Apr 23, 2012 at 1:30 PM, Ian Campbell wrote: > On Mon, 2012-04-23 at 12:29 +0100, Stefano Stabellini wrote: > > On Mon, 23 Apr 2012, Ian Campbell wrote: > > > On Sat, 2012-04-21 at 12:04 +0100, Sandi Romih wrote: > > > > [...] > > > > > > > kernel = "/etc/xen/kernels/oi151a/unix" > > > > ramdisk = "/etc/xen/kernels/oi151a/boot_archive" > > > > > > I forget how this works -- do you need to comment these out while using > > > pygrub or are these paths inside the ISO? > > > [...] > > > > disk = > > > > [ 'file:/mnt/media/comp_files/os-iso/oi151a.iso,xvdc:cdrom,r' , > > > > 'phy:/dev/dom0/oi_boot,xvda,w' ] > > > > bootloader = "/usr/bin/pygrub" > > > > > > Sadly I don't think xl is currently capable of booting using pygrub > from > > > a file:/// type device. > > > > > I expect this will be resolved by Stefano's "qdisk local attach" series > > > which was on the list last week. > > > > Actually, even without my patch series, xl should be able to boot a PV > > guest using pygrub if (and only if) the disk is a raw file. > > Yes, I've just realised that while editing > http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installeras part of the dos day -- it seems to work for me at least. > > Perhaps the issue here is the use of kernel= and ramdisk= instead of > bootloader_args? (see the new CD install section of that Debian install > guide for an example of the sort of thing which works for me) > > Ian. > > > > > > > > In the meantime as a workaround you could try using losetup on the iso > > > and pointing xl at phy:/dev/loop$N. > > > > that should also work > > > Hello guys, Thanks for the responses. I have been doing some testing, to see if I could find out what could be causing the problem. I have, once again, reinstalled the whole system as I wanted a clean system, and now I can get the system to create my openindiana VM (with the bootloader property in the cfg file), however it will not boot fully. What I did discover is that the VM boot is halted by the vif option in my cfg file. If I comment it out, the vm boots fine, but of course I cant complete the install without the network IF present. I tried creating a different networking architecture as laid out in the xen wiki's, but with no difference in the behavior. Occasionally I would get errors in the VM regarding network IF not being correctly initialized (or something to that extent), which reinforces my suspicions regarding networking causing the problems I had all this working in my initial setup, 3.1.9 kernel with xen 4.2 unstable 14785, now I am running kernel 3.1.10. The major differences are that before I used a file based disk image while now I am using LVM disk image (or partition), and that I did not patch xen with the Solaris pvgrub patch. My current disk definition is: disk = [ 'file:/mnt/media/comp_files/os-iso/oi151a.iso,xvdc:cdrom,r' , 'phy:/dev/xen-dom0/oi_boot,xvda,w' ] Have I perhaps made an error here? Hope that I have not rambled on too much and confused you. Best regards Sandi --0015174c1234cbcf8504be729aa6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Mon, Apr 2= 3, 2012 at 1:30 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
On Mon, 2012-04-23 at 12:2= 9 +0100, Stefano Stabellini wrote:
> On Mon, 23 Apr 2012, Ian Campbell wrote:
> > On Sat, 2012-04-21 at 12:04 +0100, Sandi Romih wrote:
> > > [...]
> >
> > > =A0kernel =3D "/etc/xen/kernels/oi151a/unix"
> > > =A0ramdisk =3D "/etc/xen/kernels/oi151a/boot_archive&qu= ot;
> >
> > I forget how this works -- do you need to comment these out while= using
> > pygrub or are these paths inside the ISO?
> > [...]
> > > =A0disk =3D
> > > [ 'file:/mnt/media/comp_files/os-iso/oi151a.iso,xvdc:cdr= om,r' ,
> > > 'phy:/dev/dom0/oi_boot,xvda,w' ]
> > > =A0bootloader =3D "/usr/bin/pygrub"
> >
> > Sadly I don't think xl is currently capable of booting using = pygrub from
> > a file:/// type device.
>
> > I expect this will be resolved by Stefano's "qdisk local= attach" series
> > which was on the list last week.
>
> Actually, even without my patch series, xl should be able to boot a PV=
> guest using pygrub if (and only if) the disk is a raw file.

Yes, I've just realised that while editing
http://wiki.xen.org/wiki/Debian_Guest_Installa= tion_Using_Debian_Installer as part of the dos day -- it seems to work = for me at least.

Perhaps the issue here is the use of kernel=3D and ramdisk=3D instead of bootloader_args? (see the new CD install section of that Debian install
guide for an example of the sort of thing which works for me)

Ian.

>
>
> > In the meantime as a workaround you could try using losetup on th= e iso
> > and pointing xl at phy:/dev/loop$N.
>
> that should also work


Hello guys,
=
Thanks for the=A0responses.

I have been doin= g some testing, to see if I could find out what could be causing the proble= m.
I have, once again, reinstalled the whole system= as I wanted a clean system, and now I can get the system to create my open= indiana VM (with the bootloader property in the cfg file), however it will = not boot fully.

What I did discover is that the VM boot is= =A0halted by the vif option in my cfg file. If I comment it out, the vm boo= ts fine, but of course I cant complete the install without the network IF p= resent.
I tried creating a different networking architec= ture as laid out in the xen wiki's, but with no difference in the=A0beh= avior.
Occasionally I would get errors in t= he VM regarding network IF not being correctly=A0initialized=A0(or somethin= g to that extent), which reinforces my suspicions regarding networking caus= ing the problems

I had all t= his working in my initial setup, 3.1.9 kernel with xen 4.2 unstable 14785, = now I am running kernel 3.1.10. The major differences are that before I use= d a file based disk image while now I am using LVM disk image (or partition= ), and that I did not patch xen with the Solaris pvgrub patch. My current d= isk definition is:

=A0disk =3D [ 'file:/mnt/media/comp_files/os-iso/oi151= a.iso,xvdc:cdrom,r' , 'phy:/dev/xen-dom0/oi_boot,xvda,w' ]

Have I perhaps made an error here?

Hope= that I have not rambled on too much and=A0confused=A0you.

Best regards

Sandi
--0015174c1234cbcf8504be729aa6-- --===============7000308292207593199== 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 --===============7000308292207593199==--