SeaBIOS

seabios@seabios.org

4 participants
3800 discussions

Re: [SeaBIOS] vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios
by 汤福 28 Aug '18

28 Aug '18

Excuse me, is there some case of successful attempts on Windows 10? Could you provide me some technical docs? Thanks! > -----原始邮件----- > 发件人: "Marc-André Lureau" <marcandre.lureau(a)gmail.com> > 发送时间: 2018-08-23 16:37:36 (星期四) > 收件人: tangfu(a)gohighsec.com > 抄送: "Kevin O'Connor" <kevin(a)koconnor.net>, seabios(a)seabios.org > 主题: Re: [SeaBIOS] vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios > > Hi > > On Thu, Aug 23, 2018 at 9:29 AM 汤福 <tangfu(a)gohighsec.com> wrote: > > > > Hi， > > I am sorry, I bothered you. Still vTPM 2.0 for win 10 problem， I downloaded the latest qemu source from git, the version is V3.0.50. I think this is the latest code of qemu upstream. I also downloaded seabios upstream and bulid it with tpm2 support. Unfortunately, I tried both passthrough and emulator, and I didn’t get the expected results. > > > > For emulator， I did it like this： > > #mkdir /tmp/mytpm2/ > > #chown tss:root /tmp/mytpm2 > > #swtpm_setup --tpmstate /tmp/mytpm2 --create-ek-cert --create-platform-cert --allow-signing --tpm2 > > #swtpm socket --tpmstate dir=/tmp/mytpm2 --ctrl type=unixio,path=/tmp/mytpm2/swtpm-sock --log level=20 --tpm2 > > > > No errors occurred, suggesting that the certificate was also generated successfully.Then I created a blank img file named win10.img，and install win10 virtual machine as follows： > > #qemu-system-x86_64 -display sdl -enable-kvm -cdrom win10.iso -serial stdio -m 2048 -boot d -bios bios.bin -boot menu=on -chardev socket,id=chrtpm,path=/tmp/mytpm2/swtpm-sock -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-crb,tpmdev=tpm0 win10-ovmf.img > > Enter the system when the system is successfully installed，I found that the TPM 2.0 device was not found in the System Device Manager. If I replace -device tpm-crb with -device tpm-tis and reboot the system，The TPM device can be found in the device manager.But the vTPM 2.0 is recognized as vTPM 1.2. > > > > I also tried passthrough mode， The result is the same as emulator. So, what could be the problem? > > > > Try with OVMF. According to some technical docs, it seems Windows > requires UEFI & CRB for TPM 2. That's also what testing suggestsTry. > We are able to pass most WLK TPM tests with this setup. > > > > > > > > -----原始邮件----- > > > 发件人: "Kevin O'Connor" <kevin(a)koconnor.net> > > > 发送时间: 2018-08-21 12:08:59 (星期二) > > > 收件人: "汤福" <tangfu(a)gohighsec.com> > > > 抄送: seabios(a)seabios.org > > > 主题: Re: [SeaBIOS] vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios > > > > > > On Mon, Aug 13, 2018 at 04:45:43PM +0800, 汤福 wrote: > > > > Hi, > > > > > > > > I want to use the vTPM in a qemu Windows image. Unfortunately, it didn't work. > > > > First, the equipment: > > > > TPM 2.0 hardware > > > > CentOS 7.2 > > > > Qemu v2.10.2 > > > > SeaBIOS 1.11.0 > > > > libtpm and so on > > > > > > If you retry with the latest SeaBIOS code from the master branch, does > > > the problem still exist? > > > > > > See: > > > https://mail.coreboot.org/pipermail/seabios/2018-August/012384.html > > > > > > -Kevin > > _______________________________________________ > > SeaBIOS mailing list > > SeaBIOS(a)seabios.org > > https://mail.coreboot.org/mailman/listinfo/seabios > > > > -- > Marc-André Lureau

1 0

[RFC v2 0/3] Support multiple pci domains in pci_device
by Zihan Yang 27 Aug '18

27 Aug '18

Currently seabios assumes there is only one pci domain(0), and almost everything operates on pci domain 0 by default. This patch aims to add multiple pci domain support for pci_device, while reserve the original API for compatibility. The reason to get seabios involved is that the pxb-pcie host bus created in QEMU is now in a different PCI domain, and its bus number would start from 0 instead of bus_nr. Actually bus_nr should not be used when in another non-zero domain. However, QEMU only binds port 0xcf8 and 0xcfc to bus pcie.0. To avoid bus confliction, we should use other port pairs for busses under new domains. Current issues: * when trying to read config space of pcie_pci_bridge, it actually reads out the result of mch. I'm working on this weird behavior. Changelog: v2 <- v1: - Fix bugs in filtering domains when traversing pci devices - Reformat some hardcoded codes, such as probing the pci device in pci_setup Zihan Yang (3): fw/pciinit: Recognize pxb-pcie-dev device pci_device: Add pci domain support pci: filter undesired domain when traversing pci src/fw/coreboot.c | 2 +- src/fw/csm.c | 2 +- src/fw/mptable.c | 1 + src/fw/paravirt.c | 3 +- src/fw/pciinit.c | 276 ++++++++++++++++++++++++++++++--------------------- src/hw/ahci.c | 1 + src/hw/ata.c | 1 + src/hw/esp-scsi.c | 1 + src/hw/lsi-scsi.c | 1 + src/hw/megasas.c | 1 + src/hw/mpt-scsi.c | 1 + src/hw/nvme.c | 1 + src/hw/pci.c | 69 +++++++------ src/hw/pci.h | 42 +++++--- src/hw/pci_ids.h | 6 +- src/hw/pcidevice.c | 11 +- src/hw/pcidevice.h | 8 +- src/hw/pvscsi.c | 1 + src/hw/sdcard.c | 1 + src/hw/usb-ehci.c | 1 + src/hw/usb-ohci.c | 1 + src/hw/usb-uhci.c | 1 + src/hw/usb-xhci.c | 1 + src/hw/virtio-blk.c | 1 + src/hw/virtio-scsi.c | 1 + src/optionroms.c | 3 + 26 files changed, 268 insertions(+), 170 deletions(-) -- 2.7.4

3 10

[PATCH v2 0/3] pci: resource reserve capability found
by Jing Liu 25 Aug '18

25 Aug '18

This patch serial is about QEMU resource reserve capability finding in firmware. Firstly, this fixes a logic bug. When the capability is truncated, return zero instead of the truncated offset. Secondly, this modified the debug messages when the capability is not found and when the vendor ID or device Id doesn't match REDHAT special ones. Last, this enables the firmware recongizing the REDHAT PCI BRIDGE device ID, so that QEMU can also reserve PCI bridge resource capability. Change Log: v2 -> v1 * Add two patches for fixing small bugs Jing Liu (3): pci: fix the return value for truncated capability pci: clean up the debug message for pci capability found pci: recognize RH PCI legacy bridge resource reservation capability src/fw/pciinit.c | 45 ++++++++++++++++++++++++++++----------------- src/hw/pci_ids.h | 1 + 2 files changed, 29 insertions(+), 17 deletions(-) -- 1.8.3.1

6 24

Re: [SeaBIOS] Failure to detect high-capacity SD card
by Kevin O'Connor 24 Aug '18

24 Aug '18

On Fri, Aug 24, 2018 at 09:48:27AM -0400, Chris wrote: > On Fri, Aug 24, 2018 at 9:28 AM, Chris <coderight(a)gmail.com> wrote: > > So far it has worked on the first attempt every time. So it needs only > > the delay and nothing else. > > > > I still need to test with all my SD cards. Though I only have a 64GB > > Sandisk and a handful of 32GB Samsung. The question is whether or not > > the delay is dependent on the card type or if it's just the controller > > that needs to stabilize. > > OK, I tested all the cards I have and everything works. Attached is > the simplified patch. Hopefully someone can test other cards. I'm > interested to know if 128+GB and 16GB works. Thanks. If you increase SDHCI_POWER_ON_TIME instead, does that also work? -Kevin

2 1

Re: [SeaBIOS] Failure to detect high-capacity SD card
by Chris 24 Aug '18

24 Aug '18

On Fri, Aug 24, 2018 at 9:28 AM, Chris <coderight(a)gmail.com> wrote: > So far it has worked on the first attempt every time. So it needs only > the delay and nothing else. > > I still need to test with all my SD cards. Though I only have a 64GB > Sandisk and a handful of 32GB Samsung. The question is whether or not > the delay is dependent on the card type or if it's just the controller > that needs to stabilize. OK, I tested all the cards I have and everything works. Attached is the simplified patch. Hopefully someone can test other cards. I'm interested to know if 128+GB and 16GB works. Chris

1 0

Re: [SeaBIOS] Failure to detect high-capacity SD card
by Kevin O'Connor 24 Aug '18

24 Aug '18

On Fri, Aug 24, 2018 at 09:01:03AM -0400, Chris wrote: > I know it has been months but I just had an idea that seems to fix > this issue. I still need to test for some time to make sure but so far > it is working fine. > > What I did is simply add a delay before the SD card is initialized. > The attached patch takes a brute force approach and will attempt to > initialize multiple times. However, so far it has never had to attempt > the initialize more than once. > > That little "msleep(5)" before setting up the card seems to be all > that is needed. Like I said though, still testing but looking good. Interesting. Can you test if it is the msleep() that is needed, or if it is the second initialization that is needed? (Or both?) Thanks, -Kevin

2 1

Re: [SeaBIOS] Failure to detect high-capacity SD card
by Chris 24 Aug '18

24 Aug '18

I know it has been months but I just had an idea that seems to fix this issue. I still need to test for some time to make sure but so far it is working fine. What I did is simply add a delay before the SD card is initialized. The attached patch takes a brute force approach and will attempt to initialize multiple times. However, so far it has never had to attempt the initialize more than once. That little "msleep(5)" before setting up the card seems to be all that is needed. Like I said though, still testing but looking good. Chris

1 0

Re: [SeaBIOS] [SEABIOS] [PATCH 1/1] nvme: fix I/O queue length calculation overflow
by Kevin O'Connor 23 Aug '18

23 Aug '18

On Tue, Aug 21, 2018 at 10:21:56AM -0500, Matt DeVillier wrote: > From 2741d96d07855c3bc904d6ce47c82391039bca87 Mon Sep 17 00:00:00 2001 > From: Matt DeVillier <matt.devillier(a)puri.sm> > Date: Tues, 21 Aug 2018 10:00:53 -0500 > Subject: [PATCH v2 1/1] nvme: fix I/O queue length calculation overflow > > Commit cd47172 changed the I/O queue length calculation to use the > Maximum Queue Entries Supported (MQES) value from the capabilities > register, plus one, with a maximum value of NVME_PAGE_SIZE. > > An unintended effect from this is that due to length being an unsigned > 16-bit int, a MQES value of 0xFFFF yields a length of zero, resulting > in the queue allocation failing. Fix this by changing length to a u32. Thanks. I committed this change. -Kevin

1 0

Re: [SeaBIOS] vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios
by 汤福 23 Aug '18

23 Aug '18

Excuse me, is there some case of successful attempts on Windows 10? Or just some technical knowledge has not really test? Could you provide me some technical docs? Thanks! > -----原始邮件----- > 发件人: "Marc-André Lureau" <marcandre.lureau(a)gmail.com> > 发送时间: 2018-08-23 16:37:36 (星期四) > 收件人: tangfu(a)gohighsec.com > 抄送: "Kevin O'Connor" <kevin(a)koconnor.net>, seabios(a)seabios.org > 主题: Re: [SeaBIOS] vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios > > Hi > > On Thu, Aug 23, 2018 at 9:29 AM 汤福 <tangfu(a)gohighsec.com> wrote: > > > > Hi， > > I am sorry, I bothered you. Still vTPM 2.0 for win 10 problem， I downloaded the latest qemu source from git, the version is V3.0.50. I think this is the latest code of qemu upstream. I also downloaded seabios upstream and bulid it with tpm2 support. Unfortunately, I tried both passthrough and emulator, and I didn’t get the expected results. > > > > For emulator， I did it like this： > > #mkdir /tmp/mytpm2/ > > #chown tss:root /tmp/mytpm2 > > #swtpm_setup --tpmstate /tmp/mytpm2 --create-ek-cert --create-platform-cert --allow-signing --tpm2 > > #swtpm socket --tpmstate dir=/tmp/mytpm2 --ctrl type=unixio,path=/tmp/mytpm2/swtpm-sock --log level=20 --tpm2 > > > > No errors occurred, suggesting that the certificate was also generated successfully.Then I created a blank img file named win10.img，and install win10 virtual machine as follows： > > #qemu-system-x86_64 -display sdl -enable-kvm -cdrom win10.iso -serial stdio -m 2048 -boot d -bios bios.bin -boot menu=on -chardev socket,id=chrtpm,path=/tmp/mytpm2/swtpm-sock -tpmdev emulator,id=tpm0,chardev=chrtpm -device tpm-crb,tpmdev=tpm0 win10-ovmf.img > > Enter the system when the system is successfully installed，I found that the TPM 2.0 device was not found in the System Device Manager. If I replace -device tpm-crb with -device tpm-tis and reboot the system，The TPM device can be found in the device manager.But the vTPM 2.0 is recognized as vTPM 1.2. > > > > I also tried passthrough mode， The result is the same as emulator. So, what could be the problem? > > > > Try with OVMF. According to some technical docs, it seems Windows > requires UEFI & CRB for TPM 2. That's also what testing suggestsTry. > We are able to pass most WLK TPM tests with this setup. > > > > > > > > -----原始邮件----- > > > 发件人: "Kevin O'Connor" <kevin(a)koconnor.net> > > > 发送时间: 2018-08-21 12:08:59 (星期二) > > > 收件人: "汤福" <tangfu(a)gohighsec.com> > > > 抄送: seabios(a)seabios.org > > > 主题: Re: [SeaBIOS] vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios > > > > > > On Mon, Aug 13, 2018 at 04:45:43PM +0800, 汤福 wrote: > > > > Hi, > > > > > > > > I want to use the vTPM in a qemu Windows image. Unfortunately, it didn't work. > > > > First, the equipment: > > > > TPM 2.0 hardware > > > > CentOS 7.2 > > > > Qemu v2.10.2 > > > > SeaBIOS 1.11.0 > > > > libtpm and so on > > > > > > If you retry with the latest SeaBIOS code from the master branch, does > > > the problem still exist? > > > > > > See: > > > https://mail.coreboot.org/pipermail/seabios/2018-August/012384.html > > > > > > -Kevin > > _______________________________________________ > > SeaBIOS mailing list > > SeaBIOS(a)seabios.org > > https://mail.coreboot.org/mailman/listinfo/seabios > > > > -- > Marc-André Lureau

1 0

vTPM 2.0 is recognized as vTPM 1.2 on the Win 10 virtual machine with seabios
by 汤福 23 Aug '18

23 Aug '18

Hi, I want to use the vTPM in a qemu Windows image. Unfortunately, it didn't work. First, the equipment: TPM 2.0 hardware CentOS 7.2 Qemu v2.10.2 SeaBIOS 1.11.0 libtpm and so on My host is centos 7.2 with the TPM 2.0 hardware and qemu v2.10.2. I make the libtpm and seabios with ./configure, make and so on. I checked seabios with make menuconfig the TPM setting. It is enabled tpm by default. Eventually, all works without errors. I start the Widnows 10 image with: qemu-system-x86_64 -display sdl -enable-kvm -m 2048 -boot d -bios bios.bin -boot menu=on -tpmdev cuse-tpm,id=tpm0,cancel-path=/dev/null,type=passthrough,path=/dev/tpm0 -device tpm-tis,tpmdev=tpm0 win10.img First it looks all fine. Windows 10 booted up but the vTPM was recognized as TPM 1.2 instead of TPM 2.0 in device manager. I open the tpm Manager with tpm.msc but get error with No compatible TPM found. If I use vTPM in a qemu linux image, everything gose well. So, what could be the problem? Thanks

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

SeaBIOS