[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Trying to compose my first Xen config file from documentation at xen


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Matthew Hoggan <mehoggan@xxxxxxxxx>
  • Date: Sat, 5 Jun 2010 20:04:43 -0700
  • Cc: Matthew Hoggan <mehoggan@xxxxxxxxx>
  • Delivery-date: Sat, 05 Jun 2010 20:06:23 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=sxrNqA9ITnrchnQOYYRPYZd9DzPdtYe3v7kfBW7RuayPzJzlnOoO00ZJAFyZwaVPv7 c7fWgBfuRVIE6dj1RtVhl9+wBBJK6f9ORHySLA+9knVCaI1JYmoz7wRLc1KLeZPel55s SSM2jkYIigX7S20a9Epkmr9Cg3cClfWLWDD3Y=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Okay so I am running RHEL5 with the Xen-Kernel already compiled in.

[root@laptop centos]# uname -a
Linux laptop.hom 2.6.18-128.el5xen #1 SMP Wed Dec 17 12:22:24 EST 2008 i686 i686 i386 GNU/Linux

I am trying to follow the documentation found at (pg 23 out of 110) to create a domU from a config file:

http://bits.xensource.com/Xen/docs/user.pdf

I have two specific questions at the moment. First let me post my python config file:

 #  -*- mode: python; -*-
#============================================================================
# Python setup script for 'xm create'. Can create multiple domains with
#
# xm create -c xm.conf vmid=1
# xm create -c xm.conf vmid=2
# xm create -c xm.conf vmid=3
#
# The vmid is purely a script variable, and has no effect on the the domain
# id assigned to the new domain.
#============================================================================

# xm_varsefined automatically, use xm_vars.var() to define a variable.

# This function checks that 'vmid' has been given a valid value.
# It is called automatically by 'xm create'.
def vmid_check(var, val):
    val = int(val)
    if val <= 0:
        raise ValueError
    return val

# Define the 'vmid' variable so that 'xm create' knows about it.
xm_vars.var('vmid', use="Virtual machine id. Integer greater than 0.", check=vmid_check)

# Check the defined variables have valid values..
xm_vars.check()

# This is the path to the Xen Kernel used by the hypervisor (host OS)
kernel = "/boot/vmlinuz-2.6.18-128.el5xen"

# This is the amount of virtual memory the domU will use (memory > 32mb)
memory = 64

# A name for the new domain. All domains have to have different names,
# so we use the vmid to create a name.
name = "VM%d" % vmid


# Define network interfaces.
vif = [ 'mac=00:16:3e:00:00:11, bridge=xenbr0' ]

# Define the disk devices you want the domain to have access to, and
# r for read-only, w for read-write.
disk = [ 'phy:hda2,hda2,w' ]

#create a root partition
root = "/dev/hda2 ro"

# Set if you want dhcp to allocate the IP address.
dhcp="dhcp"

# "destroy",        meaning that the domain is cleaned up as normal;
# "restart",        meaning that a new domain is started in place of the old
#                   one;
>on_reboot   = 'restart'
on_crash    = 'restart'

I am not too sure on what to specify for the hard drive variable, I only have one drive on my test computer at the moment and it is broken down into a LVM and the /boot partition on a single drive. Do I have to split the LVM up? Here is the output from df command.

[root@laptop centos]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      140G  2.7G  130G   3% /
/dev/hda1              99M   13M   81M  14% /boot
tmpfs                 1.3G     0  1.3G   0% /dev/shm
192.168.1.1:/mnt/Internal_Storage/geogadmin_files
                      917G   12G  860G   2% /mnt/nfs
none                  1.3G   56K  1.3G   1% /var/lib/xenstored

When I use the xm -create command I get the following error at the bottom (in red). I am assuming this is related to the drive variable. Please help me understand.

[root@laptop centos]# xm create -c xm.conf vmid=1
Using config file "./xm.conf".
Started domain VM1
Linux version 2.6.18-128.el5xen (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Dec 17 12:22:24 EST 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004800000 (usable)
0MB HIGHMEM available.
72MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 18432
Kernel command line:  ip=:1.2.3.4::::eth0:dhcp root=/dev/hda2 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0744000 soft=c0724000
PID hash table entries: 512 (order: 9, 2048 bytes)
Xen reported: 2792.998 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Software IO TLB disabled
vmalloc area: c5000000-f4ffe000, maxmem 2d7fe000
Memory: 60560k/73728k available (2124k kernel code, 4908k reserved, 877k data, 176k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6988.97 BogoMIPS (lpj=13977952)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 13k freed
Brought up 1 CPUs
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06F2AA0 could not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06F2AA0 could not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1275749967.357:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 31B497468CDD12CF
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Linux version 2.6.18-128.el5xen (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)) #1 SMP Wed Dec 17 12:22:24 EST 2008
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004800000 (usable)
0MB HIGHMEM available.
72MB LOWMEM available.
NX (Execute Disable) protection: active
ACPI in unprivileged domain disabled
Built 1 zonelists.  Total pages: 18432
Kernel command line:  ip=:1.2.3.4::::eth0:dhcp root=/dev/hda2 ro
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c0744000 soft=c0724000
PID hash table entries: 512 (order: 9, 2048 bytes)
Xen reported: 2792.998 MHz processor.
Console: colour dummy device 80x25
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Software IO TLB disabled
vmalloc area: c5000000-f4ffe000, maxmem 2d7fe000
Memory: 60560k/73728k available (2124k kernel code, 4908k reserved, 877k data, 176k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 6988.97 BogoMIPS (lpj=13977952)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 6144K
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 13k freed
Brought up 1 CPUs
Grant table initialized
NET: Registered protocol family 16
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06F2AA0 could not acquire Mutex [2] [20060707]
No dock devices found.
ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread C06F2AA0 could not acquire Mutex [2] [20060707]
Brought up 1 CPUs
PCI: setting up Xen PCI frontend stub
ACPI: Interpreter disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
PCI: System does not support PCI
PCI: System does not support PCI
NetLabel: Initializing
NetLabel:  domain hash size = 128
NetLabel:  protocols = UNLABELED CIPSOv4
NetLabel:  unlabeled traffic allowed by default
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 2048)
TCP reno registered
audit: initializing netlink socket (disabled)
type=2000 audit(1275749967.357:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
alg: No test for crc32c (crc32c-generic)
ksign: Installing public key data
Loading keyring
- Added public key 31B497468CDD12CF
- User ID: Red Hat, Inc. (Kernel Module GPG key)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
pci_hotplug: PCI Hot Plug PCI Core version: 0.5
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
Linux agpgart interface v0.101 (c) Dave Jones
RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize
Xen virtual console successfully installed as xvc0
Event-channel device installed.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx
ide-floppy driver 0.99.newide
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
PNP: No PS/2 controller found. Probing ports directly.
i8042.c: No controller found.
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI No-Shortcut mode
XENBUS: Device with no driver: device/vbd/770
XENBUS: Device with no driver: device/vif/0
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "hda2" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)



--
Matthew Hoggan
mehoggan@xxxxxxxxx
mbhoggan@xxxxxxxxxxx
(818)980-3603 (home)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.