Comment 5 for bug 1197484

Revision history for this message
Para Siva (psivaa) wrote : Re: Connection requests to saucy server VMs from a precise host fail after fresh VM installs

The following were obtained from a VM that had an issue

1. uname -a
Linux utah-11060-saucy-server-i386 3.10.0-2-generic #9-Ubuntu SMP Mon Jul 1 18:36:54 UTC 2013 i686 i686 i686 GNU/Linux

2. sudo aa-status
apparmor module is loaded.
5 profiles are loaded.
5 profiles are in enforce mode.
   /sbin/dhclient
   /usr/lib/NetworkManager/nm-dhcp-client.action
   /usr/lib/connman/scripts/dhclient-script
   /usr/sbin/named
   /usr/sbin/tcpdump
0 profiles are in complain mode.
2 processes have profiles defined.
2 processes are in enforce mode.
   /sbin/dhclient (610)
   /usr/sbin/named (796)
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
------
I am in the process of getting the other information from another VM since the above got destroyed by the automation tool. (When I did "sudo ifdown eth0 && sudo ifup eth0" for me to transfer the required files, the original IP address was restored to the VM and the test ran to completion and the VM got destroyed - Basically the comms between the host and the guest comes back when i do sudo ifdown eth0 and sudo ifup eth0, but not by default after the reboot)