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

[Da Zhang]

[    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.458697] ixgbevf: Copyright (c) 2009 - 2015 Intel Corporation.
[    2.481761] i40e: Intel(R) Ethernet Connection XL710 Network Driver -
version 2.1.14-k
[    2.534027] i40e: Copyright (c) 2013 - 2014 Intel Corporation.
[    2.547185] ata1.00: ATA-7: M5 IDE Disk, , max UDMA/66
[    2.547188] ata1.00: 16777216 sectors, multi 0: LBA
[    2.614939] ata1.00: configured for UDMA/33
[    2.624506] ixgb: Intel(R) PRO/10GbE Network Driver - version
1.0.135-k2-NAPI
[    2.624508] ixgb: Copyright (c) 1999-2008 Intel Corporation.
[    2.624531] i40evf: Intel(R) 40-10 Gigabit Virtual Function Network
Driver - version 3.0.0-k
[    2.624532] Copyright (c) 2013 - 2015 Intel Corporation.
[    2.640898] usbcore: registered new interface driver usb-storage
[    2.641296] mousedev: PS/2 mouse device common for all mice
[    2.641483] IR NEC protocol handler initialized
[    2.641485] IR RC5(x/sz) protocol handler initialized
[    2.641486] IR RC6 protocol handler initialized
[    2.641487] IR JVC protocol handler initialized
[    2.641488] IR Sony protocol handler initialized
[    2.641490] IR SANYO protocol handler initialized
[    2.641491] IR Sharp protocol handler initialized
[    2.641493] IR MCE Keyboard/mouse protocol handler initialized
[    2.641494] IR XMP protocol handler initialized
[    2.641819] gem5 DVFS handler is disabled
[    2.641822] gem5-energy-ctrl loaded at ffffff800899e000
[    2.641825] gem5_energy_ctrl_mc: gem5_mc_init: DVFS handler in energy
controller is disabled,                         ARM gem5 multi-cluster
cpufreq driver                         will not be registered
[    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.
[    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.
[    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


best,
Da

On Tue, Apr 16, 2019 at 9:02 AM Peter Maydell <address@hidden>
wrote:

> On Tue, 16 Apr 2019 at 13:53, Da Zhang <address@hidden> wrote:
> >
> > The qemu-system-aarch64 options support vda partition for the ubuntu
> installation. How to setup the options to support sda partition?
> > I was trying to use the image for my gem5 experiment but it gave me "[
> end Kernel panic - not syncing: No working init found.  Try passing init=
> option to kernel. See Linux Documentation/admin-guide/init.rst for
> guidance.". One difference I did notice is that all gem5 disk images (ARM
> and X86) I used are using /dev/sda. So, I want to try it and see if the
> problem fixed.
>
> You'll get 'sda' if QEMU exposes the disks to the
> guest as IDE or SCSI. 'vda' is for virtio block
> devices. 'vda' should work so I would recommend
> finding out why not rather than getting sidetracked
> into a different kind of guest disk setup that might
> not work either.
>
> If you post a link to the full boot up log then that
> will have enough information to tell whether the problem
> is that your guest kernel doesn't have virtio support
> built in or if something's wrong with your guest disk image.
>
> thanks
> -- PMM
>