search for: fedora29

Hi there I am using libvirt+lxc on fedora I just upgraded a couple boxes from f29 to f31 i am running into rather puzzling glitches on one of the boxes, and am having a hard time trying to figure what exactly is going wrong symptom being that on the faulty box, my 3 containers startup correctly, but all of them stop after some random time shortly after (approx. in the 5-10 minutes) in some

...k'/> + <target dev='vda' bus='virtio'/> + </disk> + </devices> + </domain> +</node> +EOF + +export VIRTIO_WIN="$d/fake-tools" + +rm -rf $d +mkdir -p $d +mkdir -p $VIRTIO_WIN/linux/fedora{,27,29} +# has: fedora, fedora27, fedora29; should use: fedora29 +$VG virt-v2v --debug-gc -v -x \ + -i libvirt -ic "$libvirt_uri" $guestname \ + -o local -os $d > $d/log 2>&1 +grep '^locating packages in: linux/fedora29, linux/fedora, linux/fc28$' $d/log +grep "^cd 'test-v2v-copy-guest-tools.d/fake...

...use the following kickstart partition scheme for C7 installations >> (via virt-install): >> Briefly, fixed size for /root and /boot, and the rest is filled up for >> /srv. >> >> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work >> with Fedora29 (EL8). I get a "device is too small for new format" error. >> Any hints? >> >> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part >> /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT >> part pv.0104 --fstyp...

Hi all, I still use the following kickstart partition scheme for C7 installations (via virt-install): Briefly, fixed size for /root and /boot, and the rest is filled up for /srv. The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work with Fedora29 (EL8). I get a "device is too small for new format" error. Any hints? part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT part pv.0104 --fstype="lvmpv" --ondisk=sda --grow vol...

First patch just fixes installing guest tools from directory that was broken. Second patch revamps how virt-v2v chooses from which directory install guest tools on Linux. Details in commit message. v2: - included comments from Pino and Rich - added test Tomáš Golembiovský (3): v2v: fix path to source when copying files from guest tools directory v2v: allow alternative directories for

...device. For my current task, I need to perform a "null" migration i.e. migrate the VM to the same host for testing purpose. I am using libvirt 5.1.0 on Fedora 30. >From what I know, libvirt does not allow this type of migration by default. Trying this: virsh migrate --unsafe --verbose fedora29 qemu+unix:///system results in the following error: error: internal error: Attempt to migrate guest to the same host dell Is there some way I can get this to work? If the solution requires changing the source code, then that is also fine. Using qemu-system-x86_64 to perform migration allows same-h...

...option about postgresql is --with-postgresql. This is caused by this line in catalog statement: dbdriver = "dbi:postgresql"; I tried also using "dbi:PostgreSQL" but I got the same issue. I searched online but found only one fedora bugreport with the same problem related to fedora29 but for a different bacula version. Over this I tried to run bacula and all works like expected. How I can fix this warning? Hope in help. Thanks in advance. Alessandro.

Hi, I'm having a problem with significant clock skew on fedora29 with qemu-system-x86-3.0.0 and ibvirt-daemon-kvm-4.7.0. This is on my desktop and appears to happen between suspends of the host each night. It appears like the time just stops while the guest is suspended, of course, but then doesn't update once the guest is resumed. I'm pretty sure time...

...> > I have a Fedora 29 server which serves DHCP and DNS (and DDNS). This > > all works. > > When I installed Samba DC, I specified this DNS server as a > > forwarder. > > Is this dns server also authoritative for the same dns domain as the AD > domain ? Yes, the Fedora29 server is authoritative. > > > > > On the DC server (named dc0) I can enter command, > > > dig other_machine_in_lan > > and get correct response. > > If I enter this command, > > > dig @localhost other_machine_in_lan > > It fails. Dig from do...

...he following kickstart partition scheme for C7 installations > > (via virt-install): > > Briefly, fixed size for /root and /boot, and the rest is filled up for > > /srv. > > > > The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work > > with Fedora29 (EL8). I get a "device is too small for new format" error. > > Any hints? > > > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > > /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT > > part pv.0104 --f...

..., but when the VM resumes from the host sleeping, the clock is off by some seemingly random number of hours. Any ideas greatly appreciated. On Tue, Mar 12, 2019 at 9:17 AM Alex <mysqlstudent at gmail.com> wrote: > > Hi, > > I'm having a problem with significant clock skew on fedora29 with > qemu-system-x86-3.0.0 and ibvirt-daemon-kvm-4.7.0. This is on my > desktop and appears to happen between suspends of the host each night. > It appears like the time just stops while the guest is suspended, of > course, but then doesn't update once the guest is resumed. > &...

...d to perform a "null" migration > i.e. migrate the VM to the same host for testing purpose. > I am using libvirt 5.1.0 on Fedora 30. > > >From what I know, libvirt does not allow this type of > migration by default. > Trying this: > virsh migrate --unsafe --verbose fedora29 qemu+unix:///system > results in the following error: > error: internal error: Attempt to migrate guest to the same host dell > > Is there some way I can get this to work? If the solution > requires changing the source code, then that is > also fine. Using qemu-system-x86_64 to pe...

...esql. > > This is caused by this line in catalog statement: > > dbdriver = "dbi:postgresql"; > > I tried also using "dbi:PostgreSQL" but I got the same issue. > > I searched online but found only one fedora bugreport with the same > problem related to fedora29 but for a different bacula version. > > Over this I tried to run bacula and all works like expected. > > How I can fix this warning? > > Hope in help. > > Thanks in advance. > > Alessandro. > _______________________________________________ > CentOS mailing list &...

..., > > > I still use the following kickstart partition scheme for C7 installations > (via virt-install): > Briefly, fixed size for /root and /boot, and the rest is filled up for > /srv. > > The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work > with Fedora29 (EL8). I get a "device is too small for new format" error. > Any hints? > > part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part > /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT > part pv.0104 --fstype="lvmpv" -...

...tart partition scheme for C7 installations >>> (via virt-install): >>> Briefly, fixed size for /root and /boot, and the rest is filled up for >>> /srv. >>> >>> The same kickstart (despite that c7 uses vda, f29 uses sda) doesn't work >>> with Fedora29 (EL8). I get a "device is too small for new format" error. >>> Any hints? >>> >>> part /RESCUE --fstype="ext4" --ondisk=sda --size=1280 --label=RESCUE part >>> /boot --fstype="ext4" --ondisk=sda --size=512 --label=BOOT >>> p...

Once upon a time, Leon Fauster via CentOS <centos at centos.org> said: > And this only for Fedora29, a C7 installation works fine (dynamically > expands to the boundaries of the disk). You are asking about Fedora - you'd probably get better results on the Fedora mailing lists, forums, etc. -- Chris Adams <linux at cmadams.net>

...erves DHCP and DNS (and DDNS). > > > This all works. > > > When I installed Samba DC, I specified this DNS server as a > > > forwarder. > > > > Is this dns server also authoritative for the same dns domain as > > the AD domain ? > > Yes, the Fedora29 server is authoritative. > > > > > > > > > On the DC server (named dc0) I can enter command, > > > > dig other_machine_in_lan > > > and get correct response. > > > If I enter this command, > > > > dig @localhost other_...

> > > > > > Is this dns server also authoritative for the same dns domain as > > > the AD domain ? > > > > Yes, the Fedora29 server is authoritative. > > > > > > > > > > > Lets start with the smb.conf from the DC, your DC's FQDN and > > > ipaddress (sanitised if you have to) and the same for your Fedora > > > dns server. > > === DC server smb.conf === >...

...--ro -a rhel_guest.qcow2 -m /dev/sda1 -- tar-out / - | \ guestfish --rw -a final_guest.qcow2 -m /dev/rootdg/lv_root -- tar-in - / 3) use "final_guest.qcow2" as the basis for my guests with LVM. After chasing down this issue some more and attempting various things (build the image on Fedora29, build a real XFS filesystem inside a VM and use the generated qcow2 as a basis instead of virt-format).. ..I've noticed that the SATA disk of each of those guests were using 'directsync' (instead of 'Hypervisor Default'). As soon as I switched to 'None', the XFS iss...

...and it will be interesting to see how this is handled in older clients.? We have had years to spread support for ECDSA before it started appearing from servers.? May not for EDDSA. Self-touting, I have an Internet Draft out on using openSSL command line to build an EDDSA pki.? I did the work on Fedora29-beta. I think all the other TLS 1.3 features are in the latest 1.0.n version of openSSL.? Of course that is ALSO a backport issue. I have been told that if you set up your client to only accept TLS 1.3 connections, the Secure Internet gets really small really fast... > >> one of the m...