Is there any way as part of the upgrading from older versions to newer
versions to automatically modify the templates?
We have 200-some user templates which specify PORT=-1 which is no longer
allowed in ONE4.4. We have already checked and found that the onedb
upgrade command does not remove d
No. I am talking about the VM template.
On Mon, Apr 14, 2014 at 12:47 PM, Cuquerella Sanchez, Javier
wrote:
> Hi,
>
> this is enabled in sunstone-server. conf, no? and when you are indicating
> that the port has to be empty you mean the value of: vnc_proxy_port?
>
> Regards
>
> -
Just don't specify the port. If you are manually modifying templates
this is the configuration for VNC that automatically generates the
port:
--8<--
GRAPHICS = [
TYPE= "vnc",
LISTEN = "0.0.0.0"]
-->8--
In Sunstone VNC must be activated and the port value empty. Make sure
that the
I think it is better to let OpenNebula choose the port as you can use
the same template to start several VMs and the VNC ports wont clash.
On Wed, Apr 2, 2014 at 9:57 AM, Cuquerella Sanchez, Javier
wrote:
> Hi,
>
> actually I specify the port manually. and there is no other service using
> port
Hi,
actually I specify the port manually. and there is no other service using port
5902. I should do in my template to enable VNC OpenNebula autonomously?
Regards.
Javier.
---
Javier Cuquerella Sánchez
javier.cuquere...@atos.net
Atos Research & I
Are you specifying the port manually. It may be that there's another
VM already using that port. Do not set it, let OpenNebula chose one
for you.
If this does not work try also unsetting the keymap. I can not think
of any other problem with that.
On Tue, Apr 1, 2014 at 11:43 AM, Cuquerella Sanche
Hi,
I have instantiated the machine, removing and setting parameters and end the
problem is on the line of the VNC:
GRAPHICS=[ KEYMAP=es, LISTEN=0.0.0.0, PORT=5902, TYPE=vnc ]
If I remove the template the machine boots into Xen and opennebula and I
access the virtual machine
Let's try taking out a couple of parameters. KERNEL_CMD, swap disk,
device_model and VNC. I'm using the template you provided in a
previous email:
NAME = Encourage7
MEMORY = 4096
CPU= 1
OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
"/boot/initramfs-2.6.32-279.el6.x86_64.img",
Hi,
The deployment file generated by OpenNebula is:
[root@VTSS003 114]# cat deployment.0
name = 'one-114'
#O CPU_CREDITS = 256
memory = '4096'
kernel = '/boot/vmlinuz-2.6.32-279.el6.x86_64'
ramdisk = '/boot/initramfs-2.6.32-279.el6.x86_64.img'
root = '/dev/xvda1'
extra = 'ro xencons=tty console=
Can you send us the deployment file generated by OpenNebula? Just to
check if there is something too different to your deployment file. It
should be located in you frontend at
/var/lib/one/vms//deployment.0
On Mon, Mar 24, 2014 at 10:29 AM, Cuquerella Sanchez, Javier
wrote:
> Hi,
>
> have been ab
Hi,
have been able to look at something ?
I do not understand because if I start the same image with xen ONLY works:
xm create encourage.cfg
name = " encourage"
memory = 4096
maxmem = 4096
vcpus = 1
# bootloader = "/ usr / bin / pygrub "
Hi,
I don’t output anything. by putting the command stays there
[root@VTSS003 ~]# xm list
NameID Mem VCPUs State Time(s)
Domain-0 0 1024 1 r- 19487.0
ciudad20201 67
Are you getting an error with xm console or it just doesn't output anything?
On Thu, Mar 20, 2014 at 5:50 PM, Cuquerella Sanchez, Javier
wrote:
> HI,
>
> The virtual machine runs on both xen and opennebula:
>
> [root@VTSS003 106]# xm list | grep one
> one-10613
HI,
The virtual machine runs on both xen and opennebula:
[root@VTSS003 106]# xm list | grep one
one-106133 4096 1 -b 11.3
[oneadmin@VTSS003 CUQUE]$ onevm list
ID USER GROUPNAMESTAT UCPUUMEM HOST TIME
The problem is the root parameter:
--8<--
dracut Warning: No root device "block:/dev//dev/xvda1" found
-->8--
In OpenNebula template you should drop de "/dev/" prefix and "ro" parameter:
--8<--
OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
"/boot/initramfs-2.6.32-279.
Hi,
I have a problem when starting a virtual machine. me the error that appears is:
Freeing unused kernel memory: 1260k freed
Write protecting the kernel read-only data: 10240k
Freeing unused kernel memory: 972k freed
Freeing unused kernel memory: 1732k freed
dracut: dracut-004-283.el6
device-map
16 matches
Mail list logo
