Ok. so I will then shift to using system tap, Are the timestamps
generated for events compatible with the ftrace timestamps? so that I
can still merge the traces using TSC_OFFSET.
Thanks,
On Tue, Aug 16, 2016 at 8:05 PM, Daniel P. Berrange wrote:
> On Tue, Aug 16, 2016 at
2016-08-16 21:21, Nerijus Baliūnas rašė:
I've tried gdb without daemonize on a working PC and got the same
backtrace. So it seems it is daemonize code which has a problem.
Debugging the child revealed the problem:
# gdb /usr/bin/qemu-system-alpha
(gdb) set follow-fork-mode child
(gdb) r -S
On 16 August 2016 at 18:41, Nerijus Baliūnas
wrote:
> 2016-08-16 20:26, Peter Maydell rašė:
>>>
>>> Yes, it still hangs:
>>>
>>> # gdb /usr/bin/qemu-system-alpha
>>> (gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp
>>>
2016-08-16 20:26, Peter Maydell rašė:
Yes, it still hangs:
# gdb /usr/bin/qemu-system-alpha
(gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp
unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait -pidfile
/var/lib/libvirt/qemu/capabilities.pidfile
Starting program:
Hello,
I am running QEMU 2.5 on Ubuntu 16.04. My guests are a mixture of Linux (Ubuntu
12.04 and newer with ext4) and Windows. The guest qcow2 images are stored in a
ZFS filesystem with sync=standard (on top of a mirrored vdev of SSDs) on the
host
Ubuntu 16.04 OS. After having read through
On 16 August 2016 at 17:50, Nerijus Baliūnas
wrote:
> I tried to debug with gdb:
>
> # gdb /usr/bin/qemu-system-alpha
> Reading symbols from /usr/bin/qemu-system-alpha...Reading symbols from
> /usr/lib/debug/usr/bin/qemu-system-alpha.debug...done.
> done.
> (gdb) r
I tried to debug with gdb:
# gdb /usr/bin/qemu-system-alpha
Reading symbols from /usr/bin/qemu-system-alpha...Reading symbols from
/usr/lib/debug/usr/bin/qemu-system-alpha.debug...done.
done.
(gdb) r -S -no-user-config -nodefaults -nographic -M none -qmp
On Tue, Aug 16, 2016 at 07:54:50PM +0530, Gadre Nayan wrote:
> Hi,
>
> I have setup the merging of traces from Guest QEMU and Host using the
> TSC_OFFSET. So I would like to work with ftrace backend of QEMU. So
> how can I add this option in libvirt tools to enable ftrace backends
> with my
On Tue, Aug 16, 2016 at 05:48:37AM -0400, Han Han wrote:
> Hi all,
> I created a luks image via qemu-img and tried to open it via cryptsetup but
> failed.
> I did following steps:
> # qemu-img create -f luks --object
> secret,id=sec0,data=c3RhdGUxMjMK,format=base64 -o key-secret=sec0 /tmp/qemu
On Tue, Aug 16, 2016 at 10:08:09AM +0530, Gadre Nayan wrote:
> I was trying to understand the flow of packets from the Guest OS to my
> NIC card, while using the Virtio paravirtualized drivers. (Qemu is not
> emulating the NIC)
QEMU always emulates paravirtualized NICs to some extent. Why do you
Hi all,
I created a luks image via qemu-img and tried to open it via cryptsetup but
failed.
I did following steps:
# qemu-img create -f luks --object
secret,id=sec0,data=c3RhdGUxMjMK,format=base64 -o key-secret=sec0 /tmp/qemu
500M
Hello,
qemu 2.7.0-0.1.rc2.fc24, but the same happened with 2.6.0.
I start systemctl start libvirtd, and systemctl status libvirtd
shows:
Active: active (running) since Pr 2016-08-15 22:41:43 EEST; 30s ago
CGroup: /system.slice/libvirtd.service
├─2907 /usr/sbin/libvirtd
12 matches
Mail list logo