[opensuse-virtual] Opensuse xen kernel not working on IBM x3550M4 7914
Hello, Currently we are trying to install a xen machine on a IBM x 3550M4 7914 machine Without any succes. We try to get xen running with opensuse 12.3 or opensuse 13.1 Installing opensuse is no problem, the default ( desktop ) kernel is working ok. when we install the xen-kernel and xen packages openSuse 13.1 -> booting the xen kernel makes the machine freeze and does not react at all. openSuse 12.3 -> booting the xen kernel makes - the keyboard/mouse inresponsive - the video also seems to hang ( only distorted bitmap can be seen on screen ) - However with openSuse 12.3 networking is working and console login is possible - I can not identify from the logs the specific error. - additionally lsusb gives the output "unable to initialize libusb: -99" Anybody any idea where to start trouble shooting? BR, Jeroen xm dmesg __ __ _ _ ____ _____ ___ _ _ ____ ____ _ _ \ \/ /___ _ __ | || | |___ \ |___ / / _ \/ | / | |___ \|___ \ | || | \ // _ \ '_ \ | || |_ __) | |_ \ | | | | |__| | __) | __) || || |_ / \ __/ | | | |__ _| / __/ _ ___) | | |_| | |__| |_ / __/ / __/ |__ _| /_/\_\___|_| |_| |_|(_)_____(_)____/___\___/|_| |_(_)_____|_____(_) |_| |_____| (XEN) Xen version 4.2.3_01-1.22.4 (abuild@) (gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]) Mon Dec 2 12:22:01 UTC 2013 (XEN) Latest ChangeSet: 26064 (XEN) Bootloader: GRUB2 2.00 (XEN) Command line: (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 0 MBR signatures (XEN) Found 0 EDD information structures (XEN) Multiboot-e820 RAM map: (XEN) 0000000000000000 - 000000000006c000 (usable) (XEN) 000000000006c000 - 000000000006d000 (ACPI NVS) (XEN) 000000000006d000 - 000000000009f000 (usable) (XEN) 000000000009f000 - 00000000000a0000 (ACPI NVS) (XEN) 0000000000100000 - 000000006895f000 (usable) (XEN) 000000006895f000 - 0000000068960000 (ACPI data) (XEN) 0000000068960000 - 000000006a15f000 (usable) (XEN) 000000006a15f000 - 000000006a164000 (reserved) (XEN) 000000006a164000 - 000000006a641000 (usable) (XEN) 000000006a641000 - 000000006a645000 (ACPI data) (XEN) 000000006a645000 - 000000006a647000 (usable) (XEN) 000000006a647000 - 000000006a648000 (ACPI data) (XEN) 000000006a648000 - 000000006a662000 (usable) (XEN) 000000006a662000 - 000000006a66a000 (ACPI data) (XEN) 000000006a66a000 - 000000006a672000 (usable) (XEN) 000000006a672000 - 000000006a674000 (ACPI data) (XEN) 000000006a674000 - 000000006a675000 (usable) (XEN) 000000006a675000 - 000000006a679000 (ACPI data) (XEN) 000000006a679000 - 000000006a81c000 (usable) (XEN) 000000006a81c000 - 000000006a821000 (ACPI data) (XEN) 000000006a821000 - 000000006a822000 (reserved) (XEN) 000000006a822000 - 000000006a999000 (usable) (XEN) 000000006a999000 - 000000006a99a000 (reserved) (XEN) 000000006a99a000 - 000000006a99c000 (ACPI data) (XEN) 000000006a99c000 - 000000006b1f9000 (usable) (XEN) 000000006b1f9000 - 000000006b1fa000 (ACPI data) (XEN) 000000006b1fa000 - 000000006b44f000 (usable) (XEN) 000000006b44f000 - 000000006b450000 (ACPI data) (XEN) 000000006b450000 - 000000007d971000 (usable) (XEN) 000000007d971000 - 000000007d97e000 (reserved) (XEN) 000000007d97e000 - 000000007e395000 (usable) (XEN) 000000007e395000 - 000000007e751000 (reserved) (XEN) 000000007e751000 - 000000007ebb4000 (ACPI NVS) (XEN) 000000007ebb4000 - 000000007ec02000 (usable) (XEN) 0000000080000000 - 0000000090000000 (reserved) (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) (XEN) 00000000ff800000 - 0000000100000000 (reserved) (XEN) 0000000100000000 - 0000000280000000 (usable) (XEN) ACPI Error (tbxfroot-0218): A valid RSDP was not found [20070126] (XEN) System RAM: 8163MB (8359232kB) (XEN) Domain heap initialised (XEN) Found and enabled local APIC! (XEN) Not enabling x2APIC: depends on iommu_supports_eim. (XEN) Using scheduler: SMP Credit Scheduler (credit) (XEN) Detected 2100.028 MHz processor. (XEN) Initing memory sharing. (XEN) xstate_init: using cntxt_size: 0x340 and states: 0x7 (XEN) I/O virtualisation disabled (XEN) Enabled directed EOI with ioapic_ack_old on! (XEN) Platform timer is 1.193MHz PIT (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) - Unrestricted Guest (XEN) - APIC Register Virtualization (XEN) - Virtual Interrupt Delivery (XEN) - Posted Interrupt Processing (XEN) HVM: ASIDs enabled. (XEN) HVM: VMX enabled (XEN) HVM: Hardware Assisted Paging (HAP) detected (XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB (XEN) Brought up 1 CPUs (XEN) *** LOADING DOMAIN 0 *** (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 64-bit, lsb, paddr 0x2000 -> 0xa65000 (XEN) PHYSICAL MEMORY ARRANGEMENT: (XEN) Dom0 alloc.: 0000000274000000->0000000275000000 (2013714 pages to be allocated) (XEN) Init. ramdisk: 000000027c1cb000->000000027ffff200 (XEN) VIRTUAL MEMORY ARRANGEMENT: (XEN) Loaded kernel: ffffffff80002000->ffffffff80a65000 (XEN) Init. ramdisk: 0000000000000000->0000000000000000 (XEN) Phys-Mach map: ffffea0000000000->ffffea0000f84238 (XEN) Start info: ffffffff80a65000->ffffffff80a654b4 (XEN) Page tables: ffffffff80a66000->ffffffff80a6f000 (XEN) Boot stack: ffffffff80a6f000->ffffffff80a70000 (XEN) TOTAL: ffffffff80000000->ffffffff80c00000 (XEN) ENTRY ADDRESS: ffffffff80002000 (XEN) Dom0 has maximum 1 VCPUs (XEN) Platform timer appears to have unexpectedly wrapped 1 times. (XEN) Scrubbing Free RAM: .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 252kB init memory.
On 26.03.14 at 16:19, <groen692@grosc.com> wrote: Anybody any idea where to start trouble shooting?
The two logs (inlined and attached) appear to be from 12.3, yet you said the more severe problem you have is on 13.1. Providing the logs thereof (up to the freeze point) would be a first step. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
Hi Jan, We have reinstalled opensuse 13.1. als software is up to date from the online repositorys. Attached the messages from the failed boot with the xen kernel. ( desktop kernel is ok en does not give these problems ) booting the xen kernel: -> Video is ok. ( opensuse 12.3 was not ok ) -> No input possible form (usb) mouse or ( usb ) keyboard ( same as opensuse 12.3 ) -> network not working. ( opensuse 12.3 was ok, opensuse 13.1 identifies the card as eno1-4, opensuse 12.3 it was eth0-3) I guess system is not really frozen, the access is not possible through any input device. I see in the logs, We have tried to add pci=biosirq, but it does not help. 2014-03-27T11:48:52.234442+01:00 hostname1 kernel: [ 5.675955] i801_smbus 0000:00:1f.3: enabling device (0140 -> 0143) 2014-03-27T11:48:52.234463+01:00 hostname1 kernel: [ 5.675964] i801_smbus 0000:00:1f.3: can't find IRQ for PCI INT C; please try using pci=biosirq 2014-03-27T11:48:52.234464+01:00 hostname1 kernel: [ 5.675968] ACPI Exception: AE_BAD_PARAMETER, Thread 3712074880 could not acquire Mutex [0x1] (20130517/utmutex-285) 2014-03-27T11:48:52.234465+01:00 hostname1 kernel: [ 5.675989] Failed to obtain physical IRQ 0 mfg, Jeroen Jan Beulich schreef op 26-3-2014 17:31:
On 26.03.14 at 16:19, <groen692@grosc.com> wrote: Anybody any idea where to start trouble shooting? The two logs (inlined and attached) appear to be from 12.3, yet you said the more severe problem you have is on 13.1. Providing the logs thereof (up to the freeze point) would be a first step.
Jan
Hi Jan, Attached the message log from a boot with the desktop-kernel. Perhaps the difference goodcase-badcase gives some information. mfg, Jeroen Jan Beulich schreef op 26-3-2014 17:31:
On 26.03.14 at 16:19, <groen692@grosc.com> wrote: Anybody any idea where to start trouble shooting? The two logs (inlined and attached) appear to be from 12.3, yet you said the more severe problem you have is on 13.1. Providing the logs thereof (up to the freeze point) would be a first step.
Jan
participants (2)
-
Jan Beulich -
Jeroen Groenewegen van der Weyden