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

[Xen-users] Re: fail connect console to Domain-1


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Shu Hung (Koala)" <koalay.dg21@xxxxxxxxx>
  • Date: Fri, 20 Jan 2006 13:38:50 +0800
  • Delivery-date: Fri, 20 Jan 2006 05:46:55 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=fXIH57MIs0lQqJPJOZUdG4v4rl04FOapzbmzlID4YvMNUzNoFZHNaXNe53Uwh3Mjo5PKULVrn3m1lFJgnf6t0PDgc+En7SOMPkm8GoQ5wYj1WIybL4bOk8vNdbtzDbKuZHjeoA978WiNo6YNuLDS4rkc8RkbDG4uvBBTSjbq0ys=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

Seems I have worked it out.
It should be problem using udev
I missed the creation of /dev nodes

According to FedoraXenQuickstart , I should
(1) mount the domU image to /mnt
(2) "for i in console null zero ; do /sbin/MAKEDEV -d /mnt/dev -x $i ; done"

All things are working after that

Koala

2006/1/20, Shu Hung (Koala) <koalay.dg21@xxxxxxxxx>:
Hello,

I've installed a new machine purely for Xen virtual machine test.
When I start my unprivileged domain, I get error and cannot connect the console to it.
This is the messages as I started the domain:

------------
[root@cannan xen]# xm create -c /etc/xen/fedora
Using config file "/etc/xen/fedora".
Started domain Domain-1
Linux version 2.6.12-1.1454_FC4xenU (bhcompile@xxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Fri Sep 9 00:45:34 EDT 2005
BIOS-provided physical RAM map:
 Xen: 0000000000000000 - 0000000004000000 (usable)
0MB HIGHMEM available.
64MB LOWMEM available.
Using x86 segment limits to approximate NX protection
IRQ lockup detection disabled
Built 1 zonelists
Kernel command line:  root=/dev/sda1 3
Initializing CPU#0
CPU 0 irqstacks, hard=c03b5000 soft=c0395000
PID hash table entries: 512 (order: 9, 8192 bytes)
Xen reported: 855.732 MHz processor.
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
vmalloc area: c4800000-fb7fe000, maxmem 34000000
Memory: 60416k/65536k available (1846k kernel code, 4992k reserved, 518k data, 156k init, 0k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 256K (64 bytes/line)
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... disabled
CPU0: AMD Athlon(tm) Processor stepping 02
Total of 1 processors activated (1703.93 BogoMIPS).
Brought up 1 CPUs
NET: Registered protocol family 16
store_evtchn = 1
xen_mem: Initialising balloon driver.
Grant table initialized
audit: initializing netlink socket (disabled)
audit(1137724616.307:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
SELinux:  Registering netfilter hooks
Initializing Cryptographic API
ksign: Installing public key data
Loading keyring
- Added public key ECA7AC659F473636
- 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
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
Xen virtual console successfully installed as tty1
Event-channel device installed.
xen_blk: Initialising virtual block device driver
Registering block device major 8
xen_net: Initialising virtual ethernet driver.
xen_net: Using grant tables.
md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
NET: Registered protocol family 2
IP: routing cache hash table of 256 buckets, 4Kbytes
TCP established hash table entries: 4096 (order: 4, 65536 bytes)
TCP bind hash table entries: 4096 (order: 3, 49152 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
Initializing IPsec netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
kjournald starting.  Commit interval 5 seconds
EXT3 FS on sda1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem).
Freeing unused kernel memory: 156k freed
Warning: unable to open an initial console.
 
  ***************************************************************
  ***************************************************************
  ** WARNING: Currently emulating unsupported memory accesses  **
  **          in /lib/tls libraries. The emulation is very     **
  **          slow. To ensure full performance you should      **
  **          execute the following as root:                   **
  **          mv /lib/tls /lib/tls.disabled                    **
  ** Offending process: init (pid=1)                           **
  ***************************************************************
  ***************************************************************
 
Continuing...

security:  3 users, 6 roles, 888 types, 109 bools
security:  55 classes, 236553 rules
SELinux:  Completing initialization.
SELinux:  Setting up existing superblocks.
SELinux: initialized (dev sda1, type ext3), uses xattr
SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts
SELinux: initialized (dev mqueue, type mqueue), uses transition SIDs
SELinux: initialized (dev hugetlbfs, type hugetlbfs), uses genfs_contexts
SELinux: initialized (dev devpts, type devpts), uses transition SIDs
SELinux: initialized (dev eventpollfs, type eventpollfs), uses genfs_contexts
SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs
SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts
SELinux: initialized (dev pipefs, type pipefs), uses task SIDs
SELinux: initialized (dev sockfs, type sockfs), uses task SIDs
SELinux: initialized (dev cpuset, type cpuset), not configured for labeling
SELinux: initialized (dev proc, type proc), uses genfs_contexts
SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
Restarting system.
[root@cannan xen]# xm list
Name              Id  Mem(MB)  CPU VCPU(s)  State  Time(s)
Domain-0           0      123    0      1   r----     55.6
Domain-1           4       64    0      1   ---s-     14.9
------------


The SElinux part is really strange since I should have disabled selinux in the domain by configuring /etc/sysconfig/selinux in the image file. It is even more wield to see by " xm list" that the domain is actually running.

I then examined the xend.log:
------------
[root@cannan xen]# tail -20 /var/log/xend.log                                                                                               
[2006-01-20 10:36:54 xend] INFO (XendRoot:141) EVENT> xend.domain.create ['Domain-1', 4]
[2006-01-20 10:36:54 xend] INFO (image:217) buildDomain os=linux dom=4 vcpus=1
[2006-01-20 10:36:54 xend] DEBUG (image:255) dom            = 4
[2006-01-20 10:36:54 xend] DEBUG (image:256) image          = /boot/vmlinuz- 2.6.12-1.1454_FC4xenU
[2006-01-20 10:36:54 xend] DEBUG (image:257) store_evtchn   = 1
[2006-01-20 10:36:54 xend] DEBUG (image:258) console_evtchn = 2
[2006-01-20 10:36:54 xend] DEBUG (image:259) cmdline        =  root=/dev/sda1 3
[2006-01-20 10:36:54 xend] DEBUG (image:260) ramdisk        =
[2006-01-20 10:36:54 xend] DEBUG (image:261) flags          = 0
[2006-01-20 10:36:54 xend] DEBUG (image:262) vcpus          = 1
[2006-01-20 10:36:55 xend] INFO (xsobj:326) DBMap>introduceDomain> 4 29444 <EventChannel dom1:0:17 dom2:4:1> /domain/a602f3b6-4ff0-4539-bbd9-dca25de86f3d
[2006-01-20 10:36:55 xend] DEBUG (XendDomainInfo:698) writing key availability=online to path /cpu/0 in store
[2006-01-20 10:36:55 xend] WARNING (XendDomainInfo:1100) Unknown config field boot
[2006-01-20 10:36:55 xend] DEBUG (blkif:24) exception looking up device number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
[2006-01-20 10:36:55 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy
[2006-01-20 10:36:55 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy
[2006-01-20 10:36:55 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy
[2006-01-20 10:36:55 xend] ERROR (process:37) [block-file] ioctl: LOOP_SET_FD: Device or resource busy
[2006-01-20 10:36:55 xend] ERROR (XendDomainInfo:443) ['vif', ['mac', 'aa:00:00:00:00:11'], ['bridge', 'xen-br0']]
[2006-01-20 10:36:55 xend] INFO (XendRoot:141) EVENT> xend.domain.unpause ['Domain-1', 4]

------------


You may want to see my settings.

grub.conf
------------
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/hda2
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.12-1.1454_FC4xen0)
        root (hd0,0)
        kernel /xen.gz dom0_mem=131072
        module /vmlinuz-2.6.12-1.1454_FC4xen0 ro root=LABEL=/
        module /initrd- 2.6.12-1.1454_FC4xen0.img
title Fedora Core (2.6.14-1.1656_FC4)
        root (hd0,0)
        kernel /vmlinuz-2.6.14-1.1656_FC4 ro root=LABEL=/
        initrd /initrd-2.6.14-1.1656_FC4.img
title Fedora Core (2.6.11-1.1369_FC4)
        root (hd0,0)
        kernel /vmlinuz-2.6.11-1.1369_FC4 ro root=LABEL=/
        initrd /initrd-2.6.11-1.1369_FC4.img
------------

/etc/xen/fedora
------------
#  -*- mode: python; -*-
#============================================================================
# Python configuration setup for 'xm create'.
# You use a separate script for each domain you want to create, or
# you can set the parameters for the domain on the xm command line.
#============================================================================

#----------------------------------------------------------------------------
# Kernel image file.
kernel = "/boot/vmlinuz-2.6.12-1.1454_FC4xenU"

# Optional ramdisk.
#ramdisk = "/boot/initrd.gz"

# The domain build function. Default is 'linux'.
#builder='linux'

# Initial memory allocation (in megabytes) for the new domain.
memory = 64

# A name for your domain. All domains must have different names.
name = "Domain-1"

# Which CPU to start domain on?
#cpu = -1   # leave to Xen to pick

# Number of Virtual CPUS to use, default is 1
#vcpus = 1

#----------------------------------------------------------------------------
# Define network interfaces.

# Number of network interfaces. Default is 1.
nics=1

# Optionally define mac and/or bridge for the network interfaces.
# Random MACs are assigned if not given.
vif = [ 'mac=aa:00:00:00:00:11, bridge=xen-br0' ]

#----------------------------------------------------------------------------
# Define the disk devices you want the domain to have access to, and
# what you want them accessible as.
# Each disk entry is of the form phy:UNAME,DEV,MODE
# where UNAME is the device, DEV is the device name the domain will see,
# and MODE is r for read-only, w for read-write.

#disk = [ 'phy:hda1,hda1,w' ]
disk = [ 'file:/home/xend/fedora.img,sda1,w' ]

#----------------------------------------------------------------------------
# Define to which TPM instance the user domain should communicate.
# The vtpm entry is of the form 'instance=INSTANCE,backend=DOM'
# where INSTANCE indicates the instance number of the TPM the VM
# should be talking to and DOM provides the domain where the backend
# is located.
# Note that no two virtual machines should try to connect to the same
# TPM instance. The handling of all TPM instances does require
# some management effort in so far that VM configration files (and thus
# a VM) should be associated with a TPM instance throughout the lifetime
# of the VM / VM configuration file. The instance number must be
# greater or equal to 1.
#vtpm = [ 'instance=1,backend=0' ]

#----------------------------------------------------------------------------
# Set the kernel command line for the new domain.
# You only need to define the IP parameters and hostname if the domain's
# IP config doesn't, e.g. in ifcfg-eth0 or via DHCP.
# You can use 'extra' to set the runlevel and custom environment
# variables used by custom rc scripts (e.g. VMID=, usr= ).

# Set if you want dhcp to allocate the IP address.
#dhcp="dhcp"
# Set netmask.
#netmask=
# Set default gateway.
#gateway=
# Set the hostname.
#hostname= "vm%d" % vmid

# Set root device.
root = "/dev/sda1"

# Root device for nfs.
#root = "/dev/nfs"
# The nfs server.
#nfs_server = '169.254.1.0 '
# Root directory on the nfs server.
#nfs_root   = '/full/path/to/root/directory'

# Sets runlevel 4.
extra = "3"

#----------------------------------------------------------------------------
# Set according to whether you want the domain restarted when it exits.
# The default is 'onreboot', which restarts the domain when it shuts down
# with exit code reboot.
# Other values are 'always', and 'never'.

#restart = 'onreboot'

#============================================================================

------------


Please tell me what should I do.
Thanks a lot.


Koala Yeung



--
Technical Support, DigitalOne Limited
Tel: 8100-2616 / 2545-1383   Fax: 2815-0593
_______________________________________________
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®.