[one-users] Virtual Machine has no network interfaces

Ronaldo Pinheiro ronaldopg010 at gmail.com
Fri Jun 15 13:30:50 PDT 2012


Hi,

It worked. Lack of attention.

Thank you for your help and time Carlos.

Ronaldo.


On Fri, Jun 15, 2012 at 7:27 AM, Carlos Martín Sánchez <
cmartin at opennebula.org> wrote:

> Hi,
>
> The network interfaces are defined with the NIC attribute, not NETWORK [1].
>
> Regards
>
> [1] http://opennebula.org/documentation:rel3.4:template#network_section
>
> --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - The Open-source Solution for Data Center Virtualization
> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
>
>
>
> On Thu, Jun 14, 2012 at 9:46 PM, Ronaldo Pinheiro <ronaldopg010 at gmail.com>wrote:
>
>> Here is the VM template im using:
>> NAME = "VM"
>> CPU = 1
>> MEMORY = 1024
>>
>> OS = [
>>         boot = hd,
>>         arch = x86_64 ]
>>
>> DISK = [
>>         image_id = 0,
>>         bus = virtio ]
>>
>> NETWORK = [
>>         network = "LAN",
>>         bridge = "br0",
>>         model = virtio ]
>>
>> GRAPHICS = [
>>         type = "vnc",
>>         listen = "0.0.0.0"]
>>
>> Here is the command onevm show output:
>> $ onevm show 34
>> VIRTUAL MACHINE 34
>> INFORMATION
>> ID             : 34
>> NAME           : VM
>> STATE          : ACTIVE
>> LCM_STATE      : RUNNING
>> START TIME     : 06/14 16:38:20
>> END TIME       : -
>> DEPLOY ID:     : one-34
>>
>> VIRTUAL MACHINE
>> MONITORING
>> NET_TX         : 0
>> USED MEMORY    : 0
>> USED CPU       : 0
>> NET_RX         : 0
>>
>> VIRTUAL MACHINE
>> TEMPLATE
>> CPU=1
>> DISK=[
>>   BUS=virtio,
>>   CLONE=YES,
>>   DISK_ID=0,
>>   DRIVER=qcow2,
>>   IMAGE=Planeswalker,
>>   IMAGE_ID=5,
>>   READONLY=NO,
>>   SAVE=NO,
>>   SOURCE=/var/lib/one//images/b355510b41157fcc886246ac3c3e46993278e0c3,
>>   TARGET=hda,
>>   TYPE=DISK ]
>> GRAPHICS=[
>>   LISTEN=0.0.0.0,
>>   PORT=5934,
>>   TYPE=vnc ]
>> MEMORY=1024
>> NAME=VM
>> NETWORK=[
>>   BRIDGE=br0,
>>   MODEL=virtio,
>>   NETWORK=LAN ]
>> OS=[
>>   ARCH=x86_64,
>>   BOOT=hd ]
>> VMID=34
>>
>>
>>
>> On Thu, Jun 14, 2012 at 1:16 PM, Carlos Martín Sánchez <
>> cmartin at opennebula.org> wrote:
>>
>>> Hi,
>>>
>>> Can you paste your VM template, and the output of onevm show?
>>> By the way, OpenNebula has come a long way since 2.2, the latest version
>>> is 3.4
>>>
>>> Regards
>>> --
>>> Carlos Martín, MSc
>>> Project Engineer
>>> OpenNebula - The Open-source Solution for Data Center Virtualization
>>> www.OpenNebula.org | cmartin at opennebula.org | @OpenNebula<http://twitter.com/opennebula><cmartin at opennebula.org>
>>>
>>>
>>>
>>> On Thu, Jun 14, 2012 at 4:08 PM, Ronaldo Pinheiro <
>>> ronaldopg010 at gmail.com> wrote:
>>>
>>>> Hello,
>>>>
>>>> I am running opennebula 2.2 in ubuntu server 11.10, which was installed
>>>> through apt-get.
>>>> Everything works fine, except one thing. When i execute onevm submit,
>>>> the VM goes to the host and starts normally, but as soon as it boots, there
>>>> are no network interfaces. If i execute ifconfig, it shows "loopback" and
>>>> "virbr0".
>>>> The host machine uses KVM.
>>>>
>>>> If i use virt-manager to submit the same VM, it starts, shows an
>>>> additional interface "eth0", and gets an IP address from the dhcp server.
>>>>
>>>> I suppose there is an error in my opennebula configuration.
>>>> I have set oned.conf to work with kvm and i cant see any errors in the
>>>> template files.
>>>> The virtual network used is set to ranged. The bridge is "br0".
>>>>
>>>> I cant think of anything else. Am i missing something?
>>>> All help is greatly appreciated.
>>>> Thanks in advance,
>>>>
>>>> Ronaldo.
>>>>
>>>>
>>>> _______________________________________________
>>>> 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/20120615/4776a96f/attachment-0002.htm>


More information about the Users mailing list