Re: [Qemu-discuss] [Qemu-arm] Ubuntu installation shows "No network interfaces detected"

[Peter Maydell]

On Tue, 16 Apr 2019 at 15:24, Da Zhang <address@hidden> wrote:
>

This seems to be missing some output from the start of boot.

> [    2.361820] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
> [    2.375346] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.4.0-k
> [    2.390986] igb: Copyright (c) 2007-2014 Intel Corporation.
> [    2.403596] ixgbe: Intel(R) 10 Gigabit PCI Express Network Driver - 
> version 5.1.0-k
> [    2.420739] ixgbe: Copyright (c) 1999-2016 Intel Corporation.
> [    2.437883] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function 
> Network Driver - version 4.1.0-k


> [    2.642190] usbcore: registered new interface driver usbhid
> [    2.642191] usbhid: USB HID core driver
> [    2.642322] NET: Registered protocol family 17
> [    2.916496] scsi 0:0:0:0: Direct-Access     ATA      M5 IDE Disk      n/a  
> PQ: 0 ANSI: 5
> [    2.935127] sd 0:0:0:0: [sda] 16777216 512-byte logical blocks: (8.59 
> GB/8.00 GiB)
> [    2.952327] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [    2.964648] sd 0:0:0:0: [sda] Write Protect is off
> [    2.975518] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [    2.986957] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, 
> doesn't support DPO or FUA
> [    3.101444]  sda: sda1 sda2 sda3
> [    3.109804] sd 0:0:0:0: [sda] Attached SCSI disk
> [    3.452824] VFS: Mounted root (vfat filesystem) on device 8:1.

We found and mounted the ISO image's VFAT partition...

> [    3.466085] devtmpfs: error mounting -2
> [    3.475091] Freeing unused kernel memory: 384K
> [    3.485519] Kernel panic - not syncing: No working init found.  Try 
> passing init= option to kernel. See Linux Documentation/admin-guide/init.rst 
> for guidance.

...but unsurprisingly that is not a workable root filesystem.

> [    3.516805] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.14.0+ #2
> [    3.530257] Hardware name: V2P-CA15 (DT)
> [    3.539161] Call trace:
> [    3.544930] [<ffffff8008088250>] dump_backtrace+0x0/0x370
> [    3.557065] [<ffffff80080885d4>] show_stack+0x14/0x20
> [    3.568513] [<ffffff800863ffe8>] dump_stack+0x8c/0xac
> [    3.579903] [<ffffff80080b7338>] panic+0x11c/0x274
> [    3.590712] [<ffffff8008652244>] kernel_init+0xec/0x100
> [    3.602463] [<ffffff8008084348>] ret_from_fork+0x10/0x18
> [    3.614433] Kernel Offset: disabled
> [    3.622386] CPU features: 0x002000
> [    3.630153] Memory Limit: 1024 MB
> [    3.637726] ---[ end Kernel panic - not syncing: No working init found.  
> Try passing init= option to kernel. See Linux 
> Documentation/admin-guide/init.rst for guidance.
>
> This is my ARM/gem5.fast simulation output. The following is my gem5 command:
>
> build/ARM/gem5.fast --listener-mode=on -d /home/rock64/tmp/arm_ 
> configs/example/fs.py --machine-type=VExpress_GEM5_V1 
> --kernel=vmlinux.arm.4.4 --disk-image=ubuntu-16.04.5-server-arm64.img 
> --mem-size=1GB --cpu-type=ArmV8KvmCPU --generate-dtb -n 1


Wait, are you running this on QEMU or on GEM5?

Anyway, the lack of anything virtio related in the output you
quote leads me to suggest you check that your guest kernel
config has all the virtio devices in it. You might as well
add in PCI too (you want CONFIG_PCI, CONFIG_VIRTIO_PCI,
CONFIG_PCI_HOST_GENERIC, CONFIG_VIRTIO_BLK, CONFIG_VIRTIO_NET,
CONFIG_VIRTIO_MMIO).

Also, have you actually managed to do an install onto the
hard disk image yet? If not, then something is going wrong
before here that it's not doing an install properly.

thanks
-- PMM