Re: [Bug 723983] Re: virtio-net performance in 10Gbs lan
From what I can see it is. On 03/20/2011 08:57 PM, Serge Hallyn wrote: @waltc, is this bug fixed for you in the latest natty qemu-kvm? Latest natty is based on qemu-kvm-0.14.0 release, which you say includes the fixes you were looking for. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] Re: virtio-net performance in 10Gbs lan
** Changed in: qemu-kvm (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] Re: virtio-net performance in 10Gbs lan
I don't know that I can successfully vet the fix. I can say from the hit I found on some forum the guy with the 10Gb network verified as fixed after applying the 'bottom-half fix. I will try that this w/e. I see you changed the status to incomplete. Is that due to waiting on me? Oh, I also appreciate you having gotten right on this. Thank you! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] Re: virtio-net performance in 10Gbs lan
My omission. I thought I had said I was on 10.10. I am at 10.10 for both UEC as well as guests. I merely tried 11.04 to see if that resolved the issue. However I really didn't expect to see a change, my nic is 1Gb. I was helping a guy on the Euca mb that didn't realize there was a virtio_net and then he came back with how it helped but only slightly and his 10Gb network was running at slightly better than 1Gb. I read a blog by Graziano@Euca who mentioned work on Qemu and I went to their site and saw the 0.14 was now GA, up from the rc1 in 11.04alpha. I looked into it and saw the reference to bottom-half which was in the other mb thread I tried to copy referring to the guy having rebuilt with the bottom-half fix but found no other reference to it. But the, aforementioned, guy did say that did resolve the issue, so yes, Qemu 0.14 resolves this problem. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] Re: virtio-net performance in 10Gbs lan
I believe this is fixed in QEMU 0.14... referring to changelist (first paragraph) on http://wiki.qemu.org/Changelog/0.14#virtio The references I gave above specifically referenced the authors applying the 'bottom-half' fix, although they did not, as I recall, mention what the fixed was against. Where QEMU 0.14 is final now will Natty pick the final release of it? To answer your questions, I am running 10.10 Maverick as the node controller and guest OS. Does that fix go against the host (node controller OS or the guest OS? In other words, would running a current Natty ec2 image resolve the issue? Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] Re: virtio-net performance in 10Gbs lan
I used iperf -s on one instance and iperf -c xxx.xx.xx.xx on the client image of two guest OS's running under UEC. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] Re: virtio-net performance in 10Gbs lan
I tried running natty guests and the results were actually slightly slower. This makes sense as kvm is a host component and qemu is affiliated with kvm. Presumably there is no guest component? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 723983] [NEW] virtio-net performance in 10Gbs lan
Public bug reported: Is this a bug or configuration? virtio_net performance In the course of helping a fellow UEC user he, and consequently we, hit a potential bug. In the case of a system with an e1000 or even a Realtek NIK or simulated NIC performance sucks with the emulated driver in an instance. But changing the eucalyptus.conf settings for virtio_* to 1 the generated kvm command line uses virtio where possible. This brings performance up substancially. In the case of an e1000 or Realtek NIC performance is right about 800Mbs (very close to hardware speed. This is wonderful and way better than using a fully virtualized driver. Client connecting to 172.19.1.8, TCP port 5001 TCP window size: 16.0 KByte (default) [ 3] local 172.19.1.7 port 60596 connected with 172.19.1.8 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0- 1.0 sec 67.4 MBytes 566 Mbits/sec [ 3] 1.0- 2.0 sec 90.0 MBytes 755 Mbits/sec [ 3] 2.0- 3.0 sec 90.5 MBytes 759 Mbits/sec [ 3] 3.0- 4.0 sec 98.4 MBytes 826 Mbits/sec [ 3] 4.0- 5.0 sec 91.9 MBytes 771 Mbits/sec [ 3] 5.0- 6.0 sec 92.9 MBytes 779 Mbits/sec [ 3] 6.0- 7.0 sec 94.0 MBytes 789 Mbits/sec [ 3] 7.0- 8.0 sec 97.1 MBytes 815 Mbits/sec [ 3] 8.0- 9.0 sec 103 MBytes 860 Mbits/sec [ 3] 9.0-10.0 sec 95.7 MBytes 803 Mbits/sec [ 3] 0.0-10.0 sec 921 MBytes 772 Mbits/sec However for people running 10GB NIC cards by specifying virtio_net only brings their speed up to just over 1GB/s. ubuntu@172:~$ ./nuttcp 172.19.1.4 - virtual machine speed 1283.1875 MB / 10.00 sec = 1076.4544 Mbps 39 %TX 45 %RX 0 retrans 1.49 msRTT Same test at the base install level - real measured machine speed hoot@cloud1:~$ ./nuttcp 10.10.10.3 11048.6250 MB / 10.00 sec = 9265.0703 Mbps 38 %TX 87 %RX 0 retrans 0.22 msRTT From just anecdotal hits on Google this appears to be an introduced bug in recent versions of either KVM or Linux Kernel. I saw a thread where if one were to recompile and install a different kvm-qemu the problem is rectified. I open this thread in order to provide a central place to separate fact from fiction and, hopefully, provide closure on this issue. If such a fix exists, will, or can, it be included in U11.04? References: http://www.mail-archive.com/kvm@vger.../msg42690.html http://forum.proxmox.com/threads/500...et-performance ** Affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in ubuntu. https://bugs.launchpad.net/bugs/723983 Title: virtio-net performance in 10Gbs lan -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 562189] Re: AttributeError: 'Libvirt' object has no attribute 'vm'
I also got this error on 10.10 and, to David's comment, changing the name of the --hostname bypassed the problem as you created a new vm. But using virsh or virt-manager to delete the pre-existing image resolved the problem. However, my question is this. Is the -o option intended to remove any files, including a preexisting image or does it just remove other transient files that may exist but is NOT intended to delete what may be a functioning production VM? For myself, I am totally fine with Lennart's suggestion of an error message if the vm exists already. Would someone clarify what the purpose of the -o is in that case? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. https://bugs.launchpad.net/bugs/562189 Title: AttributeError: 'Libvirt' object has no attribute 'vm' -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 613033] Re: eucalyptus-cloud: cloud fails to start on separate install
I have eucalytus at 2.0~bzr1241-0ubuntu4,1 I receive the following when sourcing eucarc WARN: Walrus URL is not configured. In reviewing the cloud-error.log It shows an initial failure with 13:32:55 ERROR [SystemConfiguration:529263...@qtp-248808824-7] com.eucalyptus.util.EucalyptusCloudException: Error locating information for [S ystemConfiguration id=-1 cloudHost=null defaultKernel=null defaultRamdisk=null registrationId=null maxUserPublicAddresses=null doDynamicPublic Addresses=null systemReservedPublicAddresses=null dnsDomain=null nameserver=null nameserverAddress=null] com.eucalyptus.util.EucalyptusCloudException: Error locating information for [SystemConfiguration id=-1 cloudHost=null defaultKernel=null defa ultRamdisk=null registrationId=null maxUserPublicAddresses=null doDynamicPublicAddresses=null systemReservedPublicAddresses=null dnsDomain=nul l nameserver=null nameserverAddress=null] at com.eucalyptus.entities.EntityWrapper.getUnique(EntityWrapper.java:138) at edu.ucsb.eucalyptus.cloud.entities.SystemConfiguration.getSystemConfiguration(SystemConfiguration.java:257) at edu.ucsb.eucalyptus.admin.server.Registration.getRegistrationId(Registration.java:142) at edu.ucsb.eucalyptus.admin.server.Registration.doGet(Registration.java:148) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:390) at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418) at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230) at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.handler.rewrite.RewriteHandler.handle(RewriteHandler.java:230) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:542) at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:926) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:549) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:410) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:582) 13:32:57 FATAL [Bootstrap$Stage:main] Fatal error occured during bootstrap: com.eucalyptus.bootstrap.Bootstrap$Stage.start:118 java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:57) at java.lang.Runtime.addShutdownHook(Runtime.java:209) at com.eucalyptus.event.SystemClock.setupTimer(SystemClock.java:88) at com.eucalyptus.ws.ServiceVerifyBootstrapper.start(ServiceVerifyBootstrapper.java:37) at com.eucalyptus.bootstrap.Bootstrap$Stage.start(Bootstrap.java:112) at com.eucalyptus.bootstrap.SystemBootstrapper.start(SystemBootstrapper.java:148) 13:32:57 ERROR [BootstrapException:main] Fatal error occured: com.eucalyptus.bootstrap.BootstrapException.fatal:54 java.lang.IllegalStateException: Shutdown in progress at java.lang.ApplicationShutdownHooks.add(ApplicationShutdownHooks.java:57) at java.lang.Runtime.addShutdownHook(Runtime.java:209) It sure sounds like the same thing as 613033 Is there anything I can provide you to help diagnose my problem, which may be this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. https://bugs.launchpad.net/bugs/613033 Title: eucalyptus-cloud: cloud fails to start on separate install -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 550689] Re: vmbuilder: error: no such option: --firstlogin
Is this going to be fixed and, if so, when? I have this problem as well and the ec2- tools appear broken in lucid as well. Consequently I, and presumably others, can't build specialized images. -- vmbuilder: error: no such option: --firstlogin https://bugs.launchpad.net/bugs/550689 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 587340] Re: otherwise live instance goes deaf connection refused
What I discovered, which means there are several paths to this problem, is the private address, in this case, remained valid. I can connect via the private address. I tried to connect then release with the intent of connect the original ip address of 192.168.3.100 but in both cases got the error Address: Permission denied while trying to release address: 192.168.3.100 The same error occurred when prefixed by sudo. -- otherwise live instance goes deaf connection refused https://bugs.launchpad.net/bugs/587340 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 587340] Re: otherwise live instance goes deaf connection refused
OK, you asked for more information. I gave you the requested information. Could this bug be placed in a status where it won't self destruct if nobody picks it up in 53 days? Thanks -- otherwise live instance goes deaf connection refused https://bugs.launchpad.net/bugs/587340 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 587340] Re: otherwise live instance goes deaf connection refused
I believe it is 1.6.2
I followed https://help.ubuntu.com/community/UEC/PackageInstall to a tee.
The only variation was rather than installing on a 10.4 image of Ubuntu Server
I installed it on Ubuntu Desktop at 10.4.
In order to insure the public addresses given the install script of the
cluster components did not interfere with anything previously in
existence I gave the ip address range 192.168.3.100-192.168.3.130 or
maybe it was 150, I think it was 130 though, so there would be 30
available public IPs.
I do have a VPNC configured but I do not know what magic it does with IP
addresses.
My Netgear router is on 192.168.0.2-192.168.0.254, the netmask is
255.255.0.0
the output from ifconfig is:
eth0 Link encap:Ethernet HWaddr 00:1e:4f:b4:e2:b5
inet addr:192.168.0.6 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::21e:4fff:feb4:e2b5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3928276 errors:0 dropped:0 overruns:0 frame:0
TX packets:4744355 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2479644119 (2.4 GB) TX bytes:3283396517 (3.2 GB)
Interrupt:17
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:23077137 errors:0 dropped:0 overruns:0 frame:0
TX packets:23077137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:16565722660 (16.5 GB) TX bytes:16565722660 (16.5 GB)
vmnet1Link encap:Ethernet HWaddr 00:50:56:c0:00:01
inet addr:192.168.5.1 Bcast:192.168.5.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12230 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vmnet8Link encap:Ethernet HWaddr 00:50:56:c0:00:08
inet addr:172.16.207.1 Bcast:172.16.207.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12239 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vmnet1 and 8 is, apparently, from VMWare Workstation which I use for a
Windows XP image.
According to the instructions for the aforementioned installation from
packages, the range I gave UEC was a unused, isolated range.
The UEC dhcp.conf is:
w...@cor720:~$ cat /var/run/eucalyptus/net/euca-dhcp.conf
# automatically generated config file for DHCP server
default-lease-time 1200;
max-lease-time 1200;
ddns-update-style none;
shared-network euca {
subnet 172.19.1.0 netmask 255.255.255.224 {
option subnet-mask 255.255.255.224;
option broadcast-address 172.19.1.31;
option domain-name-servers 192.168.0.1, 127.0.0.1;
option routers 172.19.1.1;
}
host node-172.19.1.2 {
hardware ethernet d0:0d:41:31:06:66;
fixed-address 172.19.1.2;
}
host node-172.19.1.3 {
hardware ethernet d0:0d:3E:C4:07:F8;
fixed-address 172.19.1.3;
}
host node-172.19.1.4 {
hardware ethernet d0:0d:39:38:07:41;
fixed-address 172.19.1.4;
}
host node-172.19.1.5 {
hardware ethernet d0:0d:58:A4:0A:49;
fixed-address 172.19.1.5;
}
}
The single node controller machine was installed from a Ubuntu Server
10.4 cd and is reserved the address 192.168.0.12 on the aforementioned
wireless router. On it I constructed the bridged network precisely to
the instructions given in the url noted above:
interface=eth0
bridge=br0
sudo sed -i s/^iface $interface inet \(.*\)$/iface $interface inet
manual\n\nauto br0\niface $bridge inet \1/ /etc/network/interfaces
sudo tee -a /etc/network/interfaces EOF
bridge_ports $interface
bridge_fd 9
bridge_hello 2
bridge_maxage 12
bridge_stp off
EOF
Feel free to request whatever else I can provide to assist you.
Thanks,
Walt
--
otherwise live instance goes deaf connection refused
https://bugs.launchpad.net/bugs/587340
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 587340] [NEW] otherwise live instance goes deaf connection refused
Public bug reported: I had an instance up and running for hours, quite successfully. I left it alone for awhile and when I went back to that cmd session the window was dead, as when you shell into another machine and drop the vpn. In that case the entire window is unresponsive. I tried opening another session and logging in from there. no good. I tried rebooting the instance and then logging back in. no good. I do not believe the instance rebooted at all. I did a describe-instances and it showed as running. I did a terminate-instance and it shutdown. I restarted it and still can not get in. To my knowledge nothing happened at the cluster. No matter what I do I receive, after a suitable delay ssh: connect to host 192.168.3.100 port 22: Connection refused I tried the private ip address with the same results. I suspect that isn't enough for anyone to diagnose what happened, unless it is a known bug. Where should I look for the answer, and better yet, what would prevent that in the future. It had been running fine. I had a mysql as well as tomcat 6 tasksel up and running on it. I had copied over a complete over 2M row database and was accessing it through the instance, until it went silent. Thanks, Walt ** Affects: eucalyptus (Ubuntu) Importance: Undecided Status: New -- otherwise live instance goes deaf connection refused https://bugs.launchpad.net/bugs/587340 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 587340] Re: otherwise live instance goes deaf connection refused
There is more history and documentation in Question #112157 Effectively I am running the cluster controller of a managednvlan UEC on an instance of Ubuntu 10.4 Desktop. What I had noticed, over time is running instances would go deaf, often times with what looks like valid IP addresses listed in the describe-instances output. Both the public and private IP addresses would be unavailable. What's odd is that in the case of an intervening vpn session after the vpn session was closed, the ip endpoints to that cloud instance were removed. Even if there were a separate dedicated cc would not one lose connectivity from the client machine? My existing (and previously existing) network was the 192.168.0.xxx served by my wireless router. The segment reserved for the cloud instances public IP address was 192.168.3.0-3.50 or some such limited range. What is avahi and why is it withdrawing the endpoint IPs to the cloud instance? More information...consider this: May 28 18:26:19 cor720 NetworkManager: info Maximum Segment Size (MSS): 0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 10.0.0.0/8 Next Hop: 10.0.0.0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 192.168.251.0/24 Next Hop: 192.168.251.0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 192.168.22.0/24 Next Hop: 192.168.22.0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 192.168.23.0/24 Next Hop: 192.168.23.0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 192.168.24.0/24 Next Hop: 192.168.24.0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 63.131.134.0/24 Next Hop: 63.131.134.0 May 28 18:26:19 cor720 NetworkManager: info Static Route: 208.111.81.157/32 Next Hop: 208.111.81.157 May 28 18:26:19 cor720 NetworkManager: info Static Route: 208.111.81.159/32 Next Hop: 208.111.81.159 May 28 18:26:19 cor720 NetworkManager: info Static Route: 72.20.25.16/32 Next Hop: 72.20.25.16 May 28 18:26:19 cor720 NetworkManager: info Static Route: 209.249.222.54/32 Next Hop: 209.249.222.54 May 28 18:26:19 cor720 NetworkManager: info Internal IP4 DNS: 10.50.33.21 May 28 18:26:19 cor720 NetworkManager: info Internal IP4 DNS: 10.5.4.1 May 28 18:26:19 cor720 NetworkManager: info DNS Domain: 'na.global.ad' May 28 18:26:19 cor720 NetworkManager: info Login Banner: May 28 18:26:19 cor720 NetworkManager: info - May 28 18:26:19 cor720 NetworkManager: info - May 28 18:26:19 cor720 vpnc[3537]: can't open pidfile /var/run/vpnc/pid for writing May 28 18:26:20 cor720 NetworkManager: info VPN connection 'Monster (Maynard)' (IP Config Get) complete. May 28 18:26:20 cor720 NetworkManager: info Policy set 'Monster (Maynard)' (tun0) as default for routing and DNS. May 28 18:26:20 cor720 vmnetBridge: RTM_NEWROUTE: index:5 May 28 18:26:20 cor720 NetworkManager: info VPN plugin state changed: 4 May 28 18:26:20 cor720 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. May 28 18:27:36 cor720 dhcpd: DHCPREQUEST for 172.19.1.2 from d0:0d:30:cf:06:f7 via eth0 May 28 18:27:36 cor720 dhcpd: DHCPACK on 172.19.1.2 to d0:0d:30:cf:06:f7 via eth0 May 28 18:28:26 cor720 vpnc[3537]: select: Interrupted system call May 28 18:28:26 cor720 vpnc[3537]: terminated by signal: 15 May 28 18:28:26 cor720 avahi-daemon[1175]: Withdrawing address record for 172.19.1.1 on eth0. May 28 18:28:26 cor720 avahi-daemon[1175]: Withdrawing address record for 192.168.3.100 on eth0. May 28 18:28:27 cor720 NetworkManager: info Policy set 'Auto eth0' (eth0) as default for routing and DNS. May 28 18:28:27 cor720 vmnetBridge: RTM_NEWROUTE: index:2 There was a, likely, corresponding loss of signal to the open connection to the instance: When I say it I tried to log on again. I tried restarting eucalyptus on the cluster as well as the eucalyptus-cc ubu...@ip-172-19-1-2:~$ Write failed: Broken pipe w...@cor720:~$ ssh -i .euca/mykey.priv ubu...@192.168.3.100 ssh: connect to host 192.168.3.100 port 22: Connection timed out w...@cor720:~$ ssh -i .euca/mykey.priv ubu...@192.168.3.100 ssh: connect to host 192.168.3.100 port 22: Connection timed out w...@cor720:~$ I looked at the tail end of the console log and found this: I also tried rebooting the instance: Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. cloud-init running: Sat, 29 May 2010 01:29:42 +. up 9.06 seconds waiting for metadata service at http://169.254.169.254/2009-04-04/meta-data/instance-id 01:29:44 [ 1/100]: url error [timed out] 01:29:47 [ 2/100]: url error [timed out] 01:29:50 [ 3/100]: url error [timed out] 01:29:51 [ 4/100]: url error [[Errno 113] No route to host] 01:29:54 [ 5/100]: url error [timed out] 01:29:57 [ 6/100]: url error [timed out] 01:30:01 [ 7/100]: url error [timed out] 01:30:05 [ 8/100]: url error [timed out] 01:30:09 [ 9/100]: url error [timed out] 01:30:13
