Hi Wayne, On 6/7/19 10:04 PM, Wayne wrote: > Hi Ralf, > > Thank you for your responses. I have attached the requested config > files. I am now just trying to use the same bzImage for the root and > the non-root linux node.
One question that you didn't answer: do apic-demo or tiny-demo work? They need to to have correct .console parameter set, so ensure that parameters are set if you run those demos in your linux-demo cell. Just compare it to tiny-demo.c or apic-demo.c > > Yes, I am using vanilla 4.16 because the documentation indicated that it > is the first mainline release to officially support Jailhouse Guest > images. Do you suggest that I use something else? As Jan already wrote: Try to use Siemens' 4.19 branch. > > Right now i'm just trying to get some serial output from the non-root > Linux. Hopefully, I have that configured correctly. Ideally, I would > like to share the same serial console for the Root node and non-root > node eventually if possible. I have been OK with using the virtual > console (jailhouse console -f) for the Hypervisor output. In addition to Jan's comment: Currently you only have access to the jailhouse console via 'jailhouse console' from your root cell. Imagine your root cell crashes for some reason. You will never see the fault reason, which makes things hard to debug. I would suggest to configure the hypervisor to use the serial console. You can share the device with the non-root Linux, that's no problem. In this case, the non-root kernel's output will always be printed to the serial console. Directly, if you choose console=ttySx, and indirectly via the hypervisor if you choose console=jailhouse. BTW: According to your config, your system is a PowerEdge, and the non-root cell gets both, 0x2f8 and 0x3f8. Are you sure that ttyS1 is the correct console that you are connected to? Just mentioning this as we have a similar machine here, and, afair, both platform serial device are 'usable', but one ends in the nirvana while it is accessible. Ah, and one last thing: try to switch to the current next branch for jailhouse. Jan just integrated a few patches from me that might also be relevant for your machine. HTH Ralf > > Wayne > > On Fri, Jun 7, 2019 at 9:10 AM Ralf Ramsauer > <[email protected] > <mailto:[email protected]>> wrote: > > Hi, > > On 6/7/19 2:28 PM, Wayne wrote: > > Hello, > > > > I am new to Linux development and Jailhouse. I have successfully > booted > > the Jailhouse Hypervisor and root cell on a bare metal X86 Linux > system > > (No QEMU). I am now trying to load a non-root Linux cell and I have a > > few questions. Jailhouse accepts and starts my non-root linux cell > > configuration and I see it as "running" through the "jailhouse cell > > list" command. However, I don't see any serial output from the > > "non-root linux" cell booting up. I’m not sure what the non-root node > > is doing at this point. > > Ok, first of all, can you see any output from Jailhouse's demo inmates > (e.g., tiny-demo or apic-demo)? > > > > > My root node is a 4.16 kernel configured this way: > > 1. CONFIG_JAILHOUSE_GUEST is not set > > 2. CONFIG_SERIO=y > > 3. CONFIG_SERIAL_8250_RUNTIME_UARTS=4 > > > > My non-root node is a 4.16 kernel configured this way: > > 1. CONFIG_JAILHOUSE_GUEST=y > > 2. CONFIG_SERIO=m (can't seem to disable > > completely in my config for 4.16) > > 3. CONFIG_SERIAL_8250_RUNTIME_UARTS=1 > > Could you please provide a full .config? What branch are you exactly > using? Vanilla 4.16? > > Please attach your system config and your non-root linux config as well. > > You may also want to try https://github.com/siemens/linux . See > jailhouse-enabling branches for some releases. > > > > > In general, do the kernel config settings have to match between > the root > > node and non-linux or is the above fine? > > No, they do not have to be the same, but they can. Still, an analysis > requires your .config. > > > > > The vmlinux-4.1.16-Guest bzImage is approx 7MB, and the inmate node is > > allocated ~75MB of RAM. > > > > I have a single UART, so I have configured the root cell system config > > to output to the virtual hypervisor console: > > Wait... You configured your root-cell to use the hypervisor debug > console? How? It's only available once the hypervisor is enabled. How > should this work? > > But let's have a look at your configuration first. > > So you want to: > - Have the UART (0x3f8) available in the non-root cell > - Use 0x3f8 as hypervisor debug console as well > - No console for root-cell > > Did I get this right? > > Ralf > > > > > .flags = JAILHOUSE_SYS_VIRTUAL_DEBUG_CONSOLE, > > > > .debug_console = { > > .type = JAILHOUSE_CON_TYPE_NONE, > > }, > > > > and I have configured the non-root linux cell to output to the UART: > > > > (Added serial 0x3f8 to pio bitmap for non-root linux) and started the > > node with this: > > > > ./tools/jailhouse cell linux configs/x86/linux-x86.cell > > /boot/vmlinux-4.1.16-Guest -c "console=ttyS0,115200" > > (Note I also tried "console=jailhouse" in the command above, and that > > produces the same result) > > > > I then see the following on my hypervisor console (./tools/jailhouse > > console -f): > > > > Created cell "linux-x86-demo" > > ... > > Cell "linux-x86-demo" can be loaded > > Started cell "linux-x86-demo" > > > > After a little while I do get a parked CPU error on the root node, > looks > > like its trying to do something with the UART as well: > > FATAL: Invalid PIO read, port: 3fe size: 1 > > > > I would expect something to pop out on the UART from the non-root > linux > > node first. Note that root node has serial 0x3f8 disabled in its pio > > bitmap. > > > > I verifed that the UART is functioning by allowing the hypervisor to > > print to it and also performed an echo test over ttyS0. > > > > I have tried several configurations of kernel.....including your > current > > "queues/jailhouse" branch head kernel for the non-root node, along > with > > the kernel config for 4.7 posted in this thread below (but I get same > > result as above when I start it, no kernel output): > > > > > > "https://groups.google.com/forum/#!searchin/jailhouse-dev/Re$3A$20Failed$20to$20boot$20jailhouse%7Csort:relevance/jailhouse-dev/M7UO89XFIk0/Qi40DDuMBAAJ";. > > > > Any information you can provide to me will be helpful. I'm not sure > > what might be going wrong here. > > > > Thanks, > > Wayne > > > > -- > > You received this message because you are subscribed to the Google > > Groups "Jailhouse" group. > > To unsubscribe from this group and stop receiving emails from it, send > > an email to [email protected] > <mailto:jailhouse-dev%[email protected]> > > <mailto:[email protected] > <mailto:jailhouse-dev%[email protected]>>. > > To view this discussion on the web visit > > > > https://groups.google.com/d/msgid/jailhouse-dev/CA%2B%2BKhc2iKk1J6%2B0huh5__dS4HyujXzV9r%2BLbKLzuVZ4K3Bt5eA%40mail.gmail.com > > > > <https://groups.google.com/d/msgid/jailhouse-dev/CA%2B%2BKhc2iKk1J6%2B0huh5__dS4HyujXzV9r%2BLbKLzuVZ4K3Bt5eA%40mail.gmail.com?utm_medium=email&utm_source=footer>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jailhouse-dev/166c6ad9-379c-bad6-f30f-8af4f97b8bb1%40oth-regensburg.de. For more options, visit https://groups.google.com/d/optout.
