Re: [Qemu-discuss] Upgrade from 0.11.0 to 2.9.0

[Thomas Huth]

 Hi,

On 19.09.2017 19:50, Schmidt, Alexander wrote:
[...]
> I am struggling to update one command for a powerpc machine.
> 
> Host: Windows 10 64-bits latest version. i7 CPU
> Guest: Debian 5.0 PPC
> 
> The command QEMU manager used was:
> "C:\qman70\qemu\qemu-system-ppc.exe" -L "C:\qman70\qemu" -M "g3beige" -m 1024 
> -vga std -serial vc -parallel vc -name "Debian-5.0-PPC" -drive 
> "file=C:\qman70\images\Debian-5.0-PPC.qcow2,index=0,media=disk" -boot 
> order=c,menu=off -soundhw ac97 -net 
> nic,vlan=0,macaddr=52-54-00-4A-E7-F7,model=rtl8139 -net user,vlan=0 -redir 
> tcp:10022::22 -hwnd 528058 -monitor telnet:127.0.0.1:60001,server,nowait 
> -localtime
> 
> I have been able to craft a command which works:
> "C:\Program Files (x86)\qemu\qemu-system-ppc.exe" -boot menu=off -m 1G -drive 
> "file=C:\qman70\images\Debian-5.0-PPC.qcow2,index=0,media=disk" -snapshot 
> -net nic,vlan=0,macaddr=52-54-00-4A-E7-F7,model=e1000 -net user,vlan=0 -redir 
> tcp:10022::22 -g 1024x768x8
> 
> But this generates deprecation warnings
> C:\Program Files (x86)\qemu\qemu-system-ppc.exe: -redir tcp:10022::22: The 
> -redir option is deprecated. Please use '-netdev user,hostfwd=...' instead.
> C:\Program Files (x86)\qemu\qemu-system-ppc.exe: -net 
> nic,vlan=0,macaddr=52-54-00-4A-E7-F7,model=e1000: 'vlan' is deprecated. 
> Please use 'netdev' instead.
> 
> The interface comes up and I see a message during the boot up which reads:
> [] e100: eth1: e1000_watchdog: NIC Link is Up 1000 Mbps Full Duplex, Flow 
> Control: RX
> 
> When I try to update the command to the following I no longer received 
> deprecation warnings but I can no longer SSH into the VM using port 10022.
> "C:\Program Files (x86)\qemu\qemu-system-ppc.exe" -device e1000,netdev=net0 
> -boot menu=off -m 1G -drive 
> "file=C:\qman70\images\Debian-5.0-PPC.qcow2,index=0,media=disk" -snapshot 
> -netdev user,id=net0,hostfwd=tcp::10022-:22 -g 1024x768x8
> 
> The interface doesn't come up and I see a message during the boot up which 
> reads:
> eth1: ERROR while getting interface flags: no such device
> eth1: ERROR while getting interface flags: no such device

The new command line looks ok to me at a first glance. Blind guess:
Maybe the issue is simply that the network card has a new MAC address
now? Try:

  -device e1000,netdev=net0,mac=52:54:00:4A:E7:F7

 HTH,
  Thomas


PS: I recommend to either use version 2.9.1 or 2.10.0 instead of 2.9.0
if possible.