Bug 1269052 - Adding a 2nd NIC forces PXE boot
Summary: Adding a 2nd NIC forces PXE boot
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 3.5.1.1
Hardware: x86_64
OS: Windows
high
high
Target Milestone: ovirt-3.6.2
: ---
Assignee: Eliraz Levi
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-06 07:34 UTC by Nicolas Ecarnot
Modified: 2016-02-10 19:15 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-24 07:48:58 UTC
oVirt Team: Network
Embargoed:
bazulay: ovirt-3.6.z?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?


Attachments (Terms of Use)

Description Nicolas Ecarnot 2015-10-06 07:34:52 UTC
Description of problem:
From a nice working VM in 2008 R2, I added a second NIC.
When rebooting the VM, PXE boot was forced and never falling over down to hard drive boot.

Version-Release number of selected component (if applicable):
3.5.1.1

How reproducible:
I saw it once.

Steps to Reproduce:
1. Install a VM in windows server 2008 R2 64 bits standard with a NIC, boot it, reboot it some times, see it OK, shutdown it.
2. Add a second NIC
3. Boot it.

Actual results:
The VM is trying to PXE boot. The boot order clearly shows hard drive first.
I tried to put PXE first and save, then hard drive first and save, then boot, with NO success.

Expected results:
- Adding or removing NICs should not change the boot behaviour
- Editing the VM boot order should work.

Additional info:
The workaround I found was this :
- "Unplug" both NICs
- Boot. It is booting on the hard drive
- Shutdown
- "Replug" the NICs
- Boot. It is booting on the hard drive

Comment 1 Red Hat Bugzilla Rules Engine 2015-10-19 11:01:00 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 2 Dan Kenigsberg 2015-11-23 11:41:50 UTC
Can you attach engine.log and vdsm.log?

Meni, can you see something like that?

Comment 3 Michael Burman 2015-11-23 15:14:27 UTC
This is not reproducible with rhel 6.7 and 7.1 guests

Comment 4 Michael Burman 2015-11-23 16:10:00 UTC
Can't reproduce with windows 2008 R2 64 guest as well.
Tested on 3.5.6.2-0.1.el6ev
Thanks,

Comment 5 Dan Kenigsberg 2015-11-24 07:48:58 UTC
Please reopen if this happens again. Please provide Engine, Vdsm, libvirt and qemu versions, as well as engine.log and vdsm.log.

Comment 6 Nicolas Ecarnot 2015-11-24 08:07:22 UTC
(In reply to Dan Kenigsberg from comment #5)
> Please reopen if this happens again. Please provide Engine, Vdsm, libvirt
> and qemu versions, as well as engine.log and vdsm.log.

ACK


Note You need to log in before you can comment on or make changes to this bug.