=A0vif =3D [ 'bridge=3De= th0, mac=3D00:14:3e:00:8f:d8' ]=A0

=A0vcpus =3D 2<= /div>

=A0cpus =3D "2-3"=

=A0memory =3D 2048

=A0name =3D "oi"

=A0kernel =3D "/etc/xen/kernels/oi151a/unix"=

=A0ramdisk =3D "/etc/xen/kernels= /oi151a/boot_archive"

# Pre install booting

=A0extra =3D "/platform/i86xpv/kernel/amd64/unix -B console=3Dtty= a"

=A0disk =3D [ 'file:/mnt/media/comp_fil= es/os-iso/oi151a.iso,xvdc:cdrom,r' , 'phy:/dev/dom0/oi_boot,xvda,w&= #39; ]

=A0bootloader =3D &q= uot;/usr/bin/pygrub"

# Post install booting

# extra =3D "/platform/i86xpv/kernel/amd64/unix -B zfs-bootfs=3D= rpool/ROOT/openindiana,bootpath=3D/xpvd/xdf@51712:a"

# disk =3D [ 'phy:/dev/dom0/oi_boot,xvd= a,w' ]

<= /div>

=A0on_shutdown =3D "destroy"=

=A0on_reboot =3D "restart"=

=A0on_crash =3D "destroy&quo= t;

=A0pci =3D [ '05:00.0' ]

As a test, I checked if p= ygrub has any errors:

root@dom0:/$pygrub /mnt/media/comp_files/os-iso/oi151a.iso=A0

linux (kernel /var/run/xend/boot/boot_kerne= l.RomUm9)(ramdisk /var/run/xend/boot/boot_ramdisk.WdnQsz)(args "/platf= orm/i86xpv/kernel/amd64/unix")

I am=A0assuming=A0that pygrub can correctly handle the install media.<= /div>

The irony is that I = have managed to get this working once, but I was using a regular file image= for this VM boot_disk and the VM was horribly slow. I=A0re-installed=A0my = whole system on an LVM disk, which I understand is recommended for better d= isk performance.

I would appreciate any suggestions.

Regards

Sandi

--0015174766f8967c5f04be2e5fdc-- --===============7764536702086503270== 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 --===============7764536702086503270==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to run bootloader Date: Mon, 23 Apr 2012 09:41:56 +0100 Message-ID: <1335170516.30700.12.camel@zakaz.uk.xensource.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sandi Romih Cc: "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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. In the meantime as a workaround you could try using losetup on the iso and pointing xl at phy:/dev/loop$N. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: Failed to run bootloader Date: Mon, 23 Apr 2012 12:29:27 +0100 Message-ID: References: <1335170516.30700.12.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1335170516.30700.12.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: Sandi Romih , "xen-devel@lists.xensource.com" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org 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. > 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to run bootloader Date: Mon, 23 Apr 2012 12:30:28 +0100 Message-ID: <1335180628.4347.1.camel@zakaz.uk.xensource.com> References: <1335170516.30700.12.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Stefano Stabellini Cc: Sandi Romih , "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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_Installer as 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 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:04:47 +0200 Message-ID: References: <4F953D7B.2090608@citrix.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1430365301800972487==" Return-path: In-Reply-To: <4F953D7B.2090608@citrix.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: Roger Pau Monne Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org --===============1430365301800972487== Content-Type: multipart/alternative; boundary=bcaec52be657429a1a04be724414 --bcaec52be657429a1a04be724414 Content-Type: text/plain; charset=ISO-8859-1 > > I think the test you have done here is as a regular user (because I see > the $ instead of #), could you execute the same command as you would call > xl (either as root or with sudo)? > > Yes, I did not notice that, but I was logged on as root. I was fiddling the prompt colours and I made a mistake for the root PS1 properties. I am still learning about the linux environment. :) Regards Sandi --bcaec52be657429a1a04be724414 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

I think the test you have done here is as a regular user (because= I see the $ instead of #), could you execute the same command as you would= call xl (either as root or with sudo)?

Yes, I did not notice t= hat, but I was logged on as root. I was=A0fiddling=A0the prompt colours and= I made a mistake for the root PS1 properties. I am still learning about th= e linux environment. :)

Regards

Sandi

--bcaec52be657429a1a04be724414-- --===============1430365301800972487== 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 --===============1430365301800972487==-- 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==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to run bootloader Date: Thu, 26 Apr 2012 08:30:28 +0100 Message-ID: <1335425428.4881.52.camel@dagon.hellion.org.uk> 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> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sandi Romih Cc: xen-devel List-Id: xen-devel@lists.xenproject.org (putting xen-devel back, please watch your cc lines) On Wed, 2012-04-25 at 20:45 +0100, Sandi Romih wrote: > > On Apr 25, 2012 6:38 PM, "Ian Campbell" > wrote: > > > > On Tue, 2012-04-24 at 21:28 +0100, Sandi Romih wrote: > > > > > What I did discover is that the VM boot is halted by the vif > option in > > > my cfg file. > > > > What do you mean "halted"? You mean that pygrub fails if you have > the > > vif line and succeeds if you do not? > > Well, I guess I should have used the word pauses, as the vm is still > running okay but it does not proceed beyond a certain point. When I > comment out the vif line the boot process does not stop, it proceeds > normally. So this is now a different failure mode to the one which you originally reported (pygrub failed)? What does your guest config look like now that you have resolved the pygrub issue? Can you provide a full log of the failing boot with a vif enabled to the point of the hang? Are your hotplug scripts set up properly? 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? http://wiki.xen.org/wiki/Reporting_Bugs_against_Xen has a list of other potentially useful logs/info which you should consider including. > > > disk = > > > [ 'file:/mnt/media/comp_files/os-iso/oi151a.iso,xvdc:cdrom,r' , > > > 'phy:/dev/xen-dom0/oi_boot,xvda,w' ] > > > > Can I download oi161a.iso from somewhere so I can try for myself? > > Yes, you can download it from here: > http://openindiana.org/download/ I can only find oi-dev-151a-x86.iso and oi-dev-151a-text-x86.iso here (and the usb stick equivalents). Ian. 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==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sandi Romih Subject: Re: Failed to run bootloader Date: Fri, 27 Apr 2012 20:11:19 +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="===============1592711413674331942==" Return-path: In-Reply-To: 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 --===============1592711413674331942== Content-Type: multipart/alternative; boundary=bcaec52be87df8f92704bead0730 --bcaec52be87df8f92704bead0730 Content-Type: text/plain; charset=ISO-8859-1 Ian, Please see some of the output you have requested below. >> What does your guest config look like now that you have resolved the >> pygrub issue? >> > disk = [ 'file:/home/sandi/oi151a.iso,xvdc:cdrom,r', 'phy:/dev/xen-dom0/oi_boot,xvda,w', ] vif = ['bridge=eth0,mac=00:16:3e:00:8f:d8'] vcpus = 2 cpus = "2-3" memory = 2048 name = "oi" kernel = "/etc/xen/kernels/oi151a/unix" ramdisk = "/etc/xen/kernels/oi151a/boot_archive" extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya" on_shutdown = "destroy" on_reboot = "restart" on_crash = "destroy" pci = [ '05:00.0' ] > > >> >> Can you provide a full log of the failing boot with a vif enabled to the >> point of the hang? >> >> I will send these logs if you like, if the data I have included here is of not help. >> 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? >> > > [root@xen-srv sandi]# brctl show bridge name bridge id STP enabled interfaces [root@xen-srv sandi]# xenstore-ls -fp /tool = "" (n0) /tool/xenstored = "" (n0) /local = "" (n0) /local/domain = "" (n0) /local/domain/0 = "" (n0) /local/domain/0/name = "Domain-0" (n0) /local/domain/0/memory = "" (n0) /local/domain/0/memory/target = "2097152" (n0) /local/domain/0/memory/static-max = "2097152" (n0) /local/domain/0/memory/freemem-slack = "3773506" (n0) /local/domain/0/device-model = "" (n0) /local/domain/0/device-model/2 = "" (n0) /local/domain/0/device-model/2/state = "running" (n0) /local/domain/0/backend = "" (n0) /local/domain/0/backend/qdisk = "" (n0) /local/domain/0/backend/qdisk/2 = "" (n0) /local/domain/0/backend/qdisk/2/51744 = "" (n0,r2) /local/domain/0/backend/qdisk/2/51744/frontend = "/local/domain/2/device/vbd/51744" (n0,r2) /local/domain/0/backend/qdisk/2/51744/params = "aio:/home/sandi/oi151a.iso" (n0,r2) /local/domain/0/backend/qdisk/2/51744/frontend-id = "2" (n0,r2) /local/domain/0/backend/qdisk/2/51744/online = "1" (n0,r2) /local/domain/0/backend/qdisk/2/51744/removable = "1" (n0,r2) /local/domain/0/backend/qdisk/2/51744/bootable = "1" (n0,r2) /local/domain/0/backend/qdisk/2/51744/state = "4" (n0,r2) /local/domain/0/backend/qdisk/2/51744/dev = "xvdc" (n0,r2) /local/domain/0/backend/qdisk/2/51744/type = "qdisk" (n0,r2) /local/domain/0/backend/qdisk/2/51744/mode = "r" (n0,r2) /local/domain/0/backend/qdisk/2/51744/device-type = "cdrom" (n0,r2) /local/domain/0/backend/qdisk/2/51744/feature-barrier = "1" (n0,r2) /local/domain/0/backend/qdisk/2/51744/info = "5" (n0,r2) /local/domain/0/backend/qdisk/2/51744/sector-size = "512" (n0,r2) /local/domain/0/backend/qdisk/2/51744/sectors = "1643348" (n0,r2) /local/domain/0/backend/qdisk/2/51744/hotplug-status = "connected" (n0,r2) /local/domain/0/backend/vbd = "" (n0) /local/domain/0/backend/vbd/2 = "" (n0) /local/domain/0/backend/vbd/2/51712 = "" (n0,r2) /local/domain/0/backend/vbd/2/51712/frontend = "/local/domain/2/device/vbd/51712" (n0,r2) /local/domain/0/backend/vbd/2/51712/physical-device = "fe:2" (n0,r2) /local/domain/0/backend/vbd/2/51712/params = "/dev/xen-dom0/oi_boot" (n0,r2) /local/domain/0/backend/vbd/2/51712/frontend-id = "2" (n0,r2) /local/domain/0/backend/vbd/2/51712/online = "1" (n0,r2) /local/domain/0/backend/vbd/2/51712/removable = "0" (n0,r2) /local/domain/0/backend/vbd/2/51712/bootable = "1" (n0,r2) /local/domain/0/backend/vbd/2/51712/state = "4" (n0,r2) /local/domain/0/backend/vbd/2/51712/dev = "xvda" (n0,r2) /local/domain/0/backend/vbd/2/51712/type = "phy" (n0,r2) /local/domain/0/backend/vbd/2/51712/mode = "w" (n0,r2) /local/domain/0/backend/vbd/2/51712/device-type = "disk" (n0,r2) /local/domain/0/backend/vbd/2/51712/feature-flush-cache = "1" (n0,r2) /local/domain/0/backend/vbd/2/51712/sectors = "83886080" (n0,r2) /local/domain/0/backend/vbd/2/51712/info = "0" (n0,r2) /local/domain/0/backend/vbd/2/51712/sector-size = "512" (n0,r2) /local/domain/0/backend/vif = "" (n0) /local/domain/0/backend/vif/2 = "" (n0) /local/domain/0/backend/vif/2/0 = "" (n0,r2) /local/domain/0/backend/vif/2/0/frontend = "/local/domain/2/device/vif/0" (n0,r2) /local/domain/0/backend/vif/2/0/frontend-id = "2" (n0,r2) /local/domain/0/backend/vif/2/0/online = "1" (n0,r2) /local/domain/0/backend/vif/2/0/state = "2" (n0,r2) /local/domain/0/backend/vif/2/0/script = "/etc/xen/scripts/vif-bridge" (n0,r2) /local/domain/0/backend/vif/2/0/mac = "00:16:3e:00:8f:d8" (n0,r2) /local/domain/0/backend/vif/2/0/bridge = "eth0" (n0,r2) /local/domain/0/backend/vif/2/0/handle = "0" (n0,r2) /local/domain/0/backend/vif/2/0/feature-sg = "1" (n0,r2) /local/domain/0/backend/vif/2/0/feature-gso-tcpv4 = "1" (n0,r2) /local/domain/0/backend/vif/2/0/feature-rx-copy = "1" (n0,r2) /local/domain/0/backend/vif/2/0/feature-rx-flip = "0" (n0,r2) /local/domain/0/backend/console = "" (n0) /local/domain/0/backend/console/2 = "" (n0) /local/domain/0/backend/console/2/0 = "" (n0,r2) /local/domain/0/backend/console/2/0/frontend = "/local/domain/2/console" (n0,r2) /local/domain/0/backend/console/2/0/frontend-id = "2" (n0,r2) /local/domain/0/backend/console/2/0/online = "1" (n0,r2) /local/domain/0/backend/console/2/0/state = "4" (n0,r2) /local/domain/0/backend/console/2/0/domain = "oi" (n0,r2) /local/domain/0/backend/console/2/0/protocol = "vt100" (n0,r2) /local/domain/0/backend/console/2/0/hotplug-status = "connected" (n0,r2) /local/domain/0/backend/pci = "" (n0) /local/domain/0/backend/pci/2 = "" (n0) /local/domain/0/backend/pci/2/0 = "" (n0,r2) /local/domain/0/backend/pci/2/0/frontend = "/local/domain/2/device/pci/0" (n0,r2) /local/domain/0/backend/pci/2/0/frontend-id = "2" (n0,r2) /local/domain/0/backend/pci/2/0/online = "1" (n0,r2) /local/domain/0/backend/pci/2/0/state = "3" (n0,r2) /local/domain/0/backend/pci/2/0/domain = "oi" (n0,r2) /local/domain/0/backend/pci/2/0/key-0 = "0000:05:00.0" (n0,r2) /local/domain/0/backend/pci/2/0/dev-0 = "0000:05:00.0" (n0,r2) /local/domain/0/backend/pci/2/0/opts-0 = "msitranslate=1,power_mgmt=0" (n0,r2) /local/domain/0/backend/pci/2/0/state-0 = "3" (n0,r2) /local/domain/0/backend/pci/2/0/num_devs = "1" (n0,r2) /local/domain/0/backend/pci/2/0/vdev-0 = "0000:05:00.00" (n0,r2) /local/domain/0/backend/pci/2/0/root-0 = "0000:05" (n0,r2) /local/domain/0/backend/pci/2/0/root_num = "1" (n0,r2) /local/domain/2 = "" (n0,r2) /local/domain/2/vm = "/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4" (n0,r2) /local/domain/2/name = "oi" (n0,r2) /local/domain/2/cpu = "" (n0,r2) /local/domain/2/cpu/0 = "" (n0,r2) /local/domain/2/cpu/0/availability = "online" (n0,r2) /local/domain/2/cpu/1 = "" (n0,r2) /local/domain/2/cpu/1/availability = "online" (n0,r2) /local/domain/2/memory = "" (n0,r2) /local/domain/2/memory/static-max = "2097152" (n0,r2) /local/domain/2/memory/target = "2097152" (n0,r2) /local/domain/2/memory/videoram = "0" (n0,r2) /local/domain/2/device = "" (n0,r2) /local/domain/2/device/suspend = "" (n0,r2) /local/domain/2/device/suspend/event-channel = "" (n2) /local/domain/2/device/vbd = "" (n0,r2) /local/domain/2/device/vbd/51744 = "" (n2,r0) /local/domain/2/device/vbd/51744/backend = "/local/domain/0/backend/qdisk/2/51744" (n2,r0) /local/domain/2/device/vbd/51744/backend-id = "0" (n2,r0) /local/domain/2/device/vbd/51744/state = "4" (n2,r0) /local/domain/2/device/vbd/51744/virtual-device = "51744" (n2,r0) /local/domain/2/device/vbd/51744/device-type = "cdrom" (n2,r0) /local/domain/2/device/vbd/51744/media-req = "none" (n2,r0) /local/domain/2/device/vbd/51744/ring-ref = "266" (n2,r0) /local/domain/2/device/vbd/51744/event-channel = "13" (n2,r0) /local/domain/2/device/vbd/51744/protocol = "x86_64-abi" (n2,r0) /local/domain/2/device/vbd/51712 = "" (n2,r0) /local/domain/2/device/vbd/51712/backend = "/local/domain/0/backend/vbd/2/51712" (n2,r0) /local/domain/2/device/vbd/51712/backend-id = "0" (n2,r0) /local/domain/2/device/vbd/51712/state = "4" (n2,r0) /local/domain/2/device/vbd/51712/virtual-device = "51712" (n2,r0) /local/domain/2/device/vbd/51712/device-type = "disk" (n2,r0) /local/domain/2/device/vbd/51712/media-req = "none" (n2,r0) /local/domain/2/device/vbd/51712/ring-ref = "267" (n2,r0) /local/domain/2/device/vbd/51712/event-channel = "14" (n2,r0) /local/domain/2/device/vbd/51712/protocol = "x86_64-abi" (n2,r0) /local/domain/2/device/vif = "" (n0,r2) /local/domain/2/device/vif/0 = "" (n2,r0) /local/domain/2/device/vif/0/backend = "/local/domain/0/backend/vif/2/0" (n2,r0) /local/domain/2/device/vif/0/backend-id = "0" (n2,r0) /local/domain/2/device/vif/0/state = "4" (n2,r0) /local/domain/2/device/vif/0/handle = "0" (n2,r0) /local/domain/2/device/vif/0/mac = "00:16:3e:00:8f:d8" (n2,r0) /local/domain/2/device/vif/0/tx-ring-ref = "8" (n2,r0) /local/domain/2/device/vif/0/rx-ring-ref = "9" (n2,r0) /local/domain/2/device/vif/0/event-channel = "12" (n2,r0) /local/domain/2/device/vif/0/feature-rx-notify = "1" (n2,r0) /local/domain/2/device/vif/0/request-rx-copy = "1" (n2,r0) /local/domain/2/device/pci = "" (n0,r2) /local/domain/2/device/pci/0 = "" (n2,r0) /local/domain/2/device/pci/0/backend = "/local/domain/0/backend/pci/2/0" (n2,r0) /local/domain/2/device/pci/0/backend-id = "0" (n2,r0) /local/domain/2/device/pci/0/state = "1" (n2,r0) /local/domain/2/control = "" (n0,r2) /local/domain/2/control/shutdown = "" (n2) /local/domain/2/control/platform-feature-multiprocessor-suspend = "1" (n0,r2) /local/domain/2/control/platform-feature-xs_reset_watches = "1" (n0,r2) /local/domain/2/data = "" (n2) /local/domain/2/domid = "2" (n0,r2) /local/domain/2/store = "" (n0,r2) /local/domain/2/store/port = "1" (n0,r2) /local/domain/2/store/ring-ref = "4891896" (n0,r2) /local/domain/2/console = "" (n2,r0) /local/domain/2/console/backend = "/local/domain/0/backend/console/2/0" (n2,r0) /local/domain/2/console/backend-id = "0" (n2,r0) /local/domain/2/console/limit = "1048576" (n2,r0) /local/domain/2/console/type = "ioemu" (n2,r0) /local/domain/2/console/output = "pty" (n2,r0) /local/domain/2/console/port = "2" (n2,r0) /local/domain/2/console/ring-ref = "4891895" (n2,r0) /local/domain/2/console/tty = "/dev/pts/4" (n2,r0) /local/domain/2/hvmloader = "" (n0,r2) /local/domain/2/hvmloader/bios = "rombios" (n0,r2) /local/domain/2/image = "" (n0,r2) /local/domain/2/image/device-model-pid = "4029" (n0,r2) /vm = "" (n0) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4 = "" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/uuid = "897494e6-60a2-47e4-aaa0-826ef89d63e4" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/name = "oi" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image = "" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image/ostype = "linux" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image/kernel = "/etc/xen/kernels/oi151a/unix" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image/ramdisk = "/etc/xen/kernels/oi151a/boot_archive" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image/cmdline = "/platform/i86xpv/kernel/amd64/unix -B console=ttya" (n0,r2) /vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/start_time = "1335549687.10" (n0,r2) /libxl = "" (n0) /libxl/2 = "" (n0) /libxl/2/dm-version = "qemu_xen_traditional" (n0) Hope this output helps out... Best regards Sandi --bcaec52be87df8f92704bead0730 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

Ian,

<= div class=3D"gmail_extra">Please see some of the output you have requested = below.

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

=A0disk =3D [

'file:/home/sandi/oi151a.iso,xvdc:cdrom,= r',

'= phy:/dev/xen-dom0/oi_boot,xvda,w',

]

=A0vif = =3D ['bridge=3Deth0,mac=3D00:16:3e:00:8f:d8']=A0

=A0vcpus =3D 2

=A0cpus =3D "2-3"

=A0memory =3D 2048

=A0name =3D "oi"

<= br>

=A0kernel =3D "/etc/xen/kernels/oi151a/unix"

<= div>=A0ramdisk =3D "/etc/xen/kernels/oi151a/boot_archive"

=A0extra =3D "/platform/i86xpv/kernel/amd64/unix -B console=3Dtty= a"

=A0on_shutdown =3D "destroy"

=A0on_reboot =3D "restart"

=A0on_crash =3D "= ;destroy"

=A0pci =3D [ '05:00.0' ]

=A0

=A0

Can you provide a full log of the failing boot with a vif enabled to the point of the hang?

I w= ill send these logs if you like, if the data I have included here is of not= help.

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>

[root@xe= n-srv sandi]# brctl show

bridge name bridge id STP enabled interfaces

[root@xen-srv sandi]# xenstore-ls -fp

/tool = =3D "" =A0 (n0)

/tool/xenstored =3D "" =A0 (n= 0)

/local =3D "" =A0 (n0)

/local/domain =3D &= quot;" =A0 (n0)

/local/domain/0 =3D "" =A0 (n0)

/local/domain/0/na= me =3D "Domain-0" =A0 (n0)

/local/domain/0/memory =3D &= quot;" =A0 (n0)

/local/domain/0/memory/target =3D "2097= 152" =A0 (n0)

/local/domain/0/memory/static-max =3D "2097152" =A0 (n0)

/local/domain/0/memory/freemem-slack =3D "3773506" =A0 (n0= )

/local/domain/0/device-model =3D "" =A0 (n0)

/local/domain/0/device-model/2 =3D "" =A0 (n0)

/local/domain/0/device-model/2/state =3D "running" =A0 (n0)<= /div>

/local/domain/0/backend =3D "" =A0 (n0)

/loca= l/domain/0/backend/qdisk =3D "" =A0 (n0)

/local/domain/= 0/backend/qdisk/2 =3D "" =A0 (n0)

/local/domain/0/backend/qdisk/2/51744 =3D "" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/frontend =3D "/local/doma= in/2/device/vbd/51744" =A0 (n0,r2)

/local/domain/0/backend/q= disk/2/51744/params =3D "aio:/home/sandi/oi151a.iso" =A0 (n0,r2)<= /div>

/local/domain/0/backend/qdisk/2/51744/frontend-id =3D "2" = =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/online =3D &quo= t;1" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/remov= able =3D "1" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/bootable =3D "1" =A0 (= n0,r2)

/local/domain/0/backend/qdisk/2/51744/state =3D "4&qu= ot; =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/dev =3D &qu= ot;xvdc" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/type =3D "qdisk" =A0 (= n0,r2)

/local/domain/0/backend/qdisk/2/51744/mode =3D "r&quo= t; =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/device-type = =3D "cdrom" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/feature-barrier =3D "1"= ; =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/info =3D &quo= t;5" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/secto= r-size =3D "512" =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/sectors =3D "1643348" = =A0 (n0,r2)

/local/domain/0/backend/qdisk/2/51744/hotplug-status = =3D "connected" =A0 (n0,r2)

/local/domain/0/backend/vbd= =3D "" =A0 (n0)

/local/domain/0/backend/vbd/2 =3D "" =A0 (n0)

/loc= al/domain/0/backend/vbd/2/51712 =3D "" =A0 (n0,r2)

/loc= al/domain/0/backend/vbd/2/51712/frontend =3D "/local/domain/2/device/v= bd/51712" =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/physical-device =3D "fe:2&quo= t; =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/params =3D &qu= ot;/dev/xen-dom0/oi_boot" =A0 (n0,r2)

/local/domain/0/backen= d/vbd/2/51712/frontend-id =3D "2" =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/online =3D "1" =A0 (n0,r= 2)

/local/domain/0/backend/vbd/2/51712/removable =3D "0"= ; =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/bootable =3D &q= uot;1" =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/state =3D "4" =A0 (n0,r2= )

/local/domain/0/backend/vbd/2/51712/dev =3D "xvda" = =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/type =3D "ph= y" =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/mode =3D "w" =A0 (n0,r2)=

/local/domain/0/backend/vbd/2/51712/device-type =3D "disk&q= uot; =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/feature-flus= h-cache =3D "1" =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/sectors =3D "83886080" = =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/info =3D "0&= quot; =A0 (n0,r2)

/local/domain/0/backend/vbd/2/51712/sector-size= =3D "512" =A0 (n0,r2)

/local/domain/0/backend/vif =3D "" =A0 (n0)

/local= /domain/0/backend/vif/2 =3D "" =A0 (n0)

/local/domain/0= /backend/vif/2/0 =3D "" =A0 (n0,r2)

/local/domain/0/bac= kend/vif/2/0/frontend =3D "/local/domain/2/device/vif/0" =A0 (n0,= r2)

/local/domain/0/backend/vif/2/0/frontend-id =3D "2" =A0 (n0,= r2)

/local/domain/0/backend/vif/2/0/online =3D "1" =A0 = (n0,r2)

/local/domain/0/backend/vif/2/0/state =3D "2" = =A0 (n0,r2)

/local/domain/0/backend/vif/2/0/script =3D "/etc/xen/scripts/vif-= bridge" =A0 (n0,r2)

/local/domain/0/backend/vif/2/0/mac =3D = "00:16:3e:00:8f:d8" =A0 (n0,r2)

/local/domain/0/backend= /vif/2/0/bridge =3D "eth0" =A0 (n0,r2)

/local/domain/0/backend/vif/2/0/handle =3D "0" =A0 (n0,r2)

/local/domain/0/backend/vif/2/0/feature-sg =3D "1" =A0 (= n0,r2)

/local/domain/0/backend/vif/2/0/feature-gso-tcpv4 =3D &quo= t;1" =A0 (n0,r2)

/local/domain/0/backend/vif/2/0/feature-rx-copy =3D "1" =A0 = (n0,r2)

/local/domain/0/backend/vif/2/0/feature-rx-flip =3D "= ;0" =A0 (n0,r2)

/local/domain/0/backend/console =3D "&q= uot; =A0 (n0)

/local/domain/0/backend/console/2 =3D "" =A0 (n0)

= /local/domain/0/backend/console/2/0 =3D "" =A0 (n0,r2)

= /local/domain/0/backend/console/2/0/frontend =3D "/local/domain/2/cons= ole" =A0 (n0,r2)

/local/domain/0/backend/console/2/0/frontend-id =3D "2" =A0 = (n0,r2)

/local/domain/0/backend/console/2/0/online =3D "1&qu= ot; =A0 (n0,r2)

/local/domain/0/backend/console/2/0/state =3D &qu= ot;4" =A0 (n0,r2)

/local/domain/0/backend/console/2/0/domain =3D "oi" =A0 (n0,= r2)

/local/domain/0/backend/console/2/0/protocol =3D "vt100&= quot; =A0 (n0,r2)

/local/domain/0/backend/console/2/0/hotplug-sta= tus =3D "connected" =A0 (n0,r2)

/local/domain/0/backend/pci =3D "" =A0 (n0)

/local= /domain/0/backend/pci/2 =3D "" =A0 (n0)

/local/domain/0= /backend/pci/2/0 =3D "" =A0 (n0,r2)

/local/domain/0/bac= kend/pci/2/0/frontend =3D "/local/domain/2/device/pci/0" =A0 (n0,= r2)

/local/domain/0/backend/pci/2/0/frontend-id =3D "2" =A0 (n0,= r2)

/local/domain/0/backend/pci/2/0/online =3D "1" =A0 = (n0,r2)

/local/domain/0/backend/pci/2/0/state =3D "3" = =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/domain =3D "oi" =A0 (n0,r2)<= /div>

/local/domain/0/backend/pci/2/0/key-0 =3D "0000:05:00.0"= ; =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/dev-0 =3D "000= 0:05:00.0" =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/opts-0 =3D "msitranslate=3D1,powe= r_mgmt=3D0" =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/stat= e-0 =3D "3" =A0 (n0,r2)

/local/domain/0/backend/pci/2/0= /num_devs =3D "1" =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/vdev-0 =3D "0000:05:00.00" = =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/root-0 =3D "0000= :05" =A0 (n0,r2)

/local/domain/0/backend/pci/2/0/root_num = =3D "1" =A0 (n0,r2)

/local/domain/2 =3D "" =A0 (n0,r2)

/local/domain/2= /vm =3D "/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4" =A0 (n0,r2)

/local/domain/2/name =3D "oi" =A0 (n0,r2)

/loca= l/domain/2/cpu =3D "" =A0 (n0,r2)

/local/domain/2/cpu/0 =3D "" =A0 (n0,r2)

/local/do= main/2/cpu/0/availability =3D "online" =A0 (n0,r2)

/loc= al/domain/2/cpu/1 =3D "" =A0 (n0,r2)

/local/domain/2/cp= u/1/availability =3D "online" =A0 (n0,r2)

/local/domain/2/memory =3D "" =A0 (n0,r2)

/local/d= omain/2/memory/static-max =3D "2097152" =A0 (n0,r2)

/lo= cal/domain/2/memory/target =3D "2097152" =A0 (n0,r2)

/l= ocal/domain/2/memory/videoram =3D "0" =A0 (n0,r2)

/local/domain/2/device =3D "" =A0 (n0,r2)

/local/d= omain/2/device/suspend =3D "" =A0 (n0,r2)

/local/domain= /2/device/suspend/event-channel =3D "" =A0 (n2)

/local/= domain/2/device/vbd =3D "" =A0 (n0,r2)

/local/domain/2/device/vbd/51744 =3D "" =A0 (n2,r0)

/local/domain/2/device/vbd/51744/backend =3D "/local/domain/0/backen= d/qdisk/2/51744" =A0 (n2,r0)

/local/domain/2/device/vbd/5174= 4/backend-id =3D "0" =A0 (n2,r0)

/local/domain/2/device/vbd/51744/state =3D "4" =A0 (n2,r0)

/local/domain/2/device/vbd/51744/virtual-device =3D "51744&qu= ot; =A0 (n2,r0)

/local/domain/2/device/vbd/51744/device-type =3D = "cdrom" =A0 (n2,r0)

/local/domain/2/device/vbd/51744/media-req =3D "none" =A0 (n= 2,r0)

/local/domain/2/device/vbd/51744/ring-ref =3D "266&quo= t; =A0 (n2,r0)

/local/domain/2/device/vbd/51744/event-channel =3D= "13" =A0 (n2,r0)

/local/domain/2/device/vbd/51744/protocol =3D "x86_64-abi" = =A0 (n2,r0)

/local/domain/2/device/vbd/51712 =3D "" =A0= (n2,r0)

/local/domain/2/device/vbd/51712/backend =3D "/loca= l/domain/0/backend/vbd/2/51712" =A0 (n2,r0)

/local/domain/2/device/vbd/51712/backend-id =3D "0" =A0 (n2,= r0)

/local/domain/2/device/vbd/51712/state =3D "4" =A0 = (n2,r0)

/local/domain/2/device/vbd/51712/virtual-device =3D "= ;51712" =A0 (n2,r0)

/local/domain/2/device/vbd/51712/device-type =3D "disk" =A0 = (n2,r0)

/local/domain/2/device/vbd/51712/media-req =3D "none= " =A0 (n2,r0)

/local/domain/2/device/vbd/51712/ring-ref =3D = "267" =A0 (n2,r0)

/local/domain/2/device/vbd/51712/event-channel =3D "14" =A0 = (n2,r0)

/local/domain/2/device/vbd/51712/protocol =3D "x86_6= 4-abi" =A0 (n2,r0)

/local/domain/2/device/vif =3D "&quo= t; =A0 (n0,r2)

/local/domain/2/device/vif/0 =3D "" =A0 (n2,r0)

/l= ocal/domain/2/device/vif/0/backend =3D "/local/domain/0/backend/vif/2/= 0" =A0 (n2,r0)

/local/domain/2/device/vif/0/backend-id =3D &= quot;0" =A0 (n2,r0)

/local/domain/2/device/vif/0/state =3D "4" =A0 (n2,r0)

/local/domain/2/device/vif/0/handle =3D "0" =A0 (n2,r0)

/local/domain/2/device/vif/0/mac =3D "00:16:3e:00:8f:d8" = =A0 (n2,r0)

/local/domain/2/device/vif/0/tx-ring-ref =3D "8" =A0 (n2,r0)=

/local/domain/2/device/vif/0/rx-ring-ref =3D "9" =A0 (= n2,r0)

/local/domain/2/device/vif/0/event-channel =3D "12&qu= ot; =A0 (n2,r0)

/local/domain/2/device/vif/0/feature-rx-notify =3D "1" =A0 (= n2,r0)

/local/domain/2/device/vif/0/request-rx-copy =3D "1&q= uot; =A0 (n2,r0)

/local/domain/2/device/pci =3D "" =A0 = (n0,r2)

/local/domain/2/device/pci/0 =3D "" =A0 (n2,r0)

/l= ocal/domain/2/device/pci/0/backend =3D "/local/domain/0/backend/pci/2/= 0" =A0 (n2,r0)

/local/domain/2/device/pci/0/backend-id =3D &= quot;0" =A0 (n2,r0)

/local/domain/2/device/pci/0/state =3D "1" =A0 (n2,r0)

/local/domain/2/control =3D "" =A0 (n0,r2)

/local/= domain/2/control/shutdown =3D "" =A0 (n2)

/local/domain= /2/control/platform-feature-multiprocessor-suspend =3D "1" =A0 (n= 0,r2)

/local/domain/2/control/platform-feature-xs_reset_watches =3D "1&= quot; =A0 (n0,r2)

/local/domain/2/data =3D "" =A0 (n2)<= /div>

/local/domain/2/domid =3D "2" =A0 (n0,r2)

/lo= cal/domain/2/store =3D "" =A0 (n0,r2)

/local/domain/2/store/port =3D "1" =A0 (n0,r2)

/lo= cal/domain/2/store/ring-ref =3D "4891896" =A0 (n0,r2)

/= local/domain/2/console =3D "" =A0 (n2,r0)

/local/domain= /2/console/backend =3D "/local/domain/0/backend/console/2/0" =A0 = (n2,r0)

/local/domain/2/console/backend-id =3D "0" =A0 (n2,r0)

/local/domain/2/console/limit =3D "1048576" =A0 (n2,r0)

/local/domain/2/console/type =3D "ioemu" =A0 (n2,r0)

<= div>/local/domain/2/console/output =3D "pty" =A0 (n2,r0)

/local/domain/2/console/port =3D "2" =A0 (n2,r0)

/= local/domain/2/console/ring-ref =3D "4891895" =A0 (n2,r0)

/local/domain/2/console/tty =3D "/dev/pts/4" =A0 (n2,r0)

/local/domain/2/hvmloader =3D "" =A0 (n0,r2)

/local/domain/2/hvmloader/bios =3D "rombios" =A0 (n0,r2)

/local/domain/2/image =3D "" =A0 (n0,r2)

/local/= domain/2/image/device-model-pid =3D "4029" =A0 (n0,r2)

= /vm =3D "" =A0 (n0)

/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4 =3D "" =A0 (n0,r2)<= /div>

/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/uuid =3D "897494e6-= 60a2-47e4-aaa0-826ef89d63e4" =A0 (n0,r2)

/vm/897494e6-60a2-4= 7e4-aaa0-826ef89d63e4/name =3D "oi" =A0 (n0,r2)

/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image =3D "" =A0 (n= 0,r2)

/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image/ostype =3D &= quot;linux" =A0 (n0,r2)

/vm/897494e6-60a2-47e4-aaa0-826ef89d= 63e4/image/kernel =3D "/etc/xen/kernels/oi151a/unix" =A0 (n0,r2)<= /div>

/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/image/ramdisk =3D "/etc/= xen/kernels/oi151a/boot_archive" =A0 (n0,r2)

/vm/897494e6-60= a2-47e4-aaa0-826ef89d63e4/image/cmdline =3D "/platform/i86xpv/kernel/a= md64/unix -B console=3Dttya" =A0 (n0,r2)

/vm/897494e6-60a2-47e4-aaa0-826ef89d63e4/start_time =3D "13355496= 87.10" =A0 (n0,r2)

/libxl =3D "" =A0 (n0)

/libxl/2 =3D "" =A0 (n0)

/libxl/2/dm-version =3D &quo= t;qemu_xen_traditional" =A0 (n0)

Hope this output helps out...

Best regards

Sandi

--bcaec52be87df8f92704bead0730-- --===============1592711413674331942== 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 --===============1592711413674331942==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to run bootloader Date: Fri, 27 Apr 2012 19:19:52 +0100 Message-ID: <1335550792.4881.76.camel@dagon.hellion.org.uk> 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sandi Romih Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Fri, 2012-04-27 at 19:11 +0100, Sandi Romih wrote: > > [root@xen-srv sandi]# brctl show > bridge name bridge id STP enabled interfaces You don't appear to have setup any bridges on your host. http://wiki.xen.org/wiki/HostConfiguration/Networking should lead you through the necessary steps. Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sandi Romih Subject: Re: Failed to run bootloader Date: Sat, 28 Apr 2012 01:06:42 +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> <1335550792.4881.76.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6669231586495614634==" Return-path: In-Reply-To: <1335550792.4881.76.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 --===============6669231586495614634== Content-Type: multipart/alternative; boundary=0015174766f85a8f1204beb128fa --0015174766f85a8f1204beb128fa Content-Type: text/plain; charset=ISO-8859-1 > You don't appear to have setup any bridges on your host. > > http://wiki.xen.org/wiki/HostConfiguration/Networking should lead you > through the necessary steps. > > Ian. > > Ian, Thanks for that. It looks like it has sorted out the issue. I am surprised that I did NOT have to setup my networking in this manner when I first installed openindiana. I just configured the vm with vif = bridge=eth0, and it worked. I had a feeling it was something silly... Thanks for your time and patience. Regards Sandi --0015174766f85a8f1204beb128fa Content-Type: text/html; charset=ISO-8859-1

You don't appear to have setup any bridges on your host.

http://wiki.xen.org/wiki/HostConfiguration/Networking should lead you
through the necessary steps.

Ian.

Ian,

Thanks for that. It looks like it has sorted out the issue.

I am surprised that I did NOT have to setup my networking in this manner when I first installed openindiana. I just configured the vm with vif = bridge=eth0, and it worked.

I had a feeling it was something silly...

Thanks for your time and patience.

Regards

Sandi

--0015174766f85a8f1204beb128fa-- --===============6669231586495614634== 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 --===============6669231586495614634==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to run bootloader Date: Sat, 28 Apr 2012 06:45:07 +0100 Message-ID: <1335591907.4881.77.camel@dagon.hellion.org.uk> 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> <1335550792.4881.76.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sandi Romih Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Sat, 2012-04-28 at 00:06 +0100, Sandi Romih wrote: > > > > > You don't appear to have setup any bridges on your host. > > http://wiki.xen.org/wiki/HostConfiguration/Networking should > lead you > through the necessary steps. > > Ian. > > > > Ian, > > > Thanks for that. It looks like it has sorted out the issue. Great! > I am surprised that I did NOT have to setup my networking in this > manner when I first installed openindiana. I just configured the vm > with vif = bridge=eth0, and it worked. FWIW this is a difference between xm and xl, perhaps you used xm the first time? > Thanks for your time and patience. No problem! Ian. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: Failed to run bootloader Date: Sat, 28 Apr 2012 07:12:05 +0100 Message-ID: <1335593525.4881.79.camel@dagon.hellion.org.uk> 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> <1335550792.4881.76.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sandi Romih Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Sat, 2012-04-28 at 00:06 +0100, Sandi Romih wrote: > I had a feeling it was something silly... By the way I updated a few pages on the wiki (e.g. http://wiki.xen.org/wiki/Getting_Started) to make the need to do this more obvious, since the HostConfiguration/Networking was not clearly linked to from the main landing pages. Ian.