Re: Issue on latest Clear Linux and ACRN on UP2 board
Yin, Fengwei <fengwei.yin@...>
On 4/28/20 3:13 PM, Tomasz Bursztyka
wrote:
Hi, I cannot get ACRN hypervisor running on my setup: - UP² board (Celeron N3350) - Clear Linux, fresh install, version 32910 I followed the documentation here: - https://projectacrn.github.io/latest/tutorials/up2.html - https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html However, once I rebooted I did not get the kernel message [ 0.000000] Hypervisor detected: ACRN I only get these: [ 5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor! [ 5.766132] ACRN HVLog: acrn_hvlog: not running under acrn hypervisor! This means you boot sos kernel directly without ACRN.
Regards Yin, Fengwei
So the hypervisor is not running. There is no acrn related devices in /dev, I cannot start any VM obviously etc.. Here is the kernel cmd line: [ 0.000000] Command line: initrd=\EFI\org.clearlinux\freestanding- 00-intel-ucode.cpio initrd=\EFI\org.clearlinux\freestanding-i915- firmware.cpio.xz root=PARTUUID=05e27678-99d6-4bed-bbbe-d28cb026566a quiet console=tty0 console=ttyS0,115200n8 consoleblank=0 cryptomgr.notests hvlog=2M@0x1FE00000 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_guc=0 i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-smp rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs rootwait tsc=reliable rw The EFI configuration seems legit, however: # efibootmgr -v BootCurrent: 0003 Timeout: 1 seconds BootOrder: 0003,0005,0001 Boot0001 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b- a648-bd47664c8012)..BO Boot0003* UEFI OS HD(1,GPT,f2d8aada-01a9-4c9c-86fe- 61ccb217e678,0x800,0x47000)/File(\EFI\BOOT\BOOTX64.EFI)..BO Boot0005* ACRN Hypervisor HD(1,GPT,f2d8aada-01a9-4c9c-86fe- 61ccb217e678,0x800,0x47000)/File(\EFI\ACRN\ACRN.EFI)b.o.o.t.l.o.a.d.e.r .=.\.E.F.I.\.o.r.g...c.l.e.a.r.l.i.n.u.x.\.b.o.o.t.l.o.a.d.e.r.x.6.4... e.f.i. .u.a.r.t.=.b.d.f.@.0.:.1.8...1. I switched the order to 0005,0003,0001 but it made no difference, and once I did: the bootorder had automaticaly changed back to 0003,0005,0001. Is this nominal? The acrn.efi is from acrn_quick_setup.sh, which requested to do: cp /usr/lib/acrn/acrn.nuc7i7dnb.industry.efi /usr/lib/acrn/acrn.up- apl01.industry.efi So I did. (and installation seemed to go well.) Any idea where the problem could be?
|
|