Ovirt 4.1 USB Api problems
by Adolfo
Hi,
I don't know if this is the correct place for this question (i hope it
is ;-) ).
We are trying to make "enable USB support" work with a machine created
from python ovirtsdk4 api,
here is the code:
cluster = ovirt.types.Cluster(id=six.binary_type(clusterId))
template = ovirt.types.Template(id=six.binary_type(templateId))
if usbType in ('native', 'legacy'):
usb = ovirt.types.Usb(enabled=True,
type=ovirt.types.UsbType.NATIVE if usbType == 'native' else
ovirt.types.UsbType.LEGACY)
else:
usb = ovirt.types.Usb(enabled=False)
memoryPolicy =
ovirt.types.MemoryPolicy(guaranteed=guaranteedMB * 1024 * 1024)
par = ovirt.types.Vm(name=name, cluster=cluster,
template=template, description=comments,
type=ovirt.types.VmType.DESKTOP, memory=memoryMB * 1024 * 1024,
memory_policy=memoryPolicy,
usb=usb) # display=display,
return api.system_service().vms_service().add(par).id
The cuestion is that the machines gets correctly created, but when we
try to start the machine, we get an this error (extract from vdsm):
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 552, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 1994, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py",
line 123, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 941, in
wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3784, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirtError: Error XML: Duplicate USB controllers with index 0
The question is, that if to this machine we have created, from
administration interface, remove an add support for usb, the machine
works, and the generated XML differs:
This is the difference we have found:
< <controller index="0" model="piix3-uhci" type="usb">
< <address bus="0x00" domain="0x0000" function="0x2"
slot="0x01" type="pci" />
< </controller>
40a38
> <address bus="0x00" domain="0x0000" function="0x0"
slot="0x02" type="pci" />
The "<" are from the non working (created from API call), and the ">"
are same machine after disabling and enabling again "usb support".
Is this a bug?, if not, ¿How is supposed to be enabled USB support from
API on VM Creation?,
By the way, the equivalent code for oVirt 3.x was working without
problems, the problems arises from 4.0 onwards.
Sorry for the inconveniences, and thank in advance for any help,
Adolfo Gómez
7 years, 9 months
How to configure Cloud-init in Guest OS ?
by TranceWorldLogic .
Hi,
I am trying to use cloud-int to provide some text file in guest OS as
mention in below link. (tried using sdk)
But it is not working.
http://www.ovirt.org/develop/release-management/features/cloud/cloud-init...
1> Do I need to do some configure cloud-init in Guest OS ?
-> I hav just install cloud-init package in my 2 guest
For centos 6.8 => yum install cloud-init
For ubuntu 14.05 => apt-get install cloud-init
2> Do cloud-init permanently write network configuration in ifconfig
file(Centos) or interface file (ubuntu)?
Thanks,
~Rohit
7 years, 9 months
ovirt-shell -- cannot even get started
by Phil Meyer
This is either some very obscure syntax, or it may not be working.
Difficult to tell, since the error message seems to be generic:
...
==================================== ERROR
=================================
"https://engine-tst/ovirt-engine/api" is invalid url format, valid
format is http[s]://server:port/path, where path is usually
"ovirt-engine/api" or, for older versions of the engine, just "api".
============================================================================
...
That error is reported no matter where it is run from, and no matter what
combination of manual or automated interaction is used.
It should not be this hard.
42 different combinations were tried.
In one instance when using localhost as the hostname, it actually asked for
the certificate first, and then gave me the same error as above.
Lets just say that the command line was very familiar to me when Larry Wall
wrote the Configure script (that was before the GNU configure scripts).
A strait up actual example that works would be nice, or an explanation of
prerequisites, if there are any. None are stated.
There is lots of mention of port numbers, but no actual port numbers
suggested.
Does not the ovirt-shell talk to the web server at port 443 if https is
specified?
The lsof command does not show any listeners that seem likely as a cli
interface:
-> sudo lsof -i | grep -i listen
systemd 1 root 42u IPv6 9030 0t0 TCP
*:sunrpc (LISTEN)
systemd 1 root 43u IPv4 9031 0t0 TCP
*:sunrpc (LISTEN)
ovirt-ima 582 root 5u IPv4 9196 0t0 TCP *:54323
(LISTEN)
ovirt-web 954 ovirt 4u IPv4 14915 0t0 TCP
*:synchronet-db (LISTEN)
httpd 959 root 4u IPv6 18622 0t0 TCP *:http
(LISTEN)
httpd 959 root 6u IPv6 18630 0t0 TCP *:https
(LISTEN)
sshd 962 ovirt-vmconsole 3u IPv4 17902 0t0 TCP
*:EtherNet/IP-1 (LISTEN)
sshd 962 ovirt-vmconsole 4u IPv6 17904 0t0 TCP
*:EtherNet/IP-1 (LISTEN)
sshd 1048 root 3u IPv4 19474 0t0 TCP *:ssh
(LISTEN)
sshd 1048 root 4u IPv6 19477 0t0 TCP *:ssh
(LISTEN)
postgres 1237 postgres 3u IPv4 19552 0t0 TCP
*:postgres (LISTEN)
postgres 1237 postgres 4u IPv6 19553 0t0 TCP
*:postgres (LISTEN)
java 3042 ovirt 371u IPv6 20711 0t0 TCP
localhost:8702 (LISTEN)
java 3042 ovirt 389u IPv6 24722 0t0 TCP
localhost:8706 (LISTEN)
And yes, the unfamiliar ones were tried. :)
The last straw was when a packet sniffer failed to capture ANY traffic
related to these
attempts. Apparently the ovirt-shell command fails before even
attempting a connection.
7 years, 9 months
Re: [ovirt-users] VM switched off when migration for host maintenance fails
by Eduardo Mayoral
OK, then,
Please find the vdsm logs for both source and destination attached.
Eduardo Mayoral Jimeno (emayoral(a)arsys.es)
Administrador de sistemas. Departamento de Plataformas. Arsys internet.
+34 941 620 145 ext. 5153
On 16/03/17 12:13, Yaniv Kaul wrote:
> Please share on the mailing list - I might not get to look at them.
> It's not too big.
> Y.
>
> On Thu, Mar 16, 2017 at 1:06 PM, Eduardo Mayoral <emayoral(a)arsys.es
> <mailto:emayoral@arsys.es>> wrote:
>
> Sure! Please find the logs attached. I do not mind sharing them on
> the mailing list, but I feel they are probably too big.
>
> Eduardo Mayoral Jimeno (emayoral(a)arsys.es <mailto:emayoral@arsys.es>)
> Administrador de sistemas. Departamento de Plataformas. Arsys internet.
> +34 941 620 145 ext. 5153 <tel:+34%20941%2062%2001%2045>
>
> On 16/03/17 11:58, Yaniv Kaul wrote:
>>
>>
>> On Thu, Mar 16, 2017 at 12:56 PM, Eduardo Mayoral
>> <emayoral(a)arsys.es <mailto:emayoral@arsys.es>> wrote:
>>
>> Hi,
>>
>> An interesting thing just happened on my oVirt deployment.
>>
>> While setting a host for maintenance, one of the VMs
>> running on that
>> host failed to migrate. Then ovirt-engine for some reason
>> turned the VM
>> off. Here are the relevant log lines from engine.log:
>>
>>
>>
>>
>> 2017-03-16 09:56:23,324Z INFO
>> [org.ovirt.engine.core.bll.MigrateVmCommand] (default task-60)
>> [61a52216] Lock Acquired to object
>> 'EngineLock:{exclusiveLocks='[422663a9-d712-4992-7c81-165b2976073e=<VM,
>> ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName
>> entorno127.arsysdesarrollo.lan>]', sharedLocks='null'}'
>> 2017-03-16 09:56:23,957Z INFO
>> [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
>> (default task-60) [61a52216] EVENT_ID:
>> VM_MIGRATION_START_SYSTEM_INITIATED(67), Correlation ID:
>> 61a52216, Job
>> ID: fbc5e0d7-4618-4ca8-b7a7-0fd9a43f490f, Call Stack: null,
>> Custom Event
>> ID: -1, Message: Migration initiated by system (VM:
>> entorno127.arsysdesarrollo.lan, Source: llkk594.arsyslan.es
>> <http://llkk594.arsyslan.es>,
>> Destination: llkk593.arsyslan.es
>> <http://llkk593.arsyslan.es>, Reason: Host preparing for
>> maintenance).
>> 2017-03-16 09:56:26,818Z INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (DefaultQuartzScheduler10)
>> [7c6c403b-0a82-47aa-aeb4-57fbe06e20e1] VM
>> '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan)
>> was unexpectedly detected as 'MigratingTo' on VDS
>> '43f43ec5-e51d-400d-8569-261c98382e3a'(llkk593.arsyslan.es
>> <http://llkk593.arsyslan.es>) (expected on
>> '11a82467-afa4-4e4e-bd92-3383082d0a5e')
>> 2017-03-16 09:56:42,149Z INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (DefaultQuartzScheduler10)
>> [fac8ade9-a867-4ff7-aac5-912f78cc3bb5] VM
>> '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan)
>> was unexpectedly detected as 'MigratingTo' on VDS
>> '43f43ec5-e51d-400d-8569-261c98382e3a'(llkk593.arsyslan.es
>> <http://llkk593.arsyslan.es>) (expected on
>> '11a82467-afa4-4e4e-bd92-3383082d0a5e')
>> 2017-03-16 09:56:54,755Z INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (DefaultQuartzScheduler3)
>> [54fa9a1b-fddb-4812-b5d2-06cf92834709] VM
>> '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan)
>> moved from 'MigratingFrom' --> 'Down'
>> 2017-03-16 09:56:54,755Z INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (DefaultQuartzScheduler3)
>> [54fa9a1b-fddb-4812-b5d2-06cf92834709] Handing
>> over VM
>> '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan)
>> to Host '43f43ec5-e51d-400d-8569-261c98382e3a'. Setting VM to
>> status
>> 'MigratingTo'
>> 2017-03-16 09:56:58,160Z INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (DefaultQuartzScheduler4)
>> [dd4ea7bb-85bc-410e-9a8f-357c28d85d1c] VM
>> '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan)
>> is running in db and not running on VDS
>> '43f43ec5-e51d-400d-8569-261c98382e3a'(llkk593.arsyslan.es
>> <http://llkk593.arsyslan.es>)
>> 2017-03-16 09:56:58,161Z INFO
>> [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer]
>> (DefaultQuartzScheduler4)
>> [dd4ea7bb-85bc-410e-9a8f-357c28d85d1c] add VM
>> '422663a9-d712-4992-7c81-165b2976073e'(entorno127.arsysdesarrollo.lan)
>> to rerun treatment
>> turn to maintenance while VMs are still running on it.(VM:
>> entorno127.arsysdesarrollo.lan, Source: llkk594.arsyslan.es
>> <http://llkk594.arsyslan.es>,
>> Destination: llkk593.arsyslan.es <http://llkk593.arsyslan.es>).
>> 2017-03-16 09:56:59,193Z INFO
>> [org.ovirt.engine.core.bll.MigrateVmCommand]
>> (org.ovirt.thread.pool-7-thread-27) [14d40a88] Lock freed to
>> object
>> 'EngineLock:{exclusiveLocks='[422663a9-d712-4992-7c81-165b2976073e=<VM,
>> ACTION_TYPE_FAILED_VM_IS_BEING_MIGRATED$VmName
>> entorno127.arsysdesarrollo.lan>]', sharedLocks='null'}'
>>
>> Now, I understand an VM migration may fail for a number of
>> reasons, but
>> in that case, shouldn't the VM keep running on the source
>> host? I do not
>> quite understand what happened here or how to avoid it in the
>> future.
>>
>>
>> Can you share vdsm logs from both source and destination?
>> Y.
>>
>>
>>
>> Best regards,
>>
>> --
>> Eduardo Mayoral Jimeno (emayoral(a)arsys.es
>> <mailto:emayoral@arsys.es>)
>> Administrador de sistemas. Departamento de Plataformas. Arsys
>> internet.
>> +34 941 620 145 ext. 5153
>> <tel:%2B34%20941%20620%20145%20ext.%205153>
>>
>> _______________________________________________
>> Users mailing list
>> Users(a)ovirt.org <mailto:Users@ovirt.org>
>> http://lists.ovirt.org/mailman/listinfo/users
>> <http://lists.ovirt.org/mailman/listinfo/users>
>>
>>
>
>
7 years, 9 months
how to attach lvm device to VM ?
by TranceWorldLogic .
Hi,
I have created LVM partition in host.
I don't want that partition to act as storage domain in ovirt, but I want
to attach that partition to VM.
So I used virsh command to attach device to VM and it was successfully
attached (block device as raw type).
But when I tried to take snapshot of VM from Ovirt, it fail to get
snapshot.
I think it may be due to vdsm as it is not aware of newly attached lvm
device.
Can someone help me to know another way to attach device to VM in Ovirt?
I tried with vdsClient but not got idea or command that will attach device
to VM.
Thanks,
~Rohit
7 years, 9 months
Adding posix compliant FS
by carl langlois
Hi Guys,
I am trying to add a posix FS on one of my host. Ovirt in actually mounting
it but fail with "Error while executing action Add Storage Connection:
General Exception"
If i look in the vdsm.log i cant see
sonrpc.Executor/7::DEBUG::2017-03-16
12:39:28,248::fileUtils::209::Storage.fileUtils::(createdir) Creating
directory: /rhev/data-center/mnt/_dev_dm-3 mode: None
jsonrpc.Executor/7::DEBUG::2017-03-16
12:39:28,248::fileUtils::218::Storage.fileUtils::(createdir) Using existing
directory: /rhev/data-center/mnt/_dev_dm-3
jsonrpc.Executor/7::INFO::2017-03-16
12:39:28,248::mount::226::storage.Mount::(mount) mounting /dev/dm-3 at
/rhev/data-center/mnt/_dev_dm-3
jsonrpc.Executor/7::DEBUG::2017-03-16
12:39:28,270::utils::871::storage.Mount::(stopwatch)
/rhev/data-center/mnt/_dev_dm-3 mounted: 0.02 seconds
jsonrpc.Executor/7::ERROR::2017-03-16
12:39:28,271::hsm::2403::Storage.HSM::(connectStorageServer) Could not
connect to storageServer
Traceback (most recent call last):
File "/usr/share/vdsm/storage/hsm.py", line 2400, in connectStorageServer
conObj.connect()
File "/usr/share/vdsm/storage/storageServer.py", line 242, in connect
self.getMountObj().getRecord().fs_file)
File "/usr/lib/python2.7/site-packages/vdsm/storage/mount.py", line 260,
in getRecord
(self.fs_spec, self.fs_file))
OSError: [Errno 2] Mount of `/dev/dm-3` at
`/rhev/data-center/mnt/_dev_dm-3` does not exist
any help would be appreciated.
Thanks
CL
7 years, 9 months
Re: [ovirt-users] Serious Trouble - Lost Domains
by JC Clark
This is a multi-part message in MIME format.
--------------D32B351E0E3629426DD972AA
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Thank you for your response.
My storage is NFS storage.
I will try with "qemu-img info" ..
I made an attempt to import the domain and I got an error. I will attempt to replicate tonight.
Do I have to alter any of the metafiles when importing? I seemed to remember it didn't like to import another data center's domain.
Sincerely JC
Date: Tue, 14 Mar 2017 10:16:17 +0100
From: Arman Khalatyan<arm2arm(a)gmail.com>
To: JC Clark<jc(a)saipantech.com>
Cc: users<users(a)ovirt.org>
Subject: Re: [ovirt-users] Serious Trouble - Lost Domains
Message-ID:
<CAAqDm6ap1YDV4ThRa+Z4H-2k3o9VQ8qp4PAWQ7VShYmEeGXSyQ(a)mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
What kind of storage are you using?
If you check images with "qemu-img info" are you able to see the
filesystems?
Can you simply import the domain unto the new ovirt?
Am 14.03.2017 9:59 vorm. schrieb "JC Clark"<jc(a)saipantech.com>:
> Dear Fellows and Fellettes,
>
> I am having serious disaster problems. After a power transformer outside
> the building literally exploded, surged and fried the motherboard to the
> main SPM domain computer in my Ovirt 4.0 system. After getting the computer
> working again with a new mother board. I managed to basically loose
> integrity of the old engine. I have rebuilt the engine.
>
> I have backups of the old engine and 4 data domains an ISO domain and an
> export domain which appear to not be damaged. They are all accessible from
> the CL.
> I had to create a new host and SPM. How do I get the floating domains
> into the new Engine?
>
> I have 1 storage container (85GB) I must get back. MUST GET BACK!!
>
> I really appreciate you reading my sob story. Hope you can help..
>
> Thank You much
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
7 years, 9 months
virtio-scsi drive order?
by gflwqs gflwqs
Hi list!
When we upgraded our ovirt environment to 4.1 we get the virtio-scsi
interface as default for virtual disks.
We have seen a difference in drive order from when we used the virtio
interface.
Before when we added disks the order of the drives were set by which order
the disks was created.
So if i had 1 disk as os disk it became vda and added a 50 GB disk that
disk became vdb and then added another 8GB disk that became vdc.
But now when i add two additional disks with the virtio-scsi interface like
the above when i reboot the vm the 50GB disk become sdc and the 8GB disk
become sdb even that i created the 50GB disk first?
How is the order decided in the virtio-scsi interface?
What can i do to ensure that the disks come in the order that i create them?
Regards
Christian
7 years, 9 months
iSCSI and multipath deliberation
by Marcin Kruk
In my opionion the main problem in configuration iscsi and multipath is
that the ovirt developers try to start everything automaticaly during
installation, and then during start services like vdsmd.
But during installation process adminstrator shoud choose the right
multipath WWID identifier only.
And administrator should be responsible for setting multipath and iSCSI
properly.
Otherwise ovirt installator does everything automaticaly in the universal
way which is weak due to so many storage types.
Howgh :)
7 years, 9 months
Change repository from PRE to Release
by FERNANDO FREDIANI
This is a multi-part message in MIME format.
--------------0BDD173BE2AA4DE842ADD5EF
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Hi again folks
I have been using the *ovirt-4.1-pre* and *ovirt-4.1-pre-dependencies*
repositories, but now that 4.1 is stable I want to change it to
*ovirt-release41*.
Is there any harm if I just install
http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm and remove
the other two 'pre' repositories from my /etc/yum.repos.d/ ? Or is there
anything I should be concerned when doing that ?
Thanks
Fernando
--------------0BDD173BE2AA4DE842ADD5EF
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hi again folks</p>
<p>I have been using the <b>ovirt-4.1-pre</b> and <b>ovirt-4.1-pre-dependencies</b>
repositories, but now that 4.1 is stable I want to change it to <b>ovirt-release41</b>.</p>
<p>Is there any harm if I just install
<a class="moz-txt-link-freetext" href="http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm">http://resources.ovirt.org/pub/yum-repo/ovirt-release41.rpm</a> and
remove the other two 'pre' repositories from my /etc/yum.repos.d/
? Or is there anything I should be concerned when doing that ?</p>
<p>Thanks</p>
<p>Fernando<br>
</p>
</body>
</html>
--------------0BDD173BE2AA4DE842ADD5EF--
7 years, 9 months
