This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-API] Re: Project KRONOS - Networking

To: Sébastien Riccio <sr@xxxxxxxxxxxxxxx>
Subject: [Xen-API] Re: Project KRONOS - Networking
From: Mike McClurg <mike.mcclurg@xxxxxxxxxx>
Date: Thu, 1 Sep 2011 21:42:02 +0100
Cc: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>, Rob Hoes <Rob.Hoes@xxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 01 Sep 2011 13:42:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E5F88CC.6040104@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <4E5F88CC.6040104@xxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; Linux i686; rv:5.0) Gecko/20110807 Icedove/5.0
On 09/01/2011 02:29 PM, Sébastien Riccio wrote:

I managed to adapt the interface-reconfigure and other related scripts
to enable networking
for xapi on debian, using openvswitch. I have not yet attached the
modified files to my mail because
there is still some parts I need to modify (the non-openvswitch one for

So actually it's working, I can create bonds, vlans and attach them on a
virtual machine.
Configure management interfaces etc...

Attaching a network to a linux vm is fine, the networking is working.
But if I try to start a windows (qemu) vm with the same network attached
i get this error:

01.09.2011 15:21:16 Error: Starting VM 'Win2008-64bit-R2' - Internal
error: device model failed to initialise: qemu-dm exitted unexpectedly

Without the network attached it works.

You will find attached the corresponding xensource.log entries

If someone has an idea ?

Once again, thanks for all the help with the Kronos testing you're doing. Our network guy is planning on doing a complete rewrite for the next XenServer release, but hopefully he'll have it done soon enough that we can use it in Kronos.

HVM domains get built with an emulated network card, and then once the domain is initialized they are given a paravirtualized nic. It could be that there is something strange going on in this HVM nic initialization code that's not working right with Kronos.

Feel free to send your version of interface-reconfigure directly to Jon and I, if you're not ready to release it publicly. We can start testing it ourselves as well, and maybe figure out the HVM problem.


xen-api mailing list