X64 exception type 0000000000000d вылетает ошибка

  • #1

Hi all,

I’ve been using Chimera for years, but would like to migrate over to Clover.
Every time I try to install it however, I come up with the attached screen.

X64 Exception Type etc…

This screen pops up when booting from the USB stick.

I have a Gigabyte GA-X58-UD7.

I’ve tried installing Clover using the following setup options:
Install Clover in the ESP
Install boot0af in MBR
CloverEFI 64-bits SATA

The RAM is fine, I’ve tried searching everywhere for someone with a similar message, but I’m unable to find anyone with the same problem. Does anyone have any suggestions?

I get the same issue with Mavericks, Yosemite and El Capitan.

Any help would be greatly appreciated.

Thanks!

  • x64exception.jpg

    x64exception.jpg

    213.4 KB

    · Views: 2,724

  • #2

Greetings,

I’m getting the same thing after installing Cloverboot 3526. Nobody ever helped you did they? :think:
The only difference is that I’m getting a 000D at the end of my exception type code.
I can’t find any useful help on any search or boards. Perhaps a good gentlemen would be kind enough to provide some assistance on this matter.

Cheers,

Prof. Synthology

  • #3

You have to uninstall clover and use multibeast instead

  • #4

Bump — same error/crash — same 00000D as Prof. Synthology.

With all due respect to Jasjar, no, clover IS compatible with our boards, and «Multibeast» can install either the Clover or Chimera bootloaders.

What this needs is a call from Going Bald (cue the heroic entrance music)…

Last edited:

  • #5

Facing this exact issue on a similar board. Had clover working for a long time, not sure what changed.

What fixed this?

Источник

Shaneee

  • Author

    • Share

It happens on El Capitan too. Older AMDs can’t boot Sierra yet at all. So Clover doesn’t depend on CPU Features?

Link to comment
Share on other sites

Slice

    • Share

It happens on El Capitan too. Older AMDs can’t boot Sierra yet at all. So Clover doesn’t depend on CPU Features?

No, it compiled with no-sse, no-mmx.

Did you use HFSPlus.efi or other third-party drivers? They can contain such instructions.

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

No, it compiled with no-sse, no-mmx.

Did you use HFSPlus.efi or other third-party drivers? They can contain such instructions.

No didn’t add any except the Clover installer default. Tried removing them all but still the same error.

Link to comment
Share on other sites

Slice

    • Share

There may be a reason with another interrupt model, another method for switching 16-32-64 bits, another LAPIC, MSR, CPUID.

To catch this one should know what are they. Intel gives us datasheets, what about AMD?

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

There may be a reason with another interrupt model, another method for switching 16-32-64 bits, another LAPIC, MSR, CPUID.

To catch this one should know what are they. Intel gives us datasheets, what about AMD?

You mean this? http://support.amd.com/TechDocs/43375.pdf

Link to comment
Share on other sites

Slice

    • Share

It is one of the possible datasheets, may be it also contains few useful information. 

Search for MSR found only line

2) MaxVID is reported in MSRC001_0071 (COFVID_STATUS).    

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

Pretty sure that datasheet contains my CPU. Athlon II X2 215. If there’s a way to get the info from the CPU it’s self I can do that for you. I’m on Windows just now.

Edit: Does this help? It’s from the AMD XNU patches inside cpuid.c

boolean_t IsAmdCPU(void) {
    if (ForceAmdCpu)
        return TRUE;
    
    uint32_t ourcpuid[4];
    do_cpuid(0, ourcpuid);
    if (ourcpuid[ebx] == 0x68747541 &&
        ourcpuid[ecx] == 0x444D4163 &&
        ourcpuid[edx] == 0x69746E65)
        return TRUE;
    
    return FALSE;
};

Link to comment
Share on other sites

Slice

    • Share

This is far later the red panic.

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

Ahh ok then. Is there any info I can get that will help fix this?

Link to comment
Share on other sites

  • 1 month later…

apianti

    • Share

From your image the problem is this http://wiki.osdev.org/Exceptions#Invalid_Opcode. But reading through the code dump at the bottom it seems the problem is actually that the opcode 0F 38 04 is an SSSE3 instruction PMADDUBSW. SSSE3 is not supported by AMD processors older than Bobcat.

EDIT: There is also prefix that starts with 66 (which is what is used here) and optionally followed by another byte specifying the registers before the opcode.


  • Like


    2

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

From your image the problem is this http://wiki.osdev.org/Exceptions#Invalid_Opcode. But reading through the code dump at the bottom it seems the problem is actually that the opcode 0F 38 04 is an SSSE3 instruction PMADDUBSW. SSSE3 is not supported by AMD processors older than Bobcat.

EDIT: There is also prefix that starts with 66 (which is what is used here) and optionally followed by another byte specifying the registers before the opcode.

It must be in the kernel opemu then. Thanks for the info.


  • Like


    1

Link to comment
Share on other sites

jsl

    • Share

It must be in the kernel opemu then. Thanks for the info.

If it’s the cause of error, is there any possibility to fix it ?

Otherwise no solution for older AMD CPU to boot 10.11.X by Clover.

Link to comment
Share on other sites

apianti

    • Share

When is the exception happening? When you try to boot into clover before the GUI? Or after you select to boot mac OS?

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

It happens once you boot to the OS. I’ll experiment with the kernel soon

Sent from my SM-G920F using Tapatalk

Link to comment
Share on other sites

apianti

    • Share

Yeah then you just need to find a kernel that is built without SSSE3 or build it yourself.


  • Like


    1

Link to comment
Share on other sites

  • 3 months later…

Slice

    • Share

It seems Red Screen Panic on AMD CPU is resolved in Clover 4114.


  • Like


    2

Link to comment
Share on other sites

Shaneee

  • Author

    • Share

I’d test but I’ve since updated to FX which didn’t have the issue. Only issue I’ve got is kernel related with Clover I think. Opcode issues after graphics load in verbose. Enoch is fine though. Just me with the issue so I’ll sort it at some point.

Link to comment
Share on other sites

  • 1 month later…

kibiz0r

    • Share

I am having the same issue with a Phenom II X3 720 on an MSI 790GX-G65 mobo.

I just tried Clover_v2.4k_r4173 and saw no change.

Thinking I’ll just swap to an Intel system, but if it’s supposed to be supported and I can help debug, I’m down with that.

Link to comment
Share on other sites

Gigamaxx

    • Share

I am having the same issue with a Phenom II X3 720 on an MSI 790GX-G65 mobo.

I just tried Clover_v2.4k_r4173 and saw no change.

Thinking I’ll just swap to an Intel system, but if it’s supposed to be supported and I can help debug, I’m down with that.

Did you add a AMD kernel? 

Link to comment
Share on other sites

kibiz0r

    • Share

Did you add a AMD kernel?

Yeah, this one.

I was originally trying to install Sierra, but given the FUD I found around the forum wrt SSE4a, I decided to try El Capitan instead.

  • mas install 1018109117
  • Partitioned 128GB into 20GB (as first partition «USB1») and remainder
  • [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 6.2.0 El Capitan onto 20GB partition
  • cp -f ~/Downloads/el-capitan-amd-kernel-v1-0-0/kernel /Volumes/USB1/System/Library/Kernels/kernel
rm -rf /Volumes/USB1/System/Library/Extensions/System.kext/
cp -r ~/Downloads/el-capitan-amd-kernel-v1-0-0/System.kext /Volumes/USB1/System/Library/Extensions/System.kext
  • Clover_v2.4k_r4173.pkg with default installation options onto USB1
  • Booted from USB1 on target machine
  • Clover shows correct revision number 4173
  • Select «Boot Mac OS X from USB» from Clover menu
  • Apple logo appears for a minute or so
  • X64 Exception Type 0000000000000006
Link to comment
Share on other sites

  • 1 month later…

Slice

    • Share

Yeah, this one.

I was originally trying to install Sierra, but given the FUD I found around the forum wrt SSE4a, I decided to try El Capitan instead.

  • mas install 1018109117
  • Partitioned 128GB into 20GB (as first partition «USB1») and remainder
  • [url="http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/"]#####[/url] 6.2.0 El Capitan onto 20GB partition
  • cp -f ~/Downloads/el-capitan-amd-kernel-v1-0-0/kernel /Volumes/USB1/System/Library/Kernels/kernel
rm -rf /Volumes/USB1/System/Library/Extensions/System.kext/
cp -r ~/Downloads/el-capitan-amd-kernel-v1-0-0/System.kext /Volumes/USB1/System/Library/Extensions/System.kext
  • Clover_v2.4k_r4173.pkg with default installation options onto USB1
  • Booted from USB1 on target machine
  • Clover shows correct revision number 4173
  • Select «Boot Mac OS X from USB» from Clover menu
  • Apple logo appears for a minute or so
  • X64 Exception Type 0000000000000006

So the Clover works allowing you  to «Select «Boot Mac OS X from USB»«. 

Exception appears after that.

Without logs and debugging I can’t say something useful.

Link to comment
Share on other sites

  • 3 months later…

braavos

    • Share

I’ve heard Clover v3 will be AMD ready. Is that true? I always noticed the AMD kernel by hackers is needed before. Really want to ignore that actions. Thanks.

Link to comment
Share on other sites

Gigamaxx

    • Share

I’ve heard Clover v3 will be AMD ready. Is that true? I always noticed the AMD kernel by hackers is needed before. Really want to ignore that actions. Thanks.

You still need to replace the kernel for AMD systems but the good news is Clover works now and gives you many boot parameter options.    

Link to comment
Share on other sites

braavos

    • Share

You still need to replace the kernel for AMD systems but the good news is Clover works now and gives you many boot parameter options.

Don’t understand here. Is it a choose option between replace and good news? Clover works now and do not need replace kernel?

Link to comment
Share on other sites

Gigamaxx

    • Share
Link to comment
Share on other sites

Источник

Donation with PayPal HERE

Donation with Stripe HERE

Donation with BuyMeaCoffee HERE

Donation with Mercado Livre HERE

Donation with Skrill danielnmaldonado@gmail.com

Donation with Binance 0xdbe48ef6b158f1dd0035d7f49555c99e52f72714

Donation with BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3

Donation with PicPay @danielnmaldonado

Donation with PiX @danielnmaldonado@gmail.com

About Premium Users you can check HERE

Problems with Paypal HERE

oaGK2x0.png

Источник



4765
Views

2
Replies



2
Participants



Last post by 
Undeniable, 


Jump to Latest

So today my new pc case came in and I decided to move everything over to the new case. After setting everything up my computer would post, but would not go to the BIOS screen and would say «no bootable devices found press any key to continue.» And after pressing a key it would take me to a screen with a bunch of red text with the exception error. I can’t find anything helpful online and I’m completely lost. I didn’t change anything but the case.

MSI X58M
Xeon X5660
Kingston RAM DDR3 24gb

Источник

Describe the bug
Boot is failing when attempting to configure more than 2 cores, using CLOUDHV.fd OVMF firmware. I’m hitting a few variations of errors described below, which are blocking the VM from coming up. This issue is not hit when using 2 cores or fewer, or if I use rust-hypervisor hypervisor-fw. When using hypervisor-fw the VM is able to boot with any number of cores 2,4,8 etc.

I am also able to deploy VMs using QEMU with 4+ cores and the issue does not reproduce.

Combinations:

VMM Firmware Core count Result
cloud-hypervisor rust-hypervisor 2 Success
cloud-hypervisor rust-hypervisor 4 Success
cloud-hypervisor OVMF 2 Success
cloud-hypervisor OVMF 4 Fail
QEMU In-built 2 Success
QEMU In-built 4 Success

Variations seen:

  1. #PF — Page-Fault
!!!! X64 Exception Type - 0E(#PF - Page-Fault)  CPU Apic ID - 00000001 !!!!
ExceptionData - 0000000000000000  I:0 R:0 U:0 W:0 P:0 PK:0 SS:0 SGX:0
  1. #UD — Invalid Opcode
!!!! X64 Exception Type - 06(#UD - Invalid Opcode)  CPU Apic ID - 00000001 !!!!
RIP  - 0000000000000008, CS  - 000000003FD5FE50, RFLAGS - 000000000000001F
RAX  - 0000000000000000, RCX - 0000000000000000, RDX - 000000003FD5FDF0
RBX  - 000000003FD5FDEC, RSP - 0000000000000000, RBP - 0000000000010046
RSI  - 0000000049656E69, RDI - 0000000000000018
R8   - 0000000000010046, R9  - 000000003FD5FE20, R10 - 0000000000000008
R11  - 0000000000000000, R12 - 0000000000000000, R13 - 0000000000000000
R14  - 000000003FD5FE50, R15 - 000000000000000D
DS   - 000000000009F000, ES  - 000000000000001B, FS  - 0000000000000008
GS   - 0000000000000018, SS  - 000000003FD5FE08
CR0  - 0000000000000228, CR2 - 0000000000010002, CR3 - 0000000000000000
CR4  - 0000000000000000, CR8 - 00000000004FFF00
DR0  - 00000000FFFF0FF0, DR1 - 0000000000000400, DR2 - 0000000080000013
DR3  - 0000000000000000, DR6 - 0000000000000000, DR7 - 0000000000800000
GDTR - 000000003FF624AE 0000000000000008, LDTR - 000000003FF7B008
IDTR - 0000000000000008 0000000000000008,   TR - 000000000000021F
FXSAVE_STATE - 000000003FD5FA80
!
  1. #GP — General Protection
!!!! X64 Exception Type - 06(#UD - Invalid Opcode)  CPU Apic ID - 0000003F !!!!
RIP  - 000000000F8BFBFF, CS  - 0000000000000000, RFLAGS - 0000000000000018
RAX  - 0000000000000006, RCX - 000000003FD5FE60, RDX - 0000000000000000
RBX  - 0000000000000000, RSP - 0000000000000000, RBP - 0000000000000000
RSI  - 0000000000000000, RDI - 0000000000000000
R8   - 0000000000000000, R9  - 0000000000000508, R10 - 0000000000000018
R11  - 0000000000010046, R12 - 000000003FD5FE20, R13 - 0000000000000008
R14  - 0000000000000000, R15 - 0000000000000000
DS   - 0000000000000000, ES  - 0000000000000000, FS  - 0000000000000000
GS   - 0000000000000000, SS  - 0000000000000000
CR0  - 000000000000021F, CR2 - 0000000000000008, CR3 - 0000000000000008
CR4  - 0000000000000008, CR8 - 0000000000000008
DR0  - 0000000000010046, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 00000000004FFF00, DR6 - 000000000000001F, DR7 - 000000003FF7B008
GDTR - 000000000009F000 000000003FD5FE60, LDTR - 0000000000000008
IDTR - 000000003FD5FE20 0000000000000000,   TR - 00000000000000F0
FXSAVE_STATE - 000000003FD5FAE0
!!!! Find image based on IP(0xF8BFBFF) (No PDB)  (ImageBase=0000000000BA194C, EntryPoint=0000000000BA830B) !!!!
!!!! X64 Exception Type - 0D(#GP - General Protection)  CPU Apic ID - 00000001 !!!!
ExceptionData - 0000000000000000
RIP  - 000000003FD5F7C1, CS  - 0000000000004642, RFLAGS - 000000003FD5F780
RAX  - 0000000000000000, RCX - 000000002BFA1A70, RDX - 0000000000000006
RBX  - 0000000000BA194C, RSP - 000000003FD5F780, RBP - 000000003FD5F820
RSI  - 000000003FD5F7E1, RDI - 000000003FD5F900
R8   - 000000003FD5F8A0, R9  - 000000003FF664A6, R10 - 0000000000000000
R11  - 000000003FD5F7C0, R12 - 000000003FD5FAD8, R13 - 0000000000000006
R14  - 000000002BFA1A70, R15 - 000000003FD5F8B8
DS   - 4138333042000000, ES  - 0000000000000001, FS  - 0000000000000000
GS   - 000000003FD5F7C0, SS  - 000000003FD5F8BF
CR0  - 0000000080000013, CR2 - 000000003FD5F740, CR3 - 000000003FF663B0
CR4  - 0000000000000228, CR8 - 0000000000000100
DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
GDTR - 0000000000000000 0000000000000002, LDTR - 00000000000000FF
IDTR - 000000003FD5F87F 000000003FD5F8C8,   TR - 0000000000000001
FXSAVE_STATE - 000000003FD5F430
!!!! Find image based on IP(0x3FD5F7C1) (No PDB)  (ImageBase=0000000000BA194C, EntryPoint=0000000000BA830B) !!!!
!!!! X64 Exception Type - 06(#UD - Invalid Opcode)  CPU Apic ID - 00000002 !!!!
RIP  - 0000000000000000, CS  - 000000003FD5FAD8, RFLAGS - 000000003FD5F900
RAX  - 303030303030303D, RCX - 746E696F50797274, RDX - 6E45202C43343931
RBX  - 4142303030303030, RSP - 303030303D657361, RBP - 426567616D492820
RSI  - 000000003FD5F8B8, RDI - 000000002BFA1A70
R8   - 3033384142303030, R9  - 0D21212121202942, R10 - 535F45564153000A
R11  - 30202D2045544154, R12 - 3330303030303030, R13 - 0D30454146354446
R14  - 303030303030000A, R15 - 2D2052542020202C
DS   - 000000003FD5F7C0, ES  - 0000000000000000, FS  - 000000003FF664A6
GS   - 000000003FD5F8A0, SS  - 0000000000000006
CR0  - 000000003FD5F7C0, CR2 - 0000000000000001, CR3 - 4138333042000000
CR4  - 0000000000004642, CR8 - 000000003FD5F8BF
DR0  - 0000000000000001, DR1 - 0000000000000000, DR2 - 0000000000000002
DR3  - 000000003FD5F87F, DR6 - 000000003FD5F8C8, DR7 - 000000003FD5F7C1
GDTR - 000000003FD5F780 0000000000BA194C, LDTR - 000000003FD5F7E1
IDTR - 0000000000000006 000000002BFA1A70,   TR - 000000003FD5F820
FXSAVE_STATE - 000000003FD5F4A0
!!!! Can't find image information. !!!!
  1. Hang with no stderr output.

To Reproduce
Steps to reproduce the behaviour:

Version

cloud-hypervisor v31.1

Did you build from source, if so build command line (e.g. features):
Yes

BUILD_COMMAND           rustup default stable && cargo build --release --all --manifest-path ${CMAKE_CURRENT_SOURCE_DIR}/cloud-hypervisor/Cargo.toml --target-dir ${CMAKE_CURRENT_BINARY_DIR}/cloud-hypervisor
INSTALL_COMMAND         mkdir -p ${CMAKE_INSTALL_PREFIX}/bin && cp ${CMAKE_CURRENT_BINARY_DIR}/cloud-hypervisor/release/cloud-hypervisor ${CMAKE_INSTALL_PREFIX}/bin/cloud-hypervisor

VM configuration

# Set up working directory
working_dir=/tmp/chv_work
mkdir -p $working_dir
cp -f cloud-hypervisor $working_dir/.
cp -f CLOUDHV.fd $working_dir/.

# Download Ubuntu 22.04 image
wget https://cloud-images.ubuntu.com/releases/22.04/release-20221018/ubuntu-22.04-server-cloudimg-amd64.img -O $working_dir/jammy-server-cloudimg-amd64.img
qemu-img convert -p -f qcow2 -O raw $working_dir/jammy-server-cloudimg-amd64.img $working_dir/jammy-server-cloudimg-amd64.raw

# prep image
sudo virt-customize -a $working_dir/jammy-server-cloudimg-amd64.raw --root-password password:yourpass1

# start from here for reruns
cp -f $working_dir/jammy-server-cloudimg-amd64.raw $working_dir/ubuntu.test1.raw
sudo rm -f /tmp/cloud-hypervisor.mytest.sock
sudo rm -f /tmp/log.txt

# create vm manually via cloud-hypervisor
pushd $working_dir

sudo ./cloud-hypervisor --api-socket /tmp/cloud-hypervisor.mytest.sock \
        --cmdline "console=ttyS0 root=/dev/vda1 rw iommu=off" \
        --console off \
        --serial tty \
        --log-file /tmp/log.txt -v -v -v

# From second console:
# 4 core
working_dir=/tmp/chv_work
pushd $working_dir
sudo curl --unix-socket /tmp/cloud-hypervisor.mytest.sock -i \
 	-X PUT 'http://localhost/api/v1/vm.create'  \
 	-H 'Accept: application/json'               \
 	-H 'Content-Type: application/json'         \
 	-d '{
 		"cpus":{"boot_vcpus": 4, "max_vcpus": 4},
 		"memory":{"size": 1073741824, "shared": true},
 		"payload":{"kernel":"/tmp/chv_work/CLOUDHV.fd"},
 		"serial":{"mode":"Tty"},
 		"console":{"mode":"Off"},
 		"cmdline":{"args":"console=ttyS0"},
 		"disks":[{ "path":"/tmp/chv_work/ubuntu.test1.raw" }]
 		}'

sudo curl --unix-socket /tmp/cloud-hypervisor.mytest.sock -i -X PUT 'http://localhost/api/v1/vm.boot' -H 'Accept: application/json'
sudo chmod +r /tmp/log.txt

# Get info
sudo curl --unix-socket /tmp/cloud-hypervisor.mytest.sock -i \
     -X GET 'http://localhost/api/v1/vm.info' \
     -H 'Accept: application/json'

# to terminate, after finishing.
sudo kill -9 $(pidof cloud-hypervisor)

Changing the above

«cpus»:{«boot_vcpus»: 4, «max_vcpus»: 4},

to 2, results in successful boot.

«cpus»:{«boot_vcpus»: 2, «max_vcpus»: 2},

# 2 core
sudo curl --unix-socket /tmp/cloud-hypervisor.mytest.sock -i \
 	-X PUT 'http://localhost/api/v1/vm.create'  \
 	-H 'Accept: application/json'               \
 	-H 'Content-Type: application/json'         \
 	-d '{
 		"cpus":{"boot_vcpus": 2, "max_vcpus": 2},
 		"memory":{"size": 1073741824, "shared": true},
 		"payload":{"kernel":"/tmp/chv_work/CLOUDHV.fd"},
 		"serial":{"mode":"Tty"},
 		"console":{"mode":"Off"},
 		"cmdline":{"args":"console=ttyS0"},
 		"disks":[{ "path":"/tmp/chv_work/ubuntu.test1.raw" }]
 		}'

Guest OS version details:

Ubuntu 22.04 Jammy

Host OS version details:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

$ uname -r
5.15.0-71-generic

Logs

Output of cloud-hypervisor -v from either standard error or via --log-file:

Verbose log contents (with private build tracing added, tagged with MaxB, no other functional changes):

cloud-hypervisor: 26.365771s: <vmm> INFO:vmm/src/lib.rs:1788 -- API request event: VmCreate(Mutex { data: VmConfig { cpus: CpusConfig { boot_vcpus: 4, max_vcpus: 4, topology: None, kvm_hyperv: false, max_phys_bits: 46, affinity: None, features: CpuFeatures { amx: false } }, memory: MemoryConfig { size: 1073741824, mergeable: false, hotplug_method: Acpi, hotplug_size: None, hotplugged_size: None, shared: true, hugepages: false, hugepage_size: None, prefault: false, zones: None, thp: true }, payload: Some(PayloadConfig { firmware: None, kernel: Some("/tmp/chv_work/CLOUDHV.fd"), cmdline: None, initramfs: None }), disks: Some([DiskConfig { path: Some("/tmp/chv_work/ubuntu.test1.raw"), readonly: false, direct: false, iommu: false, num_queues: 1, queue_size: 128, vhost_user: false, vhost_socket: None, rate_limiter_config: None, id: None, disable_io_uring: false, pci_segment: 0 }]), net: None, rng: RngConfig { src: "/dev/urandom", iommu: false }, balloon: None, fs: None, pmem: None, serial: ConsoleConfig { file: None, mode: Tty, iommu: false }, console: ConsoleConfig { file: None, mode: Off, iommu: false }, devices: None, user_devices: None, vdpa: None, vsock: None, iommu: false, sgx_epc: None, numa: None, watchdog: false, platform: None, tpm: None, preserved_fds: None }, poisoned: false, .. }, Sender { .. })
cloud-hypervisor: 34.327148s: <vmm> INFO:vmm/src/lib.rs:1788 -- API request event: VmBoot(Sender { .. })
cloud-hypervisor: 34.327939s: <vmm> INFO:vmm/src/vm.rs:487 -- Booting VM from config: Mutex { data: VmConfig { cpus: CpusConfig { boot_vcpus: 4, max_vcpus: 4, topology: None, kvm_hyperv: false, max_phys_bits: 46, affinity: None, features: CpuFeatures { amx: false } }, memory: MemoryConfig { size: 1073741824, mergeable: false, hotplug_method: Acpi, hotplug_size: None, hotplugged_size: None, shared: true, hugepages: false, hugepage_size: None, prefault: false, zones: None, thp: true }, payload: Some(PayloadConfig { firmware: None, kernel: Some("/tmp/chv_work/CLOUDHV.fd"), cmdline: None, initramfs: None }), disks: Some([DiskConfig { path: Some("/tmp/chv_work/ubuntu.test1.raw"), readonly: false, direct: false, iommu: false, num_queues: 1, queue_size: 128, vhost_user: false, vhost_socket: None, rate_limiter_config: None, id: None, disable_io_uring: false, pci_segment: 0 }]), net: None, rng: RngConfig { src: "/dev/urandom", iommu: false }, balloon: None, fs: None, pmem: None, serial: ConsoleConfig { file: None, mode: Tty, iommu: false }, console: ConsoleConfig { file: None, mode: Off, iommu: false }, devices: None, user_devices: None, vdpa: None, vsock: None, iommu: false, sgx_epc: None, numa: None, watchdog: false, platform: None, tpm: None, preserved_fds: None }, poisoned: false, .. }
cloud-hypervisor: 34.328563s: <vmm> INFO:vmm/src/vm.rs:505 -- MaxB Creating Memory Manager
cloud-hypervisor: 34.328595s: <vmm> INFO:vmm/src/vm.rs:519 -- MaxB Creating CPU Manager
cloud-hypervisor: 34.328632s: <vmm> INFO:vmm/src/vm.rs:536 -- MaxB cpu_manager populate_cpuid
cloud-hypervisor: 34.328665s: <vmm> INFO:arch/src/x86_64/mod.rs:579 -- Generating guest CPUID for with physical address size: 46
cloud-hypervisor: 34.328084s: <payload_loader> INFO:vmm/src/vm.rs:941 -- Loading kernel
cloud-hypervisor: 34.328778s: <vmm> INFO:vmm/src/cpu.rs:766 -- Request to create new vCPUs: desired = 4, max = 4, allocated = 0, present = 0
cloud-hypervisor: 34.328863s: <vmm> INFO:vmm/src/cpu.rs:713 -- Creating vCPU: cpu_id = 0
cloud-hypervisor: 34.329170s: <vmm> INFO:vmm/src/cpu.rs:713 -- Creating vCPU: cpu_id = 1
cloud-hypervisor: 34.329264s: <vmm> INFO:vmm/src/cpu.rs:713 -- Creating vCPU: cpu_id = 2
cloud-hypervisor: 34.329357s: <vmm> INFO:vmm/src/cpu.rs:713 -- Creating vCPU: cpu_id = 3
cloud-hypervisor: 34.329526s: <vmm> INFO:vmm/src/pci_segment.rs:90 -- Adding PCI segment: id=0, PCI MMIO config address: 0xe8000000, device area [0x100000000-0x3ffeffffffff
cloud-hypervisor: 34.329585s: <vmm> INFO:vmm/src/vm.rs:593 -- MaxB device_manager create_devices
cloud-hypervisor: 34.329759s: <vmm> INFO:vmm/src/device_manager.rs:2163 -- Creating virtio-block device: DiskConfig { path: Some("/tmp/chv_work/ubuntu.test1.raw"), readonly: false, direct: false, iommu: false, num_queues: 1, queue_size: 128, vhost_user: false, vhost_socket: None, rate_limiter_config: None, id: Some("_disk0"), disable_io_uring: false, pci_segment: 0 }
cloud-hypervisor: 34.330020s: <vmm> INFO:vmm/src/device_manager.rs:2241 -- Using asynchronous RAW disk file (io_uring)
cloud-hypervisor: 34.330063s: <vmm> INFO:virtio-devices/src/block.rs:560 -- Disk topology: DiskTopology { logical_block_size: 512, physical_block_size: 512, minimum_io_size: 512, optimal_io_size: 0 }
cloud-hypervisor: 34.330135s: <vmm> INFO:vmm/src/device_manager.rs:2511 -- Creating virtio-rng device: RngConfig { src: "/dev/urandom", iommu: false }
cloud-hypervisor: 34.330320s: <vmm> INFO:vmm/src/vm.rs:621 -- MaxB saved_clock
cloud-hypervisor: 34.330373s: <vmm> INFO:vmm/src/vm.rs:636 -- MaxB finishing new_from_memory_manager
cloud-hypervisor: 34.330410s: <vmm> INFO:vmm/src/vm.rs:1946 -- Booting VM
cloud-hypervisor: 34.330799s: <vmm> INFO:vmm/src/acpi.rs:818 -- Generated ACPI tables: took 356µs size = 5423
cloud-hypervisor: 34.330863s: <vmm> INFO:vmm/src/vm.rs:1930 -- Created ACPI tables: rsdp_addr = 0xa0000
cloud-hypervisor: 34.332783s: <payload_loader> INFO:vmm/src/vm.rs:962 -- Kernel loaded: entry_addr = 0x4fffd0
cloud-hypervisor: 34.332894s: <vmm> INFO:vmm/src/vm.rs:1971 -- MaxB Creating vCPUs
cloud-hypervisor: 34.332938s: <vmm> INFO:vmm/src/cpu.rs:345 -- Configuring vCPU: cpu_id = 0
cloud-hypervisor: 34.333052s: <vmm> INFO:vmm/src/cpu.rs:345 -- Configuring vCPU: cpu_id = 1
cloud-hypervisor: 34.333127s: <vmm> INFO:vmm/src/cpu.rs:345 -- Configuring vCPU: cpu_id = 2
cloud-hypervisor: 34.333197s: <vmm> INFO:vmm/src/cpu.rs:345 -- Configuring vCPU: cpu_id = 3
cloud-hypervisor: 34.333266s: <vmm> INFO:vmm/src/vm.rs:1044 -- Configuring system
cloud-hypervisor: 34.333323s: <vmm> INFO:vmm/src/vm.rs:2033 -- MaxB Allocating memory_manager address space
cloud-hypervisor: 34.333357s: <vmm> INFO:vmm/src/memory_manager.rs:1560 -- Creating userspace mapping: 0 -> 7f8364000000 40000000, slot 0
cloud-hypervisor: 34.333577s: <vmm> INFO:vmm/src/memory_manager.rs:1608 -- Created userspace mapping: 0 -> 7f8364000000 40000000
cloud-hypervisor: 34.333623s: <vmm> INFO:vmm/src/cpu.rs:1089 -- Starting vCPUs: desired = 4, allocated = 4, present = 0, paused = false
cloud-hypervisor: 34.333701s: <vmm> INFO:vmm/src/cpu.rs:858 -- Starting vCPU: cpu_id = 0
cloud-hypervisor: 34.333815s: <vmm> INFO:vmm/src/cpu.rs:858 -- Starting vCPU: cpu_id = 1
cloud-hypervisor: 34.333934s: <vmm> INFO:vmm/src/cpu.rs:858 -- Starting vCPU: cpu_id = 2
cloud-hypervisor: 34.334034s: <vcpu0> INFO:vmm/src/cpu.rs:900 -- MaxB vCPU 0 is waiting for all CPUs to be ready
cloud-hypervisor: 34.334093s: <vmm> INFO:vmm/src/cpu.rs:858 -- Starting vCPU: cpu_id = 3
cloud-hypervisor: 34.334129s: <vcpu1> INFO:vmm/src/cpu.rs:900 -- MaxB vCPU 1 is waiting for all CPUs to be ready
cloud-hypervisor: 34.334187s: <vmm> INFO:vmm/src/cpu.rs:1104 -- MaxB vcpu_thread_barrier waiting
cloud-hypervisor: 34.334255s: <vcpu2> INFO:vmm/src/cpu.rs:900 -- MaxB vCPU 2 is waiting for all CPUs to be ready
cloud-hypervisor: 34.334428s: <vcpu3> INFO:vmm/src/cpu.rs:900 -- MaxB vCPU 3 is waiting for all CPUs to be ready
cloud-hypervisor: 34.334481s: <vcpu3> INFO:vmm/src/cpu.rs:902 -- MaxB vCPU 3 is starting
cloud-hypervisor: 34.334483s: <vcpu1> INFO:vmm/src/cpu.rs:902 -- MaxB vCPU 1 is starting
cloud-hypervisor: 34.334485s: <vmm> INFO:vmm/src/cpu.rs:1106 -- MaxB vcpu_thread_barrier released
cloud-hypervisor: 34.334487s: <vcpu0> INFO:vmm/src/cpu.rs:902 -- MaxB vCPU 0 is starting
cloud-hypervisor: 34.334487s: <vcpu2> INFO:vmm/src/cpu.rs:902 -- MaxB vCPU 2 is starting
cloud-hypervisor: 34.335144s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 0 4
cloud-hypervisor: 34.335238s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.335332s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 6 2
cloud-hypervisor: 34.335401s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.335469s: <vcpu0> INFO:vmm/src/vm.rs:411 -- Guest PIO write to unregistered address 0x21
cloud-hypervisor: 34.335512s: <vcpu0> INFO:vmm/src/vm.rs:411 -- Guest PIO write to unregistered address 0xa1
cloud-hypervisor: 34.427651s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 0 4
cloud-hypervisor: 34.427715s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.427750s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 6 2
cloud-hypervisor: 34.427784s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.427835s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 0 4
cloud-hypervisor: 34.427868s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.427902s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 6 2
cloud-hypervisor: 34.427935s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.428145s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 0 4
cloud-hypervisor: 34.428184s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.428218s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 6 2
cloud-hypervisor: 34.428251s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.428327s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 0 4
cloud-hypervisor: 34.428363s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4
cloud-hypervisor: 34.428397s: <vcpu0> INFO:pci/src/bus.rs:307 -- MaxB Entering PciConfigIo read 3320 6 2
cloud-hypervisor: 34.428430s: <vcpu0> INFO:pci/src/bus.rs:334 -- MaxB Entering PciConfigIo write 3320 0 4

Linux kernel output:
N/A

Источник

Понравилась статья? Поделить с друзьями:
  • X64 exception type 00000000000006 вылетает ошибка
  • X trail код ошибки p1320 nissan
  • Xbox 360 ошибка e64 горит красным
  • X4 foundations ошибка exitcode 212
  • Wsus код ошибки 80131509