INACCESSIBLE_BOOT_DEVICE - Starten der VM nicht möglich

Oct 28, 2020
27
1
8
36
Guten Morgen,

ich habe eine Hyper-V Maschine in ein qcow2 umgewandelt und in Proxmox importiert.
Das ist keine Konfiguration meiner virtuellen Maschine:

Code:
#unused0%3A local%3A101/vm-101-disk-1.raw
agent: 1
args: -vnc 0.0.0.0:200,password=on
boot: order=ide0;ide2;net0
cores: 4
efidisk0: local:101/vm-101-disk-2.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: local:101/vm-101-disk-1.raw,cache=writeback,discard=on,size=128G
ide2: none,media=cdrom
machine: pc-q35-6.1
memory: 12288
meta: creation-qemu=6.1.1,ctime=1644307094
name: Gerneral
net0: virtio=82:57:1E:F7:E4:B1,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: win10
scsihw: virtio-scsi-pci
smbios1: uuid=ac37d29f-b257-46e2-914c-c28e341d9fcd
sockets: 1
tpmstate0: local:101/vm-101-disk-3.raw,size=4M,version=v2.0
vmgenid: 38317a19-37e8-42b7-9e1c-d40090b798b0

Wenn ich boote, sehe ich den Windows Loader und bekomme dann dieser Meldung:

1644466888929.png


Ich kann aber nicht erkennen, woran das Problem liegt.
Hat hier jemand eine Idee für mich.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!