Hello All! I have a new OpenSuse 12.2 (with 3.4.33-2.24-xen kernel) + Xen 4.1.3 install on an IBM x3550 server. The system is booted via EFI with Grub2 bootloader and it boots up normally, either with or without Xen. But i have one trouble with it: I can''t get console access working with Xen. The strange thing is, despite the "WARNING: no console will be available to OS" appearing during xen loading, the console actually starts, the graphical login screen does even appear... and then freezes. Just the console; the system iself continues to run normally. Booting the system up without xen leaves also the console working. Yet i do need this console: after some testing i have to implement this new Suse/Xen install on a distant server (which has a management module for remote console access) and I just can''t risk being blinded and cut off in case there will be some confusion with network interfaces, for example. Some googling on this matter didn''t give any help also. It did reveal some opinions, though, suggesting that this console problem is related to EFI.. but, unfortunately, nothing useful. Can anyone please tell me if/how it''s possible to get console access with Xen 4.1.3 and EFI boot? And if not, what would be the closest solution? Xen 4.2?, Xen 4.1.2?, ELILO? With best regards, Janno
Hello All! I have a new OpenSuse 12.2 (with 3.4.33-2.24-xen kernel) + Xen 4.1.3 install on an IBM x3550 server. The system is booted via EFI with Grub2 bootloader and it boots up normally, either with or without Xen. But i have one trouble with it: I can''t get console access working with Xen. The strange thing is, despite the "WARNING: no console will be available to OS" message appearing during xen loading, the console actually starts, the graphical login screen does even appear... and then freezes. Just the console; the system iself continues to run normally. Booting the system up without xen leaves also the console working. Yet i do need this console: after some testing i have to implement this new Suse/Xen install on a distant server (which has a management module for remote console access) and I just can''t risk being blinded and cut off in case there will be some confusion with network interfaces, for example. Some googling on this matter didn''t give any help also. It did reveal some opinions, though, suggesting that this console problem is related to EFI.. but, unfortunately, nothing useful. Can anyone please tell me if/how it''s possible to get console access with Xen 4.1.3 and EFI boot? And if not, what would be the closest solution? Xen 4.2?, Xen 4.1.2?, ELILO? With best regards, Janno
Casey DeLorme
2013-Mar-19 14:52 UTC
Re: xen 4.1.3, EFI boot and "no console to OS" problem
Hello Janno, First question, do you have SSH configured and can you access via SSH? Second, have you tried switching TTY consoles after the login screen freezes? Is it possible it could just be the GUI and not the console? Hotkeys like ctrl+alt+F# will switch you to various terminal consoles which may allow you to at least gain access and try to debug locally. This may be a long shot, but what GUI are you using? Xen 4.1 had an EFI bug for me where it would not recognize all available memory, and Gnome3 (as an example) locks up with 512MB or less. If you can access the system via the alternative TTY or via SSH you may be able to check using the xm or xl toolstacks `dmesg` and searching for "System RAM". Unfortunately if that is the cause the only solution I am aware of involves modifying the source and rebuilding, which is not at all helpful if you are using packages. Hope these suggestions help with troubleshooting. ~Casey On Tue, Mar 19, 2013 at 8:22 AM, Janno Loide <janno@kernel.ee> wrote:> Hello All! > > I have a new OpenSuse 12.2 (with 3.4.33-2.24-xen kernel) + Xen 4.1.3 > install on an IBM x3550 server. The system is booted via EFI with Grub2 > bootloader and it boots up normally, either with or without Xen. > But i have one trouble with it: I can''t get console access working with > Xen. > > The strange thing is, despite the "WARNING: no console will be available > to OS" appearing during xen loading, the console actually starts, the > graphical login screen does even appear... and then freezes. Just the > console; the system iself continues to run normally. > Booting the system up without xen leaves also the console working. > > Yet i do need this console: after some testing i have to implement this > new Suse/Xen install on a distant server (which has a management module for > remote console access) and I just can''t risk being blinded and cut off in > case there will be some confusion with network interfaces, for example. > > Some googling on this matter didn''t give any help also. It did reveal some > opinions, though, suggesting that this console problem is related to EFI.. > but, unfortunately, nothing useful. > > > Can anyone please tell me if/how it''s possible to get console access with > Xen 4.1.3 and EFI boot? And if not, what would be the closest solution? Xen > 4.2?, Xen 4.1.2?, ELILO? > > > With best regards, > Janno > > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Casey DeLorme
2013-Mar-19 19:52 UTC
Re: xen 4.1.3, EFI boot and "no console to OS" problem
Good news is if Xen recognizes all your memory the patch I mentioned is unrelated and I can think of no reason to modify the source. However that brings us back to the console not accepting input. --- Based on what you''ve said, the KDM login is not frozen (cursor is actively blinking?), but the input is not in the right place somehow. If I am understanding this right, the Java applet sits between the real VGA output and the Matrox adapter, as a layer? If so maybe some connection is belong list in transit when Xen hands VGA over to the Dom0. From the tail you posted the only line not in my xl dmesg is this one: (XEN) physdev.c:172: dom0: wrong map_pirq type 3 Google only has a series of unrelated links, a wide range of Dom0''s and generally paravirtualization questions, so possibly an unrelated error. --- Here are some questions and tests you can try: Does your VNC connection take you strait to the same KDM login or a new one? If it is the same one can you watch it change from the matrox adapter while using it? Can you kill the KDM instance from SSH? Does it return you to terminal, and does the keyboard work after? Can you unplug and reconnect the USB keyboard, and when you do what does `tail /var/log/messages` contain? Does the VNC run through the Java applet as well? Finally, is there any configuration options for the Java applet? Because if it is a layer then I am guessing something is happening at that stage of the system. The only other thoughts I have at the moment are whether the grub.cfg contains any special configuration settings that are different than the Xen version or that might be related to the Java applet. On Tue, Mar 19, 2013 at 2:07 PM, Janno Loide <janno@kodu.ee> wrote:> Hi Casey, > > Fortunately, yes, I do have ssh access, and even vnc. So I can probably > debug it in any possible way you''ll recommend :) > > But this is just my testing configuraton, laying on a desk next to me. > Implementing that software on the remote production site is what makes me > really worried. > > I did try to switch TTYs, from the usb keyboard, without any result :( The > keyboard, connected to usb port, doesn''t even put any leds on, neither > blinks when disconnecting/connecting after loading Xen. The system does > recongize the keyboard, though: > --- > kernel: [ 4.510357] input: Lite-On Technology Corp. Lenovo Low Profile > USB Keyboard as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input1 > ... > kernel: [ 4.517658] usbcore: registered new interface driver usbhid > Mar 19 17:54:58 linux-z01z kernel: [ 4.517659] usbhid: USB HID core > driver > --- > > The system has a remote management module with java-based remote console > applet and that behaves exactly the same as the real console: Kdm login > screen appears, the cursor blinks, but typing on a keyboard has no effect. > > > The graphics adapter is Matrox G200e2 with 16MB RAM. > Before Xen loading the console input works normally, btw. On the GRUB menu > I can choose between entries. And when I boot up with either default or > desktop profiled kernel the console stays on, fully functional. Just when I > choose Xen kernel, the input disappears (the usb keyboard stops responding > to NumLock) just after the ramdisk is loaded and screen blanks for a moment. > > > Xen seems to recognize the right amount of RAM, though: > #xm dmesg | grep -i ''system ram'' > (XEN) System RAM: 98237MB (100595124kB) > > Some other thing I noticed -- ''xm dmesg'' output ends with: > --- > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input > to Xen) > (XEN) Freed 232kB init memory. > (XEN) physdev.c:172: dom0: wrong map_pirq type 3 > --- > > And exept host console, everything else seems to work. I can even install > and run guest vm-s without problems (though tested HVM and PVHVM guests so > far). > > I do prefer standardized solutions of course, but modifying source and > recompiling things is ok also, if only this would help. > > > Janno > > > Hello Janno, > > First question, do you have SSH configured and can you access via SSH? > > Second, have you tried switching TTY consoles after the login screen > freezes? Is it possible it could just be the GUI and not the console? > Hotkeys like ctrl+alt+F# will switch you to various terminal consoles > which may allow you to at least gain access and try to debug locally. > > This may be a long shot, but what GUI are you using? Xen 4.1 had an EFI > bug for me where it would not recognize all available memory, and Gnome3 > (as an example) locks up with 512MB or less. > > If you can access the system via the alternative TTY or via SSH you may > be able to check using the xm or xl toolstacks `dmesg` and searching for > "System RAM". > > Unfortunately if that is the cause the only solution I am aware of > involves modifying the source and rebuilding, which is not at all helpful > if you are using packages. > > Hope these suggestions help with troubleshooting. > > ~Casey > > > On Tue, Mar 19, 2013 at 8:22 AM, Janno Loide <janno@kernel.ee> wrote: > >> Hello All! >> >> I have a new OpenSuse 12.2 (with 3.4.33-2.24-xen kernel) + Xen 4.1.3 >> install on an IBM x3550 server. The system is booted via EFI with Grub2 >> bootloader and it boots up normally, either with or without Xen. >> But i have one trouble with it: I can''t get console access working with >> Xen. >> >> The strange thing is, despite the "WARNING: no console will be available >> to OS" appearing during xen loading, the console actually starts, the >> graphical login screen does even appear... and then freezes. Just the >> console; the system iself continues to run normally. >> Booting the system up without xen leaves also the console working. >> >> Yet i do need this console: after some testing i have to implement this >> new Suse/Xen install on a distant server (which has a management module for >> remote console access) and I just can''t risk being blinded and cut off in >> case there will be some confusion with network interfaces, for example. >> >> Some googling on this matter didn''t give any help also. It did reveal >> some opinions, though, suggesting that this console problem is related to >> EFI.. but, unfortunately, nothing useful. >> >> >> Can anyone please tell me if/how it''s possible to get console access with >> Xen 4.1.3 and EFI boot? And if not, what would be the closest solution? Xen >> 4.2?, Xen 4.1.2?, ELILO? >> >> >> With best regards, >> Janno >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xen.org >> http://lists.xen.org/xen-users >> > > > > _______________________________________________ > Xen-users mailing listXen-users@lists.xen.orghttp://lists.xen.org/xen-users > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xen.org http://lists.xen.org/xen-users
Hi,> Based on what you''ve said, the KDM login is not frozen (cursor is > actively blinking?), but the input is not in the right place somehow. > > If I am understanding this right, the Java applet sits between the > real VGA output and the Matrox adapter, as a layer? If so maybe some > connection is belong list in transit when Xen hands VGA over to the Dom0.Probably. Though I guess the problem isn''t related to that applet, as the kernel without xen comes up with fully functional console. The problem is probably Xen not supporting EFI -- at least on this hardware :( Actually, I was dumb enough not to look at ''xm dmesg'' output before (thanks to Casey for bringing it up). Surprisingly, while Xen succeeds on detecting RAM, it fails reading full ACPI data structure: -- (XEN) ACPI Error (tbxfroot-0218): A valid RSDP was not found [20070126] (XEN) System RAM: 98237MB (100595124kB) (XEN) Domain heap initialised (XEN) Table is not found! (XEN) Found and enabled local APIC! -- As Xen does not detect root pointer it fails of course on everything else depending on it, including detecting the cpu: -- (XEN) Detected 2000.055 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) 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 -- Finally, it just finds one cpu instead of six hyperthreaded cores! Amazing. Compared to that, my trouble with console is just nothing. The console problem is very likely caused by this acpi detection failure also. Tried Opensuse 12.3 with Xen 4.2.1 this morning. Got the same result (the dmesg output above is actually from Xen 4.2.1 also). The OS 12.3 kernel (3.7.10-1.1) without xen continues to detect ACPI data correctly (as 3.4.33-2.24 on 12.2 did), giving no errors, finding all cores etc... I''ll probably re-check the IBM firmware updates and then submit a bug report. Regards, Janno
Janno Loide
2013-Mar-20 22:33 UTC
Re: SOLVED: xen 4.1.3, EFI boot and "no console to OS" problem
Just to conclude this topic: Xen 4.1.3 with OpenSUSE 12.2 (and 4.2.1 with OS12.3 also) works well with UEFI on IBM x35*0 hardware. The machine has to be booted with xen.efi loader, any other loader before xen won''t do, probably. I just had to - create an additional directory on efi partition; - copy xen.efi into that directory; - copy initrd and vmlinuz kernel images into that directory; - create simple xen.cfg file in the same directory containing just a few lines -- for example: options=dom0_mem=2048M,max:2048M dom0_max_vcpus=1 dom0_vcpus_pin loglvl=all noreboot kernel=vmlinuz-3.7.10-1.1-xen ignore_loglevel #earlyprintk=xen ramdisk=initrd-3.7.10-1.1-xen root=/dev/disk/by-id/scsi-3500a07510364d950-part3 - create additional boot entry in system firmware pointing to the xen.efi. And voilĂ -- everything works like a charm :) RAM and cores are counted correctly, console acts normally, vm-s run as expected. Concerning my initial question about that strange "no console will be available to OS" message I suspected to be some meaningful indication to my problem -- I''m not sure if it''s related to any problem at all. I can''t notice it on boot anymore. Though I''m still wondering what it actually means... With best regards, Janno> Hi, > >> Based on what you''ve said, the KDM login is not frozen (cursor is >> actively blinking?), but the input is not in the right place somehow. >> >> If I am understanding this right, the Java applet sits between the >> real VGA output and the Matrox adapter, as a layer? If so maybe some >> connection is belong list in transit when Xen hands VGA over to the >> Dom0. > Probably. Though I guess the problem isn''t related to that applet, as > the kernel without xen comes up with fully functional console. > > The problem is probably Xen not supporting EFI -- at least on this > hardware :( > Actually, I was dumb enough not to look at ''xm dmesg'' output before > (thanks to Casey for bringing it up). Surprisingly, while Xen succeeds > on detecting RAM, it fails reading full ACPI data structure: > -- > (XEN) ACPI Error (tbxfroot-0218): A valid RSDP was not found [20070126] > (XEN) System RAM: 98237MB (100595124kB) > (XEN) Domain heap initialised > (XEN) Table is not found! > (XEN) Found and enabled local APIC! > -- > > As Xen does not detect root pointer it fails of course on everything > else depending on it, including detecting the cpu: > -- > (XEN) Detected 2000.055 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) 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 > -- > Finally, it just finds one cpu instead of six hyperthreaded cores! > Amazing. > Compared to that, my trouble with console is just nothing. > The console problem is very likely caused by this acpi detection > failure also. > > > Tried Opensuse 12.3 with Xen 4.2.1 this morning. Got the same result > (the dmesg output above is actually from Xen 4.2.1 also). > > The OS 12.3 kernel (3.7.10-1.1) without xen continues to detect ACPI > data correctly (as 3.4.33-2.24 on 12.2 did), giving no errors, finding > all cores etc... > > > I''ll probably re-check the IBM firmware updates and then submit a bug > report. > > > Regards, > Janno > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
All, I''m currently working on an issue where I need to build Xen in areas where I may not have any networking at all. I have searched the Internet for possible remedies, but, so far, have not come up with any good solutions. My goal is to take a build of Xen 4.2.1, put it on a server (Intel or AMD) that already has the Xen 4.2.1 required packages installed, and be able to build (make world) and install (make install) without having to access any git repositories. Any ideas on how best to solve this issue? Kind regards, Todd Wardzinski