Re: Unable to install Precise domU PV on xen 4.2.0

[Fabio Fantoni <fantonifabio@tiscali.it>]

[-- Attachment #1.1.1: Type: text/plain, Size: 9235 bytes --]

Il 02/10/2012 12:34, Lukas Laukamp ha scritto:
> Am 02.10.2012 12:06, schrieb Fabio Fantoni:
>> Il 02/10/2012 11:58, Lukas Laukamp ha scritto:
>>> Am 02.10.2012 11:42, schrieb Fabio Fantoni:
>>>> Dom0 is wheezy 64 bit, kernel 3.2.23-1 from debian repository, xen 
>>>> 4.2.0 compiled from source
>>>>
>>>> When I try to install Precise domU PV with this xl configuration file:
>>>> --------------------------------------------
>>>> PRECISE.cfg
>>>> ----------------
>>>> name='PRECISE'
>>>> memory=1024
>>>> vcpus=2
>>>> disk=['/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda1,rw', 
>>>> '/mnt/vm/disks/PRECISE.disk2.xm,raw,xvda2,rw']
>>>> #disk=['/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda,rw']
>>>> vif=['bridge=xenbr0']
>>>> vfb=['vnc=1,vncunused=1,vnclisten=0.0.0.0,keymap=it']
>>>> xen_platform_pci=1
>>>> #bootloader='pygrub'
>>>> #kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
>>>> #extra = "(hd0,0)/grub/grub.cfg"
>>>> # Only for installation
>>>> kernel="/boot/domu/precise/vmlinuz"
>>>> ramdisk="/boot/domu/precise/initrd.gz"
>>>> extra = "debian-installer/exit/always_halt=true -- quiet console=hvc0"
>>>> --------------------------------------------
>>>>
>>>> The vmlinux and initrd take from here:
>>>> http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-amd64/current/images/netboot/xen/ 
>>>>
>>>>
>>>> xl create /etc/xen/PRECISE.cfg
>>>> Parsing config from /etc/xen/PRECISE.cfg
>>>> libxl: error: libxl_device.c:858:device_backend_callback: unable to 
>>>> disconnect device with path /local/domain/0/backend/vbd/2/51713
>>>> libxl: error: libxl_device.c:858:device_backend_callback: unable to 
>>>> disconnect device with path /local/domain/0/backend/vbd/2/51714
>>>> libxl: error: libxl_create.c:933:domcreate_launch_dm: unable to add 
>>>> disk devices
>>>> libxl: error: libxl_device.c:858:device_backend_callback: unable to 
>>>> disconnect device with path /local/domain/0/backend/vbd/2/51713
>>>> libxl: error: libxl_blktap2.c:73:libxl__device_destroy_tapdisk: 
>>>> Unable to find type aio disk /mnt/vm/disks/PRECISE.disk1.xm: No 
>>>> such file or directory
>>>> libxl: error: libxl_device.c:858:device_backend_callback: unable to 
>>>> disconnect device with path /local/domain/0/backend/vbd/2/51714
>>>> libxl: error: libxl.c:1465:devices_destroy_cb: 
>>>> libxl__devices_destroy failed for 2
>>>>
>>>> /mnt/vm/disks/PRECISE.disk1.xm exist, domU hvm with raw disks works
>>>>
>>>> Is xen bug, kernel bug or my error?
>>>> Thanks for any reply
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Xen-devel mailing list
>>>> Xen-devel@lists.xen.org
>>>> http://lists.xen.org/xen-devel
>>>
>>> Hello,
>>>
>>> I think that the raw parameter isn't needed and is the reason for 
>>> the device connecting error. Another way to install the guest would 
>>> be to use debootstrap. This definitly works.
>>>
>>> Best Regards
>>>
>>> Nessun virus nel messaggio.
>>> Controllato da AVG - www.avg.com <http://www.avg.com>
>>> Versione: 2012.0.2221 / Database dei virus: 2441/5303 - Data di 
>>> rilascio: 01/10/2012
>>>
>> Format seem necessary or give this error:
>> /etc/xen/PRECISE.cfg: config parsing error in disk specification: 
>> unknown value for format: near `xvda1' in 
>> `/mnt/vm/disks/PRECISE.disk1.xm,xvda1,rw'
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> http://lists.xen.org/xen-devel
>
> Hello,
>
> do you also have tried to install the guest with debootstrap?
>
> Best Regards
>
> Nessun virus nel messaggio.
> Controllato da AVG - www.avg.com <http://www.avg.com>
> Versione: 2012.0.2221 / Database dei virus: 2441/5303 - Data di 
> rilascio: 01/10/2012
>
I tried with Wheezy PV and install working, after I retried with Precise 
on new disk and working, seem was only filesystem problem for ext4 bug 
or bad blocks.
Now the problem is another one: I tried to start PV domUs but did not work.
On Wheezy domU I tried with pygrub, pv-grub and also with menu.lst with 
minimal grub1 configuration.
See below output and logs.

-----------------------------------------------------------------------------------------------
xl -vvv create /etc/xen/WHEEZY
-----------------------------------------------------------------------------------------------
WHEEZY.cfg     WHEEZYHVM.cfg
root@vfarm:~# xl -vvv create /etc/xen/WHEEZY.cfg
Parsing config from /etc/xen/WHEEZY.cfg
libxl: debug: libxl_create.c:1173:do_domain_create: ao 0x10700e0: 
create: how=(nil) callback=(nil) poller=0x106fc10
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk 
vdev=xvda spec.backend=unknown
libxl: debug: libxl_device.c:175:disk_try_backend: Disk vdev=xvda, 
backend phy unsuitable as phys path not a block device
libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk 
vdev=xvda, using backend tap
libxl: debug: libxl_create.c:677:initiate_domain_create: running bootloader
libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk 
vdev=(null) spec.backend=tap
libxl: debug: libxl.c:2310:libxl__device_disk_local_initiate_attach: 
locally attaching tap disk /mnt/vm/disks/WHEEZYPV.disk1.xm directly (ie 
without using blktap)
libxl: debug: libxl_bootloader.c:409:bootloader_disk_attached_cb: Config 
bootloader value: pygrub
libxl: debug: libxl_bootloader.c:425:bootloader_disk_attached_cb: 
Checking for bootloader in libexec path: /usr/lib/xen/bin/pygrub
libxl: debug: libxl_create.c:1186:do_domain_create: ao 0x10700e0: 
inprogress: poller=0x106fc10, flags=i
libxl: debug: libxl_event.c:512:libxl__ev_xswatch_register: watch 
w=0x1070510 wpath=/local/domain/9 token=3/0: register slotnum=3
libxl: debug: libxl_event.c:1667:libxl__ao_progress_report: ao 
0x10700e0: progress report: ignored
libxl: debug: libxl_bootloader.c:535:bootloader_gotptys: executing 
bootloader: /usr/lib/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader arg: 
/usr/lib/xen/bin/pygrub
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader arg: 
--output=/var/run/xen/bootloader.9.out
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader arg: 
--output-format=simple0
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader arg: 
--output-directory=/var/run/xen/bootloader.9.d
libxl: debug: libxl_bootloader.c:539:bootloader_gotptys: bootloader arg: 
/mnt/vm/disks/WHEEZYPV.disk1.xm
libxl: debug: libxl_event.c:457:watchfd_callback: watch w=0x1070510 
wpath=/local/domain/9 token=3/0: event epath=/local/domain/9
libxl: error: libxl_bootloader.c:628:bootloader_finished: bootloader 
failed - consult logfile /var/log/xen/bootloader.9.log
libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: bootloader 
[8800] exited with error status 1
libxl: debug: libxl_event.c:549:libxl__ev_xswatch_deregister: watch 
w=0x1070510 wpath=/local/domain/9 token=3/0: deregister slotnum=3
libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot 
(re-)build domain: -3
libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0x10700e0: 
complete, rc=-3
libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0x10700e0: destroy
xc: debug: hypercall buffer: total allocations:19 total releases:19
xc: debug: hypercall buffer: current allocations:0 maximum allocations:2
xc: debug: hypercall buffer: cache current size:2
xc: debug: hypercall buffer: cache hits:15 misses:2 toobig:2
-----------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------
/var/log/xen/bootloader.9.log
-----------------------------------------------------------------------------------------------
Traceback (most recent call last):
   File "/usr/lib/xen/bin/pygrub", line 20, in <module>
     import xen.lowlevel.xc
ImportError: No module named xen.lowlevel.xc
-----------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------
/etc/xen/WHEEZY.cfg
-----------------------------------------------------------------------------------------------
name='WHEEZY'
memory=1024
vcpus=2
#disk=['/mnt/vm/disks/PRECISE.disk1.xm,raw,xvda1,rw', 
'/mnt/vm/disks/PRECISE.disk2.xm,raw,xvda2,rw']
disk=['/mnt/vm/disks/WHEEZYPV.disk1.xm,raw,xvda,rw']
vif=['bridge=xenbr0']
vfb=['vnc=1,vncunused=1,vnclisten=0.0.0.0,keymap=it']
#xen_platform_pci=1
bootloader='pygrub'
#kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz"
#extra = "(hd0,0)/grub/grub.cfg"
# Only for installation
#kernel="/boot/domu/wheezy/vmlinuz"
#ramdisk="/boot/domu/wheezy/initrd.gz"
#extra = "debian-installer/exit/always_halt=true -- quiet console=tty0"
-----------------------------------------------------------------------------------------------

Before xen build I had do this change for python tools working:
vi Config.mk
PYTHON_PREFIX_ARG =

Are there other check or modify I must do for have pygrub working on xen 
4.2?
Thanks for any reply



[-- Attachment #1.1.2: Type: text/html, Size: 13002 bytes --]

[-- Attachment #1.2: Firma crittografica S/MIME --]
[-- Type: application/pkcs7-signature, Size: 4510 bytes --]

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

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