HCL - Sony SVF15A1C5E

106 views
Skip to first unread message

r.fl...@openmailbox.org

unread,
Mar 8, 2017, 6:20:24 AM3/8/17
to qubes...@googlegroups.com
I tested if this laptop supports VT-d both with `qubes-hcl-report` and
`xl dmesg`. Furthermore BIOS supports Intel VT.
However I cannot determine what is the PCH of this laptop. I think that
it's a HM76 chipset but, from its ark page, it does not support VT-d.
How can I determine it correctly?
I also attached lspci's output.
HCL.yml
lspci.out
xl.log

r.fl...@openmailbox.org

unread,
Mar 8, 2017, 10:16:20 AM3/8/17
to qubes...@googlegroups.com
I opened the laptop. I can confirm that it's a SLJ8E BD82HM76 PCH. So
the motherboard does not support VT-d.
So how both hcl and xen confirm that this laptop supports IOMMU?

Zrubi

unread,
Mar 8, 2017, 10:45:34 AM3/8/17
to r.fl...@openmailbox.org, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/08/2017 04:14 PM, r.fl...@openmailbox.org wrote:
> I opened the laptop. I can confirm that it's a SLJ8E BD82HM76 PCH.
> So the motherboard does not support VT-d. So how both hcl and xen
> confirm that this laptop supports IOMMU?

the HCL script is pretty easy to read. You can check how it is decide
vt-d support.

it is actually relaying on xen, and parsing the output of these commands
:
xl info
xl dmesd

If you believe it is a false report, send us the support files as well
for further investigation.


- --
Zrubi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYwCcTAAoJEH7adOMCkunm+QYP+waxhkIp753P6Kf3ksqXcCwu
eBCeIz2qUH35Xfqxo5R1+vgh9KAs0zQxdGmX8E3w1gH21Bd96reLt+8zxxmk1CRn
/gqxhzeOrMr7wmGt1Tqot+FLf3r22720RGe4kauBv9r3aCwgekEBdn9Ea/CTCUu+
xCdmeYrzgu1pNYej6SGywWSgR/ZTPxMQZ8rHsteZaKU3eTgxmKal6fgIx8qhNJ8j
rgaK7bX/b86FwhT+OzzC6Gu5Qp4aSP8qqJ2i456HhYTQfGaM/9ITgZ7k+95qAwWV
0pxihvdJ5L6hXOazak4nvHEjOeb4I1UPiic1My6rZuv5BYJie5Fnvh/OkskUJlMt
eS8Glf7KUayMjFKfMzwf5y7iuQTrj7KI6MAvFnni10COBb7kqSVgnfp5sA0aSZ3u
AFepCU3Ah6o1dCEsMNQaQG0pkckYMZ94PCj1dztQXIpwkrUY7zDmIEzlQCcvT9Xm
gTkJ210QKGFfSptR/XoNsoImk+b6fiXwIY4i7FBfx3OyMoV2EZi1LbtpQKx2iSX4
aY7cLEW27GKJOIMsxG/YPGMVsLtcvhOeyNSI85RSDZ6dJxp9kac7o8UwBW2xmZp4
51UKUQhEudBcYWHbtHoCZvPk8PvsrbFkk42tQ/EoaQ3IZjLO2vdiHTFlPpoAKsM1
JTLoDUw3xJNt8EMppO/H
=63CG
-----END PGP SIGNATURE-----

r.fl...@openmailbox.org

unread,
Mar 8, 2017, 12:02:01 PM3/8/17
to qubes...@googlegroups.com
I didn't know that `qubes-hcl-report` is a bash shell script. I've just
saw how VT-d support is recognized. Probably there is a problem with `xl
info`. It prints actually that this laptop supports VT-d.
It's strange..

However I attached support files. I hope that we can resolve this
'mistery'.
Qubes-HCL-Sony_Corporation-SVF15A1C5E-20170308-172210.cpio.gz

Zrubi

unread,
Mar 9, 2017, 3:09:08 AM3/9/17
to r.fl...@openmailbox.org, qubes...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

According the data you sent me, your device is an Ivy Bridge + i7-3537U
https://pci-ids.ucw.cz/read/PC/8086/0154

According the intel official docs, this system is supprts vt-x and
vt-d as well:

http://www.intel.com/content/www/us/en/intelligent-systems/chief-river/e
mbedded-3rd-generation-intel-core-i7-processor-with-mobile-intel-hm76-ch
ipset.html

http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/7
- -series-chipset-pch-datasheet.pdf


So Xen (and qubes HCL script) reports about vt-d is seems to be true :)


- --
Zrubi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJYwQ2HAAoJEH7adOMCkunmJfMP/3y5Em90X88vXVA3LvQ7GnQy
SQ9ORhyB9Q5g8G5Q5zos8lZg8qjUb3o2fNCWJwtBKn/Bx9XXHCSxwWSmfDMDNs3/
Bm2pG+dcq31ytXygZ5HOUxtovW2LC3wyLHxLxy15TX9UJZTAqGW5qHzNBbot02f3
0azWGFbxuExd2nxw1TvN6gkGtqybG0Oltr6I2NRsxfOA5VaH6rNYrnYnCFPWL4Iv
y0i/DxDm2qGfEsUdDaT1esP1IhPcIbhsbddjM9agiPenm2ywoFmeiTJw+jmEcn+E
UGEArO+EduzriMJzkbHYUe6TthnVqSi9qy2tCf1SRXaof26NZufTboTvBUKD/Ivr
uLMAwWUYsZQClNNkKn24J7ya/VE+BFeq6qDhnHx2fWtnh0yyohtGAjIp/bCluCs4
WSxw1ZgUrp2QckwPyyuO4jMfZZASgnq9bo/U1RXO3qJBsv2B15CEB+teyAmy85ME
8HXvMN6mo+fhhcNTVGkCt13ENTpIJYC19ioylFQh7LeQ63frjOr2LgHTfYzgb1gO
PkAAY/j1xTHcJlXdIgu8a0iuXZ/15IETuBydDaGkaUWhDLQCEcFb55kvV/xibE/N
LZAsuEaaiv9a5LoUaLEOCyYf2H7Kk5KnZNLF8Fk6GjSZpuXfsIY4gwtYZI96akZm
mtWMlD0y8Xf6RLhE8mGM
=dvHe
-----END PGP SIGNATURE-----
Reply all
Reply to author
Forward
0 new messages