Android x86 Oreo boot up takes too much time

[董倫銘]

Hi all,

When I run an Android VM on Qemu without a GPU card or a sound card, it takes quite long time.

I think the Android system was trying to connect the hardware devices.

How can I disable that the Android system tries to connect the non-exist hardware devices?

Or is there are anyway to speedup the boot time of the Oreo.

many thanks

[Chih-Wei Huang]

董倫銘 <k499...@gmail.com> 於 2019年7月3日 週三 下午3:24寫道：

An issue in sensors has been reported and fixed.
It may affect the boot time due to unexpected
crashing of system_server.

If you know how to build android-x86 source,
sync hardware/libsensors/ and rebuild the iso.


--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[董倫銘]

Hi Chih-Wei HuangThanks for reply，I tried to sync to 23c008a commit(tag: android-x86-8.1-r2), but the boot time still takes a long time.
Is the synced commit correct?

Thanks for your help.

Chih-Wei Huang <cwh...@android-x86.org> 於 2019年7月3日 週三 下午4:09寫道：

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n1LbHM2L%3DJPOEmEAn45re8FG4RwXSpiEMQpSSy6jLpthQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[董倫銘]

Hi Chih-Wei Huang

I saw the log shown:  D gralloc : Registering a buffer in the process that created it. This may cause memory ordering problems when the system pended for a long time.

Thanks for your help.

董倫銘 <k499...@gmail.com> 於 2019年7月4日 週四 下午2:29寫道：

[Chih-Wei Huang]

董倫銘 <k499...@gmail.com> 於 2019年7月4日 週四 下午2:30寫道：
>
> Hi Chih-Wei HuangThanks for reply，I tried to sync to 23c008a commit(tag: android-x86-8.1-r2), but the boot time still takes a long time.

> Is the synced commit correct?

No. It's behind 8.1-r2.
You need to sync the latest oreo-x86 branch to get it.

[董倫銘]

Hi Chih-Wei Huang

I tried to sync your patch but it still takes a long time to boot(more than 10 minutes). 

Here are the command for QEMU boot:

qemu-kvm -name node_78KF28
-S -machine pc-i440fx-rhel7.0.0,accel=kvm,usb=off,dump-guest-core=off
-m 2048 -realtime mlock=off
-smp 8,sockets=8,cores=1,threads=1
-uuid c10a7950-da35-4fc5-a8b2-e1b31e895cde
-no-user-config -nodefaults
-chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-171-node_78KF28/monitor.sock,server,nowait
-mon chardev=charmonitor,id=monitor,mode=control
-rtc base=utc -no-shutdown -no-acpi -boot strict=on
-kernel /opt/VM_Storage/DATA/6/kernel
-initrd /opt/VM_Storage/DATA/6/initrd.img
-append root=/dev/ram0 androidboot.selinux=permissive buildvariant=eng console=ttyS0 RAMDISK=vdb DATA=vdc -append video=720x1280 DPI=320
-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive file=/opt/VM_Storage/DATA/6/system1.sfs,format=raw,if=none,id=drive-virtio-disk0
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1
-drive file=/opt/VM_Storage/DATA/6/ramdisk.img,format=raw,if=none,id=drive-virtio-disk1
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1
-drive file=/opt/VM_Storage/Image/6/9.img,format=raw,if=none,id=drive-virtio-disk2
-device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk2,id=virtio-disk2
-netdev tap,fd=27,id=hostnet0
-device rtl8139,netdev=hostnet0,id=net0,mac=78:dc:90:50:9c:4b,bus=pci.0,addr=0x3
-spice port=5901,addr=0.0.0.0,disable-ticketing,seamless-migration=on
-vga std -global VGA.vgamem_mb=16
-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8
-msg timestamp=on

Is there any problem with the way I use it?

Thanks for your reply and help.

Chih-Wei Huang <cwh...@android-x86.org> 於 2019年7月4日 週四 下午4:29寫道：

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n2XVgLAHH7ZXW9wW-X_c%3D%3DOEub3kq22b8AUcrJrp_cYRA%40mail.gmail.com.

[Chih-Wei Huang]

董倫銘 <k499...@gmail.com> 於 2019年7月8日 週一 下午2:55寫道：

>
> Hi Chih-Wei Huang
> I tried to sync your patch but it still takes a long time to boot(more than 10 minutes).
> Here are the command for QEMU boot:

Then you need to check the log to see what happened.

[董倫銘]

I saw the log shown:  "D gralloc : Registering a buffer in the process that created it. This may cause memory ordering problems" when the system pended for a long time.

I did not see another error log...

Link: https://groups.google.com/d/msg/android-x86/ALCh5Dat7gA/sc9jh2dxAAAJ

Is it the root cause?

Chih-Wei Huang <cwh...@android-x86.org> 於 2019年7月8日 週一 下午4:13寫道：

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n2FC5CmLa_xEQ4AVkfXp5tYZZ-N2QmZK6s5vnmCxVQ0KQ%40mail.gmail.com.

[Chih-Wei Huang]

董倫銘 <k499...@gmail.com> 於 2019年7月8日 週一 下午4:32寫道：

>
>
> I saw the log shown: "D gralloc : Registering a buffer in the process that created it. This may cause memory ordering problems" when the system pended for a long time.
> I did not see another error log...
> Link: https://groups.google.com/d/msg/android-x86/ALCh5Dat7gA/sc9jh2dxAAAJ
> Is it the root cause?

I don't think so. That's normal.
You have to check what the system was doing during the 10min.

[董倫銘]

Hi Chih-Wei Huang

I used bootchart to check the boot time.

Found the status as shown in the attached picture(bootchart2.png): run "system server" is too late...

Than i see the log(boot_log.txt) like this:

07-09 01:56:24.849  1214  1260 I ServiceManager: Waiting for service package_native...
07-09 01:56:27.850  1214  1260 E /system/bin/storaged: getService package_native failed
07-09 01:56:27.850  1214  1260 I /system/bin/storaged: storaged: Start
07-09 01:56:25.850  1214  1260 I chatty  : uid=0(root) /system/bin/storaged identical 1 line
07-09 01:56:26.850  1214  1260 I ServiceManager: Waiting for service package_native...

07-09 01:56:35.693  1201  1315 D gralloc : Registering a buffer in the process that created it. This may cause memory ordering problems.

Does the package manager service have any issue?

Chih-Wei Huang <cwh...@android-x86.org> 於 2019年7月8日 週一 下午4:36寫道：

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at https://groups.google.com/group/android-x86.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n0K0e-1CtF6wok%3D_a0NHFzJ79Sch_XYby9%3Ditqem%3DQXCg%40mail.gmail.com.

[Dr. Lawrence]

Dears,

I found the package_native did not pend so much time in 8.1 r2.

Were there something change in package manager service or related files?

many thanks.

董倫銘於 2019年7月9日星期二 UTC+8上午10時21分26秒寫道：

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Pedro]

I don't know if it's related to your problem but i see that 7,1 is booting in ~3 sec from 'android' logo on while 8,1 takes ~30 sec.(SSD Disc)

But if you press a key (sometimes twice) as soon as you see 'android' boot logo 8,1 boots as fast as 7.1..    

 

[董倫銘]

Hi Pedro,

Yes, it is the same problem.  Do you have a solution?

Thanks for your help.

Pedro <ped.k...@gmail.com> 於 2019年9月5日 週四 上午4:41 寫道：

I don't know if it's related to your problem but i see that 7,1 is booting in ~3 sec from 'android' logo on while 8,1 takes ~30 sec.(SSD Disc)

But if you press a key (sometimes twice) as soon as you see 'android' boot logo 8,1 boots as fast as 7.1..    

 

--

You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/edb4fdaf-50ba-4f2e-93ad-59382a9d850c%40googlegroups.com.

[Daniel Cheung]

Boot in debug mode and see what the error messages are. For me, it was pstore drivers holding up the process. I removed it in the kernel configuration and it is now a lot faster.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAM5odyumH%3DP6aiSW%2B8sc6T-pCXW0cwBjaNeDZZ1ft5SBV0%3D9%2BA%40mail.gmail.com.

[Pedro]

when i press no key while booting i see this in logcat:

 

09-05 19:31:01.907  1390  1420 E /system/bin/storaged: getService package_native failed
09-05 19:31:01.914  1390  1420 I /system/bin/storaged: storaged: Start
09-05 19:32:09.355  1350  1350 D Zygote64Timing: PreloadClasses took to complete: 70279ms

 

when i press a key then i see Nothing about storaged but

09-05 19:35:49.382  1351  1351 D Zygote64Timing: PreloadClasses took to complete: 446ms

[Pedro]

This fixed the problem on my pc:

chmod 700 /data/data/com.google.android.gms

i saw in logcat someting like "700 was expected for /data/data/com.google.android.gms but 711 found" i dont remember exactly.

Am Donnerstag, 5. September 2019 03:24:00 UTC+2 schrieb 董倫銘:

Hi Pedro,

Yes, it is the same problem.  Do you have a solution?

Thanks for your help.

Pedro <ped....@gmail.com> 於 2019年9月5日 週四 上午4:41 寫道：

I don't know if it's related to your problem but i see that 7,1 is booting in ~3 sec from 'android' logo on while 8,1 takes ~30 sec.(SSD Disc)

But if you press a key (sometimes twice) as soon as you see 'android' boot logo 8,1 boots as fast as 7.1..    

 

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Dr. Lawrence]

Hi BrokenE39,

I had tried to use the kernel menuconfig to disable pstore,

but I did not find the pstore item.

Could you teach me detail about how to disable pstore?

many thanks

BrokenE39於 2019年9月5日星期四 UTC+8上午9時28分20秒寫道：

Boot in debug mode and see what the error messages are. For me, it was pstore drivers holding up the process. I removed it in the kernel configuration and it is now a lot faster.

On Wed, Sep 4, 2019 at 6:23 PM 董倫銘 <k499...@gmail.com> wrote:

Hi Pedro,

Yes, it is the same problem.  Do you have a solution?

Thanks for your help.

Pedro <ped....@gmail.com> 於 2019年9月5日 週四 上午4:41 寫道：

I don't know if it's related to your problem but i see that 7,1 is booting in ~3 sec from 'android' logo on while 8,1 takes ~30 sec.(SSD Disc)

But if you press a key (sometimes twice) as soon as you see 'android' boot logo 8,1 boots as fast as 7.1..    

 

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/edb4fdaf-50ba-4f2e-93ad-59382a9d850c%40googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.

To unsubscribe from this group and stop receiving emails from it, send an email to andro...@googlegroups.com.

[Daniel Cheung]

It's call Persistent Store Support under Misc. File System. You can use the find function and type in pstore and find it.

To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/f81afd0d-830b-4aa6-b0bc-03deae520152%40googlegroups.com.