[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

Hi,

On Tue, Oct 31, 2023 at 09:22:25PM -, Michaal R via Users wrote:
> Hi, Tomas, checking in to see if you've been able to look at the info above. 
> Let me know if there's anything I can do.

sorry, not yet. Perhaps Arik would be able to tell from the top of his
head what could be the issue here.

Tomas

> 
> Thanks!
> ___
> 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/KWQLZCKRFGAEBQYWAEP6GECMS7ZBZFE3/
___
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/J7TSEZTQ6BVUJ3HFVZTYCJDYF7WFPA5M/

[ovirt-users] Re: [External] : Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

Guys, please do not panic. virt-v2v output is full of messages and
combindes unprocessed output of various tools virt-v2v uses to do the
operation. You might even see errors there which are pretty normal and
expected.

You can tell virt-v2v properly discovered your guest OS for example by
this lines:

libguestfs: trace: v2v: inspect_get_format "/dev/sda4"
ct_name: Windows Server 2019 Datacenter
product_variant: Server
version: 10.0
arch: x86_64
hostname: **
build ID: 17763

or this line:

guestfsd: => inspect_glibguestfs: trace: v2v: inspect_get_product_name = 
"Windows Server 2019 Datacenter"

Which are from the inspection phase. Or you can see that in the final
OVF it generated on exit:


  Windows Server 2019 Datacenter
  windows_2019x64


On Thu, Oct 26, 2023 at 09:31:52PM +, Simon Coter wrote:
> It’s failing due to this error:
> 
> import-75636d68-d067-4570-84b3-3829c5cf1963-20231026T153906.log: content: 
> DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 "Invalid 
> partition
> table" at offset 0x17b "Error loading operating system" at offset 0x19a 
> "Missing operating system"; partition 1 : ID=0xee, start-CHS (0x0,0,2), 
> end-CHS
> (0x1fb,254,63), startsector 1, 4294967295 sectors

Now to clarify this. This message (and those around like export-size,
uri, etc.) come from nbdkit which is the tool that handles copying the
data from VMware. It does not need to know and does not even care what
is on the disk. Yet it is trying to interpret what's inside. It can tell
there is MBR boot sector and that there are some strings. First strings
that it could find are "Invalid partition table", "Error loading
operating system" and "Missing operating system". This is expected
because those strings belong to the bootloader. It is something you
might see if your OS failed to start. But in this context it is not
relevant at all. Nbdkit might as well say there is a string "Alice has
an apple." and the importance of the message would be the same.

Tomas

> 
> So, “virt-v2v” is not able to get your Windows-7 disk mounted to load the OS.
> 
> Simon
> 
> 
> On Oct 26, 2023, at 11:23 PM, Michaal R via Users  wrote:
> 
> Okay, it seems it got a bit further, but still errored out. I watched it 
> get past the disk import (or what looked like the disk import), but I 
> couldn't see
> in the vdsm.log file where it failed the remaining import. I tried as 
> both Other OS and as Linux (just in case the latter had a chance), but still
> failures. There were errors from vdsmd like "cannot lookup default 
> selinux label for /var/tmp/.guestfs-36/appliance.d/initrd" and some SELinux 
> errors with
> access control from qemu-kvm (the latter of which I ran the fix scripts 
> for as suggested by Cockpit). Below are the log file links from this run.
> 
> vdsm.log: 
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/aylya0u16l55ef8k36qu8/vdsm-10.26.23-15.37.log?rlkey=mawo0smdau51ja4a042bhsrqi=
> 
> 0__;!!ACWV5N9M2RV99hQ!NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQb_maUM6w$
> import log 1: 
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/xuwslr1sz9lrvbyhacasa/
> 
> import-75636d68-d067-4570-84b3-3829c5cf1963-20231026T153906.log?rlkey=kned3464ek7ctsggqddix0dsi=0__;!!ACWV5N9M2RV99hQ!
> 
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQZjHc7hRg$
> import log 2: 
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/yuimr3j0hwdpkz4siofum/
> 
> import-4a6237d9-05a0-4d5a-a7b1-ff01764a761f-20231026T155635.log?rlkey=y6kp8ttd59sbh0j8k16eauvsw=0__;!!ACWV5N9M2RV99hQ!
> 
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQb2bdYygQ$
> import log 3: 
> https://urldefense.com/v3/__https://www.dropbox.com/scl/fi/ipeol7uk00gimyn6rgfrg/
> 
> import-44bb07d9-fb1d-4e91-a025-35dc70b55cd8-20231026T160749.log?rlkey=yrrznpyagxhhgkwqsokgmk09z=0__;!!ACWV5N9M2RV99hQ!
> 
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQYrVJ_ATw$
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: 
> https://urldefense.com/v3/__https://www.ovirt.org/privacy-policy.html__;!!ACWV5N9M2RV99hQ!
> 
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQYZUcAT1w$
> oVirt Code of Conduct: 
> https://urldefense.com/v3/__https://www.ovirt.org/community/about/community-guidelines/__;!!ACWV5N9M2RV99hQ!
> 
> NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQYpOT8vxg$
> List Archives: 
> https://urldefense.com/v3/__https://lists.ovirt.org/archives/list/users@ovirt.org/message/WRNUCEDMDKUACQZPELZJAL6GAOR27XVE/__;!!
> 
> ACWV5N9M2RV99hQ!NHFEfX3K7rmRgLY00KvhRZsvZ4f_N6dn0tAShyfcyeYZ9A99xucudf2C1mGtfYvttSOAKQbwRSBMCQ$
> 
> 

> 

[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

Hi,

On Thu, Oct 26, 2023 at 09:23:50PM -, Michaal R via Users wrote:
> Okay, it seems it got a bit further, but still errored out. I watched it get 
> past the disk import (or what looked like the disk import), but I couldn't 
> see in the vdsm.log file where it failed the remaining import. I tried as 
> both Other OS and as Linux (just in case the latter had a chance), but still 
> failures. There were errors from vdsmd like "cannot lookup default selinux 
> label for /var/tmp/.guestfs-36/appliance.d/initrd" and some SELinux errors 
> with access control from qemu-kvm (the latter of which I ran the fix scripts 
> for as suggested by Cockpit). Below are the log file links from this run.

thanks for testing the patch. I can see from logs that it can read the
progress properly and it now finishes fine. Here's from vdsm.log:

2023-10-26 16:04:17,608-0500 INFO  (v2v/4a6237d9) [root] Job 
'4a6237d9-05a0-4d5a-a7b1-ff01764a761f' finished import successfully (v2v:875)
2023-10-26 16:04:32,511-0500 INFO  (jsonrpc/1) [api.host] START 
getConvertedVm(jobid='4a6237d9-05a0-4d5a-a7b1-ff01764a761f') from=***, 
flow_id=593daf15-49dc-4616-8b11-7a62f5f6ace4 (api:31)
2023-10-26 16:04:32,512-0500 INFO  (jsonrpc/1) [api.host] FINISH 
getConvertedVm return={'status': {'code': 0, 'message': 'Done'}, 'ovf': "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/FDOQVMAZSM5KHIWAVPW3ZLHG5YM3MQYP/

[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

On Thu, Oct 26, 2023 at 06:15:35PM +0200, Tomáš Golembiovský wrote:
> I have opended a pull request [1] on GitHub with the fix. Since the patch is
> simple and the test for that passes there is low risk. I have attached the
> relevant portion (without the test) to the email. What you need to do is take
> the attached patch, apply it on your host and restart vdsm:
> 
> $ cd /usr/lib...
Whops sorry, this should be:

$ cd /usr/lib/python3.9/site-packages/vdsm

> $ patch -p3 < /tmp/progress-fix.patch
> $ systemctl restart vdsmd
> 
> Then you try the import as usual. To revert the patch or if you fail to apply
> it properly for some reason, or generally in case of any doubt, reinstall the
> vdsm package with dnf and restart vdsm:
> 
> $ dnf reinstall vdsm
> $ systemctl restart vdsmd
> 
> If the import fails please post again any errors from vdsm.log and the import
> log file. It could be the patch is not good enough or perhaps there is yet
> another problem blocking you.
> 
> 
> On Thu, Oct 26, 2023 at 03:28:10PM -, Michaal R via Users wrote:
> > Also, I would like to help with the error trying to import Windows VMs when 
> > you set the OS appropriately (ie... matching the OS type at import to the 
> > OS of the VM, then getting the time zone error). If there's anything I can 
> > do or provide, please let me know.
> 
> This is more problematic as it likely involves fixing ovirt-engine. That
> in turn requires recompiling it and rebuilding the packages. That's
> much more involved and someting I cannot help with.
> 
> Tomas
> 
> [1] https://github.com/oVirt/vdsm/pull/402
> [2] https://patch-diff.githubusercontent.com/raw/oVirt/vdsm/pull/402.diff

> diff --git a/lib/vdsm/v2v.py b/lib/vdsm/v2v.py
> index 2df126a368..a05d38313e 100644
> --- a/lib/vdsm/v2v.py
> +++ b/lib/vdsm/v2v.py
> @@ -933,7 +933,7 @@ def _abort(self):
>  
>  class OutputParser(object):
>  COPY_DISK_RE = re.compile(br'.*(Copying disk (\d+)/(\d+)).*')
> -DISK_PROGRESS_RE = re.compile(br'\s+\((\d+).*')
> +DISK_PROGRESS_RE = re.compile(br'\s+\((\d+).*|.+ (\d+)% \[[*-]+\]')
>  
>  def parse(self, stream):
>  for line in stream:
> @@ -970,8 +970,9 @@ def _parse_progress(self, chunk):
>  m = self.DISK_PROGRESS_RE.match(chunk)
>  if m is None:
>  return None
> +value = [x for x in m.groups() if x is not None][0]
>  try:
> -return int(m.group(1))
> +return int(value)
>  except ValueError:
>  raise OutputParserError('error parsing progress regex: %r'
>  % m.groups)
___
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/QRDAENKTKM2Z6ZI5EZU5N42GKHTMTNNT/

[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

I have opended a pull request [1] on GitHub with the fix. Since the patch is
simple and the test for that passes there is low risk. I have attached the
relevant portion (without the test) to the email. What you need to do is take
the attached patch, apply it on your host and restart vdsm:

$ cd /usr/lib...
$ patch -p3 < /tmp/progress-fix.patch
$ systemctl restart vdsmd

Then you try the import as usual. To revert the patch or if you fail to apply
it properly for some reason, or generally in case of any doubt, reinstall the
vdsm package with dnf and restart vdsm:

$ dnf reinstall vdsm
$ systemctl restart vdsmd

If the import fails please post again any errors from vdsm.log and the import
log file. It could be the patch is not good enough or perhaps there is yet
another problem blocking you.


On Thu, Oct 26, 2023 at 03:28:10PM -, Michaal R via Users wrote:
> Also, I would like to help with the error trying to import Windows VMs when 
> you set the OS appropriately (ie... matching the OS type at import to the OS 
> of the VM, then getting the time zone error). If there's anything I can do or 
> provide, please let me know.

This is more problematic as it likely involves fixing ovirt-engine. That
in turn requires recompiling it and rebuilding the packages. That's
much more involved and someting I cannot help with.

Tomas

[1] https://github.com/oVirt/vdsm/pull/402
[2] https://patch-diff.githubusercontent.com/raw/oVirt/vdsm/pull/402.diff
diff --git a/lib/vdsm/v2v.py b/lib/vdsm/v2v.py
index 2df126a368..a05d38313e 100644
--- a/lib/vdsm/v2v.py
+++ b/lib/vdsm/v2v.py
@@ -933,7 +933,7 @@ def _abort(self):
 
 class OutputParser(object):
 COPY_DISK_RE = re.compile(br'.*(Copying disk (\d+)/(\d+)).*')
-DISK_PROGRESS_RE = re.compile(br'\s+\((\d+).*')
+DISK_PROGRESS_RE = re.compile(br'\s+\((\d+).*|.+ (\d+)% \[[*-]+\]')
 
 def parse(self, stream):
 for line in stream:
@@ -970,8 +970,9 @@ def _parse_progress(self, chunk):
 m = self.DISK_PROGRESS_RE.match(chunk)
 if m is None:
 return None
+value = [x for x in m.groups() if x is not None][0]
 try:
-return int(m.group(1))
+return int(value)
 except ValueError:
 raise OutputParserError('error parsing progress regex: %r'
 % m.groups)
___
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/PDBHNLHTXYDWU4PLEOX7UV5IO7YMJXIB/

[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

Hi,

On Wed, Oct 25, 2023 at 04:44:18PM -, Michaal R via Users wrote:
> I checked for the Fast Startup feature, which I figured wouldn't be enabled, 
> and it's not even configurable.

it really seems the VM imports below got a step further.

> 
> I tried, again, to import from vCenter and got error "All chosen VMs couldn't 
> be retrieved by the external system and therefore have been filtered. Please 
> see log for details." When I look at the log, there's nothing there 
> referencing the error. Not even sure I'm looking in the right place.
> 
> I fired up the VM, double verified Fast Startup was disabled, shut down the 
> VM again, and exported it as an OVF (folder of files). Tried to import as 
> Windows 2019 x64, same error as before ("Cannot import VM. Invalid time zone 
> for given OS type."). Tried to import as Other OS, failed, event ID 1153. I 
> get the below error log from the import log:
> 
> { "message": "Copying disk 1/1", "timestamp": 
> "2023-10-25T10:49:56.302914729-05:00", "type": "message" }
> [ 222.2] Copying disk 1/1
> protocol: newstyle-fixed without TLS, using structured packets
> export="":
>   export-size: 214748364800 (200G)
>   content: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 
> "Invalid partition table" at offset 0x17b "Error loading operating system" at 
> offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS 
> (0x0,0,2), end-CHS (0x1fb,254,63), startsector 1, 4294967295 sectors

I don't think this is a problem. virt-v2v properly detected that it is
Windows 10 what is installed in the VM.

>   uri: nbd+unix:///?socket=/tmp/v2v.qObfRy/in0
>   contexts:
>   base:allocation
>   is_rotational: false
>   is_read_only: false
>   can_cache: true
>   can_df: true
>   can_fast_zero: true
>   can_flush: true
>   can_fua: true
>   can_multi_conn: true
>   can_trim: true
>   can_zero: true
>   block_size_minimum: 1
>   block_size_preferred: 4096
>   block_size_maximum: 33554432
> 
> And this from the vdsm.log file right around when the import log ends:
> 
> 2023-10-25 10:54:07,224-0500 ERROR (v2v/e81442fd) [root] Job 
> 'e81442fd-04fc-4100-b9a1-7e0938164397' failed (v2v:851)
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 846, in _run
> self._import()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 865, in _import
> self._watch_process_output()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 888, in 
> _watch_process_output
> for event in parser.parse(out):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 944, in parse
> for chunk in self._iter_progress(stream):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 963, in 
> _iter_progress
> raise OutputParserError('copy-disk stream closed unexpectedly')
> vdsm.v2v.OutputParserError: copy-disk stream closed unexpectedly

This is the real problem. VDSM is confused because virt-v2v changed
output format and progress reporting looks different now. VDSM is still
waiting for progress update even though virt-v2v is already copying
data. And when virt-v2v terminates VDSM reports this error and aborts
the operation.

I could perhaps try creating a patch for that. But I don't have an
environment to test it.

Tomas
> 
> 
> Tried importing as Other Linux. Failed, event ID 1153. Import log has below 
> snippet (much like above):
> export="":
>   export-size: 214748364800 (200G)
>   content: DOS/MBR boot sector MS-MBR Windows 7 english at offset 0x163 
> "Invalid partition table" at offset 0x17b "Error loading operating system" at 
> offset 0x19a "Missing operating system"; partition 1 : ID=0xee, start-CHS 
> (0x0,0,2), end-CHS (0x1fb,254,63), startsector 1, 4294967295 sectors
>   uri: nbd+unix:///?socket=/tmp/v2v.kRmHY0/in0
>   contexts:
>   base:allocation
>   is_rotational: false
>   is_read_only: false
>   can_cache: true
>   can_df: true
>   can_fast_zero: true
>   can_flush: true
>   can_fua: true
>   can_multi_conn: true
>   can_trim: true
>   can_zero: true
>   block_size_minimum: 1
>   block_size_preferred: 4096
>   block_size_maximum: 33554432
> 
> vdsm.log shows below:
> 
> 2023-10-25 11:25:58,100-0500 ERROR (v2v/542ae3e4) [root] Job 
> '542ae3e4-8ea8-4f85-a35f-30bc702b8d5d' failed (v2v:851)
> Traceback (most recent call last):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 846, in _run
> self._import()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 865, in _import
> self._watch_process_output()
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 888, in 
> _watch_process_output
> for event in parser.parse(out):
>   File "/usr/lib/python3.9/site-packages/vdsm/v2v.py", line 944, in parse
> for chunk in self._iter_progress(stream):
>   File 

[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

On Tue, Oct 24, 2023 at 01:16:27PM -, Michaal R via Users wrote:
> Well, that's interesting... I wonder if the other imports I've tried give the 
> same error. That VM SHOULD have been shut down properly, but I'll check 
> again. I've three VMs that won't import, I'll check them again. Do you have 
> any insight into why the import from vCenter doesn't work? 

Well if you say that you stopped the VM and it is not hibernated then
the reason is most likely the Fast Startup feature of Windows. You can
temporarily enforce shutdown if you hold 'Shift' key when you select
'Shutdown'. If you want to disable Fast Startup then I suggest you
search the web. There are plenty of manuals covering that based on the
Windows version.

Tomas


> ___
> 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/ROIZLLQMKJO4X2I5AQGQCZEZCSSGAACT/
___
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/725GLOOME7HF6AUZVXT3NYGDTLGGXDIU/

[ovirt-users] Re: Cannot successfully import Windows vm to new ovirt deployment

[Tomáš Golembiovský]

On Sun, Oct 22, 2023 at 02:47:58PM -0500, netracerx via Users wrote:
> Did that too, before I posted here. Importing as Linux gives the same error 
> as importing as Other OS. Attempting to import directly from VMware fails 
> with a
> nondescript error message that I can't find a more descriptive log entry for.

Depending on in which phase the process failed you should possibly see
an error in vdsm.log. If the failure is during the import itself then
there should also be a virt-v2v log file in /var/log/vdsm/imports/

Hope this helps

Tomas

> The Linux import attempt says at least it can't determine the boot drive when 
> it
> attempts to import it.
> 
> 
> 
> On Oct 22, 2023 at 8:03 AM, Strahil Nikolov <[1]hunter86...@yahoo.com> 
> wrote:
> 
> Have you googled the problem ?
> 
> I find a thread with the same error: 
> [2]https://lists.ovirt.org/archives/list/users@ovirt.org/thread/GGOYZKNLBKE4QTCGJ3YFB7HYNNJID5KV/
>  
> 
> Try to import it as linux and change the type after that ?
> 
> I know that Ovirt can directly connecto to VmWare and ‘pull’ the VM, so 
> why don’t you give it a try ?
> 
> Best Regards,
> Strahil Nikolov 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> On Saturday, October 21, 2023, 10:15 PM, Michaal R via Users 
>  wrote:
> 
> I am running into an issue that, from what little Google-fu I've been 
> able to use, should be solved in oVirt 4.5. I'm trying to import WS2019 VMs 
> from
> ESXi 7 as OVFs or even OVAs. But when I do the import and set the OS 
> to Windows Server 2019 x64 in the admin portal, I get the error "Invalid time 
> zone
> for the given OS type ". If I leave it at Other OS, the import fails 
> with event ID 1153. I've been banging my head against this for over a week
> (previously couldn't get the management VM to complete setup), so any 
> guidance is appreciated. Let me know what to pull to help me pin this down?
> 
> BTW, yes this is a self hosted install as a nested VM on ESXi. Kinda 
> have to right now to test everything (easiest for me over doing a bare metal 
> on my
> old PowerEdge 2900 at the moment). Running CentOS 9 Stream.
> ___
> Users mailing list -- [3]users@ovirt.org
> To unsubscribe send an email to [4]users-le...@ovirt.org
> Privacy Statement: [5]https://www.ovirt.org/privacy-policy.html
> oVirt Code of Conduct: 
> [6]https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> [7]https://lists.ovirt.org/archives/list/users@ovirt.org/message/MZQ6TSOF2O6MV5MIMYQAVQRQQV27KBDD/
> 
> 
> 
> 
> References:
> 
> [1] mailto:hunter86...@yahoo.com
> [2] 
> https://lists.ovirt.org/archives/list/users@ovirt.org/thread/GGOYZKNLBKE4QTCGJ3YFB7HYNNJID5KV/
> [3] mailto:users@ovirt.org
> [4] mailto:users-le...@ovirt.org
> [5] https://www.ovirt.org/privacy-policy.html
> [6] https://www.ovirt.org/community/about/community-guidelines/
> [7] 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/MZQ6TSOF2O6MV5MIMYQAVQRQQV27KBDD/

> ___
> 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/5JQBIOMPO7EJ6GBB7TCHG6K6ERSDX7SW/
___
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/RZIOGU3RH2XLICOVTBIW7X4EMGOD4XPM/

[ovirt-users] Re: No bootable disk OVA

[Tomáš Golembiovský]

Hi,

On Thu, Jun 29, 2023 at 04:15:35PM -, cell...@gmail.com wrote:
> Hi all,
> we imported a rhel 9.2 image from an OVA generated on vmware and we tried to 
> create a new VM but we had a no bootable disk error. The OVA has been 
> imported with virt-2-v library

You mean you did not use the oVirt UI? If that's the case, what was the
virt-v2v command line you used? Do you have log from virt-v2v? How did
you create the disks in oVirt?

Tomas

> and if we create a new VM we noticed that the disk is 2 GB size but we 
> resized the disk to 50 GB.
> 
> The VM has been started with Q35 Chipset with UEFI options and the disk has 
> the flag bootable activated.
> 
> We're using ovirt 4.5.4-1
> 
> Could you help us to sort this issue?
> 
> Thanks,
> Marcello
> ___
> 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/6ANTGWEA34NJ3CWEAVDTNUZ7KSKIUHSE/
___
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/FJHXYR2T4BRQBI6P5CCMXQ3VDARIMOHZ/

[ovirt-users] Re: Best performance for vcpu pinning

[Tomáš Golembiovský]

On Tue, Nov 15, 2022 at 05:53:13PM -, martin.dec...@ora-solutions.net wrote:
> Hi Klaas,
> 
> in our case, the Hypervisor CPU looks like this:
> 
> CPU(s):32
> On-line CPU(s) list:   0-31
> Thread(s) per core:2
> Core(s) per socket:8
> Socket(s): 2
> NUMA node(s):  2
> NUMA node0 CPU(s): 0-7,16-23
> NUMA node1 CPU(s): 8-15,24-31
> 
> The PROD VM should have 24 PINNED (due to licensing requirements) vCPUs out 
> of the 32 threads and around 838G of the 1 TB RAM.
> The TEST VM should have 8 vCPUs out of the 32 threads and around 128G of 1 TB 
> RAM.
> 
> With these PROD VM Requirements, it does not make sense to limit vCPUs to one 
> socket / NUMA node. The TEST VM can be limited to one socket.

In this case the option here would be to actually define two vNUMA in
your PROD and TEST VMs. Give your PROD VM 12+12 and your TEST VM 4+4.
Then make sure to define the pinning so that vCPUs of one vNUMA align
with CPUs of physical NUMA. Also sharing the CPU that VDSM is using with
the TEST VM might be preferable unless you want to share some CPUs
between TEST and PROD. So like this:

TEST: pCPUs 0,1,16,17 map to first vNUMA
  pCPUs 8,9,24,25 map to second vNUMA

PROD: pCPUs 2-7,18-23 map to first vNUMA 
  pCPUS 10-15,26-31 map to second vNUMA

> 
> I guess I have made these mistakes:
> 
> - I should not use Physical CPU thread 0 but leave it for Hypervisor
> - I have configured the VM "2 threads per core" with  cores='6' threads='2'/>,

This does not add up. 16 sockets is bit too much. I think you meant
2 sockets.

> but have not specified two threads for each vCPU in the pinning field.

I don't think this is strictly necessary. But you definitely want to
make sure that the virtual threads match the physical threads. In other
words you only want to mix and match pCPUs 0 and 16 (or 1 and 17, etc.) so
I would say 0#0_1#16 is fine just like 0#0,16_1#0,16.

Alternatively you may define only single threaded VM (topology 2:12:1)
and don't care about the physical threads that much.

Which of the alternatives is best would depend on your workload in the
guest and how well it can benefit from the knowledge of the host
topology.


Hope this helps

Tomas

> In the oVirt "Resource Allocation" Tab in "CPU Pinning Topology", i have 
> specified:
> 0#8_1#9_2#10_3#11_4#12_5#13_6#14_7#15_8#16_9#17_10#18_11#19_12#20_13#21_14#22_15#23_16#24_17#25_18#26_19#27_20#28_21#29_22#30_23#31
> 
> The Calculate CPU Pinning script from the RHV HANA Guide results in this 
> mapping:
> 
> 0#1,17
> 1#1,17
> 2#2,18
> 3#2,18
> 4#3,19
> 5#3,19
> 6#4,20
> 7#4,20
> 8#5,21
> 9#5,21
> 10#6,22
> 11#6,22
> 12#9,25
> 13#9,25
> 14#10,26
> 15#10,26
> 16#11,27
> 17#11,27
> 18#12,28
> 19#12,28
> 20#13,29
> 21#13,29
> 22#14,30
> 23#14,30
> 
> But with this approach, I can not separate CPUs between PROD VM and TEST VM.
> 
> Any ideas?
> ___
> 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/PF7UCDGZPL3FJ4O5XBICJNSJKOM2ALBE/
___
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/6BYXDUJ7ZHWP742RMJNY3XBD4T3SONDP/

[ovirt-users] Re: URGENT HELP NEEDED!! Hosts are in non-operational state.

[Tomáš Golembiovský]

On Tue, Oct 25, 2022 at 08:16:56AM -, eug...@knorydev.com wrote:
> Oct 25, 2022, 4:10:01 PM - Failed to connect Host  to Storage Pool 
> 
> Oct 25, 2022, 4:10:01 PM - Host  cannot access the Storage 
> Domain(s) VM_Data attached to the . Setting Host state to 
> Non-Operational.
> Oct 25, 2022, 4:10:01 PM - Host  reports about one of the Active 
> Storage Domains as Problematic.
> Oct 25, 2022, 4:09:52 PM - Activation of host  initiated by .
> Hi All,
> 
> Today morning, noticed that my 1st and 2nd host is in non-operational status 
> and saw that my storage pool isn't being mounted and whenever I try to press 
> Activate under Management, the above error happens.
> I have multiple VM running and I can't bring it up if it goes down, and it is 
> my production server for my company.
> 
> Any advise on how to check on this or what logs to look & provide to resolve 
> this?

Start by logging into (one of) the failing host and check logs in
/var/log/vdsm and journal. This should give you more clues.

Tomas

> The person who deployed this setup is no longer in my company and I have no 
> one else to seek help for this issue.
> ___
> 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/PRNQDIWMISQ4PVVEIJQ742G6ZFQNU5WR/
___
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/MRXD6JOVLMS6VF7G7ZPY6PWOL3SQKUGE/

[ovirt-users] Re: oVirt OVA Export -> oVirt OVA Import failure

[Tomáš Golembiovský]

On Fri, Jul 01, 2022 at 04:17:00PM -, si...@justconnect.ie wrote:

> Will the single quote issue be resolved in a new release or should I accept 
> this workaround for the foreseeable future?

Depends on what you mean. The problem with superfluous quote was fixed
in oVirt 4.3 so if you still have the environment (and you're not
importing some archived OVAs) you just have to update your environment
and export agian the OVA.

If you are asking whether oVirt will be able to import the broken OVA so
that you don't have to fix them manually then I am affraid not. This is
not planned.

Tomas

-- 
Tomáš Golembiovský 
___
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/EYBWHK2DDLPXI4UU4Y7ZGBJOU6O5FTZC/

[ovirt-users] Re: oVirt OVA Export -> oVirt OVA Import failure

[Tomáš Golembiovský]

On Fri, Jul 01, 2022 at 09:17:56AM -, si...@justconnect.ie wrote:
> The error I'm seeing on the engine when loading VMs is:
> Error parsing OVF due to Error loading ovf, message Content is not allowed in 
> prolog.
> 
> Following a Google search for this error I cam up with:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1684140
> 
> The Additional info section is what I am seeing as well:
> 
> Additional info:
> The immediate difference I saw in the OVA logs is that the XML is now 
> starting with a quote: ' ...' 
> while before(working) was without it:  ...
> 
> Is this the cause and if so is there a quick fix?

Yes, this is the same issue. You will have to un-pack the OVA (it is a
tar archive) on the host. Open OVF file in editor and remove quotes from
the start and end of the XML. You don't have to re-pack the OVA, in the
import dialog you can point oVirt to the directory with extracted files.

Hope this helps,

Tomas

> 
> Kind Regards
> 
> Simon...
> ___
> 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/IRU5ANAKWNOHS2VF45MKGIVFSPFWIYQJ/

-- 
Tomáš Golembiovský 
___
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/DX43VOT65WOSVQW2ATCTXSQNUJHPQMXK/

[ovirt-users] Re: How to run virt-sysprep / How to troubleshoot template creation failure

[Tomáš Golembiovský]

On Sun, Jun 05, 2022 at 12:11:47AM -, jeremy_tourvi...@hotmail.com wrote:
> I was able to gather a VDSM log.  Would you still like the VDSM logs?  The 
> template creation process seems to be working in the sense that the template 
> always gets created.

I don't expect to find there much if the process finishes ok, but feel
free to send it to me. You don't have to post it to the mailing list.

> Now my problem has changed to having trouble with the system booting to a 
> grub prompt as mentioned in the first post.  Would the logs be of any use if 
> the template creation process finishes?
> 
> I don't understand why any VMs created from the template boot to the grub 
> prompt.

Could you please confirm that the VM that you use to create the template
works fine?

* Does the original VM boot *before* creating the template?
* Does the original VM boot *after* creating the template?
* If you clone the VM, does the clone boot?

Tomas

> ___
> 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/UB2ZO7TQK2DIIUNXBBZ6RUGDAUWXVCXW/

-- 
Tomáš Golembiovský 
___
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/5SSWJRX7MMRFRIACFYCYRRQEZMZNBSOC/

[ovirt-users] Re: How to run virt-sysprep / How to troubleshoot template creation failure

[Tomáš Golembiovský]

On Wed, May 25, 2022 at 01:04:11AM -, jeremy_tourvi...@hotmail.com wrote:
> When attempting to create a template the process fails.  It has been 
> suggested to run virt-sysprep manually and see why it it failed.  
> Specifically, I have an Ubuntu 20.04 machine that doesn't boot properly even 
> if the the template process does finish without error.

I wonder if that something tells about the template itself. How did you
create the template? Did the original VM work fine?


> I have tried creating the template several times as a test.  about 80% of the 
> time the template creation fails outright for qemu errors.  The other 20% 
> "appear" to work but the system boots to a grub emergency prompt
> 
> Can someone clarify the process?
> I know you can run the command: virt-sysprep -d 

This works for powered off libvirt domains but is not usable in oVirt
environment.

> 1. Where do you run it from?  The hypervisor host or the management engine?

It's not completely trivial to run manually and may not be the best
approach (just yet). If you have NFS domains you may be able to figure
out paths to all disks of your newly created VM and run virt-sysprep on
it. If you have block storage you need to prepare the disk images first.

For start, please provide vdsm.log. You should also see a log file
for the virt-sysprep run in /var/log/vdsm/commands/, please provide that
too.


> 2. What account do you need to use? What is the authentication username and 
> password?
> 
> I also think I read somewhere that you should refrain from using root.  
> Anything else to know?

I beleve we run all virt-* commands as vdsm user.

> 
> Anything else to try regarding the grub prompt?

Is the template worth fixing or would it make more sense to recreate it?
If the original VM/template is broken it may explain the virt-sysprep
failures.

Tomas

> 
> Thanks.
> ___
> 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/ICWANF6XMXTBHXUVMPXK442KMSRLOXI7/

-- 
Tomáš Golembiovský 
___
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/CA5RAPCXG4PO63FJGIDNGQXX3SVCIANM/

[ovirt-users] Re: Unable to boot VM due to BIOS error on oVirt 4.5.0.2.

[Tomáš Golembiovský]

On Fri, May 20, 2022 at 02:07:02AM -, msj...@kisti.re.kr wrote:
> Hi, all.
> 
> I currently operates several VMs on cockpit-machines, and I want to move 
> those VMs to oVirt.
> 
> When I tried oVirt 4.5 last month, installation failed and I tried oVirt 
> 4.3.10, it works. I moved several qcow2 disks on hyper-converged gluster and 
> I attached them on VMs and some disks boot and operate well, but some cannot 
> boot due to XFS issues - https://access.redhat.com/solutions/4582401.
> 
> So, I installed newest ovirt-engine on CentOS 8 Stream. I installed 
> ovirt-node via ovirt-node-ng-installer-4.5.0-2022051313.el8.iso. I applied 
> vdsm-gluster-cli patch manually on ovirt nodes, that does not applied on 
> ovirt-ng iso. 
> https://github.com/oVirt/vdsm/commit/2da10debcea0b9f2e235dc18c2d567e6aa4254c0.
> 
> Then, I encountered the following boot error when I launched several VMs that 
> worked on cockpit-machines and oVirt 4.3.10.
> 
> BdsDxe: failed to load Boot0001 "UEFI Misc Device" from PciRoot 
> (0x0)/Pci(0x2,0x3)/Pci(0x0,0x0): Not Found
> BdsDxe: No bootable option or device was found
> BdsDxe: Press any key to enter the Boot Manager Menu.

If your VMs are BIOS you may want to change chipset/firmware
configuration of your cluster (or on VM level) to q35+bios as it is
q35+uefi right now.

Tomas

> 
> Is there any patch that I should apply?
> 
> Best Regards
> Minseok Jang.
> 
> 
> PS.
> FIY, I leave my current status.
> 
> I currently running 4 machines
> engine.ovirt1.int - VM
> n1~n3.ovirt1.int - HP DL380 Gen9, hyper-converged gluster applied.
> 
> engine.ovirt1.int # dnf info ovirt-engine.noarch
> Installed Packages
> Name : ovirt-engine
> Version  : 4.5.0.8
> 
> n1.ovirt1.int # dnf info ovirt-release-host-node
> Installed Packages
> Name : ovirt-release-host-node
> Version  : 4.5.0.2
> 
> n1.ovirt1.int # lscpu
> Architecture:x86_64
> CPU(s):  24
> On-line CPU(s) list: 0-23
> Model name:  Intel(R) Xeon(R) CPU E5-2643 v4 @ 3.40GHz
> 
> n1.ovirt1.int # lsblk
> NAME MAJ:MIN RM   SIZE RO 
> TYPE MOUNTPOINT
> sda8:00 223.6G  0 
> disk
> ...
> └─sda3 8:30   222G  0 
> part
>   ├─onn-pool00_tmeta 253:00 1G  0 
> lvm
>   │ └─onn-pool00-tpool   253:20   173G  0 
> lvm
> ...
>   ├─onn-pool00_tdata 253:10   173G  0 
> lvm
>   │ └─onn-pool00-tpool   253:20   173G  0 
> lvm
>   ...
>   └─onn-swap 253:40 4G  0 
> lvm  [SWAP]
> sdb8:16   0   3.5T  0 
> disk
> ├─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb_tmeta   253:50  15.9G  0 
> lvm
> │ └─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb-tpool 253:70   3.5T  0 
> lvm
> │   ├─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb 253:80   3.5T  1 
> lvm
> │   └─gluster_vg_sdb-gluster_lv_vmstore1 253:10   0   3.2T  0 
> lvm  /gluster_bricks/vmstore1
> └─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb_tdata   253:60   3.5T  0 
> lvm
>   └─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb-tpool 253:70   3.5T  0 
> lvm
> ├─gluster_vg_sdb-gluster_thinpool_gluster_vg_sdb 253:80   3.5T  1 
> lvm
> └─gluster_vg_sdb-gluster_lv_vmstore1 253:10   0   3.2T  0 
> lvm  /gluster_bricks/vmstore1
> 
> # gluster volume info vmstore1
> Volume Name: vmstore1
> Type: Replicate
> Status: Started
> Number of Bricks: 1 x 3 = 3
> Bricks:
> Brick1: n1.ovirt1.int:/gluster_bricks/vmstore1/vmstore1
> Brick2: n2.ovirt1.int:/gluster_bricks/vmstore1/vmstore1
> Brick3: n3.ovirt1.int:/gluster_bricks/vmstore1/vmstore1
> ...
> ___
> 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/IC5FIL6CRJ62J2DOWCHWITW2OFHA7SWG/

-- 
Tomáš Golembiovský 
___
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/BFNTBHKIRS6BF37IXP3N5KNFRE4DAART/

[ovirt-users] Re: Set password for VM

[Tomáš Golembiovský]

Hi,

On Wed, May 04, 2022 at 02:18:18PM -, vysikant...@gmail.com wrote:
> How to set password for Virtual machine? 

In Vm/Template edit dialog see the "Initial Run" configuration. It will
be applied on first start of the VM. Alternatively, you can apply the
configuration in "Run Once" dialog when starting a VM.

The configuration differes depending on the OS of your VM: Linux
(cloud-init) or Windows (sysprep).

Tomas

> ___
> 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/6K6VRVK2CQZ2MIEZSPWZPSYUBW64NRAB/

-- 
Tomáš Golembiovský 
___
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/FDB4VG7NPSELZUTZ2XTRQJ3LSAUMYFDM/

[ovirt-users] Re: Long shot on VM failing to start

[Tomáš Golembiovský]

On Wed, Mar 09, 2022 at 12:07:51AM -, si...@justconnect.ie wrote:
> We are moving to an oVirt 4.4.9 environment from a 4.3.4.3 environment and 
> have run into a major issue.
> The method for migration to the new system is to shutdown a VM on the old 
> system, build a new VM on the new system with the same IP/name etc.

This seems unnecessarily elaborate. Was the method choice deliberate?
Why not migrate the storage domains or update the clusters?

> This has worked for several VMs so far but the latest new build failed and we 
> had to roll back - i.e. start the old VM. The old VM fails to start with the 
> following message in the VMs libvirt qemu log:
> 
> libvirtd quit during handshake: Input/output error
> shutting down, reason=failed

This is not too informative but it seems to me that something breaks when
trying to start qemu process. Could you check journal for libvirtd if
there are any errors? Also please check journal for vdsm and make sure
the service did not restart.

Hope this helps,

Tomas

> 
> Any ideas?
> Regards
> Simon...
> ___
> 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/4XOQCOLVNTOL2RWJKGREBVMVEHGTV6OX/

-- 
Tomáš Golembiovský 
___
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/HSSKORFJVOMLMKPELEZH4GKRNBDUOAZV/

[ovirt-users] Re: Linux VMs cannot boot from software raid0

[Tomáš Golembiovský]

Hi,

this seems similar to the bug: 
https://bugzilla.redhat.com/show_bug.cgi?id=1924972
that was triggered by a change in seabios. Sadly the final comments on
the bug are marked private. At the moment it seams the change in seabios
will be reverted in EL8 (on hypervisor) but it is not clear in which
version will the fix land.

I think somebody once told me that it should be possible to specify
multiple boot disks somehow -- I guess through API? Could you give that
a test? But don't take my word for it. At worst I think you could come
up with a hook that fixes domain XML by adding the bootindex to all
disks.

Hope this helps,

Tomas

On Fri, Jan 07, 2022 at 01:44:08PM +, Strahil Nikolov via Users wrote:
>  Hi Vojta
> 
> My LVM version on the hypervisor is:
> udisks2-lvm2-2.9.0-7.el8.x86_64
> llvm-compat-libs-12.0.1-4.module_el8.6.0+1041+0c503ac4.x86_64
> lvm2-libs-2.03.14-2.el8.x86_64
> lvm2-2.03.14-2.el8.x86_64
> libblockdev-lvm-2.24-8.el8.x86_64
> 
> LVM on VM:
> [root@nextcloud ~]# rpm -qa | grep lvm
> lvm2-libs-2.03.12-10.el8.x86_64
> lvm2-2.03.12-10.el8.x86_64
> 
> 
> VM disk layout is:
> 
> [root@nextcloud ~]# lsblk
> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
> sda 8:0 0 5G 0 disk 
> ├─sda1 8:1 0 500M 0 part 
> │ └─md127 9:127 0 2G 0 raid0 /boot
> └─sda2 8:2 0 4,5G 0 part 
>  └─nextcloud--system-root 253:0 0 10G 0 lvm /
> sdb 8:16 0 5G 0 disk 
> ├─sdb1 8:17 0 500M 0 part 
> │ └─md127 9:127 0 2G 0 raid0 /boot
> └─sdb2 8:18 0 4,5G 0 part 
>  └─nextcloud--system-root 253:0 0 10G 0 lvm /
> sdc 8:32 0 5G 0 disk 
> ├─sdc1 8:33 0 500M 0 part 
> │ └─md127 9:127 0 2G 0 raid0 /boot
> └─sdc2 8:34 0 4,5G 0 part 
>  └─nextcloud--system-root 253:0 0 10G 0 lvm /
> sdd 8:48 0 5G 0 disk 
> ├─sdd1 8:49 0 500M 0 part 
> │ └─md127 9:127 0 2G 0 raid0 /boot
> └─sdd2 8:50 0 4,5G 0 part 
>  └─nextcloud--system-root 253:0 0 10G 0 lvm /
> sde 8:64 0 1G 0 disk 
> └─nextcloud--db-db 253:2 0 4G 0 lvm /var/lib/mysql
> sdf 8:80 0 1G 0 disk 
> └─nextcloud--db-db 253:2 0 4G 0 lvm /var/lib/mysql
> sdg 8:96 0 1G 0 disk 
> └─nextcloud--db-db 253:2 0 4G 0 lvm /var/lib/mysql
> sdh 8:112 0 1G 0 disk 
> └─nextcloud--db-db 253:2 0 4G 0 lvm /var/lib/mysql
> sdi 8:128 0 300G 0 disk 
> └─data-slow 253:1 0 600G 0 lvm /var/www/html/nextcloud/data
> sdj 8:144 0 300G 0 disk 
> └─data-slow 253:1 0 600G 0 lvm /var/www/html/nextcloud/data
> sr0
> 
> 
> 
> 
> I have managed to start my VM as follows:
> 1. Start the VM
> 2. Dump the VM xml
> 3. Destroy
> 4. Add " to every disk entry in the dump file
> 5. virsh define VM.xml
> 6. virsh start VM
> 
> 
> Sadly I can't set more than 1 disk as bootable in oVirt.
> 
> 
> Best Regards,
> Strahil Nikolov В петък, 7 януари 2022 г., 13:38:59 Гринуич+2, Vojtech 
> Juranek  написа:  
>  
>  Hi,
> 
> > Hi All,
> > I recently migrated from 4.3.10 to 4.4.9 and it seems that booting from
> > software raid0 (I have multiple gluster volumes) is not possible with
> > Cluster compatibility 4.6 . I've tested creating a fresh VM and it also
> > suffers the problem. Changing various options (virtio-scsi to virtio,
> > chipset, VM type) did not help . Booting from rescue media shows that the
> > data is still there, but grub always drops to rescue. Any hints are
> > welcome.
> > Host: CentOS Stream 8 with qemu-6.0.0oVirt 4.4.9 (latest)VM OS:
> > RHEL7.9/RHEL8.5 Best Regards,Strahil Nikolov
> 
> What is the lvm version? There was recently issue [1] with specific lvm 
> version 
> (lvm2-2.03.14-1.el8.x86_64) which could cause boot failures.
> 
> Vojta
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2026370
> 
> ___
> 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/R2NI7T7QUD7MMIXWFRH4K7ZBTSCZSUWG/
>   

> ___
> 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/NVJQXU2VKABK7XJP3YMI5AXQC2GO2SMP/


-- 
Tomáš Golembiovský 
___
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/C2ZRCRJQX7U633DPQLRCGW4KPCCZFOYJ/

[ovirt-users] Re: cannot stop vm normally

[Tomáš Golembiovský]

Hi,

On Fri, Oct 15, 2021 at 12:04:22AM +0800, Tommy Sway wrote:
> Sometimes, some vm failed to stop it by press the shutdown button on the
> management portal, it will show such message in log: shutdown of vm ***
> failed.
> 
>  
> 
> And I want to know:
> 
> 1. why cannot shutdown it normally ?

You should possibly find more information in vdsm.log about why it has
failed.

> 2. what difference between the shutdown and power off ? (For example,
> what are the different signals sent to the QEMU process)

Power off forcibly stops the VM. From the VM point of view it is similar
to pulling out a power cord from bare metal computer.

Shutdown delivers a request to the guest OS (which may or may not
satisfy the request). If you see an error it means there was a problem
communicating the request to the guest. The request is delivered either
using a guest agent (if one is installed) or using an ACPI event.

Hope this helps,

Tomas
___
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/THOCQBPGS3AQ4CN3XMHLZR6N25SMI3WM/

[ovirt-users] Re: qemu-guest-agent not reporting IP address on boot?

[Tomáš Golembiovský]

On Wed, Oct 06, 2021 at 10:48:51PM +, Schreuders, Cliffe wrote:
> Following up on this, for the benefit of anyone else who faces the same 
> problem, I'm happy to say we have VMs reporting IP addresses with latest Kali 
> now.
> 
> I've not managed to fix the fact that it is taking Kali a lot longer to 
> report IP address (compared to the last version that shipped with 
> ovirt-guest-agent, which reports IP addresses almost instantly on boot), but 
> I extended the time out to give a lot more time for the VM to get an IP 
> address (it is taking around 5 minutes),

Good to hear that it is working now. Which version of oVirt are you
using? There were improvements for the delay of initial guest
information in oVirt 4.4 and the information should be available as soon
as the VM comes up.

Tomas


> and also needed to add exception handling to the Vagrant oVirt plugin, around 
> accessing the nics_service, which was throwing an oVirt error after a few 
> minutes "Can't send request: Failed sending data to the peer", after allowing 
> those errors to be ignored during the wait for an IP to be reported, it does 
> eventually report the IP address, and other guest information. VMs are now 
> reliably building again (albeit taking a little longer).
> 
> Thanks.
> 
> Cheers,
> Cliffe.
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email

-- 
Tomáš Golembiovský 
___
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/L4TTQPWAFONLXTRDFK4475TKBF6UYG4R/

[ovirt-users] Re: qemu-guest-agent not reporting IP address on boot?

[Tomáš Golembiovský]

On Mon, Oct 04, 2021 at 01:03:10PM +, Schreuders, Cliffe wrote:
> Thank you. It does look like that bug could be related.

Is the problem just with the IP addresses? Do you see other guest
information or are those missing too?

Tomas

> 
> I had an earlier version of the VM template which continued to work 
> correctly, and an updated version (via apt-get dist-upgrade) that did not 
> report IP addresses correctly.
> 
> I suspected that it might be related to the new ovirt/qemu user agent, so I 
> hold/pinned "ovirt-guest-agent" on the older template before re-running the 
> software updates.
> 
> This worked to create an updated Kali VM that reports it's IP address (albeit 
> more-or-less stuck with whatever dependencies the last ovirt-guest-agent has) 
> so it seems this is indeed an issue with qemu-guest-agent vs 
> ovirt-guest-agent.
> 
> Cheers,
> Cliffe.
> 
> From: Arik Hadas 
> Sent: 03 October 2021 12:04
> To: Schreuders, Cliffe 
> Cc: users ; Tomas Golembiovsky 
> Subject: Re: [ovirt-users] qemu-guest-agent not reporting IP address on boot?
> 
> 
> Caution External Mail: Do not click any links or open any attachments unless 
> you trust the sender and know that the content is safe.
> 
> 
> On Fri, Oct 1, 2021 at 5:51 PM 
> mailto:c.schreud...@leedsbeckett.ac.uk>> 
> wrote:
> Hi folks,
> 
> Kali Linux repos (based on Debian) no longer ship ovirt-guest-agent, and 
> instead package qemu-guest-agent. However, since this upgrade VMs based on 
> Kali no longer report their IP address to oVirt (and therefore timeout during 
> provisioning). If I interact with the VM console, the VM does have an IP 
> address, and the agent is running, yet oVirt reports N/A IP address. I've 
> tried restarting the agent, but that does not help. If I load the console and 
> use the VM it seems to increase the chances the IP address will eventually 
> makes it's way to oVirt, although I can't seem to reproduce an update, or get 
> it to provide the IP address on boot so that provisioning works reliably.
> 
> Any suggestions would be really appreciated.
> 
> Might be the same as/related to 
> https://bugzilla.redhat.com/show_bug.cgi?id=1981946<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.redhat.com%2Fshow_bug.cgi%3Fid%3D1981946=04%7C01%7Cc.schreuders%40leedsbeckett.ac.uk%7Cd984438c50ec4ba4e43d08d9865d93d6%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637688558745831758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=Dzfi%2FwYDoj9Y1qDcqWvTWhrJuvyEdXJq3RPGqGnRWRI%3D=0>
>  which is still being investigated
> 
> 
> Thank you.
> 
> Cheers,
> Cliffe.
> ___
> Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
> To unsubscribe send an email to 
> users-le...@ovirt.org<mailto:users-le...@ovirt.org>
> Privacy Statement: 
> https://www.ovirt.org/privacy-policy.html<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fprivacy-policy.html=04%7C01%7Cc.schreuders%40leedsbeckett.ac.uk%7Cd984438c50ec4ba4e43d08d9865d93d6%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637688558745831758%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=dXN%2BQAe4cTadmAyLNutP88Mkw%2F%2B8b3IsIcNzC2BAWt0%3D=0>
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ovirt.org%2Fcommunity%2Fabout%2Fcommunity-guidelines%2F=04%7C01%7Cc.schreuders%40leedsbeckett.ac.uk%7Cd984438c50ec4ba4e43d08d9865d93d6%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637688558745841753%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=XNy5auQL7MlljM2nrV5BjHVST4iIEQgoywYv6hYMOI0%3D=0>
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/FFINLLXPBRKYHNTBEI5GKZY53C3KX2OD/<https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.ovirt.org%2Farchives%2Flist%2Fusers%40ovirt.org%2Fmessage%2FFFINLLXPBRKYHNTBEI5GKZY53C3KX2OD%2F=04%7C01%7Cc.schreuders%40leedsbeckett.ac.uk%7Cd984438c50ec4ba4e43d08d9865d93d6%7Cd79a81124fbe417aa112cd0fb490d85c%7C0%7C0%7C637688558745841753%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000=WQnaB0srW3RKsZQ9UmYCUDcweyskmY%2Bmnb9NfoU3KK8%3D=0>
> To view the terms under which this email is distributed, please go to:-
> https://leedsbeckett.ac.uk/disclaimer/email

-- 
Tomáš Golembiovský 
___
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/S5NEZD5KKFMQJ57FKHHUJ23FOCJBGQ4X/

[ovirt-users] Re: Template for Ubuntu 18.04 Server Issues

[Tomáš Golembiovský]

> Found out a workaround, please check this link. It worked for us:
> https://kb.vmware.com/s/article/82229

Which oVirt version are we talking about? With oVirt 4.4.7 the
machine-id should be reset properly for each VM as we run virt-sysprep
also when creating the VM from template (unless it is in pool I think).
See semi-related bug: https://bugzilla.redhat.com/1887434

Hope this helps,

Tomas

On Wed, Aug 25, 2021 at 09:55:35PM -, Miguel Garcia wrote:
> ___
> 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/LCDSV775KOAMGHGL22F5JQB2KOQQCRRN/

-- 
Tomáš Golembiovský 
___
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/HRDB2WGWEF4UCB66VI56ODLEKLERLHIW/

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

[Tomáš Golembiovský]

Hi, sorry for late reply. To understand this we will have to see the
logs. Please open a bug on vdsm with description of the problem and log
attached.

Use the following procedure:
- stop the VM on problematic host
- enable debug logs for vds logger, you can do that either in
  /etc/vdsm/logger.conf (requires vdsmd restart) or temporarily from
  command line with:
  
vdsm-client Host setLogLevel level=DEBUG name=vds

- start the VM
- let it run for several minutes
- attach vdsm.log, engine.log and output of:

vdsm-client VM getStats vmID=

Thanks,

Tomas

On Sun, Jul 11, 2021 at 09:15:35PM -0300, Gervais de Montbrun wrote:
> This problem continues and I am expecting issues tomorrow morning when my 
> developers return to the office... ☹️
> 
> I did notice that my ovirt-engine is still running CentOS Linux and not 
> CentOS Stream. The release notes say that the oVirt nodes and the engine 
> would be running CentOS Stream after updating. The nodes are all on CentOS 
> stream and I had to do the necessary steps to get selinux to allow migrations 
> and fixed up the extra yum repos.
> 
> Does something need to be done regarding the ovirt-engine. I'm not seeing 
> anything in the release notes or in general documentation regarding upgrades. 
> Could the issues I am having be related to still being on CentOS Linux?
> 
> Cheers,
> Gervais
> 
> 
> 
> > On Jul 9, 2021, at 4:18 PM, Gervais de Montbrun  
> > wrote:
> > 
> > Hi Folks,
> > 
> > I upgraded my cluster yesterday and am having the same issue described 
> > here.  Boxes are booting up, but their IP addresses are never being updated 
> > in the oVirt admin console.
> > 
> > Restarting the hosts seemed to temporarily solve the issue, but it quickly 
> > returns. This is a huge issue for us as we need the ovirt engine to have 
> > the correct IP address of vm's in it as the vagrant plugin we use queries 
> > the ovirt api and uses this IP to communicate with vm's.
> > 
> > This is stopping our development team from being able to create new vm's. 
> > It will become a massive issue for me very quickly.
> > 
> > My installed versoion:
> > libvirt-7.4.0-1.el8s.x86_64
> > vdsm-common-4.40.70.6-1.el8.noarch
> > qemu-kvm-6.0.0-19.el8s.x86_64
> > 
> > Any help would be greatly appreciated.
> > 
> > Cheers,
> > Gervais
> > 
> > 
> > 
> >> On Jul 9, 2021, at 6:51 AM, Christoph Timm  >> <mailto:ov...@timmi.org>> wrote:
> >> 
> >> Hi Tomáš,
> >> 
> >> I put the host in maintenance today and give it another reboot.
> >> After that the information are available for the VMs running on that host.
> >> Also the exclamation mark is gone.
> >> 
> >> So I guess something did not come up correctly during the restart of the 
> >> host.
> >> 
> >> Best regards
> >> Christoph
> >> 
> >> Am 08.07.21 um 20:36 schrieb Christoph Timm:
> >>> Hi Tomáš,
> >>> 
> >>> sorry for the late reply and for my the missing information.
> >>> 
> >>> Am 08.07.21 um 16:50 schrieb Tomáš Golembiovský:
> >>>> On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:
> >>>>> Hi list,
> >>>>> 
> >>>>> I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs 
> >>>>> have
> >>>>> issues to report the performance information via the guest agent.
> >>>> The performance info is provided by libvirt and not by guest agent.
> >>>> Could you be more specific about which information is missing?
> >>> Sorry I did not mean the performance information like Memory, CPU and 
> >>> Network. These are available. The missing information are IP Addresses 
> >>> and FQDN. 
> >>>> What is the version of vdsm and libvirt on the host?
> >>> All hosts are running: libvirt-7.0.0-14.1.el8
> >>>> 
> >>>>> I see the following message on the VMs: The latest guest agent needs to 
> >>>>> be
> >>>>> installed and running on the guest
> >>>>> 
> >>>> This is probably unrelated to the above. But still, what is the exact
> >>>> version of the guest agent?
> >>> I have tried already different versions.
> >>> For example: 
> >>> qemu-guest-agent.x86_64
> >>> 15:4.2.0-48.module_el8.4.0+783+f8734d30 @@commandline
> >>> qemu-guest-agent.x86_64  

[ovirt-users] Re: [4.4.7] The latest guest agent needs to be installed and running on the guest

[Tomáš Golembiovský]

On Thu, Jul 08, 2021 at 02:02:14PM +0200, Christoph Timm wrote:
> Hi list,
> 
> I have upgraded my oVirt from 4.4.4 to 4.4.7 and notice that some VMs have
> issues to report the performance information via the guest agent.

The performance info is provided by libvirt and not by guest agent.
Could you be more specific about which information is missing?

What is the version of vdsm and libvirt on the host?

> 
> I see the following message on the VMs: The latest guest agent needs to be
> installed and running on the guest
> 

This is probably unrelated to the above. But still, what is the exact
version of the guest agent?

> The qemu-guest agent is installed on VMs (the VM OS is CentOS 8).
> 
> Any advice how to troubleshoot this?
> 
> I can see the stats will be presented in the GUI, if I migrate the VM to a
> different host.

Same here, could you provide version of vdsm and libvirt on the host
where your VM is working fine?

Tomas

> 
> Best regards
> Christoph
> 
> ___
> 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/4F5X6BK5OYACFSPSLIHWYE2NXQROS5R3/

-- 
Tomáš Golembiovský 
___
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/KSL3TZMWGTGLN7FDBA6IUSDEER2ZGENI/

[ovirt-users] Re: Rootless Podman container not displaying in oVirt Manager

[Tomáš Golembiovský]

On Tue, Jun 08, 2021 at 07:58:30PM +, David White via Users wrote:
> I deployed a rootless Podman container on a RHEL 8 guest on Saturday (3 days 
> ago).

Qemu-ga does not report containers. This feature was only present in
ovirt-guest-agent (i.e. it is unavailable on RHEL 8 guest) and it worked
only for docker (i.e. no podman containers).

Tomas


> 
> At the time, I remember seeing some selinux AVC "denied" messages related to 
> qemu-guest-agent and podman, but I didn't have time to look into it further, 
> but made a mental note to come back to it, because it really smelled like a 
> bug to me.
> So, I came back to it this afternoon, and now I see nothing when I look for 
> `ausearch -m AVC`
> 
> I restarted the `quemu-guest-agent` service with systemctl, and ran `ausearch 
> -m AVC` again, hoping to see some results, but I still don't.
> I really wish that I had at least copied the AVC message I saw on Saturday 
> for later investigation, but I fully expected to be able to find that 
> information again today.
> 
> Regardless, I have a rootless container running on the guest VM.
> When I login to the oVirt Manager and navigate to the VM -> Containers, I 
> don't see anything listed.
> 
> On Saturday, I thought this was a bug with selinux and qemu-guest-agent.
> But now, I have no idea.
> 
> Any thoughts?
> 
> Sent with ProtonMail Secure Email.





> ___
> 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/R6IGT4FSIRVRCCBHMB6QNRKV6T7BGFIR/


-- 
Tomáš Golembiovský 
___
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/JS6N25U3SSGCLQEY2Q5P5WWTWFRARGM3/

[ovirt-users] Re: Import VM with Xen Based in Ovirt

[Tomáš Golembiovský]

Hi,

this looks like libvirt errors. Possibly you should be able to get more
information on libvirt-users list maybe.

Hope this helps,

Tomas

On Wed, Apr 28, 2021 at 09:35:25AM -, hemaa--- via Users wrote:
> Any leads please?
> ___
> 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/WB7KTXNCLD27R2II4XPMAFJUZEDZXOJA/

-- 
Tomáš Golembiovský 
___
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/7UO2G7BVQFV7L7EG4KWRA42EXVQMC53M/

[ovirt-users] Re: Import VMs from disk

[Tomáš Golembiovský]

On Tue, Mar 30, 2021 at 02:19:22PM -, Valerio Luccio wrote:
> I might have some more details, but I don't know what it means.
> 
> When I do 'qemu-img info' on the VM image in backup I get:
> 
> file format: raw
> virtual size: 128 GiB (137438953472 bytes)
> disk size: 128 GiB
> 
> When I do the same on the VM image that was copied to the new storage I get:
> 
>file format: raw
>virtual size: 128 GiB (137438953472 bytes)
>disk size: 4 KiB
> 
> Am I reading this wrong, or did something go wrong in the import ?

Something went wrong and the upload did not happen. It seems that the
image is empty.

Tomas

> ___
> 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/P35LA2ZRUQ5W25JPL4Z5MBUBCKJFW25R/

-- 
Tomáš Golembiovský 
___
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/ZWSFGES4CO33XLUZW46TYORFEEGTYPS6/

[ovirt-users] Re: Import VMs from disk

[Tomáš Golembiovský]

On Tue, Mar 30, 2021 at 12:55:36PM -, Valerio Luccio wrote:
> > On Mon, Mar 29, 2021 at 09:03:41PM -, valerio.luccio(a)nyu.edu wrote:
> > 
> > This does not seem right. The whole idea behind disk upload is that you
> > can do that remotely from any machine that has access to the REST API.
> > If this is not working for you (but works when performed from the
> > server) you're probably missing the oVirt CA certificates in your
> > browser.
> 
> I do "Upload Image" and then hit "Chose File", the file selector opens up on 
> my laptop, which does not have access to the gluster storage.

Ok, I understand now.

> 
> > 
> > 
> > The VM is most likely misconfigured. Make sure the attached disk is
> > marked as bootable in web UI. Also verify that the chipset/firmware for
> > your VM or cluster is correct.
> > 
> > Tomas
> 
> Sorry, where do you mark a disk to be bootable ? I didn't notice any such 
> option when loading the disk.

In the VM edit dialog if you choose to Attach a disk the list contains
column with checkboxes denoted 'OS'. Alternatively if you use Create or
Edit action there are checkboxes on the right hand side of the dialog
and one of them is named 'Bootable'

Tomas

> 
> The chipset/firmware should be correct since this this is the same server 
> where the VM was working a week ago and I haven't modified the VM image.
> 
> Thanks Tomas,
> ___
> 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/GW4NENV6BIAIVRVSCP3COFNTRHIGYJF2/

-- 
Tomáš Golembiovský 
___
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/CHONV3XZA2SNVEWV5EH7YVTNDZMNLO64/

[ovirt-users] Re: Import VMs from disk

[Tomáš Golembiovský]

On Mon, Mar 29, 2021 at 09:03:41PM -, valerio.luc...@nyu.edu wrote:
> Kind of ...
> 
> First I had to run remotely a browser on the server, the only way to upload 
> files on the storage attached to it.

This does not seem right. The whole idea behind disk upload is that you
can do that remotely from any machine that has access to the REST API.
If this is not working for you (but works when performed from the
server) you're probably missing the oVirt CA certificates in your
browser.

> 
> I then created a new VM and attached the disk, but when it boots up it tells 
> me that it does not find a bootable device. What am I missing ?

The VM is most likely misconfigured. Make sure the attached disk is
marked as bootable in web UI. Also verify that the chipset/firmware for
your VM or cluster is correct.

Tomas

> 
> Thanks,
> ___
> 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/Z4EEIW2IPJWUK46UXUTTWYQOUZRY4MCM/

-- 
Tomáš Golembiovský 
___
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/MEXJMLIEQ2DRXTFIMZCYPJVT34T4TRN5/

[ovirt-users] Re: Import VMs from disk

[Tomáš Golembiovský]

On Mon, Mar 29, 2021 at 05:32:50PM -, valerio.luc...@nyu.edu wrote:
> As I've described before I had issues with my deployment and had to recreate 
> the engine.
> I never had a chance to export my VMs, but I did back up the files. Now I 
> would like to import the old VMs into the new engine. Is there a way to 
> 'slurp' in the old images ? I see different way to import from an export 
> domain, form VMWare, etc., but I don't see a way to import directly from 
> disk. Do I need to convert them ? To what and how ?

Go to the Storage -> Disks page, from there you can upload your disks to
the storage domain. Then you can create a new VM and attach existing
disks to it. If that's what you're looking for.

Tomas

> 
> Thanks, 
> ___
> 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/SJJPKRP5PVGRHSBXJNJXSGU5X57YZJ6U/

-- 
Tomáš Golembiovský 
___
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/TAB7PUPN4VXL5JIVMZXMJO5DLC6FT4BD/

[ovirt-users] Re: Reset NVRAM

[Tomáš Golembiovský]

On Mon, Mar 15, 2021 at 04:12:51PM +, Shantur Rathore wrote:
> Thanks Tomáš,
> 
> Actually I hit "Send" too quickly. Are you experiencing the issue after
> > VM reboot or even after shutdown? Because NVRAM is kept between reboots
> > and is removed only after VM shutdown.
> 
> 
> It happens after shutdown and reboot. The VM just goes into a weird state
> with "Guest hasn't initialised the display (yet)" error.
> If I create another VM with the same configuration and use the same boot
> disk it works fine.
> 
> So, if it's not NVRAM, I am not sure what could it be which stays with VM
> but is not a disk.

Maybe something in domain XML. You can compare the domain XML of VM that
does not boot any longer with your newly created VM.

One way or another, you'll have to provide more information regarding
the steps that lead to the unbootable VM before we can provide any
usefull hints.

Tomas


> 
> Thanks,
> shantur
> 
> On Mon, Mar 15, 2021 at 3:47 PM Tomáš Golembiovský 
> wrote:
> 
> > On Mon, Mar 15, 2021 at 04:43:20PM +0100, Tomáš Golembiovský wrote:
> > > On Mon, Mar 15, 2021 at 01:13:10PM +, Shantur Rathore wrote:
> > > > Hi all,
> > > >
> > > > I am doing some testing with GPU passthrough to VMs and in some cases
> > the
> > > > OVMF stops booting after a GPU passthrough.
> > > > I have figured out that it's related to some state stored in NVRAM by
> > OVMF
> > > > and as soon as I create another VM with the same disks it starts
> > booting up.
> > > >
> > > > I believe oVirt saves the NVRAM state.
> > >
> > > No it isn't. Or, better said, it wasn't. Storing of NVRAM is a new
> > > feature in 4.4.5 and it will be enabled only for VMs with Secure Boot.
> > >
> > > So whatever you're experiencing is probably caused by something else.
> >
> > Actually I hit "Send" too quickly. Are you experiencing the issue after
> > VM reboot or even after shutdown? Because NVRAM is kept between reboots
> > and is removed only after VM shutdown.
> >
> > Tomas
> >
> > >
> > > >  Is there a way to clear NVRAM for a VM without deleting it?
> > >
> > > This is not part of the feature introduced in 4.4.5. But it would make
> > > sense to have it if we later extend the NVRAM storing to all VMs with
> > > UEFI. So despite what I wrote above it would be worth opening a feature
> > > request bug.
> > >
> > > Tomas
> > >
> > > >
> > > > Regards,
> > > > Shantur
> > >
> > > > _______
> > > > 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/GJ4AQHJ6SIAT7ML526SSO7IKRTY2BHCQ/
> > >
> > >
> > > --
> > > Tomáš Golembiovský 
> >
> > --
> > Tomáš Golembiovský 
> >
> >

-- 
Tomáš Golembiovský 
___
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/47KRWMTCNDHZ3V6SGMHMIQ5NZYN7QHZR/

[ovirt-users] Re: Reset NVRAM

[Tomáš Golembiovský]

On Mon, Mar 15, 2021 at 04:43:20PM +0100, Tomáš Golembiovský wrote:
> On Mon, Mar 15, 2021 at 01:13:10PM +, Shantur Rathore wrote:
> > Hi all,
> > 
> > I am doing some testing with GPU passthrough to VMs and in some cases the
> > OVMF stops booting after a GPU passthrough.
> > I have figured out that it's related to some state stored in NVRAM by OVMF
> > and as soon as I create another VM with the same disks it starts booting up.
> > 
> > I believe oVirt saves the NVRAM state.
> 
> No it isn't. Or, better said, it wasn't. Storing of NVRAM is a new
> feature in 4.4.5 and it will be enabled only for VMs with Secure Boot.
> 
> So whatever you're experiencing is probably caused by something else.

Actually I hit "Send" too quickly. Are you experiencing the issue after
VM reboot or even after shutdown? Because NVRAM is kept between reboots
and is removed only after VM shutdown.

Tomas

> 
> >  Is there a way to clear NVRAM for a VM without deleting it?
> 
> This is not part of the feature introduced in 4.4.5. But it would make
> sense to have it if we later extend the NVRAM storing to all VMs with
> UEFI. So despite what I wrote above it would be worth opening a feature
> request bug.
> 
> Tomas
> 
> > 
> > Regards,
> > Shantur
> 
> > ___
> > 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/GJ4AQHJ6SIAT7ML526SSO7IKRTY2BHCQ/
> 
> 
> -- 
> Tomáš Golembiovský 

-- 
Tomáš Golembiovský 
___
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/CM6IJQI5LIVH6OPTWTRPKXITODFYCQUH/

[ovirt-users] Re: Reset NVRAM

[Tomáš Golembiovský]

On Mon, Mar 15, 2021 at 01:13:10PM +, Shantur Rathore wrote:
> Hi all,
> 
> I am doing some testing with GPU passthrough to VMs and in some cases the
> OVMF stops booting after a GPU passthrough.
> I have figured out that it's related to some state stored in NVRAM by OVMF
> and as soon as I create another VM with the same disks it starts booting up.
> 
> I believe oVirt saves the NVRAM state.

No it isn't. Or, better said, it wasn't. Storing of NVRAM is a new
feature in 4.4.5 and it will be enabled only for VMs with Secure Boot.

So whatever you're experiencing is probably caused by something else.

>  Is there a way to clear NVRAM for a VM without deleting it?

This is not part of the feature introduced in 4.4.5. But it would make
sense to have it if we later extend the NVRAM storing to all VMs with
UEFI. So despite what I wrote above it would be worth opening a feature
request bug.

Tomas

> 
> Regards,
> Shantur

> ___
> 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/GJ4AQHJ6SIAT7ML526SSO7IKRTY2BHCQ/


-- 
Tomáš Golembiovský 
___
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/ZL6MWWUCU3IOCXYLXZI2YGTR26GH66OS/

[ovirt-users] Re: Newly uploaded disk stuck in 'Finalizing Failure' status

[Tomáš Golembiovský]

On Wed, Mar 03, 2021 at 09:08:25AM -, n.bouwh...@speakup.nl wrote:
> Hey there, 
> 
> A few days ago, I tried to create a new template using one of the Ansible 
> playbooks I frequently use. This time, the upload of the disk failed, 
> possibly due to an unrelated error.
> 
> The disk is now stuck in Ovirt. It has the status 'Finalizing Failure' and 
> it's locked, thus I cannot remove it. Trying to unlock the disk with the 
> 'unlock_entity.sh' helper utility does not help. The utility says it has 
> completed it task successfully but the disk remains in this state.
> 

I don't know if it will still work after running the unlock tool, but
normally you should be able to cancel the operation (Storage -> Disks ->
Transfer -> Cancel). Or was that operation grayed out?

Tomas

> I decided to check the logs, and see that `engine.log` gets spammed with 
> these lines every 10 seconds
> 
> ```
> 2021-03-03 09:05:38,335Z WARN  
> [org.ovirt.engine.core.bll.storage.disk.image.TransferDiskImageCommand] 
> (EE-ManagedScheduledExecutorService-engineScheduledThreadPool-Thread-45) 
> [redacted] Failed to stop image transfer session. Ticket does not exist for 
> image '[disk uuid]'
> ```
> 
> How can I force Ovirt to remove this disk?
> 
> I presume the upload failure itself is a different error, possibly related to 
> our setup. Hence this is not the topic of this thread. I just want to know 
> how I can remove these disks.
> 
> Thanks,
> Nick
> ___
> 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/OE5DYCK67D2UROV4UJS5ZX3ARRVXNDAX/

-- 
Tomáš Golembiovský 
___
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/H5UAVUWVOJ3AOQE27KOEJN2RPOL3DNMY/

[ovirt-users] Re: ovirt guest agent ubuntu 16.04.6 LTS

[Tomáš Golembiovský]

https://www.ovirt.org/community/about/community-guidelines/
> >> List Archives:
> >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/GKJLH7EKUPHCHIUBYSYPX7RU7FSMG35N/
> >>
> >
> >
> > --
> >
> > Sandro Bonazzola
> >
> > MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> >
> > Red Hat EMEA <https://www.redhat.com/>
> >
> > sbona...@redhat.com
> > <https://www.redhat.com/>
> >
> >
> >
> > *Red Hat respects your work life balance. Therefore there is no need to
> > answer this email out of your office hours.
> > <https://mojo.redhat.com/docs/DOC-1199578>*
> >
> >
> > * <https://www.redhat.com/it/forums/emea/italy-track>*
> >
> >
> 
> -- 
> 
> Sandro Bonazzola
> 
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> 
> Red Hat EMEA <https://www.redhat.com/>
> 
> sbona...@redhat.com
> <https://www.redhat.com/>
> 
> *Red Hat respects your work life balance. Therefore there is no need to
> answer this email out of your office hours.
> <https://mojo.redhat.com/docs/DOC-1199578>*
> 
> 
> * <https://www.redhat.com/it/forums/emea/italy-track>*

-- 
Tomáš Golembiovský 
___
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/CIALOBFTTMC5GAXTNARTEFI4ELZKDLKU/

[ovirt-users] Re: All Windows vms report "Actual timezone in guest doesn't match configuration"

[Tomáš Golembiovský]

On Tue, 07 May 2019 13:43:03 -
mich...@wanderingmad.com wrote:

> I wonder if it's something that has changed in server 2016 / server 2019?  I 
> haven't loaded server 2012 in over a year.

I tried also with Windows 10 (not Server I admit) and EST timezone
worked for me.

-- 
Tomáš Golembiovský 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/MM4KNILDG2HAOGMTLM6MUGXI7RDFE3NL/

[ovirt-users] Re: All Windows vms report "Actual timezone in guest doesn't match configuration"

[Tomáš Golembiovský]

On Sat, 4 May 2019 09:56:23 +0300
Alex K  wrote:

> On Sat, May 4, 2019, 01:26  wrote:
> 
> > I wonder if the older agent would fix it?  I think this issue started with
> > 4.2.2
> >  
> I am having this issue since 4.1.x. it seems to be related with the way
> windows reports timezones and how agent expects them.

Could you guys report:

- version of guest tools installed
- version of the OS
- time zone settings in VM options
- time zone settings in the guest OS
- time zone displayed in 'Guest Info' tab
- guestTimezone object in the output of the command: vdsm-client Host 
getAllVmStats

Tomas

> 
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/CY4DA2TIVFK24UDDXH5UBWYX5G3OQHLM/
> >  


-- 
Tomáš Golembiovský 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/5I2FSC44DERWYK7IGKC6K2VYBW2LCCQZ/

[ovirt-users] Re: All Windows vms report "Actual timezone in guest doesn't match configuration"

[Tomáš Golembiovský]

On Tue, 30 Apr 2019 03:02:30 -
eshwa...@gmail.com wrote:

> Seeing the same thing here.  The Windows 2012R2 VM is set to "(GMT -05:00) US 
> Eastern Standard Time", the guest agent is reporting "Eastern Daylight Time 
> (UTC--04:-00)" (the second - is probably because it word wraps after UTC), 
> and Windows 2012R2 is set to "(UTC -05:00) Eastern Time (US & Canada)". 

I tried that and it works OK for me on Windows 2012R2. The timezone from
guest is reported as 'Eastern Standard Time'. For you however it sends
'Eastern Daylight Time'. I wonder if it is caused be some localization/time
setting in your guest.

Tomas

-- 
Tomáš Golembiovský 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/LOB5VSRYR7THGZ2XJMMYHCBHBT5IPCBI/

[ovirt-users] Re: ovirt-guest-agent running on Debian vm, but data doesn't show in web-gui

[Tomáš Golembiovský]

On Thu, 20 Sep 2018 14:37:39 +0200
Sandro Bonazzola  wrote:

> Il giorno gio 20 set 2018 alle ore 14:30 Arild Ringøy 
> ha scritto:
> 
> > Hello Sandro!
> >
> > I'll do that. What logs would be best to attach?
> >  
> 
> Tomas can you help here?

Please enable debug logs on VDSM host. Then stop / start the VM (don't
reboot!) and share vdsm.log from the host.

Tomas
> 
> 
> >
> > Regards
> > Arild
> > ___
> > Users mailing list -- users@ovirt.org
> > To unsubscribe send an email to users-le...@ovirt.org
> > Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> > oVirt Code of Conduct:
> > https://www.ovirt.org/community/about/community-guidelines/
> > List Archives:
> > https://lists.ovirt.org/archives/list/users@ovirt.org/message/IPJCRDYZPZZPLPF35VSJ3XFUI4ZHRSR7/
> >  
> 
> 
> -- 
> 
> SANDRO BONAZZOLA
> 
> MANAGER, SOFTWARE ENGINEERING, EMEA R RHV
> 
> Red Hat EMEA <https://www.redhat.com/>
> 
> sbona...@redhat.com
> <https://red.ht/sig>
> <https://www.redhat.com/en/events/red-hat-open-source-day-italia?sc_cid=701f200RgRyAAK>


-- 
Tomáš Golembiovský 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2Q7Q6TOSPC2AQAXUWFBOUJX6JTV5QWFP/

[ovirt-users] Re: Windows 10 & 2016 snapshot error

[Tomáš Golembiovský]

Based on the IRC discussion it seems to me as a bug in Engine. But we
will need more information to tackle that. Please open a bug on
ovirt-engine.

Please also enable debug logs in VDSM and attach engine.log and vdsm.log
from the time the VM started to the time of the snapshot.

Thanks,

Tomas


-- 
Tomáš Golembiovský 
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/BTCV7SRJ6BDK4OPQN4SLV2GQVUYDGVXJ/

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

[Tomáš Golembiovský]

2:
> > (a) qemu-img convert produces a 'temporary' collapsed volume
> > (b) make a tar file of the OVf configuration and that 'temporary' volume
> > (c) delete the temporary volume
> > 
> > But the fact that we produce that 'temporary' volume obviously slows down
> > the entire operation.
> > It would be much better if we could "open" a stream that we can read from
> > the 'collapsed' form of that chain and stream it directly into the
> > appropriate tar file entry, without extra writes to the storage device.
> > 
> > Few months ago people from the oVirt-storage team checked the qemu toolset
> > and replied that this capability is not yet provided, therefore we
> > implemented the workaround described above. Apparently, the desired ability
> > can also be useful for the flow discussed in this thread so it worth asking
> > for it again :)  
> 
> I think real streaming is unlikely to happen because most image formats
> that QEMU supports aren't made that way. If there is a compelling
> reason, we can consider it, but it would work only with very few target
> formats and as such would have to be separate from existing commands.
> 
> As for OVA files, I think it might be useful to have a tar block driver
> instead which would allow you to open a file inside a tar archive (you
> could then also directly run an OVA without extracting it first). We
> probably wouldn't be able to support resizing images there, but that
> should be okay.

That's something you can do with offset/size options too. In fact, that
was main reason for adding it so that virt-v2v can convert OVAs without
extracting them.

Having a layer that understands tar format and would supply offset/size
for you would be neat.

> If you can create a tar file that reserves space for the image file
> without actually writing it, a possible workaround today would be using
> the offset/size runtime options of the raw driver to convert directly
> into a region inside the tar archive.

Not easy to do for qcow2 where you don't know how much space you will
actually need.

Tomas

> 
> Kevin
> ___
> Users mailing list -- users@ovirt.org
> To unsubscribe send an email to users-le...@ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct: 
> https://www.ovirt.org/community/about/community-guidelines/
> List Archives: 
> https://lists.ovirt.org/archives/list/users@ovirt.org/message/EWEKAIIDE3SYAZVTGBVPSUJJQGNXQAVN/


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: 
https://www.ovirt.org/community/about/community-guidelines/
List Archives: 
https://lists.ovirt.org/archives/list/users@ovirt.org/message/2W4O3GEXHBOL6MCYK2L3F2DYL2YJEQQQ/

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

[Tomáš Golembiovský]

On Fri, 25 May 2018 12:13:33 +
"Vrgotic, Marko" <m.vrgo...@activevideo.com> wrote:

> 
> 
> On 25/05/2018, 12:29, "Tomáš Golembiovský" <tgole...@redhat.com> wrote:
> 
> Hi,
> 
> On Fri, 25 May 2018 08:11:13 +
> "Vrgotic, Marko" <m.vrgo...@activevideo.com> wrote:
> 
> > Dear Nir, Arik and Richard,
> > 
> > I hope discussion will continue somewhere where i am able to join as 
> watcher at least.
> 
> please open a bug on VDSM. This is something we need to deal with during
> import -- or at least prevent users from importing.
>[Marko] Where? Email to users@ovirt.org? Do you need me to provide 
> more information than in this email or additional information?
Here in Bugzilla: https://bugzilla.redhat.com/enter_bug.cgi?product=vdsm

Including the info you had in your first email should be enough for now.

>If possible, go with "deal with", instead of just 
> preventing. My team very much enjoys oVirt platform and its functionality and 
> we would love to see it grow further, internally and externally.

Could you please elaborate on your specific use-case here? Where did the
backing image came from? Snapshots, use of templates, ...?


> 
> > I have not seen any communication since Nir’s proposal. Please, if 
> possible allow me to somehow track in which direction you are leaning.
> > 
> > In the meantime, as experienced engineers, do you have any suggestion 
> how I could “workaround” current problem?
> > 
> > Rebasing image using qemu-img to remove backing file did not help (VM 
> was able to start, but No Boot Device) and I think now that is due to image 
> having functional dependency of base image.
> 
> What do you mean by rebasing? On which backing image did you rebase it?
>[Marko] It was using unsafe mode - just wanted to see what results 
> will I get if I remove the backing file (inexperienced move). This action 
> result in being able to start the VM, but ending up in No Bootable Device.

I guess you ended up with a disk full of holes in it and boot sector was
one of the missing pieces.

Tomas

> 
> I'm not too familiar with openstack, but I'd suggest doing a 'qemu-img 
> convert' on the disk in openstack to squash the backing change into new (and 
> complete) image, assign this new disk to your VM and import it to oVirt.
> [Marko] Thank you. We will test it and check the result.
> 
> Tomas
> 
> > 
> > Like with VMs in oVrt, where template can not be deleted if there are 
> still VMs existing, which were created from that template.
> > 
> > Please advise
> > 
> > — — —
> > Met vriendelijke groet / Best regards,
> > 
> > Marko Vrgotic
> > Sr. System Engineer
> > ActiveVideo
> > 
> > Tel. +31 (0)35 677 4131
> > email: m.vrgo...@activevideo.com
> > skype: av.mvrgotic.se
> > www.activevideo.com
> > 
> > From: Vrgotic, Marko
> > Sent: Thursday, May 24, 2018 5:26:30 PM
> > To: Nir Soffer
> > Cc: users@ovirt.org; Richard W.M. Jones; Arik Hadas
> > Subject: Re: [ovirt-users] Libvirt ERROR cannot access backing file 
> after importing VM from OpenStack
> > 
> > Dear Nir,
> > 
> > I believe i understand now. The image imported is not base image, but 
> required backing file to be able to work properly.
> > 
> > Maybe silly move, but i have tried to “solve/workaround” around the 
> problem by rebasing image to remove backing file dependency, but it’s clear 
> now why I than saw that “no bootable device found” during imported VM boot.
> > 
> > I support you suggestion to solve the import by either importing 
> complete chain or recreating image so in a way it’s independent from former 
> chain.
> > 
> > If you decide to go this way, please let me know which issue to track 
> and if you need any more data provided from me.
> > 
> > I still need to solve problem with 200+ VM wanting to move to oVirt.
> > 
> > Kindly awaiting further updates.
> > 
> > — — —
> > Met vriendelijke groet / Best regards,
> > 
> > Marko Vrgotic
> > Sr. System Engineer
> > ActiveVideo
> > 
> > Tel. +31 (0)35 677 4131
> > email: m.vrgo...@activevideo.com
> > skype: av.mvrgotic.se
> > www.activevideo.com
> > 
&

[ovirt-users] Re: Libvirt ERROR cannot access backing file after importing VM from OpenStack

[Tomáš Golembiovský]

s='[instance-0673=VM_NAME, 
> 1f0b608f-7cfc-4b27-a876-b5d8073011a1=VM]', sharedLocks=''}'
> 
> 2018-05-24 12:49:28,911+02 INFO  
> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConvertVmVDSCommand] 
> (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [2047673e] START, 
> ConvertVmVDSCommand(HostName = aws-ovhv-01, 
> ConvertVmVDSParameters:{hostId='cbabe1e8-9e7f-4c4b-be9c-49154953564d', 
> url='qemu+tcp://root@172.19.0.12/system<http://root@172.19.0.12/system>', 
> username='null', vmId='1f0b608f-7cfc-4b27-a876-b5d8073011a1', 
> vmName='instance-0673', 
> storageDomainId='2607c265-248c-40ad-b020-f3756454839e', 
> storagePoolId='5a5de92c-0120-0167-03cb-038a', virtioIsoPath='null', 
> compatVersion='null', Disk0='816ac00f-ba98-4827-b5c8-42a8ba496089'}), log id: 
> 53408517
> 
> 2018-05-24 12:49:29,010+02 INFO  
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-commandCoordinator-Thread-2) [2047673e] EVENT_ID: 
> IMPORTEXPORT_STARTING_CONVERT_VM(1,193), Starting to convert Vm 
> instance-0673
> 
> 2018-05-24 12:52:57,982+02 INFO  [org.ovirt.engine.core.bll.UpdateVmCommand] 
> (default task-16) [df1d5f72-eb17-46e4-9946-20ca9809b54c] Failed to Acquire 
> Lock to object 'EngineLock:{exclusiveLocks='[instance-0673=VM_NAME]', 
> sharedLocks='[1f0b608f-7cfc-4b27-a876-b5d8073011a1=VM]'}'
> 
> 2018-05-24 12:59:24,575+02 INFO  
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engineScheduled-Thread-20) [2047673e] EVENT_ID: 
> IMPORTEXPORT_IMPORT_VM(1,152), Vm instance-0673 was imported successfully 
> to Data Center AVEUNL, Cluster AWSEUOPS
> 
> 
> 
> Than trying to start VM fails with following messages:
> 
> 2018-05-24 13:00:32,085+02 INFO  
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-653729) [] EVENT_ID: 
> USER_STARTED_VM(153), VM instance-0673 was started by 
> admin@internal-authz (Host: aws-ovhv-06).
> 
> 2018-05-24 13:00:33,417+02 INFO  
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
> (ForkJoinPool-1-worker-9) [] VM 
> '1f0b608f-7cfc-4b27-a876-b5d8073011a1'(instance-0673) moved from 
> 'WaitForLaunch' --> 'Down'
> 
> 2018-05-24 13:00:33,436+02 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (ForkJoinPool-1-worker-9) [] EVENT_ID: VM_DOWN_ERROR(119), VM 
> instance-0673 is down with error. Exit message: Cannot access backing 
> file '/var/lib/nova/instances/_base/2f4f8c5fc11bb83bcab03f4c829ddda4da8c0bce' 
> of storage file 
> '/rhev/data-center/mnt/glusterSD/aws-gfs-01.awesome.lan:_gv0__he/2607c265-248c-40ad-b020-f3756454839e/images/816ac00f-ba98-4827-b5c8-42a8ba496089/8ecfcd5b-db67-4c23-9869-0e20d7553aba'
>  (as uid:107, gid:107): No such file or directory.
> 
> 2018-05-24 13:00:33,437+02 INFO  
> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] 
> (ForkJoinPool-1-worker-9) [] add VM 
> '1f0b608f-7cfc-4b27-a876-b5d8073011a1'(instance-0673) to rerun treatment
> 
> 2018-05-24 13:00:33,455+02 WARN  
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-653732) [] EVENT_ID: 
> USER_INITIATED_RUN_VM_FAILED(151), Failed to run VM instance-0673 on Host 
> aws-ovhv-06.
> 
> 2018-05-24 13:00:33,460+02 ERROR 
> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] 
> (EE-ManagedThreadFactory-engine-Thread-653732) [] EVENT_ID: 
> USER_FAILED_RUN_VM(54), Failed to run VM instance-0673  (User: 
> admin@internal-authz).
> 
> 
> 
> Checking on the Gluster volume, directory and files exist, permissions are in 
> order:
> 
> 
> 
> [root@aws-ovhv-01 816ac00f-ba98-4827-b5c8-42a8ba496089]
> 
> -rw-rw.  1 vdsm kvm  14G May 24 12:59 8ecfcd5b-db67-4c23-9869-0e20d7553aba
> 
> -rw-rw.  1 vdsm kvm 1.0M May 24 12:49 
> 8ecfcd5b-db67-4c23-9869-0e20d7553aba.lease
> 
> -rw-r--r--.  1 vdsm kvm  310 May 24 12:49 
> 8ecfcd5b-db67-4c23-9869-0e20d7553aba.meta
> 
> 
> 
> Than I have checked image info, and noticed that backing file entry is 
> pointing to non-existing location, which does and should not exist on oVirt 
> hosts:
> 
> 
> 
> [root@aws-ovhv-01 816ac00f-ba98-4827-b5c8-42a8ba496089]# qemu-img info 
> 8ecfcd5b-db67-4c23-9869-0e20d7553aba
> 
> image: 8ecfcd5b-db67-4c23-9869-0e20d7553aba
> 
> file format: qcow2
> 
> virtual size: 160G (171798691840 bytes)
> 
> disk size: 14G
> 
> cluster_size: 65536
> 
> backing file: 
> /var/lib/nova/instances/_base/2f4f8c5fc11bb83bcab03f4c829ddda4da8c0bce
> 
> Format specific information:
> 
> compat: 1.1
> 
> lazy refcounts: false
> 
> refcount bits: 16
> 
> corrupt: false
> 
> 
> 
> Can somebody advise me how to fix, address this, as I am in need of importing 
> 200+ VMs from OpenStack to oVirt?
> 
> Sure this qcow2 file will not work in oVirt.
> 
> I wonder how you did the import?
> 
> Nir
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

[ovirt-users] Re: Serial pass-through on oVirt VMs

[Tomáš Golembiovský]

Take a look at this page [1] for documentation of the hooks system. There
is also an example how to use it to change the XML at the end [2].

Tomas

[1] https://www.ovirt.org/documentation/admin-guide/appe-VDSM_and_Hooks/
[2] 
https://www.ovirt.org/documentation/admin-guide/appe-VDSM_and_Hooks/#vdsm-hook-examples

On Tue, 22 May 2018 15:15:57 +0100
Joshua Blake <maddogmcr...@gmail.com> wrote:

> Hello Tomas,
> 
> Thank you for coming back to me. I don't suppose you have any examples 
> or guides you could point me in the direction of please?
> 
> Kind Regards,
> Joshua Blake
> 
> 
> On 22/05/2018 15:08, Tomáš Golembiovský wrote:
> > Hi,
> >
> > you can try to use VDSM hook to add a dummy serial device to the VM
> > domain XML. Or if you really need a physical device then you can use the
> > hook to add the  element to the domain XML. Don't forget to pin
> > the VM to a specific host though.
> >
> > Hope this helps,
> >
> >  Tomas
> >
> > On Wed, 16 May 2018 10:17:49 +0100
> > Joshua Blake <maddogmcr...@gmail.com> wrote:
> >  
> >> Hello,
> >>
> >> We have an old Windows XP VM, that requires access to a physical serial
> >> port for our telephone system. We have this working in VMWare, however, I'm
> >> not entirely sure how we would set this up in oVirt? Can someone help
> >> please?
> >>
> >> Kind Regards,
> >> Joshua Blake  
> >  
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

[ovirt-users] Re: Serial pass-through on oVirt VMs

[Tomáš Golembiovský]

adding back the list

On Tue, 22 May 2018 16:38:31 +0200
Francesco Romani <from...@redhat.com> wrote:

> On 05/22/2018 04:08 PM, Tomáš Golembiovský wrote:
> > Hi,
> >
> > you can try to use VDSM hook to add a dummy serial device to the VM
> > domain XML. Or if you really need a physical device then you can use the
> > hook to add the  element to the domain XML. Don't forget to pin
> > the VM to a specific host though.
> 
> Yes, pinning is most likely needed. As per libvirt configuration, there
> should be direct libvirt support, maybe predating hostdev:
> 
> https://libvirt.org/formatdomain.html#elementsCharHost
> 
> Bests,
> 
> -- 
> Francesco Romani
> Senior SW Eng., Virtualization R
> Red Hat
> IRC: fromani github: @fromanirh
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

[ovirt-users] Re: Serial pass-through on oVirt VMs

[Tomáš Golembiovský]

Hi,

you can try to use VDSM hook to add a dummy serial device to the VM
domain XML. Or if you really need a physical device then you can use the
hook to add the  element to the domain XML. Don't forget to pin
the VM to a specific host though.

Hope this helps,

Tomas

On Wed, 16 May 2018 10:17:49 +0100
Joshua Blake <maddogmcr...@gmail.com> wrote:

> Hello,
> 
> We have an old Windows XP VM, that requires access to a physical serial
> port for our telephone system. We have this working in VMWare, however, I'm
> not entirely sure how we would set this up in oVirt? Can someone help
> please?
> 
> Kind Regards,
> Joshua Blake


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

[ovirt-users] Re: Mikrotik CHR guest agent

[Tomáš Golembiovský]

Hi,

On Wed, 9 May 2018 09:29:16 +
Magnus Isaksson <mag...@vmar.se> wrote:

> Hello all
> 
> I have installed MikroTik Cloud Hosted Router on my oVirt 4.2 setup
> It starts fine and so but oVirt complains about guest-agent.

oVirt complaints about missing oVirt Guest Agent. I doubt there is a
package for RouterOS.


> At MikroTik this information is available regarding guest-agent
> https://wiki.mikrotik.com/wiki/Manual:CHR#KVM
> 
> But I don't understand what I shall do with that information to get it 
> working.

The page talks about QEMU Guest Agent. We have introduced limited
support for it in oVirt 4.2 and you don't have to do anything besides
checking that it is installed and running.

Unfortunately this will not rid you of the warning about missing agent
in oVirt.

Tomas


> 
> Can somebody help me?
> 
> Regards
> Magnus
> 
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org

Re: [ovirt-users] ovirt-guest-agent for EL6

[Tomáš Golembiovský]

Hi,

On Wed, 11 Apr 2018 15:37:10 -0400
John Nguyen <jtq...@gmail.com> wrote:

> Hi,
> 
> Is there an OVirt 4.2 compatible version on of the ovirt-guest-agent for
> EL6?
> 
> I found the 1.0.13 Package but it doesn't report information to the Web UI.

That's probably because it's not using the new channel name. What
exactly is the version you are installing? If it is from EPEL you need
ovirt-guest-agent-1.0.13-2.el6.

Tomas

> 
> Thanks,
> John


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Failed to Communicate with External Provider QEMU - related to RedHat Bug 1426573

[Tomáš Golembiovský]

On Tue, 17 Apr 2018 13:34:54 +
"Vrgotic, Marko" <m.vrgo...@activevideo.com> wrote:

> If I try to use same proxy host, from command line, I am able to connect, no 
> problems what so ever:
> 
> [root@aws-ovhv-07 vdsm]# virsh -c 
> qemu+ssh://r...@aws-ovhv-08.avinity.tv/system

You need to be running this as 'vdsm' user. See the "Additional info" in
the description of the bug you referenced. Or see the preparatory steps
described in [1]. The documentation is for Xen, but the steps are
analogous for KVM.

Tomas

[1] https://www.ovirt.org/develop/release-management/features/virt/XenToOvirt/

> setlocale: No such file or directory
> The authenticity of host 'aws-ovhv-08.avinity.tv (172.16.81.57)' can't be 
> established.
> ECDSA key fingerprint is SHA256:Ysbp/LvuOCIIvMbT931rwNN9HfBv1dtJpu0uQMi4lrk.
> ECDSA key fingerprint is MD5:14:c0:9c:bf:2b:65:ee:89:10:b8:21:54:57:72:9c:58.
> Are you sure you want to continue connecting (yes/no)? yes
> r...@aws-ovhv-08.avinity.tv's password:
> Welcome to virsh, the virtualization interactive terminal.
> 
> Type:  'help' for help with commands
>'quit' to quit
> 
> virsh # list
> IdName   State
> 
> 2 tm_vpn running
> 3 tmduck running
> 22scsk29funnela  running
> 25scsk29procArunning
> 51scsk211udc1running
> 52scsk211csm1running
> 53scsk211psm1running
> 54scsk211st1 running
> 55tm_admin   running
> 
> virsh #
> 
> Found the related bug (closed) on Red Hat Bugzilla – Bug 1426573
> 
> On the same bug page, workaround suggested is also applicable.


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM guest agent

[Tomáš Golembiovský]

Hi,

On Sun, 11 Mar 2018 22:56:32 +
Nicolas Vaye <nicolas.v...@province-sud.nc> wrote:

> Hello,
> 
> i have installed one oVirt platform with 2 node and 1 HE version 4.2.1.7-1
> 
> It seem to work fine, but i would like more information on the guest agent.
> For the HE, the guest agent seem to be OK, on this vm i 've spotted that the 
> ovirt-guest-agent and qemu-guest-agent are installed.
> 
> I have 2 VM, 1 debian 9 and 1 RHEL 6.5. I've tried to install the same 
> service on each VM, but the result is the same :
> no info about IP, fqdn, or app installed for these vm, and there is a orange 
> ! for each vm on the web ui (indicate that i need to install latest guest 
> agent) .

What version of the guest agent do you have installed on RHEL 6.5?

Tomas

> 
> I have tried different test with spice-vdagent, or ovirt-guest-agent or 
> qemu-guest-agent but no way.
> 
> ovirt-guest-agent doesn't start on debian 9 and RHEL 6.5 :
> MainThread::INFO::2018-03-11 
> 22:46:02,984::ovirt-guest-agent::59::root::Starting oVirt guest 
> agentMainThread::ERROR::2018-03-11 
> 22:46:02,986::ovirt-guest-agent::141::root::Unhandled exception in oVirt 
> guest agent!Traceback (most recent call last):  File 
> "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 135, in 
> agent.run(daemon, pidfile)  File 
> "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run
> self.agent = LinuxVdsAgent(config)  File 
> "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 472, in __init__
> AgentLogicBase.__init__(self, config)  File 
> "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__
> self.vio = VirtIoChannel(config.get("virtio", "device"))  File 
> "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 153, in __init__
> self._stream = VirtIoStream(vport_name)  File 
> "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 134, in __init__
> self._vport = os.open(vport_name, os.O_RDWR)OSError: [Errno 2] No such file 
> or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm'
> 
> 
> Can i have help for this problem ?
> 
> Thanks.
> 
> Nicolas VAYE
> DSI - Nouméa
> NEW CALEDONIA
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM guest agent

[Tomáš Golembiovský]

Hi,

On Mon, 12 Mar 2018 10:48:48 +0100
Oliver Riesener <oliver.riese...@hs-bremen.de> wrote:

> Hi,
> on Debian stretch the problem is the old version of agent from stretch 
> repository.
> I downloaded 1.0.13 from Debian testing repo as *.deb file.
> With these new versions of guest-agent then is also a udev rules issue.
> The serial channels have been renamed and the rules didn`t match for ovirt.

thanks for noticing. I opened a bug on Debian here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893698

Tomas

> See my install script, as attachement.
> Cheers.
> 
> On 11.03.2018 23:56, Nicolas Vaye wrote:
> > Hello,
> >
> > i have installed one oVirt platform with 2 node and 1 HE version 4.2.1.7-1
> >
> > It seem to work fine, but i would like more information on the guest agent.
> > For the HE, the guest agent seem to be OK, on this vm i 've spotted that 
> > the ovirt-guest-agent and qemu-guest-agent are installed.
> >
> > I have 2 VM, 1 debian 9 and 1 RHEL 6.5. I've tried to install the same 
> > service on each VM, but the result is the same :
> > no info about IP, fqdn, or app installed for these vm, and there is a 
> > orange ! for each vm on the web ui (indicate that i need to install latest 
> > guest agent) .
> >
> > I have tried different test with spice-vdagent, or ovirt-guest-agent or 
> > qemu-guest-agent but no way.
> >
> > ovirt-guest-agent doesn't start on debian 9 and RHEL 6.5 :
> > MainThread::INFO::2018-03-11 
> > 22:46:02,984::ovirt-guest-agent::59::root::Starting oVirt guest 
> > agentMainThread::ERROR::2018-03-11 
> > 22:46:02,986::ovirt-guest-agent::141::root::Unhandled exception in oVirt 
> > guest agent!Traceback (most recent call last):  File 
> > "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 135, in   
> >   agent.run(daemon, pidfile)  File 
> > "/usr/share/ovirt-guest-agent/ovirt-guest-agent.py", line 65, in run
> > self.agent = LinuxVdsAgent(config)  File 
> > "/usr/share/ovirt-guest-agent/GuestAgentLinux2.py", line 472, in __init__   
> >  AgentLogicBase.__init__(self, config)  File 
> > "/usr/share/ovirt-guest-agent/OVirtAgentLogic.py", line 188, in __init__
> > self.vio = VirtIoChannel(config.get("virtio", "device"))  File 
> > "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 153, in __init__
> > self._stream = VirtIoStream(vport_name)  File 
> > "/usr/share/ovirt-guest-agent/VirtIoChannel.py", line 134, in __init__
> > self._vport = os.open(vport_name, os.O_RDWR)OSError: [Errno 2] No such file 
> > or directory: '/dev/virtio-ports/com.redhat.rhevm.vdsm'
> >
> >
> > Can i have help for this problem ?
> >
> > Thanks.
> >
> > Nicolas VAYE
> > DSI - Nouméa
> > NEW CALEDONIA
> > _______
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users  
> 
> -- 
> Mit freundlichem Gruß
> 
> 
> Oliver Riesener
> 
> --
> Hochschule Bremen
> Elektrotechnik und Informatik
> Oliver Riesener
> Neustadtswall 30
> D-28199 Bremen
> 
> Tel: 0421 5905-2405, Fax: -2400
> e-mail:oliver.riese...@hs-bremen.de
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] 4.2 downgrade

[Tomáš Golembiovský]

On Sun, 1 Oct 2017 09:53:50 +0300
Yaniv Kaul <yk...@redhat.com> wrote:

> On Sun, Oct 1, 2017 at 3:01 AM, Ryan Mahoney <
> r...@beaconhillentertainment.com> wrote:  
> 
> > I installed from the master repo, should I have used the 42pre repo?
> > Should I add that repo and update to that version, or should I update the
> > master repo every once and awhile?
> >  
> 
> I suggest the latter.

Of course, ultimately, you'll have to switch to the 4.2 repo (when that
becomes available), before the master drifts of again and becomes
unstable with code for new features.

Tomas

> Y.
> 
> >
> > On Sat, Sep 30, 2017 at 1:37 PM, Yaniv Kaul <yk...@redhat.com> wrote:
> >  
> >>
> >>
> >> On Sep 30, 2017 8:09 AM, "Ryan Mahoney" <r...@beaconhillentertainment.com>
> >> wrote:
> >>
> >> Accidentally upgraded a 4.0 environment to 4.2 (didn't realize the
> >> "master" repo was development repo).  What's my chances/best way if
> >> possible to roll back to 4.0 (or 4.1 for that matter).
> >>
> >>
> >> There is no roll back to oVirt installation.
> >> That being said, I believe the Alpha quality is good. It is not feature
> >> complete and we of course have more polishing to do, but it's very usable
> >> and we will continue to ship updates to it. Let us know promptly what
> >> issues you encounter.
> >> Y.
> >>
> >>
> >> ___
> >> Users mailing list
> >> Users@ovirt.org
> >> http://lists.ovirt.org/mailman/listinfo/users
> >>
> >>
> >>  
> >  


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.1 : Can't install guest tools for Zentyal 5.0 (based on ubuntu 16.04 xenial)

[Tomáš Golembiovský]

On Mon, 7 Aug 2017 16:08:00 +0200
"yayo (j)" <jag...@gmail.com> wrote:

> >
> > This is the problem!
> >
> > I looked at the packages for conflict and figured the issue is in gnpug.
> > Zentyal repository contains gnupg version 2.1.15-1ubuntu6 which breaks
> > python-apt <= 1.1.0~beta4.
> >
> >  
> Ok, thank you! Any workaround (something like packege pinning?) to fix this
> problem?

Package pinning is probably not a good idea. I've noticed that there are
some libraries that require gnupg >= 2.x and you would not be able to
install those. They came from Zentyal repo so I assume they might be
essential for some features.

Better workaround is to download newer python-apt from here [1] and
install it manually with dpkg. The guest agent seems to work OK with it.
There's much less chance of breaking something else, also newer
python-apt will be picked-up automatically on upgrades.

Tomas


[1] https://packages.ubuntu.com/yakkety/python-apt

-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.1 : Can't install guest tools for Zentyal 5.0 (based on ubuntu 16.04 xenial)

[Tomáš Golembiovský]

ed packages:
>   xz-utils
> *The following packages will be REMOVED:*
> *  apt apt-utils gnupg gnupg-agent libgpgme11 pinentry-curses

This is the problem!

I looked at the packages for conflict and figured the issue is in gnpug.
Zentyal repository contains gnupg version 2.1.15-1ubuntu6 which breaks
python-apt <= 1.1.0~beta4.


> samba-dsdb-modules ubuntu-minimal zentyal-samba*
> The following NEW packages will be installed:
>   python-apt
> WARNING: The following essential packages will be removed.
> This should NOT be done unless you know exactly what you are doing!
>   apt gnupg (due to apt)
> 0 upgraded, 1 newly installed, 9 to remove and 2 not upgraded.
> Need to get 139 kB of archives.
> After this operation, 8,747 kB disk space will be freed.
> *You are about to do something potentially harmful.*
> *To continue type in the phrase 'Yes, do as I say!'*
> * ?] n*
> Abort
> 
> .
> 
> 
> And this is a BIG problem ... Can I open a bug ? Where?

Agreed.

Open a bug with Zentyal. They broke the packages from Ubuntu and should
fix it themselves. They have to backport newer version of python-apt.
The one from yakkety (1.1.0~beta5) should be good enough to fix the
problem.

In the bug report note that the ovirt-guest-agent from Ubuntu repository
cannot be installed. It is not only related to the package from the
private repo.

Tomas

> 
> > Did you run 'apt-get update' to synchronize the repository content?
> >
> >  
> Yes (see above)


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt 4.1 : Can't install guest tools for Zentyal 5.0 (based on ubuntu 16.04 xenial)

[Tomáš Golembiovský]

Hi,

I just tried that with development version of Zentyal and it works for
me. Well, there are some caveats, see below.


On Fri, 4 Aug 2017 09:31:22 -0400
Wesley Stewart <wstewa...@gmail.com> wrote:

> Just wanted to add my input.  I just recently noticed the same thing.
> Luckily i was just testing Zentyal, but when I installed python-apt after
> reading the error message, apt seemed to completely break.  I would be
> curious on a workaround/fix for this as well.

Could you be more specific? What was the problem? Was it problem with
python-apt per-se or with ovirt-guest-agent using python-apt?


> 
> 
> On Fri, Aug 4, 2017 at 9:28 AM, yayo (j) <jag...@gmail.com> wrote:
> 
> > Hi all,
> >
> > I have this problem: I'm tring to install the guest tools following this
> > guide: https://www.ovirt.org/documentation/how-to/guest-
> > agent/install-the-guest-agent-in-ubuntu/#for-ubuntu-1604

I've noticed that the ovirt-guest-agent package available in the
repository mentioned on the oVirt site is missing dependency on
qemu-guest-agent. You have to install it additionally for oVirt to work
properly.

If you, however, instal the ovirt-guest-agent from official Ubuntu
repository there is different issue. There is this unresolved bug:

https://bugs.launchpad.net/ubuntu/+source/ovirt-guest-agent/+bug/1609130

You have to fix permissions on /var/log/ovirt-guest-agent as mentioned
in the bug report.


> >
> > This is the sources:
> >
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial main restricted
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial-updates main restricted
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial universe
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial-updates universe
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial multiverse
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial-updates multiverse
> > deb http://it.archive.ubuntu.com/ubuntu/ xenial-backports main restricted
> > universe multiverse
> >
> > deb http://archive.zentyal.org/zentyal 5.0 main extra
> >
> > deb http://security.ubuntu.com/ubuntu xenial-security main restricted
> > deb http://security.ubuntu.com/ubuntu xenial-security universe
> > deb http://security.ubuntu.com/ubuntu xenial-security multiverse
> >
> >
> > But when I try to install, I have this error:
> >
> >
> > root@vmdczen01:~# apt-get install ovirt-guest-agent
> > Reading package lists... Done
> > Building dependency tree
> > Reading state information... Done
> > Some packages could not be installed. This may mean that you have
> > requested an impossible situation or if you are using the unstable
> > distribution that some required packages have not yet been created
> > or been moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> >  ovirt-guest-agent : Depends: python-apt but it is not going to be
> > installed
> > E: Unable to correct problems, you have held broken packages.
> >
> >
> > I've found that python-apt is in "main" repo:
> >
> >
> > https://packages.ubuntu.com/xenial/amd64/python-apt/download
> >
> >
> > So, what's the problem?

Did you run 'apt-get update' to synchronize the repository content?


Tomas

> >
> >
> > Can you help me?
> > Thank you
> >
> >
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >
> >  


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 2016 Sysprep - Fixed IP

[Tomáš Golembiovský]

On Thu, 27 Jul 2017 04:30:16 -0500
Sven Achtelik <sven.achte...@eps.aero> wrote:

> OK, and would that answer file pick up the fields from the GUI or would I 
> have to set everything in that answer file ? 

No it would not. You have to set everything you want in your answer file.

Tomas

> 
> -Ursprüngliche Nachricht-
> Von: Tomáš Golembiovský [mailto:tgole...@redhat.com] 
> Gesendet: Donnerstag, 27. Juli 2017 11:28
> An: Sven Achtelik <sven.achte...@eps.aero>
> Cc: users@ovirt.org
> Betreff: Re: [ovirt-users] Windows 2016 Sysprep - Fixed IP
> 
> Hi,
> 
> On Wed, 26 Jul 2017 09:02:45 -0500
> Sven Achtelik <sven.achte...@eps.aero> wrote:
> 
> > Hi All,
> > 
> > I'm looking into configuring a Windows 2016 Template via Run Once to have 
> > an static IP. Is there any way to do that ? Maybe over the Sysrep Section ? 
> > I didn't find an answer about how to use it or what syntax should be used ? 
> > Must I put a complete answer file into it or will this section on overwrite 
> > specific parts of the original file that resides on the engine ?  
> 
> You have to put there complete answer file. The XML templates on engine are 
> not used in this case.
> 
> Although, I'm not sure if you can set IP address through the answer file.
> 
> Tomas
> 
> > 
> > Thank you,
> > Sven  
> 
> 
> --
> Tomáš Golembiovský <tgole...@redhat.com>


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 2016 Sysprep - Fixed IP

[Tomáš Golembiovský]

Hi,

On Wed, 26 Jul 2017 09:02:45 -0500
Sven Achtelik <sven.achte...@eps.aero> wrote:

> Hi All,
> 
> I'm looking into configuring a Windows 2016 Template via Run Once to have an 
> static IP. Is there any way to do that ? Maybe over the Sysrep Section ? I 
> didn't find an answer about how to use it or what syntax should be used ? 
> Must I put a complete answer file into it or will this section on overwrite 
> specific parts of the original file that resides on the engine ?

You have to put there complete answer file. The XML templates on engine
are not used in this case.

Although, I'm not sure if you can set IP address through the answer file.

Tomas

> 
> Thank you,
> Sven


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Libguestfs] virt-v2v import from KVM without storage-pool ?

[Tomáš Golembiovský]

Hi,

this is different from the original problem. The original description
had "" whereas the BZ addresses "" which is not supported at all.

Tomas

On Fri, 7 Jul 2017 13:02:45 +0100
"Richard W.M. Jones" <rjo...@redhat.com> wrote:

> On Fri, Jul 07, 2017 at 01:31:38PM +0200, Tomáš Golembiovský wrote:
> > Hi,
> > 
> > yes it is an issue in VDSM. We count on the disks being in storage pool
> > (except for block devices).
> > 
> > Can you open a BZ bug for that please.  
> 
> Is this the same thing?
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1468509
> 
> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> Fedora Windows cross-compiler. Compile Windows programs, test, and
> build Windows installers. Over 100 libraries supported.
> http://fedoraproject.org/wiki/MinGW


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [Libguestfs] virt-v2v import from KVM without storage-pool ?

[Tomáš Golembiovský]

Hi,

yes it is an issue in VDSM. We count on the disks being in storage pool
(except for block devices).

Can you open a BZ bug for that please.

Thanks,

Tomas


On Fri, 7 Jul 2017 02:52:26 -0400 (EDT)
Ming Xie <m...@redhat.com> wrote:

> I could reproduce customer's problem
> 
> Packages:
> rhv:4.1.3-0.1.el7
> vdsm-4.19.20-1.el7ev.x86_64
> virt-v2v-1.36.3-6.el7.x86_64
> libguestfs-1.36.3-6.el7.x86_64
> 
> Steps:
> 1.Prepare a guest which is not listed storage pool
> # virsh dumpxml avocado-vt-vm1
> 
>
>   
>   
>   
>function='0x0'/>
> 
> .
> 2.Try to import this guest in rhv4.1 from KVM host but failed to import the 
> guest as screenshot and get error info from vdsm.log
> 
> 2017-07-07 14:41:22,176+0800 ERROR (jsonrpc/6) [root] Error getting disk size 
> (v2v:1089)
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 1078, in 
> _get_disk_info
> vol = conn.storageVolLookupByPath(disk['alias'])
>   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4555, in 
> storageVolLookupByPath
> if ret is None:raise libvirtError('virStorageVolLookupByPath() failed', 
> conn=self)
> libvirtError: Storage volume not found: no storage vol with matching path 
> '/root/RHEL-7.3-x86_64-latest.qcow2'
> 
> 
> 
> 3.Try to convert this guest to rhv by virt-v2v on v2v conversion server,could 
> import the guest from export domain to data domain on rhv4.1 after finishing 
> conversion
> # virt-v2v avocado-vt-vm1 -o rhv -os 10.73.131.93:/home/nfs_export
> [   0.0] Opening the source -i libvirt avocado-vt-vm1
> [   0.0] Creating an overlay to protect the source from being modified
> [   0.4] Initializing the target -o rhv -os 10.73.131.93:/home/nfs_export
> [   0.7] Opening the overlay
> [   6.1] Inspecting the overlay
> [  13.8] Checking for sufficient free disk space in the guest
> [  13.8] Estimating space required on target for each disk
> [  13.8] Converting Red Hat Enterprise Linux Server 7.3 (Maipo) to run on KVM
> virt-v2v: This guest has virtio drivers installed.
> [  52.2] Mapping filesystem data to avoid copying unused and blank areas
> [  52.4] Closing the overlay
> [  52.7] Checking if the guest needs BIOS or UEFI to boot
> [  52.7] Assigning disks to buses
> [  52.7] Copying disk 1/1 to 
> /tmp/v2v.Zzc4KD/c9cfeba7-73f8-428a-aa77-9a2a1acf0063/images/c8eb039e-3007-4e08-9580-c49da8b73d55/f76d16ea-5e66-4987-a496-8f378b127986
>  (qcow2)
> (100.00/100%)
> [ 152.4] Creating output metadata
> [ 152.6] Finishing off
> 
> 
> Result:
> So this problem is caused by vdsm or ovirt
> 
> Regards
> Ming Xie
> 
> - Original Message -
> From: "Richard W.M. Jones" <rjo...@redhat.com>
> To: "Matthias Leopold" <matthias.leop...@meduniwien.ac.at>
> Cc: users@ovirt.org, libgues...@redhat.com
> Sent: Wednesday, July 5, 2017 9:15:16 PM
> Subject: Re: [Libguestfs] virt-v2v import from KVM without storage-pool ?
> 
> On Wed, Jul 05, 2017 at 11:14:09AM +0200, Matthias Leopold wrote:
> > hi,
> > 
> > i'm trying to import a VM in oVirt from a KVM host that doesn't use
> > storage pools. this fails with the following message in
> > /var/log/vdsm/vdsm.log:
> > 
> > 2017-07-05 09:34:20,513+0200 ERROR (jsonrpc/5) [root] Error getting
> > disk size (v2v:1089)
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 1078, in
> > _get_disk_info
> > vol = conn.storageVolLookupByPath(disk['alias'])
> >   File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4770,
> > in storageVolLookupByPath
> > if ret is None:raise libvirtError('virStorageVolLookupByPath()
> > failed', conn=self)
> > libvirtError: Storage volume not found: no storage vol with matching path
> > 
> > the disks in the origin VM are defined as
> > 
> > 
> >   
> >   
> > 
> > 
> >   
> >   
> > 
> > is this a virt-v2v or oVirt problem?  
> 
> Well the stack trace is in the oVirt code, so I guess it's an oVirt
> problem.  Adding ovirt-users mailing list.
> 
> Rich.
> 
> -- 
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-df lists disk usage of guests without needing to install any
> software inside the virtual machine.  Supports Linux and Windows.
> http://people.redhat.com/~rjones/virt-df/
> 
> ___
> Libguestfs mailing list
> libgues...@redhat.com
> https://www.redhat.com/mailman/listinfo/libguestfs


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ovirt-guest-agent - Ubuntu 16.04

[Tomáš Golembiovský]

Hi Fernando,

this seems to be a bug in python-ethtool package (or the ethtool library). I
have opened a bug report for Ubuntu here:

https://bugs.launchpad.net/ubuntu/+source/python-ethtool/+bug/1702437

Hope this helps,

Tomas


On Tue, 4 Jul 2017 11:26:48 -0300
FERNANDO FREDIANI <fernando.fredi...@upx.com> wrote:

> I am still getting problems with ovirt-guest-agent on Ubuntu machines in 
> any scenario, new or upgraded instalation.
> 
> One of the VMs has been upgraded to Ubuntu 17.04 (zesty) and the 
> upgraded version of ovirt-guest-agent also doesn't start due something 
> with python.
> 
> When trying to run it manually with: "/usr/bin/python 
> /usr/share/ovirt-guest-agent/ovirt-guest-agent.py" I get the following 
> error:
> root@hostname:~# /usr/bin/python 
> /usr/share/ovirt-guest-agent/ovirt-guest-agent.py
> *** stack smashing detected ***: /usr/bin/python terminated
> Aborted (core dumped)
> 
> Tried also to install the previous version (16.04) from evilissimo but 
> doesn't work either.
> 
> Fernando
> 
> 
> On 30/06/2017 06:16, Sandro Bonazzola wrote:
> > Adding Laszlo Boszormenyi (GCS) <g...@debian.org 
> > <mailto:g...@debian.org>> which is the maintainer according to 
> > http://it.archive.ubuntu.com/ubuntu/ubuntu/ubuntu/pool/universe/o/ovirt-guest-agent/ovirt-guest-agent_1.0.13.dfsg-1.dsc
> >  
> >
> >
> > On Wed, Jun 28, 2017 at 5:37 PM, FERNANDO FREDIANI 
> > <fernando.fredi...@upx.com <mailto:fernando.fredi...@upx.com>> wrote:
> >
> > Hello
> >
> > Is the maintainer of ovirt-guest-agent for Ubuntu on this mail list ?
> >
> > I have noticed that if you install ovirt-guest-agent package from
> > Ubuntu repositories it doesn't start. Throws an error about python
> > and never starts. Has anyone noticied the same ? OS in this case
> > is a clean minimal install of Ubuntu 16.04.
> >
> > Installing it from the following repository works fine -
> > 
> > http://download.opensuse.org/repositories/home:/evilissimo:/ubuntu:/16.04/xUbuntu_16.04
> > 
> > <http://download.opensuse.org/repositories/home:/evilissimo:/ubuntu:/16.04/xUbuntu_16.04>
> >
> > Fernando
> >
> > ___
> > Users mailing list
> > Users@ovirt.org <mailto:Users@ovirt.org>
> > http://lists.ovirt.org/mailman/listinfo/users
> > <http://lists.ovirt.org/mailman/listinfo/users>
> >
> >
> >
> >
> > -- 
> >
> > SANDRO BONAZZOLA
> >
> > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R
> >
> > Red Hat EMEA <https://www.redhat.com/>
> >
> > <https://red.ht/sig>
> > TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
> >  
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] vm shutdown long delay is a problem for users of pools

[Tomáš Golembiovský]

Hi,

On Wed, 28 Jun 2017 12:05:46 +0200
"Paul" <p...@kenla.nl> wrote:

> Hi Sharon,
> 
> Thanks for your comments. My findings on those:
> 
> 1.   Yes all VMs have ovirt-guest-agent installed and active, shutdown 
> time is still about 90 seconds. Any other way to reduce this? I see in the 
> logs “Jun 28 11:49:03 pool python: Shutdown scheduled for Wed 2017-06-28 
> 11:50:03 CEST, use 'shutdown -c' to cancel.” And then a wait of 60 seconds. 
> Is it possible to adjust this delay?

I've got good news for you... and, of course, some not so good news...

The delay can be configured in engine by engine-config. The
corresponding value is 'VmGracefulShutdownTimeout' and is in seconds
(default is 30 seconds). I.e. you can run the following to disable the
delay. 

# engine-config --set VmGracefulShutdownTimeout=0  

The not so good news is that on linux (which is your case if I
understood correctly) the delay only works by minutes and the value of
VmGracefulShutdownTimeout is rounded *up* to whole minutes. That is
anything between 1-59 seconds is turned into 60 seconds.   

Hope that helps,

Tomas

> 
> 2.   Clicking twice works. Thanks for the tip!
> 
> 3.
> 
> a.   More VMs per user: yes, could be a good option
> 
> b.  I have some trouble with the “console disconnect action” and filed a 
> bug for it last week [1]. Any disconnect action (except shutdown) combined 
> with “strict user checking” (security wise recommended) blocks and depletes 
> pool resources and in my opinion jeopardizes the pool functionality. I am 
> curious what your thoughts are on this.
> 
> Kind regards,
> 
> Paul
> 
> [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1464396
> 
>  
> 
> From: Sharon Gratch [mailto:sgra...@redhat.com] 
> Sent: dinsdag 27 juni 2017 19:04
> To: Paul <p...@kenla.nl>
> Cc: users <users@ovirt.org>
> Subject: Re: [ovirt-users] vm shutdown long delay is a problem for users of 
> pools
> 
>  
> 
> Hi,
> 
> Please see comments below.
> 
>  
> 
> On Thu, Jun 22, 2017 at 7:15 PM, Paul <p...@kenla.nl <mailto:p...@kenla.nl> > 
> wrote:
> 
> Hi,
> 
> Shutting down VM’s in the portal with the red downfacing arrow takes quite 
> some time (about 90 seconds). I read this is mainly due to a 60 second delay 
> in the ovirt-guest-agent. I got used to right-click and use “power off” 
> instead of “shutdown”, which is fine.
> 
>  
> 
> My users make use of VM in a VM-pool. They get assigned a VM and after 
> console disconnect the VM shuts down (default recommended behavior). My issue 
> is that the users stays assigned to this VM for the full 90 seconds and 
> cannot do “power off”. Suppose he disconnected by accident, he has to wait 90 
> seconds until he is assigned to the pool again until he can connect to 
> another VM. 
> 
>  
> 
> My questions are:
> 
> -  Is it possible to decrease the time delay of a VM shutdown? 90 
> seconds is quite a lot, 10 seconds should be enough
> 
> ​​
> 
> ​Is ovirt-guest-agent installed on all pool's VMs? Consider installing 
> ovirt-guest-agent in all VMs in your Pool to decrease the time taken for the 
> VM shutdown. 
> 
>  
> 
> -  Is it possible for normal users to use “power off”?
> 
> ​There is no option in UserPortal to power-off a VM but you can 
> 
> ​try to click twice (sequential clicks) on the 'shutdown' button. Two 
> sequential shutdown requests are handled in oVirt as "power off".
> 
> -  Is it possible to “unallocate” the user from a VM if it is 
> powering down? So he can allocate another VM
> 
> ​You can consider assigning two VMs per each user, if possible of-course (via 
> WebAdmin->edit Pool -> and set "Maximum number of VMs per user" field to "2") 
> so that way while one VM is still shutting down, the user can switch and 
> connect to a second VM without waiting.
> 
> Another option is to create a pool with a different policy for console 
> disconnecting so that the VM won't shutdown each time the user close the  
> console (via WebAdmin->Pool->Console tab->"Console Disconnect Action"). 
> Consider changing this field to "Lock screen" or "Logout user" instead of 
> "shutdown virtual machine". 
> This policy will avoid accidentally console disconnection waiting each 
> time...but on the other hand the VM state will remain as is since no shutdown 
> occurs, so it really depends on your requirements.
> 
> Regards,
> 
> Sharon
> 
>  
> 
> Kind regards,
> 
>  
> 
> Paul
> 
> 
> ___
> Users mailing list
> Users@ovirt.org <mailto:Users@ovirt.org> 
> http://lists.ovirt.org/mailman/listinfo/users
> 
>  
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] "Could not detect Guest Agent on VM"

[Tomáš Golembiovský]

Hi,

sorry for late answer.

On Mon, 12 Jun 2017 11:26:51 -0500
Sven Achtelik <sven.achte...@eps.aero> wrote:

> Hi All,
> 
> I have several Windows VMs (Server 2012, Server 2012 R2) running and the 
> guest tools are installed. IF I go and check the Services in those VMs I can 
> also see the "Ovirt Guest Service" running and the "QEMU Guest Agent" 
> running. Also there is Information about the VM show in the GUI, like 
> installed applications etc.. I've tried several Versions of the tools and 
> even with the latest 4.1.5 I can't get that message to disappear.

First check if the virtio-serial driver is properly installed. In Device
Manager you should see VirtIO Serial Driver in System devices category.

You should also check the oVirt GA log. Search for
ovirt-guest-agent.log, it should be in C:\Windows\SysWOW64. 

> Am I doing something wrong ?
> 
> How does this affect the Backup-API and possible Snapshots are taken for 
> Backups ?

I'm not sure about this one. I don't think we use QEMU GA (or any other
GA) to freeze filesystems. So this feature should not be affected.

Tomas

> 
> If you have any hints please let me know.
> 
> Thank you,
> 
> Sven
> 


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Export VM to ova or ovf format

[Tomáš Golembiovský]

Hi,

On Wed, 31 May 2017 18:14:53 -0400
Brett Holcomb <biholc...@l1049h.com> wrote:

> Is there anyway to export a oVirt VM to an ova or ovf format. Right 
> click export seems to be intended to transfer between oVirt storage 
> domains. There is a project to setup a gui to do this but it's still in 
> the planning stage.

Yes, this is still work in progress. But it is intended only to simplify
transfer of VMs between oVirt instances. It is not guaranteed that the OVA
will work in VMware -- unless VMware produces a conversion tool or
something.

> I've found various references that basically export 
> it to an export domain and then you strip the disk or disks from it, 

Yes that is probably the only way right now. There should be also an OVF
in the export domain -- inside master/vms directory. You can try to
fix the paths to disks and pack it all together to produce an OVA.

But than again, it's questionable whether such OVA will be importable to
VMware.

The OVF specification is too vague and too broad. It does not guarantee
interoperability between various platforms.


> create a VMware workstation VM, and then point it at the new disks you 
> have.  VMware's P2V converter is useless because it only converts Linux 
> machines to an ESXi server which I don't have and once you do that it's 
> another conversion to VMware Workstation.  Guess nobody wants to run 
> Linux on VMware workstation according to VMware.  I'm trying to get some 
> of my critical servers over to VMware Workstation on my Windows Physical 
> box so when I upgrade oVirt I still have my basic network.  I'm running 
> a self-hosted Engine setup with only one Physical server at the moment.
> 
> Thanks.
> 
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Upgrading libguestfs to import debian VM

[Tomáš Golembiovský]

Hi,

On Thu, 6 Apr 2017 12:33:36 +0100
Simon Vincent <s...@srvincent.co.uk> wrote:

> I find that running oVirt 4.1.1 I can not import any debian based VMs as
> virt-v2v/libguestfs is too old.
> This bug report https://bugzilla.redhat.com/show_bug.cgi?id=1362497
> indicates that newer versions of libguestfs support importing debian and
> Ubuntu VMs.

you did not specify what OS are your hosts so I assume it is
RHEL/CentOS. The newer libguestfs is scheduled to appear in 7.4.

AFAIK it should already be available for Fedora 25/26.


> Are there any plans to include a newer version of libguestfs in oVirt soon?
> If I built a newer version of libguestfs on my ovirt-node would it break
> everything?

That should be OK. If you feel brave enough to do that, sure you can
build your own RPMs. You should not need to update anything else
(libvirt/qemu). 


> 
> Regards
> 
> Simon


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Trouble installing windows 10

[Tomáš Golembiovský]

Hi,

On Fri, 17 Mar 2017 18:27:41 +
Jim Fuhr <jf...@shawneetel.com> wrote:

> I'm trying out Ovirt 4.1 and I have it working fine with Linux VMs.  But, 
> when I try to install Windows 10 using the virtio-win drivers for the 
> hard-drive Windows 10 refuses the drivers because they are not signed.  I 
> don't know how tell Windows 10 to ignore the missing signature.

could you tell us where did you get the drivers from? Which package and
what version of the package is that?

Thanks,

    Tomas

-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import from Oracle VM possible?

[Tomáš Golembiovský]

On Thu, 23 Feb 2017 17:49:30 +0100
Gianluca Cecchi <gianluca.cec...@gmail.com> wrote:

> On Thu, Feb 23, 2017 at 5:45 PM, Michal Skrivanek <
> michal.skriva...@redhat.com> wrote:  
> 
> >
> >
> > probably not. We can only talk to libvirt hosts and vCenter
> > I’m not even sure that it would work if you manage to be able to talk to
> > it, we do only support Xen and VMware and generic KVM
> >
> >
> > Gianluca
> >
> >  
> Where can I find the commands it would run via xen+ssh against Xen to get
> VMs and such...?

As Michal mentioned, virt-v2v uses libvirt to access VMs on Xen. So if
you have a ssh connection working then the following is the next thing
that should work:

virsh -c 'xen+ssh://root@oracle_vm_host' list --all

If it doesn't, you're out of luck.

After virt-v2v fetches the relevant information about VM it uses ssh
backend driver in Qemu to copy and modify the disks.

If you want to know more details, you probably should check the virt-v2v
sources.

Tomas

-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] ova conversion errors: where to search?

[Tomáš Golembiovský]

On Tue, 21 Feb 2017 10:09:49 +0200
Shahar Havivi <shav...@redhat.com> wrote:

> Adding Richard.
> 
> On Mon, Feb 20, 2017 at 5:34 PM, Gianluca Cecchi <gianluca.cec...@gmail.com>
> wrote:
> 
> > On Sat, Feb 18, 2017 at 12:42 AM, Tomáš Golembiovský <tgole...@redhat.com>
> > wrote:
> >  
> >>  
> >> >
> >> > where to find more details regarding reasons for failure? Other files on
> >> > engine or should I see at host side?  
> >>
> >> There are two places you should look. One is vdsm.log on the host
> >> performing the import. And if you have oVirt 4.1 another place to look
> >> at is /var/log/vdsm/import where the import logs are stored.
> >>
> >>  
> > Thanks.
> > BTW: the permissions of the ova were ok.
> >
> > I see this text near the end of the file generated into
> > /var/log/vdsm/import
> >
> > libguestfs: trace: v2v: vfs_type = "ext4"
> > [   8.6] Checking for sufficient free disk space in the guest
> > [   8.6] Estimating space required on target for each disk
> > mpstats:
> > mountpoint statvfs /dev/sda2 / (ext4):
> >   bsize=4096 blocks=3650143 bfree=3324165 bavail=3132985
> > estimate_target_size: fs_total_size = 14950985728 [13.9G]
> > estimate_target_size: source_total_size = 19327352832 [18.0G]
> > estimate_target_size: ratio = 0.774
> > estimate_target_size: fs_free = 13615779840 <(361)%20577-9840> [12.7G]
> > estimate_target_size: scaled_saving = 10532706254 [9.8G]
> > estimate_target_size: sda: 8794646578 [8.2G]
> > [   8.6] Converting Ubuntu precise (12.04.5 LTS) to run on KVM
> > virt-v2v: error: virt-v2v is unable to convert this guest type
> > (linux/ubuntu)

This is the core of the issue. Import of Debian based distributions is
not yet available in virt-v2v, unless you want to package it yourself.
Hopefully it should reach users with RHEL/CentOS 7.4 with libguestfs
version 1.36.


> > rm -rf '/var/tmp/ova.vUHL91'
> > rm -rf '/var/tmp/null.LZo6Xr'
> > libguestfs: trace: v2v: close
> > libguestfs: closing guestfs handle 0x1b79170 (state 2)
> >
> > Can we take a sort of generic linux in case? I don't think there could be
> > anything special in Ubuntu... or at least let the admin fix anything trying
> > some resuce operation after the VM has been created.

Unfortunately that is not possible with virt-v2v.

> >
> >  
> >>  
> >> > In case I have to import a windows VM ova, which iso should I attach  
> >> near  
> >> > the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I
> >> > downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is  
> >> the  
> >> > right iso for this.  
> >>
> >> Install virtio-win package somewhere. In it, inside
> >> /usr/share/virtio-win directory, you will find virtio-win-*.iso file.
> >>
> >>  
> > Is virtio-win package still current?

Yes, it is. With 0.1.126 being the latest stable version.

> > In case from where to download it?

You should have this repo in the ovirt-*-dependencies.repo file
installed as part of oVirt.

[virtio-win-stable]
name=virtio-win builds roughly matching what was shipped in latest RHEL
baseurl=http://fedorapeople.org/groups/virt/virtio-win/repo/stable
enabled=1
skip_if_unavailable=1
gpgcheck=0


> > I read here:
> > https://www.ovirt.org/develop/release-management/features/
> > engine/windows-guest-tools/
> > and installied ovirt-guest-tools-iso package that gives:
> >
> > [g.cecchi@ovmsrv05 ~]$ ll /usr/share/ovirt-guest-tools-iso/
> > total 215316
> > -rw-r--r--. 1 root root 220481536 Jan 26 16:13 oVirt-toolsSetup_4.1-3.fc24.
> > iso
> > lrwxrwxrwx. 1 root root31 Feb 20 16:13 ovirt-tools-setup.iso ->
> > oVirt-toolsSetup_4.1-3.fc24.iso

Right, I forgot. Sure, you can use ovirt-guest-tools ISO too.

Tomas

> > [g.cecchi@ovmsrv05 ~]$
> >
> > and mounting as a loop device the iso I have inside it:
> >
> > -r--r--r--.  1 root root  290 Jan 12 17:59 default.ini
> > -r--r--r--.  1 root root  667 Jan 12 17:59 default-logger.ini
> > -r--r--r--.  1 root root 1006 Jan 12 17:59 ovirt-guest-agent.ini
> > -r-xr-xr-x.  1 root root 11659498 Jan 12 17:59 OVirtGuestService.exe
> > -r--r--r--.  1 root root 30836592 Jan 26 16:13 ovirt-guest-tools-setup.exe
> > -r--r--r--.  1 root root  4216840 Aug  2  2016 vcredist_x86.exe
> > dr-xr-xr-x.  2 root root 2048 Jan 26 16:12 vdagent_x64
> > dr-xr-xr-x.  2 root root 2048 Jan 26 16:

Re: [ovirt-users] ova conversion errors: where to search?

[Tomáš Golembiovský]

Hi,

On Fri, 17 Feb 2017 17:54:28 +0100
Gianluca Cecchi <gianluca.cec...@gmail.com> wrote:

> Hello,
> testing some VMware ova imports.
> In a test that I'm doing I get failure in conversion; in engine.log
> 
> 2017-02-17 17:39:02,992+01 INFO
>  [org.ovirt.engine.core.bll.exportimport.ConvertVmCallback]
> (DefaultQuartzScheduler4) [59adde47] Conversion of VM from external
> environment failed: Job u'cdb31877-3ebb-400d-88da-1f645b1261ae' process
> failed exit-code: 1
> 
> where to find more details regarding reasons for failure? Other files on
> engine or should I see at host side?

There are two places you should look. One is vdsm.log on the host
performing the import. And if you have oVirt 4.1 another place to look
at is /var/log/vdsm/import where the import logs are stored.


> In case I have to import a windows VM ova, which iso should I attach near
> the "Attach VirtIO-Drivers" checkbox? Any "official" iso? I
> downloaded oVirt-toolsSetup-4.1-3.fc24.iso but I don't know if it is the
> right iso for this.

Install virtio-win package somewhere. In it, inside
/usr/share/virtio-win directory, you will find virtio-win-*.iso file.


> Thanks,
> Gianluca


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Exporting VM as ova

[Tomáš Golembiovský]

On Tue, 14 Feb 2017 12:23:04 -0500
Derek Atkins <de...@ihtfp.com> wrote:

> Hi,
> 
> Shahar Havivi <shav...@redhat.com> writes:
> 
> > They must have written it - as we did,
> > OVA is representation of current hypervisor virtual machine, it contains OVF
> > which is xml representation of the VM and binary disk files, the files are 
> > the
> > format of the specific hypervisor (Xen, VMWare or KVM).
> > We currently convert from VMWare and Xen on Rhel (not Citrix).
> > The main issue is to convert the disk from one hypervisor to another, we use
> > qemu-img to convert to qcow2 or raw disk format.  
> 
> Can virt-v2v convert back from ovirt format to VMware format?

If you're asking about VM conversion then the answer is no. virt-v2v
converts only to KVM, not the other way around.

If you're asking about the disks then the question is incorrect. The
right tool for this kind of operation is qemu-img. And yes, it can
convert from raw/QCow2 to VMDK.

Tomas

-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] import graylog VM fails

[Tomáš Golembiovský]

Hi,

On Sat, 21 Jan 2017 10:11:59 -0800
Alex R <ar.dig...@gmail.com> wrote:

> Thank you Gianluca.  But that did not work for tying to import the ova's.
> 
> # ls -l /tmp/graylog-2.1.2-1.ova
> -rw-rw. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova

I've looked at the OVA and you're probably hitting this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1371843

but without the vdsm.log it is just a guess. Anyway, this bug should be
fixed in oVirt 4.1.0/4.0.7 and with recent version of virt-v2v
installed.

BUT, you probably still won't be able to import the OVA since it's based
on Ubuntu. Unfortunately virt-v2v with support of Debian based
distributions is not yet readily available.

I'm afraid trying to import the QCOW2 image directly is your best
option.

BTW oVirt 4.0 has support for uploading disk images via the web
interface. That way you can avoid the magic with disk IDs and
conversions. 


Best regards,

Tomas


> I also tried again with the qcow2 image.
> 
> # ls -l /tmp/graylog-2.1.2-1.ova
> -rw-rw. 1 vdsm kvm 1129371648 Jan 15 20:19 /tmp/graylog-2.1.2-1.ova
> 
> I still get the same errors.
> 
> I am suspecting that I am converting the qcows image to the wrong
> location?  How do I know if I have the correct path?
> 
> On Sat, Jan 21, 2017 at 8:20 AM, Gianluca Cecchi <gianluca.cec...@gmail.com>
> wrote:
> 
> > On Sat, Jan 21, 2017 at 2:38 AM, Alex R <ar.dig...@gmail.com> wrote:
> >  
> >>
> >> 1dae7037-73d5-4f11-b7da-c5d1a6aa36b7
> >>
> >> # qemu-img convert -O raw /tmp/graylog-2.1.2-1.qcow2
> >> /rhev/data-center/mnt/blockSD/6643dec0-12b2-4764-9473-a86975
> >> ef523d/images/1dae7037-73d5-4f11-b7da-c5d1a6aa36b7/17a5753
> >> 5-77d1-4b3f-a0b4-a6f9b7717b4a
> >>
> >> I then try to start the VM and get in both the vdsm.log and GUI:
> >>
> >> 2017-01-21T01:06:37.145854Z qemu-kvm: -drive
> >> file=/rhev/data-center/0001-0001-0001-0001-02ad/
> >> 6643dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-
> >> 73d5-4f11-b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-
> >> a6f9b7717b4a,format=raw,if=none,id=drive-virtio-disk0,
> >> serial=1dae7037-73d5-4f11-b7da-c5d1a6aa36b7,cache=none,
> >> werror=stop,rerror=stop,aio=threads: Could not open
> >> '/rhev/data-center/0001-0001-0001-0001-02ad/6643
> >> dec0-12b2-4764-9473-a86975ef523d/images/1dae7037-73d5-4f11-
> >> b7da-c5d1a6aa36b7/17a57535-77d1-4b3f-a0b4-a6f9b7717b4a': Permission
> >> denied
> >> Thread-2666080::INFO::2017-01-20 
> >> 17:06:37,321::vm::1308::virt.vm::(setDownStatus)
> >> vmId=`a1257117-e3f8-4896-9ab4-1b010298f282`::Changed state to Down:
> >> internal error: qemu unexpectedly closed the monitor:
> >> (process:23124): GLib-WARNING **: gmem.c:482: custom memory allocation
> >> vtable not supported.
> >>  
> >
> > Images should be owned by vdsm user and with group kvm and permission 660
> > Is your one ok?
> > HIH,
> > Gianluca
> >  


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] How to pass unattend file to a sysprep Windows 2012r2 template

[Tomáš Golembiovský]

Check the information in this thread:

http://lists.ovirt.org/pipermail/users/2016-December/078251.html

It has the information on how to use 'Run Once' to do the initial run.
Notably, don't forget to add the sysprep floppy!


Best regards,

Tomas

On Thu, 12 Jan 2017 11:14:30 +
Denis Pithon <denis.pit...@gmail.com> wrote:

> Hello oVirt users,
> 
> We currently run about 300 VMs with oVirt, both Linux and Windows servers.
> Cloud init works great for Linux VMs and we would like to do the same for
> Windows. We have a 2012r2 sysprep template but we do not manage to
> configure the initial run such that the new Windows VM boot *and join our
> AD domain* thereafter. Does someone have any clues/informations about this
> kind of operation ? How to specify unattend file in the 'New Virtual
> Machine' ? What kind of data (and format) is required in the 'sysprep'
> field ?
> 
> Best whishes to everyone!
> Denis
> 
> PS: We run oVirt Engine 4.0.5


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Unable to import KVM VM from oVirt web-ui

[Tomáš Golembiovský]

l7.centos.x86_64
> > ovirt-guest-tools-iso-4.0-1.fc23.noarch
> > ovirt-vmconsole-host-1.0.4-1.el7.centos.noarch
> > ovirt-engine-sdk-python-3.6.9.1-1.el7.centos.noarch
> > ovirt-release40-4.0.5-2.noarch
> > libgovirt-0.3.3-4.el7.x86_64
> > ovirt-vmconsole-1.0.4-1.el7.centos.noarch-4.18.15.3-1.el7.centos.x86_64
> >
> > Any help would be greatly appreciated.
> >
> > - George Chlipala
> > ___
> > 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


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import Virtual Machines From Web Admin GUI

[Tomáš Golembiovský]

Forgot to attach the link.

On Thu, 5 Jan 2017 17:01:59 +0100
Tomáš Golembiovský <tgole...@redhat.com> wrote:

> Hi,
> 
> I'm sort of puzzled why you still saw "Host key verification failed" if
> you followed the procedure (or the steps described in [1]).

[1] https://www.ovirt.org/develop/release-management/features/virt/XenToOvirt/

> Only thing I can think of is that you used IP of the KVM host during the
> procedure but then you used hostname in the URL (in import dialog).
> 
> Another possible problem could be that there were two conflicting host
> keys in known_hosts file. But I believe adding "no_verify=1" would not
> help in this case.



-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import Virtual Machines From Web Admin GUI

[Tomáš Golembiovský]

Hi,

I'm sort of puzzled why you still saw "Host key verification failed" if
you followed the procedure (or the steps described in [1]).

Only thing I can think of is that you used IP of the KVM host during the
procedure but then you used hostname in the URL (in import dialog).

Another possible problem could be that there were two conflicting host
keys in known_hosts file. But I believe adding "no_verify=1" would not
help in this case.


Tomas

On Tue, 3 Jan 2017 22:07:42 +
"Beckman, Daniel" <daniel.beck...@ingramcontent.com> wrote:

> To answer my own question: as is often the case, perusing the commercial (RHV 
> 4.0) documentation proved useful.
> 
> The documentation is here:
> https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/paged/virtual-machine-management-guide/612-exporting-and-importing-virtual-machines-and-templates
> 
> However, I kept getting the error “Host key verification failed.: Connection 
> reset by peer”. This despite having followed the official documentation on 
> generating and copying keys, under Procedure 6.2.6 Importing a Virtual 
> Machine from KVM.
> 
> Then I found this article from July 2012 about a different (but similar) 
> scenario:
> 
> https://access.redhat.com/solutions/136463
> 
> What helped was the “alternative test” suggestion. Here is the URI I ended up 
> using with success:
> 
> qemu+ssh://root@MY_KVM_HOST/system?no_verify=1
> 
> Appending “no_verify=1” did the trick. It’s possible that adding hostnames 
> and IPs to /etc/hosts would have also resolved this, but for something 
> performed infrequently (importing a VM from another environment), modifying 
> the URI is easier.
> 
> Best,
> Daniel
> 
> From: <users-boun...@ovirt.org> on behalf of "Beckman, Daniel" 
> <daniel.beck...@ingramcontent.com>
> Date: Tuesday, January 3, 2017 at 9:58 AM
> To: "users@ovirt.org" <users@ovirt.org>
> Subject: [ovirt-users] Import Virtual Machines From Web Admin GUI
> 
> Can anyone point me to a step-by-step guide on getting an import (say, from 
> KVM) to work? I gather it involves some sharing of SSH keys but I haven’t 
> seen it explained in detail. Specifically, what user needs to trust what keys 
> on which machines? The hypervisor hosts? The machine running the engine? 
> Also, some examples of URI paths would be much appreciated.
> 
> Thanks,
> Daniel


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VM config warning

[Tomáš Golembiovský]

Hi,

do you have Guest Agent installed on your Windows machines?

Tomas

On Mon, 5 Dec 2016 08:29:18 +
Andrea Ghelardi <a.ghela...@iontrading.com> wrote:

> Same issue here right after importing my VMs from Ovirt3.5.5 to Ovirt4.0
> All windows server report that OS differs from configuration while all 
> settings seems correct.
> Cheers
> AG
> 
> From: Gary Pedretty [mailto:g...@ravnalaska.net]
> Sent: Sunday, December 04, 2016 00:33
> To: users <users@ovirt.org>
> Subject: [ovirt-users] VM config warning
> 
> When running a Windows 2012 R2 Server VM, why does it report that the OS 
> differs from the Configuration when the selected OS in the config is Windows 
> 2012R2 x64.   Also what is the correct way to do timezones in the config on 
> these VMs, no matter what I pick it reports that Actual Timezone is different 
> in the guest versus the config, when they are both the same.
> 
> 
> Gary


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import from OVA with encrypted root

[Tomáš Golembiovský]

Hi,

unfortunately virt-v2v cannot import VMs with encrypted root file
system. Moreover import of Debian/Ubuntu/Mint guests is not yet
supported by oVirt either. For that you would need development version
of virt-v2v. There are no packages for RHEL/CentOS yet. There should be
packages in Fedora rawhide if you feel brave enough to setup such host
in oVirt (Note: I'm not suggesting you or anyone should do that).


Best regards,

Tomas

On Tue, 8 Nov 2016 10:30:01 -0600
Chris Adams <c...@cmadams.net> wrote:

> I'm trying to import an appliance image from a vendor.  It is based on
> Debian.  For some added level of "security" I guess, the vendor disk
> image has the root filesystem encrypted (and then the key is in the
> initrd - I know that's no real added security, but... whatever).
> 
> Trying to import this VM into oVirt fails because it can't find/mount
> the root filesystem.
> 
> Is there any way around this?
> 
> -- 
> Chris Adams <c...@cmadams.net>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Import of OVA fails in 4.0.4

[Tomáš Golembiovský]

Hi,

On Sat, 5 Nov 2016 17:34:25 -0400
"Derek Atkins" <de...@ihtfp.com> wrote:

> Hi again,
> 
> After a bit more research I found this message in libguestfs[0] that seems
> to imply the issue is related to Fedora 23 in that dracut was moved from
> /sbin to /usr/bin.  Apparently this was fixed in libguestfs on January 28,
> 2016 by a change to convert_linux.ml [1].  But apparently this change
> isn't in the centos-7.2/ovirt-4.0.4 packages?

Yes you're right. That change was not back-ported to the version of
virt-v2v on CentOS 7.2. But if I understand things correctly it should
appear in CentOS 7.3. Is waiting for Centos 7.3 an option for you?


> I just looked through my ovirt host and canot find "convert_linux.ml"
> anywhere, so I have no idea how to actually apply this patch locally.

You can't just patch the code localy (it's not Python). You'd need to
recompile the virt-v2v binary.


> Short term I suppose I can fix this by adding a symlink in the VM and
> repackage the OVA, but it would be nice to actually get this bugfix
> propagated; it's been almost a year?

Adding Richard to the loop.


> Thanks,
> 
> -derek
> 
> [0] https://www.redhat.com/archives/libguestfs/2016-January/msg00138.html
> [1]
> https://github.com/libguestfs/libguestfs/commit/569ad259b4726fbdabf380bdca34da00ca262e1e
> 
> On Sat, November 5, 2016 5:02 pm, Derek Atkins wrote:
> > Hi,
> > I just tried using the OVA import feature in 4.0.4 to import an OVA file
> > created from VMware-Workstation-12.  I packaged the OVA, got it onto my
> > ovirt host, and then go the Admin GUI and under the Virtual Machines tab
> > clicked on Import.  From there I chose Source:  VMware Virtual Appliance
> > (OVA), and selected the (local-to-the-host) path where I put the OVA
> > file.  After clicking Load it displayed the vm name in the window.  I
> > click on that and click the right arrow to and then Next.  Then I select
> > my storage domain to use and continue.  It loads the VM and starts to
> > process it internally with virt-v2v, but then it inexplicably fails.
> > The only message in the GUI is:
> >Failed to import Vm  to Data Center Default, Cluster Default
> >
> > I tried to look into /var/log/vdsm/vdsm.log looking for any errors.  I
> > found this:
> >
> > Thread-88166::ERROR::2016-11-05 16:36:09,219::v2v::674::root::(_run) Job
> > u'cdb1e
> > eb7-63f3-46e8-abd5-5292dcc8809a' failed
> > Traceback (most recent call last):
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 669, in _run
> > self._import()
> >   File "/usr/lib/python2.7/site-packages/vdsm/v2v.py", line 696, in
> > _import
> > self._proc.stderr.read(1024)))
> > V2VProcessError: Job u'cdb1eeb7-63f3-46e8-abd5-5292dcc8809a' process
> > failed exit
> > -code: 1, stderr: virt-v2v: error: unable to rebuild initrd
> > (/boot/initramfs-4.2.6-301.fc23.x86_64.img) because mkinitrd or dracut was
> > not found in the guest
> >
> > If reporting bugs, run virt-v2v with debugging enabled and include the
> > complete output:
> >
> >   virt-v2v -v -x [...]
> >
> > I don't understand this error because /usr/bin/dracut certainly exists
> > in the VM.
> >
> > Anyone have any suggestions on how to get around this?
> >
> > Thanks,
> >
> > -derek
> > --
> >Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
> >Member, MIT Student Information Processing Board  (SIPB)
> >URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
> >warl...@mit.eduPGP key available
> > ___
> > Users mailing list
> > Users@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> >  
> 
> 
> -- 
>Derek Atkins 617-623-3745
>de...@ihtfp.com www.ihtfp.com
>Computer and Internet Security Consultant
> 
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] can't import vm from KVM host

[Tomáš Golembiovský]

Hi Nelson,

I have some bad news. It has turned out Shahar will be gone this week
too. Let us hope then the patch will be ready by the end of next week.


Best regards,

Tomas


On Thu, 20 Oct 2016 15:02:10 +0200
Tomáš Golembiovský <tgole...@redhat.com> wrote:

> Hi.
> 
> On Thu, 20 Oct 2016 14:10:15 +0200 (CEST)
> Nelson Lameiras <nelson.lamei...@lyra-network.com> wrote:
> 
> > Hello,
> > 
> > Any update on this issue?  
> 
> Sorry, no update yet. Unfortunately the guy working on that issue is
> on holidays. He should be back next week.
> 
> > Can I do anything to help?  
>  
> Of course we would appreciate any testing. We'll let you know when the
> updated patch is ready. Hopefully by the end of next week.
> 
> 
> Best regards,
> 
> Tomáš Golembiovský
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] VMware import, username with '.' not accepted

[Tomáš Golembiovský]

Hi,

unfortunately the mentioned bug is related only to DC and Cluster
fields. The problem with dot in user name is still present in oVirt 4.0.

Martijn, can you please open a bug for us?

Thanks,

Tomas


On Mon, 24 Oct 2016 16:33:25 +0200
Martijn Grendelman <martijn.grendel...@isaac.nl> wrote:

> Op 24-10-2016 om 16:06 schreef Michal Skrivanek:
> >> On 24 Oct 2016, at 11:21, Martijn Grendelman <martijn.grendel...@isaac.nl> 
> >> wrote:
> >>
> >> Hi,
> >>
> >> I'm trying to import a VM from VMware. On the "Import Virtual
> >> Machine(s)" screen, my VCenter username is not accepted, because "Name
> >> can only contain 'A-Z', 'a-z', '0-9', '_' or '-' characters" and it
> >> contains a '.', which should be perfectly fine.  
> > What is the exact version?
> > There were improvements in bug 1377271 which is in 4.0.5 RC2  
> 
> This is 4.0.3.
> 
> Thanks,
> Martijn.
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users


-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] can't import vm from KVM host

[Tomáš Golembiovský]

Hi.

On Thu, 20 Oct 2016 14:10:15 +0200 (CEST)
Nelson Lameiras <nelson.lamei...@lyra-network.com> wrote:

> Hello,
> 
> Any update on this issue?

Sorry, no update yet. Unfortunately the guy working on that issue is
on holidays. He should be back next week.

> Can I do anything to help?
 
Of course we would appreciate any testing. We'll let you know when the
updated patch is ready. Hopefully by the end of next week.


Best regards,

Tomáš Golembiovský
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] can't import vm from KVM host

[Tomáš Golembiovský]

Hi,

On Mon, 10 Oct 2016 12:21:47 +0200 (CEST)
Nelson Lameiras <nelson.lamei...@lyra-network.com> wrote:

> hello michal,
> 
> Yes, both paths are correct and working on the source host since the VM 
> starts and works correctly on source host. Nevertheless I have checked with 
> fdisk and mount to assure that these devices are indeed reachable.
> 
> Please understand that my setup is the following:
> source host : KVM (hosting the VM to migrate)
> target host : oVirt 4.0.4 (patched)
> 
> The error "no storage vol with matching path '/dev/sdc'" is returned by the 
> target host script /usr/lib/python2.7/site-packages/vdsm/v2v.py.
> This almost seems normal since the device /dev/sdc is not mounted on target 
> host (where script is running) but only on source host.
> 
> Can this be the source of the error ?

To me this looks more like a bug in the engine, not in VDSM.

The exception in the VDSM log is OK and it is not fatal. It is actually
to be expected for block devices. VDSM is trying to find out the size of
the disk, but the way it does that is tailored for volumes in storage
pool. But the block device is not a volume in a storage pool and that is
why libvirt complains. We can potentially skip the check for block
devices to avoid error in the log, or provide some other logic of
getting the size.


But the real problem is this error in engine.log:

> 2016-09-29 14:13:48,637 ERROR 
> [org.ovirt.engine.core.bll.GetVmsFromExternalProviderQuery] (default task-30) 
> [] Exception: org.ovirt.engine.core.common.errors.EngineException: 
> EngineException: java.lang.NumberFormatException: null (Failed with error 
> ENGINE and code 5001)

We don't send the size (or rather send null value) for the disk and
engine does not like that. I assume engine does not really consider all
the optional VM properties as optional.



Tomas

-- 
Tomáš Golembiovský <tgole...@redhat.com>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Importing VM from Xen Server 6.5

[Tomáš Golembiovský]

Hi,

On Thu, 11 Aug 2016 14:14:24 +0530
Anantha Raghava  wrote:

> Hi,
> 
> Tested this with different combinations:
> 
> a. from VDSM host, both "ssh root@192.168.1.40" and "sudo -u vdsm ssh 
> root@192.168.1.40" commands are logging in without asking for password 
> and I can run all xe commands without any glitch without modifications 
> to default xen server firewall or SELinux rules.

Could you please verify that running 'virsh list --all' localy works too?


> 
> b. With firewall enabled and SELinux set to enforcing or permissive or 
> disabled, I run "virsh -c ssh://root@192.168.1.40". And the command is 
> resulting in two errors:
> 
>  error: filed to connect to the hypervisor
>  error: unable to connect to the server at '192.168.1.40:16514' : No 
> route to the host.
> 
> c. With firewall disabled and SELinux set to Enforcing or permissive or 
> disabled, I run "virsh -c ssh://192.168.1.40". And the command is 
> resulting in two errors
> 
> error: filed to connect to the hypervisor
>  error: unable to connect to the server at '192.168.1.40:16514' : 
> Connection refused
> 

That is because your libvirt URI is wrong. It has to be 'xen+ssh://...'
not 'ssh://...'.

Does it work if you try: virsh -c 'xen+ssh://root@192.168.1.40' 

Best regards,

Tomas
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users