similar to: How does libvirt interaction with KVM to create a VM?

hello, I attached core dump - not sure if it was what you have asked for I am rather just admin not developer :) Regards, Rafal Wojciechowski W dniu 20.04.2017 o 16:44, Pavel Hrdina pisze: > On Thu, Apr 20, 2017 at 07:36:42AM +0200, Rafał Wojciechowski wrote: >> hello, >> >> I am getting such error: >> libvirtd[27218]: segfault at 0 ip 00007f4940725721 sp

From: Carsten Otte <cotte at de.ibm.com> This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's user interface that are unique to s390 architecture. Signed-off-by: Carsten Otte <cotte at de.ibm.com> --- Documentation/s390/kvm.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) Index: kvm/Documentation/s390/kvm.txt

From: Carsten Otte <cotte at de.ibm.com> This patch adds Documentation/s390/kvm.txt, which describes specifics of kvm's user interface that are unique to s390 architecture. Signed-off-by: Carsten Otte <cotte at de.ibm.com> --- Documentation/s390/kvm.txt | 125 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 125 insertions(+) Index: kvm/Documentation/s390/kvm.txt

Hello, In the .xml file I use a media which is no longer available. In the past, I got the information media not available and the creation of the VM was stopped - O.k. behavior. Since 3.10 the libvirtd stopped promptly and all open consoles windows and the virt-manager closed promptly. For diagnose: etcsvms1:/kvm/CS8200/M5 # coredumpctl TIME PID UID GID SIG

Hello, I am trying to use virt-resize. It does not work. I set the debug environment variables and ran libguestfs-test-tool. The following is its output. I am running RHEL 6.5 desktop with kernel: Linux hustedm-lnx4 2.6.32-431.5.1.el6.x86_64 #1 SMP Fri Jan 10 14:46:43 EST 2014 x86_64 x86_64 x86_64 GNU/Linux Please let me know what I have missed. Thanks, Mark bash-4.1$

As people may know, we frequently encounter errors caused by libvirt when running the libguestfs appliance. I wanted to find out exactly how frequently these happen and classify the errors, so I ran the 'virt-df' tool overnight 1700 times. This tool runs several parallel qemu:///session libvirt connections both creating a short-lived appliance guest. Note that I have added Cole's

hi, i am trying to find out the max vcpus supported for any domain by my hypervisor, however i am having some trouble with the below: vcpu=5 maxvcpus=libvirt.virConnect.getMaxVcpus(conn,'kqemu') if maxvcpus <= vcpu: logging.debug('checkmaxvcpus: max vcpus on hypervisor %i is less than requested vcpu of %i' % (maxvcpus, vcpu)) return 0 else: return 1

2015-03-02 23:41 GMT+03:00 Brian Rak <brak@gameservers.com>: > In IRC, I was directed to this patch: > https://www.redhat.com/archives/libvir-list/2015-February/msg01212.html ... > which does exactly what I was looking for. It doesn't build cleanly in that > state, but it's pretty trivial fix (needs actualType added to the function > definition for

Hi list, According to the libvirt documentation [1] "Show maximum number of virtual CPUs for guest domains on this connection" This may not be a complete definition. My first guess from the above was that this returns the number of virtual CPUs that can exist at the same time on the host, either one or several VMs. In fact it returned 16 in my fedora 20 desktop running with KVM,

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

Hi, I have set maxvcpus and vcpus options in my domU configuration file, and I can see that X number of vcpu are set for the domU. I tried to activate all the vpcus by using vpcu_avail option (using decimal to represent vpcu bitmask e.g. 24=11000) but it doesn''t seem to work, and only the first vpcu is activated (i.e. has -b- state) while all other vpcu''s set for the domU are

On Sun, Jul 12, 2020 at 10:49:21PM +0800, Zhu Lingshan wrote: > We used to detect assigned device via VFIO manipulated device > conters. This is less flexible consider VFIO is not the only > interface for assigned device. vDPA devices has dedicated > backed hardware as well. So this patch tries to detect > the assigned device via irqbypass manager. > > We will

On Sun, Jul 12, 2020 at 10:49:21PM +0800, Zhu Lingshan wrote: > We used to detect assigned device via VFIO manipulated device > conters. This is less flexible consider VFIO is not the only > interface for assigned device. vDPA devices has dedicated > backed hardware as well. So this patch tries to detect > the assigned device via irqbypass manager. > > We will

Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by: Alexander Graf <agraf at suse.de> --- drivers/s390/kvm/kvm_virtio.c | 22 ++++++++++++++++------ 1 files changed, 16 insertions(+), 6

Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by: Alexander Graf <agraf at suse.de> --- drivers/s390/kvm/kvm_virtio.c | 22 ++++++++++++++++------ 1 files changed, 16 insertions(+), 6

On Thu, Apr 20, 2017 at 06:10:04PM +0200, Rafał Wojciechowski wrote: > hello, > > I attached core dump - not sure if it was what you have asked for > I am rather just admin not developer :) > > Regards, > > Rafal Wojciechowski The attached core send in private mail helped to figure out where the crash happened. Backtrace: Thread 1 (Thread 0x7f194b99d700 (LWP 5631)):

Hey Ian and Stefano, Please see this thread: http://lists.xen.org/archives/html/xen-devel/2013-05/msg01053.html for the debug patches and some of the discussion. These three patches fix an race that has been in QEMU traditional for a long time. The guts of the bug is that if you have a guest with these options: vcpus=1 maxvcpus=32 and do ''xl vcpu-set <guest> 32'' the

Hello Rich, Well, I did give that a try. But it is back to being unable to access kvm (log attached). It did make the qemu error go away. Thanks, Mark Thanks, Mark Husted 770-236-1242 -----Original Message----- From: Richard W.M. Jones [mailto:rjones@redhat.com] Sent: Friday, August 22, 2014 8:31 AM To: Mark Husted (hustedm) Cc: libguestfs@redhat.com Subject: Re: [Libguestfs]

Using virsh edit, I made the following change to the domain XML file: <on_reboot>destroy</on_reboot> But this appears to do nothing. The VM guest is Windows 10, and when directing it to reboot, it still reboots, instead of shutting off the VM. I was trying to work around some kind of a bug, somewhere, that started happening after updating to Fedora 26 and qemu 2.9, where a

Thanks for all the replies. Looking at the specs for the processor it does not seem to have the vmx features in /proc/cpuinfo: http://www.notebookcheck.net/Intel-Core-2-Duo-T6400-Notebook-Processor.35100.0.html and the output from grep -E ?vmx|svm? /proc/cpuinfo is empty. /lib/modules/3.10.0-229.7.2.el7.x86_64/kernel/arch/x86/kvm [keith.roberts at acer-centos kvm]$ ls kvm-amd.ko kvm-intel.ko