Server will not shut down
-
Could it be that I need to manually set the interface metric -- to force one to always be master?
-
Hrm. . .
Are you using the RDP connection option from within XenCenter to connect to these systems? (still investigating the shared resources item mentioned above.)
-
@DustinB3403 said in Server will not shut down:
Hrm. . .
Are you using the RDP connection option from within XenCenter to connect to these systems? (still investigating the shared resources item mentioned above.)
This is running on VMware.
We are connecting to them via RDP and the VMware console. Neither makes any difference.
-
@travisdh1 said in Server will not shut down:
Hrm, how did you create the clones?
SAN IOPS still solid?
That's a lot of CPU for VM machines, are you getting scheduling conflicts with processor time?
Those were the first things I thought of at least.
SAN IOPs are still good. We're barely even touching the SAN (this is a security camera system that's not in production yet).
-
@dafyre said in Server will not shut down:
@DustinB3403 said in Server will not shut down:
Hrm. . .
Are you using the RDP connection option from within XenCenter to connect to these systems? (still investigating the shared resources item mentioned above.)
This is running on VMware.
We are connecting to them via RDP and the VMware console. Neither makes any difference.
Yeah I realized I was a few minutes behind the ball after posting. So ignore me.
-
@dafyre said in Server will not shut down:
Got an oddball problem here... We are working on setting up several VM clones for a project here. Each VM will be connected to the same shared storage via iSCSI.
Under the hood, right? Via the datastore, not iSCSI connecting to the OS inside of the VM, right?
-
@dafyre said in Server will not shut down:
No, we don't have anything running on them yet. The iSCSI initiator service is the only thing that has been set up, and our usual disable IEC, and UAC type stuff.
Otherwise, it is a basic Server 2012 R2 install.
Why use iSCSI from inside of the VM?
-
Why 4 vCPU each? That seems excessive.
-
Given the setup, my inkling is that you have an issue with the iSCSI Initiator. The Microsoft iSCSI Initiator is known to be flaky and can easily be causing an issue. Both architecturally and practically due to the use of Windows it is standard practice to present SAN storage as a local drive via VMware to the VM rather than inside of the VM. VMware's handling of iSCSI is much more robust than Windows is, and you need only one connection per physical host rather than one per VM.
-
@JaredBusch said in Server will not shut down:
Why 4 vCPU each? That seems excessive.
Agreed. We don't expect the software to use that much, but we're building it to the specs that our vendor has requested.
-
@dafyre said in Server will not shut down:
@JaredBusch said in Server will not shut down:
Why 4 vCPU each? That seems excessive.
Agreed. We don't expect the software to use that much, but we're building it to the specs that our vendor has requested.
With virtualization that can cause performance problems. The vendor may be injecting a mistake here. Having more cores than are needed will degrade performance. And... can cause lockups in rare cases.
-
@scottalanmiller said in Server will not shut down:
@dafyre said in Server will not shut down:
No, we don't have anything running on them yet. The iSCSI initiator service is the only thing that has been set up, and our usual disable IEC, and UAC type stuff.
Otherwise, it is a basic Server 2012 R2 install.
Why use iSCSI from inside of the VM?
Because it works that way?
That's the way I would set it up. Although this time, I'm actually not the one who set up the master image. We're connecting to a SAN to store large amounts of video for security cameras.
-
@dafyre said in Server will not shut down:
Why use iSCSI from inside of the VM?
Because it works that way?
Well it doesn't work well that way and in this case, it's possible that it doesn't work at all
-
@dafyre said in Server will not shut down:
That's the way I would set it up. Although this time, I'm actually not the one who set up the master image. We're connecting to a SAN to store large amounts of video for security cameras.
I'm not questioning the SAN or the iSCSI. I'm questioning the configuration which is extremely complex and fragile compared to a more elegant, more modern configuration using VMware as designed.
-
@scottalanmiller said in Server will not shut down:
Given the setup, my inkling is that you have an issue with the iSCSI Initiator. The Microsoft iSCSI Initiator is known to be flaky and can easily be causing an issue. Both architecturally and practically due to the use of Windows it is standard practice to present SAN storage as a local drive via VMware to the VM rather than inside of the VM. VMware's handling of iSCSI is much more robust than Windows is, and you need only one connection per physical host rather than one per VM.
I've set up shared storage with VMware before, and IIRC, isn't there a limit on the size of the disk image that you can set up? Our VMware disk images would be ~20 TB each.
-
@dafyre said in Server will not shut down:
I've set up shared storage with VMware before, and IIRC, isn't there a limit on the size of the disk image that you can set up? Our VMware disk images would be ~20 TB each.
62TB
-
@scottalanmiller said in Server will not shut down:
@dafyre said in Server will not shut down:
I've set up shared storage with VMware before, and IIRC, isn't there a limit on the size of the disk image that you can set up? Our VMware disk images would be ~20 TB each.
62TB
Cool. I'll pass that info along and see if he wants to set it up that way.
-
@dafyre said in Server will not shut down:
@scottalanmiller said in Server will not shut down:
@dafyre said in Server will not shut down:
I've set up shared storage with VMware before, and IIRC, isn't there a limit on the size of the disk image that you can set up? Our VMware disk images would be ~20 TB each.
62TB
Cool. I'll pass that info along and see if he wants to set it up that way.
Assuming you are not on some ancient VMware. It's been that big for a while.
I would take a "moment" and make one VM or two that use the "direct to VMware" SAN method and test that and see if it fixes things. It simplifies your setup by quite a bit and would be better for the long term. It's more efficient to the SAN, so might be very good for your performance, too. And avoiding that Windows component is always worth it. Just makes things simpler and more abstracted - leveraging virtualization for what it is built for.
-
It might not be the issue, but it's a place to start.
-
@scottalanmiller said in Server will not shut down:
It might not be the issue, but it's a place to start.
Seems legit, lol.
I've done set ups using the iSCSI initiator before (I have two of them running here now -- Failover Clusters) and never had any problems at all. So something in this setup is the issue.
