* [Qemu-devel] [Bug 588731] Re: PXE boot not working
2010-06-02 14:15 [Qemu-devel] [Bug 588731] [NEW] PXE boot not working Jan Smets
@ 2010-06-02 14:54 ` Anthony Liguori
2010-06-02 15:13 ` Jan Smets
` (3 subsequent siblings)
4 siblings, 0 replies; 7+ messages in thread
From: Anthony Liguori @ 2010-06-02 14:54 UTC (permalink / raw)
To: qemu-devel
I can't reproduce this. I'm using:
commit d9b73e47a3d596c5b33802597ec5bd91ef3348e2
Author: Corentin Chary <corentincj@iksaif.net>
Date: Tue Jun 1 23:05:44 2010 +0200
vnc: add missing target for vnc-encodings-*.o
I'm using the command:
sudo x86_64-softmmu/qemu-system-x86_64 -net tap,vlan=0,name=tap.0 -boot
n -net nic,vlan=0,model=e1000,name=e1000.0 -chardev
socket,id=monitor,host=0.0.0.0,port=1024,telnet,server,nowait -monitor
chardev:monitor
The DHCP server I'm using is dnsmasq and it pxe boots as expected. I've
also confirmed that pxe boot is still functional after a system_reset.
Please include information about the exact version of qemu that you are
using and the DHCP server that is configured on your network. Please
also try to reproduce with the latest git.
** Changed in: qemu
Status: New => Incomplete
--
PXE boot not working
https://bugs.launchpad.net/bugs/588731
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Bug description:
/root/qemu-test/qemu-kvm/x86_64-softmmu/qemu-system-x86_64 -net tap,vlan=0,name=tap.0 -boot n -net nic,macaddr=$MAC,vlan=0,model=e1000,name=e1000.0 -chardev socket,id=monitor,host=0.0.0.0,port=$MONITORPORT,telnet,server,nowait -monitor chardev:monitor
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1)................ Connection timed out (0x4c106035)
No more network devices
No bootable device.
After doing a system_reset ....
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1).... ok
net0: 10.201.1.161/255.0.0.0 gw 10.0.0.1
Booting from filename "boot.pxe"
tftp://x.x.x./boot.pxe.. ok
And it magaically works.
using HEAD.
^ permalink raw reply [flat|nested] 7+ messages in thread* [Qemu-devel] [Bug 588731] Re: PXE boot not working
2010-06-02 14:15 [Qemu-devel] [Bug 588731] [NEW] PXE boot not working Jan Smets
2010-06-02 14:54 ` [Qemu-devel] [Bug 588731] " Anthony Liguori
@ 2010-06-02 15:13 ` Jan Smets
2010-09-14 13:06 ` Arsen.Shnurkov
` (2 subsequent siblings)
4 siblings, 0 replies; 7+ messages in thread
From: Jan Smets @ 2010-06-02 15:13 UTC (permalink / raw)
To: qemu-devel
using latest git
dhcp-3.0.1-58.EL4
with configuration:
host xxxx { filename "boot.pxe"; hardware ethernet
02:5A:3B:27:00:A1; fixed-address 10.201.1.161; }
#
## server config
#
server-identifier a.b.c.d;
server-name "some-name";
default-lease-time 600;
max-lease-time 1200;
ddns-update-style ad-hoc;
#log-facility local6;
allow booting;
allow bootp;
Latest GIT -> git clone http://git.kernel.org/pub/scm/virt/kvm/qemu-
kvm.git
configured with options
./configure --target-list=x86_64-softmmu --enable-gprof --enable-debug --enable-linux-aio --enable-profiler --with-kvm-trace
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /root/qemu-test/qemu-kvm
C compiler gcc
Host C compiler gcc
CFLAGS -g
QEMU_CFLAGS -Werror -m64 -fstack-protector-all -Wold-style-definition -Wold-style-declaration -I. -I$(SRC_PATH) -D_FORTIFY_SOURCE=2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -W
strict-prototypes -Wredundant-decls -Wall -Wundef -Wendif-labels -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing
LDFLAGS -Wl,--warn-common -m64 -g
make make
install install
host CPU x86_64
host big endian no
target list x86_64-softmmu
tcg debug enabled yes
Mon debug enabled yes
gprof enabled yes
sparse enabled no
strip binaries no
profiler yes
static build no
-Werror enabled yes
SDL support yes
curses support yes
curl support yes
check support no
mingw32 support no
Audio drivers oss
Extra audio cards ac97 es1370 sb16
Block whitelist
Mixer emulation no
VNC TLS support yes
VNC SASL support yes
xen support no
CPU emulation yes
brlapi support no
bluez support no
Documentation yes
NPTL support yes
GUEST_BASE yes
PIE user targets no
vde support no
IO thread no
Linux AIO support yes
Install blobs yes
KVM support yes
KVM PIT support yes
KVM device assig. yes
KVM trace support yes
fdt support no
preadv support yes
fdatasync yes
uuid support yes
vhost-net support yes
--
PXE boot not working
https://bugs.launchpad.net/bugs/588731
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Bug description:
/root/qemu-test/qemu-kvm/x86_64-softmmu/qemu-system-x86_64 -net tap,vlan=0,name=tap.0 -boot n -net nic,macaddr=$MAC,vlan=0,model=e1000,name=e1000.0 -chardev socket,id=monitor,host=0.0.0.0,port=$MONITORPORT,telnet,server,nowait -monitor chardev:monitor
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1)................ Connection timed out (0x4c106035)
No more network devices
No bootable device.
After doing a system_reset ....
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1).... ok
net0: 10.201.1.161/255.0.0.0 gw 10.0.0.1
Booting from filename "boot.pxe"
tftp://x.x.x./boot.pxe.. ok
And it magaically works.
using HEAD.
^ permalink raw reply [flat|nested] 7+ messages in thread* [Qemu-devel] [Bug 588731] Re: PXE boot not working
2010-06-02 14:15 [Qemu-devel] [Bug 588731] [NEW] PXE boot not working Jan Smets
2010-06-02 14:54 ` [Qemu-devel] [Bug 588731] " Anthony Liguori
2010-06-02 15:13 ` Jan Smets
@ 2010-09-14 13:06 ` Arsen.Shnurkov
2012-03-26 15:18 ` Michal Suchanek
2016-10-27 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 7+ messages in thread
From: Arsen.Shnurkov @ 2010-09-14 13:06 UTC (permalink / raw)
To: qemu-devel
The same to me, but rarely it does start only from third attempt
--
PXE boot not working
https://bugs.launchpad.net/bugs/588731
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Incomplete
Bug description:
/root/qemu-test/qemu-kvm/x86_64-softmmu/qemu-system-x86_64 -net tap,vlan=0,name=tap.0 -boot n -net nic,macaddr=$MAC,vlan=0,model=e1000,name=e1000.0 -chardev socket,id=monitor,host=0.0.0.0,port=$MONITORPORT,telnet,server,nowait -monitor chardev:monitor
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1)................ Connection timed out (0x4c106035)
No more network devices
No bootable device.
After doing a system_reset ....
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1).... ok
net0: 10.201.1.161/255.0.0.0 gw 10.0.0.1
Booting from filename "boot.pxe"
tftp://x.x.x./boot.pxe.. ok
And it magaically works.
using HEAD.
^ permalink raw reply [flat|nested] 7+ messages in thread* [Qemu-devel] [Bug 588731] Re: PXE boot not working
2010-06-02 14:15 [Qemu-devel] [Bug 588731] [NEW] PXE boot not working Jan Smets
` (2 preceding siblings ...)
2010-09-14 13:06 ` Arsen.Shnurkov
@ 2012-03-26 15:18 ` Michal Suchanek
2012-03-26 19:01 ` Michael Tokarev
2016-10-27 4:17 ` Launchpad Bug Tracker
4 siblings, 1 reply; 7+ messages in thread
From: Michal Suchanek @ 2012-03-26 15:18 UTC (permalink / raw)
To: qemu-devel
There seems to be an issue with kvm virtual network interface being
connected to a in-kernel bridge implementation.
When you configure networking that way the bridge port comes up when the
kvm instance is started.
As the time from the kvm start to entering the netboot rom is minimal
and the timeout before the bridge starts forwarding on new ports is long
this may cause the machine never getting an address.
If you are using a bridge try setting the forwarding delay to a small
value like:
iface vmbridge inet static
bridge_ports <probably should put some network interface name here - undocumented>
address 10.10.10.1
netmask 255.255.255.0
post-up brctl setfd vmbridge 3
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/588731
Title:
PXE boot not working
Status in QEMU:
Incomplete
Bug description:
/root/qemu-test/qemu-kvm/x86_64-softmmu/qemu-system-x86_64 -net
tap,vlan=0,name=tap.0 -boot n -net
nic,macaddr=$MAC,vlan=0,model=e1000,name=e1000.0 -chardev
socket,id=monitor,host=0.0.0.0,port=$MONITORPORT,telnet,server,nowait
-monitor chardev:monitor
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1)................ Connection timed out (0x4c106035)
No more network devices
No bootable device.
After doing a system_reset ....
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1).... ok
net0: 10.201.1.161/255.0.0.0 gw 10.0.0.1
Booting from filename "boot.pxe"
tftp://x.x.x./boot.pxe.. ok
And it magaically works.
using HEAD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/588731/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Qemu-devel] [Bug 588731] Re: PXE boot not working
2012-03-26 15:18 ` Michal Suchanek
@ 2012-03-26 19:01 ` Michael Tokarev
0 siblings, 0 replies; 7+ messages in thread
From: Michael Tokarev @ 2012-03-26 19:01 UTC (permalink / raw)
To: Bug 588731; +Cc: Michal Suchanek, qemu-devel
On 26.03.2012 19:18, Michal Suchanek wrote:
> There seems to be an issue with kvm virtual network interface being
> connected to a in-kernel bridge implementation.
>
> When you configure networking that way the bridge port comes up when the
> kvm instance is started.
>
> As the time from the kvm start to entering the netboot rom is minimal
> and the timeout before the bridge starts forwarding on new ports is long
> this may cause the machine never getting an address.
>
> If you are using a bridge try setting the forwarding delay to a small
> value like:
>
> iface vmbridge inet static
> bridge_ports <probably should put some network interface name here - undocumented>
> address 10.10.10.1
> netmask 255.255.255.0
> post-up brctl setfd vmbridge 3
Use
bridge_fd 0
here instead of these post-up things.
/mjt
^ permalink raw reply [flat|nested] 7+ messages in thread
* [Qemu-devel] [Bug 588731] Re: PXE boot not working
2010-06-02 14:15 [Qemu-devel] [Bug 588731] [NEW] PXE boot not working Jan Smets
` (3 preceding siblings ...)
2012-03-26 15:18 ` Michal Suchanek
@ 2016-10-27 4:17 ` Launchpad Bug Tracker
4 siblings, 0 replies; 7+ messages in thread
From: Launchpad Bug Tracker @ 2016-10-27 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/588731
Title:
PXE boot not working
Status in QEMU:
Expired
Bug description:
/root/qemu-test/qemu-kvm/x86_64-softmmu/qemu-system-x86_64 -net
tap,vlan=0,name=tap.0 -boot n -net
nic,macaddr=$MAC,vlan=0,model=e1000,name=e1000.0 -chardev
socket,id=monitor,host=0.0.0.0,port=$MONITORPORT,telnet,server,nowait
-monitor chardev:monitor
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1)................ Connection timed out (0x4c106035)
No more network devices
No bootable device.
After doing a system_reset ....
net0: 02:5a:3b:27:00:a1 on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
DHCP (net0 02:5a:3b:27:00:a1).... ok
net0: 10.201.1.161/255.0.0.0 gw 10.0.0.1
Booting from filename "boot.pxe"
tftp://x.x.x./boot.pxe.. ok
And it magaically works.
using HEAD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/588731/+subscriptions
^ permalink raw reply [flat|nested] 7+ messages in thread