484 reputation
2821
bio website
location
age 41
visits member for 3 years, 7 months
seen Mar 20 at 11:58

Oct
1
comment Access pty login prompt in VM
This looks promising. I will check if my guest has the tty defined (I thought this was standard). What worries me is this sentence: "note that username input works even if the login promt is not shown". If I do not get visual output, this is not really gonna help me: no use running commands on the VM if I get not output.
Oct
1
comment Access pty login prompt in VM
Not really. My VM is working fine, I do not use virt-manager, I do not want to use virt-manager. I just want to connect to the login prompt of the VM. Surely virt-manager is not a dependency of libvirt, correct? You can run VMs without virt-manager, with full functionality, correct? So, now that we have that cleared: how do I configure the VM to be able to connect with virsh console (or any other virsh command?) to the login prompt? I do not know it, and it seems you do not know it neither. Which is fine. Maybe somebody else knows it?
Oct
1
comment Access pty login prompt in VM
@MichaelHampton: As I said, no GUI: ImportError: No module named libvirt. virt-manager is broken in Ubuntu (actually, Mint)
Oct
1
comment Access pty login prompt in VM
Thanks, but no GUI.
Oct
1
asked Access pty login prompt in VM
Sep
30
comment Connect to the text console of a running VM
@dyasny: You got me! :) Yes, I am creating the VM with virt-install, which probably uses libvirt.
Sep
30
accepted Connect to the text console of a running VM
Sep
30
comment Connect to the text console of a running VM
Yes, it works. But I do not understand why, since I am not using virsh to manage this particular VM.
Sep
30
asked Connect to the text console of a running VM
Sep
10
comment autossh does not kill ssh when link down
I would say the name is confusing: this is not autossh, this is just a keep-process-alive. What is ssh specific about it? Just the fact that understands some command line parameters used by ssh?
Sep
10
comment autossh does not kill ssh when link down
@NikolaidisFotis: sure, sure, I will try that. This is an ssh parameter, so the question remains: why is autossh relying on ssh to do the far-end check. Shouldn't it do the far-end check itself? What if ssh has a bug and it does never die? I guess autossh is not really aware of anything related to ssh: it seems to be doing just a simple process monitoring, and relying on the process being controlled to die whenever it must die.
Sep
10
comment autossh does not kill ssh when link down
@NikolaidisFotis: which actually makes me think that ServerAliveCountMax is just too high?
Sep
10
comment autossh does not kill ssh when link down
@NikolaidisFotis: added relevant part of ssh config
Sep
10
revised autossh does not kill ssh when link down
added 828 characters in body
Sep
9
comment autossh does not kill ssh when link down
@NilsToedtmann: thanks, I'll give it a try. Is it easy to implement? Do you have any link to a good howto?
Sep
9
comment autossh does not kill ssh when link down
@NikolaidisFotis: the timeout is fine. It is ... timing out. But it does not do the right thing (imho) whenever the timeout kicks in, namely: verifying the far-end!
Sep
5
revised autossh does not kill ssh when link down
added 46 characters in body
Sep
5
asked autossh does not kill ssh when link down
Sep
5
comment autossh failed recreating a tunnel due to different timing
And the OP has just "complained" about a problem in autossh: it is not doing what is supposed to do, in a very specific case. The network is there, the ssh is broken, but autossh is not gracefully restarting it. That is a bug in autossh.
Sep
5
comment autossh failed recreating a tunnel due to different timing
And if the network is too bad, then autossh should keep trying until it can restablish the connection (eventually exponentially increasing the retry delay, to not cause network / cpu overload)