Compatibility and Limits Matrix for version 4.0.0

Image	RAM	VCPU	Root	Drive 1	Drive 2	create	start	stop	reboot	migrate	Internal reboot
Ubuntu 16.04 HVM	4096	4	40	0	0
	4096	8	20	0	0
	2048	4	10	0	0
	512	1	10	0	0
Centos 7 HVM	512	1	10	0	0
	4096	8	20	0	0
	4096	4	40	0	0
	2048	4	10	0	0
	512	1	25	0	0
	1024	2	35	0	0
	2048	4	55	0	0
	4096	8	26	26	26
	4096	8	40	40	0
	4096	8	95	0	0
	8192	16	53	53	53
	8192	16	80	80	0
	8192	16	175	0	0
	16384	32	106	106	106
	16384	32	160	160	0
	16384	32	335	0	0
	142304	34	486	486	486
	142304	34	729	729	0
	142304	34	1459	0	0
Ubuntu 14.04 HVM	4096	4	40	0	0
	4096	8	20	0	0
	2048	4	10	0	0
	512	1	10	0	0
Windows 2012 HVM	4096	4	40	0	0
	4096	1	40	0	0
	8192	2	65	0	0
	16384	4	50	50	0
	16384	4	115	0	0
	32768	8	66	66	66
	32768	8	100	100	0
	32768	8	215	0	0
	65536	16	133	133	133
	65536	16	200	200	0
	65536	16	415	0	0
Ubuntu 18.04 HVM	4096	4	40	0	0
	4096	8	20	0	0
	2048	4	10	0	0
	512	2	5	0	0
	512	1	10	0	0
	512	1	5	0	0
Ubuntu 20.04 HVM	4096	4	40	0	0
	4096	8	20	0	0
	2048	4	10	0	0
	512	2	5	0	0
	512	1	10	0	0
	512	1	5	0	0
Windows 2016 HVM	4096	4	40	0	0
	142304	34	729	729	0
	142304	34	1459	0	0
Windows 10 HVM	4096	4	40	0	0
	142304	34	729	729	0
	142304	34	1459	0	0
Windows 19 HVM	8192	10	120	30	0
	53098	8	120	30	0

Warning

In some cases, a windows 2012 HVM instance may become unresponsive, following its forced shutdown. This is due to the filesystem changing into a “read-only”. In that case the filesystem needs to be repaired.