Re: [Xen-devel] Test result of xen-unstable changeset 25259

[Fantu <fantonifabio@xxxxxxxxxx>]

Ian Campbell-10 wrote
> 
> On Tue, 2012-05-08 at 14:22 +0100, Fantu wrote:
>> Ian Campbell-10 wrote
>> >
>> > When we went through this on you last posting this seemed to be related
>> > to the python path stuff on Ubuntu/Debian. However you don't mention
>> > tweaking that in your setup -- are you sure you have corrected this
>> > issue?
>> >
>> > If this isn't the issue then please can you provide (separately) full
>> > logs (xl cr -vvv & /var/log/xen/foo, etc) for both these cases.
>> >
>> "PYTHON_PREFIX_ARG =" in Config.mk solves python error on pygrub but not
>> domU pv boot error.
> 
> Your logs seem to show the opposite -- pygrub still fails by pvgrub
> works ok.
> 
>> --------------------------------------
>> lucid.cfg
>> --------
>> name="lucid"
>> vcpus=2
>> memory=512
>> disk=['/mnt/vm/disks/lucid.disk1.xm,raw,xvda1,rw',
>> '/mnt/vm/disks/lucid.disk2.xm,raw,xvda2,rw']
>> vif=['bridge=xenbr0']
>> vfb=['vnc=1,vncunused=1,vnclisten=0.0.0.0,keymap=it']
>> bootloader = '/usr/bin/pygrub'
>> #kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
>> #extra = "(hd0,0)/grub/grub.cfg"
>> --------------------------------------
>> 
>> With pygrub:
>> --------------------------------------
>> xl -vvv create /etc/xen/lucid.cfg
>> Parsing config file /etc/xen/lucid.cfg
>> libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk
>> vdev=xvda1 spec.backend=unknown
>> libxl: debug: libxl_device.c:137:disk_try_backend: Disk vdev=xvda1,
>> backend
>> phy unsuitable as phys path not a block device
>> libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk
>> vdev=xvda1, using backend tap
>> libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk
>> vdev=xvda2 spec.backend=unknown
>> libxl: debug: libxl_device.c:137:disk_try_backend: Disk vdev=xvda2,
>> backend
>> phy unsuitable as phys path not a block device
>> libxl: debug: libxl_device.c:219:libxl__device_disk_set_backend: Disk
>> vdev=xvda2, using backend tap
>> libxl: debug: libxl_device.c:183:libxl__device_disk_set_backend: Disk
>> vdev=xvda1 spec.backend=tap
>> libxl: debug: libxl.c:1689:libxl_device_disk_local_attach: locally
>> attaching
>> tap disk /mnt/vm/disks/lucid.disk1.xm directly (ie without using blktap)
>> libxl: error: libxl_create.c:603:do_domain_create: failed to run
>> bootloader:
>> -3
> 
> Do you still get the same error about xen.lowlevel.xc as before if you
> run
>       pygrub /mnt/vm/disks/lucid.disk1.xm
> by hand?
> 
> Ian.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@.xen
> http://lists.xen.org/xen-devel
> 
---------------------------------------------
pygrub /mnt/vm/disks/lucid.disk1.xm 
Traceback (most recent call last):
  File "/usr/local/bin/pygrub", line 822, in <module>
    raise RuntimeError, "Unable to find partition containing kernel"
RuntimeError: Unable to find partition containing kernel
---------------------------------------------

About pv-grub I think it fails with:
... (from xl create...)
xc: error: panic: xc_dom_bzimageloader.c:588: xc_dom_probe_bzimage_kernel:
kernel is not a bzImage: Invalid kernel
...
And after seems start as hvm domU but is not working and I must destroy it.

--
View this message in context: 
http://xen.1045712.n5.nabble.com/Test-result-of-xen-unstable-changeset-25259-tp5691153p5694426.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

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