Failed to run bootloader

Failed to run bootloader

[Sandi Romih]

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

Hello list,

I am attempting to run openindiana 151a in xen (xen 2.4-unstable rev 24785,
patched with this patch <http://xen.markmail.org/thread/d7qhk4vzikgo5ofc>),
but when attempting to create the VM I get the following error:

*root@dom0:/$xl create /etc/xen/vm/oi.cfg*
*Parsing config file /etc/xen/vm/oi.cfg*
*libxl: error: libxl_create.c:494:do_domain_create: failed to run
bootloader: -3*


Here is my oi.cfg file:

* vif = [ 'bridge=eth0, mac=00:14: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"*
*
*
*# Pre install booting*
* extra = "/platform/i86xpv/kernel/amd64/unix -B console=ttya"*
* disk = [ 'file:/mnt/media/comp_files/os-iso/oi151a.iso,xvdc:cdrom,r' ,
'phy:/dev/dom0/oi_boot,xvda,w' ]*
* bootloader = "/usr/bin/pygrub"*
*
*
*# Post install booting*
*# extra = "/platform/i86xpv/kernel/amd64/unix -B
zfs-bootfs=rpool/ROOT/openindiana,bootpath=/xpvd/xdf@51712:a"*
*# disk = [ 'phy:/dev/dom0/oi_boot,xvda,w' ]*
*
*
* on_shutdown = "destroy"*
* on_reboot = "restart"*
* on_crash = "destroy"*
*
*
* pci = [ '05:00.0' ]*



As a test, I checked if pygrub has any errors:

*root@dom0:/$pygrub /mnt/media/comp_files/os-iso/oi151a.iso *
*linux (kernel /var/run/xend/boot/boot_kernel.RomUm9)(ramdisk
/var/run/xend/boot/boot_ramdisk.WdnQsz)(args
"/platform/i86xpv/kernel/amd64/unix")*

I am assuming that pygrub can correctly handle the install media.



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 re-installed my whole system on an LVM disk, which I understand is
recommended for better disk performance.

I would appreciate any suggestions.

Regards

Sandi

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

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

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

Re: Failed to run bootloader

[Ian Campbell]

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.

Re: Failed to run bootloader

[Stefano Stabellini]

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

Re: Failed to run bootloader

[Ian Campbell]

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

Re: Failed to run bootloader

[Sandi Romih]

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

On Mon, Apr 23, 2012 at 1:30 PM, Ian Campbell <Ian.Campbell@citrix.com>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

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

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

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

Re: Failed to run bootloader

[Ian Campbell]

(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" <Ian.Campbell@citrix.com>
> 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.

Re: Failed to run bootloader

[Sandi Romih]

[-- 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

Re: Failed to run bootloader

[Sandi Romih]

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

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

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

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

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

Re: Failed to run bootloader

[Ian Campbell]

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.

Re: Failed to run bootloader

[Sandi Romih]

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

> 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

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

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

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

Re: Failed to run bootloader

[Ian Campbell]

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.

Re: Failed to run bootloader

[Ian Campbell]

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.

Re: Failed to run bootloader

[Sandi Romih]

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

>
> 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

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

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

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