WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

RE: [Xen-API] Re: Project KRONOS - Networking

To: Sébastien Riccio <sr@xxxxxxxxxxxxxxx>, "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-API] Re: Project KRONOS - Networking
From: Paul Durrant <Paul.Durrant@xxxxxxxxxx>
Date: Fri, 2 Sep 2011 12:01:15 +0100
Accept-language: en-US
Acceptlanguage: en-US
Cc: Jonathan Ludlam <Jonathan.Ludlam@xxxxxxxxxxxxx>
Delivery-date: Fri, 02 Sep 2011 04:02:58 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4E6026BC.3030206@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> <C28EE874-E850-4589-8725-F60F0B5EBA2B@xxxxxxxxxxxxx> <4E6026BC.3030206@xxxxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcxpCXqNzeho5qkVRB+K/Mp22LG3zQAVeW1w
Thread-topic: [Xen-API] Re: Project KRONOS - Networking

The failure of qemu-ifup is mostly likely key here. If the tap device is not initialized then, when qemu-dm is lauched, it will fail to open the tap, hence the network device model will fail to initialize, hence it will exit prematurely.

 

  Paul

 

From: xen-api-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Sébastien Riccio
Sent: 02 September 2011 01:44
To: xen-api@xxxxxxxxxxxxxxxxxxx
Cc: Jonathan Ludlam
Subject: [Xen-API] Re: Project KRONOS - Networking

 

On 01.09.2011 22:45, Jonathan Ludlam wrote:

Hi Sebastien,

 

qemu should (theoretically) be logging to syslog - has it dumped anything interesting in there at all?

 

Jon

 

On 1 Sep 2011, at 14:29, Sébastien Riccio wrote:



<xensource.txt>

 


Hi Jonathan,

Thanks for pointing that out.
Here is a transcript of an interesting part of syslog while trying to launche a network attached qemu vm:

"/etc/xen/scripts/qemu-ifup: could not launch network script" and "Could not initialize device 'tap'"  seems
to be quite revelant, i'll try to look what the script tries to do.

Cheers,
Sébastien

Sep  2 02:41:26 xen-blade13 scripts-vif: Called as "online type_if=vif" domid:15 devid:0 mode:openvswitch
Sep  2 02:41:26 xen-blade13 fe: qemu-dm-15[12453]: domid: 15
Sep  2 02:41:26 xen-blade13 scripts-vif: Setting vif15.0 MTU 1500
Sep  2 02:41:26 xen-blade13 fe: qemu-dm-15[12453]: -c config qemu network with xen bridge for
Sep  2 02:41:26 xen-blade13 fe: qemu-dm-15[12453]: tap15.0 xapi2
Sep  2 02:41:26 xen-blade13 fe: qemu-dm-15[12453]: can't add tap15.0 to bridge xapi2: Operation not supported
Sep  2 02:41:26 xen-blade13 fe: qemu-dm-15[12453]: /etc/xen/scripts/qemu-ifup: could not launch network script
Sep  2 02:41:26 xen-blade13 fe: qemu-dm-15[12453]: Could not initialize device 'tap'
Sep  2 02:41:26 xen-blade13 scripts-vif: Adding vif15.0 to xapi2 with address fe:ff:ff:ff:ff:ff
Sep  2 02:41:26 xen-blade13 logger: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=
Sep  2 02:41:26 xen-blade13 fe: 12453 (/usr/lib/xen-common/xapi/libexec/qemu-dm-wrapper 15 -d 15 -m 1536 -boot dc -s...) exitted with code 1
Sep  2 02:41:26 xen-blade13 scripts-vif: Failed to ip link set vif15.0 address fe:ff:ff:ff:ff:ff
Sep  2 02:41:26 xen-blade13 scripts-vif: vif15.0 external-ids:"xs-vm-uuid"="7ef51a1e-2a0a-5ef4-50f6-618cbb251543"
Sep  2 02:41:26 xen-blade13 scripts-vif: vif15.0 external-ids:"xs-vif-uuid"="ea160a73-36a6-cfdc-dcf9-3083653d917b"
Sep  2 02:41:26 xen-blade13 scripts-vif: vif15.0 external-ids:"xs-network-uuid"="65c59465-b20d-f640-01bd-c78e83ae7b72"
Sep  2 02:41:26 xen-blade13 scripts-vif: vif15.0 external-ids:"attached-mac"="3a:97:29:2f:c0:aa"
Sep  2 02:41:26 xen-blade13 scripts-vif: /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port vif15.0 -- add-port xapi2 vif15.0 -- set interface vif15.0 external-ids:"xs-vm-uuid"="7ef51a1e-2a0a-5ef4-50f6-618cbb251543"#012-- set interface vif15.0 external-ids:"xs-vif-uuid"="ea160a73-36a6-cfdc-dcf9-3083653d917b"#012-- set interface vif15.0 external-ids:"xs-network-uuid"="65c59465-b20d-f640-01bd-c78e83ae7b72"#012-- set interface vif15.0 external-ids:"attached-mac"="3a:97:29:2f:c0:aa"
Sep  2 02:41:26 xen-blade13 ovs-vsctl: 00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=30 -- --if-exists del-port vif15.0 -- add-port xapi2 vif15.0 -- set interface vif15.0 "external-ids:\"xs-vm-uuid\"=\"7ef51a1e-2a0a-5ef4-50f6-618cbb251543\"" -- set interface vif15.0 "external-ids:\"xs-vif-uuid\"=\"ea160a73-36a6-cfdc-dcf9-3083653d917b\"" -- set interface vif15.0 "external-ids:\"xs-network-uuid\"=\"65c59465-b20d-f640-01bd-c78e83ae7b72\"" -- set interface vif15.0 "external-ids:\"attached-mac\"=\"3a:97:29:2f:c0:aa\""
Sep  2 02:41:26 xen-blade13 kernel: [46644.650044] device vif15.0 entered promiscuous mode
Sep  2 02:41:26 xen-blade13 kernel: [46644.689221] ADDRCONF(NETDEV_UP): vif15.0: link is not ready

_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api