More on the latest variant of Petya/Petrwrap/Petyawrap ransomware outbreak here.
We'd love to hear about it! Click here to go to the product suggestion community
I just tried to boot the latest version (as of writing build: 16_05_2160) of XG firewall on a public Openstack cloud. I uploaded the qcow image and started the VM. The VM has 1GB of RAM and 32GB Disk.
The KVM hypervisor boots the image with 1 local disk for the OS to partition and no separate SWAP or extra DISK. After the boot procedure it errors after:
I can acces the console but no luck after that. This issue also exists in the firstboot question on the community forum but it does not work for the latest version i guess.
How can I boot this image with the correct swap size?
Could you increase the ram to 2GB and try again and the minimum requirement is 20 GB , as for the VM you could try using our recommended Virtual environment .
Virtual appliances provide the same functionality as the standard UTM hardware platform. You can install UTM v9 within the following virtual environments:
All supported VM platforms undergo QA testing to ensure installation from ISO image and proper operation. UTM performance in a VM environment can vary widely due to various hardware differences, allocated resources, type of storage, etc.
If you experience problems installing the UTM on a KVM, try the following steps:
Reference : http://sophos.com/kb/119230
In reply to Aditya Patel:
> Could you increase the ram to 2GB and try again and the minimum requirement is 20 GB , as for the VM you could try using our recommended Virtual environment .
Options when booting:
As you see i don't have an option to get a prompt to fill in: default no-kvmlock. Can you advise any more steps?