From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: -netdev & PXEboot Date: Mon, 29 Mar 2010 19:31:28 +0400 Message-ID: <4BB0C7D0.9090500@msgid.tls.msk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit To: KVM list Return-path: Received: from isrv.corpit.ru ([81.13.33.159]:56765 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752192Ab0C2Pba (ORCPT ); Mon, 29 Mar 2010 11:31:30 -0400 Sender: kvm-owner@vger.kernel.org List-ID: I sent this email yesterday but it never come back to me and is not shown in archives. So resending it. I noticed that with the -netdev syntax (introduced in 0.12) it is not possible to perform network booting anymore: $ kvm -net tap,ifname=tap-kvm,id=net0 \ -device virtio-net-pci,id=net0 -boot n Cannot boot from non-existent NIC On the other hand, $ kvm -net tap,ifname=tap-kvm \ -net nic,model=virtio -boot n boots ok. I also noticed that it's not possible to use boot=on parameter for network booting at all: $ kvm -net tap,ifname=tap-kvm -net nic,model=virtio,boot=on option "boot" is not valid for net $ kvm -net tap,ifname=tap-kvm,id=net0 -device virtio-net-pci,id=net0,boot=on property "virtio-net-pci.boot" not found can't set property "boot" to "on" for "virtio-net-pci" What's the way to PXE-boot when using the new -netdev syntax? Thanks! /mjt