Can't set SUBUTAI_DISK more than 100 GB

[jadilet]

User configuraration parameter(vagrant-subutai.yml):

SUBUTAI_ENV: master
DISK_SIZE: 200

I did following commands:

vagrant init subutai/stretch-master
vagrant up 

I got following errors:

==> default: Disk size configured to 200GB, increasing 100GB default by 100GB.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Cloning VM...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'subutai/stretch-master' is up to date...
==> default: A newer version of the box 'subutai/stretch-master' for provider 'virtualbox' is
==> default: available! You currently have version '0'. The latest is version
==> default: '7.0.5'. Run `vagrant box update` to update.
==> default: Setting the name of the VM: virtualbox_default_1535694236659_48847
==> default: Fixed port collision for 22 => 2222. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Available bridged network interfaces:
1) br1
2) enp4s0
3) vptp1
4) vptp0
5) enp3s0
6) vmnet1
7) vmnet8
8) vptp2
==> default: When choosing an interface, it is usually the one that is
==> default: being used to connect to the internet.
    default: Which interface should the network bridge to? 1
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: bridged
==> default: Forwarding ports...
    default: 8443 (guest) => 10001 (host) (adapter 1)
    default: 22 (guest) => 2201 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2201
    default: SSH username: subutai
    default: SSH auth method: private key
    default: Warning: Connection reset. Retrying...
    default: 
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default: 
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
[default] No installation found.
Reading package lists...
Building dependency tree...
Reading state information...
dkms is already the newest version (2.3-2).
dkms set to manually installed.
linux-headers-4.9.0-8-amd64 is already the newest version (4.9.110-3+deb9u4).
linux-headers-4.9.0-8-amd64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /dev/loop0 is write-protected, mounting read-only
Installing Virtualbox Guest Additions 5.2.8 - guest version is unknown
Verifying archive integrity... All good.
Uncompressing VirtualBox 5.2.8 Guest Additions for Linux........
VirtualBox Guest Additions installer
Copying additional installer modules ...
Installing additional modules ...
VirtualBox Guest Additions: Building the VirtualBox Guest Additions kernel modules.
VirtualBox Guest Additions: Starting.
Unmounting Virtualbox Guest Additions ISO from: /mnt
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Mounting shared folders...
    default: /vagrant => /home/adilet/peer/virtualbox
==> default: Running provisioner: shell...
    default: Running: /tmp/vagrant-shell20180831-16867-1uq55e2.sh
    default: Added new virtual disk /dev/sdb
    default: The ZFS modules are not loaded.
    default: Try running '/sbin/modprobe zfs' as root to load them.
    default: The ZFS modules are not loaded.
    default: Try running '/sbin/modprobe zfs' as root to load them.
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

[Almansherov]

Followed the commands from above and successfully created VMs (two times):