similar to: Bug#723656: xen-hypervisor-4.1-amd64: IPMI serial console hangs

I have this happening in Ubuntu precise also. When I upgraded from 12.04.1 to 12.04.4 it looks like my ipmi/serial/hvc0 console stopped working and the last message is: (XEN) Platform timer is 14.318MHz HPET From /etc/default/grub: GRUB_DEFAULT="Xen 4.1-amd64" GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo

Control: tag -1 moreinfo ISTR various supermicro fixes as well as serial stuff etc over the last few years. Please could you test with the Xen 4.4 currenty in Jessie? Ian.

I have a Dell PowerEdge SC1425 server and I installed Xen with Debian on it. When I plug the power in, I''m able to access the server via IPMI. After I start the machine, IPMI is still available. But when I command a shutdown on dom0, it will go down and say "Power down", stay there and IPMI is not available anymore. Only after I remove the power cord and replug it is the

Hello! I'm trying to install Centos 6.4 64 bit on this Xserve: http://www.everymac.com/systems/apple/xserve/specs/xserve-intel-xeon-2.8-eight-core-specs.html I got a bootloader from: http://blog.christophersmart.com/2009/07/23/linux-on-an-apple-xserve-efi-only-machine/ as none of the official Centos releases (full, minimal, network 64 bit) boot on this machine. They all crash when loading

Never used IPMI in my life and while I thought it was cool when I heard about it, had no plans to. Just built a home server (while out of town) using a SUPERMICRO MBD-X10SLM+-F-O I put an nVidia 405 based video card in it but it may be bad. When I power it on, I get some beeps but they are different than the no memory beeps (I intentionally powered on w/o memory to hear those) and I think

Well, we're figure the board's got problems, but I installed OpenIPMI a couple weeks ago, and fired it up as a service, then added a cron job. That all ran well until last evening; we came in to find 5 zillion emails complaining Unable to open SDR for reading I worked my way through logs, and googling, and then trying to run ipmitool by hand, and it complains there's no such device as

Hallo *! I have a board SE7501HG2. - On 2.6.18 ipmitool works succefull. On Xen-3.1 (2.6.18) ipmitool say: # ipmitool sensor WARNING: Unknown SDR repository version 0x00 SDR record id 0x0000: invalid length 0 (see thread [ipmitool-devel] Unknown SDR version) - On page [4] as written: ipmitool -> BMC ---> i2c/smbus ''-> SDR - On Thread [9] was written:

On 09/17/2016 04:11 AM, Mauricio Tavares wrote: > On Sat, Sep 17, 2016 at 6:25 AM, Alice Wonder <alice at domblogger.net> wrote: >> Never used IPMI in my life and while I thought it was cool when I heard >> about it, had no plans to. >> > Under many different names (Sun called it LOM; I forgot IBM's > name), this has been out there for a while. And it

This is that system with the missing management port, and I'm still fighting it. Everything *looks* right: 3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:25:90:0a:42:87 brd ff:ff:ff:ff:ff:ff inet 192.168.0.100/24 brd 192.168.0.255 scope global enp6s0 ip route 192.168.0.0/24 dev enp6s0 proto kernel scope link

Hi, I hope somebody can help me with this problem. I don't know whether it's a problem with my configuration or a bug or feature in extlinux. I am using an IPMI 2.0 serial-over-lan console to connect to a system with an Intel S3200SHL motherboard. The first line of my extlinux.conf file looks like this: serial 0 57600 0x003 I am using ipmitool to access the console, like so:

On 09/17/2016 09:15 PM, Keith Keller wrote: > On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: >> >> Okay if it requires DHCP this might be out, I'm currently out of town >> watching my brothers (various disabilities) while parents are on much >> needed vacation. Don't have easy physical access to the router, would >> have to take out

Hi Everyone, I have a dell 1750 server with ERA/O card running on FreeBSD 7.0-STABLE According to Dell, the ERA card supports ipmi 1.0: http://linux.dell.com/ipmi.shtml But so far no luck with freebsd :/ [root@home /usr/src/sys/i386/conf]# ipmitool -I open channel info 1 Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory

Greetings all, I am looking for a solution to use IPMI (BMC) in with LibVirt (Virt-Manager). Actually there is a Customer behind this request as well. Trying to be short: We are looking for a Solution in OpenStack Environment. Customer wants to have the entire environment running in Virt-Manager (probably for a P.O.C or tests purposes). So here is what he is trying to do: http://red.ht/1HfNn9r

Hi all I'm trying to get to grips with this one, but just can't figure it out. I recently acquired some 2nd hand Dell Poweredge 860 servers, and noticed that they have built in remote management interfaces. So, I have setup one, and assigned an IP address to it, but have no idea on how to access it remotely. Google'ing for an answer didn't bring me more than general product

On Thu, Jul 12, 2018 at 07:27:58PM -0500, Chris Adams wrote: > > Default Gateway IP : 192.168.0.100 > > Default Gateway MAC : 00:25:90:0a:42:87 > > No, that does not look right. You have configured the gateway of the > IPMI to be the host OS side of the NIC. You can't do that... in a lot > of systems I've seen, the IPMI side of the NIC can't even

Is there a little setup display right on the box? Just asking because I have seen that on some boxes. Cheers, Boris. On Sun, Sep 18, 2016 at 12:15 AM, Keith Keller < kkeller at wombat.san-francisco.ca.us> wrote: > On 2016-09-17, Alice Wonder <alice at domblogger.net> wrote: > > > > Okay if it requires DHCP this might be out, I'm currently out of town > >

Hi Al, (FYI, I cc'ed the NUT developers list for info) 2011/6/30 Albert Chu <chu11 at llnl.gov> > Hi Arnaud, > > On Tue, 2011-06-28 at 12:19 -0700, Arnaud Quette wrote: > > Hi Al, > > > > 2011/6/28 Albert Chu <chu11 at llnl.gov> > > On Tue, 2011-06-28 at 02:28 -0700, Arnaud Quette wrote: > > (...) > > >

Package: xen-hypervisor-4.1-amd64 Version: 4.1.4-3+deb7u1 Package: xen-linux-system-amd64 Version: 3.2+46 Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Package: xenwatch Version: 0.5.4-3 Package: xenstore-utils Version: 4.1.4-3+deb7u1 Package: xen-tools Version: 4.3.1-1 I installed Debian 7 (amd64) in a HX5 blade server (IBM Bladecenter H) 32 GB RAM, 2 Intel Xeon SixCore 2.Ghz, Internal

Hi, Thanks for your help. On Mon, Nov 11, 2013 at 08:00:47PM -0800, H. Peter Anvin wrote: > There is no reason by Syslinux would reboot the system on a serial > disconnect. There could be a bug, of course; now, Syslinux 4.05 is > pretty old so unless you can reproduce this on a current version that > would be useful. I am using 4.05 because that's what's packaged in the

We have recently been asked to evaluate some computing machinery for a new project. This particular end user has very limited experience with the stated security requirements in a lights-out environment. Their primary work (as well as mine) in the past has been with very small, simple networks of desktop machines and a few servers with extremely limited access.? For the most part, their admins