Hi, Please reply-all and not only to me.
On 01/07/2018 12:07 AM, frm wrote: >> The first step here is to collect more information. Things that are or are >> not >> working with Xen setups can be difficult to track down, since it can be >> related >> to any combination of anything like hardware, hypervisor, dom0, domU etc... >> >> From your description I guess that changing domU from >> linux-image-4.9.0-3-amd64 to linux-image-4.9.0-5-amd64 while all other >> things remain the same caused the issue. Is that right? > Yes. If I revert back to 4.9.0-3-amd64 at the guest, I can boot in hvm mode. Ok, great. >> I see you're using Debian Release: 8.10, which might imply Xen 4.4 and the >> jessie kernel for the dom0. >> >> As seen from the dom0, can you please reply with `uname -a`, `xen info` and >> `lspci -v` output. > uname -a > Linux nuc1 4.9.0-3-amd64 #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 > GNU/Linux So that's a stretch kernel package for the dom0. How did you end up reporting this from a Jessie system? > xen info > host : nuc1 > release : 4.9.0-3-amd64 > version : #1 SMP Debian 4.9.30-2+deb9u5 (2017-09-19) > machine : x86_64 > nr_cpus : 4 > max_cpu_id : 3 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 1895 > hw_caps : > b7ebfbff:77faf3bf:2c100800:00000021:00000001:000027ab:00000000:00000100 > virt_caps : hvm hvm_directio > total_memory : 16309 > free_memory : 366 > sharing_freed_memory : 0 > sharing_used_memory : 0 > outstanding_claims : 0 > free_cpus : 0 > xen_major : 4 > xen_minor : 8 > xen_extra : .1 > xen_version : 4.8.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 : > xen_commandline : loglvl=all noreboot dom0_mem=3328M max=3328M > dom0_max_vcpus=4 dom0_vcpus_pin gnttab_max_frames=256 > cc_compiler : gcc (Debian 6.3.0-18) 6.3.0 20170516 > cc_compile_by : ian.jackson > cc_compile_domain : eu.citrix.com > cc_compile_date : Thu Sep 7 18:24:26 UTC 2017 > build_id : bc5b60fc44b11ff01ffbaea6cbc8cf9d > xend_config_format : 4 Ok, xen 4.8 > lspci -v > 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) > Subsystem: Intel Corporation Haswell-ULT DRAM Controller > Flags: bus master, fast devsel, latency 0 > Capabilities: [e0] Vendor Specific Information: Len=0c <?> > > 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated > Graphics Controller (rev 09) (prog-if 00 [VGA controller]) > Subsystem: Intel Corporation Haswell-ULT Integrated Graphics > Controller > Flags: bus master, fast devsel, latency 0, IRQ 77 > Memory at f7800000 (64-bit, non-prefetchable) [size=4M] > Memory at e0000000 (64-bit, prefetchable) [size=256M] > I/O ports at f000 [size=64] > [virtual] Expansion ROM at 000c0000 [disabled] [size=128K] > Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [d0] Power Management version 2 > Capabilities: [a4] PCI Advanced Features > Kernel driver in use: i915 > Kernel modules: i915 > > 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev > 09) > Subsystem: Intel Corporation Haswell-ULT HD Audio Controller > Flags: bus master, fast devsel, latency 0, IRQ 78 > Memory at f7c34000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 2 > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) > (prog-if 30 [XHCI]) > Subsystem: Intel Corporation 8 Series USB xHCI HC > Flags: medium devsel, IRQ 73 > Memory at f7c20000 (64-bit, non-prefetchable) [size=64K] > Capabilities: [70] Power Management version 2 > Capabilities: [80] MSI: Enable+ Count=1/8 Maskable- 64bit+ > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > > 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) > Subsystem: Intel Corporation 8 Series HECI > Flags: bus master, fast devsel, latency 0, IRQ 75 > Memory at f7c3e000 (64-bit, non-prefetchable) [size=32] > Capabilities: [50] Power Management version 3 > Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Kernel driver in use: mei_me > Kernel modules: mei_me > > 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-V > (rev 04) > Subsystem: Intel Corporation Ethernet Connection I218-V > Flags: bus master, fast devsel, latency 0, IRQ 72 > Memory at f7c00000 (32-bit, non-prefetchable) [size=128K] > Memory at f7c3c000 (32-bit, non-prefetchable) [size=4K] > I/O ports at f080 [size=32] > Capabilities: [c8] Power Management version 2 > Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [e0] PCI Advanced Features > Kernel driver in use: e1000e > Kernel modules: e1000e > > 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) > Subsystem: Intel Corporation 8 Series HD Audio Controller > Flags: bus master, fast devsel, latency 0, IRQ 76 > Memory at f7c30000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [50] Power Management version 3 > Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ > Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 > Capabilities: [100] Virtual Channel > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > > 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) > (prog-if 20 [EHCI]) > Subsystem: Intel Corporation 8 Series USB EHCI > Flags: medium devsel, IRQ 23 > Memory at f7c3b000 (32-bit, non-prefetchable) [size=1K] > Capabilities: [50] Power Management version 3 > Capabilities: [58] Debug port: BAR=1 offset=00a0 > Capabilities: [98] PCI Advanced Features > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > > 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) > Subsystem: Intel Corporation 8 Series LPC Controller > Flags: bus master, medium devsel, latency 0 > Capabilities: [e0] Vendor Specific Information: Len=0c <?> > Kernel driver in use: lpc_ich > Kernel modules: lpc_ich > > 00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 [AHCI > mode] (rev 04) (prog-if 01 [AHCI 1.0]) > Subsystem: Intel Corporation 8 Series SATA Controller 1 [AHCI mode] > Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 74 > I/O ports at f0d0 [size=8] > I/O ports at f0c0 [size=4] > I/O ports at f0b0 [size=8] > I/O ports at f0a0 [size=4] > I/O ports at f060 [size=32] > Memory at f7c3a000 (32-bit, non-prefetchable) [size=2K] > Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- > Capabilities: [70] Power Management version 3 > Capabilities: [a8] SATA HBA v1.0 > Kernel driver in use: ahci > Kernel modules: ahci > > 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) > Subsystem: Intel Corporation 8 Series SMBus Controller > Flags: medium devsel, IRQ 18 > Memory at f7c39000 (64-bit, non-prefetchable) [size=256] > I/O ports at f040 [size=32] > Kernel driver in use: i801_smbus > Kernel modules: i2c_i801 > >> >> Since the domU is running linux-image-4.9.0-5-amd64 that can only mean it's >> the kernel update just done, which is version 4.9.65-3+deb9u2 > It is running but only in pv mode, not in hvm mode > (commenting out pvh=1 in the guest config file). > >> When reporting kernel versions, note that the package name and the actual >> version can be different. So please always include the real package version, >> like 4.9.65-3 or whatever in case of linux-image-4.9.0-4-amd64. >> >> Anything you could do yourself to narrow down the issue would help. >> > What happens is that pygrub succeeds in processing menu.lst at domU. > It seems not to load the kernel however (but if I do boot in pv mode it does). > I get somehow the impression that the xen drivers for hvm are not loaded. > But I cannot check that. > If there is some logging I can turn on, I am happy to do so. Ok, thanks for the additional information. I included the debian bug email address again and did not remove any of your reply, so it's visible. Sadly, I have no ready to go answer now, but at least this adds more info to get forward. Hans
