19. Setup Guides

This chapter provides specific setup guides and troubleshooting for the different GSM appliances:

19.1. GSM 5400/6500

This setup guide will show the steps required to put a GSM 5400 or 6500 appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
Power supply (2 connectors)  
Serial console cable/USB converter  
Putty/screen setup  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Web administrator account  
SSL certificate  
Readiness  

19.1.1. Installing the Appliance

The GSM 5400 and GSM 6500 are 19” mountable and require two rack units (RU). For installation in a 19” this equipment comes with the respective racking brackets.

For cabling GSM 5400 and GSM 6500 appliances have corresponding connectors at the front and back:

  • Front:
    • Keyboard via USB
    • 2 management Ethernet network ports, labeled “MGMT”
    • 1 RS-232 console port (|O|O|O), Cisco compatible, suitable cable is enclosed
    • 2 USB 2.0 ports
    • Up to 4 network modules with additional ports (Ethernet, SFP, SFP+ or XFP)
  • Back:
    • 2 power supplies
    • 2 USB 2.0 ports
    • 2 USB 3.0 ports
    • 1 VGA port

For the installation a terminal application and a console cable for establishing a connection have to be used.

19.1.2. Utilizing the Serial Port

The enclosed console cable is used for utilizing the serial port. Alternatively, a blue Cisco console cable (rollover cable) can be used.

To access the serial port a terminal application is required. The application needs to be configured to a speed of 9600 bits/s (Baud).

In Linux the command screen can be used in the command line. It is sufficient to run the command providing the serial port.

Tip

When starting a command, it may be necessary to hit Return several times to get a command prompt.

screen /dev/ttyS0  #(for serial port)
screen /dev/ttyUSB0 #(for USB adapter)

Note

Sometimes the first serial port does not work.

Experiment with the number (0, 1 or 2).

Quit the command by entering CTRL-a \.

In Microsoft Windows the Putty application can be used. After starting it, the options as shown in figure Setting up the serial port in Putty and the appropriate serial port have to be selected.

_images/putty-serial.png

Setting up the serial port in Putty

19.1.3. Starting the Appliance

Once the appliance is fully wired, a connection to the appliance using the console cable is achieved and the terminal application (Putty, screen or similar) is set up, the appliance can be started.

The appliance will boot and after short time – depending on the exact model – the first messages will be displayed in the terminal application.

19.1.4. Performing a General System Setup

All GSM appliances share the same way of basic configuration and readiness check.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System. Afterwards, continue with logging into the web interface.

19.1.5. Logging into the Web Interface

The main interface of the GSM is the web interface. The web interface can be accessed as follows:

  1. Open the web browser.

  2. Enter the IP address of the web interface of the GSM.

    Tip

    The IP address of the GSM is displayed on the login prompt of the console or in the GOS administration menu after selecting About and pressing Enter.

  3. Log in using the web administrator created during the setup.

19.2. GSM 400/600/650

This setup guide shows the steps required to put a GSM 400, 600 or 650 appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
Power supply  
Serial console cable/USB converter  
Putty/screen setup  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Web administrator account  
SSL certificate  
Readiness  

19.2.1. Installing the Appliance

The GSM 400, GSM 600 and GSM 650 are 19” mountable and require one rack unit (RU). For installation in a 19” this equipment comes with the respective racking brackets.

For cabling GSM 400, GSM 600 and GSM 650 appliances have corresponding connectors at the front and back:

  • Front:
    • Keyboard via USB
    • Network port eth0
    • 1 RS-232 console port (|O|O|O), Cisco compatible, suitable cable is enclosed
  • Back:
    • 1 power supply
    • 1 VGA port
    • Keyboard via USB
    • Serial console

For the installation a terminal application and a console cable for establishing a connection have to be used.

19.2.2. Utilizing the Serial Port

The enclosed console cable is used for utilizing the serial port. Alternatively, a blue Cisco console cable (rollover cable) can be used.

To access the serial port a terminal application is required. The application needs to be configured to a speed of 9600 bits/s (Baud).

In Linux the command screen can be used in the command line. It is sufficient to run the command providing the serial port.

Tip

When starting a command, it may be necessary to hit Return several times to get a command prompt.

screen /dev/ttyS0  #(for serial port)
screen /dev/ttyUSB0 #(for USB adapter)

Note

Sometimes the first serial port does not work.

Experiment with the number (0, 1 or 2).

Quit the command by entering CTRL-a \.

In Microsoft Windows the Putty application can be used. After starting it, the options as shown in figure Setting up the serial port in Putty and the appropriate serial port have to be selected.

_images/putty-serial.png

Setting up the serial port in Putty

19.2.3. Starting the Appliance

Once the appliance is fully wired, a connection to the appliance using the console cable is achieved and the terminal application (Putty, screen or similar) is set up, the appliance can be started.

The appliance will boot and after short time – depending on the exact model – the first messages will be displayed in the terminal application.

19.2.4. Performing a General System Setup

All GSM appliances share the same way of basic configuration and readiness check.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System. Afterwards, continue with logging into the web interface.

19.2.5. Logging into the Web Interface

The main interface of the GSM is the web interface. The web interface can be accessed as follows:

  1. Open the web browser.

  2. Enter the IP address of the web interface of the GSM.

    Tip

    The IP address of the GSM is displayed on the login prompt of the console or in the GOS administration menu after selecting About and pressing Enter.

  3. Log in using the web administrator created during the setup.

19.3. GSM 150

This setup guide shows the steps required to put a GSM 150 appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
Power supply  
Serial console cable/USB converter  
Putty/screen setup  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Web administrator account  
SSL certificate  
Readiness  

19.3.1. Installing the Appliance

The GSM 150 is 19” mountable and requires one rack unit (RU). The optional RACKMOUNT150 kit provides the racking brackets for installing the appliance in a 19” rack.

For stand-alone appliances four self-sticking rubber pads have to be mounted on the corresponding bottom side embossments.

For cabling the GSM 150 appliance has corresponding connectors at the front and back:

  • Front
    • 1 RS-232 console port, Cisco compatible, suitable cable is enclosed
    • 2 USB 3.0 ports
    • 1 HDMI port
    • 4 Ethernet network ports
  • Back:
    • 1 Power supply +12V DC (one)

For the installation a terminal application and a serial cable for establishing a connection have to be used.

19.3.2. Utilizing the Serial Port

The enclosed console cable is used for utilizing the serial port. Alternatively, a blue Cisco console cable (rollover cable) can be used.

To access the serial port a terminal application is required. The application needs to be configured to a speed of 9600 bits/s (Baud).

In Linux the command screen can be used in the command line. It is sufficient to run the command providing the serial port.

Tip

When starting a command, it may be necessary to hit Return several times to get a command prompt.

screen /dev/ttyS0  #(for serial port)
screen /dev/ttyUSB0 #(for USB adapter)

Note

Sometimes the first serial port does not work.

Experiment with the number (0, 1 or 2).

Quit the command by entering CTRL-a \.

In Microsoft Windows the Putty application can be used. After starting it, the options as shown in figure Setting up the serial port in Putty and the appropriate serial port have to be selected.

_images/putty-serial.png

Setting up the serial port in Putty

19.3.3. Starting the Appliance

Once the appliance is fully wired, a connection to the appliance using the console cable is achieved and the terminal application (Putty, screen or similar) is set up, the appliance can be started.

The appliance will boot and after short time – depending on the exact model – the first messages will be displayed in the terminal application.

19.3.4. Performing a General System Setup

All GSM appliances share the same way of basic configuration and readiness check.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System. Afterwards, continue with logging into the web interface.

19.3.5. Logging into the Web Interface

The main interface of the GSM is the web interface. The web interface can be accessed as follows:

  1. Open the web browser.

  2. Enter the IP address of the web interface of the GSM.

    Tip

    The IP address of the GSM is displayed on the login prompt of the console or in the GOS administration menu after selecting About and pressing Enter.

  3. Log in using the web administrator created during the setup.

19.4. GSM 35

This setup guide shows the steps required to put a GSM 35 sensor appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
Power supply  
Serial console cable/USB converter  
Putty/screen setup  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Scan user account  
Master key download  
Sensor setup on the master  
Readiness  

19.4.1. Installing the Appliance

The GSM 35 is 19” mountable and requires one rack unit (RU). The optional RACKMOUNT35 kit provides the racking brackets for installing the appliance in a 19” rack.

For stand-alone appliances four self-sticking rubber pads have to be mounted on the corresponding bottom side embossments.

For cabling the GSM 35 appliance has corresponding connectors at the front and back:

  • Front
    • RS-232 console port, Cisco compatible, suitable cable is enclosed
    • 2 USB 3.0 ports
    • 1 HDMI port
    • 4 Ethernet network ports
  • Back:
    • 1 power supply +12V DC

For the installation a terminal application and a serial cable for establishing a connection have to be used.

19.4.2. Utilizing the Serial Port

The enclosed console cable is used for utilizing the serial port. Alternatively, a blue Cisco console cable (rollover cable) can be used.

To access the serial port a terminal application is required. The application needs to be configured to a speed of 9600 bits/s (Baud).

In Linux the command screen can be used in the command line. It is sufficient to run the command providing the serial port.

Tip

When starting a command, it may be necessary to hit Return several times to get a command prompt.

screen /dev/ttyS0  #(for serial port)
screen /dev/ttyUSB0 #(for USB adapter)

Note

Sometimes the first serial port does not work.

Experiment with the number (0, 1 or 2).

Quit the command by entering CTRL-a \.

In Microsoft Windows the Putty application can be used. After starting it, the options as shown in figure Setting up the serial port in Putty and the appropriate serial port have to be selected.

_images/putty-serial.png

Setting up the serial port in Putty

19.4.3. Starting the Appliance

Once the appliance is fully wired, a connection to the appliance using the console cable is achieved and the terminal application (Putty, screen or similar) is set up, the appliance can be started.

The appliance will boot and after short time – depending on the exact model – the first messages will be displayed in the terminal application.

19.4.4. Performing a General System Setup

All GSM appliances share the same basic configuration and readiness check.

However, since the GSM 35 is a dedicated sensor, some setup steps differ from those of other appliances:

  • A scan user account has to be created instead of a web administrator account.
  • The master key has to be exchanged with the sensor.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System.

Add the scan user account instead of a web administrator account. Afterwards, continue with the Chapter Master-Sensor Setup to exchange the keys with the master.

The GSM 35 sensor does not offer any web interface. The sensor is solely managed by the master. Logging into the sensor is possible by using the console and SSH from the master.

If the communication between master and sensor fails, the rule set of any internal firewall governing the network connection may be adjusted.

19.5. GSM 150V

This setup guide shows the steps required to put the GSM 150V appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
VMware ESXi installed  
Integrity verification (optional)  
Import of the OVA  
Resources: 2 CPUs, 8 GB RAM, 32 GB hard disk  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Web administrator account  
SSL certificate  
Readiness  

19.5.1. Setup Requirements

This section lists the requirements for successfully deploying the GSM 150V appliance. All requirements have to be met.

19.5.1.1. Resources

The virtual appliance requires at least the following resources:

  • 2 virtual CPUs
  • 8 GB RAM
  • 32 GB hard disk

19.5.1.2. Supported Hypervisor

While the GSM 150V can be run on various hypervisors, only VMware hypervisors are currently supported.

The GSM 150V is delivered in VM version 7 format.

For VMware ESXi/ESX version 5.1 or higher is required.

19.5.1.3. Verification of Integrity

Note

The integrity of the virtual appliance can be verified. On request the Greenbone Networks support provides an integrity checksum.

To request the checksum contact the Greenbone Networks support via e-mail (support@greenbone.net) including the subscription number.

The integrity checksum can be provided via phone or via support portal at https://support.greenbone.net. Specify the preferred channel in the e-mail.

The local verification of the checksum depends on the host operating system.

On Linux systems the following command for calculating the checksum for the GSM 150V can be used:

sha256sum GSM-150V-4.3.13-gsf201905271.ova

On Microsoft Windows systems an appropriate program has to be installed first.

Tip

Rehash may be used which can be found at http://rehash.sourceforge.net.

To calculate the checksum, use:

rehash.exe -none -sha256 C:\<path>\GSM-150V-4.3.13-gsf201905271.ova

If the checksum does not match the checksum provided by the Greenbone Network support, the virtual appliance has been modified and should not be used.

19.5.2. Deploying the Appliance

The GSM 150V is provided by Greenbone Networks in the Open Virtualization Appliance (OVA) format.

Each GSM 150V is activated using a unique subscription key.

Note

Cloning the GSM 150V and using several instances in parallel is not permitted because it can result in inconsistencies and unwanted side effects.

To deploy the GSM 150V, it has to be imported into the hypervisor of choice as follows:

Note

The example features VMware ESXi, but is also applicable for VMware vSphere.

  1. Install VMware ESXi for the current operating system.

  2. Open the web interface of the VMware ESXi instance and log in.

  3. Click create_register_vm Create / Register VM.

  4. Select Deploy a virtual machine from an OVF or OVA file and click Next (see figure Selecting the creation type).

    _images/25v-150v_setup_vmware_createvm.png

    Selecting the creation type

  5. Enter a name for the virtual machine in the input box and click Next.

  6. Click Click to select files or drag/drop, select the OVA file of the appliance and click Next.

  7. Select the storage location in which to store the virtual machine files and click Next.

  8. Adjust the deployment options as needed and click Next.

    Note

    The default deployment settings may be used.

  9. Check the configuration of the virtual machine (see figure Checking the configuration of the virtual machine).

    Tip

    Settings can be changed by clicking Back and adjusting them in the respective dialog.

    _images/25v-150v_setup_vmware_readycomplete.png

    Checking the configuration of the virtual machine

  10. Click Finish.

    → The appliance is imported. This can take up to 10 minutes.

    Important

    Do not refresh the browser while the virtual machine is being deployed.

    When the appliance is imported, it is displayed in the list Virtual Machines in the Navigator panel (see figure Imported virtual machine).

  11. Select the appliance in the list and click vm_poweron Power on.

    _images/25v-150v_setup_vmware_vms.png

    Imported virtual machine

19.5.3. Performing a General System Setup

All GSM appliances share the same way of basic configuration and readiness check.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System. Afterwards, continue with logging into the web interface.

19.5.4. Logging into the Web Interface

The main interface of the GSM is the web interface. The web interface can be accessed as follows:

  1. Open the web browser.

  2. Enter the IP address of the web interface of the GSM.

    Tip

    The IP address of the GSM is displayed on the login prompt of the console or in the GOS administration menu after selecting About and pressing Enter.

  3. Log in using the web administrator created during the setup.

19.6. GSM 25V

This setup guide will show the steps required to put the GSM 25V appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
VMware ESXi installed  
Integrity verification (optional)  
Import of the OVA  
Resources: 2 CPUs, 4 GB RAM, 16 GB hard disk  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Web administrator account  
Readiness  

19.6.1. Setup Requirements

This section lists the requirements for successfully deploying the GSM 25V appliance. All requirements have to be met.

19.6.1.1. Resources

The virtual appliance requires at least the following resources:

  • 2 virtual CPUs
  • 4 GB RAM
  • 16 GB hard disk

19.6.1.2. Supported Hypervisor

While the GSM 25V can be run on various hypervisors, only VMware hypervisors are currently supported.

The GSM 25V is delivered in VM version 7 format.

For VMware ESXi/ESX version 5.1 or higher is required.

19.6.1.3. Verification of Integrity

Note

The integrity of the virtual appliance can be verified. On request the Greenbone Networks support provides an integrity checksum.

To request the checksum contact the Greenbone Networks support via e-mail (support@greenbone.net) including the subscription number.

The integrity checksum can be provided via phone or via support portal at https://support.greenbone.net. Specify the preferred channel in the e-mail.

The local verification of the checksum depends on the host operating system.

On Linux systems the following command for calculating the checksum for the GSM 25V can be used:

sha256sum GSM-25V-4.3.13-gsf201905271.ova

On Microsoft Windows systems an appropriate program has to be installed first.

Tip

Rehash may be used which can be found at http://rehash.sourceforge.net.

To calculate the checksum, use:

rehash.exe -none -sha256 C:\<path>\GSM-25V-4.3.13-gsf201905271.ova

If the checksum does not match the checksum provided by the Greenbone Network support, the virtual appliance has been modified and should not be used.

19.6.2. Deploying the Appliance

The GSM 25V is provided by Greenbone Networks in the Open Virtualization Appliance (OVA) format.

Each GSM 25V is activated using a unique subscription key.

Note

Cloning the GSM 25V and using several instances in parallel is not permitted because it can result in inconsistencies and unwanted side effects.

To deploy the GSM 25V, it has to be imported into the hypervisor of choice as follows:

Note

The example features VMware ESXi, but is also applicable for VMware vSphere.

  1. Install VMware ESXi for the current operating system.

  2. Open the web interface of the VMware ESXi instance and log in.

  3. Click create_register_vm Create / Register VM.

  4. Select Deploy a virtual machine from an OVF or OVA file and click Next (see figure Selecting the creation type).

    _images/25v-150v_setup_vmware_createvm.png

    Selecting the creation type

  5. Enter a name for the virtual machine in the input box and click Next.

  6. Click Click to select files or drag/drop, select the OVA file of the appliance and click Next.

  7. Select the storage location in which to store the virtual machine files and click Next.

  8. Adjust the deployment options as needed and click Next.

    Note

    The default deployment settings may be used.

  9. Check the configuration of the virtual machine (see figure Checking the configuration of the virtual machine).

    Tip

    Settings can be changed by clicking Back and adjusting them in the respective dialog.

    _images/25v-150v_setup_vmware_readycomplete.png

    Checking the configuration of the virtual machine

  10. Click Finish.

    → The appliance is imported. This can take up to 10 minutes.

    Important

    Do not refresh the browser while the virtual machine is being deployed.

    When the appliance is imported, it is displayed in the list Virtual Machines in the Navigator panel (see figure Imported virtual machine).

  11. Select the appliance in the list and click vm_poweron Power on.

    _images/25v-150v_setup_vmware_vms.png

    Imported virtual machine

19.6.3. Performing a General System Setup

All GSM appliances share the same basic configuration and readiness check.

However, since the GSM 25V is a dedicated sensor, some setup steps differ from those of other appliances:

  • A scan user account has to be created instead of a web administrator account.
  • The master key has to be exchanged with the sensor.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System.

Add the scan user account instead of a web administrator account. Afterwards, continue with the Chapter Master-Sensor Setup to exchange the keys with the master.

The GSM 25V sensor does not offer any web interface. The sensor is solely managed by the master. Logging into the sensor is possible by using the console and SSH from the master.

If the communication between master and sensor fails, the rule set of any internal firewall governing the network connection may be adjusted.

19.7. GSM ONE/MAVEN

This setup guide shows the steps required to put the GSM ONE/MAVEN appliance into operation.

The following checklist can be used to monitor the progress:

Step Done
VirtualBox installed  
Integrity verification (optional)  
Import of the OVA  
Resources: 2 CPUs, 4 GB RAM, 16 GB hard disk  
Keyboard layout  
IP address configuration  
DNS configuration  
Password change  
Web administrator account  
SSL certificate  
Readiness  

19.7.1. Setup Requirements

This section lists the requirements for successfully deploying the GSM ONE/MAVEN appliance. All requirements have to be met.

19.7.1.1. Resources

The virtual appliance requires at least the following resources:

  • 2 virtual CPUs
  • 4 GB RAM
  • 16 GB hard disk

19.7.1.2. Supported Hypervisor

While the GSM ONE/MAVEN can be run on various hypervisors, only the following two hypervisors are currently supported:

  • Oracle VirtualBox on GNU/Linux
  • Oracle VirtualBox on Microsoft Windows

19.7.1.3. Verification of Integrity

Note

The integrity of the virtual appliance can be verified. On request the Greenbone Networks support provides an integrity checksum.

To request the checksum contact the Greenbone Networks support via e-mail (support@greenbone.net) including the subscription number.

The integrity checksum can be provided via phone or via support portal at https://support.greenbone.net. Specify the preferred channel in the e-mail.

The local verification of the checksum depends on the host operating system.

On Linux systems the following command for calculating the checksum for the GSM ONE/MAVEN can be used:

sha256sum GSM-ONE-4.3.13-gsf201905271.ova
sha256sum GSM-MAVEN-4.3.13-gsf201905271.ova

On Microsoft Windows systems an appropriate program has to be installed first.

Tip

Rehash may be used which can be found at http://rehash.sourceforge.net.

To calculate the checksum, use:

rehash.exe -none -sha256 C:\<path>\GSM-ONE-4.3.13-gsf201905271.ova
rehash.exe -none -sha256 C:\<path>\GSM-MAVEN-4.3.13-gsf201905271.ova

If the checksum does not match the checksum provided by the Greenbone Network support, the virtual appliance has been modified and should not be used.

19.7.2. Deploying the Appliance

The GSM ONE/MAVEN is provided by Greenbone Networks in the Open Virtualization Appliance (OVA) format.

Each GSM ONE/MAVEN is activated using a unique subscription key.

Note

Cloning the GSM ONE/MAVEN and using several instances in parallel is not permitted because it can result in inconsistencies and unwanted side effects.

To deploy the GSM ONE/MAVEN, it has to be imported into the hypervisor of choice as follows:

  1. Install Oracle VirtualBox for the current operating system.

    Note

    VirtualBox is often included with Linux distributions.

    Should this not be the case and or a version of Microsoft Windows is used, VirtualBox is available at https://www.virtualbox.org/wiki/Downloads.

  2. Start VirtualBox.

  3. Select File > Import Appliance in the menu bar.

  4. Click import_vbox and select the OVA file of the appliance (see figure Importing the OVA file of the appliance).

    _images/vbox-import.png

    Importing the OVA file of the appliance

  5. Check the configuration of the virtual machine in the window Appliance settings (see figure Importing the OVA file of the appliance).

    Values can be changed by double clicking into the input box of the respective value.

    Note

    If possible, select 4096 MB RAM (memory) for optimal configuration of the virtual appliance.

  6. Click Import.

    → The appliance is imported. This can take up to 10 minutes.

    When the appliance is imported, it is displayed in the list Tools in VirtualBox.

  7. Select the appliance in the list and click Start.

19.7.3. Performing a General System Setup

All GSM appliances share the same way of basic configuration and readiness check.

Note

Follow the steps described in Chapter Managing the Greenbone Operating System. Afterwards, continue with logging into the web interface or with troubleshooting.

19.7.4. Logging into the Web Interface

The main interface of the GSM is the web interface. The web interface can be accessed as follows:

  1. Open the web browser.

  2. Enter the IP address of the web interface of the GSM.

    Tip

    The IP address of the GSM is displayed on the login prompt of the console or in the GOS administration menu after selecting About and pressing Enter.

  3. Log in using the web administrator created during the setup.

19.7.5. GSM ONE/MAVEN Troubleshooting

The following warnings and problems are known and depend on the environment:

  • On Linux host systems VirtualBox may warn during the import that the Host-I/O-Cache is activated if the virtual image is stored on a xfs partition. This warning is expected and can be accepted.

  • On Linux host systems the warning “Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)” is displayed if the virtual machine does not discover any network card.

    The network card within the VirtualBox hypervisor needs to be configured by clicking Settings and selecting Network. Usually the default can be accepted.

_images/vb-networkcard.png

Choosing the correct network card in VirtualBox

  • If the warning “AMD-V is disabled in the BIOS. (VERR_SVM_DISABLED).” is displayed, the option “VT-X/AMD-V” in the BIOS of the host has to be enabled.

    An alternative solution is disabling the acceleration in the system configuration of the virtual machine by clicking Settings and selecting System > Acceleration.

_images/vb-system.png

Disabling the hardware acceleration in VirtualBox