Your message dated Fri, 22 Feb 2019 19:01:22 +0100 with message-id <d79cfc22-6895-ab9b-19b0-b68013a71...@knorrie.org> and subject line Re: xen-hypervisor-4.6-amd64: Can't start a VM has caused the Debian Bug report #806226, regarding xen-hypervisor-4.6-amd64: Can't start a VM to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: xen-hypervisor-4.6-amd64 Version: 4.6.0-1 Severity: normal Dear maintaners, I was using XEN 4.4 on that machine ("unstable") and want to switch to 4.6. All xen stuff was uninstalled (XEN 4.4), the machine restarted before installing 4.6. When I uninstall XEN 4.4 (libxenlight4.4) it deinstall also part of QEMU and when I reinstall QEMU libxenlight-4.4 aws reinstalled. First try (noeload is the file descripting the VM, was OK with xen4.4, the file is enclosed): xl create neoload /usr/lib/xen-4.6/bin/xl: error while loading shared libraries: libxenlight-4.6.so: cannot open shared object file: No such file or directory The "/usr/lib/xen-4.6/lib" contains only : /usr/lib/xen-4.6/lib total 64 drwxr-xr-x 4 root root 4096 nov. 25 14:45 . drwxr-xr-x 4 root root 4096 nov. 25 14:45 .. drwxr-xr-x 9 root root 4096 nov. 25 14:45 fs -rw-r--r-- 1 root root 14592 nov. 1 21:58 libfsimage.so -rw-r--r-- 1 root root 31160 nov. 1 21:58 libxenstat.so drwxr-xr-x 4 root root 4096 nov. 25 14:45 python Where is "libxenlight" ? cd /usr find ./ -name 'libxenlight*' ./lib/x86_64-linux-gnu/libxenlight-4.4.so Only the libxenlight-4.4 is present ? There is a dependency whith "qemu" so it was reinstalled with qemu. I try to reinstall libxen-4.6 (4.6.0.1 was marked as installed) a and cd /usr find ./ -name 'libxenlight*' ./lib/x86_64-linux-gnu/libxenlight-4.6.so ./lib/x86_64-linux-gnu/libxenlight-4.4.so give another try : xl create neoload Parsing config from neoload After many minutes nothing happens so I try to give up with Ctrl+c ... without any success. Can't kill the xl process even with kill -9. Libvirt was not ok (searching libxenlight-4.6, and can't alse been restarted or even killed, so I restart the system and get some "oops" while stopping (10 minutes to stop with systemd!!!). Nov 25 15:49:53 k2000 kernel: [ 2408.822702] INFO: task libvirtd:6305 blocked for more than 120 seconds. Nov 25 15:49:53 k2000 kernel: [ 2408.822704] Not tainted 4.3.0-x #4 Nov 25 15:49:53 k2000 kernel: [ 2408.822705] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 25 15:49:53 k2000 kernel: [ 2408.822706] libvirtd D ffffffff810766ab 0 6305 1 0x00000004 Nov 25 15:49:53 k2000 kernel: [ 2408.822709] ffff880052d9a700 0000000000000286 ffff880236208000 ffff880236207ce8 Nov 25 15:49:53 k2000 kernel: [ 2408.822710] ffffffff81c1b734 ffff880052d9a700 00000000ffffffff ffffffff81c1b738 Nov 25 15:49:53 k2000 kernel: [ 2408.822712] ffffffff8153914a ffffffff81c1b730 ffffffff815393d5 ffffffff8153a4a0 Nov 25 15:49:53 k2000 kernel: [ 2408.822713] Call Trace: Nov 25 15:49:53 k2000 kernel: [ 2408.822717] [<ffffffff8153914a>] ? schedule+0x2a/0x70 Nov 25 15:49:53 k2000 kernel: [ 2408.822719] [<ffffffff815393d5>] ? schedule_preempt_disabled+0x5/0x10 Nov 25 15:49:53 k2000 kernel: [ 2408.822720] [<ffffffff8153a4a0>] ? __mutex_lock_slowpath+0x90/0x110 Nov 25 15:49:53 k2000 kernel: [ 2408.822722] [<ffffffff8153a536>] ? mutex_lock+0x16/0x30 Nov 25 15:49:53 k2000 kernel: [ 2408.822724] [<ffffffff81397347>] ? xs_talkv+0x67/0x1d0 Nov 25 15:49:53 k2000 kernel: [ 2408.822725] [<ffffffff8139770f>] ? xs_watch+0x4f/0x70 Nov 25 15:49:53 k2000 kernel: [ 2408.822727] [<ffffffff81397bd6>] ? register_xenbus_watch+0x96/0x110 Nov 25 15:49:53 k2000 kernel: [ 2408.822728] [<ffffffff8139a57f>] ? xenbus_file_write+0x48f/0x520 Nov 25 15:49:53 k2000 kernel: [ 2408.822731] [<ffffffff810bab75>] ? cgroup_post_fork+0x75/0x100 Nov 25 15:49:53 k2000 kernel: [ 2408.822732] [<ffffffff812e570a>] ? cpumask_next_and+0x2a/0x40 Nov 25 15:49:53 k2000 kernel: [ 2408.822734] [<ffffffff81138bfe>] ? __vfs_write+0x1e/0xe0 Nov 25 15:49:53 k2000 kernel: [ 2408.822736] [<ffffffff811393c9>] ? vfs_write+0x99/0x180 Nov 25 15:49:53 k2000 kernel: [ 2408.822737] [<ffffffff81139f3d>] ? SyS_write+0x3d/0xa0 Nov 25 15:49:53 k2000 kernel: [ 2408.822739] [<ffffffff8153c236>] ? entry_SYSCALL_64_fastpath+0x16/0x75 Nov 25 15:50:47 k2000 kernel: [ 2462.781116] e1000e: enp0s31f6 NIC Link is Down Nov 25 15:50:47 k2000 kernel: [ 2462.781133] br1: port 1(enp0s31f6) entered disabled state Nov 25 15:51:53 k2000 kernel: [ 2529.121353] INFO: task libvirtd:6305 blocked for more than 120 seconds. Nov 25 15:51:53 k2000 kernel: [ 2529.121355] Not tainted 4.3.0-x #4 Nov 25 15:51:53 k2000 kernel: [ 2529.121356] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 25 15:51:53 k2000 kernel: [ 2529.121357] libvirtd D ffffffff810766ab 0 6305 1 0x00000004 Nov 25 15:51:53 k2000 kernel: [ 2529.121359] ffff880052d9a700 0000000000000286 ffff880236208000 ffff880236207ce8 Nov 25 15:51:53 k2000 kernel: [ 2529.121361] ffffffff81c1b734 ffff880052d9a700 00000000ffffffff ffffffff81c1b738 Nov 25 15:51:53 k2000 kernel: [ 2529.121363] ffffffff8153914a ffffffff81c1b730 ffffffff815393d5 ffffffff8153a4a0 Nov 25 15:51:53 k2000 kernel: [ 2529.121364] Call Trace: Nov 25 15:51:53 k2000 kernel: [ 2529.121368] [<ffffffff8153914a>] ? schedule+0x2a/0x70 Nov 25 15:51:53 k2000 kernel: [ 2529.121369] [<ffffffff815393d5>] ? schedule_preempt_disabled+0x5/0x10 Nov 25 15:51:53 k2000 kernel: [ 2529.121371] [<ffffffff8153a4a0>] ? __mutex_lock_slowpath+0x90/0x110 Nov 25 15:51:53 k2000 kernel: [ 2529.121372] [<ffffffff8153a536>] ? mutex_lock+0x16/0x30 Nov 25 15:51:53 k2000 kernel: [ 2529.121374] [<ffffffff81397347>] ? xs_talkv+0x67/0x1d0 Nov 25 15:51:53 k2000 kernel: [ 2529.121376] [<ffffffff8139770f>] ? xs_watch+0x4f/0x70 Nov 25 15:51:53 k2000 kernel: [ 2529.121377] [<ffffffff81397bd6>] ? register_xenbus_watch+0x96/0x110 Nov 25 15:51:53 k2000 kernel: [ 2529.121379] [<ffffffff8139a57f>] ? xenbus_file_write+0x48f/0x520 Nov 25 15:51:53 k2000 kernel: [ 2529.121381] [<ffffffff810bab75>] ? cgroup_post_fork+0x75/0x100 Nov 25 15:51:53 k2000 kernel: [ 2529.121383] [<ffffffff812e570a>] ? cpumask_next_and+0x2a/0x40 Nov 25 15:51:53 k2000 kernel: [ 2529.121385] [<ffffffff81138bfe>] ? __vfs_write+0x1e/0xe0 Nov 25 15:51:53 k2000 kernel: [ 2529.121387] [<ffffffff811393c9>] ? vfs_write+0x99/0x180 Nov 25 15:51:53 k2000 kernel: [ 2529.121388] [<ffffffff81139f3d>] ? SyS_write+0x3d/0xa0 Nov 25 15:51:53 k2000 kernel: [ 2529.121390] [<ffffffff8153c236>] ? entry_SYSCALL_64_fastpath+0x16/0x75 After restarting the system : libvirtd seems to be OK (no messages in log) Xen processes seems to bo OK : ps -ef | grep xen root 49 2 0 16:00 ? 00:00:00 [xenwatch] root 50 2 0 16:00 ? 00:00:00 [xenbus] root 57 2 0 16:00 ? 00:00:00 [xenbus_frontend] root 3180 1 0 16:00 ? 00:00:00 /usr/lib/xen-4.6/bin/xenstored --pid-file=/var/run/xenstore.pid root 3191 1 0 16:00 ? 00:00:00 /usr/lib/xen-4.6/bin/xenconsoled --pid-file=/var/run/xenconsoled.pid So I try : xl create neoload Parsing config from neoload xc: error: Could not open kernel image '/usr/lib/xen/boot/hvmloader' (2 = No such file or directory): Internal error libxl: error: libxl_dom.c:1006:libxl__build_hvm: hvm building failed libxl: error: libxl_create.c:1142:domcreate_rebuild_done: cannot (re-)build domain: -3 libxl: error: libxl_dm.c:2004:libxl__destroy_device_model: xs_rm failed for /local/domain/0/device-model/1 libxl: error: libxl_dm.c:1956:kill_device_model: unable to find device model pid in /local/domain/1/image/device-model-pid libxl: error: libxl.c:1628:libxl__destroy_domid: libxl__destroy_device_model failed for 1 libxl: error: libxl.c:1591:libxl__destroy_domid: non-existant domain 1 libxl: error: libxl.c:1549:domain_destroy_callback: unable to destroy guest with domid 1 libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 1 failed The directory "/usr/lib/xen" does not exist on my system ! And no "hvmloader" program as in previous versions. The /usr/lib/xen-4.6 directory does not even contain a "boot" subdirectory, so I don't try to install a symlink. Regards -- System Information: Debian Release: stretch/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.3.0-x (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xen-hypervisor-4.6-amd64 depends on no packages. Versions of packages xen-hypervisor-4.6-amd64 recommends: ii xen-utils-4.6 4.6.0-1 xen-hypervisor-4.6-amd64 suggests no packages. -- no debconf information# ostype='other' name='neoload' memory=3072 vcpus=1 uuid='cb72cd1c-ffcf-4768-99d8-c69f8573799e' on_crash='destroy' on_poweroff='destroy' on_reboot='restart' localtime=0 builder='hvm' extid=0 # pour le boot initial sur le CD #boot='d' boot='c' disk=[ 'phy:/dev/DUO/NEOLOAD,xvda,w', # 'file:/BAIES/BTRFS_2/ISOS/debian-7.3.0-amd64-DVD-1.iso,hdd:cdrom,r', ] vif=[ 'mac=00:16:3e:90:54:01,bridge=br0' ] vnc=1 vncunused=1 apic=0 acpi=1 pae=1 usb=1 usbdevice='tablet' keymap='fr' serial='pty' stdvga=0
--- End Message ---
--- Begin Message ---On 1/22/19 5:24 PM, Hans van Kranenburg wrote: > [...] > > Please note that unless there's a response within a month from now, we > will close the bug report. Closing now. Hans
--- End Message ---
