Support and News Forum

Hi,

I added windows server 2008 and 2012 following the instructions (add a disk, rename the iso to cdrom.iso, ...)
But, it does not start and does not go blue. It just says started and nothing happens. Double click on it and again says start or stop and ../ No console appears and nothing happens.

Latest community version installed as a VM on ESXi 6.7

any idea?

Regards,

it can mean only one, image is not prepared properly
or your EVE has not enabled virtualization..

type in eve cli
kvm-ok

if it is saying enabled, then your image is made wrong

Hi,

INFO: /dev/kvm exists
KVM acceleration can be used
root@eve-ng:/opt/unetlab/addons/qemu/winserver-2012R2#


I just installed a windows O.S. by that image. I just copied it into eve and changed it to cdrom.iso, created a disk and ...

I also tested this with a healthy 2008 R2 image.

any other considerations?

any specific image should I use?

and how big virtioa.qcow2 you created for winserver
??
with just cdrom.iso loaded in winserver folder is not not enough

5. Create a new virtual harddisk named virtioa.qcow2. Size you can choose per your needs. This example is used 60Gb HDD.

/opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 60G

https://www.eve-ng.net/index.php/docume ... n-the-eve/

I certainly did that and created a 40G and then a 60G disk using " /opt/qemu/bin/qemu-img create -f qcow2 virtioa.qcow2 60G" though as of creation it takes a very limited space. Here is a ls from that directory:

total 4436040
drwxr-xr-x 2 root root 4096 Mar 17 21:44 .
drwxr-xr-x 7 root root 4096 Mar 17 19:47 ..
-rw-r--r-- 1 root root 4542291968 Mar 17 20:31 cdrom.iso
-rw-r--r-- 1 root root 197632 Mar 17 21:44 virtioa.qcow2

I just installed a windows O.S. by that image. I just copied it into eve and changed it to cdrom.iso, created a disk and ... 9apps get-cartoonhd.com

Same issue here.
EVE-NG CE installed as OVF (the latest one).
Using the Server2016 ISO (changed the name to cdrom.iso), created 60G virtual hdd.
When I start the machine, I get a success notification, the node doesn't turn blue and I can't VNC to the node.

This happened to me yesterday. My devices were working fine. I did do the update/upgrade process. Thats the only thing I did different that I can recall. My community version works fine. I had had three different Windows devices installed and they all stopped working.

wipe your win node and start