Date
1 - 5 of 5
acrn tools warn on startup
|
Ross Burton <ross.burton@...>
So I've acrn-hypervisor working on my NUC as demonstrated by cpuid -l
0x40000000 showing ACRNACRNACRN. I've build kernel-acrn using kernel_config_uefi_sos and it boots, but I get these warnings on startup: $ dmesg | grep ACRN Hypervisor detected: ACRN ACRNTrace; Failed to setup SBuf, cpuid 0 ACRN HVLog: Failed to init last hvlog devs, errno -19 ACRN HVLog: Initialised hvlog module with 4 cpu Are these okay to ignore, or are they going to cause me problems? Thanks, Ross |
|
|
|
toggle quoted message
Show quoted text
-----Original Message-----As far as I know these are not critical errors, at least not for the hypervisor. Can you paste the output of: * dmesg | grep vh * ls /dev/acrn* Thanks, Geoffroy
|
|
|
|
Ross Burton <ross.burton@...>
(abridged because I'm transcribing, no working networking on this NUC
with the acrn kernel for some reason) $ dmesg | grep hv Command line: ... hvlog=2M@0x1fe00000 vhm: hv api version 1.0 ACRN HVLog: Failed to init last hvlog devs errno -19 ACRN HVLog: Initialised hvlog module with 4 cpu $ ls -l /dev/acrn* crw------ /dev/acrn_hvlog_cur_0 10,52 crw------ /dev/acrn_hvlog_cur_1 10,51 crw------ /dev/acrn_hvlog_cur_2 10,50 crw------ /dev/acrn_hvlog_cur_3 10,49 crw------ /dev/acrn_vhm 243,0 $ acrnlog hvlog_open_dev 208 /dev/acrn_hwlog_cur_0: Bad file descriptor (repeated for 1 2 3) hvlog_open_dev 208 /dev/acrn_hvlog_last_0: Bad file descriptior (repeated for 1 2 3) open cur:0 last:0 Ross On Wed, 30 Jan 2019 at 15:58, Geoffroy Van Cutsem <geoffroy.vancutsem@...> wrote: -----Original Message-----As far as I know these are not critical errors, at least not for the hypervisor. Can you paste the output of: |
|
|
|
It looks like the hypervisor is there and you can use it. The stuff that's broken is the logging and tracing but I don't believe this would prevent you from starting up VMs.
toggle quoted message
Show quoted text
I don't know myself what can cause the hvlog failure. I know we've seen that in the past so hopefully others monitoring this list can provide some guidance. -----Original Message----- |
|
|
|
Yin, Fengwei <fengwei.yin@...>
On 2/1/19 6:55 AM, Geoffroy Van Cutsem wrote:
It looks like the hypervisor is there and you can use it. The stuff that's broken is the logging and tracing but I don't believe this would prevent you from starting up VMs.Yes. This log is showed because the hv logging/tracing has problem. It doesn't impact the VM booting. I don't know myself what can cause the hvlog failure. I know we've seen that in the past so hopefully others monitoring this list can provide some guidance.This log shows the hvlog device is not initialized successfully. Can you-----Original Message----- share the your whole SOS kernel dmesg? Regards Yin, Fengwei
|
|
|