search for: hastexo

hello all, my vm (windows server 2008) keep crashing? 2011-09-21 15:00:45.924: 1355: info : libvirt version: 0.9.6 2011-09-21 15:00:45.924: 1355: error : virSysinfoRead:465 : internal error Failed to find path for dmidecode binary 2011-09-21 15:05:43.873: 1349: warning : qemuDomainObjTaint:1128 : Domain id=1 name='IIS' uuid=a02e41a9-9f4d-d94f-43a6-995b1ca6d37d is tainted:

On Thu, Feb 8, 2018 at 1:07 PM, David Hildenbrand <david@redhat.com> wrote: > We should certainly document what I have summaries here properly at a > central palce! Please review the three edits I've submitted to the wiki: https://www.linux-kvm.org/page/Special:Contributions/Fghaas Feel free to ruthlessly edit/roll back anything that is inaccurate. Thanks! Cheers, Florian

On Fri, Feb 9, 2018 at 11:48 AM, Kashyap Chamarthy <kchamart@redhat.com> wrote: > On Thu, Feb 08, 2018 at 06:44:43PM +0100, Florian Haas wrote: >> On Thu, Feb 8, 2018 at 1:07 PM, David Hildenbrand <david@redhat.com> wrote: >> > We should certainly document what I have summaries here properly at a >> > central palce! >> >> Please review the three

Hello everyone, referring back to https://www.redhat.com/archives/libvirt-users/2013-August/msg00107.html, in which a user discovered that there is no equivalent to "virsh -c lxc:/// lxc-enter-namespace" in the Python API. Has that ever changed? In that thread Daniel suggested that the user file a bug, but that apparently never happened. Why am I interested in this? Ansible currently

Hello everyone, referring back to https://www.redhat.com/archives/libvirt-users/2013-August/msg00107.html, in which a user discovered that there is no equivalent to "virsh -c lxc:/// lxc-enter-namespace" in the Python API. Has that ever changed? In that thread Daniel suggested that the user file a bug, but that apparently never happened. Why am I interested in this? Ansible currently

On Thu, Feb 8, 2018 at 2:47 PM, David Hildenbrand <david@redhat.com> wrote: >> Again, I'm somewhat struggling to understand this vs. live migration — >> but it's entirely possible that I'm sorely lacking in my knowledge of >> kernel and CPU internals. > > (savevm/loadvm is also called "migration to file") > > When we migrate to a file, it

On Wed, Feb 7, 2018 at 11:26 PM, David Hildenbrand <david@redhat.com> wrote: > On 07.02.2018 16:31, Kashyap Chamarthy wrote: >> [Cc: KVM upstream list.] >> >> On Tue, Feb 06, 2018 at 04:11:46PM +0100, Florian Haas wrote: >>> Hi everyone, >>> >>> I hope this is the correct list to discuss this issue; please feel >>> free to redirect me

Hi David, thanks for the added input! I'm taking the liberty to snip a few paragraphs to trim this email down a bit. On Thu, Feb 8, 2018 at 1:07 PM, David Hildenbrand <david@redhat.com> wrote: >> Just to give an example, >> https://www.redhat.com/en/blog/inception-how-usable-are-nested-kvm-guests >> from just last September talks explicitly about how "guests can

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