Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate qemu with palmetto-bmc machine model #498

Closed
amboar opened this issue Aug 8, 2016 · 5 comments
Closed

Integrate qemu with palmetto-bmc machine model #498

amboar opened this issue Aug 8, 2016 · 5 comments
Labels

Comments

@amboar
Copy link
Member

amboar commented Aug 8, 2016

Currently bitbake can cook up an image for a versatilepb to be be run under qemu for virtualised testing. This requires a number of differences (such as kernel configuration) to the ast2x00s, and so problems don't always reflect reality on hardware.

Integrate a newer qemu (at least 2.6.0) into openbmc via runqemu to load a palmetto-bmc machine instead of versatilepb.

@williamspatrick williamspatrick added this to the openBMC v2.0 Backlog milestone Aug 8, 2016
@williamspatrick
Copy link
Member

@amboar - Were you expecting to own this or someone else? The first part of qemu update should be a straight-forward .bbappend (or new .bb for the version) in meta-phosphor. The second part I think you were previously working on and we were having trouble figuring out how to mesh it with what was going on upstream in Yocto pertaining to QEMU.

@amboar
Copy link
Member Author

amboar commented Aug 8, 2016

@williamspatrick I still expect to do the work myself, however if anyone is keen to take it up I wouldn't mind! I added this as an issue to give it some visibility given that there has been some confusion in other issues with respect to test suite behaviour and differences in kernel configuration.

The first part of qemu update should be a straight-forward .bbappend (or new .bb for the version) in meta-phosphor. The second part I think you were previously working on and we were having trouble figuring out how to mesh it with what was going on upstream in Yocto pertaining to QEMU.

Not so much having trouble figuring it out, rather converging on a solution we both agreed was acceptable. I think we have a way forward with the patches that have stagnated on the openembedded-core list - the plan was to pick them up, polish them, send them upstream for inclusion and carry them in openbmc/openbmc in the mean time.

@williamspatrick
Copy link
Member

Ack. My wording isn't always the most precise. We are on the same page with respect to the upstream work.

@stale
Copy link

stale bot commented Mar 28, 2019

This issue has been automatically marked as stale because no activity has occurred in the last 6 months. It will be closed if no activity occurs in the next 30 days. If this issue should not be closed please add a comment. Thank you for your understanding and contributions.

@stale stale bot added the stale label Mar 28, 2019
@rfrandse rfrandse removed this from the IBM Backlog 2 milestone Mar 28, 2019
@stale stale bot removed the stale label Mar 28, 2019
@amboar
Copy link
Member Author

amboar commented Apr 2, 2019

Closing as a duplicate of #1057

@amboar amboar closed this as completed Apr 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants