419 reputation
1819
bio website
location
age 41
visits member for 3 years, 5 months
seen Jan 12 at 16:34

Jan
10
comment iLO 3 Firmware Update (HP Proliant DL380 G7)
Thanks, I'll consider installing that (if I ever get it running for Ubuntu)
Jan
10
comment iLO 3 Firmware Update (HP Proliant DL380 G7)
Having Ubuntu as host OS, and being Ubuntu badly supported by HP, I doubt that I have any "Management Agent" (never heard of it) installed. I have just vanilla Ubuntu running. Anyway, just for upgrading the iLO firmware it is too much hassle to care about that many moving parts. Get .bin file, upload with web interface, and bum, iLO firmware upgraded. That easy!
Jan
10
comment iLO 3 Firmware Update (HP Proliant DL380 G7)
I have never used HP support before (which I am glad of), but now I see that Ubuntu is just second citizen for them. On the other hand, I have been running Ubuntu (10.04 and 12.04) for years without issues in this HP Proliant DL380 G7
Jan
10
comment iLO 3 Firmware Update (HP Proliant DL380 G7)
Yes it has! Successfully upgraded from 1.28 to 1.80! I'll post what I did for reference for others
Jan
10
comment iLO 3 Firmware Update (HP Proliant DL380 G7)
Thanks, I found it myself. The problem all along was that I was selecting my OS (Ubuntu 12.04) and apparently HP does not offer a firmware installer for Ubuntu. Now I have selected Red Hat and there it is: an installer (.scexe executable) which I can unpack. My confusion comes from the fact that I did not know what to expect, and that selecting my host OS was offering some downloads, but no firmware and no firmware installer. Now the iLO is updating, hopefully without problems.
Jan
10
comment iLO 3 Firmware Update (HP Proliant DL380 G7)
Thanks for your reply. I am connecting from a linux (Ubuntu) system. Do you have a link to an Ubuntu installer? Is there no direct link to the .bin firmware, which is (I presume) OS independent?
Oct
6
comment autossh does not kill ssh when link down
And after re-reading the autossh man page now I remember why I set -M 0: it is not easy to use a monitoring port, and it is indirectly discouraged: In many ways this may be a better solution than the monitoring port
Oct
6
comment autossh does not kill ssh when link down
Thanks, this makes sense. I indeed meant "client process", not server process.
Oct
2
comment connect: Network is unreachable
So, never mind, I was apparently lying. If I do: wlan off, eth off, eth on, the default gateway is set correctly. So you are right, it was a matter of two interfaces with a default gateway. But I am sure this has never caused a problem before. Somehow I have taken the interfaces out of the control of the OS (I have been playing with VMs and bridges lately), so it seems now the OS is not able to set the default gateway properly by itself, and needs some help.
Oct
2
comment connect: Network is unreachable
Sure, but I am turning off wlan and restarting eth0 (I do this because the wlan in my workplace is sometimes flaky, and I need a reliable connection to my servers for long-running tasks). This has worked fine for me in the past, but somehow now it is broken.
Oct
2
comment connect: Network is unreachable
Thanks, I have just got to that conclusion with the help of @faker. I wonder why I do not get a default gateway (eth0 is just setup with ` iface eth0 inet dhcp`)
Oct
2
comment connect: Network is unreachable
@faker: yes, I already realized about it comparing with the settings with wlan active. See my updated question.
Oct
2
comment connect: Network is unreachable
@faker: bingo! IPv4 is indeed broken: wget -4 just fails. I was not seeing the forest because of so many trees :). Thanks. Now I wonder if that is an issue with my interface configuration (I have indeed been playing with it recently) or if it has something to do with the network itself.
Oct
2
comment connect: Network is unreachable
That is a very good hint. I'll check that in a minute but ... how do you know that wget used IP6 from the output I pasted?
Oct
1
comment Access pty login prompt in VM
thanks!!! Defining the ttyS0 in the guest worked. Now I will be able to tweak the VM, even if network access is not working! If I could upvote you 10 times, I would do it!
Oct
1
comment Access pty login prompt in VM
For me hitting enter (repeteadly!) did not have any effect. My VM is not up now. but I will try this later and report. Thanks for the hint!
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.