similar to: virDomainCoreDumpWithFormat files created as root

2015-05-28 12:04 GMT+03:00 Michal Privoznik <mprivozn@redhat.com>: > On 28.05.2015 09:29, NoxDaFox wrote: > > Greetings, > > > > I am dumping a guest VM memory for inspection using the command > > "virDomainCoreDumpWithFormat" and the created files appear to belong to > > root (both user and group). > > > > I have searched around but

Just a hunch but is the binary that creates the dump suid? You may want to check the perms on it. Not sure if it is libvirtd or some other binary. Sent from my iPhone > On May 29, 2015, at 3:39 AM, NoxDaFox <noxdafox@gmail.com> wrote: > > 2015-05-28 12:04 GMT+03:00 Michal Privoznik <mprivozn@redhat.com>: >> On 28.05.2015 09:29, NoxDaFox wrote: >> > Greetings,

On 28.05.2015 09:29, NoxDaFox wrote: > Greetings, > > I am dumping a guest VM memory for inspection using the command > "virDomainCoreDumpWithFormat" and the created files appear to belong to > root (both user and group). > > I have searched around but didn't find any answer. Is there a way to > instruct QEMU to create those files under a different user?

On 08.11.2015 12:43, noxdafox wrote: > I've been spending a bit of time looking into libvirt's code and I > believe this is not implemented as Daniel first said. > > The issue is in the qemuOpenFileAs function in src/qemu/qemu_driver.c > which ignores the dynamic ownership flag and does not set correct > ownership on the file. > > The qemuOpenFileAs function is

Greetings, I am working on a platform for analysis automation. I need to run several Virtual Environments concurrently and record information about their behavior. I wrote some months ago about the capability of reading the Memory during the Environment's execution (in paused state). What do I need is the complete linear memory image, byte per byte, nothing special; I will give this output

https://bugzilla.redhat.com/show_bug.cgi?id=619334 This is a slightly unsatisfactory patch which allows coredumps to be captured when they occur inside the appliance. You can capture coredumps by doing: export LIBGUESTFS_COREDUMP=/sysroot/core.%t.%p.%e or equivalently: g.set_coredump ("/sysroot/core.%t.%p.%e") or variations thereof, see the manual page. When a coredump occurs,

Hello Everyone, I am working on a grad school project for virtual introspection. I have a vm running (with 512mb of memory) and want to access the pmemsave function through virsh with the qemu-monitor-command. I am typing the following: virsh qemu-monitor-command --hmp Shawn 'pmemsave 0 536870912 image.dump' Shawn is the name of my vm and image.dump is the name of my output

OK, got it (my fault, as always, put the LimitCORE in the wrong line). Here is the stack trace: > On 14. Jan 2019, at 10:33, Joan Moreau via dovecot <dovecot at dovecot.org> wrote: > > Difficult to figure out without a coredump + gdb > > > > I have also battled quite a lot to make sure dovecot can core dump on my Archlinux servers. > > I remember that the

Greetings, I have the following typical scenario: given one or more qcow2 base images I clone them with COW and start the VMs. At a certain point I'd like to inspect them in order to see their evolution compared to the known base images. To do so I was thinking about taking a disk snapshot of each VM and inspect its content through libguestfs (using it's Python bindings). Obviously I

Hi, Is there any tool out there that can help me analyze a coredump? Thanks, David. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi Daniel, here are any informations. A little bit strange, coredumpctl showthe libvirtd. coredumpctl dump libvirt and info libvirt  no information. Best regards Holger -------------------------------------------------------------------------- etcsvms5:/var/adm # coredumpctl TIME                            PID   UID   GID SIG PRESENT EXE Tue 2017-11-07 16:22:57 CET     485     0     0  11

Hi, I am getting following 'qemu: could not load kernel' error while trying to create a new VM using virt-install or virt-manager. The software versions are as follows: CentOS 6.2, Libvirt 0.9.4, qemu-kvm 2:0.12.1.2-2.209.el6_2.1. The qemu.conf has disabled dynamic_ownership setting. The VM instantiation has worked fine before when dynamic_ownership was enabled (default). So is this

Here it is: Jan 14 09:26:08 mail dovecot: indexer-worker(paul at iwascoding.com <mailto:paul at iwascoding.com>)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Effective uid=8, gid=8, home=/var/spool/mail/iwascoding/paul Jan 14 09:26:08 mail dovecot: indexer-worker(paul at iwascoding.com <mailto:paul at iwascoding.com>)<16777><IKpfOqBHPFyJQQAADYqDFA>: Debug: Quota

On Mon, 19 Feb 2024 12:21:53 +0100 Simon FONTENEAU via samba <samba at lists.samba.org> wrote: > Hello everyone, > > For the context, I'm trying to add support for offline join in WAPT > WADS OS deployment [1]. Currently WADS supports offline join of > Windows computers, and I want to add support for Linux computer using > SSSD as a authentication client (for the

Thank you. Here is the stack trace with all debug symbols: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: bt.txt URL: <https://dovecot.org/pipermail/dovecot/attachments/20190114/76bcc796/attachment-0001.txt> -------------- next part -------------- > On 14. Jan 2019, at 11:07, Stephan Bosch <stephan at rename-it.nl> wrote:

Hello, I use the virsh change-media command and since the combination of: etcsvms5:/kvm/CS8400/M1 # virsh version Compiled against library: libvirt 3.9.0 Using library: libvirt 3.9.0 Using API: QEMU 3.9.0 Running hypervisor: QEMU 2.10.1 etcsvms5:/kvm/CS8400/M1 # I got the following problem: ---------------------- etcsvms5:/kvm/CS8400/M1 # virsh change-media S5VCS84M1-VLP0 hdc --eject

Hello everyone, For the context, I'm trying to add support for offline join in WAPT WADS OS deployment [1]. Currently WADS supports offline join of Windows computers, and I want to add support for Linux computer using SSSD as a authentication client (for the persons who might dismiss this mail because of a certain keywords, yes it is related to sssd, but it triggers a Samba bug). I also

Hi, I'm playing with dynamic ownership and not all objects have their owners changed. Is dynamic_ownership and its scope documented somewhere, besides the comment in qemu.conf? And what kinds of objects are handled by dynamic ownership? While some objects seem to be handled, other objects are apparently unaffected. For instance /dev/hwrng or a USB host device keep their root owners and are

http://bugzilla.mindrot.org/show_bug.cgi?id=910 fullung at gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fullung at gmail.com ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the