Bug 460817 - pxe network boot doesn't work on second boot using virt-manager
Summary: pxe network boot doesn't work on second boot using virt-manager
Keywords:
Status: CLOSED DUPLICATE of bug 484068
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: virt-manager
Version: 5.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-01 14:22 UTC by ITT Tech
Modified: 2009-12-14 21:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-13 20:56:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description ITT Tech 2008-09-01 14:22:22 UTC
Description of problem:
pxe network boot doesn't work on second boot using virt-manager

Version-Release number of selected component (if applicable):
latest yum updated

How reproducible:
always

Steps to Reproduce:
1. create a VM using virt-manager select pxe boot
2. reboot VM
3. doesn't PXE boot
  
Actual results:
boots from local hard drive

Expected results:
PXE boot

Additional info:
works ok if i use "xm create" command

domU boot="n"

Comment 1 Cole Robinson 2008-09-11 19:17:45 UTC
Problem here is that we assume you are pxe booting to install an os, and afterwards you plan on booting off the harddrive, which obviously isn't always the intended case.

The workaround for this is:

virsh dumpxml {vmname} > tmp.xml
edit tmp.xml, replace <boot dev='hd'/> with <boot dev='network'/>
virsh define tmp.xml

FYI, upstream virt-manager has support for changing the guests boot device
post install, so the ability is there. However it's getting a little late for a large backport. This may make it in a future release if we rebase to a newer version, but probably not likely for 5.3.

Comment 2 Cole Robinson 2009-02-13 20:56:39 UTC
Closing this a dup of the 'option to change boot device' RFE

*** This bug has been marked as a duplicate of bug 484068 ***


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