search for: aptalaska

...t your xml, the host system will have a bigger impact. Maybe you can see this link: Https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html-single/virtualization_tuning_and_optimization_guide/index >Date: Wed, 8 Aug 2018 17:35:11 +0000 >From: Matt Schumacher <matt.s@aptalaska.com> >To: "libvirt-users@redhat.com" <libvirt-users@redhat.com> >Subject: [libvirt-users] Windows Guest I/O performance issues (already > using virtio) >Message-ID: <30EE4896-CF82-4E23-82D5-0C56B38F5E09@aptalaska.com> >Content-Type: text/plain; charset="...

...ay getting back to you, I've been pretty slammed lately. Anyway I have the bracktrace you requested. I simply started libvirtd, started my vm, killed libvirtd, then started it again with gdb in foreground mode with the breakpoint set. I got a ton of debug info that I posted here: http://www.aptalaska.net/~matt.s/libvirt.txt but the backtrace is simply: Breakpoint 1, 0x00007fffc72a0240 in qemuProcessKill () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so (gdb) bt #0 0x00007fffc72a0240 in qemuProcessKill () from /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so #1 0...

On 04/20/2015 05:42 PM, Laine Stump wrote: > Well, this is when the qemu process is killed (I'm pretty clever, eh? :-) > > I have 3 questions: > > 1) what version of libvirt are you running and on what distro? > > 2) can you reproduce this reliably? > > 3) If the answer to 2 is "yes", do you have the libvirt-debuginfo > package installed, and can you

...pretty slammed > lately. Anyway I have the bracktrace you requested. > > I simply started libvirtd, started my vm, killed libvirtd, then started > it again with gdb in foreground mode with the breakpoint set. > > I got a ton of debug info that I posted here: > > http://www.aptalaska.net/~matt.s/libvirt.txt > > but the backtrace is simply: > > Breakpoint 1, 0x00007fffc72a0240 in qemuProcessKill () from > /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so > (gdb) bt > #0 0x00007fffc72a0240 in qemuProcessKill () from > /usr/lib64/libvirt/connecti...

...ttps://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/ Specifically: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Tuning_and_Optimization_Guide/index.html Good luck! Nikki On Tue, Apr 14, 2015 at 9:18 AM, Matt Schumacher <matt.s@aptalaska.com> wrote: > Jatin, > > Using qemu without the virtio scsi and nic drivers is like running vmware > with ide disks and e1000 nic instead of LSI disks and vmxnet3 nics, it > forces the system to emulate completely different hardware. > > In linux the virtio drivers are imp...

Thanks Dominique & Daniel. Looks like i need to upgrade my VMs kernel to make it aware of virtio. Found this information from this link: http://wiki.libvirt.org/page/Virtio#Disk_.28block.29_device_driver I tried without upgrading the Kernel and as soon as i start my VM it got into Kernel Panic. I will try using virtio after upgrading my VMs kernel. Thanks for all the responses and

Hello List, Seems like blockcopy --wait doesn't work work qemu-2.2.x. I found someone else having the same problem, but it never went anywhere: https://www.redhat.com/archives/libvirt-users/2015-January/msg00045.html I went ahead and did some more debugging and created a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1210903 I'm going to do some more debugging and hopefully

> On Friday 10 April 2015 13:07:38 Matthew Schumacher wrote: >> Hello List, >> >> Seems like blockcopy --wait doesn't work work qemu-2.2.x. >> >> I found someone else having the same problem, but it never went anywhere: >> >> https://www.redhat.com/archives/libvirt-users/2015-January/msg00045.html >> >> I went ahead and did some more

I have a small embedded 486 system that is having a very strange problem booting the linux kernel. The system boots fine normally, but if I don't do a proper shutdown on it (everything is in ramdisk anyway) then I can no longer boot the 2.6 kernel. It simply hangs after the "Ready.": SYSLINUX 2.10 2004-06-18 Copyright (C) 1994-2004 H. Peter Anvin boot: Loading

I am getting a bad username or password error when I try to logon to the domain from a windows 2000 server. I can't find anything wrong with my config and I'm using a root user that is in the directory with the uid and gid set to 0. The only thing I see in the logs is something about incorrect password length, but I checked that my passwords are encrypted and I can access shares as

I keep getting this error when trying to do a" net ads join" or "net ads status". I am trying to get samba 3.07 to join win 2003 domain. I have been working at this for quite some time. I just installed fresh box with latest kerberos, openldap and samba on redhat 9 box. Any help/hints would ease my pain. Here is my smb.conf: (which I copied from Samba-3 by Example)

Hello List, I'm trying to get libvirt to work on slackware64-current (slackware64-14.2 beta) and while it compiles just fine, it refuses to run because of an undefined symbol: 2016-03-01 20:09:26.822+0000: 27849: error : virDriverLoadModule:73 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so /usr/lib64/../lib64/libfl.so.2: undefined symbol: yylex

List, Two years ago there was discussion on implementing QEMU's block-dirty-bitmap backup solution: https://www.redhat.com/archives/libvir-list/2016-June/msg00380.html https://www.redhat.com/archives/libvir-list/2016-April/msg00401.html But I haven't seen anything since, and looking through git, it doesn't look like any of these patches were included. Can someone please bring me

Posted to https://bugzilla.redhat.com/show_bug.cgi?id=1217185 I just stumbled on another bug while snapshotting and think it's related to 1210903 and 1197592 as it seems like some sort of race condition because it depends on what logging is in place and doesn't happen every time. Here are the details: I wrote this test script to snapshot and commit over and over: #!/bin/sh while [ 1

Jatin, Using qemu without the virtio scsi and nic drivers is like running vmware with ide disks and e1000 nic instead of LSI disks and vmxnet3 nics, it forces the system to emulate completely different hardware. In linux the virtio drivers are implemented in the kernel, so you either need a new kernel or the virtio kernel modules. I'm not sure which for RHEL5, but I suspect you can get

On 04/28/2015 05:13 PM, Laine Stump wrote: > Bah. Your debug symbols aren't enough to give a full stack trace - what > I was really looking for was those things marked as ??. > > However, your debug output shows several things leading up tothe > qemuProcessStop that might have been the reason for it being called: > > 1) virStorageFileBackendFileReadHeader() complains

Matthew Schumacher wrote: > List, > > I think I found a bug here because I can repeatably get the same kernel > (checked with md5sum) to decompress and to fail with the error: > > invalid compressed format (err=2) > > --System halted > > > Here is how I can reproduce the problem: > > Boot 2.6.8-rc1 > Run md5sum on 2.6.8-rc1 kernel >

List, I purchased 2 g729 licenses but I can't get it to answer a g729 call from a cisco router with a vwic card. In the debug output below you will see that asterisk thinks it only supports: (gsm|ulaw|alaw|h263) when it should support g729 according to the config also listed below. The real odd thing is I can place g729 calls to the router, just not from the router to *. Anyone have any

List, I have a number of Windows 2016 servers I am deploying, but I’m having some I/O performance issues. I have done all of the obvious things like virtio drivers, but am finding there is more performance to be found with hyper-v extensions, how we virtualize the hardware clock, and iothreads. I’m using ZVOLs to back the VM, and I’m using 4k block sizes, which seems to offer the best 4k random

List, I was under the impression that I could restart libvirtd without it destroying my VMs, but am not finding that to be true. When I killall libvirtd then my VM's keep running, but then when I start libvirtd it calls qemuDomainObjEndJob:1542 : Stopping job: modify (async=none vm=0x7fb8cc0d8510 name=test) and my domain gets whacked. Any way to disable this behavior? Also, while I'm