Not able to add and run new virtual machine


New Member
Sep 19, 2019

I have installed:
proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve)
pve-manager: 6.0-4 (running version: 6.0-4/2a719255)

On a HPE DL 360 Gen 10 server:
CPU = 2 x Intel(R) Xeon(R) Bronze 3106 CPU @ 1.70GHz
RAM = 2 x 16G RDIMM
DISK = 2 x 1TB

- Unfortunately the HPE server is without HW RAID controller so I brought up a zfs soft RAID for 2 x 1TB HDDs

storage 63.1G 836G 120K /storage
storage/data 63.1G 836G 96K /storage/data
storage/data/backups 27.4G 836G 27.4G /storage/data/backups
storage/data/images 35.7G 836G 35.7G /storage/data/images
root@atm-pve:/dev/mapper# zpool status
pool: storage
state: ONLINE
scan: scrub repaired 0B in 0 days 00:15:02 with 0 errors on Sun Sep 8 00:39:04 2019

storage ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
sda ONLINE 0 0 0
sdb ONLINE 0 0 0

- Proxmox is installed on microSD class 10 UHS-I card
- I've installed a win server 2019 essential machine with params bellow:

OS Guest OS Microsoft Windows (10/2016)
CD image Your downloaded ISO
System Graphics card Default
SCSI Controller VirtIO SCSI
Qemu Agent Enabled
Hard Disk Bus/Device VirtIO Block (0)
Disk Size 200GB
Cache Write Back
CPU Sockets 1
Cores 4
Type host
Memory Memory 8192
Network Model VirtIO (paravirtualized)

- I've created a new machine for new windows server 2019 standard with same params above besides CPU = 2 cores, mem = 4096 and less disk

- When wanted to start second machine my Proxmox stucks with message bellow and was kicking me off from web and ssh

- however the WIN SERV 2019 ESSENTIAL was accessible and working fine

Sep 18 11:41:01 atm-pve kernel: [ 1833.996912] EXT4-fs warning (device dm-0): ext4_end_bio:323: I/O error 10 writing to inode 153586 (offset 0 size 4096 starting block 601570)
Sep 18 11:41:01 atm-pve kernel: [ 1833.996915] Buffer I/O error on device dm-0, logical block 601570

- Also a notice high kvm RAM usage

I had to delete newly created machine WIN SERV 2019 STANDARD and restore the WIN SERV 2019 ESSENTIAL from weekend backup to make the Proxmox work fine, because PVE doesn't want to start and run on with the current WIN SERV 2019 ESSENTIAL running version

Please help me to understand what can cause this issue and what I've miss in my Proxmox setup that is having such behavior, maybe resource allocation, maybe zfs file system is not at all suitable, maybe windows machine tune is missing ....
You're seeing a warning from the EXT4 module, which means it's coming from your root disk (since your HDDs are ZFS, not ext4 - also explains why your VM on your ZFS kept running). An I/O error usually indicates a broken disk, or in your case SD card.

It's strongly recommended to not install PVE on an SD card or flash drive, since the core is a regular Debian Linux and as such does quite a bit of IO on the root disk, even if your VMs are stored elsewhere.

If you don't have a backup of your root system, I'd advise to at least make external backups of your VMs and then cleanly reinstall PVE on a suitable disk (e.g. an SSD or hard disk).


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!