Bug 329709

Created attachment 175676 [details]
The var log directory created after a reboot with the non xen aware kernel

Please attach hwinfo, your xen entry from grub and if possible the output from a serial cable during the xen boot using the debug xen kernel.  tia

Are you possibly just not seeing the lower half of the screen? I.e., can you do keyboard input at that point?

I believe I am having the same problem and Jan I think your comment is correct.

When booting into runlevel 5 I come to a black screen and a little clock for a mouse cursor.  I don't think too much is happening with the system at this point, but I can't change to another console to see what is happening.

I rebooted into runlevel 3 and it looked like the system was hung on starting ssh.  However, when I switched to another console I could see that the system was up and running (however libvirtd start looked like it was hanging).  Your guess seemed to be correct that on the main console I was only seeing the top portion of the screen, and I was unable to see the actual login prompt much further down the screen.  Once I hit return a couple of times I could then see the prompt start to scroll up to the viewable portion of the display.

I have attached my hwinfo output, the ps list at the time of the issue,  I also attached the var/log output.

Thanks, Chris



###Don't change this comment - YaST2 identifier: Original name: xen###
title XEN -- openSUSE 10.3 - 2.6.22.5-31
    root (hd0,0)
    kernel /xen.gz
    module /vmlinuz-2.6.22.5-31-xen root=/dev/disk/by-id/scsi-SATA_Maxtor_6V250F0_V50BH8LG-part2 vga=0x31a resume=/dev/sda3 splash=silent showopts
    module /initrd-2.6.22.5-31-xen

Created attachment 176860 [details]
hwinfo,process list, /var/log

This is the requested output for my system, not the original system the bug was reported for.

I should also add that I tried installing the x86 opensuse and didn't have the same problem.  It looks like it might be specific to the x86_64 install.

Thanks, Chris

I agree only partially. The X startup problem you're talking about is likely a different issue, at least if my suspicion (#3) is right (i.e. the behavior you [Chris] are observing when booting into run level 3, which then is a duplicate of bug 164378). I therefore still need an answer to #3 from the originator.

Hi Jan,

It sounds like bug 164378 will address the console based font problem (however when I try to view the status of the bug I get access denied).

I'll look at separate bugs for the X11/KDE problem and the libvirtd hang.

Thanks for the help

Same thing happens to me.  After hanging for 10-15 seconds at the "Loading CPUFreq modules (CPUFreq not supported)" line I get a hard reset.  The BIOS POST reports "Hypertransport sync flood error occured during last boot."

One thing in common that I see based on the hwinfo.txt that was submitted is that I am also running an MSI motherboard with Nvidia chipset.  In my case it is a Nvidia 500 Ultra vs. 570 ultra.  I am NOT running x86_64.  Is this a possible motherboard driver or BIOS issue?

based on comments #4 and #8

Created attachment 180915 [details]
Belated hwinfo of the system

I've even did BIOS updates and all openSuSE updates. I never got this system to run Xen on openSuSE 10.3. Eventhough openSuSE 10.2 worked like a breeze. 

Today i installed openSuSE 11.0 Alpha1 on this system it started up without any problems, on the Xen kernel.