This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
zvm-linux_notes_on_running_linux_under_z_vm [2020/12/21 17:30] prppedro ref |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Some notes on running Linux under z/VM ====== | ||
- | There' | ||
- | |||
- | ===== CPU's ===== | ||
- | |||
- | I won't lie to you: it's insufferably slow. And for a good reason: you are virtualising twice, and the first level (Hercules) has zero paravirt. as s390x is a completely different architecture. But, maybe -- I said //maybe// -- you can suffer less, giving the VM more CPU's. So, here's how it's done: | ||
- | |||
- | When creating the profile, you probably specified 4 max CPU's ('' | ||
- | |||
- | So, you take '' | ||
- | < | ||
- | vmcp define cpu 02 type cp | ||
- | </ | ||
- | |||
- | There are other types of CPU other than CP'' | ||
- | < | ||
- | CP | ||
- | indicates the central processor. | ||
- | IFL | ||
- | indicates the IBM® Integrated Facility for Linux. | ||
- | ZAAP | ||
- | indicates the IBM zEnterprise® Application Assist Processor. | ||
- | ZIIP | ||
- | indicates the IBM z Integrated Information Processor. | ||
- | ICF | ||
- | indicates the Internal Coupling Facility. | ||
- | </ | ||
- | |||
- | But CP is the general kind. And I don't think we should bother much about IFL or others when running z/VM inside an emulated mainframe. | ||
- | |||
- | Well, now your VM got a new CPU. It's offline, though: | ||
- | < | ||
- | vmcp q v cpus | ||
- | CPU 01 ID FF0288F728288000 CP | ||
- | CPU 02 ID FF0288F728288000 STOPPED CP | ||
- | [...] | ||
- | </ | ||
- | |||
- | Tell the guest to rescan for CPU's, by issuing '' | ||
- | |||
- | ===== References ===== | ||
- | |||
- | - {{ : | ||
- | - [[https:// | ||
- | - [[https:// |