Date: Tue, 24 May 2022 12:26:31 +0000 From: Souradeep Chakrabarti <schakrabarti@microsoft.com> To: "arm@freebsd.org" <arm@freebsd.org>, "hacker@freebsd.org" <hacker@freebsd.org> Cc: Wei Hu <weh@microsoft.com> Subject: RE: unable to get virtual serial console for EFI Message-ID: <PSAP153MB0536353A03BF26D0F384842DCCD79@PSAP153MB0536.APCP153.PROD.OUTLOOK.COM> In-Reply-To: <PSAP153MB0536FC1FA3DA80BC228AEC6ECCD49@PSAP153MB0536.APCP153.PROD.OUTLOOK.COM> References: <PSAP153MB0536FC1FA3DA80BC228AEC6ECCD49@PSAP153MB0536.APCP153.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
--_000_PSAP153MB0536353A03BF26D0F384842DCCD79PSAP153MB0536APCP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, I am trying to get the virtual serial console to access via putty while boo= ting FreeBSD 13 arm64 bootonly on Hyper-V. Setting console=3D"efi" is not helping to have the virtual serial console a= ccess using putty for ARM64. It is before any kernel module loaded. I can get the loader output in vmconnect.exe but not in the putty. Though I can see VM is getting connected to Hyper-V virtual COM1 console. B= ut no output is coming to putty. I have following question : Any specific support from EFI firmware, is required for virtual serial to w= ork in EFI loader in this phase of loading? I can see FreeBSD EFI loader is able to read the ConInDev and ConOutDev var= iables. With set console=3D"efi" or set console=3D"comconsole,efi" or set console= =3D"efi" , nothing in getting redirected in putty in arm64. But in X86 that is not the problem. Without this debugging the bring up of FreeBSD on arm64 Hyper-V is quite di= fficult. Any help or pointers are really appreciated. Regards, Souradeep From: Souradeep Chakrabarti Sent: Monday, May 23, 2022 3:28 PM To: arm@freebsd.org Cc: Wei Hu <weh@microsoft.com> Subject: unable to get virtual serial console for EFI Hi, I am trying to get the virtual serial console to access via putty while boo= ting FreeBSD 13 arm64 bootonly on Hyper-V. Setting console=3D"efi" is not helping to have the virtual serial console a= ccess using putty for ARM64. It is before any kernel module loaded. I can get the loader output in vmconnect.exe but not in the putty. Though I can see VM is getting connected to Hyper-V virtual COM1 console. B= ut no output is coming to putty. I have following question : Any specific support from EFI firmware, is required for virtual serial to w= ork in EFI loader in this phase of loading? I can see FreeBSD EFI loader is able to read the ConInDev and ConOutDev var= iables. With set console=3D"efi" or set console=3D"comconsole,efi" or set console= =3D"efi" , nothing in getting redirected in putty in arm64. But in X86 that is not the problem. Without this debugging the bring up of FreeBSD on arm64 Hyper-V is quite di= fficult. Any help or pointers are really appreciated. Regards, Souradeep --_000_PSAP153MB0536353A03BF26D0F384842DCCD79PSAP153MB0536APCP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr= osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:= //www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"= > <meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;} p.MsoPlainText, li.MsoPlainText, div.MsoPlainText {mso-style-priority:99; mso-style-link:"Plain Text Char"; margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif; mso-fareast-language:EN-US;} span.PlainTextChar {mso-style-name:"Plain Text Char"; mso-style-priority:99; mso-style-link:"Plain Text"; font-family:"Calibri",sans-serif;} span.EmailStyle21 {mso-style-type:personal-reply; font-family:"Calibri",sans-serif; color:windowtext;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </head> <body lang=3D"EN-IN" link=3D"#0563C1" vlink=3D"#954F72" style=3D"word-wrap:= break-word"> <div class=3D"WordSection1"> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Hi,<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">I am trying to get the virtual serial console to acc= ess via putty while booting FreeBSD 13 arm64 bootonly on Hyper-V.<o:p></o:p= ></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoPlainText">Setting console=3D"efi" is not helping = to have the virtual serial console access using putty for ARM64. It is befo= re any kernel module loaded. <o:p></o:p></p> <p class=3D"MsoPlainText">I can get the loader output in vmconnect.exe but = not in the putty. <o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Though I can see VM is getting connected to Hyper= -V virtual COM1 console. But no output is coming to putty.<o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">I have following question :<o:p></o:p></p> <p class=3D"MsoPlainText">Any specific support from EFI firmware, is requir= ed for virtual serial to work in EFI loader in this phase of loading?<o:p><= /o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">I can see FreeBSD EFI loader is able to read the = ConInDev and ConOutDev variables.<o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">With set console=3D"efi" or set console= =3D"comconsole,efi" or set console=3D"efi" , noth= ing in getting redirected in putty in arm64.<o:p></o:p></p> <p class=3D"MsoPlainText">But in X86 that is not the problem.<o:p></o:p></p= > <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Without this debugging the bring up of FreeBSD on= arm64 Hyper-V is quite difficult. Any help or pointers are really apprecia= ted.<o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Regards,<o:p></o:p></p> <p class=3D"MsoPlainText">Souradeep<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <div> <div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm = 0cm 0cm"> <p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag= e:EN-IN">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language= :EN-IN"> Souradeep Chakrabarti <br> <b>Sent:</b> Monday, May 23, 2022 3:28 PM<br> <b>To:</b> arm@freebsd.org<br> <b>Cc:</b> Wei Hu <weh@microsoft.com><br> <b>Subject:</b> unable to get virtual serial console for EFI<o:p></o:p></sp= an></p> </div> </div> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoNormal">Hi,<o:p></o:p></p> <p class=3D"MsoNormal">I am trying to get the virtual serial console to acc= ess via putty while booting FreeBSD 13 arm64 bootonly on Hyper-V.<o:p></o:p= ></p> <p class=3D"MsoNormal"><o:p> </o:p></p> <p class=3D"MsoPlainText">Setting console=3D"efi" is not helping = to have the virtual serial console access using putty for ARM64. It is befo= re any kernel module loaded. <o:p></o:p></p> <p class=3D"MsoPlainText">I can get the loader output in vmconnect.exe but = not in the putty. <o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Though I can see VM is getting connected to Hyper= -V virtual COM1 console. But no output is coming to putty.<o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">I have following question :<o:p></o:p></p> <p class=3D"MsoPlainText">Any specific support from EFI firmware, is requir= ed for virtual serial to work in EFI loader in this phase of loading?<o:p><= /o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">I can see FreeBSD EFI loader is able to read the = ConInDev and ConOutDev variables.<o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">With set console=3D"efi" or set console= =3D"comconsole,efi" or set console=3D"efi" , noth= ing in getting redirected in putty in arm64.<o:p></o:p></p> <p class=3D"MsoPlainText">But in X86 that is not the problem.<o:p></o:p></p= > <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Without this debugging the bring up of FreeBSD on= arm64 Hyper-V is quite difficult. Any help or pointers are really apprecia= ted.<o:p></o:p></p> <p class=3D"MsoPlainText"><o:p> </o:p></p> <p class=3D"MsoPlainText">Regards,<o:p></o:p></p> <p class=3D"MsoPlainText">Souradeep<o:p></o:p></p> <p class=3D"MsoNormal"><o:p> </o:p></p> </div> </body> </html> --_000_PSAP153MB0536353A03BF26D0F384842DCCD79PSAP153MB0536APCP_--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PSAP153MB0536353A03BF26D0F384842DCCD79>