reactos 4.15 amd64 won't boot on qemu

Ask your support questions in here

Moderator: Moderator Team

Post Reply
uglygoose
Posts: 1
Joined: Thu Aug 27, 2020 7:28 am
Contact:

reactos 4.15 amd64 won't boot on qemu

Post by uglygoose »

reactos version:reactos-livecd-0.4.15-dev 669-g17dc5f7 msvc dbg amd64
processor: AMD Ryzen 5 4600H
environment: qemu pc-i440fx-4.2 with openBIOS
accelerator: kvm(on linux), whpx( on windows), tcg(default)
qemu command line: qemu-system-x86_64 -machine pc,accel=<accelerator> -cdrom reactos.iso -m 2000 -smp 1

ReactOS won't boot into user interface on qemu4.2 with or without an accelerator. The boot process will be stuck at "loading boot drivers". None of the boot options work therefore I can't get logs from ReactOS (SCREEN).

Are there any other ways to get logs?

P.S. x86 version of ReactOS works on qemu without any problem.

Jah-On
Posts: 22
Joined: Sun Dec 01, 2019 8:51 pm

Re: reactos 4.15 amd64 won't boot on qemu

Post by Jah-On »

64 bit is not as matured as 32 bit and is not really ready for testing.

oldman
Posts: 1138
Joined: Sun Dec 20, 2009 1:23 pm

Re: reactos 4.15 amd64 won't boot on qemu

Post by oldman »

uglygoose wrote:
Fri Aug 28, 2020 12:53 pm
reactos version:reactos-livecd-0.4.15-dev 669-g17dc5f7 msvc dbg amd64

ReactOS won't boot into user interface on qemu4.2 with or without an accelerator. The boot process will be stuck at "loading boot drivers". None of the boot options work therefore I can't get logs from ReactOS (SCREEN).
You have done well to get that far.
uglygoose wrote:
Fri Aug 28, 2020 12:53 pm
Are there any other ways to get logs?
Unfortunately it is failing just before debug output starts. Debug info starts flowing just after loading the drivers and before you get to the first blue screens.

There is a way to get it to output debug info to screen in the first stage of an installation; you could try that and see if you manage to get anything before the failure. See this and this
Please keep the Windows classic (9x/2000) look and feel.
The layman's guides to - debugging - bug reporting - compiling - ISO remaster.
They may help you with a problem, so do have a look at them.

popeye
Posts: 1
Joined: Fri Sep 11, 2020 6:17 am

Re: reactos 4.15 amd64 won't boot on qemu

Post by popeye »

Hi,
Just tried to install Reactos on Fedora 32, and the install fails.
Fedora 32 uses "cockpit" to manage VMs, and has a serial console connection.

Below is the serial console output.

Code: Select all

kdb:>  reboot
(../boot/freeldr/freeldr/disk/partition.c:425) fixme: DiskGetPartitionEntry() unimplemented for RAW
(ntoskrnl/kd/kdio.c:105) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:106) ReactOS 0.4.13 (Build 20200409-0.4.13-release-0-g4ee3778) (Commit 4ee3778a4ed2d80c96e7a0f7a1e52e78d3a6568e)
(ntoskrnl/kd/kdio.c:107) 1 System Processor [2048 MB Memory]
(ntoskrnl/kd/kdio.c:108) Command Line: NOGUIBOOT KDSERIAL DEBUGPORT=COM1 FIRSTCHANCE
(ntoskrnl/kd/kdio.c:109) ARC Paths: multi(0)disk(0)cdrom(96) \ multi(0)disk(0)cdrom(96) \reactos\
(ntoskrnl/ke/i386/cpu.c:450) Supported CPU features : KF_V86_VIS KF_RDTSC KF_CR4 KF_CMOV KF_GLOBAL_PAGE KF_LARGE_PAGE KF_MTRR KF_CMPXCHG8B KF_MMX KF_WORKING_PTE KF_PAT KF_FXSR KF_FAST_SYSCALL KF_XMMI   KF_XMMI64  KF_NX_BIT  
(ntoskrnl/ke/i386/cpu.c:722) Prefetch Cache: 64 bytes   L2 Cache: 2097152 bytes L2 Cache Line: 64 bytes L2 Cache Associativity: 8
(ntoskrnl/mm/ARM3/mminit.c:1452) HAL I/O Mapping at FFFE0000 is unsafe
(ntoskrnl/mm/mminit.c:131)           0x80000000 - 0x83400000    Boot Loaded Image
(ntoskrnl/mm/mminit.c:135)           0xB0000000 - 0xB0E01000    PFN Database
(ntoskrnl/mm/mminit.c:139)           0xB0E01000 - 0xB4DB1000    ARM3 Non Paged Pool
(ntoskrnl/mm/mminit.c:143)           0xB9400000 - 0xBB400000    System View Space
(ntoskrnl/mm/mminit.c:147)           0xBB400000 - 0xC0000000    Session Space
(ntoskrnl/mm/mminit.c:150)           0xC0000000 - 0xC03FFFFF    Page Tables
(ntoskrnl/mm/mminit.c:153)           0xC0300000 - 0xC0300FFF    Page Directories
(ntoskrnl/mm/mminit.c:156)           0xC0400000 - 0xC07FFFFF    Hyperspace
(ntoskrnl/mm/mminit.c:159)           0xC1000000 - 0xE0FFFFFF    System Cache
(ntoskrnl/mm/mminit.c:163)           0xE1000000 - 0xECC00000    ARM3 Paged Pool
(ntoskrnl/mm/mminit.c:166)           0xECC00000 - 0xF7BE0000    System PTE Space
(ntoskrnl/mm/mminit.c:169)           0xF7BE0000 - 0xFFBE0000    Non Paged Pool Expansion PTE Space
(ntoskrnl/config/cmcheck.c:25) CmCheckRegistry(0xB4B19008, 2) is UNIMPLEMENTED!
(hal/halx86/legacy/bussupp.c:699) Your machine has a PCI-to-PCI or CardBUS Bridge. PCI devices may fail!
(hal/halx86/legacy/bussupp.c:728) Found parent bus (indicating PCI Bridge). PCI devices may fail!

====== PCI BUS HARDWARE DETECTION =======

00:00.0 Host bridge [0600]: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller [8086:29c0] (rev 00)
        Subsystem: QEMU Virtual Machine [1af4:1100]
        Flags: fast devsel, latency 0

00:01.0 VGA compatible controller [0300]: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04)
        Subsystem: QEMU Virtual Machine [1af4:1100]
        Flags: fast devsel, latency 0, IRQ 10
        Memory at f4000000 (32-bit, non-prefetchable) [size=64M]
        Memory at f8000000 (32-bit, non-prefetchable) [size=128M]
        Memory at fca14000 (32-bit, non-prefetchable) [size=16K]
        I/O ports at d040 [size=64]
        Device is using IRQ 10! ISA Cards using that IRQ may fail!

00:02.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCIe Root port [1b36:000c] (rev 00)
        Subsystem: Unknown [0000:0000]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fca16000 (32-bit, non-prefetchable) [size=8K]
        Memory at 00010100 (32-bit, non-prefetchable) [size=256]
        Memory at 0000c0c0 (32-bit, non-prefetchable) [size=16K]
        Memory at fc90fc80 (32-bit, non-prefetchable) [size=1K]
        I/O ports at feb1fea0 [size=32]

00:02.1 PCI bridge [0604]: Red Hat, Inc. QEMU PCIe Root port [1b36:000c] (rev 00)
        Subsystem: Unknown [0000:0000]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fca17000 (32-bit, non-prefetchable) [size=4K]
        Memory at 00020200 (32-bit, non-prefetchable) [size=512]
        Memory at 0000c0d0 (32-bit, non-prefetchable) [size=16K]
        Memory at fc70fc60 (32-bit, non-prefetchable) [size=1K]
        I/O ports at fe91fe80 [size=128]

00:02.2 PCI bridge [0604]: Red Hat, Inc. QEMU PCIe Root port [1b36:000c] (rev 00)
        Subsystem: Unknown [0000:0000]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fca18000 (32-bit, non-prefetchable) [size=32K]
        Memory at 00030300 (32-bit, non-prefetchable) [size=256]
        Memory at 0000c0d0 (32-bit, non-prefetchable) [size=16K]
        Memory at fc50fc40 (32-bit, non-prefetchable) [size=1K]
        I/O ports at fe71fe60 [size=32]

00:02.3 PCI bridge [0604]: Red Hat, Inc. QEMU PCIe Root port [1b36:000c] (rev 00)
        Subsystem: Unknown [0000:0000]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fca19000 (32-bit, non-prefetchable) [size=4K]
        Memory at 00040400 (32-bit, non-prefetchable) [size=1K]
        Memory at 0000c0d0 (32-bit, non-prefetchable) [size=16K]
        Memory at fc30fc20 (32-bit, non-prefetchable) [size=1K]
        I/O ports at fe51fe40 [size=64]

00:02.4 PCI bridge [0604]: Red Hat, Inc. QEMU PCIe Root port [1b36:000c] (rev 00)
        Subsystem: Unknown [0000:0000]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fca1a000 (32-bit, non-prefetchable) [size=8K]
        Memory at 00050500 (32-bit, non-prefetchable) [size=256]
        Memory at 0000c0d0 (32-bit, non-prefetchable) [size=16K]
        Memory at fc10fc00 (32-bit, non-prefetchable) [size=1K]
        I/O ports at fe31fe20 [size=32]

00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03)
        Subsystem: QEMU Virtual Machine [1af4:1100]
        Flags: fast devsel, latency 0, IRQ 10
        Memory at fca10000 (32-bit, non-prefetchable) [size=64K]
        Device is using IRQ 10! ISA Cards using that IRQ may fail!

00:1f.0 ISA bridge [0601]: Intel Corporation 82801IB (ICH9) LPC Interface Controller [8086:2918] (rev 02)
        Subsystem: QEMU Virtual Machine [1af4:1100]
        Flags: fast devsel, latency 0

00:1f.2 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02)
        Subsystem: QEMU Virtual Machine [1af4:1100]
        Flags: bus master, fast devsel, latency 0, IRQ 10
        I/O ports at d060 [size=32]
        Memory at fca1b000 (32-bit, non-prefetchable) [size=4K]
        Device is using IRQ 10! ISA Cards using that IRQ may fail!

00:1f.3 SMBus [0c05]: Intel Corporation 82801I (ICH9 Family) SMBus Controller [8086:2930] (rev 02)
        Subsystem: QEMU Virtual Machine [1af4:1100]
        Flags: fast devsel, latency 0, IRQ 10
        I/O ports at 0700 [size=256]
        Device is using IRQ 10! ISA Cards using that IRQ may fail!

01:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3] (rev 00)
        Subsystem: Unknown [8086:0000]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fc840000 (32-bit, non-prefetchable) [size=256K]
        Memory at fc860000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at c000 [size=16K]
        Memory at fc880000 (32-bit, non-prefetchable) [size=512K]
        Device is using IRQ 11! ISA Cards using that IRQ may fail!

02:00.0 USB controller [0c03]: Red Hat, Inc. QEMU XHCI Host Controller [1b36:000d] (rev 01)
        Subsystem: Unknown [1af4:1100]
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at fc600000 (64-bit, non-prefetchable) [size=2M]
        Device is using IRQ 11! ISA Cards using that IRQ may fail!

03:00.0 Communication controller [0780]: Red Hat, Inc. Virtio console [1af4:1043] (rev 01)
        Subsystem: Unknown [1af4:1100]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fc400000 (32-bit, non-prefetchable) [size=4M]
        Memory at fe600000 (64-bit, prefetchable) [size=2M]
        Device is using IRQ 11! ISA Cards using that IRQ may fail!

04:00.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon [1af4:1045] (rev 01)
        Subsystem: Unknown [1af4:1100]
        Flags: fast devsel, latency 0, IRQ 11
        Memory at fe400000 (64-bit, prefetchable) [size=4M]
        Device is using IRQ 11! ISA Cards using that IRQ may fail!

05:00.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block device [1af4:1042] (rev 01)
        Subsystem: Unknown [1af4:1100]
        Flags: bus master, fast devsel, latency 0, IRQ 11
        Memory at fc000000 (32-bit, non-prefetchable) [size=64M]
        Memory at fe200000 (64-bit, prefetchable) [size=2M]
        Device is using IRQ 11! ISA Cards using that IRQ may fail!

====== PCI BUS DETECTION COMPLETE =======

PC Compatible Eisa/Isa HAL Detected
(sdk/lib/rtl/image.c:171) Invalid base address: 00000000
(ntoskrnl/io/iomgr/driver.c:1635) '\Driver\sacdrv' initialization failed, status (0xc0000037)
(ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\sacdrv'
(drivers/filesystems/fastfat/iface.c:161) FastFAT KDBG extension registered: yes
Btrfs ERR : add_group_mapping : invalid SID
WARNING:  NtNotifyChangeMultipleKeys at ntoskrnl/config/ntapi.c:1450 is UNIMPLEMENTED!
Btrfs ERR : watch_registry : ZwNotifyChangeKey returned c0000002
(drivers/storage/class/ramdisk/ramdisk.c:2486) FIXME: Installing from RamDisk is UNSUPPORTED!
(drivers/storage/scsiport/scsiport.c:5859) ZwOpenKey() failed with Status=0xC0000034
(hal/halx86/legacy/bussupp.c:1274) Slot assignment for 5 on bus 0
(hal/halx86/legacy/bus/pcibus.c:742) WARNING: PCI Slot Resource Assignment is FOOBAR
(hal/halx86/legacy/bus/sysbus.c:109) Translation of fca1b002 failed!
(ntoskrnl/io/iomgr/driver.c:1635) '\Driver\uniata' initialization failed, status (0xc00000c0)
(ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\uniata'
(ntoskrnl/io/iomgr/driver.c:1635) '\Driver\buslogic' initialization failed, status (0xc00000c0)
(ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\buslogic'
(drivers/storage/port/storport/storport.c:961) StorPortInitialize(B4D756F8 F7683A4C F7683880 00000000)
(drivers/storage/port/storport/storport.c:963) HwInitializationDataSize: 84
(drivers/storage/port/storport/storport.c:964) AdapterInterfaceType: 5
(drivers/storage/port/storport/storport.c:965) HwInitialize: F7AA151C
(drivers/storage/port/storport/storport.c:966) HwStartIo: F7AA4091
(drivers/storage/port/storport/storport.c:967) HwInterrupt: F7AA266A
(drivers/storage/port/storport/storport.c:968) HwFindAdapter: F7AA4430
(drivers/storage/port/storport/storport.c:969) HwResetBus: F7AA15B3
(drivers/storage/port/storport/storport.c:970) HwDmaStarted: 00000000
(drivers/storage/port/storport/storport.c:971) HwAdapterState: 00000000
(drivers/storage/port/storport/storport.c:972) DeviceExtensionSize: 75584
(drivers/storage/port/storport/storport.c:973) SpecificLuExtensionSize: 0
(drivers/storage/port/storport/storport.c:974) SrbExtensionSize: 1320
(drivers/storage/port/storport/storport.c:975) NumberOfAccessRanges: 6
(drivers/storage/port/storport/storport.c:1001) No driver object extension!
(drivers/storage/port/storport/storport.c:1013) Driver object extension created!
(drivers/storage/port/storport/storport.c:31) PortAddDriverInitData()
(drivers/storage/port/storport/storport.c:1044) StorPortInitialize() done (Status 0x00000000)
(ntoskrnl/io/iomgr/driver.c:1635) '\Driver\floppy' initialization failed, status (0xc000000e)
(ntoskrnl/io/iomgr/driver.c:64) Deleting driver object '\Driver\floppy'
(drivers/storage/port/storport/storport.c:461) DriverEntry(B4B11038 F7683A4C)
(ntoskrnl/io/iomgr/iomgr.c:573) IopCreateArcNames failed: c0000034

*** Fatal System Error: 0x00000069
                       (0x00000000,0x00000000,0x00000000,0x00000000)


Entered debugger on embedded INT3 at 0x0008:0x809566f8.
kdb:> 
The qemu command is

Code: Select all

usr/bin/qemu-system-x86_64 -name guest=ReactOS,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-9-ReactOS/master-key.aes -machine pc-q35-4.2,accel=kvm,usb=off,vmport=off,dump-guest-core=off -cpu Skylake-Client-IBRS,ss=on,vmx=on,pdcm=on,hypervisor=on,tsc-adjust=on,clflushopt=on,umip=on,md-clear=on,stibp=on,arch-capabilities=on,ssbd=on,xsaves=on,pdpe1gb=on,ibpb=on,amd-ssbd=on,skip-l1dfl-vmentry=on,hle=off,rtm=off,hv-time,hv-relaxed,hv-vapic,hv-spinlocks=0x1fff -m 2048 -overcommit mem-lock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 0811569b-44f3-4c88-9d3e-e5a94e01c0f8 -no-user-config -nodefaults -chardev socket,id=charmonitor,fd=36,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -no-shutdown -global ICH9-LPC.disable_s3=1 -global ICH9-LPC.disable_s4=1 -boot strict=on -device pcie-root-port,port=0x10,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x2 -device pcie-root-port,port=0x11,chassis=2,id=pci.2,bus=pcie.0,addr=0x2.0x1 -device pcie-root-port,port=0x12,chassis=3,id=pci.3,bus=pcie.0,addr=0x2.0x2 -device pcie-root-port,port=0x13,chassis=4,id=pci.4,bus=pcie.0,addr=0x2.0x3 -device pcie-root-port,port=0x14,chassis=5,id=pci.5,bus=pcie.0,addr=0x2.0x4 -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.2,addr=0x0 -device virtio-serial-pci,id=virtio-serial0,bus=pci.3,addr=0x0 -blockdev {"driver":"file","filename":"/home/VMs/ReactOS.img","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-2-format","read-only":false,"driver":"qcow2","file":"libvirt-2-storage","backing":null} -device virtio-blk-pci,scsi=off,bus=pci.5,addr=0x0,drive=libvirt-2-format,id=virtio-disk0 -blockdev {"driver":"file","filename":"/home/Iso_Pool/ReactOS-0.4.13.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"} -blockdev {"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"} -device ide-cd,bus=ide.1,drive=libvirt-1-format,id=sata0-0-1,bootindex=1 -netdev tap,fd=38,id=hostnet0 -device e1000e,netdev=hostnet0,id=net0,mac=52:54:00:5d:b4:5f,bus=pci.1,addr=0x0 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -vnc 127.0.0.1:1 -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 -device ich9-intel-hda,id=sound0,bus=pcie.0,addr=0x1b -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny -msg timestamp=on
Any tips please

Thanks

User avatar
EmuandCo
Developer
Posts: 4436
Joined: Sun Nov 28, 2004 7:52 pm
Location: Germany, Bavaria, Steinfeld
Contact:

Re: reactos 4.15 amd64 won't boot on qemu

Post by EmuandCo »

It would be insteresting what entering bt and enter button is outputting.
https://reactos.org/wiki/Kdbg
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.

hbelusca
Developer
Posts: 1173
Joined: Sat Dec 26, 2009 10:36 pm
Location: Zagreb, Croatia

Re: reactos 4.15 amd64 won't boot on qemu

Post by hbelusca »

The x64 builds of ReactOS available in the getbuilds page are not for everyone usage and won't work. These are just builds to control that the existing code compiles in x64 mode too.
The actual x64 development is done in a separate branch, for which no builds are publicly available.
Also, these are build using MSVC, which necessitate the usage of the WinDbg debugger (or assimilated debugging protocol) (and to my knowledge the Kdbg thing is of no use there), which you couldn't have clearly used since you used Linux to perform your tests.

learn_more
Developer
Posts: 182
Joined: Fri Dec 19, 2014 10:00 pm

Re: reactos 4.15 amd64 won't boot on qemu

Post by learn_more »

> ReactOS 0.4.13 (Build 20200409-0.4.13-release-0-g4ee3778)

Your title states 4.15
That is not even close...

Missingno50
Posts: 64
Joined: Tue Mar 13, 2018 4:28 am
Location: Dixon, California
Contact:

Re: reactos 4.15 amd64 won't boot on qemu

Post by Missingno50 »

learn_more wrote:
Sat Sep 12, 2020 4:06 pm
> ReactOS 0.4.13 (Build 20200409-0.4.13-release-0-g4ee3778)

Your title states 4.15
That is not even close...
That's not the same guy. uglygoose started the post, and that reply is by popeye.
"We are going to have to act, if we want to live in a different world."
Proud owner of one semi-modern ROS compatible computer. I hope to make an industry out of selling ROS compatibles the moment 0.5.0 releases.

Post Reply

Who is online

Users browsing this forum: Ahrefs [Bot], Google [Bot], Yandex [Bot] and 1 guest