Sponsored Content
Operating Systems OS X (Apple) 12-Core MacPro (2013) kernel_task over 1200% Post 303033961 by wisecracker on Monday 15th of April 2019 10:43:23 AM
Old 04-15-2019
Hi Neo...

Having dealt with Apple with my old MacBook Pro, under extended warranty, the unit was effectively fixed the same day, new HDD required.
(My choice to pick up the next day.)
IIRC their diagnostics was through the "ethernet" port on my old machine and I was relatively impressed with how it worked.
(Said machine runs dedicated Linux now.)

I have heard NOT particularly good reports of some APPLE outlets but ours here in Leicester, UK was good.
YMMV in your area of the USA.

Good luck with your serious tool, and I hope all is fixed at a sensible price soon...

Bazza.
This User Gave Thanks to wisecracker For This Post:
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Can I use a general printer(HP LaserJet 1200) on solaris?

can it be used? how to config it? thanks (4 Replies)
Discussion started by: cloudsmell
4 Replies

2. OS X (Apple)

kernel_task help

I installed 10.5 (Leopard) on my G4 733 Mhz (after minor tampering with the install package, just switched a boolean FALSE to TRUE). Everything works fine after startup, but once I sleep the computer and wake it back up, kernel_task starts using at as much CPU runtime as it can, as in past 90%.... (0 Replies)
Discussion started by: peter.story
0 Replies

3. Solaris

T5140 CPU Speed is 1200 Mhz or 1165 Mhz?

Hi bros, CPU speed of Sun Sparc Enterprise T5140 in data sheet is 1200 Mhz. Why it shows in "prtdiag -v" command each thread just has speed at 1165 Mhz. Thank you, tien86 (4 Replies)
Discussion started by: tien86
4 Replies

4. Hardware

2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1

Hey MacPro users. I just bought a refurbished 13-Core MacPro with 64GB of RAM for a cybersecurity gaming project I'm working on. Could not wait for the new MacPro in 2019, so this will have to do: 2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1 Now, I'm... (0 Replies)
Discussion started by: Neo
0 Replies

5. OS X (Apple)

DiskSpeedTest 256GB OEM v. 960GB Transcend 855 SSD MacPro 2013, 12-Core, 64GB RAM

Before Upgrade: https://www.unix.com/members/1-albums177-picture1220.png After Upgrade: https://www.unix.com/members/1-albums177-picture1221.png (0 Replies)
Discussion started by: Neo
0 Replies

6. OS X (Apple)

Warning! Upgrade to Catalina 10.15.3 Crashes MacPro (2013) - Will Not Boot !

WARNING! Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3. After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed. Now, I'm in the process of a 15 hour restore from my last time machine backup. I'm not very happy with... (3 Replies)
Discussion started by: Neo
3 Replies
libguestfs-make-fixed-appliance(1)			      Virtualization Support				libguestfs-make-fixed-appliance(1)

NAME
libguestfs-make-fixed-appliance - Make a "fixed appliance" for libguestfs SYNOPSIS
libguestfs-make-fixed-appliance [--options] OUTPUTDIR libguestfs-make-fixed-appliance [--options] --xz DESCRIPTION
libguestfs-make-fixed-appliance lets you make a pre-built binary appliance for libguestfs. Note that ordinary users should not need to run this tool. Some reasons why you might want to use this include: o You want to make a self-contained libguestfs appliance that can be copied to another machine or platform that doesn't support supermin(8). o You have multiple users on the same machine and want to avoid the storage duplication and start-up overhead of having multiple cached copies of the appliance. o You want to have very predictable performance from libguestfs (see guestfs-performance(1)). For deeper understanding of why you might need this tool, read the section "FIXED APPLIANCE" below. Instead of running this tool, you can download fixed appliances from http://libguestfs.org/download/binaries/appliance/. These appliances were made using this tool. There are two ways to use this tool. o Specify an output directory, for example: libguestfs-make-fixed-appliance /usr/local/lib/guestfs/appliance The output directory is created if it does not exist. Four files are created in this directory: <OUTPUTDIR>/kernel <OUTPUTDIR>/initrd <OUTPUTDIR>/root <OUTPUTDIR>/README.fixed Note that "OUTPUTDIR/root" is a sparse file, so take care when copying it. You can then run libguestfs (possibly after copying this directory to another machine) by setting the environment variable LIBGUESTFS_PATH to "OUTPUTDIR". o The alternative method is to use the --xz option to create a compressed tarball: libguestfs-make-fixed-appliance --xz This creates a tarball in the current directory called: appliance-<VERSION>.tar.xz (where "VERSION" is the version of libguestfs). The tarball contains the four files: appliance/kernel appliance/initrd appliance/root appliance/README.fixed Note that "appliance/root" is a sparse file, so take care when copying it. OPTIONS
--help Display short usage information and exit. -V --version Display the version number and exit. --xz Instead of creating the appliance in an output directory, create a compressed tarball of the appliance in the current directory called "appliance-VERSION.tar.xz" where "VERSION" is the version of libguestfs. Using --xz can take some time. If working normally, the tool is completely silent when it is running. FIXED APPLIANCE
When libguestfs (or libguestfs tools) are run, they search a path looking for an appliance. The path is built into libguestfs, or can be set using the "LIBGUESTFS_PATH" environment variable. Normally a supermin appliance is located on this path (see "SUPERMIN APPLIANCE" in supermin(8)). libguestfs reconstructs this into a full appliance by running supermin-helper(8). However, a simpler "fixed appliance" can also be used. libguestfs detects this by looking for a directory on the path containing four files called "kernel", "initrd", "root" and "README.fixed" (note the "README.fixed" file must be present as well). If the fixed appliance is found, libguestfs skips supermin entirely and just runs qemu with the kernel, initrd and root disk from the fixed appliance. Thus the fixed appliance can be used when a platform or Linux distro does not support supermin. You build the fixed appliance on a platform that does support supermin, and copy it over, and use that to run libguestfs. LICENSING
The fixed appliance is a complete Linux binary distro. If you distribute it, you may need to distribute corresponding source files to remain in legal compliance with the licenses of the software in the appliance (such as the GNU General Public License). EXIT STATUS
libguestfs-make-fixed-appliance returns 0 if the appliance was built without errors. ENVIRONMENT VARIABLES
For the full list of environment variables which may affect libguestfs, please see the guestfs(3) manual page. SEE ALSO
guestfs(3), supermin(8), supermin-helper(8), xz(1), http://libguestfs.org/, http://qemu.org/. AUTHORS
Richard W.M. Jones ("rjones at redhat dot com") COPYRIGHT
Copyright (C) 2009-2013 Red Hat Inc. LICENSE
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. BUGS
To get a list of bugs against libguestfs, use this link: https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=Virtualization+Tools To report a new bug against libguestfs, use this link: https://bugzilla.redhat.com/enter_bug.cgi?component=libguestfs&product=Virtualization+Tools When reporting a bug, please supply: o The version of libguestfs. o Where you got libguestfs (eg. which Linux distro, compiled from source, etc) o Describe the bug accurately and give a way to reproduce it. o Run libguestfs-test-tool(1) and paste the complete, unedited output into the bug report. libguestfs-1.22.6 2013-08-24 libguestfs-make-fixed-appliance(1)
All times are GMT -4. The time now is 11:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy