[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] xen hypervisor does not like my Dom0 LVM partition: I/O Errors

On Wed, Nov 30, 2016 at 4:58 AM Roger Pau Monné <roger.pau@xxxxxxxxxx> wrote:
Please avoid top-posting, it breaks the conversation flow.

On Wed, Nov 30, 2016 at 02:19:25AM +0000, Jeff Swicegood wrote:
> A check of the logs shows you are right--there were no lost interrupt
> messages. I  just assumed since it crashed it was the same situation.  But
> syslog is one of the first services to go when the crash starts happening,
> so all those I/O errors and the like are usually not logged but I can see
> them in the terminal flying by. I cannot write to any files when the crash
> is happening
> [image: 20161129_202954.jpg][image: 20161129_174028.jpg][image:
> 20161129_174024.jpg][image: 20161129_173838.jpg][image: 20161129_173744.jpg]so
> I cannot capture xl dmesg very well. I  just assumed since it crashed it
> was the same situation. I am not able to verify if it is reporting a lost
> interrupt. In fact the only error at all was:

Hm, I'm afraid there's not much we can do without having access to the debug
keys output. Could you hook a serial console to that box so that you can get the
serial output? Alternatively it might have SOL, which can also be used by Xen.

> [31832.152507] Mount of device (uid: 0) not owned by requested user (uid:
> 1000)
> [31832.152655] Reading sb failed; rc = [-1]
> Updating grub with the boot option ioapic_ack=old did not help.

Can you paste the output of `xl dmesg` after booting with ioapic_ack=old?


I'm working on getting debug_keys output.

Here is the output with the  ioapic=old option:

jaga@jaga-Desktop:~$ sudo xl dmesg
[sudo] password for jaga:
(XEN) Xen version 4.7.0 (Ubuntu 4.7.0-0ubuntu2) (stefan.bader@xxxxxxxxxxxxx) (gcc (Ubuntu 6.2.0-5ubuntu12) 6.2.0 20161005) debug=n Fri Oct  7 19:25:16 UTC 2016
(XEN) Bootloader: GRUB 2.02~beta2-36ubuntu11.1
(XEN) Command line: placeholder ioapic_ack=old
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN) Disc information:
(XEN)  Found 2 MBR signatures
(XEN)  Found 5 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009e400 (usable)
(XEN)  000000000009e400 - 00000000000a0000 (reserved)
(XEN)  00000000000e2c00 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000bf780000 (usable)
(XEN)  00000000bf780000 - 00000000bf798000 (ACPI data)
(XEN)  00000000bf798000 - 00000000bf7da000 (ACPI NVS)
(XEN)  00000000bf7da000 - 00000000c0000000 (reserved)
(XEN)  00000000fee00000 - 00000000fee01000 (reserved)
(XEN)  00000000ffe00000 - 0000000100000000 (reserved)
(XEN)  0000000100000000 - 0000000640000000 (usable)
(XEN) ACPI: RSDP 000FB940, 0014 (r0 ACPIAM)
(XEN) ACPI: RSDT BF780000, 0048 (r1 030111 RSDT1120 20110301 MSFT       97)
(XEN) ACPI: FACP BF780200, 0084 (r1 030111 FACP1120 20110301 MSFT       97)
(XEN) ACPI: DSDT BF7804B0, C469 (r1  A1682 A1682001        1 INTL 20060113)
(XEN) ACPI: FACS BF798000, 0040
(XEN) ACPI: APIC BF780390, 00D8 (r1 030111 APIC1120 20110301 MSFT       97)
(XEN) ACPI: MCFG BF780470, 003C (r1 030111 OEMMCFG  20110301 MSFT       97)
(XEN) ACPI: OEMB BF798040, 0072 (r1 030111 OEMB1120 20110301 MSFT       97)
(XEN) ACPI: HPET BF78F4B0, 0038 (r1 030111 OEMHPET  20110301 MSFT       97)
(XEN) ACPI: DMAR BF7980C0, 0140 (r1    AMI  OEMDMAR        1 MSFT       97)
(XEN) ACPI: ASPT BF7984B0, 0034 (r6 030111 PerfTune 20110301 MSFT       97)
(XEN) ACPI: OSFR BF78F4F0, 00B0 (r1 030111 OEMOSFR  20110301 MSFT       97)
(XEN) ACPI: SSDT BF79A940, 0363 (r1 DpgPmm    CpuPm       12 INTL 20060113)
(XEN) System RAM: 24567MB (25156728kB)
(XEN) Domain heap initialised
(XEN) IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 9, version 32, address 0xfec8a000, GSI 24-47
(XEN) Enabling APIC mode:  Flat.  Using 2 I/O APICs
(XEN) [VT-D]  RMRR address range bf7da000..bf7d9fff not in reserved memory; need "iommu_inclusive_mapping=1"?
(XEN) [VT-D]  RMRR (bf7da000, bf7d9fff) is incorrect
(XEN) Failed to parse ACPI DMAR.  Disabling VT-d.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Detected 3207.349 MHz processor.
(XEN) Initing memory sharing.
(XEN) PCI: Not using MCFG for segment 0000 bus 00-ff
(XEN) I/O virtualisation disabled
(XEN)  -> Using old ACK method
(XEN) Platform timer is 14.318MHz HPET
(XEN) Allocated console ring of 16 KiB.
(XEN) VMX: Supported advanced features:
(XEN)  - APIC MMIO access virtualisation
(XEN)  - APIC TPR shadow
(XEN)  - Extended Page Tables (EPT)
(XEN)  - Virtual-Processor Identifiers (VPID)
(XEN)  - Virtual NMI
(XEN)  - MSR direct-access bitmap
(XEN) HVM: ASIDs enabled.
(XEN) HVM: VMX enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB
(XEN) Brought up 8 CPUs
(XEN) Dom0 has maximum 816 PIRQs
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x225f000
(XEN)  Dom0 alloc.:   0000000624000000->0000000628000000 (6160573 pages to be allocated)
(XEN)  Init. ramdisk: 000000063d7a4000->000000063ffffdd5
(XEN)  Loaded kernel: ffffffff81000000->ffffffff8225f000
(XEN)  Init. ramdisk: 0000000000000000->0000000000000000
(XEN)  Phys-Mach map: 0000008000000000->0000008002f348c8
(XEN)  Start info:    ffffffff8225f000->ffffffff8225f4b4
(XEN)  Page tables:   ffffffff82260000->ffffffff82275000
(XEN)  Boot stack:    ffffffff82275000->ffffffff82276000
(XEN)  TOTAL:         ffffffff80000000->ffffffff82400000
(XEN)  ENTRY ADDRESS: ffffffff81f83180
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Scrubbing Free RAM on 1 nodes using 4 CPUs
(XEN) ..................................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 308kB init memory. 
Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.