Sponsored Content
Full Discussion: Xen Virtual Manager
Operating Systems Linux SuSE Xen Virtual Manager Post 302860611 by jgt on Sunday 6th of October 2013 06:14:59 PM
Old 10-06-2013
I installed the application; re-booted the new kernel. I suppose at this point I might as well ask: do the virtual installations have to have device drivers for the installed hardware?
 

4 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Problem regarding :::: Xen virtual console

hello, I am using fedora core 6. and there is Xen Virtual Console installed in my system ....due to which I am not able to use my serial ports....... What is thi Xen virtual console and what it does????? So, Can I unintall this Xen virtual Console..... or any method so that I can use my... (3 Replies)
Discussion started by: arunchaudhary19
3 Replies

2. Linux

LVM (volume manager) and virtual disks

:eek: Hi guys, I'm pulling my hair out over this one. I am trying to set up a virtual server environment. ( I am using VirtualBox, but I think this is irrelevant to this problem.) I have downloaded a pre-packaged Linux virtual disk, with which I have successfully started a virtual instance of a... (4 Replies)
Discussion started by: otheus
4 Replies

3. Red Hat

error on virtual manager

In red hat linux server 6 I start up virtual manager and I get below error prompt. Package reuired for KVM usage The following packages are not installed qemu-kvm These are required to create KVM guests locally. Would you like to install them now . I press yes but the package cannot... (0 Replies)
Discussion started by: chuikingman
0 Replies

4. Red Hat

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool Hi, I don't seem to have the Virtual Machine Manager Desktop tool set up on my RHEL6 Machine. The Linux machine runs off VMWare player and I'm not sure whether it is a VMWare software issue or a problem with the RHEL6... (2 Replies)
Discussion started by: accipiter1
2 Replies
PCINITRD(8)						      System Manager's Manual						       PCINITRD(8)

NAME
pcinitrd - create a PCMCIA initrd ram disk image SYNOPSIS
pcinitrd [-v] [-a] [--all] [-d alternate-root] [--dir=alternate-root] [-r kernel-release] [--release=kernel-release] [-s image-size] [--size=image-size] [-u] [--update] initrd-image [modules ...] DESCRIPTION
The pcinitrd script creates an initrd ram disk image for booting with the root filesystem on a PCMCIA device. If the target is a block special device (i.e., /dev/fd0), then the initrd image is created on that device. If the target does not already exist or if it is an ordinary file, then pcinitrd will create the image file using the ``loopback'' device. Modules are specified with paths relative to /lib/modules/[kernel-release]. The core PCMCIA modules (pcmcia/pcmcia_core and pcmcia/ds) will automatically be installed in the target image. All other device-specific modules need to be listed on the command line, along with the appropriate socket driver (pcmcia/i82365.o or pcmcia/tcic.o). Alternatively, if -a is specified, then all available PCMCIA socket drivers and block device drivers will be included in the image. Additional files to be copied to the initrd image may also be listed on the command line. Executable programs will be installed in /bin, shared libraries will be installed in /lib, device files will be installed in /dev, and any other files will be placed in /etc. The startup script in the resulting image, linuxrc, may need to be customized for a particular system. It contains the same variable defi- nitions as the normal PCMCIA startup scripts (i.e., PCIC=, PCIC_OPTS=, and CORE_OPTS= variables). The /etc/config.opts file may also need to be edited. Any changes to linuxrc or config.opts will be preserved if pcinitrd is executed in ``update'' mode. Another feature of the generated linuxrc is that if the DEBUG variable is set to a non-blank string at the boot prompt, then cardmgr will echo all its status messages to the console, and after linuxrc executes, it will fire up a shell on the console. This can be helpful for debugging initrd problems. However, few commands are available in the normal initrd environment. OPTIONS
-v Verbose mode. Identify files as they are copied. -a, --all Install all socket drivers and block-style PCMCIA device drivers, including memory card, SCSI card, and fixed-disk drivers. This is mainly intended for use by package maintainers. -d alternate-root, --dir=alternate-root Specifies an alternate directory tree to search for all the files used to put together the initrd image. This may be helpful for running pcinitrd after booting from an installation or rescue diskette. -r kernel-release, --release=kernel-release Specifies the kernel release number (i.e., 2.0.28) to use when looking for modules in /lib/modules. The default is the release of the running kernel. -s image-size, --size=image-size Specifies the filesystem size to create on the target file or device, in 1k blocks. The default is 2400. -u, --update Update mode: updates cardmgr and all the kernel modules in an existing initrd image, but does not modify other files. AUTHOR
David Hinds - dahinds@users.sourceforge.net SEE ALSO
pcmcia(5), cardmgr(8), lilo(8). pcmcia-cs $Date PCINITRD(8)
All times are GMT -4. The time now is 12:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy