On Sat, Oct 18, 2014 at 12:03:23AM +0200, Wouter Verhelst wrote:
Hi all,
(added rjones from nbdkit fame -- hi there)
[I'm happy to implement whatever you come up with, but I've added
Florian Weimer to CC who is part of Red Hat's product security group]
So I think the following would make
The allocator in malloc-pc has been extracted, so it can be used in every arch.
This operation showed that both the alloc and free functions can be also
generic.
Because of this, the QGuestAllocator has been removed from is function to wrap
the alloc and free function, and now just contains the
Hi ALL:
There are two ways to eject the cdrom tray. One is by the eject's qmp
commmand(eject_device).
The another one is by the guest(bdrv_eject). They have different results.
eject_device: close the BlockDriverState(bdrv_close(bs))
bdrv_eject: don't close the BlockDriverState,
This is
I'm pleased to announce libguestfs 1.28, a library and set of tools
for accessing and modifying virtual machine disk images.
This release took 7 months of work by a considerable number of people,
and has many new features (see release notes below), including new
'virt-v2v' and 'virt-p2v' tools
This patch is identical to the previous version, except that I have
rebased it on top of current qemu HEAD.
Previous discussion:
https://lists.gnu.org/archive/html/qemu-devel/2014-10/threads.html#00518
qemu_opt_get_number returns a uint64_t, and curl_easy_setopt expects a
long (not an int).
Store the timeout (which is a positive number of seconds) as a
uint64_t. Check that the number given by the user is reasonable.
Cast it to long before calling curl_easy_setopt.
Example error message after
qemu experts, please help.
This is seen with the latest qemu 1.5 (commit
62c339c5272ce8fbe8ca52695cee8ff40da7872e), guest VM stalls intermittently.
Setup:2) start a linux guest with a PTY device, for example
serial type='pty'
source path='/dev/pts/4'/
target port='0'/
Hello,
please take a look on
http://lists.nongnu.org/archive/html/qemu-devel/2014-09/msg00600.html,
I had reported the simular issue for recent emulator versions. It
would be good if this particular problem can achieve more votes,
because I have not enough knowledge to fix it by myself.
Hi,
while migrating a bunch of VMs i saw multiple times segaults with qemu
2.1.2.
Is this a known bug?
Full backtrace:
Program terminated with signal 11, Segmentation fault.
#0 0x7ff9c73bca90 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0 0x7ff9c73bca90 in ?? () from
From: Ray Strode rstr...@redhat.com
The first two patches are resends from last year that have already
been reviewed and just need to be pulled in.
The third patch is something I ran into a few days ago when trying
to set up kerberos (preauthentication with pkinit) in a guest.
Ray Strode (3):
From: Ray Strode rstr...@redhat.com
commit 57f97834efe0c208ffadc9d2959f3d3d55580e52 cleaned up
the cac_applet_pki_process_apdu function to have a single
exit point. Unfortunately, that commit introduced a bug
where the sign buffer can get free'd and nullified while
it's still being used.
This
From: Ray Strode rstr...@redhat.com
vcard_emul_reset currently only logs NSS out, but there is a TODO
for potentially sending insertion/removal events when powering down
or powering up.
For clarity, this commit moves the current guts of vcard_emul_reset to
a new vcard_emul_logout function which
From: Ray Strode rstr...@redhat.com
When a process in a guest uses an emulated smartcard, libcacard running
on the host passes the PIN from the guest to the PK11_Authenticate NSS
function. The first time PK11_Authenticate is called the passed in PIN
is used to unlock the certificate database.
Hey Vlad,
Sorry about this delay...
I tried the following commands within the guest (that router/firewall
guest-fw-1.domain.com):
root@guest-fw-1:~# ethtool -K eth1 tso off
root@guest-fw-1:~# ethtool -K eth1 gso off
root@guest-fw-1:~# ethtool -K eth1 tx off
But it did not fixed the problem...
We need this to protect dataplane thread from race conditions with block
jobs until the latter is made dataplane-safe.
Signed-off-by: Fam Zheng f...@redhat.com
---
hw/scsi/virtio-scsi-dataplane.c | 4
hw/scsi/virtio-scsi.c | 19 +--
include/hw/virtio/virtio-scsi.h
Hi,
this series fixes loading uImage kernels on MMUv2 xtensa cores.
U-boot for xtensa always treats uImage load address as virtual address.
This is important when booting uImage on xtensa core with MMUv2, because
MMUv2 has fixed non-identity virtual-to-physical mapping after reset.
Changes
U-boot for xtensa always treats uImage load address as virtual address.
This is important when booting uImage on xtensa core with MMUv2, because
MMUv2 has fixed non-identity virtual-to-physical mapping after reset.
Always do virtual-to-physical translation of uImage load address and
load uImage
Oops!
It seems to be working now! :-D
This that I just said:
I tried to disable tso/gso/tx at another guest, of vlan100 net, didn't
worked either.
Isn't true... I created a new guest, side-by-side with guest-fw-1, on
vlan100, and after disabling `tso/gso/tx`, its connectivity becomes
18 matches
Mail list logo
