I am having a virtualization problem with a machine that runs on Fedora Core 4. I created a IDE virtual machine running FEDORA CORE 4. Then I restored the original servers partition one by one. Everything works until I restore root. Then When I load up I get
And I get a kernel panic.
The original machine may have run on a SATA box so I am thinking the virtual machine now things there is a sata drive when it is a IDE drive: VMWARE does not give option for a SATA drive.
Is there something I can do?
Last edited by Yogesh Sawant; 05-14-2009 at 02:14 AM..
Reason: added code tags
Hello all,
For my internship assignment I have a Sunfire 880 at my disposal for comparing virtualization with the normal mostly Windows based servers in the company.
Are there any applications like VirtualBox or Vmware that can be used on a Sparc-system equipped with Solaris 10?
I tried... (1 Reply)
Hello to all
In my organization we want to pass to move the systems to an virtualized environment, nevertheless, considering the absence of resources, the idea is to acquire the versers and that the department (I) do the facilities, tests, etc. Wearing out the possible minimal cost in... (1 Reply)
Hi,
My script needs to find out if it is running on a virtual machine.
If it is then it needs to find out.
1 . The number of virtual processors.
2 . Actual physical box onto which the virtual machine is hosted.
3 .Processors on the physical machine.
Actually there are some commands like... (1 Reply)
Hello peopel
I am interesting in implement a virtualization system on HP-UX v3. I have some Integrity servers with this OS installed but I want to virtualize one of them because I have a problem that has no solution in HP-UX and I have to install RedHat for this reason.
Then I don't know what... (1 Reply)
Hi everyone.
Last week we have some hardware problems in our Unixware 7 server, and i decided to change this physical machine into a virtual machine.
The scenario is:
architecture=IA32
bus_types=PCI2.10,ISA,PnP1.0
hostname=tecsup2uw.tecsupaqp.edu
hw_provider=Generic AT... (1 Reply)
Hi everyone,
I have ten servers with solaris (diffrent versions).
there is solaris 10, solaris 6 and solaris 8.
some are SPARC and some are x86
I would like to move them to one server so they all will be virtual.
Is it possible? how? (4 Replies)
Hello admins and gurus
I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Got tired of messing around with real hardware old and others..
Decided to spend some $$ for a QUAD-core dual cpu laptop with 8 gig of ram and 1 TB disk space..
running VMware workstation 10 on windows 8.0 , with a pair of solx86 vcs 5.1 cluster and a pair of rhel 6.4 vcs 6.x cluster..
... (0 Replies)
Hello All,
To start with, I am not an expert of solaris and VMs. Unfortunately, I can't find a direct or understandable (at least to me) answer to my question online. So please, excuse me if my question will sound dumb to you. :o
We have 2 remaining solaris 8 servers are on sparc... (9 Replies)
Discussion started by: forextrafun
9 Replies
LEARN ABOUT MINIX
fd
FD(4) Kernel Interfaces Manual FD(4)NAME
fd - floppy disk
DESCRIPTION
The fd* devices refer to the Floppy disk driver using the NEC PD765 floppy disk controller. These diskettes are arrays of 512 byte sec-
tors, although Minix always works with two sectors at a time due to its 1024 byte block size. You can read or write any number of bytes
however, Minix takes care of cutting and pasting incomplete blocks together.
The driver is normally configured for two floppy disk devices fd0 and fd1. It can handle two more, but it is unlikely that the average PC
can.
On the first access to an fd device (by open(2) or mount(2)), the driver will execute a series of read tests to determine the floppy type.
This works ok for all floppy types except the true 360k type, because it is indistinguishable from the 720k type. This only means that the
size of the floppy is not estimated right.
Bits 2-6 of the minor device number may be set to the floppy disk type to make it known to the driver what type of diskette it is reading
or writing. The non-auto devices should be used for formatting, or when one wants to be absolutely sure that the device is accessed right.
These devices exist for drive 0:
type device minor media
0 fd0 0 autodetect
1 pc0 4 360k, 5.25"
2 at0 8 1.2M, 5.25"
3 qd0 12 360k in a 720k, 5.25" drive
4 ps0 16 720k, 3.5"
5 pat0 20 360k in a 1.2M, 5.25" drive
6 qh0 24 720k in a 1.2M, 5.25" drive
7 PS0 28 1.44M, 3.5"
Type 4 may also be used for the rarely seen 720k, 5.25" floppies (type 2 made them obsolete fast.) Note that these "types" only describe
the floppies from a software point of view, type 1 and 4 drives use the same parameters.
If the format bit (bit 7) is set, then the driver interprets write commands as track formatting requests. This is used by the format(1)
command.
If the type bits are set to 28, 29, 30, or 31, then the driver uses a partition table found in sector 0 to partition the floppy. The par-
titions of fd0 may be accessed as fd0a through fd0d. See hd(4) for a description of the partition table, and associated ioctl commands.
FILES
/dev/fd[0-3], /dev/pc[0-3], /dev/at[0-3], /dev/qd[0-3], /dev/ps[0-3], /dev/pat[0-3], /dev/qh[0-3], /dev/PS[0-3], /dev/fd[0-3][a-d]
SEE ALSO format(1), hd(4), part(8).
BUGS
The driver does not know the size of a 360k diskette in a 360k 5.25" drive, because it uses the 720k parameters for it. So it will happily
try to read past the end making all kinds of interesting noises. It's a good thing these drives are practically obsolete.
The partition table is only read when the drive motor is off and only for an auto or partition device. The driver assumes that a floppy in
a drive with a running motor can't have been replaced all of a sudden.
AUTHOR
Kees J. Bot (kjb@cs.vu.nl)
FD(4)