Re: Encrypting boot partition Libvirt not showing the OS booting up

On 10/13/2020 3:30 AM, Laine Stump wrote: > On 10/12/20 1:10 PM, john doe wrote: >> On 10/12/2020 5:14 PM, Michal Privoznik wrote: >>> On 10/12/20 4:27 PM, john doe wrote: >>>> On 10/12/2020 4:09 PM, Peter Krempa wrote: >>>>> On Mon, Oct 12, 2020 at 16:05:43 +0200, Michal Privoznik wrote: >>>>>> On 10/12/20 2:14 PM, john doe wrote: >>>>>>>> <snip/> >>>>>>> >>>>>>> I sent privately the requested xml file to 'Peter Krempa >>>>>>> <pkrempa(a)redhat.com&gt;&#39;. >>>>>>> Peter Krempa 's privately answered me back suggesting to add the >>>>>>> following in the domain xml file: >>>>>> >>>>>> Solving things privately doesn't help the community. >>>>> >>>>> Additionally it doesn't help solving the problem, since it's now >>>>> opaque >>>>> to others what the problem might be. >>>>> >>>>>>> >>>>>>> <bios useserial='yes'/> under <os> >>>>> >>>>> I've suggested this as the outputs I've got privately hinted that the >>>>> console (as in virsh console) didn't get to asking for the password, >>>>> while the manually-started-qemu did. >>>>> >>>>> Thus the problem actually doesn't have to do with encryption or >>>>> wahatver, but the console doesn't plainly work. >>>>> >>>>>>> >>>>>>> such as ... >>>>>>> >>>>>>>      <os> >>>>>>>        <type arch='x86_64' machine='pc-q35-3.1'>hvm</type> >>>>>>>        <boot dev='hd'/> >>>>>>>        <bios useserial='yes'/> >>>>>>>      </os> >>>>>>> >>>>>> >>>>>> Try adding: >>>>>> >>>>>>      <loader type='rom'>/usr/share/seabios/bios.bin</loader> >>> >>> Darn, this should have been sgabios: /usr/share/sgabios/sgabios.bin >>> but if your seabios is new enough (v1.11.0 and newer) then this is not >>> needed as seabios itself is capable of serial interface. And looking at >>> earlier e-mails in the thread you have v1.12.0-1 you you're good and >>> don't need to add <loader/> at all. >>> >>> But honestly, I don't know why you are not getting the console. >>> Could it >>> be that you are getting the console and the qemu is waiting for your >>> input, i.e. what happens if you type in the password? >>> >> >> Nothing happened at all if I try to type the password. >> Yes, so am I , I'm totaly lost on why it does not work. >> >> How can I find the command libvirt is passing to qemu? > > The qemu command issued by libvirt can be found at the end of > /etc/libvirt/qemu/${guestname}.log > Thank you, I have now isolated the command generated by libvirt. Starting this command from a script, a vnc server is started. Is libvirt internally using vnc connection?