Windows 2016 Server VM crash Nothing in log


Recommended Posts

i have tried allocation 1 core and 2 gig of memory and the issue still persists

 

 

what happens is when i start the vm as its on windows loading screen it shutsdown (no warning or anything)

 

i have tryed multiple senarios

 

1 core 1 hyperthred

1 core only 2 gig of memory

8 cores 5 gig of memory

4 cores 2 gig and 4g of memory

 

but problem still exists (dont want to lose the vm as its my only working domain controller for my network (spent hours getting it working) (my backup server is on but not fully configured (forgot to migrate AD to it)

 

edit : got vms to work kinda of it keeps pausing and cant resume

titan-diagnostics-20161030-1214.zip

Link to comment

vdisk is located on the default domains share

 

/mnt/user/domains

 

share is set to perfer cache storage

 

vdisk size is 60gb (install is about 40gb in total)

 

Cache Drive = 120gb ssd

since the share is set to 'Prefer Cache' I would expect the vdisk to be on the cache disk.  Since the cache disk has almost no spare space and the vdisk is not yet the full size allowed then it is almost certain that new writes to the vdisk would fail and this could explain your problems.
Link to comment

You cache disk has less than 2GB free, that's probably your problem, free some space on it.

 

[name] => cache

            [device] => sdc

            [id] => Corsair_Force_3_SSD_12417914000014800186

            [rotational] => 0

            => 117220792

            [status] => DISK_OK

            [temp] => 30

            [numReads] => 64330

            [numWrites] => 203981

            [numErrors] => 0

            [format] => MBR: 4K-aligned

            [type] => Cache

            [comment] =>

            => green-on

            [exportable] => no

            [fsStatus] => Mounted

            [fsColor] => yellow-on

            [fsError] =>

            [fsType] => btrfs

            [fsSize] => 117220792

            [fsFree] => 1647504

            [spindownDelay] => -1

            [spinupGroup] => host4

            [deviceSb] => sdc1

            [idSb] => Corsair_Force_3_SSD_12417914000014800186

            [sizeSb] => 117220792

            [uuid] =>

Link to comment

There is always the chance that previous writes to the vdisk failed when it ran out of space and thisaahs resulted in the contents being corrupted/invalid. Windows would not understand not being able to write a disk that it thinks it has complete control off and may not handle failures well.  If that has happened you are probably going to need to recreate the VM from scratch.

Link to comment

ok i think i have fixed it

 

issue only happens when ever when i try to allocate more than 4.5 gig to the vm (in process of testing memory to see if fuality )

 

could the memory issue be why i cant allocate more than 4.5 to a vm (when i try qemu just says cant alocate memory) even though nothing else is running (only unraid witch only takes about 200mb or less (napkin math in bed for you) ??

 

will find out in a few hours as i need to go to a friends to fix his damm server (hyper-v) Pain in the Ass (might just change him to esxi and tell him to live with it

Link to comment

im using a hyper-v install with the 2016 template if you want i can send you my discord chat channel and we can talk ?

 

That sounds good. I'm new to the Windows Server game, so I may have some terminology mixed up causing some of the confusion. Shoot me a PM with the channel when you get a chance.

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
Reply to this topic...

×   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.