vdisk cant be upgrade

Thanks for opening a separate report, however please provide details, screenshots (as appropriate), diagnostic.zip (as appropriate).  I realize you might have posted this stuff elsewhere and I realize your time is valuable.  However it's not all gathered together and it would save me a lot time trying to figure what is the issue you are reporting.

here you go

brun3tte-diagnostics-20180320-2339.zip

Here is a description of your issue I think:

 

From VM manager click on the name of a stopped VM.  This brings up the "Disk Devices" section where all the attached vdisks are displayed.  Click on one of the Capacity sizes for a vdisk (rollover says "click to increase").

When you do this, the page scrolls back to the top, but if you scroll back down you can enter a number in the field, but after doing so and hitting enter, the page goes totally blank.  There is also a corresponding error message in the system log:
 

Mar 21 00:25:36 Test1 root: error: /VMs?subaction=disk-resize

Result is the vdisk size was not changed and you have to click Back in browser.

yes, so any fix for that error 

1 minute ago, ren88 said:

yes, so any fix for that error 

 

Workaround until we fix it is to use the fallocate shell command to extend the size of the vdisk file.

ok thanks, i will wait for the next update, but good work on the first beta of 6.5.1, so what command is to increase vdisk 

Edited March 21, 2018 by ren88

2 hours ago, ren88 said:

so what command is to increase vdisk 

 

fallocate -l xxG /path/to/vdisk.img

Replace xx with new size you want.

40 minutes ago, johnnie.black said:

 

fallocate -l xxG /path/to/vdisk.img

Replace xx with new size you want.

ok thanks 

i got this error = unexpected number of arguments

Paste here the command you're using

fallocate -l 100G /mnt/user/Windows 10/vdisk1.img

It's because of the space, use:

 

fallocate -l 100G "/mnt/user/Windows 10/vdisk1.img" 

 

i did that, type fallocate -l 100G "/mnt/user/Windows 10/vdisk1.img" and then enter = 

root@brun3tte:~#, is that a -L or a -1

 

Edited March 21, 2018 by ren88

34 minutes ago, ren88 said:

i did that, type fallocate -l 100G "/mnt/user/Windows 10/vdisk1.img" and then enter = 

root@brun3tte:~#, is that a -L or a -1

 

 

I believe it is an L for length (aka size), from the man page:

 

-l, --length length
              Specifies the length of the range, in bytes.

It's a lower case L, copy/past the code I posted above, there will be no output after typing it, just refresh the VM page and you'll see the new size.

ok but i got to shut off the vm first and paste it in the terminal commands, never mind i got it change = me an idiot, i was suppose to put fallocate -l 500G "/mnt/user/Windows 10/vdisk1.img"

Edited March 21, 2018 by ren88

the change works, but it doesnt see in windows 10 vm, its still 400GB when i try to open c drive, i tried the computer management 100GB unallocated is not showing = no 500GB 

 

On Windows 10 (and 8 ) you need to restart (not shutdown) the VM to detect the increased space.

ok thanks 

1 hour ago, ren88 said:

the change works, but it doesnt see in windows 10 vm, its still 400GB when i try to open c drive, i tried the computer management 100GB unallocated is not showing = no 500GB 

 

 

Also need to go into windows disk manager and extend partition size.  But we are now getting beyond scope of this issue right?  And you could  have 'googled' fallocate command and learned all about it.

20 minutes ago, limetech said:

 

Also need to go into windows disk manager and extend partition size.  But we are now getting beyond scope of this issue right?  And you could  have 'googled' fallocate command and learned all about it.

ok thanks, i hope you fix this issue on the next update 

Changed Status to Solved

Changed Version to 6.5.1-rc2

I can confirm that this is resolved in 6.5.1-RC2