On Tue, Oct 6, 2020 at 11:28 PM Thomas <74cmo...@gmail.com> wrote: > > Hello! > > Many thanks for your support. > > I managed to get emulated RPi starting. > > However there's one question I want to ask: > How can I accelerate the startup sequence? > I mean booting the emulated RPi takes more than 3 minutes. > > Regards > Thomas
Get a faster computer? ;) On my Intel i7 desktop it takes about 40 seconds to boot to the login: prompt on the serial console, and about 1 min 8 seconds before the GUI is up. On my 5 year old laptop it's probably twice that. I don't know of any way to make it go faster. - Paul > > Am 06.10.20 um 11:58 schrieb Alex Bennée: > > Thomas Schneider <74cmo...@gmail.com> writes: > > > >> Hello Paul, > >> > >> many thanks for sharing this info. > >> > >> Can you confirm that the emulated RPi with your command will use > >> "internal QEMU" network, means the client cannot be accessed from any > >> other device in LAN? > > The support for user-mode and TAP networking is orthogonal to the > > emulated device. However if you only want a few ports it's quite easy to > > use port forwarding, e.g: > > > > -netdev user,id=unet,hostfwd=tcp::2222-:22 > > > > which forwards 2222 to port 22 on the device. I have an alias in > > .ssh/config for accessing my QEMU devices. > > > >> If yes, what is required to setup a TAP connected to host's network > >> bridge? > > I'll defer to others for this but generally when I want proper bridged > > networking for a VM I use virt-manager/libvirt to configure it because > > it can be quite fiddly to do by hand. > > >
