On 26 Dec 2013, at 07:32, bigclouds wrote:
the paramters received when vmCreate has a long part called custom,
do we use custom infomation? what does the long key
device_* means?
custom properties for devices
see the UI Custom Properties tab in Edit VM
Thanks,
On 26 Dec 2013, at 07:36, bigclouds wrote:
hi,all
please explain what does both agent do when migrate?
what do dest and src do?it use libvirt's migration or create a new vm
throught vmCreate?
src calls vmCreate on dst to prepare storage create a hollow VM
then trigger libvirt
On 26 Dec 2013, at 09:20, bigclouds wrote:
hi,all
there are many channels like spicevmc,unix,vdsm-agent, if that devices impact
live migration?
from following erroe message, i have no idea where is the root cause?
looks like your QEMU process died, might be that there is a problem in
On 27 Dec 2013, at 15:28, bigclouds wrote:
hi,all
this error is after launch libvirt's migration API. but this error is
common.
a windows guest os which has virtio-device will fail to migration.
--log of that vm---
features 0x1e unsupported allowed features 0x7102
On Fri, Jan 03, 2014 at 11:25:04AM +0100, Michal Skrivanek wrote:
On 26 Dec 2013, at 07:32, bigclouds wrote:
the paramters received when vmCreate has a long part called custom,
do we use custom infomation? what does the long key
device_* means?
custom
- Original Message -
From: Dan Kenigsberg dan...@redhat.com
To: Michal Skrivanek michal.skriva...@redhat.com, emes...@redhat.com,
ilvov...@gmail.com
Cc: bigclouds bigclo...@163.com, vdsm-devel@lists.fedorahosted.org
Sent: Friday, January 3, 2014 12:42:54 PM
Subject: Re: [vdsm]
On 03/01/14 12:20 +, Dan Kenigsberg wrote:
Recently, Miguel Angel Ajo (CCed) has added a nice functionality to the
implementation of setupNetworks in Vdsm: two hook points where added:
before and after the setupNetworks verb takes place.
This is useful because sometimes, Vdsm's
