[one-users] Fwd: VM's state is not steady and VM is unreacheble
Tino Vazquez
tinova at fdi.ucm.es
Tue Oct 27 04:37:08 PDT 2009
Hi there,
If you boot the "/home/domains/disk.img" image with xen, not using
opennebula, does it boot correctly?
For the network setup you need to place a script [1] within the VM so
it can set the IP address from the MAC address.
Hope it helps,
-Tino
[1] http://opennebula.org/doku.php?id=documentation:rel1.4:vgg -->
look for vmcontext.sh
--
Constantino Vázquez, Grid Technology Engineer/Researcher:
http://www.dsa-research.org/tinova
DSA Research Group: http://dsa-research.org
Globus GridWay Metascheduler: http://www.GridWay.org
OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
2009/10/21 张佳宝 <zhangjiabao at gmail.com>:
>
>
> ---------- Forwarded message ----------
> From: 张佳宝 <zhangjiabao at gmail.com>
> Date: 2009/10/21
> Subject: VM's state is not steady and VM is unreacheble
> To: users at lists.opennebula.org
>
>
> Hi,
> I installed Opennebula on my system,I use a host named oneserve as the
> front-end(the host is also a node in the system),whose IP is 192.168.1
> 105,and I use a host named oneclient as the node ,whose IP is 192.168.1.106.
> I use the following template to create a virtual network:
> -----------------------------------------------------------
> NAME = "Public VLAN"
> TYPE = FIXED
> BRIDGE = eth0
> LEASES = [IP=192.168.1.249,MAC=00:1C:25:A2:8D:B7]
>
> ------------------------------------------------------------
>
> I can see the virtual network created successfully.
>
> -----------------------------------------------------
> [root at oneserver domains]# onevm list
> ID NAME STAT CPU MEM HOSTNAME TIME
> 42 xen01 susp 0 524288 oneserver 00 00:19:55
> [root at oneserver domains]# onevnet list
> NID NAME TYPE BRIDGE
> 1 Public VLAN Fixed eth0
> [root at oneserver domains]# onevnet show 1
> NID : 1
> UID : 0
> Network Name : Public VLAN
> Type : Fixed
> Bridge : eth0
>
> ....: Template :....
> BRIDGE=eth0
> LEASES=IP=192.168.1.249,MAC=00:1C:25:A2:8D:B7
> NAME=Public VLAN
> TYPE=FIXED
>
> ....: Leases :....
> IP = 192.168.1.249 MAC = 00:1c:25:a2:8d:b7 USED = 1 VID = 42
> -------------------------------------------------------------------
>
> and next,I use a template to create a VM as follow:
>
> ------------------------------------------------------------------------
> NAME = xen01
> CPU = 1
> MEMORY = 512
> OS = [ kernel = "/boot/vmlinuz-2.6.18-128.el5xen",
> initrd = "/boot/initrd-2.6.18-128.el5xen.img",
> root = "sda1"]
> DISK = [ source = "/home/domains/disk.img",
> target = "sda1",
> readonly = "no"]
> DISK = [ type = "swap",
> size = 512,
> target = "sdb1",
> readonly = "no"]
> NIC = [NETWORK="Public VLAN"]
> --------------------------------------------------------------------------
>
> and after minites the VM's state is running,
>
> ---------------------------------------------------------------------------
>
> [root at oneserver domains]# onevm list
> ID NAME STAT CPU MEM HOSTNAME TIME
> 42 xen01 runn 0 524288 oneserver 00 00:11:20
>
> [root at oneserver domains]# onevm show 42
> VID : 42
> UID : 0
> STATE : SUSPENDED
> LCM STATE : LCM_INIT
> DEPLOY ID : one-42
> MEMORY : 524288
> CPU : 0
> LAST POLL : 1256200675
> START TIME : 10/22 16:26:03
> STOP TIME : 01/01 08:00:00
> NET TX : 0
> NET RX : 0
>
> ....: Template :....
> CPU : 1
> DISK : READONLY=no,SOURCE=/home/domains/disk.img,TARGET=sda1
> DISK : READONLY=no,SIZE=512,TARGET=sdb1,TYPE=swap
> MEMORY : 512
> NAME : xen01
> NIC :
> BRIDGE=eth0,IP=192.168.1.249,MAC=00:1c:25:a2:8d:b7,NETWORK=Public
> VLAN,VNID=1
> OS :
> INITRD=/boot/initrd-2.6.18-128.el5xen.img,KERNEL=/boot/vmlinuz-2.6.18-128.el5xen,ROOT=sda1
>
> --------------------------------------------------------------------
>
> but the state of the VM changes ,sometimes it is done ,and sometimes it is
> suspend,like the following.
>
> -----------------------------------------------------------------
>
> [root at oneserver domains]# onevm list
> ID NAME STAT CPU MEM HOSTNAME TIME
> 42 xen01 susp 0 524288 oneserver 00 00:19:55
> -----------------------------------------------------------------------
>
>
> when the VM's state is running ,i try to login it ,but the VM is
> unreacheable.
> ----------------------------------------------------------------------------
>
> [root at oneserver domains]# ping 192.168.1.249
> PING 192.168.1.249 (192.168.1.249) 56(84) bytes of data.
> From 192.168.1.105 icmp_seq=1 Destination Host Unreachable
> From 192.168.1.105 icmp_seq=2 Destination Host Unreachable
> >From 192.168.1.105 icmp_seq=3 Destination Host Unreachable
>
> ---------------------------------------------------------------------------
>
> and I try to use the order 'xm console 'to login some error returns too.
>
> ----------------------------------------------------------------------------
>
> [root at oneserver domains]# xm console one-42
>
> SELinux: Initializing.
> selinux_register_security: Registering secondary module capability
> Capability LSM initialized as secondary
> Mount-cache hash table entries: 256
> CPU: L1 I cache: 32K, L1 D cache: 32K
> CPU: L2 cache: 6144K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> (SMP-)alternatives turned off
> Brought up 1 CPUs
> checking if image is initramfs... it is
> Grant table initialized
> NET: Registered protocol family 16
> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread F467A0 could not
> acquire Mutex [2] [20060707]
> No dock devices found.
> ACPI Exception (utmutex-0262): AE_BAD_PARAMETER, Thread F467A0 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: 32768 (order: 6, 262144 bytes)
> TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
> TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
> TCP: Hash tables configured (established 131072 bind 65536)
> TCP reno registered
> audit: initializing netlink socket (disabled)
> type=2000 audit(1256201781.637:1): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
> Initializing Cryptographic API
> alg: No test for crc32c (crc32c-generic)
> ksign: Installing public key data
> Loading keyring
> - Added public key 75ED35FE9471DC0E
> - User ID: CentOS (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
> XENBUS: Device with no driver: device/vbd/2049
> XENBUS: Device with no driver: device/vbd/2065
> XENBUS: Device with no driver: device/vif/0
> XENBUS: Device with no driver: device/console/0
> Write protecting the kernel read-only data: 467k
> Red Hat nash version 5.1.19.6 starting
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Setting up hotplug.
> Creating block device nodes.
> Loading ehci-hcd.ko module
> Loading ohci-hcd.ko module
> Loading uhci-hcd.ko module
> USB Universal Host Controller Interface driver v3.0
> Loading jbd.ko module
> Loading ext3.ko module
> Loading scsi_mod.ko module
> SCSI subsystem initialized
> Loading sd_mod.ko module
> Loading libata.ko module
> Loading ahci.ko module
> Loading dm-mod.ko module
> device-mapper: uevent: version 1.0.3
> device-mapper: ioctl: 4.11.5-ioctl (2007-12-12) initialised:
> dm-devel at redhat.com
> Loading dm-log.ko module
> Loading dm-mirror.ko module
> Loading dm-zero.ko module
> Loading dm-snapshot.ko module
> Loading dm-mem-cache.ko module
> Loading dm-region_hash.ko module
> Loading dm-message.ko module
> Loading dm-raid45.ko module
> device-mapper: dm-raid45: initialized v0.2429
> Waiting for driver initialization.
> Scanning and configuring dmraid supported devices
> Scanning logical volumes
> Reading all physical volumes. This may take a while...
> Activating logical volumes
> Volume group "VolGroup00" not found
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem '/dev/root'
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Kernel panic - not syncing: Attempted to kill init!
>
> ---------------------------------------------------------------------------------------------
>
> the following is the vm.log file:
>
> ------------------------------------------------------------------------
> Thu Oct 22 16:26:07 2009 [DiM][I]: New VM state is ACTIVE.
> Thu Oct 22 16:26:07 2009 [LCM][I]: New VM state is PROLOG.
> Thu Oct 22 16:26:07 2009 [TM][I]: tm_clone.sh:
> oneserver:/home/domains/disk.img oneserver:/home/one/var//42/images/disk.0
> Thu Oct 22 16:26:07 2009 [TM][I]: tm_clone.sh: DST:
> /home/one/var//42/images/disk.0
> Thu Oct 22 16:26:07 2009 [TM][I]: tm_clone.sh: Creating directory
> /home/one/var//42/images
> Thu Oct 22 16:26:07 2009 [TM][I]: tm_clone.sh: Executed "mkdir -p
> /home/one/var//42/images".
> Thu Oct 22 16:26:07 2009 [TM][I]: tm_clone.sh: Executed "chmod a+w
> /home/one/var//42/images".
> Thu Oct 22 16:26:07 2009 [TM][I]: tm_clone.sh: Cloning
> /home/domains/disk.img
> Thu Oct 22 16:29:38 2009 [TM][I]: tm_clone.sh: Executed "cp
> /home/domains/disk.img /home/one/var//42/images/disk.0".
> Thu Oct 22 16:29:38 2009 [TM][I]: tm_clone.sh: Executed "chmod a+w
> /home/one/var//42/images/disk.0".
> Thu Oct 22 16:29:38 2009 [TM][I]: tm_mkswap.sh: Creating 512Mb image in
> /home/one/var//42/images/disk.1
> Thu Oct 22 16:29:38 2009 [TM][I]: tm_mkswap.sh: Executed "dd if=/dev/zero
> of=/home/one/var//42/images/disk.1 bs=1 count=1 seek=512M".
> Thu Oct 22 16:29:38 2009 [TM][I]: tm_mkswap.sh: Initializing swap space
> Thu Oct 22 16:29:39 2009 [TM][I]: tm_mkswap.sh: Executed "/sbin/mkswap
> /home/one/var//42/images/disk.1".
> Thu Oct 22 16:29:39 2009 [TM][I]: tm_mkswap.sh: Executed "chmod a+w
> /home/one/var//42/images/disk.1".
> Thu Oct 22 16:29:39 2009 [LCM][I]: New VM state is BOOT
> Thu Oct 22 16:29:39 2009 [VMM][I]: Generating deployment file:
> /home/one/var/42/deployment.0
> Thu Oct 22 16:29:39 2009 [VMM][I]: Command: scp
> /home/one/var/42/deployment.0
> oneserver:/home/one/var//42/images/deployment.0
> Thu Oct 22 16:29:39 2009 [VMM][I]: Copy success
> Thu Oct 22 16:29:39 2009 [VMM][I]: Setting credits for the VM
> Thu Oct 22 16:29:39 2009 [VMM][I]: Command: sudo /usr/sbin/xm create
> /home/one/var//42/images/deployment.0 \&\& sudo /usr/sbin/xm sched-cred -d
> one-42 -w 256
> Thu Oct 22 16:29:42 2009 [LCM][I]: New VM state is RUNNING
> Thu Oct 22 16:29:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:30:28 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:30:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:31:28 2009 [VMM][I]: Monitor Information:
> CPU : 1
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:31:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:32:28 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:32:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:33:28 2009 [VMM][I]: Monitor Information:
> CPU : 5
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:33:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:34:28 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:34:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:35:28 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:35:58 2009 [VMM][I]: Monitor Information:
> CPU : 2
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:36:28 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:36:58 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:37:28 2009 [VMM][I]: Monitor Information:
> CPU : 0
> Memory: 524288
> Net_TX: 0
> Net_RX: 0
>
> Thu Oct 22 16:37:58 2009 [VMM][I]: VM running but new state from monitor is
> PAUSED.
>
> Thu Oct 22 16:37:58 2009 [LCM][I]: VM is suspended.
> Thu Oct 22 16:37:58 2009 [DiM][I]: New VM state is SUSPENDED
> Thu Oct 22 16:52:32 2009 [DiM][I]: New VM state is DONE.
>
> -------------------------------------------------------------------------------------------
>
> I really do not why it is ,do you know how to fix it?
>
> Best wishes,
>
> Atlas.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
More information about the Users
mailing list