[coreboot] Lenovo G505s AMD Hardware Virtualization

Ivan Ivanov qmastery16 at gmail.com
Wed Nov 29 17:35:50 CET 2017

Hi awokd, are you sure that your HVM is correctly installed / has a
correct config ?
Because: you may have heard about Qubes OS - excellent OS which is based on Xen,
has the same and even stronger security than Xen in some cases, and it
is working perfectly
at Lenovo G505S laptop with coreboot installed

Please go to Qubes HCL hardware compatibility list page -
https://www.qubes-os.org/hcl/ ,
and look at G505S report for Qubes R3.2 version - both HVM and IOMMU
and even SLAT :
all these hardware virtualization functions are working perfectly.

also please read this message:
it contains a link to a forum post with attachments, not just .config
but also the coreboot G505S binaries
which have been tested with Qubes OS
(yes they have been done almost 1 year ago, outdated, but they contain
some nice extra stuff)

about 0 bytes cpu_microcode_blob.bin - if you look at the memory map
of 1 year old coreboot G505S build,
(provided below), there is no microcode. My guess is that no microcode
is needed for A10-5750M APU,
it is Richland architecture which is pretty refined, not even sure if
the microcode updates exist for this one -
please tell me if I'm wrong here

Performing operation on 'COREBOOT' region...
Name                           Offset     Type         Size
cbfs master header             0x0        cbfs header  32
apu/amdfw                      0x80       raw          4096
fallback/romstage              0x10c0     stage        300588
fallback/ramstage              0x4a780    stage        111690
config                         0x65c40    raw          478
revision                       0x65e80    raw          575
cmos_layout.bin                0x66100    cmos_layout  1392
pci1002,990b.rom               0x666c0    optionrom    61952
fallback/dsdt.aml              0x75940    raw          9004
img/coreinfo                   0x77cc0    payload      101048
img/nvramcui                   0x907c0    payload      140636
fallback/payload               0xb2d80    payload      62953
payload_config                 0xc23c0    raw          1543
payload_revision               0xc2a00    raw          238
img/tint                       0xc2b40    payload      93928
img/memtest                    0xd9a80    payload      180268
img/filo.lzma                  0x105b00   payload      110829
floppyimg/kolibri.lzma         0x120c40   raw          1254336
(1474560 after LZMA decompression)
(empty)                        0x253080   null         1755288
bootblock                      0x3ff940   bootblock    1408

2017-11-28 15:48 GMT+03:00 awokd <awokd at elude.in>:
> Have been struggling for the past couple months to get Xen hardware
> virtualization working on this Corebooted laptop. Paravirtualized VMs
> work, but whenever I start a fully virtualized VM (HVM) it hard freezes
> the entire system- no keyboard or mouse response. No related output is
> showing in any logs, maybe because it's freezing too fast.
> I'm not entirely sure if this is a Coreboot or Xen issue so I'm trying to
> rule out Coreboot. Would anyone on the list be able to provide a known
> good G505s Coreboot .config that is working with fully hardware
> virtualized VMs, preferably under Xen 4.8.2 or another recent version? KVM
> or ESXi might be OK too; should also let me narrow down the problem
> domain.
> One odd thing found from boot logs is:
> [    6.744165] microcode: CPU0: patch_level=0x00000000
> [    6.744205] microcode: CPU1: patch_level=0x00000000
> [    6.744220] microcode: CPU2: patch_level=0x00000000
> [    6.744227] microcode: CPU3: patch_level=0x00000000
> [    6.744290] microcode: Microcode Update Driver: v2.01
> and the cpu_microcode_blob is 0 bytes even though I set the menuconfig
> options:
> Name                           Offset     Type           Size   Comp
> cbfs master header             0x0        cbfs header        32 none
> cpu_microcode_blob.bin         0x80       microcode           0 none
> fallback/ramstage              0x100      stage          129898 none
> payload_revision               0x1fcc0    raw               239 none
> (empty)                        0x1fe00    null              152 none
> apu/amdfw                      0x1fec0    raw            131072 none
> fallback/romstage              0x3ff00    stage          320844 none
> config                         0x8e4c0    raw               528 none
> revision                       0x8e740    raw               568 none
> cmos_layout.bin                0x8e9c0    cmos_layout      1164 none
> pci1002,990b.rom               0x8eec0    optionrom       61952 none
> fallback/postcar               0x9e140    stage           13268 none
> fallback/dsdt.aml              0xa1580    raw              9435 none
> img/coreinfo                   0xa3ac0    payload        102264 none
> img/nvramcui                   0xbca80    payload        141596 none
> fallback/payload               0xdf400    payload         63860 none
> payload_config                 0xeedc0    raw              1563 none
> img/memtest                    0xef440    payload        180268 none
> (empty)                        0x11b4c0   null          2968024 none
> s3nv                           0x3efec0   raw             32768 none
> (empty)                        0x3f7f00   null            31192 none
> bootblock                      0x3ff900   bootblock        1424 none
> Is that normal for an A10-5750M APU? This is the first machine I've
> attempted to Coreboot so maybe I'm missing something obvious.
> --
> coreboot mailing list: coreboot at coreboot.org
> https://mail.coreboot.org/mailman/listinfo/coreboot

More information about the coreboot mailing list