search

inclavare-containers / verdictd

9 stars 14 forks source link

[ERROR] failed to read msr 0xc0010131 when running verdictd #28

Open graziadonghia opened 1 year ago

graziadonghia commented 1 year ago

Hello, I successfully installed Verdictd on my laptop, but when I try to run it I receive this weird error, which I cannot understand:

╰─➤  sudo verdictd                                                                                                                          130 ↵
[ERROR] failed to read msr 0xc0010131
[ERROR] failed to read msr 0xc0010131
[2022-11-03T09:36:41Z INFO  verdictd] Verdictd info: v0.0.1
    commit: 1d632bebe5546ef300beba8eb6c2cf32fb266d55
    buildtime: 2022-11-03 10:15:52 +01:00
[2022-11-03T09:36:41Z INFO  verdictd] Listen client API server addr: [::1]:60000
[2022-11-03T09:36:41Z INFO  verdictd] Listen addr: 127.0.0.1:1234

I did some searches and I found out that msr 0xc0010131 is related to the fact that my CPU doesn't support AMD SEV (I don't get any output when typing either dmesg|grep SME or dmesg|grep SEV. Does it mean that I cannot use Verdictd on my machine?

Another thing: before installing Verdictd I could successfully test rats-TLS with sample client and server but after Verdict installation I cannot run rats-TLS client and server anymore, moreover I receive the same error [ERROR] failed to read msr 0xc0010131, which was not present before. What does it mean?

jiazhang0 commented 1 year ago

The error message "failed to read msr" should be not printed by default. The AMD SEV platform detection should go background. I will submit a patch to mute the noise. Right now you can simply ignore it.

Do you try to specify another listening port such as "verdictd --listen 127.0.0.1:3333" to ensure sample rats-TLS server doesn't listen the same port against Verdictd?