KVM domain error

[hiyon-imu-463]

I'm trying to use Junos EVO 23.2R2-21 on CML 2.7, so I started a virtual machine using the information in the URL below.
However, I'm getting the following error and it won't start.
Do you know how to fix this?

https://github.com/billgraham5/cml-junos/blob/main/PTX.yaml

I've seen several similar posts, but they're not the same situation, so I'd appreciate any advice.

・error

PTX-0: Failed to start (Unable to start node: 84151a7f-b887-4edf-9516-02b485fa5cb3 KVM domain could not be started)

※EX
https://community.cisco.com/t5/%E3%83%A9%E3%82%A4%E3%82%BB%E3%83%B3%E3%82%B9/cisco-cml%E3%81%A7%E3%83%8E%E3%83%BC%E3%83%89%E3%81%AE%E8%B5%B7%E5%8B%95%E3%81%AB%E5%A4%B1%E6%95%97%E3%81%99%E3%82%8B/td-p/4603015

Cannot Start Cisco Devices in the web interface ----- Failed to start (Unable to start KVM node: 3529d124-a439-4774-b384-29883f26464a KVM domain could not be started)

Failed to start (Unable to start KVM node: 321cab22-615c-42c5-b618-c66d7f954a71 KVM domain could not be started)

[Torbjørn]

Since the git repo specifically lists 2.7 as functioning I am inclined to think there is either a problem with your CML deployment or the node image. Are you able to start other nodes? Have you verified the integrity of the image you are using?

[bigevilbeard]

I am guessing here after some digging around, but something are worth a try! In the YAML file

sim:
  linux_native:
    libvirt_domain_driver: kvm
    driver: server
    disk_driver: virtio
    ram: 8096
    cpus: 4
    cpu_limit: 100
    cpu_model: host-passthrough  <-- CHANGE THIS LINE
    nic_driver: virtio
...

You will have to delete and add again after this change, start again etc.... You could even remove this line from the YAML and i think CML will use its default CPU model.

See how that goes.

[hiyon-imu-463]

I tried to fix it as you suggested, but it didn't work.

[bigevilbeard]

The same error or another?

[hiyon-imu-463]

When I provided PTXc_yaml, the same KVM error occurred.

However, when I applied "vjunos-ptx-evo1 (1)" based on other information, I ended up in an infinite loop.
*Lab_at_Mon_11_55_AM-vjunos--ptx-evo1-0-serial0 (1)(log)

Has anyone been able to get current juniper images into CML? - Cisco Community

This situation leads me to wonder if Juniper PTX can be used with CML2.7?

[bigevilbeard]

On your txt file you have cpu_model: PTX10001-36MR, is that supported? Did you try cpu_model: host-passthrough?

[hiyon-imu-463]

① If cpu_model: had information, a kvm error occurred.
The error occurred in a kvm/Xid/infinite loop in CML 2.7.2, so
upgrading to 2.8.1 was successful.
*The same procedure was followed as in ① above.
Attached is the successful yaml.