[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1736655] Re: 2k3/xp guests w/virtio-net randomly DHCP
|
From: |
Patrick Schweiger |
|
Subject: |
[Qemu-devel] [Bug 1736655] Re: 2k3/xp guests w/virtio-net randomly DHCP fail on boot |
|
Date: |
Wed, 06 Dec 2017 06:02:50 -0000 |
** Description changed:
Host:
Debian GNU/Linux 9 with Linux 4.13.0-0.bpo.1-amd64
QEMU 2.10.1
Guest:
Windows 2003 Standard SP2 (x64)
Windows XP SP3 (i386)
QEMU command line:
http://cfp.vim-cn.com/cbdF3
Description:
After upgrading from QEMU 2.8 to 2.10.1, my Windows 2003 x64 and Windows XP
guests with "virtio-net-pci" NIC would randomly fail to aquire DHCP address on
boot. When it fails, cycle disable/enable the connection in Control Panel could
make it connect successfully. As an immediate workaround, I switched to the
RTL8139 NIC which works fine. Further investigation showed that manually
reverting commit '4a3f03ba8dbf53fce36d0c1dd5d0cc0f340fe5f3' on top of 2.10.1
"fixed" the problem.
Here are the test results:
- git branch 4a3f03b: 25 boots, 8 failures
- git branch 39f099e: 60 boots, 0 failure
+ git branch 97cd965: 17 boots, 5 failures (Feb 18)
+ git branch 77424a4: 27 boots, 0 failure (Jan 09)
+ git branch c25d97c: 7 boots, 2 failures (Feb 01)
+ git branch 4a3f03b: 25 boots, 8 failures (Jan 19)
+ git branch 39f099e: 60 boots, 0 failure (Jan 18)
2.10.1 with revert: 194 boots, 0 failure
** Description changed:
Host:
Debian GNU/Linux 9 with Linux 4.13.0-0.bpo.1-amd64
QEMU 2.10.1
Guest:
Windows 2003 Standard SP2 (x64)
Windows XP SP3 (i386)
QEMU command line:
http://cfp.vim-cn.com/cbdF3
Description:
After upgrading from QEMU 2.8 to 2.10.1, my Windows 2003 x64 and Windows XP
guests with "virtio-net-pci" NIC would randomly fail to aquire DHCP address on
boot. When it fails, cycle disable/enable the connection in Control Panel could
make it connect successfully. As an immediate workaround, I switched to the
RTL8139 NIC which works fine. Further investigation showed that manually
reverting commit '4a3f03ba8dbf53fce36d0c1dd5d0cc0f340fe5f3' on top of 2.10.1
"fixed" the problem.
- Here are the test results:
+ Here are the bisect test results:
git branch 97cd965: 17 boots, 5 failures (Feb 18)
git branch 77424a4: 27 boots, 0 failure (Jan 09)
git branch c25d97c: 7 boots, 2 failures (Feb 01)
git branch 4a3f03b: 25 boots, 8 failures (Jan 19)
git branch 39f099e: 60 boots, 0 failure (Jan 18)
2.10.1 with revert: 194 boots, 0 failure
** Description changed:
Host:
Debian GNU/Linux 9 with Linux 4.13.0-0.bpo.1-amd64
QEMU 2.10.1
Guest:
Windows 2003 Standard SP2 (x64)
Windows XP SP3 (i386)
QEMU command line:
http://cfp.vim-cn.com/cbdF3
Description:
After upgrading from QEMU 2.8 to 2.10.1, my Windows 2003 x64 and Windows XP
guests with "virtio-net-pci" NIC would randomly fail to aquire DHCP address on
boot. When it fails, cycle disable/enable the connection in Control Panel could
make it connect successfully. As an immediate workaround, I switched to the
RTL8139 NIC which works fine. Further investigation showed that manually
reverting commit '4a3f03ba8dbf53fce36d0c1dd5d0cc0f340fe5f3' on top of 2.10.1
"fixed" the problem.
Here are the bisect test results:
git branch 97cd965: 17 boots, 5 failures (Feb 18)
git branch 77424a4: 27 boots, 0 failure (Jan 09)
git branch c25d97c: 7 boots, 2 failures (Feb 01)
git branch 4a3f03b: 25 boots, 8 failures (Jan 19)
git branch 39f099e: 60 boots, 0 failure (Jan 18)
2.10.1 with revert: 194 boots, 0 failure
+ 2.10.1 without revert: 4 boots, 3 failures
** Description changed:
Host:
Debian GNU/Linux 9 with Linux 4.13.0-0.bpo.1-amd64
QEMU 2.10.1
Guest:
Windows 2003 Standard SP2 (x64)
Windows XP SP3 (i386)
QEMU command line:
http://cfp.vim-cn.com/cbdF3
Description:
After upgrading from QEMU 2.8 to 2.10.1, my Windows 2003 x64 and Windows XP
guests with "virtio-net-pci" NIC would randomly fail to aquire DHCP address on
boot. When it fails, cycle disable/enable the connection in Control Panel could
make it connect successfully. As an immediate workaround, I switched to the
RTL8139 NIC which works fine. Further investigation showed that manually
reverting commit '4a3f03ba8dbf53fce36d0c1dd5d0cc0f340fe5f3' on top of 2.10.1
"fixed" the problem.
Here are the bisect test results:
git branch 97cd965: 17 boots, 5 failures (Feb 18)
git branch 77424a4: 27 boots, 0 failure (Jan 09)
git branch c25d97c: 7 boots, 2 failures (Feb 01)
git branch 4a3f03b: 25 boots, 8 failures (Jan 19)
git branch 39f099e: 60 boots, 0 failure (Jan 18)
2.10.1 with revert: 194 boots, 0 failure
- 2.10.1 without revert: 4 boots, 3 failures
+ 2.10.1 without revert: 30 boots, 4 failures
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1736655
Title:
2k3/xp guests w/virtio-net randomly DHCP fail on boot
Status in QEMU:
New
Bug description:
Host:
Debian GNU/Linux 9 with Linux 4.13.0-0.bpo.1-amd64
QEMU 2.10.1
Guest:
Windows 2003 Standard SP2 (x64)
Windows XP SP3 (i386)
QEMU command line:
http://cfp.vim-cn.com/cbdF3
Description:
After upgrading from QEMU 2.8 to 2.10.1, my Windows 2003 x64 and Windows XP
guests with "virtio-net-pci" NIC would randomly fail to aquire DHCP address on
boot. When it fails, cycle disable/enable the connection in Control Panel could
make it connect successfully. As an immediate workaround, I switched to the
RTL8139 NIC which works fine. Further investigation showed that manually
reverting commit '4a3f03ba8dbf53fce36d0c1dd5d0cc0f340fe5f3' on top of 2.10.1
"fixed" the problem.
Here are the bisect test results:
git branch 97cd965: 17 boots, 5 failures (Feb 18)
git branch 77424a4: 27 boots, 0 failure (Jan 09)
git branch c25d97c: 7 boots, 2 failures (Feb 01)
git branch 4a3f03b: 25 boots, 8 failures (Jan 19)
git branch 39f099e: 60 boots, 0 failure (Jan 18)
2.10.1 with revert: 194 boots, 0 failure
2.10.1 without revert: 30 boots, 4 failures
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1736655/+subscriptions