Bug 437939 - "xm create" does not start a guest when host is not resolvable through DNS
Summary: "xm create" does not start a guest when host is not resolvable through DNS
Alias: None
Product: Fedora
Classification: Fedora
Component: xen
Version: 8
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Xen Maintainance List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-03-18 10:44 UTC by Egon Kastelijn
Modified: 2009-01-09 06:12 UTC (History)
0 users

Clone Of:
Last Closed: 2009-01-09 06:12:47 UTC

Attachments (Terms of Use)

Description Egon Kastelijn 2008-03-18 10:44:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20080208 Fedora/ Firefox/

Description of problem:
"xm create" does not start a guest when host is not resolvable through DNS.

Version-Release number of selected component (if applicable):
kernel-xen-   xen-3.1.2-2.fc8

How reproducible:

Steps to Reproduce:
1. Start a Xen kernel
2. Disconnect the network-cable (or make sure that the DNS-server is not accessible)
3. Start a network sniffer on the network card (wire-shark)
4. Start a xen guest using "xm create"
5. Notice the failing DNS lookup
6. Notice the failing start of the xen guest

Actual Results:
The Xen guest fails to start

Expected Results:
The Xen guest should have started.

Additional info:

Comment 1 Bug Zapper 2008-11-26 10:12:24 UTC
This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 8 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 2 Bug Zapper 2009-01-09 06:12:47 UTC
Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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