qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Corey Minyard <minyard@acm.org>
To: RamakrishnaDeepak Battu <ramakrishnadeepak@gmail.com>
Cc: "openipmi-developer@lists.sourceforge.net"
	<openipmi-developer@lists.sourceforge.net>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cant make the IPMI simulator work, help needed.
Date: Thu, 04 Jun 2015 13:45:21 -0500	[thread overview]
Message-ID: <55709CC1.9000905@acm.org> (raw)
In-Reply-To: <CAJb9KbWkbLVHNefJYLzh0nRfNT1A4=jHeczEcpgXi5V-DQzVxg@mail.gmail.com>

This question is probably best destined for the openipmi mailing list,
not qemu, so I'll add that to the CC.

This work is still not completely there, so it will be changing, but it
should work as is.

On 06/02/2015 05:58 AM, RamakrishnaDeepak Battu wrote:
> Hi, 
>
> I am trying to simulate the IPMI simulator for test purposes  but was
> failing somehow.. 
> I see lot of help being given in this forum , especially Corey
> Minyard. Thank you.
> I am new to IPMI and QEMU, but followed the threads and was able to
> fix up to some point. Right now struck and not able to figure out .So
> reaching for you guys help.
>
> I compiled and installed  stable-2.2-ipmi Qemu branch, and new version
> of OpenIPMI.
> I am using the cirros image to boot up using the Qemu.
>
> My startcmd is as follows: 
>
> /usr/local/bin/qemu-system-x86_64 --enable-kvm  -nographic -net
> nic,model=e1000,macaddr=52:54:00:12:34:59 -net
> user,hostfwd=tcp::5555-10.0.2.15:22 -chardev
> socket,id=ipmi0,host=localhost,port=9002,reconnect=10 -device
> isa-ipmi,chardev=ipmi0,interface=bt,irq=5 -serial
> mon:tcp::9003,server,telnet,nowait -initrd
> /opt/cirros/cirros-0.3.4-x86_64-initramfs -kernel
> /opt/cirros/cirros-0.3.4-x86_64-kernel --append 'root=/dev/hda
> console=ttyS0,115200'
>

What happens when you run this by hand directly from the command line?

> When ran Qemu command alone on the console get this error: 
> qemu-system-x86_64: Unable to connect character device ipmi0: Error
> connecting to socket: Connection refused
>
> My BMC and lan.conf are  
> https://gist.github.com/bot11/5d33a14a1cba442b5ef2
> https://gist.github.com/bot11/3c385eea081609a8a7f4
>
> Once I ran the ipmi_sim command, I can see the bmc variables read from
> the emu file, but I dont see the qemu instance booted up.
> And when I ran the ipmitool , I am getting the following errors:
>
> [root@localhost~]# ipmitool -I lanplus -v  -H 127.0.0.1 -p 9002 -U
> ipmiusr power status                                                  
>                           Password:
> Get Auth Capabilities error
> Get Auth Capabilities error
> Error issuing Get Channel Authentication Capabilies request
> Error: Unable to establish IPMI v2 / RMCP+ session
> Unable to get Chassis Power Status
> ----
>

You have the IPMI port set to 623 in the lan.conf config.  You have the
VM interface on port 9002.  So you should use 623.

-corey

>
> This is where I am struck. Please suggest.
>
> Thanks,
> Ramakrishna.

  reply	other threads:[~2015-06-04 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-02 10:58 [Qemu-devel] Cant make the IPMI simulator work, help needed RamakrishnaDeepak Battu
2015-06-04 18:45 ` Corey Minyard [this message]
2015-06-08  5:24   ` RamakrishnaDeepak Battu
2015-06-09  2:21     ` Corey Minyard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55709CC1.9000905@acm.org \
    --to=minyard@acm.org \
    --cc=openipmi-developer@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.org \
    --cc=ramakrishnadeepak@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).