similar to: My Issue

Hi folks I use libvirt to programmatically spawn lxc containers I am facing an issue when migrating from fedora23 to fedora24 I use the stock kernel and libvirt version on both deployments, i.e.: f23: libvirt-1.2.18.3-2.fc23.x86_64 - kernel 4.5.7-202.fc23.x86_64 f24: libvirt-1.3.3.1-4.fc24.x86_64 - kernel 4.6.3-300.fc24.x86_64 First off, I need to outline that the host installation is done

I don't know if anything will help or not. It has 2 different NVidia cards running 2 DVI, 1 HDMI, 1 VGA, and 1 unused HDMI. It works on FC22 from the install disk on. Breaks on abi going to fc23. Here are the log files. The system was in such a state, that a do not want to go back there again. I reported this a while back but did not gather anything because I was in need of getting back

I think I've hit the same problem that Predrag reported in http://comments.gmane.org/gmane.comp.emulators.libvirt.user/8825. With libvirt-1.3.2-1.fc23.x86_64 on Fedora 23, when I try uploading an image with vol-upload to a user libvirtd (qemu:///session): virsh vol-upload --pool default volume.qcow /path/to/file.qcow2 I am getting: error: Disconnected from qemu:///session due to

Hi everyone! It's the first time I send a message to this list, I hope it's not the last :) So my issue is that when booting a disk image generated with virt-builder [1] it takes more than 5 minutes, waiting in the boot screen that says: " Booting from disk... press any key to continue. " The press any key message shows up to 5 times. The issue is that it stays in that screen

hasm> Every few minutes windbindd posts an error message like: hasm> winbindd: ../source3/libads/ldap.c:552(ads_find_dc) hasm> winbindd: ads_find_dc: name resolution for realm 'XXX.CO' hasm> (domain 'XXX_01') failed: NT_STATUS_NO_LOGON_SERVERS hasm> How can I shut this thing up? I've also seen, not sure hasm> whether related, winbindd shooting up to

On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: > > It actuallly looks from Adam's investigation that this isn't different > for this package. So, less than certainly. It looks like maybe more a > gcc 5 difference. > > > Regardless of whatever is actually causing this, here is the isolinux-debug.bin output: Booting from DVD/CD... ISOLINUX 6.03

Thanks. This is making a lot more sense now and it's looking like this issue isn't Mips specific. Here's the IR dump before simple register coalescing (note: I've patched the IR printer to print the contents of the regmask): 4480B %vreg260<def> = LDC1 %vreg253, <cp#3>[TF=6]; mem:LD8[ConstantPool] AFGR64:%vreg260 GPR32:%vreg253 4496B %vreg261<def> = FMUL_D32

Hi, I know that there was a jitter buffer patch (for sip) for the 1.0.9 branch some time agin. At this time, we can not upgrade to 1.4.x. Is there a useable, fairly stable INCOMING sip jitter buffer patch? That is.. I want Asterisk to jitter buffer incoming SIP packets. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello, I have first a question (and then may be a problem), that I have difficulties to understand and eventually to investigate. On each of my guests VM, I see constantly a RX dropped number increasing , Even if the VM does nothing ! ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.100.15 netmask 255.255.255.0 broadcast 192.168.100.255

Hey there everyone! Trying to use virt-builder to download & resize the standard fedora-23 image from libguestfs.org ... ??[rsawhill at jiop 11:50 ~] {0} $ rpm -q libguestfs-tools > libguestfs-tools-1.32.7-1.fc23.noarch > ??[rsawhill at jiop 11:50 ~] {0} $ virt-builder --list | grep fedora-23 > fedora-23 x86_64 Fedora? 23 Server > fedora-23 i686

On Fri, Mar 04, 2016 at 04:57:30PM +0000, Daniel P. Berrange wrote: > What version of libvirt ? We had an unfortunate implementation mistake > which caused us to waste tonnes of time in memmove(). versions since > 1.2.19 have a fix that addresses it Ah, this is on F23, which has: libvirt-1.2.18.2-2.fc23.x86_64 There's nothing more recent right now in either updates or

Hello I have error virt-v2v: error: unable to rebuild initrd (/boot/initramfs-4.2.3-300.fc23.x86_64.img) because mkinitrd or dracut was not found in the guest My physical machine run on fedora23 Boot on usb made from virt-p2v-livecd-1.32.0.fc23.iso <http://oirase.annexia.org/virt-p2v/virt-p2v-livecd-1.32.0.fc23.iso> Log joined to this mail Do you have this problem ?

On 23.06.2015 01:27, Adam Williamson wrote: > On Mon, 2015-06-22 at 14:57 -0700, Adam Williamson wrote: >> On Mon, 2015-06-22 at 22:12 +0200, poma wrote: >>> https://kojipkgs.fedoraproject.org/mash/rawhide/x86_64/os/images/ >>> boot.iso >>> >>> https://kojipkgs.fedoraproject.org/work/tasks/6196/10176196/ >>>

On 30.06.2015 04:27, Gene Cumm wrote: > On Mon, Jun 29, 2015 at 6:20 PM, poma via Syslinux <syslinux at zytor.com> wrote: >> On 29.06.2015 17:06, Matthew Miller via Syslinux wrote: >> >>> >>> It actuallly looks from Adam's investigation that this isn't different >>> for this package. So, less than certainly. It looks like maybe more a

> grep("f[0-9]+=", "f1=5,f22=3,", value = T) [1] "f1=5,f22=3," How do I make the line output c("f1", "f22") instead? (Actually, c(1,22) would be even better). Thank you. -- View this message in context: http://r.789695.n4.nabble.com/Quick-GREP-challenge-tp2339486p2339486.html Sent from the R help mailing list archive at Nabble.com.

Hi, all: Two examples are shown below. I want to use the multiple comparison of Dunnett. It succeeded in upper case "example 1". However, the lower case "example 2" went wrong. In "example 2", the function pmvt return NaN, so I cannot show this simtest result. Is there any solution? (I changed the variable "maxpts" to a large number in front of the

To reduce memory consumption clobbered registers are handled with RegisterMask machine operands which contain a bitset of all registers clobbered. - Matthias > On Jul 29, 2015, at 3:00 PM, Daniel Sanders <daniel.sanders at imgtec.com> wrote: > > I believe I've identified the problem with almabench but I haven't found the root cause in the compiler yet. > > The

https://bugs.freedesktop.org/show_bug.cgi?id=92922 Bug ID: 92922 Summary: Xorg random freeze Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau at

I have a quad display set up. It is working perfectly under FC22, but bombs on FC23. I wish I had more information for you, but I had to get this machine back up and running. Not only does the quad head not work, the one working head was operating at 1280x1024 versus 1920x1080. I tried doing a fresh install of FC23 and an upgrade from FC22 to FC23. It did not work in either situation. So, I

Hello, I use fedora-virt-preview repo and it recently updated to qemu-2.6.0-0.1.rc1.fc23.x86_64 and libvirt-1.3.3-1.fc23.x86_64. Now my arm VM does not start: Error starting domain: internal error: process exited while connecting to monitor: qemu-system-arm: -device pci-bridge,chassis_nr=2,id=pci,bus=pci,addr=0x1: Duplicate ID 'pci' for device I uploaded VM xml file to