[virt-tools-list] installing from iso image problem

[Cole Robinson]

On 02/07/2012 10:26 AM, Gergely Buday wrote:
>> Hmm, okay, so when you start virt-manager, MobileOtp3 isn't listed? Is that
>> also the name you were using for a new VM that threw the 'name already in use'
>> error?
>>
>> What's the output of virt-manager --debug when reproducing the reported issue?
> 
> Now MobileOtp3 was listed. I tried to run the VM and then got
> 
> Error starting domain: 'NoneType' object has no attribute 'info'
> 
> Traceback (most recent call last):
>   File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in cb_wrapper
>     callback(asyncjob, *args, **kwargs)
>   File "/usr/share/virt-manager/virtManager/engine.py", line 959, in asyncfunc
>     vm.startup()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 1129, in startup
>     self._update_status()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 1355, in
> _update_status
>     info = self.get_info()
>   File "/usr/share/virt-manager/virtManager/domain.py", line 1024, in get_info
>     return self._backend.info()
> AttributeError: 'NoneType' object has no attribute 'info'
> 
> virt-manager said
> 
> $ virt-manager --debug
> 2012-02-07 16:21:15,246 (virt-manager:175): Application startup
> 2012-02-07 16:21:15,273 (virt-manager:363): Launched as:
> /usr/share/virt-manager/virt-manager.py --debug
> 2012-02-07 16:21:15,274 (virt-manager:364): GTK version: (2, 24, 7)
> 2012-02-07 16:21:18,325 (engine:338): About to connect to uris ['xen:///']
> 2012-02-07 16:21:18,380 (virt-manager:436): Connected to already
> running instance.
> 

You'll need to fully shutdown all virt-manager instances before you can get
full debug output. That message 'connected to already running instance'
indicates you've got another instance kicking around.

So try fully shutting down all instances, run virt-manager --debug, try to
open the VM, or if it doesn't appear try and create a new VM with the same
name, then post the entire debug output.

At the end of the day though I'm guessing this isn't virt-manager specific,
it's probably the result of xen/libvirt weirdness on f15. I think the dom0
kernel was only fully merged into f16, so are you getting dom0 for f15 from a
different repo? Basically after fedora + xen + libvirt + virt-manager not
having a lot of testing together for many many fedora releases, things are
only now starting to back in shape, but f15 likely still has a bunch of issues.

Thanks,
Cole