Archives

pob579

issues with assigning virtual adapter

Hi,

I upgrade HOST from 2012 to 2019.

Have some issues with networking…

I assigned static IP to the card in yellow…

Created 2 virt switches #54 VMs only.   #55 Manage

When attach any to VMs NIC, I get APIPA address.

What I am missing?

Thx.


— When you hit a wrong note its the next note that makes it good or bad. — Miles Davis

Read full post . . . .

getting error when assign static mac to vm

Server 2019 host (in Lab). One NIC.

I am trying to assign static mac to vm and get an error:

Failed to modify device "Synthetic Ethernet Port"

What to do?

Thx. 


— When you hit a wrong note its the next note that makes it good or bad. — Miles Davis

Read full post . . . .

problem with NAT

hi I need to create NAT network on Windows Server 2019 Hyper-V.

I following powershell  steps from here:

https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network

1. New-VMSwitch -SwitchName "SwitchName" -SwitchType Internal

2. PS C:> Get-NetAdapter

New-NetIPAddress -IPAddress 192.168.0.1 -PrefixLength
24 -InterfaceIndex 24

* I insert correct InterfaceIndex from Get-NetAdapter

3. on this command I get the error and don't know what to do.  Please help.

I understand that I have to assign static IP in VM without Default Gateway (?). But what the error means? What duplicate name it refers to?

New-NetNat -Name MyNATnetwork -InternalIPInterfaceAddressPrefix
192.168.0.0/24

My output:

PS C:UsersAdministrator> New-NetNat -Name MyNATnetwork -InternalIPInterfaceAddressPrefix 192.168.0.0/24
New-NetNat : You were not connected because a duplicate name exists on the network. If joining a domain, go to System
in Control Panel to change the computer name and try again. If joining a workgroup, choose another workgroup name.
At line:1 char:1
+ New-NetNat -Name MyNATnetwork -InternalIPInterfaceAddressPrefix 192.1 …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (MSFT_NetNat:root/StandardCimv2/MSFT_NetNat) [New-NetNat], CimException
    + FullyQualifiedErrorId : Windows System Error 52,New-NetNat


— When you hit a wrong note its the next note that makes it good or bad. — Miles Davis

Read full post . . . .

apply vs revert

revert and delete checkpoint are absolutely clear…

basically I can quickly test if my thinking about APPLY is correct:

revert will bring a VM to the state after a checkpoint was taking, removing all changes made after.

I understand that Apply save(apply) any changes made after checkpoint creation and it will not be reversible.

Correct?

Then if Delete checkpoint will be made this checkpoint (with Apply) will be merged to VM.


— When you hit a wrong note its the next note that makes it good or bad. — Miles Davis

Read full post . . . .

dynamicly expanding vhdx strange behaviour

Hi,

look please at a screenshot…

D: partition is on dedicated vhdx and set as dynamically expanding.

The strange thing I cannot explain:

1.The VHDX size is 100 GB

2. in Windows I have 39GB of free space

3. When in Hyper-V manager the Current file size is about whole 100GB

For example for partition C: on dedicated VHDX it correctly matches Windows free space and current file size.

The final result is that total VM folder size is influenced by 100GB current file size. So I am loosing 40GB.

Why it could happen? Should I convert the drive to gain back 40GB. It is not a static drive…

Thanks.


— When you hit a wrong note its the next note that makes it good or bad. — Miles Davis

Read full post . . . .

Go Que Newsroom Categories

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 40 bytes) in /home/content/36/8658336/html/goquecom/wp-includes/taxonomy.php on line 3363