[one-users] onevm shows vm is running but it is not in xen
Carlos Martín Sánchez
cmartin at opennebula.org
Fri Jul 22 03:25:28 PDT 2011
Hi there,
A comment on Prakhar's email: 'onevm submit' is actually an alias to 'onevm
create'.
The VMs are deployed automatically because the scheduler is running. If you
need to control manually the deployments, you can edit the 'one' script (in
/usr/bin/one or $ONE_LOCATION/bin/one) to start only the core daemon 'oned',
and not the scheduler daemon 'mm_sched'.
And now please find my comments to your questions inline:
> - I believe this whole confusion is due to my lack of knowledge on
> OpenNebula VM Template.
> - Have I pointed to the correct kernel on host machine ? if not what is
> the correct way
> - Do I need to copy Virtual Image's kernel in to host machine
> (Cluster node) and then point it to them on VM Template.
>
> Yes, the KERNEL and INITRD paths are relative to the Host's FS
>
> -
> - Can Someone please elaborate the meaning of ROOT and TARGET on VM
> template. To what should they be pointed at ?
> - ROOT - to which device should we point this at ? Where can I
> obtain this info , is it to the Host Machine ? or to the Virtual Machine ?
> and what is the device ? is it "/" partition device ?
> - TARGET- to which device should we point this at ? Where can I
> obtain this info , is it to Host Machine ? or to Virtual Machine
>
> ROOT is the VM's device to mount as '/'.
TARGET is the VM's device where the DISK will be mapped. But when using an
Image it is optional, and you can rely on the default targets, see [1].
Regards,
Carlos.
[1] http://opennebula.org/documentation:rel2.2:template#disks_device_mapping
--
Carlos Martín, MSc
Project Major Contributor
OpenNebula - The Open Source Toolkit for Cloud Computing
www.OpenNebula.org <http://www.opennebula.org/> | cmartin at opennebula.org
On Tue, Jul 19, 2011 at 10:10 PM, Rasika Karunathilaka <
rasika.karunathilaka at yahoo.com> wrote:
> Hi Puneeth/Team,
> Please find the answers to the questions.
> 1.) I am using xen id
> 2.) I have not written the script yet, I am trying to check whether it
> is successful through xen console.
> 3.) All three commands displays that the xen virtual machine is
> running.
>
> I still haven't got full understanding about the VM Template. Let me brief
> you my environment. I have two machines.
>
> Machine A. ) OpenNebula front end with NFS share with cluster node
> Machine B.) Cluster Node with OpenSuse 11.4 xen kernel.
>
> - Both machines are running on OpenSuse 11.4.
> - Fedora virtual machine was created on Machine B using Xen kernel. (
> This virtual machine is working fine on Machine B with xen commands.)
> - Same Fedora Virtual machine's image was used to create opennebula
> fedora image.
> - Then OpenNebula VM template was created as follows
> - ##################################################
>
> Name = Fed12
> CPU = 0.5
> MEMORY = 512
> OS = [
> KERNEL =
> "/boot/vmlinuz-2.6.37.6-0.5-xen",
> INITRD = "/boot/initrd-2.6.37.6-0.5-xen",
> ROOT = "sda2"
> ]
> DISK = [
> IMAGE_ID = "1",
> TARGET = "/dev/sda2",
> READONLY = "no"
> ]
> ################################################
>
> - in the OS section of VM template, I have put Linux kernel information
> of Machine B, which is the cluster node (the host machine) there I have
> specified the Suse Xen kernel which runs the main OS. Same applies to INTRD
> as well.
> - I am bit confused about ROOT partition, I assume ROOT partition
> means host machine's (Cluster Node's) "/" Partition. Even though /etc/fstab
> shows /dev/disk ... id , the df -kh displays as "/" maps to /dev/sda2
> - Now on Disk section I assumed TARGET means "/" partition on
> Cluster node or host machine, which is again /dev/sda2
> - Anyhow still OpenNebula xen virtual image creation is not
> successful. Right now it creates the Virtual Image and copies it however I
> can't login through the console, it displays set of messages.
> - I believe this whole confusion is due to my lack of knowledge on
> OpenNebula VM Template.
> - Have I pointed to the correct kernel on host machine ? if not what is
> the correct way
> - Do I need to copy Virtual Image's kernel in to host machine
> (Cluster node) and then point it to them on VM Template.
> - Can Someone please elaborate the meaning of ROOT and TARGET on
> VM template. To what should they be pointed at ?
> - ROOT - to which device should we point this at ? Where can I
> obtain this info , is it to the Host Machine ? or to the Virtual Machine ?
> and what is the device ? is it "/" partition device ?
> - TARGET- to which device should we point this at ? Where can I
> obtain this info , is it to Host Machine ? or to Virtual Machine
>
> Highly appreciate if someone can help me to understand above. Please find
> following xen console output, vm.log and xend.log info.
>
> Cheers !
> Rasika karunathilaka.
>
> ################################ vm.log###################################
> Tue Jul 19 07:55:48 2011 [DiM][I]: New VM state is ACTIVE.
> Tue Jul 19 07:55:48 2011 [LCM][I]: New VM state is PROLOG.
> Tue Jul 19 07:55:48 2011 [VM][I]: Virtual Machine has no context
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh:
> linux-q3r2:/srv/cloud/one/var/images/95f2274e26a954f8131912f41f84967fbd411c33
> cdv-gtoopensuse:/srv/cloud/images/87/images/disk.0
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: DST:
> /srv/cloud/images/87/images/disk.0
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: Creating directory
> /srv/cloud/images/87/images
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: Executed "mkdir -p
> /srv/cloud/images/87/images".
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: Executed "chmod a+w
> /srv/cloud/images/87/images".
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: Cloning
> /srv/cloud/one/var/images/95f2274e26a954f8131912f41f84967fbd411c33
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: Executed "cp -r
> /srv/cloud/one/var/images/95f2274e26a954f8131912f41f84967fbd411c33
> /srv/cloud/images/87/images/disk.0".
> Tue Jul 19 07:58:22 2011 [TM][I]: tm_clone.sh: Executed "chmod a+rw
> /srv/cloud/images/87/images/disk.0".
> Tue Jul 19 07:58:22 2011 [LCM][I]: New VM state is BOOT
> Tue Jul 19 07:58:22 2011 [VMM][I]: Generating deployment file:
> /srv/cloud/one/var/87/deployment.0
> Tue Jul 19 07:58:24 2011 [LCM][I]: New VM state is RUNNING
> #########################################################################
>
> ################################ Xend.log #################################
> 2011-07-19 23:04:50 2141] DEBUG (XendDomainInfo:1841) Storing domain
> details: {'console/ring-ref': '306145', 'image/entry': '3221233664',
> 'console/port': '2', 'store/ring-ref': '306146', 'image/loader': 'generic',
> 'vm': '/vm/9e0e9651-b379-dfd1-f9ef-8782e445499c',
> 'control/platform-feature-multiprocessor-suspend': '1',
> 'image/hv-start-low': '4118806528', 'image/guest-os': 'linux',
> 'image/features/writable-descriptor-tables': '1', 'image/virt-base':
> '3221225472', 'memory/target': '524288', 'image/guest-version': '2.6',
> 'image/features/supervisor-mode-kernel': '1', 'image/pae-mode': 'yes',
> 'description': '', 'console/limit': '1048576', 'image/paddr-offset': '0',
> 'image/hypercall-page': '3221237760', 'image/suspend-cancel': '1',
> 'cpu/0/availability': 'online', 'image/features/pae-pgdir-above-4gb': '1',
> 'image/features/writable-page-tables': '1', 'console/type': 'xenconsoled',
> 'image/features/auto-translated-physmap': '1', 'name': 'one-87', 'domid':
> '11', 'image/xen-version': 'xen-3.0', 'store/port': '1'}
> [2011-07-19 23:04:50 2141] DEBUG (DevController:95) DevController: writing
> {'protocol': 'x86_32-abi', 'state': '1', 'backend-id': '0', 'backend':
> '/local/domain/0/backend/console/11/0'} to
> /local/domain/11/device/console/0.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:97) DevController: writing
> {'domain': 'one-87', 'frontend': '/local/domain/11/device/console/0',
> 'uuid': '0d4176fe-0129-6b05-6ece-46955ecb81bd', 'frontend-id': '11',
> 'state': '1', 'location': '2', 'online': '1', 'protocol': 'vt100'} to
> /local/domain/0/backend/console/11/0.
> [2011-07-19 23:04:50 2141] DEBUG (XendDomainInfo:1928)
> XendDomainInfo.handleShutdownWatch
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> tap2.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vif.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vkbd.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> ioports.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> tap.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vif2.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> console.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:144) Waiting for 0.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vscsi.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vbd.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:144) Waiting for 2050.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:671) hotplugStatusCallback
> /local/domain/0/backend/vbd/11/2050/hotplug-status.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:671) hotplugStatusCallback
> /local/domain/0/backend/vbd/11/2050/hotplug-status.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:685) hotplugStatusCallback
> 1.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> irq.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vfb.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> pci.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vusb.
> [2011-07-19 23:04:50 2141] DEBUG (DevController:139) Waiting for devices
> vtpm.
> [2011-07-19 23:04:50 2141] INFO (XendDomain:1224) Domain one-87 (11)
> unpaused.
> #########################################################################
>
> ################################ Xen Console############################
>
> [ 0.000000] Reserving virtual address space above 0xf5800000
> [ 0.000000] Initializing cgroup subsys cpuset
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Linux version 2.6.37.6-0.5-xen (geeko at buildhost) (gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) ) #1 SMP 2011-04-25 21:48:33 +0200
>
> [ 0.000000] Xen-provided physical RAM map:
> [ 0.000000] Xen: 0000000000000000 - 0000000020800000 (usable)
> [ 0.000000] NX (Execute Disable) protection: active
> [ 0.000000] last_pfn = 0x20800 max_arch_pfn = 0x10000000
>
> [ 0.000000] init_memory_mapping: 0000000000000000-0000000020800000
> [ 0.000000] RAMDISK: 00832000 - 01b50000
> [ 0.000000] ACPI in unprivileged domain disabled
> [ 0.000000] 0MB HIGHMEM available.
> [ 0.000000] 520MB LOWMEM available.
>
> [ 0.000000] mapped low ram: 0 - 20800000
> [ 0.000000] low ram: 0 - 20800000
> [ 0.000000]
> Zone PFN ranges:
> [ 0.000000] DMA 0x00000000 -> 0x00001000
> [ 0.000000] Normal 0x00001000 -> 0x00020800
> [ 0.000000] HighMem empty
> [ 0.000000] Movable zone start PFN for each node
>
> [ 0.000000] early_node_map[2] active PFN ranges
> [ 0.000000] 0: 0x00000000 -> 0x00020000
> [ 0.000000] 0: 0x00020800 -> 0x00020800
> [ 0.000000] setup_percpu: NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1
>
> [ 0.000000] PERCPU: Embedded 9 pages/cpu @dfb5e000 s16320 r0 d20544 u36864
> [ 0.000000] Swapping MFNs for PFN 75d and 1fb5f (MFN 4b456 and 2ac6a)
> [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130032
>
> [ 0.000000] Kernel command line: root=/dev/sda2
> [ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
> [ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> [ 0.000000] Inode-cache hash
> table entries: 32768 (order: 5, 131072 bytes)
> [ 0.000000] Initializing CPU#0
> [ 0.000000] allocated 2662400 bytes of page_cgroup
> [ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
>
> [ 0.000000] Software IO TLB disabled
> [ 0.000000] Initializing HighMem for node 0 (00000000:00000000)
> [ 0.000000] Memory: 487660k/532480k available (4173k kernel code, 36628k reserved, 3025k data, 344k init, 0k highmem)
>
> [ 0.000000] virtual kernel memory layout:
> [ 0.000000] fixmap : 0xf5476000 - 0xf57ff000 (3620 kB)
> [ 0.000000] pkmap : 0xf5000000 - 0xf5200000 (2048 kB)
> [ 0.000000] vmalloc : 0xe1000000 - 0xf4ffe000 ( 319 MB)
>
> [ 0.000000] lowmem : 0xc0000000 - 0xe0800000 ( 520 MB)
> [ 0.000000] .init : 0xc070a000 - 0xc0760000 ( 344 kB)
> [ 0.000000] .data : 0xc04157d7 - 0xc0709e28 (3025 kB)
> [ 0.000000] .text :
> 0xc0002000 - 0xc04157d7 (4173 kB)
> [ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
> [ 0.000000] Hierarchical RCU implementation.
> [ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
>
> [ 0.000000] RCU-based detection of stalled CPUs is disabled.
> [ 0.000000] NR_IRQS:2624 nr_irqs:584 16
> [ 0.000000] Xen reported: 2926.044 MHz processor.
> [ 0.000000] Console: colour dummy device 80x25
>
> [ 0.000000] console [tty0] enabled
> [ 0.000000] console [xvc-1] enabled
> [ 0.080003] Calibrating delay using timer specific routine.. 5859.38 BogoMIPS (lpj=11718775)
> [ 0.080012] pid_max: default: 32768 minimum: 301
>
> [ 0.080037] Security Framework initialized
> [ 0.080049] AppArmor: AppArmor initialized
> [ 0.080062] Mount-cache hash table entries: 512
> [ 0.080137] Initializing cgroup subsys ns
> [ 0.080143] ns_cgroup deprecated: consider
> using the 'clone_children' flag without the ns_cgroup.
> [ 0.080149] Initializing cgroup subsys cpuacct
> [ 0.080153] Initializing cgroup subsys memory
> [ 0.080160] Initializing cgroup subsys devices
>
> [ 0.080164] Initializing cgroup subsys freezer
> [ 0.080168] Initializing cgroup subsys net_cls
> [ 0.080172] Initializing cgroup subsys blkio
> [ 0.080603] SMP alternatives: switching to UP code
> [ 0.098308] Freeing SMP alternatives: 24k freed
>
> [ 0.098812] Brought up 1 CPUs
> [ 0.098873] devtmpfs: initialized
> [ 0.099027] regulator: core version 0.5
> [ 0.099059] regulator: dummy:
> [ 0.118929] Time: 165:165:165 Date: 165/165/65
> [ 0.118989] NET: Registered protocol family 16
>
> [ 0.119108] Brought up 1 CPUs
> [ 0.119108] PCI: Fatal: No config space access function found
> [ 0.119108] PCI: setting up Xen PCI frontend stub
> [ 0.120308] bio: create slab <bio-0> at 0
> [
> 0.120355] ACPI: Interpreter disabled.
> [ 0.120403] suspend: event channel 6
> [ 0.120403] xen_mem: Initialising balloon driver.
> [ 0.120403] SCSI subsystem initialized
> [ 0.120403] vgaarb: loaded
>
> [ 0.120403] PCI: System does not support PCI
> [ 0.120403] PCI: System does not support PCI
> [ 0.120403] NetLabel: Initializing
> [ 0.120403] NetLabel: domain hash size = 128
> [ 0.120403] NetLabel: protocols = UNLABELED CIPSOv4
>
> [ 0.120403] NetLabel: unlabeled traffic allowed by default
> [ 0.120403] Switching to clocksource xen
> [ 0.121040] AppArmor: AppArmor Filesystem Enabled
> [ 0.121046] pnp: PnP ACPI: disabled
> [ 0.122338] NET: Registered protocol family 2
>
> [ 0.122379] IP route cache hash table entries: 16384 (order: 4, 65536 bytes)
> [ 0.122379] TCP established hash table entries: 65536 (order: 7, 524288 bytes)
> [ 0.122379] TCP bind hash table entries: 65536 (order: 7,
> 524288 bytes)
> [ 0.122514] TCP: Hash tables configured (established 65536 bind 65536)
> [ 0.122519] TCP reno registered
> [ 0.122522] UDP hash table entries: 256 (order: 1, 8192 bytes)
> [ 0.122528] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
>
> [ 0.122569] NET: Registered protocol family 1
> [ 0.122603] Unpacking initramfs...
> [ 0.138321] Freeing initrd memory: 19576k freed
> [ 0.145576] platform rtc_cmos: registered platform RTC device (no PNP device found)
>
> [ 0.145697] audit: initializing netlink socket (disabled)
> [ 0.145713] type=2000 audit(1311096890.831:1): initialized
> [ 0.170606] VFS: Disk quotas dquot_6.5.2
> [ 0.170629] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
>
> [ 0.170703] msgmni has been set to 265
> [ 0.170847] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
> [ 0.170868] io scheduler noop registered
> [ 0.170872] io
> scheduler deadline registered
> [ 0.170881] io scheduler cfq registered (default)
> [ 0.171081] Non-volatile memory driver v1.3
> [ 0.171086] Linux agpgart interface v0.103
> [ 0.171186] Xen virtual console successfully installed as xvc0
>
> [ 0.171258] Fixed MDIO Bus: probed
> [ 0.171282] PNP: No PS/2 controller found. Probing ports directly.
> [ 0.172123] i8042.c: No controller found.
> [ 0.172170] mice: PS/2 mouse device common for all mice
>
> [ 0.172295] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0
> [ 0.172323] rtc_cmos: probe of rtc_cmos failed with error -38
> [ 0.172466] TCP cubic registered
> [ 0.172486] NET: Registered protocol family 10
>
> [ 0.172685] lo: Disabled Privacy Extensions
> [ 0.172815] Registering the dns_resolver key type
> [ 0.172846] libceph: loaded (mon/osd proto 15/24, osdmap 5/5 5/5)
> [ 0.172922] registered taskstats version 1
>
> [ 0.172937] Magic
> number: 1:252:3141
> [ 0.172952] XENBUS: Device with no driver: device/vbd/2050
> [ 0.172957] /usr/src/packages/BUILD/kernel-xen-2.6.37.6/linux-2.6.37/drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
> [ 0.173004] Freeing unused kernel memory: 344k freed
>
> [ 0.174096] Write protecting the kernel text: 4176k
> [ 0.174769] Write protecting the kernel read-only data: 2796k
> [ 0.215187] netfront: Initialising virtual ethernet driver.
> [ 0.226035] register_blkdev: cannot get major 8 for sd
>
> [ 0.226044] ------------[ cut here ]------------
> [ 0.226052] WARNING: at /usr/src/packages/BUILD/kernel-xen-2.6.37.6/linux-2.6.37/lib/vsprintf.c:1293 vsnprintf+0x3dd/0x3f0()
> [ 0.226058] Modules linked in: xenblk(+) cdrom xennet processor thermal_sys hwmon ata_generic
>
> [ 0.226075] Pid: 11, comm: xenwatch Not tainted 2.6.37.6-0.5-xen #1
> [ 0.226079] Call Trace:
> [ 0.226091] [<c00098f3>]
> try_stack_unwind+0x173/0x190
> [ 0.226098] [<c0007b3f>] dump_trace+0x3f/0xe0
> [ 0.226103] [<c000995b>] show_trace_log_lvl+0x4b/0x60
> [ 0.226110] [<c0009988>] show_trace+0x18/0x20
> [ 0.226118] [<c040b13c>] dump_stack+0x6d/0x72
>
> [ 0.226127] [<c003adf8>] warn_slowpath_common+0x78/0xb0
> [ 0.226133] [<c003ae4b>] warn_slowpath_null+0x1b/0x20
> [ 0.226139] [<c01ed59d>] vsnprintf+0x3dd/0x3f0
> [ 0.226146] [<c01ecd07>] pointer+0x1d7/0x260
>
> [ 0.226171] [<c01ed338>] vsnprintf+0x178/0x3f0
> [ 0.226177] [<c01f0327>] kvasprintf+0x27/0x60
> [ 0.226182] [<c01f0371>] kasprintf+0x11/0x20
> [ 0.226189] [<c02a43d6>] _dev_error+0x36/0xd0
>
> [ 0.226196] [<c02a4666>] xenbus_dev_fatal+0x26/0x40
> [ 0.226205] [<e10dd76d>] connect+0x26d/0x2e0 [xenblk]
> [ 0.226215] [<c02a6cef>] otherend_changed+0x9f/0x120
> [
> 0.226222] [<c02a4dba>] xenwatch_handle_callback+0x1a/0x60
> [ 0.226229] [<c02a501f>] xenwatch_thread+0x17f/0x190
> [ 0.226236] [<c0058e54>] kthread+0x74/0x80
> [ 0.226243] [<c0006502>] kernel_thread_helper+0x6/0x10
>
> [ 0.226249] ---[ end trace e4544fbf68dc1b63 ]---
> [ 0.226254] vbd vbd-2050: 19
> [ 0.320035] XENBUS: Device not ready: device/vbd/2050
> [ 0.328662] udev[66]: starting version 166
> ########################################################################
>
>
>
>
> ------------------------------
> *From:* puneeth <puneeth.poduri at gmail.com>
> *To:* Rasika Karunathilaka <rasika.karunathilaka at yahoo.com>
> *Sent:* Monday, 18 July 2011 7:27 PM
> *Subject:* Re: [one-users] onevm shows vm is running but it is not in xen
>
> Hi,
> ok firstly is the vm visible when you try xentop or xm list.
> secondly no the vm is started automatically once we say submit.
> the reason its in a blocked state is because its booted and waiting for
> an input (ie a login) please note the bolcked state in xen is not same
> as that of opennebula. now i have a set of questions for you ?
> 1. how are you trying to accesses the console of the deployed vm ?(i
> know your trying through the command xm console <ID> but what is the ID
> you are using is it the opennebula vm ID or the xen vm ID note they are
> different.) -> are you trying a onevm id instead of xen id ??
>
> 2. Have you written the script files required to take care of the
> context variables ? (IE init.sh , rc.local(in your case)).please note
> that rc.local should be present in the VM image inside the desiered
> folder. and the init.sh should be present in the dom0 or your host
> system. -> if this is not done you cant establish a network.
>
> 3. do you have a virt-manager ? if you do can you find the deployed vm
> there ? ok please tell me the output of the following commands.
> i. xm list
> ii. onevm list
> iii. xentop
> --
> regards
> puneeth
>
> On Mon, 2011-07-18 at 06:39 -0700, Rasika Karunathilaka wrote:
> > Hi Team,
> > I was able to create vm instance, and it was created successfully.
> > Please find my vm template below. However I can't log in to the vm.
> > when I try to get the console (xm console <id>) it provide following
> > messages. Further vm is in blocked state. Please Help ! ..
> >
> > Why does it deploy, when I just used onevm create <VMTemplate> ,
> > shouldn't it create the image only and not start it. I believe stating
> > should come when we issue onevm deploy . Highly appreciate you
> > help on this. Kernel and Initrd on template is pointed to the same on
> > Xen Host machine.
> >
> >
> >
> > Cheers !
> > Rasika
> >
> >
> >
> > ############################ VM Template
> > ##############################
> >
> > Name = Fed12
> > CPU = 1
> > MEMORY = 512
> > OS = [
> > KERNEL = "/boot/vmlinuz-2.6.37.1-1.2-xen",
> > INITRD = "/boot/initrd-2.6.37.1-1.2-xen",
> > ROOT =
> > "/dev/disk/by-id/ata-Hitachi_HDS721680PLA380_PVE101Z7UGE1AM-part2 "
> > ]
> >
> > DISK = [
> > IMAGE_ID = "1"
> > ]
> >
> >
> > CONTEXT = [
> > HOSTNAME = "Fed12",
> > USERNAME = "oneadmin",
> > IP_PRIVATE = "$NIC[IP]",
> > IP_GEN = "192.168.104.$VMID",
> > FILES =
> > "/vms_configuration/id_rsa.pub /vms_configuration/init.sh",
> > TARGET = "hdb"
> > ]
> >
> >
> > ############################## Console messages
> > #################################################
> >
> >
> >
> > 0.171869] PNP: No PS/2 controller found. Probing ports directly.
> > [ 0.172713] i8042.c: No controller found.
> > [ 0.172756] mice: PS/2 mouse device common for all mice
> > [ 0.172882] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as
> > rtc0
> > [ 0.172910] rtc_cmos: probe of rtc_cmos failed with error -38
> > [ 0.173054] TCP cubic registered
> > [ 0.173075] NET: Registered protocol family 10
> > [ 0.173274] lo: Disabled Privacy Extensions
> > [ 0.173405] Registering the dns_resolver key type
> > [ 0.173436] libceph: loaded (mon/osd proto 15/24, osdmap 5/5 5/5)
> > [ 0.173506] registered taskstats version 1
> > [ 0.173522] Magic number: 1:252:3141
> > [ 0.173537] XENBUS: Device with no driver: device/vbd/51712
> > [ 0.173541] XENBUS: Device with no driver: device/vbd/832
> > [
> > 0.173545]
> /usr/src/packages/BUILD/kernel-xen-2.6.37.1/linux-2.6.37/drivers/rtc/hctosys.c:
> unable to open rtc device (rtc0)
> > [ 0.173592] Freeing unused kernel memory: 344k freed
> > [ 0.174686] Write protecting the kernel text: 4176k
> > [ 0.175358] Write protecting the kernel read-only data: 2792k
> > [ 0.217635] netfront: Initialising virtual ethernet driver.
> > [ 0.232769] xen-vbd: registered block device major 202
> > [ 0.232795] blkfront: xvda: barriers enabled
> > [ 0.234407] xvda: xvda1 xvda2
> > [ 0.234661] Setting capacity to 8388610
> > [ 0.234667] xvda: detected capacity change from 0 to 4294968320
> > [ 0.234827] xen-vbd: registered block device major 3
> > [ 0.234840] blkfront: hdb: barriers enabled
> > [ 0.236238] hdb: unknown partition table
> > [ 0.236355] Setting capacity to 736
> > [ 0.236360] hdb: detected capacity change from 0 to 376832
> > [ 0.336171] udev[65]: starting version 166
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20110722/32ff31a3/attachment-0003.htm>
More information about the Users
mailing list