Hot answers tagged virtual-machines
As you correctly state, all Azure disk storage (except for temporary disks) are replicated 3 times in the same DC, and if you use geo replication than another 3 times in another DC, so realistically disk failure is an unlikely cause. There are a few reasons I could think of that might explain this: As HopelesNoob mention, it could be data corruption, if ...
The maximum disk size is typically limited by the amount of free space available on the datastore that holds the VM. Check the free space on the datastore. If it is full try to move the VM to another datastore (that has more space) or move other VMs that are on the same datastore to somewhere else to free up space.
The problem was due to the machine being cloned. Remote Desktop has a certificate associated with it. That certificate has the machine name within it. If the machine name in the certificate does not match the current machine name, Remote Desktop will not run. To solve this problem: Run the Certificate Manager ( certlm.msc ). Navigate to Remote Desktop -> ...
You can switch to another console, log in to a new session, and then kill the ping process running in the first console. To switch consoles, just press Alt while pressing the left or right arrow keys. This take me through 6 different consoles.
Do you think 2 VMs on a SATA RAID 1 will allow a flawless symultanous usage of two somehow "desktop" virtual machines? It'll work fine though I'd need to understand your definition of 'flawless', and yes I would go with the HW RAID controller rather than just two disks to protect your data, make sure you get one that's on VMware's HCL so there'll be ...
I think there is no solution out-of-the-box for doing that for SQL Azure that you may configure between a virtual machine and SQL Azure instances that will route the request according to the IP/whatever. There is the Azure Traffic Manager service that you may use for that job, and best practices for that list some sentence about SQL Azure that basically is ...
I want to sync files from serverA to serverB, but there's no direct connection between them, but I have serverC that can access both serverA and serverB. what worked for me is: on serverC: ssh user@serverA 'rsync -avP -e "ssh -ax user@serverC ssh " /source/files user@serverB:/des/tination'
In a general sense I suspect MTU (frame size) is the root of the problem. I have a few reasons and a few suggestions. First, this behavior varies by L2 (it only happens with the wired traffic as opposed to wireless). That in itself is suspicious and suggests that there is a problem at the interface level. Second, packet fragmentation is a symptom of MTU ...
I raised a ticket with Microsoft and they confirmed that the SQL Express version number caused the problem. Their response was: the product team has confirmed that the "SQL Server 2014 SP1 Express on Windows Server 2012 R2" image was wrongly built by an internal builds (12.0.4193.9). I am not sure when they will have it fixed. As a workaround I ...
Only top voted, non community-wiki answers of a minimum length are eligible