Windows Server 2022 / Ubuntu 20.04, 22.04 / Processor compatibility mode / "can't allocate initrd"
Hi, I tried to create a new virtual machine on my upgraded window server (2019 -> 2022). Before the upgrade it worked fine with Ubuntu 20.04 linux virtual machines (gen 2). But now the boot stops with "can't allocate initrd". Disabling "Processor compatibility mode" helps, but blocks live migrations to different servers. Can't even boot a live disk. This happens on a System with a AMD Ryzen 5 3600 but not on a AMD Ryzen 7 5700G. Without quiet mode i got a kernel panic.ssh from hyper-v host to linux guest not working. Works perfectly from other machines. How to fix?
I have a linux guest with ssh enabled on a hyper-v host. Depending on the assigned vSwitch (Default or External), I can ssh into linux from hyper-v host but not from other systems, or I cannot ssh into linux from hyper-v host but I can from other systems. In both cases, linux can access the internet. host's IP address is 192.168.1.204. Other test machine's IP address is 192.168.1.7. Case 1: Linux on Default vSwitch, assigned address 172.23.174.5 ping from host to linux - works ssh from host to linux - works (as the network 172.23.160/20 is directly connected to host by the Hyper-V setup) ping from test to linux - will not work, since it is on another subnet ssh from test to linux - will not work, since it is on another subnet ping from linux to 8.8.8.8 - works Case 2: Linux on External vSwitch, assigned address 192.168.1.214 ping from host to linux - works!! ssh from host to linux - "Connection refused" <<<--- this is the culprit ping from test to linux - works ssh from test to linux - works ping from linux to 8.8.8.8 - works Obviously, I could go with Case 1 (NAT) and use port forwarding (netsh interface portproxy..) on the host. But I'd rather like to understand why Case 2 does not work. Especially why ping from host to linux works, but ssh does not. Any idea why this does not work and how to fix this? Dan
DNS suffix is added when using nslookup but not when using ping or browsing
Hi everyone, I am using Windows Server 2016, running DHCP and DNS. I have configured DHCP option 15 to add suffix "abc.de". In the DNS server, I've created a zone called "corp.abc.de" .Entries in that zone should be resolvable only by hostname. In theory, if I want to ping user.corp , this should be resolved as the FQDN user.corp.abc.de . example: Server config: A record: "user" inside the forwarding Lookup zone "corp.abc.de" Client machine: We run the below command that works nslookup user.corp Server: DC.corp.abc.de Address: 10.130.3.254 Name: user.corp.abc.de Address: 10.150.70.11 Then we rung the below command that should also work, but it doesn't. ping user.corp Ping request could not find host user.corp. Please check the name and try again. This however, works on Linux machines, but doesn't work on Windows or MAC. I've tried reinstalling the server (both with DC AD and without). After spending 2 days on this, I'm out of ideas. Any help will be highly appreciated.
