search for: fedora23

I have an automatic process setup. It's still pretty new and obviously in need of better error handling because now I find myself in a bad state. I run snapshot-create-as across all my vms, then do zfs replication to the target backup system, then blockcommit everything. virsh snapshot-create-as --domain $vm snap --diskspec $DISK,file=$VMPREFIX/"$vm"-snap.qcow2 --disk-only --atomic

...f libvirt still knows about the overlay > image (this is necessary only so that it can say the proper things to > qemu) you can re-do the block commit: > > $ virsh list > Id Name State > ---------------------------------------------------- > 3 fedora23 running > > $ virsh snapshot-create-as --disk-only --no-metadata fedora23 > Domain snapshot 1498817916 created > $ virsh domblklist fedora23 > Target Source > ------------------------------------------------ > vda /var/lib/libvirt/images/fedora2...

...30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: [...] > file or directory > > $ virsh blockcommit --active --pivot fedora23 vda > > > > Successfully pivoted > > $ virsh domblklist fedora23 > > Target Source > > ------------------------------------------------ > > vda /var/lib/libvirt/images/fedora23.qcow2 > > hda - > > > > Thanks for the reply! The...

...30, 2017 6:22 AM, "Peter Krempa" <pkrempa@redhat.com> wrote: > > On Fri, Jun 30, 2017 at 12:05:47 +0200, Peter Krempa wrote: > > > On Thu, Jun 22, 2017 at 11:02:41 -0400, Doug Hughes wrote: [...] > file or directory > > $ virsh blockcommit --active --pivot fedora23 vda > > > > Successfully pivoted > > $ virsh domblklist fedora23 > > Target Source > > ------------------------------------------------ > > vda /var/lib/libvirt/images/fedora23.qcow2 > > hda - > > > > Thanks for the reply! The...

...ers. > > Fedora is the place to try out bonkers stuff. If RedHat is satisfied > with dnf then they will include it and not yum in RHELN. Maybe they > will make yum an alias to dnf, who knows. But whatever they do it's > much less likely to be bonkers. > <snip> Under Fedora23 issuing a yum command gets you a warning, then it automatically runs the appropriate dnf command. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: <http://lists....

Hi, I wonder if someone can provide pointers on what might be wrong with my setup. I'm running a kvm host Fedora23 with rawhide kernel on top of a skylake cpu - Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz (family: 0x6, model: 0x4e, stepping: 0x3) As part of an experiment, I have enabled Nested virt support on the host and created a fedora23 guest with virt-manager using host-passthrough as the cpu model. The gues...

...create a pty device each time I want to spin up a vm (if there's a way to tell libvirt to do that for me that would be ok too). Is there any workaround I can do to avoid having to create a pty and still get fast boot? The xml of the slow vm: <domain type='kvm'> <name>fedora23</name> <memory unit='MiB'>2048</memory> <vcpu>1</vcpu> <cpu mode='host-passthrough'> <topology sockets='1' cores='1' threads='1'/> </cpu> <os> <type arch='x86_64'...

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 ?

I have been trying to run Centos 6 and 7 in virtualbox on this Fedora23 computer. Actually I also tried Scientific Linux and a DVD copy of Fedora 21 XFCE Live that I had on hand. The Fedora21 works as expected but I seem to be missing something in Centos and Scientific Linux. They boot and run with a text screen but startx reports "command not found"...

On Fri, 9 Sep 2016, Always Learning wrote: > > On Thu, 2016-09-08 at 23:22 +0100, J Martin Rushton wrote: > >> Under Fedora23 issuing a yum command gets you a warning, then it >> automatically runs the appropriate dnf command. > > Can you tell us the DNF for:- > > yum update > yum groupinstall > yum reinstall > yum erase DNF isn't used on CentOS. Stop. If you want to learn about thing...

...e I guess. >I don't want to have to create a pty device each time I want to spin up a vm >(if there's a way to tell libvirt to do that for me that would be ok too). > You could use virt-xml from the virt-tools (installed as part of virt-manager, I believe) to do that: virt-xml fedora23 --add-device --serial pty >Is there any workaround I can do to avoid having to create a pty and still get >fast boot? > > >The xml of the slow vm: > ><domain type='kvm'> > <name>fedora23</name> > <memory unit='MiB'>2048</m...

...-format qcow2 --firstboot-command 'dpkg-reconfigure openssh-server' --arch x86_64 And imported it to libvirt with # virt-install --import --name ubuntu-xenial --ram 2048 --disk path=/var/lib/libvirt/images/ubuntu-16.04.qcow2,format=qcow2 --os-variant fedora23 --graphics none These successfully create the Ubuntu guest and import it as well. But - when I tried to access it using 'virsh console', it connects and shows a blank screen. No interaction whatsoever. - When I tried to access it via ssh, it did not accept the root passw...

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 through some ad ho...

Dear testers, My list of blockers is empty, and there were no new problems discovered with rc3, so I have gone ahead and tagged 3.8.0-final [1]. Please build the final binaries and upload to the sftp. For others following along: yes, this means 3.8.0 is complete, but it takes a couple of days to get the source and binary tarballs built. I will send the release announcement when everything's

On Thu, 2016-09-08 at 23:22 +0100, J Martin Rushton wrote: > Under Fedora23 issuing a yum command gets you a warning, then it > automatically runs the appropriate dnf command. Can you tell us the DNF for:- yum update yum groupinstall yum reinstall yum erase ? Thanks, -- Regards, Paul. England, EU. England's place is in the European Union.

On Fri, Sep 09, 2016 at 09:28:09AM +0100, John Hodrien wrote: > On Fri, 9 Sep 2016, Always Learning wrote: > > > > > On Thu, 2016-09-08 at 23:22 +0100, J Martin Rushton wrote: > > > > > Under Fedora23 issuing a yum command gets you a warning, then it > > > automatically runs the appropriate dnf command. > > > > Can you tell us the DNF for:- > > > > yum update > > yum groupinstall > > yum reinstall > > yum erase > > DNF isn't use...

...oot-command 'dpkg-reconfigure openssh-server' > --arch x86_64 > > And imported it to libvirt with > > # virt-install --import --name ubuntu-xenial --ram 2048 > --disk path=/var/lib/libvirt/images/ubuntu-16.04.qcow2,format=qcow2 > --os-variant fedora23 > --graphics none > > These successfully create the Ubuntu guest and import it as well. But > > - when I tried to access it using 'virsh console', it connects and shows a > blank screen. No interaction whatsoever. Yes, this is a bug. > - When I tried to...

On Wed, 2016-09-07 at 23:40 +0000, Joseph L. Casale wrote: > > I think it should be called YUM. > https://fedoraproject.org/wiki/Features/DNF#Naming > DNF stands for Dandified yum. Since DNF is a tech preview > in Fedora 18 the Python module names can not be 'yum.*' as > that would clash with yum itself. In any single version of Centos there is only one YUM. Having

...?? Originally script used mkisofs, but run into issues with it not excepting the efi modification, so switched to switched using genisoimage option. Build works, and it runs with EFI off, but fails when trying it, so something must be wrong? Tried using EFI/BOOT directory, since that is what the Fedora23 CD seems to have, and copied the syslinux.efi file from the efi32 directory. Also, placed alls the efi32 version of the modules in the directory. The was no ldlinux.c32, but was a ldlinux.e32?? Here is the testing script to build the boot.iso #!/bin/sh # # # USAGE: ./makecd DEVICE [blank] # ex...

...--git a/builder/templates/fedora-23-aarch64.index-fragment b/builder/templates/fedora-23-aarch64.index-fragment new file mode 100644 index 0000000..72fb635 --- /dev/null +++ b/builder/templates/fedora-23-aarch64.index-fragment @@ -0,0 +1,25 @@ +[fedora-23] +name=Fedora® 23 Server (aarch64) +osinfo=fedora23 +arch=aarch64 +file=fedora-23-aarch64.xz +checksum=aa1359b2a81841ac07e4e25bef9d3ef3b7cf10c171403505cbbd732644fe6c37938cf6c9e3251dae201b659b47033fb792cb29f587fd4d4816b6c0d100dc5be8 +format=raw +size=6442450944 +compressed_size=216417776 +expand=/dev/sda4 +notes=Fedora 23 Server (aarch64) + + This F...