• 6.8.0 RC5 Windows 10 VM boot loop


    SpecFroce
    • Minor

    Hi! I recently managed to yank out my former cache drive that sat in a pool and format it for use in another system and in the process destroyed my old VMs. I have since focused on maintaining my docker containers and replaced the before-mentioned cache drive with another NVME drive that was larger.

     

    Now to the problem at hand: I´m trying to reinstall a VM and i´m having issues with the boot process. The BIOS image shows and the VM goes into a constant boot loop, and i cannot manually boot my downloaded Windows 10 ISO file to make a fresh install. Please see attached diagnostics.

     

    I updated to RC5 since i heard that it was better for VMs and had fixed the corruption bug in Plex and had better performance overall.

     

    Any help is greatly appreciated. Thanks in advance!

    tower-diagnostics-20191103-2104.zip




    User Feedback

    Recommended Comments

    Why do you suppose this is specifically an -rc5 issue? If you messed up and want help a better place would be in the general help forum.

    Link to comment
    Quote

     cannot manually boot my downloaded Windows 10 ISO file to make a fresh install.

    If you edit the VM and switch to xml view, you can change the boot order

        <disk type='file' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source file='/mnt/user/domains/Windows 10/vdisk1.img'/>
          <target dev='hdc' bus='virtio'/>
          <boot order='1'/>
          <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/Win10_1903_V1_Norwegian_x64.iso'/>
          <target dev='hda' bus='sata'/>
          <readonly/>
          <boot order='2'/>
          <address type='drive' controller='0' bus='0' target='0' unit='0'/>
        </disk>
        <disk type='file' device='cdrom'>
          <driver name='qemu' type='raw'/>
          <source file='/mnt/user/isos/virtio-win-0.1.160-1.iso'/>
          <target dev='hdb' bus='sata'/>
          <readonly/>
          <address type='drive' controller='0' bus='0' target='0' unit='1'/>
        </disk>

    Change the boot order for the cdrom to be 1, and the vdisk to be 2

     

    But, as to the boot loop, try only setting the VM to use a single core and see if that makes a difference temporarily

    Edited by Squid
    Link to comment


    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.