Bug 1326819

Summary:	unsupported network type="ethernet" in libvirt 1.2.11
Product:	[Community] Virtualization Tools	Reporter:	sonia <soniaverma9727>
Component:	libvirt	Assignee:	Libvirt Maintainers <libvirt-maint>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	jtomko, rbalakri, soniaverma9727
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-13 13:23:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description sonia 2016-04-13 13:18:41 UTC

Description of problem:I tested the LXC VM with libvirt 1.2.11


I'm  getting following errors..

virsh -c lxc: start test      
error: Failed to start domain test
error: internal error: Unsupported network type ethernet

I'm using the below XML file for launching LXC VM..

<domain type="lxc">
  <uuid>64c48da2-e318-4085-8b88-c980aab4de34</uuid>
  <name>test</name>
  <memory>524288</memory>
  <vcpu>1</vcpu>
  <os>
    <type machine="virt">exe</type>
    <cmdline>root=/dev/ram0 rw  console=ttyAMA0 rootwait earlyprintk</cmdline>
    <init>/bin/sh</init>
  </os>
  <clock offset="utc"/>
  <devices>
    <file/>
    <interface type='ethernet'>
      <mac address='e2:75:ee:92:33:89'/>
      <script path=''/>
      <target dev='tap74f2-f5'/>
    </interface>
    <console type="pty"/>
  </devices>
</domain>



Version-Release number of selected component (if applicable):
1.2.11

How reproducible:
virsh --lxc: define lxc.xml
virsh --lxc: start lxc.xml

error: Failed to start domain test
> error: internal error: Unsupported network type ethernet



Steps to Reproduce:
1.
2.
3.

Actual results:
 Unsupported network type ethernet


Expected results:
Instance is running.

Additional info:

Comment 1 Ján Tomko 2016-04-13 13:23:34 UTC


*** This bug has been marked as a duplicate of bug 1325687 ***