Open Marietto2008 opened 2 years ago
thiagomacieira
commented
2 years ago That might be a red herring. The powerclamp driver does fail to load, but that shouldn't be fatal. The error happened after the driver.
Can you boot without "quiet" in the kernel command-line and capture the logs? Preferably as text, not as a screenshot. The kernel will log to the first serial port, so configure your hypervisor to provide a serial port that logs to a file and that should be the best.
Marietto2008
commented
2 years ago Hello.
I've just emulated the same clear linux physical installation on Linux with qemu + kvm and it worked. It was able to boot. I remember that the same installation is frozen if I emulate it on FreeBSD using bhyve. So,at this point it seems that bhyve misses some component that qemu + kvm has. Or ? Do you have an alternative reason ? Please give a look at the pictures below :
[image: Istantanea_2022-07-12_20-36-57.png] [image: Istantanea_2022-07-12_20-36-14.png]
Il giorno mar 12 lug 2022 alle ore 20:52 Thiago Macieira < @.***> ha scritto:
That might be a red herring. The powerclamp driver does fail to load, but that shouldn't be fatal. The error happened after the driver.
Can you boot without "quiet" in the kernel command-line and capture the logs? Preferably as text, not as a screenshot. The kernel will log to the first serial port, so configure your hypervisor to provide a serial port that logs to a file and that should be the best.
— Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2672#issuecomment-1182264046, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAFYNC7ZMTDRZVGU65OGBLTVTW5HRANCNFSM53KJOPAQ . You are receiving this because you authored the thread.Message ID: @.***>
-- Mario.
thiagomacieira
commented
2 years ago Doesn't look like you included any images.
Marietto2008
commented
2 years ago I'd attached the images via email,but I see that in that way it can't add them here :
thiagomacieira
commented
2 years ago Those images don't tell me anything.
Please get the kernel non-quiet boot log.
Marietto2008
commented
2 years ago bhyve -S -c sockets=1,cores=2,threads=2 -m 4G -w -H -A \
-s 0,hostbridge \
-s 1,ahci-hd,/dev/$vmdisk2 \
-s 8:,virtio-net,tap20 \
-s 29,fbuf,tcp=0.0.0.0:5920,w=1600,h=950 \
-s 30,xhci,tablet \
-s 31,lpc \
-l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd \
-l com1,stdio \
vm20
=
BdsDxe: loading Boot0001 "UEFI BHYVE SATA DISK BHYVE-122D-074E-7937" from PciRoot(0x0)/Pci(0x1,0x0)/Sata(0x0,0xFFFF,0x0)
BdsDxe: starting Boot0001 "UEFI BHYVE SATA DISK BHYVE-122D-074E-7937" from PciRoot(0x0)/Pci(0x1,0x0)/Sata(0x0,0xFFFF,0x0)
rdmsr to register 0x140 on vcpu 0
wrmsr to register 0x140(0) on vcpu 0
rdmsr to register 0x64d on vcpu 0
rdmsr to register 0x64e on vcpu 0
rdmsr to register 0x34 on vcpu 0
[ 0.288552] kvm: no hardware support for 'kvm_intel'
[ 0.724107] intel_powerclamp: CPU does not support MWAIT
rdmsr to register 0x64d on vcpu 0
rdmsr to register 0x48 on vcpu 0
rdmsr to register 0x122 on vcpu 0
rdmsr to register 0x10f on vcpu 0
rdmsr to register 0x123 on vcpu 0
rdmsr to register 0xc0011020 on vcpu 0
Unhandled ps2 mouse command 0xe1
clr-827c52e759364ad885ee8ed30a817164 login: marietto
Password:
Login wrong
PC192 login: root
Password:
root@PC192.168.1.4 ~ # uname -a
Linux PC192.168.1.4 5.18.9-1159.native #1 SMP Wed Jul 6 14:51:31 PDT 2022 x86_64 GNU/Linux
root@PC192.168.1.4 ~ # uname -r
5.18.9-1159.native
root@PC192.168.1.4 ~ # startx
xauth: file /root/.serverauth.491 does not exist
xauth: file /root/.Xauthority does not exist
xauth: file /root/.Xauthority does not exist
X.Org X Server 1.21.1.3
X Protocol Version 11, Revision 0
Current Operating System: Linux PC192.168.1.4 5.18.9-1159.native #1 SMP Wed Jul 6 14:51:31 PDT 2022 x86_64
Kernel command line: initrd=\EFI\org.clearlinux\freestanding-00-intel-ucode.cpio initrd=\EFI\org.clearlinux\freestanding-i915-firmware.cpio.xz root=PARTUUID=e7df100d-df12-4a37-bc89-2194815df4ef quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests init=/usr/bin/initra-desktop initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check noreplace-smp page_alloc.shuffle=1 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs,f2fs tsc=reliable rw
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 13 03:22:51 2022
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE)
Fatal server error:
(EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: server error
Hello to everyone.
I've installed CL physically on one of my disks and it seems that everything works correctly (except the audio for the moment) and then I tried to boot ClearLinux with bhyve on FreeBSD 13.1-RELEASE. Below you can see the parameters that I've used :
Unfortunately CL didn't boot because an error that seems freezes the booting of the OS on the screen :
CPU does not support MWAIT?
Is there a method to disable the parameter MWAIT from the kernel parameters loaded during the boot ? Below you can see what are the hardware specs of PC :