gem5-users@gem5.org

The gem5 Users mailing list

View all threads

(1 of 3) A start job is running for...twork interfaces (14s / 5min 1s)

XL
Xiang Li
Thu, May 11, 2023 12:03 AM

Hi,

I'm running a X86 full-system, which needs a about 30G memory. When I'm running the FS, it would say ' Welcome to Ubuntu 16.04.7 LTS!', and then somehing like these:
'''
systemd[1]: Reached target Encrypted Volumes.
[  OK  ] Reached target Encrypted Volumes.
systemd[1]: Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
systemd[1]: Started Trigger resolvconf update for networkd DNS.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
...
[  OK  ] Started LSB: AppArmor initialization.
Starting Raise network interfaces...
[  *** ] (1 of 3) A start job is running for...twork interfaces (14s / 5min 1s)

'''
Someone says that's because I don't have enough swap space, but I made a 30G swap space for my host, and I used --mem-size=30000MB in the command. Maybe because my disk-img file only have a 8.5G space? Could please tell me why? It would run several hours. Thanks,

Best wish,
Xiang

Hi, I'm running a X86 full-system, which needs a about 30G memory. When I'm running the FS, it would say ' Welcome to Ubuntu 16.04.7 LTS!', and then somehing like these: ''' systemd[1]: Reached target Encrypted Volumes. [ OK ] Reached target Encrypted Volumes. systemd[1]: Listening on fsck to fsckd communication Socket. [ OK ] Listening on fsck to fsckd communication Socket. systemd[1]: Listening on udev Kernel Socket. [ OK ] Listening on udev Kernel Socket. systemd[1]: Started Trigger resolvconf update for networkd DNS. [ OK ] Started Trigger resolvconf update for networkd DNS. systemd[1]: Created slice System Slice. [ OK ] Created slice System Slice. systemd[1]: Listening on udev Control Socket. [ OK ] Listening on udev Control Socket. ... [ OK ] Started LSB: AppArmor initialization. Starting Raise network interfaces... [ *** ] (1 of 3) A start job is running for...twork interfaces (14s / 5min 1s) ''' Someone says that's because I don't have enough swap space, but I made a 30G swap space for my host, and I used --mem-size=30000MB in the command. Maybe because my disk-img file only have a 8.5G space? Could please tell me why? It would run several hours. Thanks, Best wish, Xiang
AA
Ayaz Akram
Fri, May 12, 2023 4:34 AM

Hi Xiang,

From the guest terminal output you shared, it seems like it is busy running
systemd services after the kernel boot. Simulating those can take a long
time. How long has it been running for?

-Ayaz

On Wed, May 10, 2023 at 5:07 PM Xiang Li via gem5-users gem5-users@gem5.org
wrote:

Hi,
I'm running a X86 full-system, which needs a about 30G memory. When I'm
running the FS, it would say ' Welcome to Ubuntu 16.04.7 LTS!', and then
somehing like these:
'''
systemd[1]: Reached target Encrypted Volumes.
[  OK  ] Reached target Encrypted Volumes.
systemd[1]: Listening on fsck to fsckd communication Socket.
[  OK  ] Listening on fsck to fsckd communication Socket.
systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
systemd[1]: Started Trigger resolvconf update for networkd DNS.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
...
[  OK  ] Started LSB: AppArmor initialization.
Starting Raise network interfaces...
[  *** ] (1 of 3) A start job is running for...twork interfaces (14s /
5min 1s)
'''
Someone says that's because I don't have enough swap space, but I made a
30G swap space for my host, and I used --mem-size=30000MB in the command.
Maybe because my disk-img file only have a 8.5G space? Could please tell me
why? It would run several hours. Thanks,

Best wish,
Xiang


gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-leave@gem5.org

Hi Xiang, From the guest terminal output you shared, it seems like it is busy running systemd services after the kernel boot. Simulating those can take a long time. How long has it been running for? -Ayaz On Wed, May 10, 2023 at 5:07 PM Xiang Li via gem5-users <gem5-users@gem5.org> wrote: > Hi, > I'm running a X86 full-system, which needs a about 30G memory. When I'm > running the FS, it would say ' Welcome to Ubuntu 16.04.7 LTS!', and then > somehing like these: > ''' > systemd[1]: Reached target Encrypted Volumes. > [ OK ] Reached target Encrypted Volumes. > systemd[1]: Listening on fsck to fsckd communication Socket. > [ OK ] Listening on fsck to fsckd communication Socket. > systemd[1]: Listening on udev Kernel Socket. > [ OK ] Listening on udev Kernel Socket. > systemd[1]: Started Trigger resolvconf update for networkd DNS. > [ OK ] Started Trigger resolvconf update for networkd DNS. > systemd[1]: Created slice System Slice. > [ OK ] Created slice System Slice. > systemd[1]: Listening on udev Control Socket. > [ OK ] Listening on udev Control Socket. > ... > [ OK ] Started LSB: AppArmor initialization. > Starting Raise network interfaces... > [ *** ] (1 of 3) A start job is running for...twork interfaces (14s / > 5min 1s) > ''' > Someone says that's because I don't have enough swap space, but I made a > 30G swap space for my host, and I used --mem-size=30000MB in the command. > Maybe because my disk-img file only have a 8.5G space? Could please tell me > why? It would run several hours. Thanks, > > Best wish, > Xiang > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-leave@gem5.org >