[ovirt-users] Re: oVirt Engine no longer Starting
ouch, re: starting vms without ovirt, you can get access to vms locally using guestfish, i've used that before to fix vms after server room aircon failure. (it's not really a way to run the vms, but more for access when you can run the vm) export LIBGUESTFS_BACKEND=direct should be able to copy out if you need the files before you manage to solve your deps issues. you can also use this method to inspect log files on the engine vm if needed... Kind Regards, Mike On 15/01/2021 15:09, penguin pages wrote: > Update: > > [root@thor ~]# dnf update --allowerasing > Last metadata expiration check: 0:00:09 ago on Fri 15 Jan 2021 10:02:05 AM > EST. > Dependencies resolved. > = > Package > Architecture Version >Repository >Size > = > Upgrading: > cockpit-bridge x86_64 > 234-1.el8 > baseos 597 k > cockpit-system noarch > 234-1.el8 > baseos 3.1 M > replacing cockpit-dashboard.noarch 217-1.el8 > Removing dependent packages: > cockpit-ovirt-dashboard noarch > 0.14.17-1.el8 > @ovirt-4.416 M > ovirt-host x86_64 > 4.4.1-4.el8 > @ovirt-4.411 k > ovirt-hosted-engine-setup noarch > 2.4.9-1.el8 > @ovirt-4.4 1.3 M > > Transaction Summary > = > Upgrade 2 Packages > Remove 3 Packages > > Total download size: 3.7 M > Is this ok [y/N]: y > Downloading Packages: > (1/2): cockpit-bridge-234-1.el8.x86_64.rpm > > 160 kB/s | 597 kB 00:03 > (2/2): cockpit-system-234-1.el8.noarch.rpm > > 746 kB/s | 3.1 MB 00:04 > - > Total > > 499 kB/s | 3.7 MB 00:07 > Running transaction check > Transaction check succeeded. > Running transaction test > Transaction test succeeded. > Running transaction > Preparing: > > 1/1 > Upgrading: cockpit-bridge-234-1.el8.x86_64 > > 1/8 > Upgrading: cockpit-system-234-1.el8.noarch > > 2/8 > Erasing : ovirt-host-4.4.1-4.el8.x86_64 >
[ovirt-users] Re: CPU Type / Cluster
Thanks for the email; unfortunately it seems "Opteron_G5" is not on the 2nd host (guessing it was removed in 4.2 or some strange cpu compat thing); I upgraded the CPU #consumerism, now both are "model_EPYC-IBPB / EPYC Secure" and clustered. Kind Regards, Mike On 04/10/2020 17:51, Strahil Nikolov wrote: > Hi Mike, > > In order to add them to a single cluster , you should set them to Opteron_G5 > (my FX-8350 is also there) , untill you replace the host with something more > modern. > > Of course , you can have your hosts in separate clusters - but then you won't > be able to live migrate your VMs. > > Best Regards, > Strahil Nikolov > > > > > > > В събота, 3 октомври 2020 г., 16:50:24 Гринуич+3, Michael Jones > написа: > > > > > > to get these two hosts into a cluster would i need to castrate them down > to nehalem, or would i be able to botch the db for the 2nd host from > "EPYC-IBPB" to "Opteron_G5"? > > I don't really want to drop them down to nehalem, so either I can botch > the 2nd cpu so they are both on opteron_G5 or i'll have to buy a new CPU > for host1 to bring it up to "EPYC-IBPB"; > > I have; > > host1; > > # vdsm-client Host getCapabilities | grep cpuFlags | tr "," "\n" | grep > model_ | sed 's/"//' | sort -n > model_486 > model_Conroe > model_cpu64-rhel6 > model_kvm32 > model_kvm64 > model_Nehalem > model_Opteron_G1 > model_Opteron_G2 > model_Opteron_G3 > model_Opteron_G4 > model_Opteron_G5 <<<< "AMD FX(tm)-8350 Eight-Core Processor" > model_Penryn > model_pentium > model_pentium2 > model_pentium3 > model_qemu32 > model_qemu64 > model_Westmere > > host2; > > # vdsm-client Host getCapabilities | grep cpuFlags | tr "," "\n" | grep > model_ | sed 's/"//' | sort -n > model_486 > model_Conroe > model_Dhyana > model_EPYC > model_EPYC-IBPB <<<< "AMD Ryzen 7 1700X Eight-Core Processor" > model_kvm32 > model_kvm64 > model_Nehalem > model_Opteron_G1 > model_Opteron_G2 > model_Opteron_G3 > model_Penryn > model_pentium > model_pentium2 > model_pentium3 > model_qemu32 > model_qemu64 > model_SandyBridge > model_Westmere > > Thanks, > > Mike > > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/NULJX3JB736A4MHC2GX7ADDW3ZT3C37O/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/R6EB3FXBVSVF72ZN3QGAS3SOWNQKN2LG/
[ovirt-users] Re: CPU Type / Cluster
to get these two hosts into a cluster would i need to castrate them down to nehalem, or would i be able to botch the db for the 2nd host from "EPYC-IBPB" to "Opteron_G5"? I don't really want to drop them down to nehalem, so either I can botch the 2nd cpu so they are both on opteron_G5 or i'll have to buy a new CPU for host1 to bring it up to "EPYC-IBPB"; I have; host1; # vdsm-client Host getCapabilities | grep cpuFlags | tr "," "\n" | grep model_ | sed 's/"//' | sort -n model_486 model_Conroe model_cpu64-rhel6 model_kvm32 model_kvm64 model_Nehalem model_Opteron_G1 model_Opteron_G2 model_Opteron_G3 model_Opteron_G4 model_Opteron_G5 "AMD FX(tm)-8350 Eight-Core Processor" model_Penryn model_pentium model_pentium2 model_pentium3 model_qemu32 model_qemu64 model_Westmere host2; # vdsm-client Host getCapabilities | grep cpuFlags | tr "," "\n" | grep model_ | sed 's/"//' | sort -n model_486 model_Conroe model_Dhyana model_EPYC model_EPYC-IBPB "AMD Ryzen 7 1700X Eight-Core Processor" model_kvm32 model_kvm64 model_Nehalem model_Opteron_G1 model_Opteron_G2 model_Opteron_G3 model_Penryn model_pentium model_pentium2 model_pentium3 model_qemu32 model_qemu64 model_SandyBridge model_Westmere Thanks, Mike ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/NULJX3JB736A4MHC2GX7ADDW3ZT3C37O/
[ovirt-users] Re: Multiple GPU Passthrough with NVLink (Invalid I/O region)
First things I'd check would be what driver is on host and that it's all nvidia driver all the way make sure nouveau is blacklisted throughout On Fri, 4 Sep 2020, 21:01 Michael Jones, wrote: > Yea pass through, I think vgpu you have to pay for driver upgrade with > nvidia, I've not tried that and don't know the price, didn't find getting > info on it easy last time I tried. > > Have used in both legacy and uefi boot machines, don't know the chipsets > off the top of my head, will look on Monday. > > > On Fri, 4 Sep 2020, 20:56 Vinícius Ferrão, > wrote: > >> Thanks Michael and Arman. >> >> To make things clear, you guys are using Passthrough, right? It’s not >> vGPU. The 4x GPUs are added on the “Host Devices” tab of the VM. >> What I’m trying to achieve is add the 4x V100 directly to one specific VM. >> >> And finally can you guys confirm which BIOS type is being used in your >> machines? I’m with Q35 Chipset with UEFI BIOS. I haven’t tested it with >> legacy, perhaps I’ll give it a try. >> >> Thanks again. >> >> On 4 Sep 2020, at 14:09, Michael Jones wrote: >> >> Also use multiple t4, also p4, titans, no issues but never used the nvlink >> >> On Fri, 4 Sep 2020, 16:02 Arman Khalatyan, wrote: >> >>> hi, >>> with the 2xT4 we haven't seen any trouble. we have no nvlink there. >>> >>> did u try to disable the nvlink? >>> >>> >>> >>> Vinícius Ferrão via Users schrieb am Fr., 4. Sept. >>> 2020, 08:39: >>> >>>> Hello, here we go again. >>>> >>>> I’m trying to passthrough 4x NVIDIA Tesla V100 GPUs (with NVLink) to a >>>> single VM; but things aren’t that good. Only one GPU shows up on the VM. >>>> lspci is able to show the GPUs, but three of them are unusable: >>>> >>>> 08:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 >>>> 16GB] (rev a1) >>>> 09:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 >>>> 16GB] (rev a1) >>>> 0a:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 >>>> 16GB] (rev a1) >>>> 0b:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 >>>> 16GB] (rev a1) >>>> >>>> There are some errors on dmesg, regarding a misconfigured BIOS: >>>> >>>> [ 27.295972] nvidia: loading out-of-tree module taints kernel. >>>> [ 27.295980] nvidia: module license 'NVIDIA' taints kernel. >>>> [ 27.295981] Disabling lock debugging due to kernel taint >>>> [ 27.304180] nvidia: module verification failed: signature and/or >>>> required key missing - tainting kernel >>>> [ 27.364244] nvidia-nvlink: Nvlink Core is being initialized, major >>>> device number 241 >>>> [ 27.579261] nvidia :09:00.0: enabling device ( -> 0002) >>>> [ 27.579560] NVRM: This PCI I/O region assigned to your NVIDIA device >>>> is invalid: >>>>NVRM: BAR1 is 0M @ 0x0 (PCI::09:00.0) >>>> [ 27.579560] NVRM: The system BIOS may have misconfigured your GPU. >>>> [ 27.579566] nvidia: probe of :09:00.0 failed with error -1 >>>> [ 27.580727] NVRM: This PCI I/O region assigned to your NVIDIA device >>>> is invalid: >>>>NVRM: BAR0 is 0M @ 0x0 (PCI::0a:00.0) >>>> [ 27.580729] NVRM: The system BIOS may have misconfigured your GPU. >>>> [ 27.580734] nvidia: probe of :0a:00.0 failed with error -1 >>>> [ 27.581299] NVRM: This PCI I/O region assigned to your NVIDIA device >>>> is invalid: >>>>NVRM: BAR0 is 0M @ 0x0 (PCI::0b:00.0) >>>> [ 27.581300] NVRM: The system BIOS may have misconfigured your GPU. >>>> [ 27.581305] nvidia: probe of :0b:00.0 failed with error -1 >>>> [ 27.581333] NVRM: The NVIDIA probe routine failed for 3 device(s). >>>> [ 27.581334] NVRM: loading NVIDIA UNIX x86_64 Kernel Module >>>> 450.51.06 Sun Jul 19 20:02:54 UTC 2020 >>>> [ 27.649128] nvidia-modeset: Loading NVIDIA Kernel Mode Setting >>>> Driver for UNIX platforms 450.51.06 Sun Jul 19 20:06:42 UTC 2020 >>>> >>>> The host is Secure Intel Skylake (x86_64). VM is running with Q35 >>>> Chipset with UEFI (pc-q35-rhel8.2.0) >>>> >>>> I’ve tried to change the I/O mapping options on the host, tried with >>>> 56TB and 12TB without success. Same results. Didn’t tried with 512GB since &
[ovirt-users] Re: Multiple GPU Passthrough with NVLink (Invalid I/O region)
Yea pass through, I think vgpu you have to pay for driver upgrade with nvidia, I've not tried that and don't know the price, didn't find getting info on it easy last time I tried. Have used in both legacy and uefi boot machines, don't know the chipsets off the top of my head, will look on Monday. On Fri, 4 Sep 2020, 20:56 Vinícius Ferrão, wrote: > Thanks Michael and Arman. > > To make things clear, you guys are using Passthrough, right? It’s not > vGPU. The 4x GPUs are added on the “Host Devices” tab of the VM. > What I’m trying to achieve is add the 4x V100 directly to one specific VM. > > And finally can you guys confirm which BIOS type is being used in your > machines? I’m with Q35 Chipset with UEFI BIOS. I haven’t tested it with > legacy, perhaps I’ll give it a try. > > Thanks again. > > On 4 Sep 2020, at 14:09, Michael Jones wrote: > > Also use multiple t4, also p4, titans, no issues but never used the nvlink > > On Fri, 4 Sep 2020, 16:02 Arman Khalatyan, wrote: > >> hi, >> with the 2xT4 we haven't seen any trouble. we have no nvlink there. >> >> did u try to disable the nvlink? >> >> >> >> Vinícius Ferrão via Users schrieb am Fr., 4. Sept. >> 2020, 08:39: >> >>> Hello, here we go again. >>> >>> I’m trying to passthrough 4x NVIDIA Tesla V100 GPUs (with NVLink) to a >>> single VM; but things aren’t that good. Only one GPU shows up on the VM. >>> lspci is able to show the GPUs, but three of them are unusable: >>> >>> 08:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >>> (rev a1) >>> 09:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >>> (rev a1) >>> 0a:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >>> (rev a1) >>> 0b:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >>> (rev a1) >>> >>> There are some errors on dmesg, regarding a misconfigured BIOS: >>> >>> [ 27.295972] nvidia: loading out-of-tree module taints kernel. >>> [ 27.295980] nvidia: module license 'NVIDIA' taints kernel. >>> [ 27.295981] Disabling lock debugging due to kernel taint >>> [ 27.304180] nvidia: module verification failed: signature and/or >>> required key missing - tainting kernel >>> [ 27.364244] nvidia-nvlink: Nvlink Core is being initialized, major >>> device number 241 >>> [ 27.579261] nvidia :09:00.0: enabling device ( -> 0002) >>> [ 27.579560] NVRM: This PCI I/O region assigned to your NVIDIA device >>> is invalid: >>>NVRM: BAR1 is 0M @ 0x0 (PCI::09:00.0) >>> [ 27.579560] NVRM: The system BIOS may have misconfigured your GPU. >>> [ 27.579566] nvidia: probe of :09:00.0 failed with error -1 >>> [ 27.580727] NVRM: This PCI I/O region assigned to your NVIDIA device >>> is invalid: >>>NVRM: BAR0 is 0M @ 0x0 (PCI::0a:00.0) >>> [ 27.580729] NVRM: The system BIOS may have misconfigured your GPU. >>> [ 27.580734] nvidia: probe of :0a:00.0 failed with error -1 >>> [ 27.581299] NVRM: This PCI I/O region assigned to your NVIDIA device >>> is invalid: >>>NVRM: BAR0 is 0M @ 0x0 (PCI::0b:00.0) >>> [ 27.581300] NVRM: The system BIOS may have misconfigured your GPU. >>> [ 27.581305] nvidia: probe of :0b:00.0 failed with error -1 >>> [ 27.581333] NVRM: The NVIDIA probe routine failed for 3 device(s). >>> [ 27.581334] NVRM: loading NVIDIA UNIX x86_64 Kernel Module >>> 450.51.06 Sun Jul 19 20:02:54 UTC 2020 >>> [ 27.649128] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver >>> for UNIX platforms 450.51.06 Sun Jul 19 20:06:42 UTC 2020 >>> >>> The host is Secure Intel Skylake (x86_64). VM is running with Q35 >>> Chipset with UEFI (pc-q35-rhel8.2.0) >>> >>> I’ve tried to change the I/O mapping options on the host, tried with >>> 56TB and 12TB without success. Same results. Didn’t tried with 512GB since >>> the machine have 768GB of system RAM. >>> >>> Tried blacklisting the nouveau on the host, nothing. >>> Installed NVIDIA drivers on the host, nothing. >>> >>> In the host I can use the 4x V100, but inside a single VM it’s >>> impossible. >>> >>> Any suggestions? >>> >>> >>> >>> ___ >>> Users mailing list -- users@ovirt.org >>> To unsubscribe send an email to users-l
[ovirt-users] Re: Multiple GPU Passthrough with NVLink (Invalid I/O region)
Also use multiple t4, also p4, titans, no issues but never used the nvlink On Fri, 4 Sep 2020, 16:02 Arman Khalatyan, wrote: > hi, > with the 2xT4 we haven't seen any trouble. we have no nvlink there. > > did u try to disable the nvlink? > > > > Vinícius Ferrão via Users schrieb am Fr., 4. Sept. > 2020, 08:39: > >> Hello, here we go again. >> >> I’m trying to passthrough 4x NVIDIA Tesla V100 GPUs (with NVLink) to a >> single VM; but things aren’t that good. Only one GPU shows up on the VM. >> lspci is able to show the GPUs, but three of them are unusable: >> >> 08:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >> (rev a1) >> 09:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >> (rev a1) >> 0a:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >> (rev a1) >> 0b:00.0 3D controller: NVIDIA Corporation GV100GL [Tesla V100 SXM2 16GB] >> (rev a1) >> >> There are some errors on dmesg, regarding a misconfigured BIOS: >> >> [ 27.295972] nvidia: loading out-of-tree module taints kernel. >> [ 27.295980] nvidia: module license 'NVIDIA' taints kernel. >> [ 27.295981] Disabling lock debugging due to kernel taint >> [ 27.304180] nvidia: module verification failed: signature and/or >> required key missing - tainting kernel >> [ 27.364244] nvidia-nvlink: Nvlink Core is being initialized, major >> device number 241 >> [ 27.579261] nvidia :09:00.0: enabling device ( -> 0002) >> [ 27.579560] NVRM: This PCI I/O region assigned to your NVIDIA device >> is invalid: >>NVRM: BAR1 is 0M @ 0x0 (PCI::09:00.0) >> [ 27.579560] NVRM: The system BIOS may have misconfigured your GPU. >> [ 27.579566] nvidia: probe of :09:00.0 failed with error -1 >> [ 27.580727] NVRM: This PCI I/O region assigned to your NVIDIA device >> is invalid: >>NVRM: BAR0 is 0M @ 0x0 (PCI::0a:00.0) >> [ 27.580729] NVRM: The system BIOS may have misconfigured your GPU. >> [ 27.580734] nvidia: probe of :0a:00.0 failed with error -1 >> [ 27.581299] NVRM: This PCI I/O region assigned to your NVIDIA device >> is invalid: >>NVRM: BAR0 is 0M @ 0x0 (PCI::0b:00.0) >> [ 27.581300] NVRM: The system BIOS may have misconfigured your GPU. >> [ 27.581305] nvidia: probe of :0b:00.0 failed with error -1 >> [ 27.581333] NVRM: The NVIDIA probe routine failed for 3 device(s). >> [ 27.581334] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 450.51.06 >> Sun Jul 19 20:02:54 UTC 2020 >> [ 27.649128] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver >> for UNIX platforms 450.51.06 Sun Jul 19 20:06:42 UTC 2020 >> >> The host is Secure Intel Skylake (x86_64). VM is running with Q35 Chipset >> with UEFI (pc-q35-rhel8.2.0) >> >> I’ve tried to change the I/O mapping options on the host, tried with 56TB >> and 12TB without success. Same results. Didn’t tried with 512GB since the >> machine have 768GB of system RAM. >> >> Tried blacklisting the nouveau on the host, nothing. >> Installed NVIDIA drivers on the host, nothing. >> >> In the host I can use the 4x V100, but inside a single VM it’s impossible. >> >> Any suggestions? >> >> >> >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/73CXU27AX6ND6EXUJKBKKRWM6DJH7UL7/ >> > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/PIO4DIVUU4JWG5FXYW3NQSVXCFZWYV26/ > ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ZOMK6ULEK3IXNC3TQV5TYIY5SH23NNA4/
[ovirt-users] Re: Impossible to install Windows VMs on 4.4.1
I know 4.4.1 had a new windows driver iso... so you need to make sure you're using that newer one. On 27/08/2020 20:18, Michael Jones wrote: > just need to load the extra drivers, > > in virt viewer; > > 1. boot windows installer > 2. proceed installer until you see the windows with no disks present > 3. in virt-viewer swap the cd for the ovirt windows add-ons, this iso > has changed names a few times... > 4. load the driver from the iso > 5. refresh disks > 6. virtual disk will appear ready for windows to use. > > Kind Regards, > > Mike > > On 27/08/2020 13:21, fga...@gmail.com wrote: >> Hi, >> I'm having problem after I upgraded to 4.4.1 with Windows machines. >> >> The installation sees no disk. Even IDE disk doesn't get detected and >> installation won't move forward no matter what driver i use for the disk. >> >> Any one else having this issue?. >> >> Regards, >> Facundo >> ___ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LRM6X3MPFWOZ6GH7WXZBQE6VOTAFMIX7/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/JWZDSDH3QCWTGTGABBXTX5IK4EZC3B4H/
[ovirt-users] Re: Impossible to install Windows VMs on 4.4.1
just need to load the extra drivers, in virt viewer; 1. boot windows installer 2. proceed installer until you see the windows with no disks present 3. in virt-viewer swap the cd for the ovirt windows add-ons, this iso has changed names a few times... 4. load the driver from the iso 5. refresh disks 6. virtual disk will appear ready for windows to use. Kind Regards, Mike On 27/08/2020 13:21, fga...@gmail.com wrote: > Hi, > I'm having problem after I upgraded to 4.4.1 with Windows machines. > > The installation sees no disk. Even IDE disk doesn't get detected and > installation won't move forward no matter what driver i use for the disk. > > Any one else having this issue?. > > Regards, > Facundo > ___ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/LRM6X3MPFWOZ6GH7WXZBQE6VOTAFMIX7/ ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2O3WJAKMVIZ23WIAEPXJURXVX7JKGJGQ/
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 22/08/2020 23:57, Nir Soffer wrote: >> Bug raised: >> >> https://bugzilla.redhat.com/show_bug.cgi?id=1871348 > Thanks, but we need more info why you cannot use the recommended deployment. > See my questions in the bug. > updated, thanks. Mike ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/WJXS3KULGFI7BAMHU4LEKIWIEUSGCHA5/
[ovirt-users] Re: Actual oVirt install questions
On 22/08/2020 18:20, David White via Users wrote: >> You can actually upload directly via scp to the iso domain, just make >> sure to; >> >> chown -v vdsm: >> /path/to/iso/domain/local_iso_domain/000----00/images/----/uploaded-file.iso > That worked. Thanks. > I was able to get a VM going. > > Unfortunately, I can't seem to get a 2nd ISO recognized to setup a different > VM. > > I have the following structure: > [root@dev1-centos data]# pwd > /data > [root@dev1-centos data]# ls -la > total 0 > drwxr-xr-x. 4 vdsm kvm 31 Aug 19 20:49 . > dr-xr-xr-x. 19 root root 260 Aug 19 20:28 .. > drwxr-xr-x. 3 vdsm kvm 50 Aug 22 13:10 images > drwxr-xr-x. 5 vdsm kvm 124 Aug 22 13:10 iso > > [root@dev1-centos data]# cd iso/ > [root@dev1-centos iso]# ls -la > total 0 > drwxr-xr-x. 5 vdsm kvm 124 Aug 22 13:10 . > drwxr-xr-x. 4 vdsm kvm 31 Aug 19 20:49 .. > drwxr-xr-x. 3 vdsm kvm 20 Aug 22 09:47 000----00 > drwxr-xr-x. 3 vdsm kvm 20 Aug 22 12:57 000----01 when you create the iso domain, it should have created the path for you, -000-00 was just an example path; for local iso domain, it should be along the lines of; 1. create top level dir and chown to vdsm: in your case "/data/iso" 2. add iso domain in ui 3. when it added the local iso domain it will setup a bunch of subfolders, in the end folder which is 1-111-111 you can dump all your iso images in that 1x dir... ie, move the iso file "ubuntu-20.04.1-live-server-amd64.iso" into the same dir as "CentOS-8.2.2004-x86_64-minimal.iso" > > The folder ending in 0 has the original ISO I uploaded (a CentOS 8.2 ISO) - > this is working. > The folder ending in 1 has a Ubuntu 20.04 ISO. - this is not working. > > CentOS path to ISO: > /data/iso/000----00/images/----/CentOS-8.2.2004-x86_64-minimal.iso > Ubuntu path: > /data/iso/000----01/images/----1112/ubuntu-20.04.1-live-server-amd64.iso > > At this point, I have no idea why my CentOS ISO is showing up, but my Ubuntu > ISO is not showing up. > > > Second question: > I left, and came back a while later, and have noticed that when I go to > Storage -> Data Centers, that the Data Center I created (named 'Office') > keeps going from Unresponsive to Activated. It keeps going back and forth, > and I'm not sure why. That seems like an issue. check the engine logs > > > Third Question: > When I go to Compute -> Hosts, and go into the host, under Action Items, I > see: "A new version is available. Upgrade." with a link. > > Yet from the console, when I run `yum update`, nothing is available to update. > I already clicked on that Upgrade link once, and allowed the whole host to > reboot... and that Action Item is still there. > That also seems weird. I would also feel a lot more comfortable about > clicking on "Upgrade" if I had more details - what is it upgrading "from" and > what is it upgrading "to"? yum update will only ensure the packages are installed, however this doesn't mean ovirt has run the upgrade, just upgrade through the ui; 1. put host to maint 2. update host this will trigger ansible which; 1. does yum updates 2. updates the ovirt version to match your latest package you can check what the upgrade is doing as there is a one off log file each time you click update. can't remember the path off the top of my head, just look in /var/log/ovirt* > > > Sent with ProtonMail Secure Email. > > ‐‐‐ Original Message ‐‐‐ > On Saturday, August 22, 2020 9:37 AM, Michael Jones > wrote: > >> On 22/08/2020 13:58, David White via Users wrote: >> >>> So, what's the point of all-in-one if you cannot upload ISOs and boot VMs >>> off of ISOs? >>> Is there an alternative way to setup a VM in all-in-one, such as boot from >>> PXE or something? >> You can actually upload directly via scp to the iso domain, just make >> sure to; >> >> chown -v vdsm: >> /path/to/iso/domain/local_iso_domain/000----00/images/----/uploaded-file.iso >> >> the system will still see it and you can attach to vms at boot; >> >> you can also use pxe, i like the "fai" project for this. >> >>> Regardless, the all-in-one setup was just for learning purposes. >>> I may try a different install approach, and try to get the self-hosted >>> engine working. That said, I'm still unclear on the exact differences >>> between the "self-hosted engine&qu
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 20/08/2020 20:55, Michael Jones wrote: > On 19/08/2020 14:48, Michael Jones wrote: >> On 19/08/2020 12:12, Michael Jones wrote: >>> On 19/08/2020 10:41, Nir Soffer wrote: >>>>> There is no warning the method was deprecated and will be missing >>>>> functionality. >>>>> >>>>> The steps detailed on the alt install page are for the all-in-one running >>>>> engine-setup. >>>>> >>>>> It's also worth noting this works fine in; >>>>> >>>>> Version 4.3.1.1-1.el7 >>>>> >>>>> but not in; >>>>> >>>>> Version 4.4.1.10-1.el8 >>>>> >>>>> (el8 has the change in imageio daemons) >>>>> >>>>> The alternate install method is still useful to have, but i think a red >>>>> warning about all-in-one on el8 on that page would be good. >>>>> >>>>> Kind Regards, >>>>> Michael Jones >>>> Micheal, can you file a bug for this? >>>> >>>> If you have a good use case for all-in-one deployment (not using >>>> hosted engine), please explain >>>> it in the bug. >>>> >>>> Personally I think simple all-in-one deployment without the complexity >>>> of hosted engine is better, >>>> and we should keep it, but for this we need to teach engine to handle >>>> the case when the proxy >>>> and the daemon are the same server. >>>> >>>> In this case engine will not try to setup a proxy ticket, and image >>>> transfer would work directly >>>> with the host daemon. >>>> >>>> I'm not very optimistic that we will support this again, since this >>>> feature is not needed for RHV >>>> customers, but for oVirt this makes sense. >>>> >>>> Nir >>>> >>> Yes, I can file a bug, >>> >>> The main usage / setup's I have are; >>> >>> on-prem installs: >>> >>> - hosted engine >>> - gluster >>> - high availiblity >>> - internal ip address >>> - easy great... >>> >>> dedicated host provider for example OVH single machine: >>> >>> - alternate install >>> - all-in-one >>> >>> The main reason for the separation is that using the cockpit install >>> / hosted engine install causes problems with ip allocations; >>> >>> cockpit method requires 1x ip for host, and 1x ip for engine vm, and >>> both ip must be in the same subnet... >>> >>> applying internal ip would cut off access, and to make it even >>> harder, getting public ip blocks didn't work as the box main ip >>> wouldn't be in the same subnet, adding nic alias ip doesn't work >>> either (fail on install due to failing to setup ovirtmgmt network). >>> >>> atm, i'll struggle with changing the machine's main ip to be one of >>> the same subnet with the engine one... (currently causes host to be >>> taken offline due to hosting provider, health checks) >>> >>> provided i can change the host primary ip to be one of the OVH >>> failover ip allocated in a block... i will be able to install using >>> the cockpit. >>> >>> and after the install i can setup internal ip with the network tag. >>> >>> Kind Regards, >>> >>> Mike >>> >> despite managing to get OVH to disable monitoring (ping to the main >> ip, and rebooting host) and getting the host in the same ip range as >> the engine vm... >> >> ie: >> >> host ip: 158.x.x.13/32 = not used anymore >> >> new subnet: 54.x.x.x/28 >> >> and reserving; >> host = 54.x.x.16 >> engine = 54.x.x.17 >> >> [ ERROR ] The Engine VM (54.x.x.17/28) and the default gateway >> (158.x.x.254) will not be in the same IP subnet. >> >> the hosted engine installer crashes due to the gw being in a >> different subnet, so all three; >> >> - host >> - engine >> - gateway >> >> must be in the same subnet... >> >> this rules out an install on ovh dedicated server. >> >> unless... I can install the all-in-one again (this bit works), and >> then install the engine vm in an existing all-in-one setup... >> >> essentially the cockpit installation is not compatible with this >> infra setup. >> > After going through the documentation again, I understan
[ovirt-users] Re: Actual oVirt install questions
On 22/08/2020 13:58, David White via Users wrote: > So, what's the point of all-in-one if you cannot upload ISOs and boot VMs off > of ISOs? > Is there an alternative way to setup a VM in all-in-one, such as boot from > PXE or something? You can actually upload directly via scp to the iso domain, just make sure to; chown -v vdsm: /path/to/iso/domain/local_iso_domain/000----00/images/----/uploaded-file.iso the system will still see it and you can attach to vms at boot; you can also use pxe, i like the "fai" project for this. > > > Regardless, the all-in-one setup was just for learning purposes. > I may try a different install approach, and try to get the self-hosted engine > working. That said, I'm still unclear on the exact differences between the > "self-hosted engine" and the standalone Manager. I'll go re-read earlier > responses to my questions on that, as well as the glossary of sorts that Didi > was so kind to write in your earlier thread on the imageio issue. 4.4 all-in-one is still fully functional par the iso upload and download, which i was using for backups. if you were to go CentOS7+4.3 these features fully work no problem in all-in-one. the alternate to all-in-one would be to choose a different host when adding to the standalone manager, or you can have hosted engine, where the engine is a vm (dependent on some other stuff re: storage/ips) Kind Regards, Mike signature.asc Description: OpenPGP digital signature ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/ILLRQN4DUZX5NAFRC44QUJEFJKB7HYNT/
[ovirt-users] Re: Actual oVirt install questions
I see you are using 4.4 standalone; by standalone do you mean all-in-one? or separate engine and hosts? In 4.4 the change in imageio means it's not compatible with all-in-one anymore, i'll be raising a bug request to support this later today (but officially all-in-one support ended in 4.0 so i don't know if the bug will be actioned). Kind Regards, Mike On 22/08/2020 12:06, David White via Users wrote: > Ok, that at least got the certificate trusted. > Thank you for the fast response on that! > > The certificate is now installed and trusted, and I removed the exception in > Firefox. > (Screenshots attached) > > > Unfortunately, the upload is still not working. > I'm still getting the same error message that "Connection to > ovirt-imageio-proxy service has failed." > signature.asc Description: OpenPGP digital signature ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/QSUGX7LWYR7WSGEIRDE7LARKTSLC7NPA/
[ovirt-users] Re: Actual oVirt install questions
On 22/08/2020 11:20, David White via Users wrote: > I'm not sure if I'm actually importing the CA certificate into Firefox > properly. > This Red Hat solution suggests that Firefox should prompt me to install the > cert when I download it: https://access.redhat.com/solutions/95103 > > Instead, it is just downloading and displaying the certificate in plaintext. > > Perhaps this is because I'm on a newer version of Firefox? > > Anyway, it doesn't appear that I'm able to attach a CD / ISO to the VM even > from the console, which I was hoping would be an option. > So at this point, my install is kind of useless. :) 1. download it, it will save as pki-resource 2. rename file to blah.pem 3. open firefox > preferences > privacy and security > view certificates 4. open authorities tab 5. import > select blah.pem 6. check the box for trust to identify websites make sure to remove any exception granted, so it uses ca instead of exception for auth. signature.asc Description: OpenPGP digital signature ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/YY6OOFL7NHEKM77PUSSROFUGLWD3CBNW/
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 19/08/2020 14:48, Michael Jones wrote: > > > On 19/08/2020 12:12, Michael Jones wrote: >> On 19/08/2020 10:41, Nir Soffer wrote: >>>> There is no warning the method was deprecated and will be missing >>>> functionality. >>>> >>>> The steps detailed on the alt install page are for the all-in-one running >>>> engine-setup. >>>> >>>> It's also worth noting this works fine in; >>>> >>>> Version 4.3.1.1-1.el7 >>>> >>>> but not in; >>>> >>>> Version 4.4.1.10-1.el8 >>>> >>>> (el8 has the change in imageio daemons) >>>> >>>> The alternate install method is still useful to have, but i think a red >>>> warning about all-in-one on el8 on that page would be good. >>>> >>>> Kind Regards, >>>> Michael Jones >>> Micheal, can you file a bug for this? >>> >>> If you have a good use case for all-in-one deployment (not using >>> hosted engine), please explain >>> it in the bug. >>> >>> Personally I think simple all-in-one deployment without the complexity >>> of hosted engine is better, >>> and we should keep it, but for this we need to teach engine to handle >>> the case when the proxy >>> and the daemon are the same server. >>> >>> In this case engine will not try to setup a proxy ticket, and image >>> transfer would work directly >>> with the host daemon. >>> >>> I'm not very optimistic that we will support this again, since this >>> feature is not needed for RHV >>> customers, but for oVirt this makes sense. >>> >>> Nir >>> >> Yes, I can file a bug, >> >> The main usage / setup's I have are; >> >> on-prem installs: >> >> - hosted engine >> - gluster >> - high availiblity >> - internal ip address >> - easy great... >> >> dedicated host provider for example OVH single machine: >> >> - alternate install >> - all-in-one >> >> The main reason for the separation is that using the cockpit install >> / hosted engine install causes problems with ip allocations; >> >> cockpit method requires 1x ip for host, and 1x ip for engine vm, and >> both ip must be in the same subnet... >> >> applying internal ip would cut off access, and to make it even >> harder, getting public ip blocks didn't work as the box main ip >> wouldn't be in the same subnet, adding nic alias ip doesn't work >> either (fail on install due to failing to setup ovirtmgmt network). >> >> atm, i'll struggle with changing the machine's main ip to be one of >> the same subnet with the engine one... (currently causes host to be >> taken offline due to hosting provider, health checks) >> >> provided i can change the host primary ip to be one of the OVH >> failover ip allocated in a block... i will be able to install using >> the cockpit. >> >> and after the install i can setup internal ip with the network tag. >> >> Kind Regards, >> >> Mike >> > despite managing to get OVH to disable monitoring (ping to the main > ip, and rebooting host) and getting the host in the same ip range as > the engine vm... > > ie: > > host ip: 158.x.x.13/32 = not used anymore > > new subnet: 54.x.x.x/28 > > and reserving; > host = 54.x.x.16 > engine = 54.x.x.17 > > [ ERROR ] The Engine VM (54.x.x.17/28) and the default gateway > (158.x.x.254) will not be in the same IP subnet. > > the hosted engine installer crashes due to the gw being in a different > subnet, so all three; > > - host > - engine > - gateway > > must be in the same subnet... > > this rules out an install on ovh dedicated server. > > unless... I can install the all-in-one again (this bit works), and > then install the engine vm in an existing all-in-one setup... > > essentially the cockpit installation is not compatible with this infra > setup. > After going through the documentation again, I understand the best way to approach this would be to have a remote manager, ie; self hosted engine (on-prem) > host/2nd DC/Cluster (remote/ovh) standalone manager (on-prem) > host/2nd DC/Cluster (remote/ovh) That way resolves the ip issues (only need host ip, just don't install the manager on the remote server) outstanding... i need to workout the security implications of this. shame all-in-one is gone, but the above does work, and even means the remote host can again use local storage. I'll raise the bug report now i've finished testing, as I think stand alone, all-in-one, dedicated hosts are affordable and open ovirt to a wider user base (keeping hardware requirements minimal). Thanks again, Mike ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KQXRXEQRTYAARZMPA3DAZR53LPQZLY6E/
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 19/08/2020 12:12, Michael Jones wrote: > On 19/08/2020 10:41, Nir Soffer wrote: >>> There is no warning the method was deprecated and will be missing >>> functionality. >>> >>> The steps detailed on the alt install page are for the all-in-one running >>> engine-setup. >>> >>> It's also worth noting this works fine in; >>> >>> Version 4.3.1.1-1.el7 >>> >>> but not in; >>> >>> Version 4.4.1.10-1.el8 >>> >>> (el8 has the change in imageio daemons) >>> >>> The alternate install method is still useful to have, but i think a red >>> warning about all-in-one on el8 on that page would be good. >>> >>> Kind Regards, >>> Michael Jones >> Micheal, can you file a bug for this? >> >> If you have a good use case for all-in-one deployment (not using >> hosted engine), please explain >> it in the bug. >> >> Personally I think simple all-in-one deployment without the complexity >> of hosted engine is better, >> and we should keep it, but for this we need to teach engine to handle >> the case when the proxy >> and the daemon are the same server. >> >> In this case engine will not try to setup a proxy ticket, and image >> transfer would work directly >> with the host daemon. >> >> I'm not very optimistic that we will support this again, since this >> feature is not needed for RHV >> customers, but for oVirt this makes sense. >> >> Nir >> > Yes, I can file a bug, > > The main usage / setup's I have are; > > on-prem installs: > > - hosted engine > - gluster > - high availiblity > - internal ip address > - easy great... > > dedicated host provider for example OVH single machine: > > - alternate install > - all-in-one > > The main reason for the separation is that using the cockpit install / > hosted engine install causes problems with ip allocations; > > cockpit method requires 1x ip for host, and 1x ip for engine vm, and > both ip must be in the same subnet... > > applying internal ip would cut off access, and to make it even harder, > getting public ip blocks didn't work as the box main ip wouldn't be in > the same subnet, adding nic alias ip doesn't work either (fail on > install due to failing to setup ovirtmgmt network). > > atm, i'll struggle with changing the machine's main ip to be one of > the same subnet with the engine one... (currently causes host to be > taken offline due to hosting provider, health checks) > > provided i can change the host primary ip to be one of the OVH > failover ip allocated in a block... i will be able to install using > the cockpit. > > and after the install i can setup internal ip with the network tag. > > Kind Regards, > > Mike > despite managing to get OVH to disable monitoring (ping to the main ip, and rebooting host) and getting the host in the same ip range as the engine vm... ie: host ip: 158.x.x.13/32 = not used anymore new subnet: 54.x.x.x/28 and reserving; host = 54.x.x.16 engine = 54.x.x.17 [ ERROR ] The Engine VM (54.x.x.17/28) and the default gateway (158.x.x.254) will not be in the same IP subnet. the hosted engine installer crashes due to the gw being in a different subnet, so all three; - host - engine - gateway must be in the same subnet... this rules out an install on ovh dedicated server. unless... I can install the all-in-one again (this bit works), and then install the engine vm in an existing all-in-one setup... essentially the cockpit installation is not compatible with this infra setup. ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/25OJW2TRRR66KV2AKXAVGBADWYQS2A4V/
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 19/08/2020 10:41, Nir Soffer wrote: >> There is no warning the method was deprecated and will be missing >> functionality. >> >> The steps detailed on the alt install page are for the all-in-one running >> engine-setup. >> >> It's also worth noting this works fine in; >> >> Version 4.3.1.1-1.el7 >> >> but not in; >> >> Version 4.4.1.10-1.el8 >> >> (el8 has the change in imageio daemons) >> >> The alternate install method is still useful to have, but i think a red >> warning about all-in-one on el8 on that page would be good. >> >> Kind Regards, >> Michael Jones > Micheal, can you file a bug for this? > > If you have a good use case for all-in-one deployment (not using > hosted engine), please explain > it in the bug. > > Personally I think simple all-in-one deployment without the complexity > of hosted engine is better, > and we should keep it, but for this we need to teach engine to handle > the case when the proxy > and the daemon are the same server. > > In this case engine will not try to setup a proxy ticket, and image > transfer would work directly > with the host daemon. > > I'm not very optimistic that we will support this again, since this > feature is not needed for RHV > customers, but for oVirt this makes sense. > > Nir > Yes, I can file a bug, The main usage / setup's I have are; on-prem installs: - hosted engine - gluster - high availiblity - internal ip address - easy great... dedicated host provider for example OVH single machine: - alternate install - all-in-one The main reason for the separation is that using the cockpit install / hosted engine install causes problems with ip allocations; cockpit method requires 1x ip for host, and 1x ip for engine vm, and both ip must be in the same subnet... applying internal ip would cut off access, and to make it even harder, getting public ip blocks didn't work as the box main ip wouldn't be in the same subnet, adding nic alias ip doesn't work either (fail on install due to failing to setup ovirtmgmt network). atm, i'll struggle with changing the machine's main ip to be one of the same subnet with the engine one... (currently causes host to be taken offline due to hosting provider, health checks) provided i can change the host primary ip to be one of the OVH failover ip allocated in a block... i will be able to install using the cockpit. and after the install i can setup internal ip with the network tag. Kind Regards, Mike ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/3VPIDUNLYB6CHYCVIJ4AQK3G6HMQFUBW/
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 19/08/2020 06:52, Yedidyah Bar David wrote: > On Tue, Aug 18, 2020 at 8:51 PM Michael Jones wrote: >> On 18/08/2020 17:58, Nir Soffer wrote: >> >> it does sound as if, my problems are around the fact that i am using an >> all-in-one box, (host and engine all in one); >> >> https://www.ovirt.org/download/alternate_downloads.html >> >> This explains how that you can install all-in-one when engine is a VM >> running on the single host, not as a program running on the host. > Let's clarify the terminology first. I admit we are not always super-clear > about this. > > - Standalone engine - Engine is running on some machine, which it does > not manage by itself. Normally, this is a physical machine, but can be > a VM managed by something else (virsh/virt-manager, another ovirt engine, > vmware/virtualbox/hyperv/xen, etc.). > > - Hosted-engine - An engine that is running in a VM, that runs inside > a host, that this engine manages. If it sounds like a chicken-and-egg > problem, it indeed is... See documentation and some presentation slides > on the website for the architecture, if interested. > > - All-In-One - a Standalone engine that also manages, as a host, the > machine on which it runs. This used to have official support in the > past, in terms of code helping to implement it (in engine-setup): > > https://www.ovirt.org/develop/release-management/features/integration/allinone.html > > As above page states, this is long gone. However, over the years, > people did report successes in doing this manually - install and > setup an engine, then add it to itself. I agree it would be nice to > keep it working, and the discussion below indeed clarifies that it's > currently broken, but this is definitely very low priority IMO. The > official answer to the question "How can I setup oVirt on a single > machine?" is: Use Hosted-engine with gluster, a.k.a HCI. > from the link you shared, the status is; Current status * Included since 3.1 * Deprecated since 3.6.0 * Removed since 4.0.0 I think there should be a warning that the install is deprecated, traversing; - https://www.ovirt.org/ - https://www.ovirt.org/download/ (download button) - https://www.ovirt.org/download/alternate_downloads.html (Alternate download options <https://www.ovirt.org/download/alternate_downloads.html>) There is no warning the method was deprecated and will be missing functionality. The steps detailed on the alt install page are for the all-in-one running engine-setup. It's also worth noting this works fine in; Version 4.3.1.1-1.el7 but not in; Version 4.4.1.10-1.el8 (el8 has the change in imageio daemons) The alternate install method is still useful to have, but i think a red warning about all-in-one on el8 on that page would be good. Kind Regards, Michael Jones ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5K4B7A5STMH42WYSG5FDA6VDCDBNW5E4/
[ovirt-users] Re: ovirt-imageio : can't upload / download
On 18/08/2020 17:58, Nir Soffer wrote: >> it does sound as if, my problems are around the fact that i am using an >> all-in-one box, (host and engine all in one); >> >> https://www.ovirt.org/download/alternate_downloads.html > This explains how that you can install all-in-one when engine is a VM > running on the single host, not as a program running on the host. > > How did you managed to get engine installed on the same host? > > I would expect that the installer would fail or at least warn about this. > The alternate install method is essentially, install packages and run engine-setup, which doesn't setup the hosted vm. The default installer via cockpit always installs engine as vm. perhaps a warning is needed on the alternate installer page for epel8. at the moment there is only a recommendation to use the normal installer. On 18/08/2020 17:58, Nir Soffer wrote: >> the download / upload function is important to me as my backup solution >> is dependent on this. > Until the sort this out, you should know that you can transfer images > without the > proxy. The proxy is needed only for the UI, for cases when engine and hosts > are > on different networks, so the only way to transfer images is via the > engine host. I use vprotect which i think is dependent on the proxy, but I'll definitely checkout the sdk/scripts you linked. I'll post an update once the new host is setup the normal way / working. Thanks again. Michael Jones ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/5EYH4WHTVRXQN4V2Q6JSJ5HB6QFDRPTQ/
[ovirt-users] Re: ovirt-imageio : can't upload / download
Hi Nir,
Thanks for the help, not sure if this is a top post or bottom post mail
list, feel free to tell me off;
it does sound as if, my problems are around the fact that i am using an
all-in-one box, (host and engine all in one);
https://www.ovirt.org/download/alternate_downloads.html
I'm about to setup another server, so i'll perhaps try engine as vm
setup through the cockpit installer, which i've only used on ovirt
clusters so far, not on single host machines.
If that works, perhaps i'll work out a way to port the server i'm having
issues with.
the download / upload function is important to me as my backup solution
is dependent on this.
Thanks,
Kind Regards,
Michael Jones
On 18/08/2020 16:55, Nir Soffer wrote:
> On Tue, Aug 18, 2020 at 4:06 PM Michael Jones wrote:
>> I have image upload/download working on some older ovirt servers where
>> it still has the split daemon/proxy...
>>
>> on one newer one this feature is not working;
>>
>> software in use:
>>
>> CentOS 8
>> ovirt-engine-4.4.1.10-1.el8.noarch
>> ovirt-imageio-client-2.0.9-1.el8.x86_64
>> ovirt-imageio-daemon-2.0.9-1.el8.x86_64
>> ovirt-imageio-common-2.0.9-1.el8.x86_64
> Both host and engine running these versions?
>
>> the ui test button allowed me to work out 50-vdsm.conf was setting the
>> wrong remote port... (was 54322, changed to 54323)
> 50-vdsm.conf is cannot break the connection test, since it should be
> installed only
> on the hosts. On engine you have 50-engine.conf.
>
> The correct configuration for engine is:
>
> [tls]
> enable = true
> key_file = /etc/pki/ovirt-engine/keys/apache.key.nopass
> cert_file = /etc/pki/ovirt-engine/certs/apache.cer
> ca_file = /etc/pki/ovirt-engine/apache-ca.pem
>
> [remote]
> port = 54323
>
> [local]
> enable = false
>
> [control]
> transport = tcp
> port = 54324
>
> The correct settings for the hosts are:
>
> [tls]
> enable = true
> key_file = /etc/pki/vdsm/keys/vdsmkey.pem
> cert_file = /etc/pki/vdsm/certs/vdsmcert.pem
> ca_file = /etc/pki/vdsm/certs/cacert.pem
>
> [remote]
> port = 54322
>
> These files belongs to engine and vdsm and you should not change them.
> Your changes will be overwirtten on the next upgrade.
>
> The top of the file explain how to change the configuration.
>
>> updated remote with;
>>
>> [remote]
>> host = 0.0.0.0
>> port = 54323
>>
>> the test now passes, but on upload or download it still fails.
> Do you have 50-vdsm.conf on the engine host?!
>
> It sounds like you have all-in-one configuration when engine host is also
> the single host. This configuration is not supported for 5 years or so.
>
> Or you installed vdsm by mistake on engine host, in this case you will have
> both 50-vdsm.conf and 50-engine.conf, and because "vdsm" sorts after "engine"
> its configuration will win.
>
>> Next i changed the control to be unix socket instead of tcp port 54324
>> (vdsm was giving an error: Image daemon is unsupported);
>>
>> I looked up the error line in the vdsm code, and found it was looking
>> for unix socket: DAEMON_SOCK=/run/ovirt-imageio/sock
>>
>> switching to sock seemed to resolve all errors in the vdsm log;
> Expected, using tcp for the host is not supported.
>
>> ---
>>
>> content of the imageio log;
> imagieo log on engine or host?
>
>> no errors as far as i can see:
>>
>> 2020-08-18 12:49:56,109 INFO(MainThread) [server] Starting
>> (pid=2696562, version=2.0.9)
>> 2020-08-18 12:49:56,109 DEBUG (MainThread) [services] Creating
>> remote.service on port 54323
>> 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Prefer IPv4: False
>> 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Available network
>> interfaces: [(, ,
>> 6, '', ('0.0.0.0', 54323))]
>> 2020-08-18 12:49:56,111 DEBUG (MainThread) [http] Creating server
>> socket with family=AddressFamily.AF_INET and type=SocketKind.SOCK_STREAM
>> 2020-08-18 12:49:56,111 DEBUG (MainThread) [services] Securing server
>> (cafile=/etc/pki/vdsm/certs/cacert.pem,
>> certfile=/etc/pki/vdsm/certs/vdsmcert.pem,
>> keyfile=/etc/pki/vdsm/keys/vdsmkey.pem)
> So this is log from the host
>
>> 2020-08-18 12:49:56,113 INFO(MainThread) [services] remote.service
>> listening on ('0.0.0.0', 54323)
> This port is wrong, you will not be able to tansfer anything since
> engine assumes
> port 54322.
>
>> 2020-08-18 12:49:56,113 DEBUG (MainThread) [services] Creating
>> local.service on socket '\x00/org/ovirt/imageio'
>> 2020-08-18 12:49:56,113 INFO(MainThread) [services] local.service
>> liste
[ovirt-users] ovirt-imageio : can't upload / download
12:51:34,603+ INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.add_image_ticket succeeded in 0.00 seconds (__init__:312) --- engine log: urn [status=Status [code=0, message=Done]], log id: 7ac2f68b 2020-08-18 12:51:34,604Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Started transfer session with ticket id 17db8f9f-328 0-4e7c-8fbf-e5326e1f98be, timeout 300 seconds 2020-08-18 12:51:34,604Z INFO [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Adding image ticket to ovirt-imageio-proxy, id 17db8 f9f-3280-4e7c-8fbf-e5326e1f98be 2020-08-18 12:51:34,604Z ERROR [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] (default task-6) [19204d8c-ffe6-4c45-81fe-96e07097d519] Failed to add image ticket to ovirt-imageio-proxy: C onnection refused (Connection refused): java.lang.RuntimeException: Connection refused (Connection refused) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.getConnection(ImageioClient.java:114) at deployment.engine.ear.bll.jar//org.ovirt.engine.core.bll.storage.disk.image.ImageioClient.putTicket(ImageioClient.java:65) is there a way for me to validate where engine thinks the proxy is? the test button passed after changing remote port to 54323... any help much appreciated. Kind Regards, Michael Jones ___ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/W4OTINLXYDWG3YSF2OUQU3NW3ADRPGUR/
