Mdthbs

Why didn't Eitri join the fight?

How to compare two different files line by line in unix?

Can you use the Shield Master feat to shove someone before you make an attack by using a Readied action?

How do pianists reach extremely loud dynamics?

Trademark violation for app?

If a contract sometimes uses the wrong name, is it still valid?

What causes the direction of lightning flashes?

Is it a good idea to use CNN to classify 1D signal?

Amount of permutations on an NxNxN Rubik's Cube

Around usage results

What do you call the main part of a joke?

Using et al. for a last / senior author rather than for a first author

Can anything be seen from the center of the Boötes void? How dark would it be?

Is there a kind of relay only consumes power when switching?

Why wasn't DOSKEY integrated with COMMAND.COM?

How can I use the Python library networkx from Mathematica?

Can a new player join a group only when a new campaign starts?

How does the math work when buying airline miles?

How to deal with a team lead who never gives me credit?

How would a mousetrap for use in space work?

Irreducible of finite Krull dimension implies quasi-compact?

Wu formula for manifolds with boundary

Generate an RGB colour grid

Most bit efficient text communication method?

QEMU: How to convert -net flags into -device & -netdev

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

1

I'm trying to emulate Raspberry Pi via QEMU and the following works for me:

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -net nic 

    -net user,id=user.0,hostfwd=tcp::5555-:22

and I'm able to both VNC in via 5904 and SSH in via 5555 (after starting SSHd via VNC). In other words network seems to be set up correctly.

As I discovered -net option has been deprecated in favour of -device & -netdev, so I'd like to translate the above two last flags into "new QEMU".

It appears that the new -device flag forces me to pick a driver, which isn't the case with -net. I like explicitness, but how do I know what is the default/implicit driver?

Port forwarding in the following example doesn't seem to work anymore (I can't SSH in; connection times out):

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -device e1000,netdev=user.0 

    -netdev user,id=user.0,hostfwd=tcp::5555-:22

Am I just using wrong driver?

---

QEMU 3.1.0 (installed from Homebrew)

(Host) MacOS 10.14.4

osx raspberry-pi qemu

share|improve this question

asked 8 hours ago

Radek SimkoRadek Simko

1063

New contributor

Radek Simko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I managed to make it work with -nic user,id=user.0,hostfwd=tcp::5555-:22 (which seems to be a new flag too) but I'm still very confused about differences between all these flags and I'm still curious whether they are replaceable with each other.
  
  – Radek Simko
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  qemu.org/2018/05/31/nic-parameter provides some background with some hints that these flags may not actually be equivalent. Should I turn this into an answer?
  
  – Radek Simko
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  you should, if it works for you. as a completion, you can check the default network device with info network in the qemu monitor (for your machine (versatilepb) it's probably smc91c111.
  
  – mosvy
  6 hours ago
  
  
  

  
  
  
  

add a comment | 

1

I'm trying to emulate Raspberry Pi via QEMU and the following works for me:

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -net nic 

    -net user,id=user.0,hostfwd=tcp::5555-:22

and I'm able to both VNC in via 5904 and SSH in via 5555 (after starting SSHd via VNC). In other words network seems to be set up correctly.

As I discovered -net option has been deprecated in favour of -device & -netdev, so I'd like to translate the above two last flags into "new QEMU".

It appears that the new -device flag forces me to pick a driver, which isn't the case with -net. I like explicitness, but how do I know what is the default/implicit driver?

Port forwarding in the following example doesn't seem to work anymore (I can't SSH in; connection times out):

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -device e1000,netdev=user.0 

    -netdev user,id=user.0,hostfwd=tcp::5555-:22

Am I just using wrong driver?

---

QEMU 3.1.0 (installed from Homebrew)

(Host) MacOS 10.14.4

osx raspberry-pi qemu

share|improve this question

asked 8 hours ago

Radek SimkoRadek Simko

1063

New contributor

Radek Simko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I managed to make it work with -nic user,id=user.0,hostfwd=tcp::5555-:22 (which seems to be a new flag too) but I'm still very confused about differences between all these flags and I'm still curious whether they are replaceable with each other.
  
  – Radek Simko
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  qemu.org/2018/05/31/nic-parameter provides some background with some hints that these flags may not actually be equivalent. Should I turn this into an answer?
  
  – Radek Simko
  8 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  you should, if it works for you. as a completion, you can check the default network device with info network in the qemu monitor (for your machine (versatilepb) it's probably smc91c111.
  
  – mosvy
  6 hours ago
  
  
  

  
  
  
  

add a comment | 

I'm trying to emulate Raspberry Pi via QEMU and the following works for me:

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -net nic 

    -net user,id=user.0,hostfwd=tcp::5555-:22

and I'm able to both VNC in via 5904 and SSH in via 5555 (after starting SSHd via VNC). In other words network seems to be set up correctly.

As I discovered -net option has been deprecated in favour of -device & -netdev, so I'd like to translate the above two last flags into "new QEMU".

It appears that the new -device flag forces me to pick a driver, which isn't the case with -net. I like explicitness, but how do I know what is the default/implicit driver?

Port forwarding in the following example doesn't seem to work anymore (I can't SSH in; connection times out):

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -device e1000,netdev=user.0 

    -netdev user,id=user.0,hostfwd=tcp::5555-:22

Am I just using wrong driver?

---

QEMU 3.1.0 (installed from Homebrew)

(Host) MacOS 10.14.4

osx raspberry-pi qemu

share|improve this question

asked 8 hours ago

Radek SimkoRadek Simko

1063

New contributor

Radek Simko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -net nic 

    -net user,id=user.0,hostfwd=tcp::5555-:22

qemu-system-arm 

    -append "root=/dev/sda2 panic=1 rootfstype=ext4 rw" 

    -boot c 

    -cpu arm1176 

    -drive "file=2019-04-08-raspbian-stretch-lite.img,if=scsi,cache=none,discard=ignore,format=raw" 

    -kernel ./kernel-qemu-4.4.34-jessie 

    -m 256M 

    -machine type=versatilepb,accel=tcg 

    -name packer-qemu 

    -no-reboot 

    -vnc 127.0.0.1:4 

    -device e1000,netdev=user.0 

    -netdev user,id=user.0,hostfwd=tcp::5555-:22

share|improve this question

asked 8 hours ago

Radek SimkoRadek Simko

1063

New contributor

Radek Simko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

asked 8 hours ago

Radek SimkoRadek Simko

1063

New contributor

Radek Simko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 8 hours ago

Radek SimkoRadek Simko

1063

New contributor

Radek Simko is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 8 hours ago

Radek SimkoRadek Simko

1063