On 12/20/2010 07:57 AM, Jiri Denemark wrote:
>> Here are the version numbers:
>>
>> virsh # version
>> Compiled against library: libvir 0.6.3
>> Using library: libvir 0.6.3
>> Using API: QEMU 0.6.3
>> Running hypervisor: QEMU 0.9.0
>>
>> Also here are the logs:
>>
>> # cat /var/log/libvirt/qemu/tes
On Mon, Dec 20, 2010 at 02:14:42PM +0100, Jiri Denemark wrote:
> Ouch, I wonder if that could be the reason... Could you just compile libvirt
> yourself?
I still had a box around where I was using a hand-compiled libvirt with
the following version output:
Compiled against library: libvir 0.8.5
U
On 20 Dec 2010, at 12:57, Jiri Denemark wrote:
>> Here are the version numbers:
>>
>> virsh # version
>> Compiled against library: libvir 0.6.3
>> Using library: libvir 0.6.3
>> Using API: QEMU 0.6.3
>> Running hypervisor: QEMU 0.9.0
>>
>> Also here are the logs:
>>
>> # cat /var/log/libvirt/q
> > So could you make sure you have debug info libvirt packages installed
> > or in case you compile libvirt yourself that you compile with -g
> > (should be there by default) and don't strip binaries.
>
> I am using the rpm packages distributed from the website, which I've
> installed on my debia
> Here are the version numbers:
>
> virsh # version
> Compiled against library: libvir 0.6.3
> Using library: libvir 0.6.3
> Using API: QEMU 0.6.3
> Running hypervisor: QEMU 0.9.0
>
> Also here are the logs:
>
> # cat /var/log/libvirt/qemu/test01.log LC_ALL=C
> PATH=/sbin:/usr/sbin:/bin:/usr/bi
On 20 Dec 2010, at 02:09, Osier Yang wrote:
> 于 2010年12月20日 04:48, Anthony Davis 写道:
>> Hi,
>>
>> I wonder if anyone can help me with this, I have been trying to get a vm up
>> and running for a while now and cant for the life of me work out why it isnt
>> working. The errors I get arnt very h
On Mon, Dec 20, 2010 at 10:37:56AM +0100, Jiri Denemark wrote:
> in your first email, you said you can't even run virsh list while migration is
> running, right?
yup -- when i start my migration using my python application, 'virsh
list' no longer works from the command-line. i will try setting up
> I did some MORE testing. I obtain a domain object to a domain in two
> separate python processes. I begin migrating the domain in one of these
> processes, and then I call migrateSetMaxDowntime() on the domain in the
> other process. Unsurprisingly, the call is blocked and does not return
> until
