02-16-2019
Sounds like it is more of a Hyper-V problem than a Red-Hat issue.
It may well be that Hyper-V didn't support newer technology that
Red-Hat may have implemented at the time.
When running any guest OS through a hypervisor, you should try
the hypervisor forums first. This isn't a Windows 10 forum.
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i'm having 2 problems.
1. the system will always look to boot from the net. i've changed the prom settings so that it boots from the disk, by entering "setenv boot-device disk0:3", but the system still seems to want to boot from the net.
2. i replaced my creator3d with an elitem6 and i did... (6 Replies)
Discussion started by: xyyz
6 Replies
2. UNIX for Advanced & Expert Users
hardware on my first FreeBSD server has crashed. i was planning on
swapping the HD into another machine, booting the generic kernel and then
custom tailoring it to the new machine specs.
however, i'm having a problem.
the new machine is using a promise ultra100 card. i don't have any... (2 Replies)
Discussion started by: xyyz
2 Replies
3. Solaris
I have a client with a V1280 onsite and it is having boot problems. Below is the message it is returning when trying to boot. Is this something that anybody has run into, or that you might be able to shed some light on?
{0} ok boot
/ssm@0,0/pci@18,700000/ide@3/cdrom@0,0:f
SunOS Release 5.9... (3 Replies)
Discussion started by: xcwhitex
3 Replies
4. SCO
Hello those more knowledgeable than I:
I have been trying to get xp and SCO to coexist on the same system. I have tried several different ways to make both work, here's the list:
-install xp, image it, move the partition to the end of drive, verify it boots, image again,
-boot off of SCO... (6 Replies)
Discussion started by: stay0ut
6 Replies
5. Solaris
I have a pentium IV with 512 MB ram and 80 GB HDD.
I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies
6. Solaris
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies
7. Solaris
I 'm trying to configure a WAN boot server on Solaris10 x86 for sparc clients ..
when i try to set up the server m getting following error
./setup_install_server -w /var/apache2/htdocs/wanboot10/wpath /var/apache2/htdocs/wanboot10/ipath
ERROR: Cannot make WAN boot Image file on this... (6 Replies)
Discussion started by: fugitive
6 Replies
CPU(1) General Commands Manual CPU(1)
NAME
cpu - connection to cpu server
SYNOPSIS
cpu [ -h server ] [ -c cmd args ... ]
DESCRIPTION
Cpu starts an rc(1) running on the server machine, or the machine named in the $cpu environment variable if there is no -h option. Rc's
standard input, output, and error files will be /dev/cons in the name space where the cpu command was invoked. Normally, cpu is run in an
81/2(1) window on a terminal, so rc output goes to that window, and input comes from the keyboard when that window is current. Rc's cur-
rent directory is the working directory of the cpu command itself.
The name space for the new rc is an analogue of the name space where the cpu command was invoked: it is the same except for architecture-
dependent bindings such as /bin and the use of fast paths to file servers, if available.
If a -c argument is present, the remainder of the command line is executed by rc on the server, and then cpu exits.
The name space is built by running /usr/$user/lib/profile with the root of the invoking name space bound to /mnt/term. The service envi-
ronment variable is set to cpu; the cputype and objtype environment variables reflect the server's architecture.
FILES
The name space of the terminal side of the cpu command is mounted on the CPU side on directory /mnt/term.
SOURCE
/sys/src/cmd/cpu.c
SEE ALSO
rc(1), 81/2(1)
BUGS
Binds and mounts done after the terminal lib/profile is run are not reflected in the new name space.
CPU(1)