XenParavirtOpsHelp: Difference between revisions

From Xen
Jump to navigationJump to search
(Created page with "<!-- MoinMoin name: XenParavirtOpsHelp --> <!-- Comment: --> <!-- WikiMedia name: XenParavirtOpsHelp --> <!-- Page revision: 00000006 --> <!-- Original date: Wed Oct 2…")
 
(fix link)
 
(2 intermediate revisions by 2 users not shown)
Line 4: Line 4:
<!-- Page revision: 00000006 -->
<!-- Page revision: 00000006 -->
<!-- Original date: Wed Oct 26 18:39:52 2011 (1319654392000000) -->
<!-- Original date: Wed Oct 26 18:39:52 2011 (1319654392000000) -->

{{Needs_Additions|It is not quite clear what this page is for: an introduction would be useful. Maybe it is what information people are required to supply when they need help?}}


<!-- ! TOC here -->
<!-- ! TOC here -->

== Xen Paravirt Ops Help Page ==

[[XenParavirtOps#Nothing_is_helping.21_Help.21.21]]

When debugging [[XenParavirtOps]] related issues, this page lists all the information you '''NEED''' to provide so the problem can be diagnosed and debugged!

Please mail questions/answers/patches/etc to the [http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel Xen-devel mailing list].



= Things we need =
= Things we need =
Line 72: Line 79:




To get it, follow the steps outlined in [[[XenSerialConsole]]] We '''NEED''' the full serial debug output, not just the crash section but also before to see in what state the machine is in.
To get it, follow the steps outlined in [[XenSerialConsole]] We '''NEED''' the full serial debug output, not just the crash section but also before to see in what state the machine is in.


* Full PCI output of all devices:
* Full PCI output of all devices:
Line 173: Line 180:
[[Category:PVOPS]]
[[Category:PVOPS]]
[[Category:Developers]]
[[Category:Developers]]
[[Category:Project]]

Latest revision as of 11:30, 11 April 2012


Xen Paravirt Ops Help Page

XenParavirtOps#Nothing_is_helping.21_Help.21.21

When debugging XenParavirtOps related issues, this page lists all the information you NEED to provide so the problem can be diagnosed and debugged!

Please mail questions/answers/patches/etc to the Xen-devel mailing list.


Things we need

To help figure out the problem there are couple of things that we need:

  • full serial output
  • lspci -vvv output
  • .config file contents
  • dmidecode output
  • grub.conf or grub2.conf file

Specifically

  • Full serial console output. It looks something like this:

 __  __            _  _    ___      ___   ___  _ ____  ____  ____  
 \ \/ /___ _ __   | || |  / _ \    / _ \ / _ \/ |___ \|___ _ \ 
  \  // _ \ '_ \  | || |_| | | |__| | | | (_) | | __) | __) | __)   |
  /  \  __/ | | | |__   _| |_| |__| |_| |\__, | |/ __/ / __/ / __/ 
 /_/\_\___|_| |_|    |_|(_)___/    \___/   /_/|_|_____|_____|_____|
                                                                   
(XEN) Xen version 4.0-100128 (konrad@dumpdata.com) (gcc version 4.1.2 20070115 (SUSE Linux)) Thu Jan 28 21:29:17 UTC 2010
(XEN) Latest ChangeSet: unavailable
(XEN) Console output is synchronous.
(XEN) Command line: com1=115200,8n1,0xd800,0 sync_console console=com1,vga guest_loglvl=all dom0_mem=max:2G 
(XEN) Video information:
(XEN)  VGA is text mode 80x25, font 8x16
(XEN)  VBE/DDC methods: V2; EDID transfer time: 1 seconds
(XEN)  EDID info not retrieved because of reasons unknown
(XEN) Disc information:
(XEN)  Found 3 MBR signatures
(XEN)  Found 3 EDD information structures
(XEN) Xen-e820 RAM map:
(XEN)  0000000000000000 - 000000000009f400 (usable)
(XEN)  000000000009f400 - 00000000000a0000 (reserved)
(XEN)  00000000000e4000 - 0000000000100000 (reserved)
(XEN)  0000000000100000 - 00000000cfe90000 (usable)
(XEN)  00000000cfe90000 - 00000000cfe9e000 (ACPI data)
(XEN)  00000000cfe9e000 - 00000000cfee0000 (ACPI NVS)
...
(XEN) Xen is relinquishing VGA console.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen)
(XEN) Freed 164kB init memory.
mapping kernel into physical memory
Xen: setup ISA identity maps
about to get started...
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Linux version 2.6.31.1-xen0-00364-gaa75c0a-dirty (konrad@phenom.dumpdata.com) (gcc version 4.1.2 20070115 (SUSE Linux)) #89 SMP Thu Jan 28 21:29:24 UTC 2010
[    0.000000] Command line: debug selinux=0 initrd_ignore_loglevel sysrq_always_enable ip=:::::eth0:dhcp earlyprintk=xen console=hvc0 loglevel=10 xen-pciback.hide=(07:00.0)(08:05.0)(08:07.0)(08:07.2) pci=resource_alignment=08:05.0 initcall_debug bb_inittab=/etc/inittab-debug iscsi_max_lun=1024 silent=3 
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
[    0.000000]   AMD AuthenticAMD
[    0.000000]   Centaur CentaurHauls
[    0.000000] xen_release_chunk: looking at area pfn 80000-cfe90
[    0.000000] xen_release_chunk: looking at area pfn cfeee-cfef0
[    0.000000] xen_release_chunk: looking at area pfn cff00-e0000
[    0.000000] xen_release_chunk: looking at area pfn f0000-fec00
[    0.000000] xen_release_chunk: looking at area pfn fec01-fee00
...


To get it, follow the steps outlined in XenSerialConsole We NEED the full serial debug output, not just the crash section but also before to see in what state the machine is in.

  • Full PCI output of all devices:
#lspci -vvv
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
        Subsystem: Elitegroup Computer Systems Device 1b61
        Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
        Latency: 0
        Capabilities: [c4] HyperTransport: Slave or Primary Interface
                Command: BaseUnitID=0 UnitCnt=12 MastHost- DefDir- DUL-
                Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 IsocEn+ LSEn- ExtCTL- 64b-
                Link Config 0: MLWI=16bit DwFcIn- MLWO=16bit DwFcOut- LWI=16bit DwFcInEn- LWO=16bit DwFcOutEn-
                Link Control 1: CFlE- CST- CFE- <LkFail+ Init- EOC+ TXO+ <CRCErr=0 IsocEn- LSEn- ExtCTL- 64b-
                Link Config 1: MLWI=8bit DwFcIn- MLWO=8bit DwFcOut- LWI=8bit DwFcInEn- LWO=8bit DwFcOutEn-
                Revision ID: 3.00
                Link Frequency 0: [a]
                Link Error 0: <Prot- <Ovfl- <EOC- CTLTm-
                Link Frequency Capability 0: 200MHz+ 300MHz- 400MHz+ 500MHz- 600MHz+ 800MHz+ 1.0GHz+ 1.2GHz- 1.4GHz- 1.6GHz- Vend-
                Feature Capability: IsocFC- LDTSTOP+ CRCTM- ECTLT- 64bA- UIDRD-
                Link Frequency 1: 200MHz
                Link Error 1: <Prot- <Ovfl- <EOC- CTLTm-
                Link Frequency Capability 1: 200MHz- 300MHz- 400MHz- 500MHz- 600MHz- 800MHz- 1.0GHz- 1.2GHz- 1.4GHz- 1.6GHz- Vend-
                Error Handling: PFlE- OFlE- PFE- OFE- EOCFE- RFE- CRCFE- SERRFE- CF- RE- PNFE- ONFE- EOCNFE- RNFE- CRCNFE- SERRNFE-
                Prefetchable memory behind bridge Upper: 00-00
                Bus Number: 00
        Capabilities: [54] HyperTransport: UnitID Clumping
        Capabilities: [40] HyperTransport: Retry Mode
        Capabilities: [9c] HyperTransport: #1a
        Capabilities: [f8] HyperTransport: #1c
...


  • Your .config file. It looks as so:

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.11
# Tue Apr 27 18:18:16 2010
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_TIME=y
...
  • Your DMI of your machine:
#dmidecode

SMBIOS 2.5 present.
51 structures occupying 1971 bytes.
Table at 0x0009F800.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
        Vendor: American Megatrends Inc.
        Version: 080014 
        Release Date: 11/23/2009
        Address: 0xF0000
        Runtime Size: 64 kB
        ROM Size: 1024 kB
        Characteristics:
...
  • grub contents file.
title XenRedHat
        root (hd0,0)
       kernel /xen-4.0.0-rc9.gz console=vga noreboot loglvl=all  vga=text-80x50,keep iommu=off apic=debug guest_loglvl=all
       module /vmlinuz-2.6.31.13  root=/dev/sda1 ro console=hvc0  earlyprintk=xen nomodeset initcall_debug debug loglevel=10
       module /ramdisk.img.gz


Summary

To summarize, we need four things:

  • full serial output
  • lspci -vvv output
  • .config file contents
  • dmidecode output
  • grub contents

to help you along.

Retrieved from "https://wiki.xenproject.org/index.php?title=XenParavirtOpsHelp&oldid=3100"