and drive this process from xm create. Architecturally, this separates the
process of domain creation from the process of waiting for devices, allowing
tools to choose when to perform that wait (if at all). This places the waiting
in the same category as the unpause after domain creation, architecturally.
The main advantage to this approach is that it takes waiting for devices out
of the scope of XendDomain's domains_lock. When restarting a domain, the
watch would fire for @releaseDomain while we were waiting for new domains to
come up. This would deadlock the watch thread, as no more new watches could
be delivered. Closes bug #387.
In the longer term, we expect to be able to wait for devices to come up
completely, not simply to wait for the hotplug scripts to run, and so it is
necessary then to move the waiting procedure right out of the server, so that
it can be performed after the domain unpause. Without unpausing the domain,
the frontends will not come up, and so we cannot detect successful device
completion.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
xm now accepts a parameter 'ioports' that accepts a hex ioport
or ioport range, in the form 02f8[-02ff]
Signed-off-by: Jody Belka <knew (at) pimb (dot) org>
xm now accepts a parameter 'ioports' that accepts a hex ioport
or ioport range, in the form 02f8[-02ff]
Signed-off-by: Jody Belka <knew (at) pimb (dot) org>
vnet-create is correct. This is better than throwing IOError, because
IOError's are currently reported as xend communication failures.
Also, fix the IOError handling at the end of the file so we don't get
a stack dump if that path is taken.
Signed-off-by: Dan Smith <danms@us.ibm.com>
on vncserver or remote X. Changeset 7547 added a test of
opts.vals.display when getenv("DISPLAY"); because there is a default
value:localhost:0, that causes the test always to be true.
Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com>
The problem is: There is no mechanism to detect block device setup failure
Network devices have the same problem, and are fixed with this too.
I handling this problem in the way suggested by aliguori:
- hotplug scripts write a "hotplug-status" node on store
- Xend DevController.createDevice() check verify this node and return success
or throw an exception on failure.
- If no changes in "hotplug-status" node after DEVICE_CREATE_TIMEOUT seconds
Xend throw an exception showing the problem with hotplug scripts.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
list is passed rather than a single string. This expands the config-file
interface so that parameters may be passed to the network scripts from the
config file.
Fix XendRoot._logError (missing asterisk before args parameter).
In XendRoot, allow an empty configuration file. This makes it easier to unit
test code reliant on XendRoot.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
for the command line parsing code in xm create. To make it easier to test,
create.py has changed in structure around the main(argv) function, adding a new
parseCommandLine function.
Remove a large number of useless parameters, where the opts structure was being
passed all over the place, just to eventually log through it. Instead two
methods -- err and warn -- have been broken out from the Opts class, and there
is now no need to pass the opts value everywhere.
Change the parsing inside make_config to remove lots of cut-and-pasted cruft.
Change the documentation to the vif command to indicate that the bridge can be
auto-detected.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
This was passing down to dhclient which was keeping the 8001 port
open and preventing xend restarting.
Also fixed a case typo in setCloExec
Signed-off-by: James Bulpin <james@xensource.com>
be refused, with the domain being destroyed instead.
Further fix for reboot logic when using on_reboot=rename-restart: the incorrect
node was being removed once restart has completed, leaving Xend to conclude
later that it had crashed in the middle of a restart.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Reject the removal of -Werror from the xentop Makefile.
Reject the #include of xs.h inside xentop -- there is no need for it.
Have XendDomainInfo write domain names into /local/domain (which used to happen,
but hasn't for a little while).
Remove the dead code from xentop.c.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
It doesn't make sense to undo the network configuration when stopping
xend since that would cut off all VMs from the network. Undoing the
network setup should be an option independent of xend stop.
Signed-off-by: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
