Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
emulab-devel
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
emulab
emulab-devel
Commits
297cea0d
Commit
297cea0d
authored
20 years ago
by
Mike Hibler
Browse files
Options
Downloads
Patches
Plain Diff
Warn about imageunzip running out of memory.
parent
bcc9b295
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/customize-image.txt
+7
-0
7 additions, 0 deletions
doc/customize-image.txt
with
7 additions
and
0 deletions
doc/customize-image.txt
+
7
−
0
View file @
297cea0d
...
...
@@ -56,6 +56,13 @@ We will assume the machine is called "pc1" in the following directions.
(or use "/dev/da0" for SCSI). Image loading should take anywhere from
45 seconds, to several minutes.
If the ssh returns with "Killed" then imageunzip ran out of memory.
By default, imageunzip will consume memory without bound for buffering
of pending disk writes. In this case, retry the imageunzip with
"-W <num-MB>" where <num-MB> is a number of MB maximum to use for
disk buffering. If the node you are loading has 512MB of memory, try
a number like 300.
Now you can begin customizing the FreeBSD and Linux partitions.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment