[Bug 263118] bhyve: "Can't find /boot/entropy"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 263118] bhyve: "Can't find /boot/entropy""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 263118] bhyve: "Can't find /boot/entropy""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 263118] bhyve: "Can't find /boot/entropy""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 263118] bhyve: "Can't find /boot/entropy""
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 263118] bhyve: "Can't find /boot/entropy""
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 07 Apr 2022 12:26:31 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=263118 Bug ID: 263118 Summary: bhyve: "Can't find /boot/entropy" Product: Base System Version: 13.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bhyve Assignee: virtualization@FreeBSD.org Reporter: benoitc@enki-multimedia.eu I am trying to use an raw image (originally provided as qcow2) to install the stormishield appliance. This works and boot perfectly wellunder KVM and seabios but using bhyve it is stuck at the error "Can't find /boot/entropy". It also have to be started manually. There is no uefi boot on this raw image: ``` # mdconfig -a -t vnode -f /home/benoitc/utm-SNS-EVA-4.3.6-kvm.img md0 # file -s /dev/md0 /dev/md0: DOS/MBR boot sector; partition 1 : ID=0xa5, active, start-CHS (0x3ff,255,63), end-CHS (0x3ff,255,63), startsector 1, 20971536 sectors ``` This is why I tried with the default loader. I have the following displayed in the console: ``` Loading kernel... /boot/kernel/kernel text=0x6de318 data=0x95f20+0x95a430 syms=[0x8+0xbdc18+0x8+0xbbc32] Loading configured modules... can't find '/boot/entropy' Consoles: userboot FreeBSD/amd64 User boot lua, Revision 1.2 Loading /boot/defaults/loader.conf Loading /boot/loader.whitelist Loading /boot/device.hints Loading /boot/device.hints.sns Loading /boot/loader.conf Loading /boot/loader.conf.local ERROR: /boot/lua/password.lua:127: attempt to call a nil value (field 'restrictInteractive'). Type '?' for a list of commands, 'help' for more detailed help. OK ls / d .snap d data d boot d libexec COPYRIGHT d bin d dev d etc d lib d sbin d tmp d usr d var OK ls boot boot d kernel boot1.efi gptboot mbr loader.efi pmbr userboot.so loader boot d lua d defaults loader.whitelist device.hints manifest manifest.rcerts manifest.rsig pass_manifest pass_manifest.rcerts pass_manifest.rsig OK boot unknown command OK boot Loading kernel... /boot/kernel/kernel text=0x6de318 data=0x95f20+0x95a430 syms=[0x8+0xbdc18+0x8+0xbbc32] Loading configured modules... can't find '/boot/entropy' ``` I am trying to start it using the default bhyve loader firmware using the following configuration with vm-bhyve: ``` loader="bhyveload" cpu=1 memory=2G network0_type="virtio-net" network0_switch="public" disk0_type="virtio-blk" disk0_name="disk0" disk0_dev="sparse-zvol" uuid="7aa0cad4-b4fc-11ec-898b-1402ec690a80" network0_mac="58:9c:fc:04:33:de" ``` The vm image itself is stored on the disk as a spare zvolume instead of using the img file. vm-bhyve log: ``` Apr 07 14:19:33: initialising Apr 07 14:19:33: [loader: bhyveload] Apr 07 14:19:33: [cpu: 1] Apr 07 14:19:33: [memory: 2G] Apr 07 14:19:33: [hostbridge: standard] Apr 07 14:19:33: [com ports: com1] Apr 07 14:19:33: [uuid: 7aa0cad4-b4fc-11ec-898b-1402ec690a80] Apr 07 14:19:33: [utctime: yes] Apr 07 14:19:33: [debug mode: no] Apr 07 14:19:33: [primary disk: disk0] Apr 07 14:19:33: [primary disk dev: sparse-zvol] Apr 07 14:19:33: initialising network device tap1 Apr 07 14:19:33: adding tap1 -> bridge0 (public addm) Apr 07 14:19:33: bring up tap1 -> bridge0 (public addm) Apr 07 14:19:33: booting Apr 07 14:19:33: bhyveload -c /dev/nmdm-utm.1A -m 2G -e autoboot_delay=3 -d /dev/zvol/zroot/pollen1.my.domain.tld/vm/utm/disk0 utm Apr 07 14:19:52: [bhyve options: -c 1 -m 2G -AHP -U 7aa0cad4-b4fc-11ec-898b-1402ec690a80 -u] Apr 07 14:19:52: [bhyve devices: -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/dev/zvol/zroot/pollen1.my.domain.tld/vm/utm/disk0 -s 5:0,virtio-net,tap1,mac=58:9c:fc:04:33:de] Apr 07 14:19:52: [bhyve console: -l com1,/dev/nmdm-utm.1A] Apr 07 14:19:52: starting bhyve (run 1) root@pollen1:~ # ``` What could I test to help to debug this issue? Let me know :) -- You are receiving this mail because: You are the assignee for the bug.