.controller->model =
> VIR_DOMAIN_CONTROLLER_MODEL_SCSI_VIRTIO_SCSI;
> +
I think it's good to make this the default on s390. So, FWIW
Reviewed-by: Jens Freimann
--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
es kvm 85 identify as QEMU? If so Daniel's patch to enable migration
> for QEMU >= 0.10 might help
--
jens
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
You are right, my irc client tricks me.
On 05/05/09 Daniel P. Berrange wrote:
> Sounds like you're probably on the wrong IRC network. #virt is on
> irc.oftc.net, and is fully open to anyone who wishes to join
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listin
Hello,
on http://libvirt.org/contact.html I read about the #virt irc channel.
How can I participate in this channel, it seems to be locked because I
have to specify a channel key.
Greetings
Jens
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir
In my case kvm is just a link to qemu-system-x86_64.
Please let me ask another question: do you know if the mentioned patch
is already integrated in the cvs repository tree?
Thank you very much
Jens
On 05/03/09 Guido Günther wrote:
> Does kvm 85 identify as QEMU? If so Daniel's patch t
kernel 2.6.29.1 and kvm-85 with libvirt 0.6.2 on an debian
unstable system.
Attached are debug logs generated by the source- and destination-machine.
Thank you very much
Jens
18:57:19.599: debug : virEventAddHandleImpl:111 : Add handle 3 1 0x80557d0 0x80a4470
18:57:19.599: debug : virEv
