On Tue, Mar 21, 2017 at 11:25:20AM -0400, Ram Krishna wrote:
> lstopo, lstopo --output-format xml
Yes that's interesting, although it's unfortunate that it doesn't
include the CPU model (eg. "Broadwell" etc) in a form which libvirt
can understand. Also the topology is rather difficult to parse.
Gianluca Cecchi writes:
> # running in the guest. For instance, qemu-ga doesn't support guest time
> # synchronization on Windows guests, but Linux ones. By default, this
> # functionality is turned off.
I observed this too but the agent sounded too dangerous to me since
changelog mentioned some
lstopo, lstopo --output-format xml
These commands might be helpful
> On Mar 21, 2017, at 10:35 AM, Richard W.M. Jones wrote:
>
>
> For virt-p2v we want to get the host CPU model, topology etc, and the
> best way we found to do that was to pull it from libvirt
> capabilities[1]. Since libvirt
Thanks for the reply, this is the outputMachine (31GB) Package L#0 + L3 L#0 (15MB) L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0 PU L#0 (P#0) PU L#1 (P#6) L2 L#1 (256KB) + L1d L#1 (32KB) + L1i L#1 (32KB) + Core L#1 PU L#2 (P#1) PU L#3 (P#7) L2 L#2 (256KB)
For virt-p2v we want to get the host CPU model, topology etc, and the
best way we found to do that was to pull it from libvirt
capabilities[1]. Since libvirt is already parsing the host CPU
information, and because /proc/cpuinfo is such a stupid format to
parse, this is very convenient.
Unfortun
(CC devel list - better late than never)
On 03/16/2017 04:23 PM, Daniel P. Berrange wrote:
> On Thu, Mar 16, 2017 at 04:17:51PM +0100, Peter Krempa wrote:
>> On Thu, Mar 16, 2017 at 14:52:47 +, Daniel Berrange wrote:
>>> On Thu, Mar 16, 2017 at 03:50:51PM +0100, Peter Krempa wrote:
On Th
On Tue, Mar 21, 2017 at 1:37 AM, ıuoʎ wrote:
> On Mon, Mar 20, 2017 at 9:58 PM, Timo Juhani Lindfors
> wrote:
> > ıuoʎ writes:
> >> I have a host running a few guests all configured to autostart.
> >> I'm also using libvirt-guests to suspend the guests when the host
> >> restarts or shuts down
On Tue, Mar 21, 2017 at 12:50:39PM +0100, Peter Krempa wrote:
On Tue, Mar 21, 2017 at 12:06:25 +0100, Martin Kletzander wrote:
On Mon, Mar 20, 2017 at 02:11:21PM +0100, Thibaut SAUTEREAU wrote:
> Hello,
>
> I cannot find a way to retrieve PIDs of QEMU instances from libvirt domains'
> IDs (I'm u
On Tue, Mar 21, 2017 at 12:06:25 +0100, Martin Kletzander wrote:
> On Mon, Mar 20, 2017 at 02:11:21PM +0100, Thibaut SAUTEREAU wrote:
> > Hello,
> >
> > I cannot find a way to retrieve PIDs of QEMU instances from libvirt domains'
> > IDs (I'm using libvirt C API). I recognize it sounds like a bad
On Mon, Mar 20, 2017 at 02:11:21PM +0100, Thibaut SAUTEREAU wrote:
Hello,
I cannot find a way to retrieve PIDs of QEMU instances from libvirt domains'
IDs (I'm using libvirt C API). I recognize it sounds like a bad idea doing so
(and I know PIDs are explicitly made not available, as I gathered f
10 matches
Mail list logo