all the "two bridges don't work" bugs that have been reported (bug #381).
Consideration will be given to raising the default limit -- this is just a
diagnostic of the problem.
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>
1: mistake sequence of set/clr to virtual IRQ line.
2: wrong sequence of IRQ request clear
3: Add one more place to enable_irq_window.
Signed-off-by: Eddie Dong <eddie.dong@intel.com>
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>
be enabled and disabled dynamically while the system is running. The
existing DOM0_TBUFCONTROL hypercall is used, and three new operations
have been added: enable, disable, and set_size. This is to address
concerns that use of the trace buffers impacts system performance.
The initial value of opt_tbuf_size is set to zero, so that trace
buffers remain disabled by default. They can be enabled as they used
to be, by adding tbuf_size= to the xen command line at boot time. They
can also be turned on and off any time when the system is running. The
size of the trace buffer allocation can also be changed dynamically
while the system is running. The trace buffers may be completely
deallocated by setting the size to zero. No change in buffer size can
be done while tracing is enabled;
Other Changes made:
- Update the constants in tools/xentrace/formats to match those in
public/trace.h
- libxc functions for enable/disable, get/set size
Still left to do:
- remove all ifdef's for trace buffers and the 'trace' build option
- xm command to do enable/disable trace buffers and get/set size
Signed-off-by: Rob Gardner <rob.gardner@hp.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>
