| Summary: | Unknown credentials on local Hyper-V after first reboot | ||
|---|---|---|---|
| Product: | IPFire | Reporter: | xeonium <joergwendlandt+ipfire> |
| Component: | --- | Assignee: | Michael Tremer <michael.tremer> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | Crash | ||
| Priority: | Will affect almost no one | CC: | michael.tremer, peter.mueller |
| Version: | 2 | ||
| Hardware: | other | ||
| OS: | Windows | ||
| Attachments: | Screenshot 1st reboot | ||
It looks like I have added this problem last July in https://git.ipfire.org/?p=ipfire-2.x.git;a=commitdiff;h=b9021f9277e83b488c27c434ea6fee3c3d85490d. There is a function to detect whether IPFire is running on Azure or not which seems to go wrong on your Hyper-V system: https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=src/initscripts/system/functions;hb=HEAD#l809 I do not have access to a Hyper-V box, so I do not know how to change this to fix the function. (In reply to Michael Tremer from comment #1) > I do not have access to a Hyper-V box, so I do not know how to change this > to fix the function. This is no a problem for me. I have access to multiple Hyper-V host systems. Which information do you need? 'cat /sys/devices/virtual/dmi/id/*' Yes, I tried to Google what ways we have and could not find anything. We need a way to identify a Hyper-V installation that is *not* running on Azure. The DMI information might be a good start. Please do not forget to include the file names. Do you have access to a system on Azure, too? (In reply to Michael Tremer from comment #3) > Do you have access to a system on Azure, too? No sorry. respectively a free account. but it is very restricted with vm's on it. ...or i'm too stupid for that. Host1=Windows 10 Pro 1909 x64 /sys/devices/virtual/dmi/id/bios_date 12/07/2018 /sys/devices/virtual/dmi/id/board_serial 3332-0404-4679-1995-9011-0781-80 /sys/devices/virtual/dmi/id/uevent MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: /sys/devices/virtual/dmi/id/product_serial 3332-0404-4679-1995-9011-0781-80 /sys/devices/virtual/dmi/id/product_name Virtual Machine /sys/devices/virtual/dmi/id/chassis_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/chassis_asset_tag 3332-0404-4679-1995-9011-0781-80 /sys/devices/virtual/dmi/id/sys_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/bios_version 090008 /sys/devices/virtual/dmi/id/product_version 7.0 /sys/devices/virtual/dmi/id/board_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/chassis_version 7.0 /sys/devices/virtual/dmi/id/chassis_type 3 /sys/devices/virtual/dmi/id/chassis_serial 3332-0404-4679-1995-9011-0781-80 /sys/devices/virtual/dmi/id/product_uuid D1653375-0C17-9A4D-A084-858CBF12B26A /sys/devices/virtual/dmi/id/bios_vendor American Megatrends Inc. /sys/devices/virtual/dmi/id/board_version 7.0 /sys/devices/virtual/dmi/id/modalias dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachi ne:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: /sys/devices/virtual/dmi/id/board_name Virtual Machine ################################################################ Host2=Server 2016 Core x64 /sys/devices/virtual/dmi/id/bios_date 04/28/2016 /sys/devices/virtual/dmi/id/board_serial 0954-6577-4149-3742-7314-2811-91 /sys/devices/virtual/dmi/id/uevent MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr090006:bd04/28/2016:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: /sys/devices/virtual/dmi/id/product_serial 0954-6577-4149-3742-7314-2811-91 /sys/devices/virtual/dmi/id/product_name Virtual Machine /sys/devices/virtual/dmi/id/chassis_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/chassis_asset_tag 0954-6577-4149-3742-7314-2811-91 /sys/devices/virtual/dmi/id/sys_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/bios_version 090006 /sys/devices/virtual/dmi/id/product_version 7.0 /sys/devices/virtual/dmi/id/board_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/chassis_version 7.0 /sys/devices/virtual/dmi/id/chassis_type 3 /sys/devices/virtual/dmi/id/chassis_serial 0954-6577-4149-3742-7314-2811-91 /sys/devices/virtual/dmi/id/product_uuid C5E0AA9D-0638-B44C-9A34-AED4024E0904 /sys/devices/virtual/dmi/id/bios_vendor American Megatrends Inc. /sys/devices/virtual/dmi/id/board_version 7.0 /sys/devices/virtual/dmi/id/modalias dmi:bvnAmericanMegatrendsInc.:bvr090006:bd04/28/2016:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: /sys/devices/virtual/dmi/id/board_name Virtual Machine ################################################################ Host3 = Windows 10 Pro 1909 x64 /sys/devices/virtual/dmi/id/bios_date 12/07/2018 /sys/devices/virtual/dmi/id/board_serial 1579-8797-4647-6935-5994-7234-43 /sys/devices/virtual/dmi/id/uevent MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: /sys/devices/virtual/dmi/id/product_serial 1579-8797-4647-6935-5994-7234-43 /sys/devices/virtual/dmi/id/product_name Virtual Machine /sys/devices/virtual/dmi/id/chassis_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/chassis_asset_tag 1579-8797-4647-6935-5994-7234-43 /sys/devices/virtual/dmi/id/sys_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/bios_version 090008 /sys/devices/virtual/dmi/id/product_version 7.0 /sys/devices/virtual/dmi/id/board_vendor Microsoft Corporation /sys/devices/virtual/dmi/id/chassis_version 7.0 /sys/devices/virtual/dmi/id/chassis_type 3 /sys/devices/virtual/dmi/id/chassis_serial 1579-8797-4647-6935-5994-7234-43 /sys/devices/virtual/dmi/id/product_uuid 221D05F3-FC0D-204F-B6E2-21C93B2E831C /sys/devices/virtual/dmi/id/bios_vendor American Megatrends Inc. /sys/devices/virtual/dmi/id/board_version 7.0 /sys/devices/virtual/dmi/id/modalias dmi:bvnAmericanMegatrendsInc.:bvr090008:bd12/07/2018:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: /sys/devices/virtual/dmi/id/board_name Virtual Machine I have come to the conclusion that we cannot reliably detect this. So my proposed patch is as follows:
> https://patchwork.ipfire.org/patch/2709/
We will try to obtain a DHCP lease. If that is successful, everything is fine. If that is not successful we will continue with the standard boot operation.
If we got a lease, we will try to connect to the metadata service. If that is unsuccessful we will now abort walking through the script. That should always work.
It is not elegant and I consider this dangerous, but it works.
@Michael: I cannot find a commit where we shipped this change. Please investigate. :-) It definitely is in next so must have gone with 141 or earlier. |
Created attachment 728 [details] Screenshot 1st reboot I've installed core 138 from x86_64 iso into a VM. Host system is Windows 10 Pro 1909 x64. 1st setup boot (license agreement, partition scheme) works fine. During first reboot I see 'Importing Microsoft Azure configuration for instance'. A few seconds later boot completed and console is waiting for login(screenshot). Ctrl+C during 'Importing Microsoft Azure configuration for instance' boot run into pre setup(hostname, network configuration etc.) Changing the MAC vendor(of VM) does not solve the problem.