Re: [ovirt-users] Installing Windows - no virtio-win.vfd as floppy option
Yeah I just read that. I managed to discover that there is the "virtio-win" packages available in my repo, but apparently they aren't signed. So then I disovered the Fedora relased ones that at least are signed. Guess I will give those a whirl and see where it gets me. -G On Thu, Feb 22, 2018 at 3:50 PM, Vincent Royer <vinc...@epicenergy.ca> wrote: > download the ISO separately and put it in your storage domain. Then use > the "Change CD" function to load it part-way through the windows > installation when it is looking for the disk to install to. Once you > install all the drivers, the network will start working and the drives will > show up and you'll be able to proceed with your windows installation. > > Following the instructions did not work for me either. > > *Vincent Royer* > *778-825-1057* > > > <http://www.epicenergy.ca/> > *SUSTAINABLE MOBILE ENERGY SOLUTIONS* > > > > > On Thu, Feb 22, 2018 at 3:38 PM, Geoff Sweet < > geoffrsweet+ovirtus...@gmail.com> wrote: > >> Howdy all, I'm following this document: >> >> https://www.ovirt.org/documentation/vmm-guide/chap-Installin >> g_Windows_Virtual_Machines/ >> >> To launch a couple Windows VM's. The document outlines that the >> virtio-win.vfd file is automatically installed into the ISO storage domain >> for the engine host. And that you can upload it to other ISO domains as >> needed. For the life of me, I can not find that file anywhere across any >> of my ovirt servers. For reference this is 4.2.0. >> >> Am I missing something obvious? >> >> Thanks for any help you can offer. >> >> -Geoff >> >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> >> > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Installing Windows - no virtio-win.vfd as floppy option
Howdy all, I'm following this document: https://www.ovirt.org/documentation/vmm-guide/chap-Installing_Windows_Virtual_Machines/ To launch a couple Windows VM's. The document outlines that the virtio-win.vfd file is automatically installed into the ISO storage domain for the engine host. And that you can upload it to other ISO domains as needed. For the life of me, I can not find that file anywhere across any of my ovirt servers. For reference this is 4.2.0. Am I missing something obvious? Thanks for any help you can offer. -Geoff ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] API endpoint for a VM to fetch metadata about itself
Is there an API endpoint that VM's can query to discover it's oVirt metadata? Something similar to AWS's http://169.254.169.254/latest/ meta-data/ query in EC2? I'm trying to stitch a lot of automation workflow together and so far I have had great luck with oVirt. But the next small hurdle is to figure out how all the post-install setup stuff can figure out who the VM is so it can the appropriate configurations. Thanks! -Geoff ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [ovirt-users] API endpoint for a VM to fetch metadata about itself
OK, that's a great place for me to start. However the problem is that all
my post-install tooling is now running on a VM that knows nothing about
itself (having been installed via pxe and kickstart) like it's {vm_id}.
Can the API be used to query for a VM and it's attributes based on
something like a MAC address or the IP itself?
-Geoff
On Sun, Feb 25, 2018 at 11:05 PM, Ondra Machacek <omach...@redhat.com>
wrote:
> We don't have any such resource. We have those information in different
> places of the API. For example to find the information about devices of
> the VM, like network device information (IP address, MAC, etc), you can
> query:
>
> /ovirt-engine/api/vms/{vm_id}/reporteddevices
>
> The FQDN is listed right in the basic information of the VM quering the
> VM itself:
>
> /ovirt-engine/api/vms/{vm_id}
>
> You can find all the information about specific attributes returned by
> the API here in the documentation:
>
> http://ovirt.github.io/ovirt-engine-api-model/4.2/#types/vm
>
> On 02/25/2018 03:13 AM, Geoff Sweet wrote:
>
>> Is there an API endpoint that VM's can query to discover it's oVirt
>> metadata? Something similar to AWS's http://169.254.169.254/latest/
>> meta-data/ <http://169.254.169.254/latest/meta-data/> query in EC2? I'm
>> trying to stitch a lot of automation workflow together and so far I have
>> had great luck with oVirt. But the next small hurdle is to figure out how
>> all the post-install setup stuff can figure out who the VM is so it can the
>> appropriate configurations.
>>
>> Thanks!
>> -Geoff
>>
>>
>> ___
>> Users mailing list
>> Users@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/users
>>
>>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[ovirt-users] Failed export to OVA
I'm currently running a stand alone server on 4.2.0.2-1.el7.centos. I know this is an older version and I am trying to do some exports for migrations off of it. The Export to OVA seems simple enough but it fails consistently and I really can't figure out why. The logfiles don't provide a lot of information that speaks to me. I double checked the known bug (of older versions) to make sure there is a description set for the disks associated with the VM. I also tried to look in the Ansible logs referenced below but no such log exists. I've also tried multiple different paths for the output. All with the same failure. Below you can see I am attempting to export to /tmp/. Here is the output of the engine logs: ## engine.log ## 2019-12-03 11:15:43,320-08 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-3785977) [d25a398d-f650-4911-ae2a-2ca2b54e8396] EVENT_ID: IMPORTEXPORT_STARTING_EXPORT_VM_TO_OVA(1,223), Starting to export Vm GRAYLOG as a Virtual Appliance 2019-12-03 11:15:43,916-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:43,923-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-12) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'default' is using 0 threads out of 1 and 5 tasks are waiting in the queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engine' is using 0 threads out of 500, 9 threads waiting for tasks and 0 tasks in queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engineScheduled' is using 0 threads out of 100 and 100 tasks are waiting in the queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'engineThreadMonitoring' is using 1 threads out of 1 and 0 tasks are waiting in the queue. 2019-12-03 11:15:44,261-08 INFO [org.ovirt.engine.core.bll.utils.ThreadPoolMonitoringService] (EE-ManagedThreadFactory-engineThreadMonitoring-Thread-1) [] Thread pool 'hostUpdatesChecker' is using 0 threads out of 5 and 5 tasks are waiting in the queue. 2019-12-03 11:15:45,979-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:45,988-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-64) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'CreateAllOvaDisks' (id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa') waiting on child command id: '0e3e3df9-73f5-4ca2-b592-0b9ce7371247' type:'CopyImageGroup' to complete 2019-12-03 11:15:46,882-08 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Polling and updating Async Tasks: 1 tasks, 1 tasks to poll now 2019-12-03 11:15:46,893-08 INFO [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] SPMAsyncTask::PollTask: Polling task 'fe1a173f-869c-4522-9984-9c57bace7c87' (Parent Command 'CopyImageGroup', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters') returned status 'running'. 2019-12-03 11:15:46,893-08 INFO [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (EE-ManagedThreadFactory-engineScheduled-Thread-1) [] Finished polling Tasks, will poll again in 10 seconds. 2019-12-03 11:15:50,059-08 INFO [org.ovirt.engine.core.bll.SerialChildCommandsExecutionCallback] (EE-ManagedThreadFactory-engineScheduled-Thread-31) [d25a398d-f650-4911-ae2a-2ca2b54e8396] Command 'ExportOva' (id: 'd684210f-56b3-41ba-a699-e93341afdba2') waiting on child command id: 'ef1b7dde-5908-4f1f-9d0a-228bf234d9fa' type:'CreateAllOvaDisks' to complete 2019-12-03 11:15:50,064-08 INFO [org.ovirt.engine.core.bll.ConcurrentChildCommandsExecutionCallback]
