loon0,bus=pci.0,addr=0x5 -msg timestamp=on
Regards
Tanmoy Sinha
kvm-core-net
...
.....
Regards
Tanmoy Sinha
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
Correct no libvirt involved as such, will post this on qemu mailing list.
Regards
Tanmoy Sinha
On Thu, Jun 27, 2019 at 5:09 PM Peter Krempa wrote:
> On Thu, Jun 27, 2019 at 16:22:27 +0530, Tanmoy Sinha wrote:
> > Hi All,
> >
> > I am unable to figure out the issue here, w
bian 4.9.168-1+deb9u2 (2019-05-13)
x86_64 GNU/Linux
Regards
Tanmoy Sinha
___
libvirt-users mailing list
libvirt-users@redhat.com
https://www.redhat.com/mailman/listinfo/libvirt-users
approach will not cause any issue.
On Mon, 26 Nov 2018 at 5:23 PM, Peter Krempa wrote:
> On Fri, Nov 23, 2018 at 20:08:13 +0530, Tanmoy Sinha wrote:
> > Hi,
> >
> > I would like to get a clear picture on external snapshots memory dump (
> > i.e. system-checkpoint) vs dump
Hi,
I would like to get a clear picture on external snapshots memory dump (
i.e. system-checkpoint) vs dumping the memory of the guest. I have created
external snapshots which produces a disk file and a memory file. I am not
able to use this memory file in any memory analysis tools, for instance
v
ow what was the last reason (i..e
the default value 0 or UNKNOWN), but the state remains as shutfoff!
Is there a patch for it? Or someway to retain the reason code across
reboots and restart?
Regards,
Tanmoy Sinha
___
libvirt-users mailing list
libvirt-us