[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [libvirt] qemudDomainSetMemory() / qemudDomainSetVcpus() error codes
- From: Atsushi SAKAI <sakaia jp fujitsu com>
- To: Kaitlin Rupert <kaitlin linux vnet ibm com>
- Cc: libvir-list redhat com
- Subject: Re: [libvirt] qemudDomainSetMemory() / qemudDomainSetVcpus() error codes
- Date: Fri, 06 Jun 2008 10:37:26 +0900
Hi, Kaitlin
I agree your point. and It should use such an error code.
I am looking around the discussion but it is not discussed your point.
https://www.redhat.com/archives/libvir-list/2008-March/msg00160.html
If any policy exists, I also want to know the reason.
Thanks
Atsushi SAKAI
Kaitlin Rupert <kaitlin linux vnet ibm com> wrote:
> Hello,
>
> I noticed qemudDomainSetMemory() / qemudDomainSetVcpus() use the
> VIR_ERR_INTERNAL_ERROR error code when the caller attempts to set the
> mem/vcpus of an active domain.
>
> In this case, returning something like VIR_ERR_NO_SUPPORT would indicate
> that this is an invalid call - which would distinguish the error from a
> failure that occurred during the call.
>
> Is it possible to use such a return code to indicate what is supported
> by QEMU/KVM and what isn't?
>
> Thanks!
> --
> Kaitlin Rupert
> IBM Linux Technology Center
> kaitlin linux vnet ibm com
>
> --
> Libvir-list mailing list
> Libvir-list redhat com
> https://www.redhat.com/mailman/listinfo/libvir-list
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]