ar16@imapmail.org
2012-Sep-29 00:13 UTC
Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
Migrating from a stable/production install of Opensuse 12.1 + Xen
4.{1,2} + ''xm'' toolstack to Opensuse 12.2 + Xen 4.2 + xl
toolstack +
Opensuse 12.2 has been problematic.
To simplify troubleshooting, I''m attempting to init a new/clean 12.2
Guest
The procedure is to init an HVM Guest, boot to a physically-attached
Opensuse 12.2 Install DVD, and install a new/clean 12.2 Guest.
Atm, the guest is failing to launch, with a series of errors:
...
libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot
(re-)build domain: -3
libxl: error: libxl_dm.c:1251:libxl__destroy_device_model: could
not find device-model''s pid for dom 6
libxl: error: libxl.c:1429:libxl__destroy_domid:
libxl__destroy_device_model failed for 6
...
@wiki (http://wiki.xen.org/wiki/Xen_4.2_Release_Notes) we''re advised:
"... it is strongly recommended that users evaluate Xen 4.2 with
XL for their use cases and report any omissions or blockers
...".
I was advised @ #xen to ''report'' this to this list, rather
than to our
distro (already done anyway @
https://bugzilla.novell.com/show_bug.cgi?id=782835).
System info,
lsb_release -a
LSB Version: n/a
Distributor ID: SUSE LINUX
Description: openSUSE 12.2 (x86_64)
Release: 12.2
Codename: Mantis
uname -a
Linux test 3.4.6-2.10-xen #1 SMP Thu Jul 26 09:36:26 UTC
2012 (641c197) x86_64 x86_64 x86_64 GNU/Linux
pkg info,
rpm -qa | grep -i xen
ipset-kmp-xen-6.12_k3.4.6_2.10-2.3.1.x86_64
kernel-xen-3.4.6-2.10.1.x86_64
kernel-xen-devel-3.4.6-2.10.1.x86_64
patterns-openSUSE-xen_server-12.2-5.5.1.x86_64
xen-4.2.0_01-204.1.x86_64
xen-devel-4.2.0_01-204.1.x86_64
xen-doc-html-4.2.0_01-204.1.x86_64
xen-doc-pdf-4.2.0_01-204.1.x86_64
xen-kmp-default-4.2.0_01_k3.4.6_2.10-204.1.x86_64
xen-libs-4.2.0_01-204.1.x86_64
xen-tools-4.2.0_01-204.1.x86_64
Xen/xl info,
xl info
host : test
release : 3.4.6-2.10-xen
version : #1 SMP Thu Jul 26 09:36:26 UTC
2012 (641c197)
machine : x86_64
nr_cpus : 4
max_cpu_id : 5
nr_nodes : 1
cores_per_socket : 4
threads_per_core : 1
cpu_mhz : 2806
hw_caps :
178bf3ff:efd3fbff:00000000:00001310:00802001:00000000:000037ff:00000000
virt_caps : hvm
total_memory : 7935
free_memory : 6844
sharing_freed_memory : 0
sharing_used_memory : 0
free_cpus : 0
xen_major : 4
xen_minor : 2
xen_extra : .0_01-204.1
xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p
hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler : credit
xen_pagesize : 4096
platform_params : virt_start=0xffff800000000000
xen_changeset : 25844
xen_commandline : conring_size=64
vga=gfx-1280x1024x16 log_buf_len=4M console=vga
console_timestamps dom0_mem=1024M dom0_vcpus_pin=true
dom0_max_vcpus=4 sched=credit apic_verbosity=verbose
iommu=verbose cpuidle=1 cpufreq=xen clocksource=acpi
numa=on
cc_compiler : gcc (SUSE Linux) 4.7.1 20120723
[gcc-4_7-branch revision 189773
cc_compile_by : abuild
cc_compile_domain :
cc_compile_date : Fri Sep 28 15:30:52 UTC 2012
xend_config_format : 4
Verifying HVM availability,
xl dmesg | grep -i hvm
(XEN) [2012-09-28 22:53:56] HVM: ASIDs enabled.
(XEN) [2012-09-28 22:53:56] HVM: SVM enabled
(XEN) [2012-09-28 22:53:56] HVM: Hardware Assisted
Paging (HAP) detected
(XEN) [2012-09-28 22:53:56] HVM: HAP page sizes: 4kB,
2MB, 1GB
The config I''m using,
cat test.cfg
name = ''test''
builder = ''hvm''
acpi = 1
apic = 1
boot = ''f''
disk = [ ''phy:/dev/VG0/boot,xvda,w'',
''phy:/dev/VG0/swap,xvdb,w'',
''phy:/dev/VG0/root,xvdc,w'',
''phy:/dev/cdrom,xvdd:cdrom,r'',]
vif = [ ''mac=00:16:3E:55:00:01, model=rtl8139,
type=ioemu, bridge=br0, vifname=vifO'',]
vfb = [ ''type=vnc, vncdisplay=1,
vnclisten=127.0.0.1'' ]
maxmem = 1024
vcpus = 4
localtime = 0
netif = ''yes''
on_shutdown = ''destroy''
on_reboot = ''destroy''
on_crash = ''destroy''
The failing launch cmd,
xl -vvv create -c /home/ar/test.cfg
Parsing config from /home/ar/test.cfg
libxl: debug: libxl_create.c:1173:do_domain_create: ao
0x7e1c80: create: how=(nil) callback=(nil)
poller=0x7e1ce0
libxl: debug:
libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=xvda spec.backend=unknown
libxl: debug:
libxl_device.c:265:libxl__device_disk_set_backend: Disk
vdev=xvda, using backend phy
libxl: debug:
libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=xvdb spec.backend=unknown
libxl: debug:
libxl_device.c:265:libxl__device_disk_set_backend: Disk
vdev=xvdb, using backend phy
libxl: debug:
libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=xvdc spec.backend=unknown
libxl: debug:
libxl_device.c:265:libxl__device_disk_set_backend: Disk
vdev=xvdc, using backend phy
libxl: debug:
libxl_device.c:229:libxl__device_disk_set_backend: Disk
vdev=xvdd spec.backend=unknown
libxl: debug:
libxl_device.c:265:libxl__device_disk_set_backend: Disk
vdev=xvdd, using backend phy
libxl: debug: libxl_create.c:677:initiate_domain_create:
running bootloader
libxl: debug:
libxl_bootloader.c:321:libxl__bootloader_run: not a PV
domain, skipping bootloader
libxl: debug:
libxl_event.c:561:libxl__ev_xswatch_deregister: watch
w=0x7e2690: deregister unregistered
libxl: debug:
libxl_numa.c:435:libxl__get_numa_candidate: New best
NUMA placement candidate found: nr_nodes=1, nr_cpus=4,
nr_vcpus=8, free_memkb=6842
libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA
placement candidate with 1 nodes, 4 cpus and 6842 KB
free selected
xc: detail: elf_parse_binary: phdr: paddr=0x100000
memsz=0x9e028
xc: detail: elf_parse_binary: memory: 0x100000 ->
0x19e028
xc: info: VIRTUAL MEMORY ARRANGEMENT:
Loader: 0000000000100000->000000000019e028
TOTAL: 0000000000000000->000000007f800000
ENTRY ADDRESS: 0000000000100000
xc: info: PHYSICAL MEMORY ALLOCATION:
4KB PAGES: 0x0000000000000200
2MB PAGES: 0x00000000000003fb
1GB PAGES: 0x0000000000000000
xc: detail: elf_load_binary: phdr 0 at 0x0x7f8d58910000
-> 0x0x7f8d589a4eb5
libxl: error: libxl_create.c:901:domcreate_rebuild_done:
cannot (re-)build domain: -3
libxl: error:
libxl_dm.c:1251:libxl__destroy_device_model: could not
find device-model''s pid for dom 6
libxl: error: libxl.c:1429:libxl__destroy_domid:
libxl__destroy_device_model failed for 6
libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao
0x7e1c80: complete, rc=-3
libxl: debug: libxl_create.c:1186:do_domain_create: ao
0x7e1c80: inprogress: poller=0x7e1ce0, flags=ic
libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao
0x7e1c80: destroy
xc: debug: hypercall buffer: total allocations:871 total
releases:871
xc: debug: hypercall buffer: current allocations:0
maximum allocations:4
xc: debug: hypercall buffer: cache current size:4
xc: debug: hypercall buffer: cache hits:863 misses:4
toobig:4
ar16@imapmail.org
2012-Sep-29 01:34 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
Using exactly the same setup and configuration, but changing toolstack from xl -> xm, i.e. service xend start xm create -c test.cfg The Guest launches, and is accessible via VNC (very slow response; liklely a different issue)
Joseph Glanville
2012-Sep-30 02:32 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
On 29 September 2012 11:34, <ar16@imapmail.org> wrote:> Using exactly the same setup and configuration, but changing toolstack > from xl -> xm, i.e. > > service xend start > xm create -c test.cfg > > The Guest launches, and is accessible via VNC (very slow response; > liklely a different issue) > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-develHi, Does changing the guest disk specification to hda/hdb/hdc/hdd syntax correct the problem? Also, can you post the qemu-dm logs for that domain? (usually in /var/log/xen/qemu-dm-*) Joseph. -- CTO | Orion Virtualisation Solutions | www.orionvm.com.au Phone: 1300 56 99 52 | Mobile: 0428 754 846
ar16@imapmail.org
2012-Sep-30 06:22 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
hi On Sat, Sep 29, 2012, at 07:32 PM, Joseph Glanville wrote:> Does changing the guest disk specification to hda/hdb/hdc/hdd syntax > correct the problem?no, it does not. with config -- ... disk = [ ''phy:/dev/VG0/boot,hda,w'', ''phy:/dev/VG0/swap,hdb,w'', ''phy:/dev/VG0/root,hdc,w'', ''phy:/dev/cdrom,hdd:cdrom,r'', ... executing xl -vvv create -c /home/ar/test.cfg still returns, Parsing config from /home/ar/test.cfg libxl: debug: libxl_create.c:1173:do_domain_create: ao 0xd278e0: create: how=(nil) callback=(nil) poller=0xd281f0 libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hda spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hda, using backend phy libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hdb spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hdb, using backend phy libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hdc spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hdc, using backend phy libxl: debug: libxl_device.c:229:libxl__device_disk_set_backend: Disk vdev=hdd spec.backend=unknown libxl: debug: libxl_device.c:265:libxl__device_disk_set_backend: Disk vdev=hdd, using backend phy libxl: debug: libxl_create.c:677:initiate_domain_create: running bootloader libxl: debug: libxl_bootloader.c:321:libxl__bootloader_run: not a PV domain, skipping bootloader libxl: debug: libxl_event.c:561:libxl__ev_xswatch_deregister: watch w=0xd28790: deregister unregistered libxl: debug: libxl_numa.c:435:libxl__get_numa_candidate: New best NUMA placement candidate found: nr_nodes=1, nr_cpus=4, nr_vcpus=5, free_memkb=6841 libxl: detail: libxl_dom.c:192:numa_place_domain: NUMA placement candidate with 1 nodes, 4 cpus and 6841 KB free selected xc: detail: elf_parse_binary: phdr: paddr=0x100000 memsz=0x9e028 xc: detail: elf_parse_binary: memory: 0x100000 -> 0x19e028 xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000019e028 TOTAL: 0000000000000000->000000003f000000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001f7 1GB PAGES: 0x0000000000000000 xc: detail: elf_load_binary: phdr 0 at 0x0x7f9da35c1000 -> 0x0x7f9da3655eb5 libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:1251:libxl__destroy_device_model: could not find device-model''s pid for dom 70 libxl: error: libxl.c:1429:libxl__destroy_domid: libxl__destroy_device_model failed for 70 libxl: debug: libxl_event.c:1497:libxl__ao_complete: ao 0xd278e0: complete, rc=-3 libxl: debug: libxl_create.c:1186:do_domain_create: ao 0xd278e0: inprogress: poller=0xd281f0, flags=ic libxl: debug: libxl_event.c:1469:libxl__ao__destroy: ao 0xd278e0: destroy xc: debug: hypercall buffer: total allocations:482 total releases:482 xc: debug: hypercall buffer: current allocations:0 maximum allocations:4 xc: debug: hypercall buffer: cache current size:4 xc: debug: hypercall buffer: cache hits:474 misses:4 toobig:4> Also, can you post the qemu-dm logs for that domain? (usually in > /var/log/xen/qemu-dm-*)cat /var/log/xen/qemu-dm-test.log domid: 69 Using file /dev/VG0/boot in read-write mode Using file /dev/VG0/swap in read-write mode Using file /dev/VG0/root in read-write mode Using file /dev/cdrom in read-only mode Watching /local/domain/0/device-model/69/logdirty/cmd Watching /local/domain/0/device-model/69/command Watching /local/domain/69/cpu char device redirected to /dev/pts/2 qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 4c29586f-89bd-8c01-e00a-5af6a7ce8267 Time offset set 0 char device redirected to /dev/pts/3 xen be: console-0: xen be: console-0: initialise() failed initialise() failed populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/69/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/4c29586f-89bd-8c01-e00a-5af6a7ce8267/vncpasswd. medium change watch on `hdd'' (index: 3): /dev/cdrom I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Log-dirty: no command yet. xen be: console-0: xen be: console-0: initialise() failed initialise() failed vcpu-set: watch node error. xen be: console-0: xen be: console-0: initialise() failed initialise() failed xs_read(/local/domain/69/log-throttling): read error qemu: ignoring not-understood drive `/local/domain/69/log-throttling'' medium change watch on `/local/domain/69/log-throttling'' - unknown device, ignored xen be: console-0: xen be: console-0: initialise() failed initialise() failed
ar16@imapmail.org
2012-Oct-01 00:41 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
hoping to provide some form of useful debug info, per 3.2. Debugging your program using Valgrind gdbserver and GDB http://valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.gdbserver i''ve attached, below, the output of: valgrind -v --vgdb=yes --vgdb-error=0 --track-origins=yes --trace-children=yes --leak-check=full --show-reachable=yes xl create -c /home/ar/test.cfg & the corresponding gdb session: gdb xl (gdb) target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=7667 ... (gdb) continue ... (gdb) bt ... which appears to get a SIGTRAP at 101 libxl_utils.h: No such file or directory. although, ls -al /usr/include/libxl_utils.h -rw-r--r-- 1 root root 5.7K Sep 18 14:42 /usr/include/libxl_utils.h =====================================================================valgrind -v --vgdb=yes --vgdb-error=0 --track-origins=yes --trace-children=yes --leak-check=full --show-reachable=yes xl create -c /home/ar/test.cfg ==7667== Memcheck, a memory error detector ==7667== Copyright (C) 2002-2012, and GNU GPL''d, by Julian Seward et al. ==7667== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info ==7667== Command: xl create -c /home/ar/test.cfg ==7667=--7667-- Valgrind options: --7667-- -v --7667-- --vgdb=yes --7667-- --vgdb-error=0 --7667-- --track-origins=yes --7667-- --trace-children=yes --7667-- --leak-check=full --7667-- --show-reachable=yes --7667-- Contents of /proc/version: --7667-- Linux version 3.4.6-2.10-xen (geeko@buildhost) (gcc version 4.7.1 20120723 [gcc-4_7-branch revision 189773] (SUSE Linux) ) #1 SMP Thu Jul 26 09:36:26 UTC 2012 (641c197) --7667-- Arch and hwcaps: AMD64, amd64-sse3-cx16-lzcnt --7667-- Page sizes: currently 4096, max supported 4096 --7667-- Valgrind library directory: /usr/lib64/valgrind --7667-- Reading syms from /usr/sbin/xl --7667-- Considering /usr/lib/debug/.build-id/30/a64409d9dfee58a099b01b8e833b012f11f0bd.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /lib64/ld-2.15.so --7667-- Considering /usr/lib/debug/.build-id/e4/2d5feaef8b50f76c5d9011480021d8c76be03a.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/valgrind/memcheck-amd64-linux --7667-- Considering /usr/lib/debug/usr/lib64/valgrind/memcheck-amd64-linux.debug .. --7667-- .. CRC is valid --7667-- object doesn''t have a dynamic symbol table --7667-- Scheduler: using generic scheduler lock implementation. --7667-- Reading suppressions file: /usr/lib64/valgrind/default.supp ==7667== (action at startup) vgdb me ... ==7667== embedded gdbserver: reading from /tmp/vgdb-pipe-from-vgdb-to-7667-by-root-on-server ==7667== embedded gdbserver: writing to /tmp/vgdb-pipe-to-vgdb-from-7667-by-root-on-server ==7667== embedded gdbserver: shared mem /tmp/vgdb-pipe-shared-mem-vgdb-7667-by-root-on-server ==7667===7667== TO CONTROL THIS PROCESS USING vgdb (which you probably ==7667== don''t want to do, unless you know exactly what you''re doing, ==7667== or are doing some strange experiment): ==7667== /usr/lib64/valgrind/../../bin/vgdb --pid=7667 ...command... ==7667===7667== TO DEBUG THIS PROCESS USING GDB: start GDB like this ==7667== /path/to/gdb xl ==7667== and then give GDB the following command ==7667== target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=7667 ==7667== --pid is optional if only one valgrind process is running ==7667=--7667-- REDIR: 0x4017980 (strlen) redirected to 0x3806c751 (vgPlain_amd64_linux_REDIR_FOR_strlen) --7667-- Reading syms from /usr/lib64/valgrind/vgpreload_core-amd64-linux.so --7667-- Considering /usr/lib/debug/.build-id/58/fafcae89b15a60beb5a94f5cebe506d63adbe2.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so --7667-- Considering /usr/lib/debug/.build-id/19/a54751b3d366463830a2dcab6372e03b1cba14.debug .. --7667-- .. build-id is valid --7667-- REDIR: 0x40177f0 (index) redirected to 0x4c2c930 (index) --7667-- REDIR: 0x4017870 (strcmp) redirected to 0x4c2d940 (strcmp) --7667-- Reading syms from /usr/lib64/libxlutil.so.1.0.0 --7667-- Considering /usr/lib/debug/.build-id/57/db42dff0f5c8eaf2270b9b2c1749372e7a43eb.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libxenlight.so.2.0.0 --7667-- Considering /usr/lib/debug/.build-id/c5/612d35a8a81737c65c7373b51b513aae115ead.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libxenctrl.so.4.2.0 --7667-- Considering /usr/lib/debug/.build-id/b2/95761d280c399a5a6fcad017488f114c9eb134.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libyajl.so.2.0.1 --7667-- Considering /usr/lib/debug/.build-id/99/9a0d33091222f1538223325db7f5e243dd63c9.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /lib64/libpthread-2.15.so --7667-- Considering /usr/lib/debug/.build-id/d5/a497713b5ae7d06971fb34530b63d89a42e0af.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /lib64/libc-2.15.so --7667-- Considering /usr/lib/debug/.build-id/74/a39090ae55f5852f5051263d722588db13bf55.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libxenguest.so.4.2.0 --7667-- Considering /usr/lib/debug/.build-id/f0/4b4f86cb8506da6a8bfe4d5294c9f7708f8ddb.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libxenstore.so.3.0.1 --7667-- Considering /usr/lib/debug/.build-id/82/5de7c92321f509c1f56f5c82de84f1391d5b16.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/local/lib64/libblktapctl.so.1.0.0 --7667-- Reading syms from /lib64/libutil-2.15.so --7667-- Considering /usr/lib/debug/.build-id/ff/73a066c7363459b2c6a83f8530333bacea5b53.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libuuid.so.1.3.0 --7667-- Considering /usr/lib/debug/.build-id/6b/2300887663497904f5bd17e51e0f6e04849058.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /lib64/libdl-2.15.so --7667-- Considering /usr/lib/debug/.build-id/d0/ec4dbdb0d7b15bb7a6454fefa923d5de1daf40.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/libbz2.so.1.0.6 --7667-- Considering /usr/lib/debug/.build-id/ec/1a7cb75fb00b3027653c7e44ab2ae5e1bdc323.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /usr/lib64/liblzma.so.5.0.3 --7667-- Considering /usr/lib/debug/.build-id/40/ab1743eda0b177bfd7097de713d3842973ef98.debug .. --7667-- .. build-id is valid --7667-- Reading syms from /lib64/libz.so.1.2.7 --7667-- Considering /usr/lib/debug/.build-id/07/c94c65d4108bb9372f7943566cc01c54f161ca.debug .. --7667-- .. build-id is valid --7667-- REDIR: 0x596e4d0 (strncasecmp) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x5968590 (strnlen) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x596c200 (strcasecmp) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x5967e00 (strcpy) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x5968460 (strlen) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x596afe0 (memset) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x5970bb0 (memcpy@@GLIBC_2.14) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x59666b0 (strcat) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x5969f80 (__GI_strrchr) redirected to 0x4c2c750 (__GI_strrchr) --7667-- REDIR: 0x59684b0 (__GI_strlen) redirected to 0x4c2ccb0 (__GI_strlen) --7667-- REDIR: 0x5962bb0 (malloc) redirected to 0x4c2c200 (malloc) --7667-- REDIR: 0x59720f0 (strchrnul) redirected to 0x4c2f2c0 (strchrnul) --7667-- REDIR: 0x59630d0 (free) redirected to 0x4c2aef0 (free) --7667-- REDIR: 0x59dca60 (__strcpy_chk) redirected to 0x4c2f330 (__strcpy_chk) --7667-- REDIR: 0x5970c00 (__GI_memcpy) redirected to 0x4c2dc70 (memcpy@@GLIBC_2.14) --7667-- REDIR: 0x5968670 (strncmp) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x59686b0 (__GI_strncmp) redirected to 0x4c2d180 (__GI_strncmp) --7667-- REDIR: 0x59668f0 (__GI_strchr) redirected to 0x4c2c830 (__GI_strchr) --7667-- REDIR: 0x59668b0 (index) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) Parsing config from /home/ar/test.cfg --7667-- REDIR: 0x5963160 (realloc) redirected to 0x4c2c400 (realloc) --7667-- REDIR: 0x5966970 (strcmp) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) --7667-- REDIR: 0x59669b0 (__GI_strcmp) redirected to 0x4c2d8f0 (__GI_strcmp) --7667-- REDIR: 0xffffffffff600000 (???) redirected to 0x3806c733 (vgPlain_amd64_linux_REDIR_FOR_vgettimeofday) --7667-- REDIR: 0x5963c30 (calloc) redirected to 0x4c2a020 (calloc) --7667-- REDIR: 0x5975870 (__memset_x86_64) redirected to 0x4c2ed70 (memset) --7667-- REDIR: 0x5969f40 (rindex) redirected to 0x4a24750 (_vgnU_ifunc_wrapper) ==7667== Warning: noted but unhandled ioctl 0x305000 with no size/direction hints ==7667== This could cause spurious value errors to appear. ==7667== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==7667== Conditional jump or move depends on uninitialised value(s) ==7667== at 0x505FBC4: libxl__domain_build_info_setdefault (libxl_utils.h:101) ==7667== by 0x505B404: libxl_domain_need_memory (libxl.c:3514) ==7667== by 0x40CB8C: create_domain (xl_cmdimpl.c:1591) ==7667== by 0x410A60: main_create (xl_cmdimpl.c:3905) ==7667== by 0x406FFF: main (xl.c:267) ==7667== Uninitialised value was created by a stack allocation ==7667== at 0x4014225: _dl_runtime_resolve (dl-trampoline.S:43) ==7667===7667== (action on error) vgdb me ... =====================================================================gdb xl GNU gdb (GDB) SUSE (7.4.50.20120603-78.5) Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/sbin/xl...Reading symbols from /usr/lib/debug/usr/sbin/xl.debug...done. done. (gdb) target remote | /usr/lib64/valgrind/../../bin/vgdb --pid=7667 Remote debugging using | /usr/lib64/valgrind/../../bin/vgdb --pid=7667 relaying data between gdb and process 7667 Reading symbols from /lib64/ld-linux-x86-64.so.2...Reading symbols from /usr/lib/debug/lib64/ld-2.15.so.debug...done. done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 [Switching to Thread 7667] 0x00000000040014e0 in _start () from /lib64/ld-linux-x86-64.so.2 (gdb) continue Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. 0x000000000505fbc4 in libxl_cpu_bitmap_alloc (max_cpus=6, cpumap=0x7fefff238, ctx=0x6f1e0b0) at libxl_utils.h:101 101 libxl_utils.h: No such file or directory. (gdb) bt #0 0x000000000505fbc4 in libxl_cpu_bitmap_alloc (max_cpus=6, cpumap=0x7fefff238, ctx=0x6f1e0b0) at libxl_utils.h:101 #1 libxl__domain_build_info_setdefault (gc=gc@entry=0x7fefff060, b_info=b_info@entry=0x7fefff220) at libxl_create.c:215 #2 0x000000000505b405 in libxl_domain_need_memory (ctx=<optimized out>, b_info=b_info@entry=0x7fefff220, need_memkb=need_memkb@entry=0x7fefff0f0) at libxl.c:3514 #3 0x000000000040cb8d in freemem (b_info=0x7fefff220) at xl_cmdimpl.c:1591 #4 create_domain (dom_info=dom_info@entry=0x7fefff4d0) at xl_cmdimpl.c:1874 #5 0x0000000000410a61 in main_create (argc=3, argv=0x7fefffac0) at xl_cmdimpl.c:3905 #6 0x0000000000407000 in main (argc=3, argv=0x7fefffac0) at xl.c:267 (gdb) ======================================================================
ar16@imapmail.org
2012-Oct-01 02:00 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
On Sun, Sep 30, 2012, at 05:41 PM, ar16@imapmail.org wrote:> 101 libxl_utils.h: No such file or directory.looking in a xen source tree cd src/xen-4.2-testing.hg grep libxl_utils `grep -rlni "libxl__domain_build_info_setdefault" tools/` tools/libxl/libxl_internal.h:#include "libxl_utils.h" cat tools/libxl/libxl_internal.h ... #define _protected #endif #include "flexarray.h" 76 #include "libxl_utils.h" #include "libxl_json.h" ... given, ls -1 /usr/include/libxl_* /usr/include/libxl_event.h /usr/include/libxl_json.h /usr/include/libxl_utils.h /usr/include/libxl_uuid.h should that not be: - #include "libxl_utils.h" + #include <libxl_utils.h> - #include "libxl_json.h" + #include <libxl_json.h> ?
Olaf Hering
2012-Oct-01 14:52 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
On Fri, Sep 28, ar16@imapmail.org wrote:> Atm, the guest is failing to launch, with a series of errors: > > ... > libxl: error: libxl_create.c:901:domcreate_rebuild_done: cannot > (re-)build domain: -3This is caused by an incorrect patch in the xen package, libxl__build_hvm() returns an error unconditional. Olaf
ar16@imapmail.org
2012-Oct-01 15:11 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
On Mon, Oct 1, 2012, at 07:52 AM, Olaf Hering wrote:> This is caused by an incorrect patch in the xen package, > libxl__build_hvm() returns an error unconditional.That''s in the *distro* xen package, then? Over on the Opensuse side?
Olaf Hering
2012-Oct-01 15:21 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
On Mon, Oct 01, ar16@imapmail.org wrote:> > > On Mon, Oct 1, 2012, at 07:52 AM, Olaf Hering wrote: > > This is caused by an incorrect patch in the xen package, > > libxl__build_hvm() returns an error unconditional. > > That''s in the *distro* xen package, then? Over on the Opensuse side?Yes, the package update from 4.1 to 4.2 is broken in some areas as you found out. The package will be fixed soon. Olaf
ar16@imapmail.org
2012-Oct-01 15:24 UTC
Re: Xen HVM Guest fails (errors) to launch on Opensuse 12.2''s Xen 4.2 + ''xl'' toolstack
On Mon, Oct 1, 2012, at 08:21 AM, Olaf Hering wrote:> > That''s in the *distro* xen package, then? Over on the Opensuse side? > > Yes, the package update from 4.1 to 4.2 is broken in some areas as you > found out. The package will be fixed soon.Thanks. Moving this back to https://bugzilla.novell.com/show_bug.cgi?id=782835 ...