On Sun, 2011-11-20 at 09:08 +0100, Alexandre Vaissière wrote: > Package: xen-hypervisor-4.1-amd64 > Version: 4.1.1-3 > Severity: important > > Whenever I try to start a domU, xm create failed for > 'Boot loader didn't return any data!'. > > % sudo xm create -c squeeze.cfg > Using config file "/etc/xen/squeeze.cfg". > Error: Boot loader didn't return any data! > > It seems related to the following error in dmesg > [1440.163935] pygrub[3654] trap invalid opcode ip:7f732a997c50 > sp:7fff60eb2258 error:0 in ld-2.13.so[7f732a984000+1f000]
An invalid op from the dynamic linker could be a more general bug or a bug in the python interpreter, but lets try and confirm before we pass this on. > Note that pygrub does NOT fail If I launch 'pygrub mydisk.img' on a standard > kernel boot, only if the hypervisor is used (tested with linux-image-3.0.0 > and linux-image-2.39.2) Can you try: /usr/lib/xen-default/bin/pygrub --args="root=/dev/xvda2 ro" --output=/var/run/xend/boot/xenbl.8881 /home/starch/data/xen/domains/squeeze/disk.img Since this is the actual command which is failing. You might want to replace /var/run/xend/boot/xenbl.8881 with your own temp file (which you will need to touch first). Having done that (and assuming it does repro the issue) can you run under gdb to see where the crash really is. Ian. -- Ian Campbell Current Noise: Venom - Sacrifice All rights reserved. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
