Re: [one-users] Odp.: Re: VM Failed with Windows OS

[Sudeep Narayan Banerjee]

Hello Mateusz,

I have given now 17G for win7 OS.

On adding target=hda * hdb, it throws the below error.

[root@front images]# virt-install --connect qemu:///system --name win7
--ram 1024 --vcpus 2 --disk
path=/var/lib/libvirt/images/win7.qcow2,size=17,format=qcow2,bus=virtio,cache=none,target=hda
--cdrom /home/Windows-7-x86.iso,target=hdb --vnc --os-type=windows
--os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us

ERRORUnknown options ['target']

Regards,
Sudeep



On Wed, Jul 16, 2014 at 1:57 PM, Mateusz Skała 
wrote:

>
>
> W dniu 2014-07-16 08:00, Sudeep Narayan Banerjee napisał(a):
>
>  Dear Mateusz,
>>
>> Thanks for replying. Is the below command correct?
>>
>> [root@front ~]# virt-install --connect qemu:///system --name win7
>> --ram 1024 --vcpus 2 --disk
>> path=/var/lib/libvirt/images/win7.qcow2,size=7,format=
>> qcow2,bus=virtio,cache=none
>> --cdrom /home/Windows-7-x86.iso --vnc --os-type=windows
>> --os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us
>>
>>
> try to add target=hda, for example:
>
> virt-install --connect qemu:///system --name win7 --ram 1024 --vcpus 2
> --disk path=/var/lib/libvirt/images/win7.qcow2,size=7,format=
> qcow2,bus=virtio,cache=none,target=hda --cdrom 
> /home/Windows-7-x86.iso,target=hdb
> --vnc --os-type=windows --os-variant=win7 -noautoconsole --accelerate
> --noapic --keymap=en-us
>
> If You are using virtio then drivers for this bus will be needed, so You
> need add floppy drive with drivers.
>
>
>
>  The win7.qcow2 image is prepared under /var/lib/libvirt/images folder
>>
>> [root@front images ~]# qemu-img create -f qcow2 -o
>> preallocation=metadata /var/lib/libvirt/images/win7.qcow2 7G
>>
>>
>
> Only 7G for win7 os device?
>
>
>  Or how do I tweak it?
>>
>> Regards,
>> Sudeep
>>
>>
>


-- 
Thanks & Regards,
Sudeep Narayan Banerjee
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] CloudCatalyst Survey about Cloud Computing Trends

[Carlos Martín Sánchez]

Dear OpenNebula community,

The EU CloudCatalyst  initiative invites you to
participate in a survey about cloud computing trends. You can influence
over the CloudCatalyst project by collaborating on the identification of
existing challenges for Cloud expansion as well as on the definition of new
market opportunities. The survey will produce detailed information about
the main barriers to cloud adoption in order to help entrepreneurs,
researchers, and software developers create value-added Cloud solutions and
services.

To take the survey, click the link:

*https://www.surveymonkey.com/s/3GHCM9K
*

The deadline for filling in the survey is *22 July 2014*. The results of
the survey will be shared (for free) with all the respondents.

Cloud Catalyst is an initiative funded by the European Commission that aims
to provide useful tools to foster the adoption of Cloud Computing in
Europe. CloudCatalyst will set up a cross-border advice and support service
targeting two main groups:

   1. Software developers, researchers, start-ups, and other Cloud
   entrepreneurs interested in accelerating the development and deployment of
   Cloud Computing and internet services
   2. End-users from large industries, SMEs, and public entities interested
   in knowing how to benefit from the implementation of Cloud solutions.

On behalf of the CloudCatalyst Team,

*Thank you in advance for your participation!*

http://CloudCatalyst.eu 
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
 
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Odp.: Re: VM Failed with Windows OS

[Sudeep Narayan Banerjee]

Dear Mateusz & All,

I tried a lot but looks like I am not able to figure out.

Again the VM says "No bootable device" gpxe searching for bootdisk from
HDD/Floppy/DVD-CD" etc.

But it is running fine from frontend mode "virt-viewer -c qemu:///system
myvm3"

I tried to virtually mount the iso in the CD drive but that too did not
help.

I have also tried the interactive setup: virt-install --prompt  --> that
too does not work when I instantiate in OpenNebula VM.

I have also tried to write the template in Advanced Tab in OpenNebula
following [1] but I am failing.

[1] *http://wiki.ieeta.pt/wiki/index.php/OpenNebula#SetupComplete.cmd
*


Regards,
Sudeep


On Wed, Jul 16, 2014 at 2:43 PM, Sudeep Narayan Banerjee <
snbaner...@iitgn.ac.in> wrote:

> Hello Mateusz,
>
> I have given now 17G for win7 OS.
>
> On adding target=hda * hdb, it throws the below error.
>
> [root@front images]# virt-install --connect qemu:///system --name win7
> --ram 1024 --vcpus 2 --disk
> path=/var/lib/libvirt/images/win7.qcow2,size=17,format=qcow2,bus=virtio,cache=none,target=hda
> --cdrom /home/Windows-7-x86.iso,target=hdb --vnc --os-type=windows
> --os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us
>
> ERRORUnknown options ['target']
>
> Regards,
> Sudeep
>
>
>
> On Wed, Jul 16, 2014 at 1:57 PM, Mateusz Skała 
> wrote:
>
>>
>>
>> W dniu 2014-07-16 08:00, Sudeep Narayan Banerjee napisał(a):
>>
>>  Dear Mateusz,
>>>
>>> Thanks for replying. Is the below command correct?
>>>
>>> [root@front ~]# virt-install --connect qemu:///system --name win7
>>> --ram 1024 --vcpus 2 --disk
>>> path=/var/lib/libvirt/images/win7.qcow2,size=7,format=
>>> qcow2,bus=virtio,cache=none
>>> --cdrom /home/Windows-7-x86.iso --vnc --os-type=windows
>>> --os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us
>>>
>>>
>> try to add target=hda, for example:
>>
>> virt-install --connect qemu:///system --name win7 --ram 1024 --vcpus 2
>> --disk path=/var/lib/libvirt/images/win7.qcow2,size=7,format=
>> qcow2,bus=virtio,cache=none,target=hda --cdrom 
>> /home/Windows-7-x86.iso,target=hdb
>> --vnc --os-type=windows --os-variant=win7 -noautoconsole --accelerate
>> --noapic --keymap=en-us
>>
>> If You are using virtio then drivers for this bus will be needed, so You
>> need add floppy drive with drivers.
>>
>>
>>
>>  The win7.qcow2 image is prepared under /var/lib/libvirt/images folder
>>>
>>> [root@front images ~]# qemu-img create -f qcow2 -o
>>> preallocation=metadata /var/lib/libvirt/images/win7.qcow2 7G
>>>
>>>
>>
>> Only 7G for win7 os device?
>>
>>
>>  Or how do I tweak it?
>>>
>>> Regards,
>>> Sudeep
>>>
>>>
>>
>
>
> --
> Thanks & Regards,
> Sudeep Narayan Banerjee
>



-- 
Thanks & Regards,
Sudeep Narayan Banerjee
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] ACL's in vDC

[Mateusz Skała]

Hi,
I'm trying to setup vdc admin acl's. He should have rights to create 
vm's from his image's and templates. I setup group (first-group) and 
admin (first-group-admin) for this group, next i set acls:
Applies to   Affected resources 	Resource ID / Owned 
by	   Allowed operations	Zone
 All 	 Zones   All   
use,manageAll
 first-groupVirtual Machines, Images, VM templates   All 
  createAll
 first-groupVirtual Machines, Images, VM templates
first-groupuse,manage,admin,create All
 All Hosts   All 
  use,manageAll
 All Datastores  ID 0
   use  All
 All Datastores  ID 2
   use  All
 All Datastores  ID 101  
   use  All


101 is id of my ceph datastore, id 0 is system datastore.
Network, image and template owner is first-group.
I don't have add button to create VM. If oneadmin create vm and assign 
it to first-group then everything is ok, but i will allow to modify 
template by first-group.

Can someone help me?

--
Regards,
Mateusz
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] OpenNebula does not use MAC value included into VM NIC template

[Alvaro Simon Garcia]

Hi

We need to set (and modify from time to time) the MAC address in our VM 
templates, by default ONE generates this MAC using the default prefix 
value and the VM ip, but we need to set a different MAC in some cases. 
We are including the MAC address into NIC section, as example:



NIC=[
  IP="10.141.8.30",
  MAC="AA:00:00:80:01:00",
  MODEL="virtio",
  NETWORK="br100",
  NETWORK_UNAME="oneadmin",
  TARGET="eth0" ]


but OpenNebula is still using the default value, and at the end we have 
to include the harcoded mac into our vnet conf (and we don't want to do 
that):


LEASE=[ MAC="aa:01:00:80:01:00", IP="10.141.8.40", 
IP6_LINK="fe80::ac01:ff:fe80:100", USED="0", VID="-1" ]


do you know if this is a known issue, or do we need to do something else 
to set the MAC from the VM template? We are testing opennebula 4.6 right now


Thanks in advance!
Álvaro
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Odp.: Re: VM Failed with Windows OS

[Lorenzo Faleschini]

Hi Sudeep ,

I deal with windows machines in ONE day by day (unfortunately).

what I can see here (a part from the raw-qcow issue) is that it seems 
you never installed virtio-drivers (and devices) and you're trying to 
boot using virtio bus.


if you haven't installed in the OS (windows) the "Red Hat Virtio SCSI 
controller" (see VirtIO drivers) you will have no luck in using virtio 
bus.. don't use bus=virtio, use standard emulated IDE ( in the template 
a plain IMAGE=[ID="whatever"]  ) and you eventually be able to boot it.


then if you want to convert it (the window machine) to use virtio bus, 
you can do the following:


1-  attach a second image as virtio device (like this: 
IMAGE=[ID="xx",DEV_PREVIX="vd"]  being "xx" any non persistent image in 
your datastore eg: a cdrom image),


2- boot it  (keeping your main image in IDE emulation without virtio, 
like IMAGE=[ID="yy"]   where "yy" is your vbox converted image of Win's 
C: drive


3- install the newly found "unknown device" with the divers of Red Hat 
Virtio SCSI controller from the binaries relative to your win edition in 
the iso here: 
http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers as 
suggested by Valentin (he's a smart guy, follow his suggestions ;) in 
this way you will tell windows that it's now on "virtio-steroids" that 
is: it will eventually boot from a virtio device 'cause now the 
controller drivers are enabled at boot.


4- then you can shutdown vm, modify template removing the "xx" cdrom 
image you put to install the virtio controller and edit the main image 
(c: drive) with a string like this:

DISK=[AIO="native",CACHE="none",DEV_PREFIX="vd",IMAGE_ID="yy"]
if you find awkard slowliness try to enable default cache for 
virtio and see if you get it any better (windows really sucks anyway.. 
be at peace with it)

DISK=[AIO="native",CACHE="default",DEV_PREFIX="vd",IMAGE_ID="yy"]
i usually get best results with these 2 configs for images of the "best 
OS out there"


5- instatiate it again... boom virtio storage will boot.


hope it helps.

cheers

Lorenzo Faleschini
IT Manager @ Nord Est Systems srl

m: +39 335 6055225 | skype: falegalizeit

Il 16/07/2014 13:13, Sudeep Narayan Banerjee ha scritto:

Dear Mateusz & All,

I tried a lot but looks like I am not able to figure out.

Again the VM says "No bootable device" gpxe searching for bootdisk 
from HDD/Floppy/DVD-CD" etc.


But it is running fine from frontend mode "virt-viewer -c 
qemu:///system myvm3"


I tried to virtually mount the iso in the CD drive but that too did 
not help.


I have also tried the interactive setup: virt-install --prompt  --> 
that too does not work when I instantiate in OpenNebula VM.


I have also tried to write the template in Advanced Tab in OpenNebula 
following [1] but I am failing.


[1] _http://wiki.ieeta.pt/wiki/index.php/OpenNebula#SetupComplete.cmd_


Regards,
Sudeep


On Wed, Jul 16, 2014 at 2:43 PM, Sudeep Narayan Banerjee 
mailto:snbaner...@iitgn.ac.in>> wrote:


Hello Mateusz,

I have given now 17G for win7 OS.

On adding target=hda * hdb, it throws the below error.

[root@front images]# virt-install --connect qemu:///system --name
win7 --ram 1024 --vcpus 2 --disk

path=/var/lib/libvirt/images/win7.qcow2,size=17,format=qcow2,bus=virtio,cache=none,target=hda
--cdrom /home/Windows-7-x86.iso,target=hdb --vnc --os-type=windows
--os-variant=win7 -noautoconsole --accelerate --noapic --keymap=en-us

ERRORUnknown options ['target']

Regards,
Sudeep



On Wed, Jul 16, 2014 at 1:57 PM, Mateusz Ska?a
mailto:mateusz.sk...@budikom.net>> wrote:



W dniu 2014-07-16 08:00, Sudeep Narayan Banerjee napisa?(a):

Dear Mateusz,

Thanks for replying. Is the below command correct?

[root@front ~]# virt-install --connect qemu:///system
--name win7
--ram 1024 --vcpus 2 --disk

path=/var/lib/libvirt/images/win7.qcow2,size=7,format=qcow2,bus=virtio,cache=none
--cdrom /home/Windows-7-x86.iso --vnc --os-type=windows
--os-variant=win7 -noautoconsole --accelerate --noapic
--keymap=en-us


try to add target=hda, for example:

virt-install --connect qemu:///system --name win7 --ram 1024
--vcpus 2 --disk

path=/var/lib/libvirt/images/win7.qcow2,size=7,format=qcow2,bus=virtio,cache=none,target=hda
--cdrom /home/Windows-7-x86.iso,target=hdb --vnc
--os-type=windows --os-variant=win7 -noautoconsole
--accelerate --noapic --keymap=en-us

If You are using virtio then drivers for this bus will be
needed, so You need add floppy drive with drivers.



The win7.qcow2 image is prepared under
/var/lib/libvirt/images folder

[root@front images ~]# qemu-img create -f qcow2 -o
preallocation=metadata /var/lib/libvirt/images/win7.qcow2 7G



  

Re: [one-users] templates and images explanation needed

[Aradyel]

Hello,

We would like to create a few templates with persistent images so they
can be shared with a group of users, so then users can provision new
VM's, each having its own VM with persistent image. The persistent image
is bacause we want that VM's be users personal VM's (aka desktops).

But if I create VM from a template, this VM is using image from template
so when another users wants to create another VM from this template, he
can't because image is in use. If this is correct behaviour I wonder
what is the purpose of this. Can someone explain this?

Thanks

Pawel



In the context of Opennebula the persistent image indicates that the 
changes done after shutting down the VM will return to the image (will 
be updated).

From the documentation:
"Note that depending on the Datastore type a persistent image can be a 
link to the original image,

so any modification is directly made on the image."

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org