Regarding the issue of building Guest OS

[Jay Ironman]

Hello, I have two questions about building Guest OS:
Is there no problem with the error shown in the following figure? Can it be ignored? I have looked at the source code and it seems that this error does not affect the construction of Guest OS.

2. I am using Linux 6.8.2 to build a Guest OS (using Ubuntu 22.04), but I have been stuck in the following interface and unable to perform further operations. Is it because Linux 6.8.2 is incompatible with Ubuntu 22.04? I am very puzzled.

Thank you for browsing this question. I hope you can help me answer it.

[Jay Ironman]

I have tested on several computers, and the GuestOS build always gets stuck at the step shown in Figure 2 above.I am curious that if I manually start the GuestOS, it will not freeze, or if I use an older version of S2E to build the GuestOS, this problem will not occur. So I wonder if there is a problem with the updated S2E code?

[Jay Ironman]

In addition, I tested with Linux 6.8.2+Ubuntu 22.04 and also got stuck in Figure 2. I'm not sure why this is happening. I carefully reviewed the source code and think it might be stuck at the 'TAKE_SNAPSHOT' section.

[Vitaly Chipounov]

Hi,

The error in the makefile is ok. How long did you wait before terminating it? It can take a long time to boot Ubuntu in S2E mode. Did you compare it with 24.04?

Note that I first added support for Linux 6.8.2, then added Ubuntu 24.04, so normally 22.04 should still work.

Vitaly

--
You received this message because you are subscribed to the Google Groups "S2E Developer Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to s2e-dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/dca8ae48-54fa-4677-99a0-49fe458be137n%40googlegroups.com.

[Jay Ironman]

1. Yes, the first error is allowed because I have carefully read the source code and now I understand this problem
2. I still have questions about the second issue. Whether it's Linux 6.8.2+ubuntu 22.04 or ubuntu 24.04, it will get stuck at the "Loading initial ramdisk" screen in Figure 2 at the beginning. If you ask how long it's stuck, I would say that it's been waiting on this screen for 10 hours. I don't think this is a reasonable amount of time. In addition, my CPU core is 16 and my memory is allocated 16G, so resources should not have been exhausted.On the contrary, I built the GuestOS in the old version of S2E (Linux 4.9.3+Ubuntu 22.04) without any problems, and easily completed the entire process.

[Vitaly Chipounov]

10 hours sounds like a problem. It shouldn't take more than a few minutes. Does the qemu process use 100% the whole time? I wonder if there are kernel options you could use to increase verbosity, perhaps switch to text mode, etc.

Vitaly

On Mon, Jul 22, 2024 at 11:00 AM Jay Ironman <ironman...@gmail.com> wrote:

1. Yes, the first error is allowed because I have carefully read the source code and now I understand this problem
2. I still have questions about the second issue. Whether it's Linux 6.8.2+ubuntu 22.04 or ubuntu 24.04, it will get stuck at the "Loading initial ramdisk" screen in Figure 2 at the beginning. If you ask how long it's stuck, I would say that it's been waiting on this screen for 10 hours. I don't think this is a reasonable amount of time. In addition, my CPU core is 16 and my memory is allocated 16G, so resources should not have been exhausted.On the contrary, I built the GuestOS in the old version of S2E (Linux 4.9.3+Ubuntu 22.04) without any problems, and easily completed the entire process.

在2024年7月22日星期一 UTC+8 16:50:50<Vitaly Chipounov> 写道：

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/7f9b5cd3-a7f9-4c5b-a5f7-b4453f162ae0n%40googlegroups.com.

[Jay Ironman]

Okay, I'll go for a new test now and I'll send you the new test results as soon as possible. (Actually, using an old version of S2E can also complete my experiment, but I really want to figure out why this problem occurred.)

[Jay Ironman]

Hi, the issue still persists after retesting. I checked the startup output information of qemu and found 'end Kernel panic - not syncing: System is deadline on memory'. I think the memory allocation was too small, so I allocated 16GB of memory to it. However, after retesting, the issue still persists:

And I checked the usage rate of QEMU and found that its CPU usage rate has always been 100%, which I think is also a problem. PS: This test was stuck in the kernel initialization interface (as shown in Figure 2 at the beginning) for up to 3 hours

[Vitaly Chipounov]

Hi,

Can you try increasing the guest memory size? It's set to 256MB for S2E snapshots, which might be too low. It's not clear what you mean with "I allocated 16GB to it".

Vitaly

[1] https://github.com/S2E/guest-images/blob/master/images.json#L20

To view this discussion on the web visit https://groups.google.com/d/msgid/s2e-dev/f93fb687-fc12-42c4-a3c7-2f8512c29a12n%40googlegroups.com.

[Jay Ironman]

Thank you, I have solved this problem.I made a mistake in my previous analysis, mistaking the 'default_disk_size' variable for the memory size and neglecting the 'default_snapshot_size' variable. After setting the value of the 'default_snapshot_size' variable to 4096M, the issue disappeared.