SeaBIOS

seabios@seabios.org

4 participants
3801 discussions

allocation zone extensions for the firmware linker/loader
by Laszlo Ersek 12 Jun '17

12 Jun '17

Hi, this message is cross-posted to three lists (qemu, seabios, edk2). I'll follow up with three patch series, one series for each project. I'll cross-post all of the patches as well, but I'll add the project name in the "bag of tags" in the subject lines. The QEMU series introduces two extensions to the ALLOCATE firmware linker/loader command. One extension is a new allocation zone, with value 3, for allowing the firmware to allocate the fw_cfg blobs in 64-bit address space. The other extension is a repurposing of the most significant bit (bit 7) in the zone field. This bit becomes orthogonal to the rest of the zone field. If the bit is set, it means that QEMU promises the firmware that the blob referenced by the ALLOCATE command contains no ACPI tables at all. After introducing these, the QEMU series puts them to use, covering all of the currently generated ALLOCATE commands, as appropriate. Among the benefits we can mention - the removal of the OVMF ACPI SDT Header Probe suppressor from VMGENID (and from any similar future devices), - and the fact that the "virt" machine type (and maybe other machine types) of the arm/aarch64 target will no longer require RAM under 4GB for ACPI to work. Both of these extensions are irrelevant for SeaBIOS, therefore the SeaBIOS patches simply mask out bit 7 (for ignoring the "no ACPI content" hint), and fall back to the HIGH zone (= 32-bit address space) when the 64-bit zone is permitted. In other words, SeaBIOS needs some patches to recognize the new zone values, but beyond that, the behavior is unchanged. Both extensions are important for virtual UEFI firmware (OVMF in x86 guests and ArmVirtQemu in aarch64 guests). The edk2 patches add support to OvmfPkg/AcpiPlatformDxe for the extensions. Please see the commit messages for details (all the extensions are explained in detail in the relevant patches for all of the projects). The patches can cause linker/loader breakage when old firmware is booted on new QEMU. However, that's no problem (it's nothing new), the next release of QEMU should bundle the new firmware binaries as always. New firmware will continue running on old QEMU without issues. (In case you have sent me emails about this in the last few tens of hours, please know that I'm not ignoring them, I just haven't seen / read them. Reading emails every five minutes makes focused work impossible, so when I'm busy, I tend to read email once per day.) Thanks Laszlo

6 26

[PATCH] boot: boot menu up to 35 devices with letters and possible pages
by Ivan Ivanov 10 Jun '17

10 Jun '17

Extend boot menu: make it possible to select the boot menu entries with ID larger than 10 by pressing a corresponding letter key. If there are more than 18 devices, then a boot menu splits into two pages; you can switch between the pages by pressing the ENTER key. NOTE: now to access the TPM you need to press the M key. It makes more sense, because Trusted is adjective while Module is noun - and adds more convenience, because M letter is at the end of keyboard's 3rd row of letters, not in the middle of them Signed-off-by: Ivan Ivanov <qmastery16 at gmail.com> --- diff --git a/src/boot.c b/src/boot.c index 59623fb..fa2a0fe 100644 --- a/src/boot.c +++ b/src/boot.c @@ -447,6 +447,7 @@ get_keystroke(int msec) ****************************************************************/ #define DEFAULT_BOOTMENU_WAIT 2500 +#define DEFAULT_BOOTMENU_PAGE_SIZE 18 // Show IPL option menu. void @@ -475,20 +476,37 @@ interactive_bootmenu(void) while (get_keystroke(0) >= 0) ; - printf("Select boot device:\n\n"); + printf("Select boot device"); wait_threads(); - // Show menu items + // Show menu items after counting them and determining a number of pages + int maxmenu = 0; struct bootentry_s *pos; + hlist_for_each_entry(pos, &BootList, node) + maxmenu++; + + if (maxmenu > DEFAULT_BOOTMENU_PAGE_SIZE) + printf(" - page 1 : // press ENTER " + "to switch between the pages...\n\n"); + else + printf(":\n\n"); + + char keyboard_keys[35] = {'1','2','3','4','5','6','7','8','9','0', + 'q','w','e','r','t','y','u','i','o','p', + 'a','s','d','f','g','h','j','k','l', + 'z','x','c','v','b','n'}; /* m = TPM */ + int entry_id = 0; hlist_for_each_entry(pos, &BootList, node) { char desc[77]; - maxmenu++; - printf("%d. %s\n", maxmenu + if (entry_id == DEFAULT_BOOTMENU_PAGE_SIZE) // show only the first page + break; + printf("%c. %s\n", keyboard_keys[entry_id] , strtcpy(desc, pos->description, ARRAY_SIZE(desc))); + entry_id++; } if (tpm_can_show_menu()) { - printf("\nt. TPM Configuration\n"); + printf("\nm. TPM Configuration\n"); } // Get key press. If the menu key is ESC, do not restart boot unless @@ -496,16 +514,65 @@ interactive_bootmenu(void) // repeatedly hitting keys to enter the BIOS) will end up hitting ESC // multiple times and immediately booting the primary boot device. int esc_accepted_time = irqtimer_calc(menukey == 1 ? 1500 : 0); + int choice; + int page_number = 1; for (;;) { scan_code = get_keystroke(1000); if (scan_code == 1 && !irqtimer_check(esc_accepted_time)) continue; - if (tpm_can_show_menu() && scan_code == 20 /* t */) { + if (scan_code == 1) + break; + if (scan_code == 50 && tpm_can_show_menu()) { // 50 scan code = m = TPM printf("\n"); tpm_menu(); } - if (scan_code >= 1 && scan_code <= maxmenu+1) + /* 4 rows of keyboard_keys: 1 row with numbers, 3 rows with letters. + Use any of them to select boot device (except the M letter = TPM) */ + choice = 0; + // 1st range: 1-9 and 0 (10) keys <==> 2-11 scan codes <==> 1-10 choice + if (scan_code >= 2 && scan_code <= 11) choice = scan_code - 1; + // 2nd range: Q-P row of letters <==> 16-25 scan codes <==> 11-20 choice + if (scan_code >= 16 && scan_code <= 25) choice = scan_code - 5; + // 3rd range: A-L row of letters <==> 30-38 scan codes <==> 21-29 choice + if (scan_code >= 30 && scan_code <= 38) choice = scan_code - 9; + // 4th range: Z-N row of letters <==> 44-49 scan codes <==> 30-35 choice + if (scan_code >= 44 && scan_code <= 49) choice = scan_code - 14; + + // After you choose any of detected boot devices, lets start booting + if (choice > 0 && choice <= maxmenu) break; + + // If the ENTER key has been pressed and there are 2 pages, switch them + if (scan_code == 28 && maxmenu > DEFAULT_BOOTMENU_PAGE_SIZE) { + entry_id = 0; + page_number = 3 - page_number; // 3 - 1 = 2 ; 3 - 2 = 1 + printf("\n\nSelect boot device - page %d : // press ENTER " + "to switch between the pages...\n\n", page_number); + if (page_number == 1) { // print the 1st page + hlist_for_each_entry(pos, &BootList, node) { + char desc[77]; + if (entry_id == DEFAULT_BOOTMENU_PAGE_SIZE) + break; + printf("%c. %s\n", keyboard_keys[entry_id] + , strtcpy(desc, pos->description, ARRAY_SIZE(desc))); + entry_id++; + } + } + else { // print the 2nd page + hlist_for_each_entry(pos, &BootList, node) { + char desc[77]; + if (entry_id == 35) + break; + if (entry_id >= DEFAULT_BOOTMENU_PAGE_SIZE) + printf("%c. %s\n", keyboard_keys[entry_id] + , strtcpy(desc, pos->description, ARRAY_SIZE(desc))); + entry_id++; + } + } + if (tpm_can_show_menu()) { + printf("\nm. TPM Configuration\n"); + } + } } printf("\n"); if (scan_code == 0x01) @@ -513,7 +580,6 @@ interactive_bootmenu(void) return; // Find entry and make top priority. - int choice = scan_code - 1; hlist_for_each_entry(pos, &BootList, node) { if (! --choice) break;

1 0

[PATCH] boot: boot menu up to 35 devices with letters and possible pages
by Ivan Ivanov 10 Jun '17

10 Jun '17

1 0

CFP: KVM Forum 2017
by Paolo Bonzini 08 Jun '17

08 Jun '17

================================================================ KVM Forum 2017: Call For Participation October 25-27, 2017 - Hilton Prague - Prague, Czech Republic (All submissions must be received before midnight June 15, 2017) ================================================================= KVM Forum is an annual event that presents a rare opportunity for developers and users to meet, discuss the state of Linux virtualization technology, and plan for the challenges ahead. We invite you to lead part of the discussion by submitting a speaking proposal for KVM Forum 2017. At this highly technical conference, developers driving innovation in the KVM virtualization stack (Linux, KVM, QEMU, libvirt) can meet users who depend on KVM as part of their offerings, or to power their data centers and clouds. KVM Forum will include sessions on the state of the KVM virtualization stack, planning for the future, and many opportunities for attendees to collaborate. As we celebrate ten years of KVM development in the Linux kernel, KVM continues to be a critical part of the FOSS cloud infrastructure. This year, KVM Forum is joining Open Source Summit in Prague, Czech Republic. Selected talks from KVM Forum will be presented on Wednesday October 25 to the full audience of the Open Source Summit. Also, attendees of KVM Forum will have access to all of the talks from Open Source Summit on Wednesday. http://events.linuxfoundation.org/cfp Suggested topics: * Scaling, latency optimizations, performance tuning, real-time guests * Hardening and security * New features * Testing KVM and the Linux kernel: * Nested virtualization * Resource management (CPU, I/O, memory) and scheduling * VFIO: IOMMU, SR-IOV, virtual GPU, etc. * Networking: Open vSwitch, XDP, etc. * virtio and vhost * Architecture ports and new processor features QEMU: * Management interfaces: QOM and QMP * New devices, new boards, new architectures * Graphics, desktop virtualization and virtual GPU * New storage features * High availability, live migration and fault tolerance * Emulation and TCG * Firmware: ACPI, UEFI, coreboot, U-Boot, etc. Management and infrastructure * Managing KVM: Libvirt, OpenStack, oVirt, etc. * Storage: Ceph, Gluster, SPDK, etc.r * Network Function Virtualization: DPDK, OPNFV, OVN, etc. * Provisioning =============== SUBMITTING YOUR PROPOSAL =============== Abstracts due: June 15, 2017 Please submit a short abstract (~150 words) describing your presentation proposal. Slots vary in length up to 45 minutes. Also include the proposal type -- one of: - technical talk - end-user talk Submit your proposal here: http://events.linuxfoundation.org/cfp Please only use the categories "presentation" and "panel discussion" You will receive a notification whether or not your presentation proposal was accepted by August 10, 2017. Speakers will receive a complimentary pass for the event. In the instance that case your submission has multiple presenters, only the primary speaker for a proposal will receive a complimentary event pass. For panel discussions, all panelists will receive a complimentary event pass. TECHNICAL TALKS A good technical talk should not just report on what has happened over the last year; it should present a concrete problem and how it impacts the user and/or developer community. Whenever applicable, focus on work that needs to be done, difficulties that haven't yet been solved, and on decisions that other developers should be aware of. Summarizing recent developments is okay but it should not be more than a small portion of the overall talk. END-USER TALKS One of the big challenges as developers is to know what, where and how people actually use our software. We will reserve a few slots for end users talking about their deployment challenges and achievements. If you are using KVM in production you are encouraged submit a speaking proposal. Simply mark it as an end-user talk. As an end user, this is a unique opportunity to get your input to developers. HANDS-ON / BOF SESSIONS We will reserve some time for people to get together and discuss strategic decisions as well as other topics that are best solved within smaller groups. These sessions will be announced during the event. If you are interested in organizing such a session, please add it to the list at http://www.linux-kvm.org/page/KVM_Forum_2017_BOF Let people you think who might be interested know about your BOF, and encourage them to add their names to the wiki page as well. Please try to add your ideas to the list before KVM Forum starts. PANEL DISCUSSIONS If you are proposing a panel discussion, please make sure that you list all of your potential panelists in your the abstract. We will request full biographies if a panel is accepted. =============== HOTEL / TRAVEL =============== This year's event will take place at the Hilton Prague. For information on discounted room rates for conference attendees and on other hotels close to the conference, please visit http://events.linuxfoundation.org/events/kvm-forum/attend/hotel-travel. =============== IMPORTANT DATES =============== Submission deadline: June 15, 2017 Notification: August 10, 2017 Schedule announced: August 17, 2017 Event dates: October 25-27, 2017 Thank you for your interest in KVM. We're looking forward to your submissions and seeing you at the KVM Forum 2017 in October! -your KVM Forum 2017 Program Committee Please contact us with any questions or comments at kvm-forum-2017-pc(a)redhat.com

1 1

Unable to boot VM with scsi enabled.
by Maciej Józefczyk 07 Jun '17

07 Jun '17

Hello, my environment: - qemu: 2.5+dfsg-5ubuntu10.13~cloud0 - seabios: latest master I'm trying to boot VM with parameters: <disk type='file' device='disk'> <driver name='qemu' type='qcow2' cache='none'/> <source file='/home/instances/xxxxx-xxxx/disk'/> <target dev='sda' bus='scsi'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <controller type='scsi' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> and it fails with message (instance screen): Booting from Hard Disk... Boot failed: could not read the boot disk No bootable device. I figure out that rollback of those commits: - 3198c06b7b5457eecf5fbc6fd47fbea300a843e7 (lsi-scsi: try to enumerate luns with REPORT LUNS) - 11277846e819b9eef3db5ac833a6a47f95f5ef15 (lsi-scsi: reset in case of a serious problem) Solves the problem. What i'm doing wrong? Maybe its a bug? Thank you! Maciej -- ---- Maciej Józefczyk maciej.jozefczyk(a)corp.ovh.com

2 1

Re: [SeaBIOS] SSL certificate error - SeaBIOS git repository
by Paul Menzel 05 Jun '17

05 Jun '17

Dear qmastery, Am Sonntag, den 04.06.2017, 22:44 +0000 schrieb qma ster: > Good day! When I select "SeaBIOS version - master" at my coreboot > build settings, it tries to obtain the latest SeaBIOS from your git > repository. However I am getting the following error: > Cloning SeaBIOS from Git > Cloning into 'seabios'... > mafatal: unable to access > 'https://review.coreboot.org/p/seabios.git/': SSL certificate problem: > unable to get local issuer certificate > make[1]: *** [Makefile:19: seabios] Error 128 > make: *** [payloads/external/Makefile.inc:72: > payloads/external/SeaBIOS/seabios/out/bios.bin.elf] Error 2 > > Of course this problem will disappear if I will add > "GIT_SSL_NO_VERIFY=true" before git clone > https://review.coreboot.org/p/seabios.git/ command, but this is > incorrect and insecure solution. Please fix your SSL certificates. My > OpenSSL version is 1.1.0-f-1 and OpenSSL-1.0 version is 1.0.2.l-1 if > that matters. I am not having problems with coreboot git repository, > only with SeaBIOS repository I am unable to reproduce this with Debian Sid/unstable which ships 1.1.0f-2. ``` $ curl -I https://review.coreboot.org/p/seabios.git/ HTTP/1.1 302 Found Server: nginx/1.8.1 Date: Mon, 05 Jun 2017 09:30:58 GMT Content-Length: 0 Connection: keep-alive Location: https://review.coreboot.org/#/q/status%3Aopen+project%3Aseabios Strict-Transport-Security: max-age=31536000 X-Frame-Options: DENY $ git clone https://review.coreboot.org/p/seabios.git/ […] ``` I believe that’s a problem with your local setup. But I am out of ideas, as you say it works with the coreboot repository URL. https://review.coreboot.org/p/coreboot.git/ Thanks, Paul

1 0

SSL certificate error - SeaBIOS git repository
by qma ster 04 Jun '17

04 Jun '17

Good day! When I select "SeaBIOS version - master" at my coreboot build settings, it tries to obtain the latest SeaBIOS from your git repository. However I am getting the following error: Cloning SeaBIOS from Git Cloning into 'seabios'... mafatal: unable to access 'https://review.coreboot.org/p/seabios.git/': SSL certificate problem: unable to get local issuer certificate make[1]: *** [Makefile:19: seabios] Error 128 make: *** [payloads/external/Makefile.inc:72: payloads/external/SeaBIOS/seabios/out/bios.bin.elf] Error 2 Of course this problem will disappear if I will add "GIT_SSL_NO_VERIFY=true" before git clone https://review.coreboot.org/p/seabios.git/ command, but this is incorrect and insecure solution. Please fix your SSL certificates. My OpenSSL version is 1.1.0-f-1 and OpenSSL-1.0 version is 1.0.2.l-1 if that matters. I am not having problems with coreboot git repository, only with SeaBIOS repository Best regards qmastery

1 0

ia16 gcc port - handy for SeaBIOS?
by Rudolf Marek 16 May '17

16 May '17

Hi all, Perhaps you already noticed. There are efforts to resurrect true 16-bit only x86 GCC port [1][2]. I added it coreboot cross toolchain script. https://review.coreboot.org/#/c/19711/ You can compile it ./buildgcc -j4 -p ia16-elf So far, I only tried to compile some simple programs, but I believe it could be handy for SeaBIOS 16-bit code, which could be true 16-bit. Or, if someone ever does SeaBIOS port to xi8088 board [3] which uses 8088 or NEC v20 Thanks Rudolf [1] https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00082.html [2] https://sourceware.org/ml/binutils/2017-04/msg00012.html [3] http://www.malinov.com/Home/sergeys-projects/xi-8088

2 1

Re: [SeaBIOS] A20: ahci_process_op is called with A20 off
by Kevin O'Connor 12 May '17

12 May '17

On Thu, May 11, 2017 at 11:22:02PM +0000, Xu, Anthony wrote: > > SeaBIOS has a couple of different methods to accomplish this mode > > switching - it can directly switch modes (C16_BIG switch) or it can > > use a helper in SMM mode to perform the switch (C16_SMM). The > > preferred method is C16_SMM as C16_BIG isn't available in VM86 mode > > and it also clobbers the 16bit segment registers. > > Hi Kevin, > > Why does SeaBios use VM86 mode? As Paolo mentioned, SeaBIOS doesn't use it, but it must support callers that use it. > vtx supports real mode long time ago. > > C16_SMM is slow because it causes several extra switches between VM and QEMU. > I would prefer C16_BIG for better performance. > Does SeaBios know if it runs in real mode or VM86 mode? > Can SeaBios choose C16_SMM/C16_BIG based on VCPU mode? Yes, SeaBIOS could use the smsw instruction (see x86.h:cr0_vm86_read) to check if it is in VM86 mode. Using C16_BIG would still clobber the segment registers, but it might be worth that risk to avoid the extra overhead of C16_SMM. -Kevin

3 3

Re: [SeaBIOS] A20: ahci_process_op is called with A20 off
by Paolo Bonzini 12 May '17

12 May '17

On 12/05/2017 01:22, Xu, Anthony wrote: >> SeaBIOS has a couple of different methods to accomplish this mode >> switching - it can directly switch modes (C16_BIG switch) or it can >> use a helper in SMM mode to perform the switch (C16_SMM). The >> preferred method is C16_SMM as C16_BIG isn't available in VM86 mode >> and it also clobbers the 16bit segment registers. > > Hi Kevin, > > Why does SeaBios use VM86 mode? SeaBIOS doesn't, but for example old DOS extenders uses it. You can run Windows 95 inside SeaBIOS. Paolo > vtx supports real mode long time ago. > > C16_SMM is slow because it causes several extra switches between VM and QEMU. > I would prefer C16_BIG for better performance. > Does SeaBios know if it runs in real mode or VM86 mode? > Can SeaBios choose C16_SMM/C16_BIG based on VCPU mode? > > > Thanks, > Anthony >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS