Jump to content
  • 6.9.0-beta25 Creation of New VM yields drive space of 0mb for client OS


    fmp4m
    • Minor

    I have attempted to install Linux VMs and Windows VMs.

    When creating I set 120-240GB depending on which I want at the time.

    Loading the Client OS Installer, selecting the created virtual hard drive - it shows no space available or partitionable.

    Vdisk.img = 56kb in size.

     

    I believe that the VM Creation tool is not provisioning QCow or raw drives space correctly.

     

    Image from WIn10 install post-driver installation shows the drive with zero space for easier clarity.

    UnraidBUG-Store.jpg



    User Feedback

    Recommended Comments

    Post a screenshot of the Add VM page right before you would hit the "create" button.

    Share this comment


    Link to comment
    Share on other sites
    jonathanm

    Posted (edited)

    @limetech, I can confirm for the listed options in the create VM screenshot of qcow that it indeed creates a very small sparse file in my b25 test install

     

    I'm torn about the urgent label, but I'm going to let it stand until reviewed by @bonienl and company.

     

    However, the sparse qcow file does indeed expand appropriately during install, so I failed to replicate the actual issue.

    Edited by jonathanm
    Updated

    Share this comment


    Link to comment
    Share on other sites

    Changed Status to Open

    Changed Priority to Minor

    Share this comment


    Link to comment
    Share on other sites

    Out of curiosity if you pick RAW instead of qcow, does the behavior go away?

    Share this comment


    Link to comment
    Share on other sites

    Sorry, thought I mentioned in the post,

    Either raw or qcow does the same for me.  On all 3 servers I tried.   Two Intel, one amd.

    Share this comment


    Link to comment
    Share on other sites

    Installing Arch seemed  to work ok, I'll try win10

    Share this comment


    Link to comment
    Share on other sites

    If you can't reproduce at your end, I can give you remote access to my machine.

    Share this comment


    Link to comment
    Share on other sites

    Do you see the vdisk image file in the share?  What size is it?

    Share this comment


    Link to comment
    Share on other sites

    On my servers 

    Vdisk1.img = 56kb in size.

     

    Share this comment


    Link to comment
    Share on other sites
    bonienl

    Posted (edited)

    6 hours ago, jonp said:

    Out of curiosity if you pick RAW instead of qcow, does the behavior go away?

    In my testing when RAW is selected, it creates a vdisk of the right size (120G)

    (I took the exact same settings as in the screenshot above)

     

    qcow gives a vdisk of 19 Kb (incorrect size).

    Edited by bonienl

    Share this comment


    Link to comment
    Share on other sites
    11 hours ago, bonienl said:

    qcow gives a vdisk of 19 Kb (incorrect size).

    That is probably correct.  qcow2 auto-expands as necessary.  With VM stopped you can navigate to where the vdisk image file is stored and type:

     

    qemu-img info vdisk1.img  # or whatever filename it is

     

    Should show the correct "virtual size".

    Share this comment


    Link to comment
    Share on other sites

    I can confirm the qcow file is indeed behaving correctly for me during the install process. Sorry for the initial alarm, I didn't go beyond getting the apparent size and allocated size for the created file, which obviously behaves quite differently than the raw file.

    Share this comment


    Link to comment
    Share on other sites

    To solve the issue of the OP, it is necessary to choose "virtio" as Primary vDisk Bus (instead of SATA)

     

    Share this comment


    Link to comment
    Share on other sites

    btw: I don't see the point at this time of using qcow2 format.  Even with raw, qemu will create a sparse file, and if the backing file system is btrfs you get snapshot and ref-copy capability.

    Share this comment


    Link to comment
    Share on other sites

    Using virtio instead of Sata did work for WIndows 10.  Using raw with linux worked.    Odd things,  but I can confirm I am good now.

    Share this comment


    Link to comment
    Share on other sites
    On 7/18/2020 at 9:02 PM, fmp4m said:

    Using virtio instead of Sata did work for WIndows 10.  Using raw with linux worked.    Odd things,  but I can confirm I am good now.

    Out of curiosity, how old is that installation media for Windows 10 that you're trying to use?  Can you try to download a new ISO from here (https://www.microsoft.com/en-us/software-download/windows10) and see if that works with SATA + QCOW2?  I just did this test and do not have the issue you have. 

    Share this comment


    Link to comment
    Share on other sites

    New ISO created out of the Media Creation Tool   -   Wanted to make sure it had all the latest patches.   I don't keep a cached copy.

    Share this comment


    Link to comment
    Share on other sites

    And your server wasn't getting close to running out of space on the storage where the vdisk was, correct?  This is just really odd that I can't recreate the original issue you were seeing.

    Share this comment


    Link to comment
    Share on other sites

    Hi JonP sorry for the delay,   I checked and no,  I have over 2TB available.  Cache was balanced and scrubbed.   I have no idea why it can't be recreated.   There may be something wrong with my setup - I've posted a couple issues that got worked through and a couple untouched in general, however I have had time-outs occur when updating dockers and dockers disappearing because of it, as well as really sluggish web gui responses in general.   Can't seem to nail it down at this point - and generic posts tend to yield no results.   Maybe its related to my system only?

    Share this comment


    Link to comment
    Share on other sites


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.