10-06-2013
Are you running paravirtualised or full-virtualised (HVM, hardware assisted virtualisation)?
You do know that you need to boot Xens own (patched) kernel first, because it can't run from a standard kernel, don't you?
Sorry, if i state the obvious, i just want to make sure the simple issues are all covered.
I hope this helps.
bakunin
4 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
: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
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
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
LEARN ABOUT CENTOS
mkbootdisk
MKBOOTDISK(8) System Manager's Manual MKBOOTDISK(8)
NAME
mkbootdisk - creates a stand-alone boot floppy for the running system
SYNOPSIS
mkbootdisk [--version] [--noprompt] [--verbose]
[--device devicefile] [--size size]
[--kernelargs <args>] [--iso] kernel
DESCRIPTION
mkbootdisk creates a boot floppy appropriate for the running system. The boot disk is entirely self-contained, and includes an initial
ramdisk image which loads any necessary SCSI modules for the system. The created boot disk looks for the root filesystem on the device sug-
gested by /etc/fstab. The only required argument is the kernel version to put onto the boot floppy.
OPTIONS
--device devicefile
The boot image is created on devicefile. If --device is not specified, /dev/fd0 is used. If devicefile does not exist mkinitrd cre-
ates a 1.44Mb floppy image using devicefile as the filename.
--noprompt
Normally, mkbootdisk instructs the user to insert a floppy and waits for confirmation before continuing. If --noprompt is specified,
no prompt is displayed.
--verbose
Instructs mkbootdisk to talk about what it's doing as it's doing it. Normally, there is no output from mkbootdisk.
--iso Instructs mkbootdisk to make a bootable ISO image as devicefile.
--version
Displays the version of mkbootdisk and exits.
--kernelargs args
Adds args to the arguments appended on the kernel command line. If this is not specified mkbootdisk uses grubby to parse the argu-
ments for the default kernel from grub.conf, if possible.
--size size
Uses size (in kilobytes) as the size of the image to use for the boot disk. If this is not specified, mkbootdisk will assume a
standard 1.44Mb floppy device.
SEE ALSO
grubby(8) dracut(8)
AUTHOR
Erik Troan <ewt@redhat.com>
4th Berkeley Distribution Tue Mar 31 1998 MKBOOTDISK(8)