propagate changes in template to existing node
Posted: Mon Nov 16, 2020 3:01 pm
Dear Eve-NG experts,
i have several question regarding template and node creation using qemu:
1. Can we change a template and then propagate the changes to existing node ?
2. if cannot, how can we ask eve to re-read template file to existing node (perhaps by right click and "reread" template) ?
3. can we modify individual qemu wrapper / qemu command ? lets say in templates it says "cpu = 1", and we modify some particular node qemu config and modify with " -smp 2" ?
4. where can we see error log of running qemu ? my nodes is started for a very shord period and then shutdown (probably because of template error). i checked file /opt/unetlab/data/Logs/unl_wrapper.txt but cannot see reasons why the node cannot started.
if using command line, for example :
"/opt/qemu-2.4.0/bin/qemu-system-x86_64 -d 0 -- -nographic -device e1000,netdev= ....", and the parameter is incorrect, qemu will tell the error and immediately exit. But at least we have got the error message and we can try fixing that.
thanks.
i have several question regarding template and node creation using qemu:
1. Can we change a template and then propagate the changes to existing node ?
2. if cannot, how can we ask eve to re-read template file to existing node (perhaps by right click and "reread" template) ?
3. can we modify individual qemu wrapper / qemu command ? lets say in templates it says "cpu = 1", and we modify some particular node qemu config and modify with " -smp 2" ?
4. where can we see error log of running qemu ? my nodes is started for a very shord period and then shutdown (probably because of template error). i checked file /opt/unetlab/data/Logs/unl_wrapper.txt but cannot see reasons why the node cannot started.
if using command line, for example :
"/opt/qemu-2.4.0/bin/qemu-system-x86_64 -d 0 -- -nographic -device e1000,netdev= ....", and the parameter is incorrect, qemu will tell the error and immediately exit. But at least we have got the error message and we can try fixing that.
thanks.