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 configuration
Hello everybody,
2014/1/3 Dan Kenigsberg
> 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.
>
Dan, thank you for starting this thread,
>
> [..
On Fri, Jan 03, 2014 at 07:55:02AM -0500, Martin Perina wrote:
>
>
> - Original Message -
> > From: "Eli Mesika"
> > To: "Dan Kenigsberg"
> > Cc: "Michal Skrivanek" , ilvov...@gmail.com,
> > "bigclouds" ,
> > vdsm-devel@lists.fedorahosted.org, "Martin Perina"
> > Sent: Friday, January
- Original Message -
> From: "Eli Mesika"
> To: "Dan Kenigsberg"
> Cc: "Michal Skrivanek" , ilvov...@gmail.com,
> "bigclouds" ,
> vdsm-devel@lists.fedorahosted.org, "Martin Perina"
> Sent: Friday, January 3, 2014 1:30:14 PM
> Subject: Re: [vdsm] what does custom option mean when vmcre
- Original Message -
> From: "Dan Kenigsberg"
> To: "Michal Skrivanek" , emes...@redhat.com,
> ilvov...@gmail.com
> Cc: "bigclouds" , vdsm-devel@lists.fedorahosted.org
> Sent: Friday, January 3, 2014 12:42:54 PM
> Subject: Re: [vdsm] what does custom option mean when vmcreate ?
>
> On
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 configuration is not good
enough for the user. For example, so
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?
>
> cus
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 0x71
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 cr
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 m
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,
mi
11 matches
Mail list logo