This appendix collects together answers to a selection of Frequently Asked Questions that can be helpful in solving various issues with cOS Core running under Hyper-V.

Question Summary

1. The 2 hour cOS Core demo mode time limit has expired. What do I do?
2. Are upgrades of cOS Core done differently under Hyper-V?
3. How do I release the focus from the Hyper-V console window?
4. Do all virtual interfaces have to be configured as virtio NICs?
5. How do I manage multiple virtual firewalls?

Questions and Answers

1. The 2 hour cOS Core demo mode time limit has expired. What do I do?

cOS Core will not respond after it enters lockdown mode after 2 hours and will consume all the Hyper-V resources. In this situation, the Hyper-V virtual machine must be stopped and then restarted so that cOS Core restarts and enters a new 2 hour evaluation period.

2. Are upgrades of cOS Core done differently under Hyper-V?

No. cOS Core upgrades are performed under Hyper-V just as they would be in non-Hyper-V environments.

3. How do I release the focus from the Hyper-V console window?

Hyper-V keeps focus in the console window. To click outside the console window, press the key combination Ctrl-Alt .

4. Do all virtual interfaces have to be configured as virtio NICs?

Yes. cOS Core will not work with virtual interfaces that are not configured to use the virtio driver. Any added interfaces must have the Device model property set to virtio.

5. How do I manage multiple virtual firewalls?

The IP address of the management virtual Ethernet interface for cOS Core must be different for the different virtual firewalls running under a single hypervisor.