It is currently Thu Nov 23, 2017 11:12 am


All times are UTC




Post new topic Reply to topic  [ 1 post ] 
Author Message
 Post subject: Telnet/ console dbus error. GNS3 V1
PostPosted: Tue Oct 21, 2014 11:16 am 
Offline

Joined: Wed Sep 10, 2014 6:51 pm
Posts: 9
I have tried Ubuntu 14.04, debian Jessie x86 and now Mint 17 . This console issue only happens with virtualbox and qemu when trying to emulate the XRv.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------GNS3 management console. Running GNS3 Early Release (ER) version 1.0.dev1 on Linux (32-bit).
Copyright (c) 2006-2014 GNS3 Technologies.

output below from mint 17.
================================================================================================================================
[I 141021 12:03:49 qemu_vm:212] XRv1: updating hda_disk_image from '' to '/root/GNS3/images/QEMU/iosxrv-demo-5.2.0.vmdk'
[I 141021 12:03:49 qemu_vm:229] QEMU VM XRv1 has been created
Formatting '/tmp/gns3-57t380lk-files/qemu/vm-1/hda_disk.qcow2', fmt=qcow2 size=3221225472 backing_file='/root/GNS3/images/QEMU/iosxrv-demo-5.2.0.vmdk' encryption=off cluster_size=65536 lazy_refcounts=off
[I 141021 12:03:51 qemu_vm:710] /usr/bin/qemu-img returned with 0
[I 141021 12:03:51 qemu_vm:538] starting QEMU: ['/usr/bin/qemu-system-x86_64', '-name', 'XRv1', '-m', '3004', '-hda', '/tmp/gns3-57t380lk-files/qemu/vm-1/hda_disk.qcow2', '-serial', 'telnet:127.0.0.1:5001,server,nowait', '-device', 'e1000,mac=00:00:ab:18:cc:00,netdev=gns3-0', '-netdev', 'user,id=gns3-0']
[I 141021 12:03:51 qemu_vm:540] logging to /tmp/gns3-57t380lk-files/qemu/vm-1/qemu.log
[I 141021 12:03:51 qemu_vm:546] QEMU VM instance 1 started PID=5739
[I 141021 12:03:51 qemu_vm:261] XRv1 has started
[I 141021 12:04:00 telnet_console:47] starting telnet console "roxterm -n XRv1 --tab -e telnet 127.0.0.1 5001"

** (roxterm:5741): CRITICAL **: Error connecting to dbus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

** (roxterm:5741): CRITICAL **: optsdbus_listen_for_opt_signals: assertion 'rtdbus_ok' failed

** (roxterm:5741): CRITICAL **: optsdbus_listen_for_stuff_changed_signals: assertion 'rtdbus_ok' failed

** (roxterm:5741): CRITICAL **: optsdbus_listen_for_set_profile_signals: assertion 'rtdbus_ok' failed

** (roxterm:5741): CRITICAL **: optsdbus_listen_for_set_colour_scheme_signals: assertion 'rtdbus_ok' failed

** (roxterm:5741): CRITICAL **: optsdbus_listen_for_set_shortcut_scheme_signals: assertion 'rtdbus_ok' failed

** (roxterm:5741): WARNING **: Failed to connect to session manager: None of the authentication protocols specified are supported




Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 1 post ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group

phpBB SEO