Do not worry about transition to running state when starting a container, this is handled from outside

lib/vagrant-lxc/driver.rb

@@ -78,7 +78,7 @@ module Vagrant
         prune_customizations
         write_customizations(customizations + @customizations)
 
-        @cli.transition_to(:running) { |c| c.start(extra) }
+        @cli.start(extra)
       end
 
       def forced_halt
@@ -109,7 +109,7 @@ module Vagrant
           @logger.info "Compressing '#{rootfs_path}' rootfs to #{target_path}"
           @sudo_wrapper.run('rm', '-f', 'rootfs.tar.gz')
           @sudo_wrapper.run('tar', '--numeric-owner', '-czf', target_path, 'rootfs')
-          
+
           @logger.info "Changing rootfs tarball owner"
 
           user_details=Etc.getpwnam(Etc.getlogin)

spec/unit/driver_spec.rb

@@ -80,7 +80,6 @@ describe Vagrant::LXC::Driver do
     subject { described_class.new('name', sudo, cli) }
 
     before do
-      cli.stub(:transition_to).and_yield(cli)
       subject.customizations << internal_customization
       subject.start(customizations)
     end
@@ -92,10 +91,6 @@ describe Vagrant::LXC::Driver do
     it 'starts container with configured customizations' do
       cli.should have_received(:start)
     end
-
-    it 'expects a transition to running state to take place' do
-      cli.should have_received(:transition_to).with(:running)
-    end
   end
 
   describe 'halt' do