search for: fedora27

...twork.remote-dio: enable performance.low-prio-threads: 32 performance.io-cache: off performance.read-ahead: off performance.quick-read: off nfs.disable: on transport.address-family: inet server.outstanding-rpc-limit: 512 After a server reboot (brick 1) a single file has become unavailable: # touch fedora27.qcow2 touch: setting times of 'fedora27.qcow2': Input/output error Looking at the split brain status from the client side cli: # getfattr -n replica.split-brain-status fedora27.qcow2 # file: fedora27.qcow2 replica.split-brain-status="The file is not under data or metadata split-brain&...

...-threads: 32 > performance.io-cache: off > performance.read-ahead: off > performance.quick-read: off > nfs.disable: on > transport.address-family: inet > server.outstanding-rpc-limit: 512 > > After a server reboot (brick 1) a single file has become unavailable: > # touch fedora27.qcow2 > touch: setting times of 'fedora27.qcow2': Input/output error > > Looking at the split brain status from the client side cli: > # getfattr -n replica.split-brain-status fedora27.qcow2 > # file: fedora27.qcow2 > replica.split-brain-status="The file is not under...

...off > > performance.read-ahead: off > > performance.quick-read: off > > nfs.disable: on > > transport.address-family: inet > > server.outstanding-rpc-limit: 512 > > > > After a server reboot (brick 1) a single file has become unavailable: > > # touch fedora27.qcow2 > > touch: setting times of 'fedora27.qcow2': Input/output error > > > > Looking at the split brain status from the client side cli: > > # getfattr -n replica.split-brain-status fedora27.qcow2 > > # file: fedora27.qcow2 > > replica.split-brain-statu...

...t: 512 > > > Why are you not able to get the xattrs from arbiter brick? It is the same > > way as you do it on data bricks. > > Yes I must have confused myself yesterday somehow, here it is in full > from all three bricks: > > Brick 1 (virt2): # getfattr -d -m . -e hex fedora27.qcow2 > # file: fedora27.qcow2 > trusted.afr.dirty=0x000000000000000000000000 > trusted.afr.virt_images-client-1=0x000002280000000000000000 > trusted.afr.virt_images-client-3=0x000000000000000000000000 > trusted.bit-rot.version=0x1d000000000000005a3aa0db000c6563 > trusted.gfid=0x7...

...ient-1=0x000002280000000000000000 I would think that the changelog for client 1 should win by majority vote? Or how does the self-healing process work? I assumed this as the correct version, and reset client 2 on brick 2: # setfattr -n trusted.afr.virt_images-client-2 -v 0x000000000000000000000000 fedora27.qcow2 I then did a directory listing, which might have started a heal, but heal statistics show (i also did a full heal): Starting time of crawl: Fri Dec 22 11:34:47 2017 Ending time of crawl: Fri Dec 22 11:34:47 2017 Type of crawl: INDEX No. of entries healed: 0 No. of entries in split-brain: 0...

...0000 > > I would think that the changelog for client 1 should win by majority > vote? Or how does the self-healing process work? > I assumed this as the correct version, and reset client 2 on brick 2: > # setfattr -n trusted.afr.virt_images-client-2 -v > 0x000000000000000000000000 fedora27.qcow2 > > I then did a directory listing, which might have started a heal, but > heal statistics show (i also did a full heal): > Starting time of crawl: Fri Dec 22 11:34:47 2017 > > Ending time of crawl: Fri Dec 22 11:34:47 2017 > > Type of crawl: INDEX > No. of entries...

...ily: inet server.outstanding-rpc-limit: 512 > Why are you not able to get the xattrs from arbiter brick? It is the same > way as you do it on data bricks. Yes I must have confused myself yesterday somehow, here it is in full from all three bricks: Brick 1 (virt2): # getfattr -d -m . -e hex fedora27.qcow2 # file: fedora27.qcow2 trusted.afr.dirty=0x000000000000000000000000 trusted.afr.virt_images-client-1=0x000002280000000000000000 trusted.afr.virt_images-client-3=0x000000000000000000000000 trusted.bit-rot.version=0x1d000000000000005a3aa0db000c6563 trusted.gfid=0x7a36937d52fc4b55a93299e2328f02b...

...lddir/$disk'/> + <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-to...

...es/firewalld-restore/0002- firewalld-restart_0 I: [OK] ././iptables/tests/shell/testcases/ipt-restore/0001load- specific-table_0 I: [OK] ././iptables/tests/shell/testcases/ipt-save/0001load- dumps_0 I: [OK] ././iptables/tests/shell/testcases/ipt-save/0002load- fedora27-firewalld_0 I: legacy results: [OK] 9 [FAILED] 0 [TOTAL] 9 I: [OK] ././iptables/tests/shell/testcases/chain/0001duplicate_1 I: [OK] ././iptables/tests/shell/testcases/chain/0002newchain_0 I: [OK] ././iptables/tests/shell/testcases/chain/0003rename_1 I:...

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

Hi, I have a fedora27 system with a win10 guest trying to use photoshop 2015. I've adjusted the vram parameter for the guest to 512M with QXL, but photoshop still reports "3D features and some filters require 512MB vRAM and photoshop has detected less than that on your system." What is the proper way to a...

...omain='0x0000' bus='0x42' slot='0x02' function='0x5'/> + </source> + <address type='pci' domain='0x0000' bus='0x00' slot='0x0b' function='0x0'/> +</interface> + +# Source Hypervisor +#!/bin/bash + +DOMAIN=fedora27-tap01 +PF=enp66s0f0 +VF_NUM=5 +TAP_IF=tap01 +VF_XML= + +MAC=52:54:00:00:12:53 +ZERO_MAC=00:00:00:00:00:00 + +virsh domif-setlink $DOMAIN $TAP_IF up +bridge fdb del $MAC dev $PF master +virsh detach-device $DOMAIN $VF_XML +ip link set $PF vf $VF_NUM mac $ZERO_MAC + +virsh migrate --live $DOMAIN qemu...

...rt-builder fedora-27 \ --size 20G \ --update \ --install @japanese-support \ @@ -977,7 +977,7 @@ I<--import> option. virt-install --import \ --name guest --ram 2048 \ - --disk path=disk.img,format=raw --os-variant fedora25 + --disk path=disk.img,format=raw --os-variant fedora27 Notes: @@ -1012,7 +1012,7 @@ tools probably work differently as well. Import the image into Glance (the OpenStack image store) by doing: - glance image-create --name fedora-25-image --file fedora-25.img \ + glance image-create --name fedora-27-image --file fedora-27.img \ --disk-forma...

On Fri, Feb 16, 2018 at 6:38 PM, Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 16 Feb 2018 10:11:19 -0800, Sridhar Samudrala wrote: >> Ppatch 2 is in response to the community request for a 3 netdev >> solution. However, it creates some issues we'll get into in a moment. >> It extends virtio_net to use alternate datapath when available and >> registered.

On Fri, Feb 16, 2018 at 6:38 PM, Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 16 Feb 2018 10:11:19 -0800, Sridhar Samudrala wrote: >> Ppatch 2 is in response to the community request for a 3 netdev >> solution. However, it creates some issues we'll get into in a moment. >> It extends virtio_net to use alternate datapath when available and >> registered.

The main motivation for this patch is to enable cloud service providers to provide an accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes. This also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices. Patch 1 introduces a failover module that provides a generic interface for

The main motivation for this patch is to enable cloud service providers to provide an accelerated datapath to virtio-net enabled VMs in a transparent manner with no/minimal guest userspace changes. This also enables hypervisor controlled live migration to be supported with VMs that have direct attached SR-IOV VF devices. Patch 1 introduces a failover module that provides a generic interface for