On 12/27/2013 02:40 PM, Wout Mertens wrote:
> OK… So what is the next step?
[please don't top-post on technical lists]
>
> I just noticed the node
> (http://libvirt.org/formatdomain.html#elementsMetadata), could that be used
> for this? E.g.
>
> http://libvirt.org/vmware/“>[foo]
> bar/b
OK… So what is the next step?
I just noticed the node
(http://libvirt.org/formatdomain.html#elementsMetadata), could that be used for
this? E.g.
http://libvirt.org/vmware/“>[foo]
bar/bar.vmx
Otherwise it seems to me that this would be part of the general section,
perhaps simply a “path
* src/util/virerror.h (virReportInvalidZeroArg): Fix double space.
Signed-off-by: Eric Blake
---
Pushing under the trivial rule.
src/util/virerror.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/util/virerror.h b/src/util/virerror.h
index 05e9950..87272e9 100644
-
On 12/19/2013 09:15 AM, Daniel P. Berrange wrote:
> On Wed, Dec 18, 2013 at 07:19:31PM +0100, Michal Privoznik wrote:
>> Currently, the @flags usage is a bit unclear at first sight to say the
>> least. There's no need for such unclear code especially when we can
>> borrow the working code from qemu
On 12/27/2013 07:25 AM, yue wrote:
> hi,all
> this error occured when live migration windows os, log of that vm is:
>
> features 0x1e unsupported allowed features 0x7102
> qemu warning error while loading state for instance 0x0 of device
> ':00:04.4/virtio-console'
>
> do you have
On 12/26/2013 04:02 PM, Wout Mertens wrote:
> Workarounds I can think of:
> - Augment the domain xml description so it also defines the storage pool on
> which the created domain should reside
This is a good idea which I've wanted for other reasons - the qemu
driver also has instances where we a
Hi,
This is an initial version of the bhyve driver. bhyve is a hypervisor for
FreeBSD: http://bhyve.org/.
I've tried to make this initial version as small as possible but functional,
e.g.
so it could be tested without lots of manual actions outside of libvirt.
Hopefully
it's not large enough fo
At this point it has a limited functionality and is highly
experimental. Supported domain operations are:
* define
* start
* destroy
It's only possible to have only one disk device and only one
network, which should be of type bridge.
---
configure.ac| 37
daemon/libvi
hi,all
this error occured when live migration windows os, log of that vm is:
features 0x1e unsupported allowed features 0x7102
qemu warning error while loading state for instance 0x0 of device
':00:04.4/virtio-console'
do you have some idea about that?
thanks--
libvir-list maili
