[Xen-devel] Test result of xen-unstable changeset 25459

[Fantu <fantonifabio@xxxxxxxxxx>]

Dom0:
Wheezy 64 bit with kernel from package linux-image-3.2.0-2-amd64 version
3.2.18-1, package blktap-dkms and all dependency packages for xen, spice and
usb redirection.
-------------------------
/etc/modules
------------
loop max_loop=64
xenfs
xen-evtchn
blktap
-------------------------
hg clone http://xenbits.xen.org/xen-unstable.hg (in this build changeset is
25459:f6bfaf9daa50)
vi config/StdGNU.mk # Workaround for Wheezy with multiarch support, there
are parts that use LIBDIR set here instead of the one in configure (libdir)
LIBLEAFDIR_x86_64 ?= lib
vi Config.mk
PYTHON_PREFIX_ARG =
-------------------------
Added some patches:
- autoconf: add variable for pass arbitrary options to qemu upstream v3
- tools: Improve make deb
- libxc: do not "panic" if a kernel is not a bzImage.
- tools/hotplug/Linux/init.d/: added other xen kernel modules on xencommons
start
-------------------------
./configure --enable-qemuu-spice --enable-qemuu-usbredir
--enable-qemuu-debug
-------------------------
make deb


-------------------------
Old issue:
-------------
- Network not working after save/restore on W7 64 bit domU with qemu
upstream
-------------
- HVM domU continue booting even if qemu-xen not start correctly:
xl create /etc/xen/PRECISEHVM.cfg
Parsing config from /etc/xen/PRECISEHVM.cfg
xc: info: VIRTUAL MEMORY ARRANGEMENT:
  Loader:        0000000000100000->000000000019dc88
  TOTAL:         0000000000000000->000000003f800000
  ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
  4KB PAGES: 0x0000000000000200
  2MB PAGES: 0x00000000000001fb
  1GB PAGES: 0x0000000000000000
libxl: error: libxl_exec.c:371:spawn_timeout: domain 26 device model:
startup timed out
libxl: error: libxl_dm.c:1066:device_model_spawn_outcome: domain 26 device
model: spawn failed (rc=-3)
libxl: error: libxl_qmp.c:641:libxl__qmp_initialize: Connection error:
Connection refused
Daemon running with PID 9137
root@vfarm:/mnt/vm/xen/xen-unstable.hg# xl list
Name                                        ID   Mem VCPUs      State  
Time(s)
Domain-0                                     0  2047     8     r-----   
1791.8
PRECISEHVM                                  26  1015     1     ------      
0.0
-------------------------

-------------------------
Fixed issue:
-------------
-
http://xen.1045712.n5.nabble.com/Build-error-of-libxl-in-xen-unstable-changeset-25374-td5709046.html
-------------------------

-------------------------
Old regression:
-------------
- CRITICAL - PV domU unable to start:
With pygrub:
xl create /etc/xen/lucid.cfg
Parsing config file /etc/xen/lucid.cfg
libxl: error: libxl_bootloader.c:517:bootloader_finished: bootloader failed
- consult logfile /var/log/xen/bootloader.14.log
libxl: error: libxl_exec.c:108:libxl_report_child_exitstatus: bootloader
[6196] exited with error status 1
--------------
Traceback (most recent call last):
  File "/usr/bin/pygrub", line 822, in <module>
    raise RuntimeError, "Unable to find partition containing kernel"
RuntimeError: Unable to find partition containing kernel
--------------
With pv-grub:
Starts but arrive at grubdom (see with xl console)

Tried also with xen-unstable old commit and old kernel package, same
problem, cause unknown.
------------------------- 

--
View this message in context: 
http://xen.1045712.n5.nabble.com/Test-result-of-xen-unstable-changeset-25459-tp5709334.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