Displaying 11 results from an estimated 11 matches for "msg00014".
Did you mean:
msg00011
2011 Mar 15
3
[PATCH 0/3] Various fixes to the Ruby bindings (RHBZ#667610).
https://bugzilla.redhat.com/show_bug.cgi?id=667610
Original message from clalance:
https://www.redhat.com/archives/libguestfs/2011-January/msg00014.html
I believe that these 3 patches fix all of the issues that Chris has
raised.
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, lo...
2017 Jun 23
2
qemu-kvm-ev-2.6.0-28.el7_3.10.1 now available
...0.1
<https://cbs.centos.org/koji/buildinfo?buildID=17495> has been tagged for
release and will soon be available on CentOS mirrors.
This release addresses a security issue (CVE-2017-7718) which has a
security impact rated important.
See https://www.redhat.com/archives/rhsa-announce/2017-June/msg00014.html
for more details on this update.
Here's the Changelog:
* Fri Jun 23 2017 Sandro Bonazzola <sbonazzo at redhat.com> -
ev-2.6.0-28.el7_3.10.1
- Removing RH branding from package name
* Mon May 22 2017 Miroslav Rezanina <mrezanin at redhat.com> -
rhev-2.6.0-28.el7_3.10
- kvm-vi...
2018 Feb 06
2
Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
Hi everyone,
I hope this is the correct list to discuss this issue; please feel
free to redirect me otherwise.
I have a nested virtualization setup that looks as follows:
- Host: Ubuntu 16.04, kernel 4.4.0 (an OpenStack Nova compute node)
- L0 guest: openSUSE Leap 42.3, kernel 4.4.104-39-default
- Nested guest: SLES 12, kernel 3.12.28-4-default
The nested guest is configured with
2019 Jun 14
1
Re: blockcommit of domain not successfull
On Thu, Jun 13, 2019 at 16:01:18 +0200, Lentes, Bernd wrote:
>
> ----- On Jun 13, 2019, at 1:08 PM, Bernd Lentes bernd.lentes@helmholtz-muenchen.de wrote:
>
> I found further information in /var/log/messages for both occurrences:
>
> 2019-06-01T03:05:31.620725+02:00 ha-idg-2 systemd-coredump[14253]: Core Dumping has been disabled for process 30590 (qemu-system-x86).
>
2009 May 22
2
Where are usbhid-ups driver parameters defined - and what do some of them mean?
I am using the usbhid-ups driver with a Belkin UPS.
upsc shows several parameters which I would like to both understand and
probably change. In particular the following part of upsc output:
battery.charge.low: 30
battery.charge.warning: 30
battery.runtime: 120
My questions are:
1) What is the difference between battery.charge.low and
battery.charge.warning? I presume these are %
2018 Feb 08
0
Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
...L0 guest wakes up
>>> from managed save (openstack server resume in OpenStack parlance).
>>> Then, in the L0 guest we immediately see this:
>>
>> [...] # Snip the call trace from Florian. It is here:
>> https://www.redhat.com/archives/libvirt-users/2018-February/msg00014.html
>>
>>> What does fix things, of course, is to switch from the nested guest
>>> from KVM to Qemu — but that also makes things significantly slower.
>>>
>>> So I'm wondering: is there someone reading this who does run nested
>>> KVM and has...
2018 Feb 07
0
Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
...working just beautifully, except when the L0 guest wakes up
> from managed save (openstack server resume in OpenStack parlance).
> Then, in the L0 guest we immediately see this:
[...] # Snip the call trace from Florian. It is here:
https://www.redhat.com/archives/libvirt-users/2018-February/msg00014.html
> What does fix things, of course, is to switch from the nested guest
> from KVM to Qemu — but that also makes things significantly slower.
>
> So I'm wondering: is there someone reading this who does run nested
> KVM and has managed to successfully live-migrate or manage...
2018 Feb 07
5
Re: Nested KVM: L0 guest produces kernel BUG on wakeup from managed save (while a nested VM is running)
...y, except when the L0 guest wakes up
>> from managed save (openstack server resume in OpenStack parlance).
>> Then, in the L0 guest we immediately see this:
>
> [...] # Snip the call trace from Florian. It is here:
> https://www.redhat.com/archives/libvirt-users/2018-February/msg00014.html
>
>> What does fix things, of course, is to switch from the nested guest
>> from KVM to Qemu — but that also makes things significantly slower.
>>
>> So I'm wondering: is there someone reading this who does run nested
>> KVM and has managed to successfull...
2012 Jul 04
1
NOTICE: Data corruption bug when writing to qcow2 files
...2] https://www.redhat.com/archives/libguestfs/2012-July/msg00008.html
[3] https://github.com/libguestfs/libguestfs/blob/cb24ceedd8a8ef7da71cfcce6db10669de47685c/resize/test-virt-resize.sh
[4] https://bugzilla.redhat.com/show_bug.cgi?id=836710
[5] https://www.redhat.com/archives/libguestfs/2012-July/msg00014.html
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
2008 Jun 30
0
FreeBSD 7.0 + Xen 3.1 + HVM: Success!
Kip,
Does the problem with Xen 3.1 in HVM/Intel manifest as those BTX halted
errors (e.g.
http://lists.xensource.com/archives/html/xen-users/2006-10/msg00014.html) ?
If so, do you happen to know whether this problem has been solved in Xen
3.2 or 3.2.1? This message of yours was written this March, so I'm
assuming that 3.2.1 will contain this fix?
Can anybody confirm this? I'm having a hard time finding an RPM for
CentOS 5.2/Xen 3.2.1 right...
2019 Jun 04
9
[PATCH libnbd v2 0/4] api: Implement concurrent writer.
v1:
https://www.redhat.com/archives/libguestfs/2019-June/msg00014.html
I pushed a few bits which are uncontroversial. The main
changes since v1 are:
An extra patch removes the want_to_send / check for nbd_aio_is_ready
in examples/threaded-reads-and-writes.c. This logic was wrong since
commit 6af72b87 as was pointed out by Eric in his review. Comments
and str...