>=3D3B On Tue=3D2C Oct 20=3D2C 2015 at 4:51 AM=3D2C Dan K=
enigsberg =3D
<=3D3Bdanken at redhat.com>=3D3B wrote:=3D0A=3D
>=3D3B =3D0A=3D
>=3D3B >=3D3B On Mon=3D2C Oct 19=3D2C 2015 at 09:16:06PM +0200=3D2C Joh=
an Kooijma=3D
n wrote:=3D0A=3D
>=3D3B >=3D3B >=3D3B Never seen an  update to this ticket. Are there =
any pl=3D
ans?=3D0A=3D
>=3D3B >=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B >=3D3B On Tue=3D2C Jun 24=3D2C 2014 at 3:35 PM=3D2C Sve=
n Kieske <=3D
=3D3BS.Kieske at mittwald.de>=3D3B=3D0A=3D
>=3D3B >=3D3B wrote:=3D0A=3D
>=3D3B >=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B Am 24.06.2014 15:13=3D2C schrieb Nathan=
a=3DEBl Blan=3D
chet:=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B >=3D3B Hi all=3D2C=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B >=3D3B now rhel7 is out=3D2C it will =
become a par=3D
t of the ovirt project in a=3D0A=3D
>=3D3B >=3D3B near=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B >=3D3B future. Given taht official LX=
C support =3D
aims to complete the KVM=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B >=3D3B virtualization part=3D2C is LX=
C planned to=3D
  be supported for linux VM by=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B >=3D3B ovirt=3D2C like openvz is with=
 proxmox?=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B very good question=3D2C can't wait to r=
ead an ans=3D
wer!=3D0A=3D
>=3D3B >=3D3B >=3D3B >=3D3B +1 from here.=3D0A=3D
>=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B I'm not aware of current plans. We can consider this when=
 ovi=3D
rt-4.0=3D0A=3D
>=3D3B >=3D3B feature request season opens.=3D0A=3D
>=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B Until then=3D2C can you share your own use case for runni=
g LXC?=3D
=3D0A=3D
>=3D3B >=3D3B=3D0A=3D
>=3D3B =3D0A=3D
>=3D3B It seems like Proxmox have quite the install base especially due t=
o =3D
the=3D0A=3D
>=3D3B ability to mix containers and "fat" VMs. AFAIK that's the only fea=
tu=3D
re they=3D0A=3D
>=3D3B have that is ahead of oVirt. And that install base should tell us =
th=3D
is is=3D0A=3D
>=3D3B indeed a feature needed and widely used.=3D0A=3D
>=3D3B =3D0A=3D
>=3D3B =3D0A=3D
>=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B I'd love to see a vdsm hook that translates the qemu-kvm =
domx=3D
ml into an=3D0A=3D
>=3D3B >=3D3B lxc one=3D2C as a first step. Anyone?=3D0A=3D
>=3D3B >=3D3B=3D0A=3D
>=3D3B =3D0A=3D
>=3D3B That can be a fun project to do=3D2C but I'm not volunteering just=
 yet=3D
 =3D3B)=3D0A=3D
>=3D3B =3D0A=3D
>=3D3B =3D0A=3D
>=3D3B >=3D3B=3D0A=3D
>=3D3B >=3D3B Dan.=3D0A=3D
>=3D3B >=3D3B _______________________________________________=3D0A=3D
>=3D3B >=3D3B Users mailing list=3D0A=3D
>=3D3B >=3D3B Users at ovirt.org=3D0A=3D
>=3D3B >=3D3B http://lists.ovirt.org/mailman/listinfo/users=3D0A=3D
>=3D3B >=3D3B=3D0A=3D

A couple of related questions= =3D :

*) what can we expect from the deprecation of li= =3D bvirt LXC driver in RHEL? (CentOS would follow suit=3D2C barring an extraor= di=3D nary effort from the Virtualization SIG=3D2C akin to the Xen-on-CentOS one)=

*) dreaming of a future convergence of oVirt-node a= =3D nd Atomic would be... well=3D2C just dreaming? =3D3B)

<= div>=3D Giuseppe