Tag Info

New answers tagged

0

Check the firewall (firewalld) on the F22 server and ensure that the ports are open. I would expect this to be part of the problem as by default these ports are unlikely to be opened. However, other things you may like to check Does routing need to be enable on the host and if so has it? Does the firewall on the host have to be opened and if so has it?


1

Just wanted to point out to official Microsoft KB about this: Virtual machines lose network connectivity when you use Broadcom NetXtreme 1-gigabit network adapters As I understand this VMQ thing not properly implemented in cheap NICs and as vendors tend to deliver drivers which are targeted to whole product family of NICs not for specific one (i.e. one ...


0

we're spamming network discovery with our VMs - What does that mean? Can you elaborate on that? we have to manually go in to each VM on creation, statically set the DNS to the TFS, join the test domain, reset to DHCP, and reboot the machine. - Why are you resetting them to DHCP? You should use static ip addresses on the test machines in order to: 1. Not ...


0

The Hyper-V machine that I've configured uses an External Virtual Switch that has a dynamic IP, but only when the box is initially brought up by "vagrant up" - if I destroy the box and remake, I get a new IP, but until then, it stays the same. Setting it up like this gives my host machine, and the VM internet access, and I can hit my vm from my host to ...


0

Maybe you can shrink the VHDx file directly from inside your virtual machine, by using TRIN/UNMAP from your guest. Simply try recreating a new partition inside your guest's free space, and format it. If all stars align correctly, it will free a significant amount of space, returning it to the host OS. Please note that the file will appear to have the same ...


0

I don't know why, but with DHCP networking it's running w/ gigabit speed. With static IP it got 100Mbits again. But it's working.


1

There are two ways to 'view' a virtual hard drive. You can see it on the host system as a vhd file and you can see it as you described from inside the virtual machine as an attached drive. From disk management inside the virtual machine you will see no difference between a fixed size disk and a dynamic disk. If you created a 70GB disk either fixed or ...


1

A dynamic VHD disk will not preallocate all the space on creation. It will expand its size as you use it, until it reaches the maximum size defined, or the available space on the host disk. If you create a 70GB disk, for instance, it will allocate a few GB and keep increasing the size until it reaches 70GB. It will stop growing on 70GB or when it exhausts ...


1

You had to resize the filesystem to let the added space be usable. Try booting with a Parted live cd and resize you filesystem, then retry the refresh process.


0

This is not a direct answer to your question, just a brief list of some potential alternatives. As others have said, if you don't have shared storage there's no point in having a failover cluster. You do have the option of shared-nothing live migration. You can freely move your virtual machines between hosts, provided you have the resources to do so, ...


0

Some form of shared storage is required in order to build a Hyper-V failover cluster; however, it doesn't necessarily have to be a SAN: any server acting as an iSCSI target will work fine, and Windows Server 2012 even introduced the possibility of using SMB shares to store VMs.


1

Windows Failover Clustering (which is what Hyper-V uses for clustering) requires shared storage of some sort. Further to Massimo's answer, and if I'm reading this page right, I don't think you can use exclusively SMB shares for a failover cluster. You'd still need some shared disks (SAS, iSCSI, FC) for the cluster portion, but you can store the Hyper-V VM ...


2

You could use Storage Spaces to create two pools; one for SSD and one for HDD and allow SS to migrate the data around based on its IO requirements. I know for a fact this works great in a file-services system, I've not tried it with HV but there's no reason to assume it won't.


2

Put the host OS on a partition on the standard HD. Leave some space on the standard HD for VM overflow... even if you can fit all of the VMs on the SSD right now, you need to expect some growth. Then put as much of the VM's as you can on the SSD. This may mean using multiple VHD's per VM, to separate the VM OS from the application hosted on that OS. If you ...


1

We've had issues in the past when virtual machines have consumed too much memory and the host has locked up. There is a way to reserve some memory for Hyper-V which might help you. This solved some problems for us. The registry path to use is explained here. It's a DWORD and should be specified in MB, for example 2048. ...


1

You can setup Performance Monitor to log memory used per process. Under available counters, scroll down to the Process object, expand it. Add Private Bytes, Working Set and Working Set-Private. Make sure to select so it would show you a breakdown per individual process instead of totals. That will show you the memory allocated per process and hopefully ...


4

For Windows guests you'd use Sysprep to generalize the VM that you're using as your template. I don't know if something similar exists for Linux. As for the MAC address, each cloned VM will have it's own unique MAC address, which is generated by Hyper-V so that shouldn't be an issue. As for the ip address, if you use DHCP to assign ip addresses then this ...


0

By default the standard Windows key combinations do not get sent to the virtual machine, unless you are in full screen mode. maximize the virtual machine console screen window and then click the action menu, ctrl-alt-del



Top 50 recent answers are included