cannot allocate a contiguous multi-page extent of memory. This
should avoid unnecessary crashes in the xen-specific skbuff
cache constructor.
Signed-off-by: Keir Fraser <keir@xensource.com>
with a block device attached. It starts up a domain, mounts a block
device, writes data to it, saves, restores, and then verifies that the
block device can still be read.
Signed-off-by: Dan Smith <danms@us.ibm.com>
This includes quite a few cleanups / refactoring of the old code, some
of which is intended to prepare for 64-bit save/restore.
Signed-off-by: Steven Hand <steven@xensource.com>
to 8. These interfaces are very cheap, so there's no problem having a few
spare. Anyone with more than 8 NICs can still use the kernel command line or
the module parameter line to pass a larger limit to this module.
Detail the kernel command line parameter for nloopbacks in the diagnostic in
network-bridge.
Closes bug #381.
Signed-off-by: Ewan Mellor <ewan@xensource.com>
Separate out the ability for domains to be able to write to their
pagetables (ala "writable page tables", which uses write-protected PTEs
to address the page tables: this is shadow_mode_write_all()) from the
right of a domain to create a PTE with write permissions that points
at a page table (this is shadow_mode_wr_pt_pte())...
Minor cleanup of SHADOW_DEBUG (at least make it compilable) in shadow.c.
in with xm-test in changeset 7634. It also adds an "autogen" script
that re-creates these files.
The auto-generated files really don't need to be in the tree, as they
should be generated by the user on the machine where they plan to run
xm-test.
Signed-off-by: Dan Smith <danms@us.ibm.com>
starting with #!) found in the example directory under tools. It
further changes the installation path of the udev rules to comply with
what debian does: It places the rules file in /etc/udev/ und creates a
symlink to it in /etc/udev/rules.d.
Signed-off-by: Tobias Hunger <tobias@aquzul.com>
2. Change the MEM_PER_DOM amount in 11_create_concurrent to 24MB, so
that the test will run on x86_64.
3. Increase the number of DomUs created in 12_create_concurrent to 5
4. Fix a logic error in 01_unpause
5. Add a test 06_help that checks all xm commands with 0-10 arguments
to make sure none of them traceback with varying argument counts.
Signed-off-by: Dan Smith <danms@us.ibm.com>
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>
flag is now associated with the pgd rather than the mm -- this
avoids a race where a pgd is allocated from the pgd_cache but,
before it gets associated with an mm, the kernel suspends itself.
At this point the kernel mappings will not get rewritten when the
kernel is resumed, and the system will fail.
A further advantage is that the code is slightly simpler and less
invasive (no changes to mm_context for example).
Signed-off-by: Keir Fraser <keir@xensource.com>
