Re: [Users] Help - Cannot run VM. Invalid time zone for given OS type.
On 2 Jan 2014, at 20:12, Dan Ferris wrote: Hi, Has anyone run across this error: Cannot run VM. Invalid time zone for given OS type. The OS type for these VMs is set to Linux Other. What was the original TZ in 3.2? They were all exported from an Ovirt 3.2 cluster and are being reimported into an Ovirt 3.3 cluster. Linux Other was supposed to be changed to Other on import. Did it happen correctly? None of these VMs will boot. We also can't delete them because delete protection is enabled and we can't edit the VM to turn off delete protection. Can you edit and just change the TZ to something else? Thanks, michal Does anyone know what this error means exactly and how to fix it? Thanks, Dan ___ 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
Re: [Users] Help - Cannot run VM. Invalid time zone for given OS type.
On 02.01.2014 20:12, Dan Ferris wrote: Hi, Has anyone run across this error: Cannot run VM. Invalid time zone for given OS type. The OS type for these VMs is set to Linux Other. They were all exported from an Ovirt 3.2 cluster and are being reimported into an Ovirt 3.3 cluster. None of these VMs will boot. We also can't delete them because delete protection is enabled and we can't edit the VM to turn off delete protection. Does anyone know what this error means exactly and how to fix it? Thanks, Dan Hi Dan, I had the very problem myself. The fix for it is quite easy, but requires manual editing of one database table. In table vm_static find your non-starting vms (they propably all have an empty string set as timezone in column time_zone) and update that column to null. There was a recent change in the timezone code and it now fails when the timezone is an empty string, but works fine if it null. Regards Patrick -- Lobster LOGsuite GmbH, Münchner Straße 15a, D-82319 Starnberg HRB 178831, Amtsgericht München Geschäftsführer: Dr. Martin Fischer, Rolf Henrich ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Help - Cannot run VM. Invalid time zone for given OS type.
Hi, I'm a little surprised by this development technique. In my world, when you change data formats in a not compatible way you should also write some sort of transition code to convert the old data to the new data format for all possible cases. And if this is not possible for some reason, at least document this prominent in the release notes. In which version did this change occur? With such bad behaviour, I doubt we will ever get to something like a stable release. I'm sorry when I missed the part of the release notes where this is described and I'm happy if I'm totally wrong and just didn't look good enough to find it. Please point me to some docs which mention this behaviour. Am 03.01.2014 10:54, schrieb Patrick Hurrelmann: Hi Dan, I had the very problem myself. The fix for it is quite easy, but requires manual editing of one database table. In table vm_static find your non-starting vms (they propably all have an empty string set as timezone in column time_zone) and update that column to null. There was a recent change in the timezone code and it now fails when the timezone is an empty string, but works fine if it null. Regards Patrick -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Host cannot access storage domains
Hi, I am starting with oVirt 3.3.2 and I have an issue adding a host to a cluster. I am using oVirt Engine Version 3.3.2-1.el6 There is a cluster with one host (installed with oVirt Node - 3.0.3 - 1.1.fc19 ISO image) up and running. I installed a second host using the same ISO image. I approved the host in the cluster. When I try to activate the second host, I receive the following messages in the events pane: State was set to Up for host host02. Host host02 reports about one of the Active Storage Domains as Problematic. Host host02 cannot access one of the Storage Domains attached to the Data Center Test303. Stetting Host state to Non-Operational. Failed to connect Host host02 to Storage Pool Test303 There are 3 FC Storage Domains configured and visible to both hosts. multipath -ll shows all LUNs on both hosts. The engine.log reports the following about every five minutes: 2014-01-03 13:50:15,408 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 7841a1c0-181a-4d43-9a25-b707accb5c4b: LUN_105 check timeot 69.7 is too big 2014-01-03 13:50:15,409 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 52cf84ce-6eda-4337-8c94-491d94f5a18d: LUN_103 check timeot 59.6 is too big 2014-01-03 13:50:15,410 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_105 of pool Test303 is in problem in host host02 2014-01-03 13:50:15,411 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_103 of pool Test030 is in problem in host host02 Please let me know if there are any log files I should attach. Thank you for your help! All the best, Oliver Albl ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
yes, please attach the vdsm log also, can you run vdsClient 0 getStorageDomainsList and vdsClient 0 getDeviceList on both hosts? It might be a cache issue, so can you please restart the host and if it helps attach output before and after the reboot? Thanks, Dafna On 01/03/2014 01:12 PM, Albl, Oliver wrote: Hi, I am starting with oVirt 3.3.2 and I have an issue adding a host to a cluster. I am using oVirt Engine Version 3.3.2-1.el6 There is a cluster with one host (installed with oVirt Node - 3.0.3 - 1.1.fc19 ISO image) up and running. I installed a second host using the same ISO image. I approved the host in the cluster. When I try to activate the second host, I receive the following messages in the events pane: State was set to Up for host host02. Host host02 reports about one of the Active Storage Domains as Problematic. Host host02 cannot access one of the Storage Domains attached to the Data Center Test303. Stetting Host state to Non-Operational. Failed to connect Host host02 to Storage Pool Test303 There are 3 FC Storage Domains configured and visible to both hosts. multipath –ll shows all LUNs on both hosts. The engine.log reports the following about every five minutes: 2014-01-03 13:50:15,408 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 7841a1c0-181a-4d43-9a25-b707accb5c4b: LUN_105 check timeot 69.7 is too big 2014-01-03 13:50:15,409 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 52cf84ce-6eda-4337-8c94-491d94f5a18d: LUN_103 check timeot 59.6 is too big 2014-01-03 13:50:15,410 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_105 of pool Test303 is in problem in host host02 2014-01-03 13:50:15,411 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_103 of pool Test030 is in problem in host host02 Please let me know if there are any log files I should attach. Thank you for your help! All the best, Oliver Albl ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] qemu-img-rhev can't handle -s parameter
Hello, I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s parameter, but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm) errors out with: convert: invalid option -- 's' What am I missing? Do I need any special rpmbuild switches or something? I see the spec already says rhev 1 which should be enough. Regards, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] qemu-img-rhev can't handle -s parameter
yes, there are bugs reported in openstack for the same issue on qemu-kvm: https://bugzilla.redhat.com/show_bug.cgi?id=1027074 https://bugzilla.redhat.com/show_bug.cgi?id=1016896 On 01/03/2014 01:34 PM, Nux! wrote: Hello, I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s parameter, but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm) errors out with: convert: invalid option -- 's' What am I missing? Do I need any special rpmbuild switches or something? I see the spec already says rhev 1 which should be enough. Regards, Lucian -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
Dafna, you were right, it seems to be a caching issue. Rebooting the host did the job: Before Reboot: [root@host01 log]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b [root@host02 log]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b 925ee53a-69b5-440f-b145-138ada5b452e After Reboot: [root@host02 admin]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b So now I have both hosts up and running but when I try to start a VM on the second host, I receive the following messages in the events pane: VM TEST2 was started by oliver.albl (Host: host02) VM TEST2 is down. Exit message: Child quit during startup handshake: Input/output error. Thanks again for your help! Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 14:22 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: [Users] Host cannot access storage domains yes, please attach the vdsm log also, can you run vdsClient 0 getStorageDomainsList and vdsClient 0 getDeviceList on both hosts? It might be a cache issue, so can you please restart the host and if it helps attach output before and after the reboot? Thanks, Dafna On 01/03/2014 01:12 PM, Albl, Oliver wrote: Hi, I am starting with oVirt 3.3.2 and I have an issue adding a host to a cluster. I am using oVirt Engine Version 3.3.2-1.el6 There is a cluster with one host (installed with oVirt Node - 3.0.3 - 1.1.fc19 ISO image) up and running. I installed a second host using the same ISO image. I approved the host in the cluster. When I try to activate the second host, I receive the following messages in the events pane: State was set to Up for host host02. Host host02 reports about one of the Active Storage Domains as Problematic. Host host02 cannot access one of the Storage Domains attached to the Data Center Test303. Stetting Host state to Non-Operational. Failed to connect Host host02 to Storage Pool Test303 There are 3 FC Storage Domains configured and visible to both hosts. multipath -ll shows all LUNs on both hosts. The engine.log reports the following about every five minutes: 2014-01-03 13:50:15,408 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 7841a1c0-181a-4d43-9a25-b707accb5c4b: LUN_105 check timeot 69.7 is too big 2014-01-03 13:50:15,409 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 52cf84ce-6eda-4337-8c94-491d94f5a18d: LUN_103 check timeot 59.6 is too big 2014-01-03 13:50:15,410 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_105 of pool Test303 is in problem in host host02 2014-01-03 13:50:15,411 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_103 of pool Test030 is in problem in host host02 Please let me know if there are any log files I should attach. Thank you for your help! All the best, Oliver Albl ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
Thanks for reporting the issue :) As for the vm, can you please find the error in vdsm.log and in engine and paste it? Thanks, Dafna On 01/03/2014 01:49 PM, Albl, Oliver wrote: Dafna, you were right, it seems to be a caching issue. Rebooting the host did the job: Before Reboot: [root@host01 log]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b [root@host02 log]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b 925ee53a-69b5-440f-b145-138ada5b452e After Reboot: [root@host02 admin]# vdsClient -s 0 getStorageDomainsList 52cf84ce-6eda-4337-8c94-491d94f5a18d f404398a-97f9-474c-af2c-e8887f53f688 7841a1c0-181a-4d43-9a25-b707accb5c4b So now I have both hosts up and running but when I try to start a VM on the second host, I receive the following messages in the events pane: VM TEST2 was started by oliver.albl (Host: host02) VM TEST2 is down. Exit message: Child quit during startup handshake: Input/output error. Thanks again for your help! Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 14:22 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: [Users] Host cannot access storage domains yes, please attach the vdsm log also, can you run vdsClient 0 getStorageDomainsList and vdsClient 0 getDeviceList on both hosts? It might be a cache issue, so can you please restart the host and if it helps attach output before and after the reboot? Thanks, Dafna On 01/03/2014 01:12 PM, Albl, Oliver wrote: Hi, I am starting with oVirt 3.3.2 and I have an issue adding a host to a cluster. I am using oVirt Engine Version 3.3.2-1.el6 There is a cluster with one host (installed with oVirt Node - 3.0.3 - 1.1.fc19 ISO image) up and running. I installed a second host using the same ISO image. I approved the host in the cluster. When I try to activate the second host, I receive the following messages in the events pane: State was set to Up for host host02. Host host02 reports about one of the Active Storage Domains as Problematic. Host host02 cannot access one of the Storage Domains attached to the Data Center Test303. Stetting Host state to Non-Operational. Failed to connect Host host02 to Storage Pool Test303 There are 3 FC Storage Domains configured and visible to both hosts. multipath -ll shows all LUNs on both hosts. The engine.log reports the following about every five minutes: 2014-01-03 13:50:15,408 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 7841a1c0-181a-4d43-9a25-b707accb5c4b: LUN_105 check timeot 69.7 is too big 2014-01-03 13:50:15,409 ERROR [org.ovirt.engine.core.vdsbroker.irsbroker.IrsBrokerCommand] (pool-6-thread-44) Domain 52cf84ce-6eda-4337-8c94-491d94f5a18d: LUN_103 check timeot 59.6 is too big 2014-01-03 13:50:15,410 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_105 of pool Test303 is in problem in host host02 2014-01-03 13:50:15,411 ERROR [org.ovirt.engine.core.bll.InitVdsOnUpCommand] (pool-6-thread-44) Storage Domain LUN_103 of pool Test030 is in problem in host host02 Please let me know if there are any log files I should attach. Thank you for your help! All the best, Oliver Albl ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
Dafna,
please find the logs below:
ERRORs in vdsm.log on host02:
Thread-61::ERROR::2014-01-03
13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-61::ERROR::2014-01-03
13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-323::ERROR::2014-01-03
13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm)
vmId=`d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 2092, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/vm.py, line 2959, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py, line 76,
in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.7/site-packages/libvirt.py, line 2920, in createXML
libvirtError: Child quit during startup handshake: Input/output error
Thread-60::ERROR::2014-01-03
13:52:23,111::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain 52cf84ce-6eda-4337-8c94-491d94f5a18d
Thread-60::ERROR::2014-01-03
13:52:23,111::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 52cf84ce-6eda-4337-8c94-491d94f5a18d
Thread-62::ERROR::2014-01-03
13:52:26,353::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain 7841a1c0-181a-4d43-9a25-b707accb5c4b
Thread-62::ERROR::2014-01-03
13:52:26,355::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 7841a1c0-181a-4d43-9a25-b707accb5c4b
engine.log:
2014-01-03 14:52:06,976 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, IsVmDuringInitiatingVDSCommand( vmId =
d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6), log id: 5940cf72
2014-01-03 14:52:06,976 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, IsVmDuringInitiatingVDSCommand,
return: false, log id: 5940cf72
2014-01-03 14:52:07,057 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] Running command: RunVmOnceCommand internal:
false. Entities affected : ID: d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 Type: VM,
ID: d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 Type: VM
2014-01-03 14:52:07,151 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, IsoPrefixVDSCommand(HostName = host02,
HostId = 6dc7fac6-149e-4445-ace1-3c334a24d52a,
storagePoolId=b33d1793-252b-44ac-9685-3fe56b83c4c9), log id: 1705b611
2014-01-03 14:52:07,152 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, IsoPrefixVDSCommand, return:
/rhev/data-center/mnt/vmmgmt:_var_lib_exports_iso/f74f052e-0dc6-456d-af95-248c2227c2e5/images/----,
log id: 1705b611
2014-01-03 14:52:07,170 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp--127.0.0.1-8702-3)
[2ab5cd2] START, CreateVmVDSCommand(HostName = host02, HostId =
6dc7fac6-149e-4445-ace1-3c334a24d52a,
vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6, vm=VM [TEST2]), log id: 27b504de
2014-01-03 14:52:07,190 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, CreateVDSCommand(HostName = host02,
HostId = 6dc7fac6-149e-4445-ace1-3c334a24d52a,
vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6, vm=VM [TEST2]), log id: 6ad0220
2014-01-03 14:52:08,472 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2]
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand
spiceSslCipherSuite=DEFAULT,memSize=1024,kvmEnable=true,smp=1,vmType=kvm,emulatedMachine=pc-1.0,keyboardLayout=en-us,memGuaranteedSize=1024,pitReinjection=false,nice=0,display=qxl,smartcardEnable=false,smpCoresPerSocket=1,spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard,timeOffset=0,transparentHugePages=true,vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6,devices=[Ljava.util.HashMap;@3692311a,acpiEnable=true,vmName=TEST2,cpuType=SandyBridge,custom={}
2014-01-03 14:52:08,476 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, CreateVDSCommand, log id: 6ad0220
2014-01-03 14:52:08,484 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp--127.0.0.1-8702-3)
[2ab5cd2] FINISH, CreateVmVDSCommand, return: WaitForLaunch, log id: 27b504de
2014-01-03 14:52:08,497 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ajp--127.0.0.1-8702-3) [2ab5cd2] Correlation ID: 2ab5cd2, Job ID:
2913133b-1301-484e-9887-b110841c8078, Call Stack: null, Custom Event ID: -1,
Message: VM TEST2 was started by oliver.albl (Host: host02).
2014-01-03 14:52:14,728 INFO
Re: [Users] Host cannot access storage domains
Can you please try this?
http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html
On 01/03/2014 02:00 PM, Albl, Oliver wrote:
Dafna,
please find the logs below:
ERRORs in vdsm.log on host02:
Thread-61::ERROR::2014-01-03
13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-61::ERROR::2014-01-03
13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-323::ERROR::2014-01-03
13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm)
vmId=`d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 2092, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/vm.py, line 2959, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py, line
76, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.7/site-packages/libvirt.py, line 2920, in createXML
libvirtError: Child quit during startup handshake: Input/output error
Thread-60::ERROR::2014-01-03
13:52:23,111::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain 52cf84ce-6eda-4337-8c94-491d94f5a18d
Thread-60::ERROR::2014-01-03
13:52:23,111::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 52cf84ce-6eda-4337-8c94-491d94f5a18d
Thread-62::ERROR::2014-01-03
13:52:26,353::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain 7841a1c0-181a-4d43-9a25-b707accb5c4b
Thread-62::ERROR::2014-01-03
13:52:26,355::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 7841a1c0-181a-4d43-9a25-b707accb5c4b
engine.log:
2014-01-03 14:52:06,976 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, IsVmDuringInitiatingVDSCommand( vmId =
d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6), log id: 5940cf72
2014-01-03 14:52:06,976 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, IsVmDuringInitiatingVDSCommand,
return: false, log id: 5940cf72
2014-01-03 14:52:07,057 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] Running command: RunVmOnceCommand internal:
false. Entities affected : ID: d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 Type: VM,
ID: d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 Type: VM
2014-01-03 14:52:07,151 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, IsoPrefixVDSCommand(HostName = host02,
HostId = 6dc7fac6-149e-4445-ace1-3c334a24d52a,
storagePoolId=b33d1793-252b-44ac-9685-3fe56b83c4c9), log id: 1705b611
2014-01-03 14:52:07,152 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, IsoPrefixVDSCommand, return:
/rhev/data-center/mnt/vmmgmt:_var_lib_exports_iso/f74f052e-0dc6-456d-af95-248c2227c2e5/images/----,
log id: 1705b611
2014-01-03 14:52:07,170 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp--127.0.0.1-8702-3)
[2ab5cd2] START, CreateVmVDSCommand(HostName = host02, HostId =
6dc7fac6-149e-4445-ace1-3c334a24d52a,
vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6, vm=VM [TEST2]), log id: 27b504de
2014-01-03 14:52:07,190 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, CreateVDSCommand(HostName = host02,
HostId = 6dc7fac6-149e-4445-ace1-3c334a24d52a,
vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6, vm=VM [TEST2]), log id: 6ad0220
2014-01-03 14:52:08,472 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2]
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand
spiceSslCipherSuite=DEFAULT,memSize=1024,kvmEnable=true,smp=1,vmType=kvm,emulatedMachine=pc-1.0,keyboardLayout=en-us,memGuaranteedSize=1024,pitReinjection=false,nice=0,display=qxl,smartcardEnable=false,smpCoresPerSocket=1,spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard,timeOffset=0,transparentHugePages=true,vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6,devices=[Ljava.util.HashMap;@3692311a,acpiEnable=true,vmName=TEST2,cpuType=SandyBridge,custom={}
2014-01-03 14:52:08,476 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, CreateVDSCommand, log id: 6ad0220
2014-01-03 14:52:08,484 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp--127.0.0.1-8702-3)
[2ab5cd2] FINISH, CreateVmVDSCommand, return: WaitForLaunch, log id: 27b504de
2014-01-03 14:52:08,497 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ajp--127.0.0.1-8702-3)
Re: [Users] Help - Cannot run VM. Invalid time zone for given OS type.
On 01/03/2014 12:22 PM, Sven Kieske wrote: Hi, I'm a little surprised by this development technique. its not a development technique. its a bug in upgrade or export/import of the change to the much more powerful config file based OsInfo implementation in 3.3. though i thought we already fixed it. michal/roy - isn't this fixed already? In my world, when you change data formats in a not compatible way you should also write some sort of transition code to convert the old data to the new data format for all possible cases. And if this is not possible for some reason, at least document this prominent in the release notes. In which version did this change occur? With such bad behaviour, I doubt we will ever get to something like a stable release. I'm sorry when I missed the part of the release notes where this is described and I'm happy if I'm totally wrong and just didn't look good enough to find it. Please point me to some docs which mention this behaviour. Am 03.01.2014 10:54, schrieb Patrick Hurrelmann: Hi Dan, I had the very problem myself. The fix for it is quite easy, but requires manual editing of one database table. In table vm_static find your non-starting vms (they propably all have an empty string set as timezone in column time_zone) and update that column to null. There was a recent change in the timezone code and it now fails when the timezone is an empty string, but works fine if it null. Regards Patrick ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
actually, looking at this again, it's a libvirt error and it can be
related to selinux or sasl.
can you also, look at libvirt log and the vm log under /var/log/libvirt?
On 01/03/2014 02:00 PM, Albl, Oliver wrote:
Dafna,
please find the logs below:
ERRORs in vdsm.log on host02:
Thread-61::ERROR::2014-01-03
13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-61::ERROR::2014-01-03
13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain f404398a-97f9-474c-af2c-e8887f53f688
Thread-323::ERROR::2014-01-03
13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm)
vmId=`d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6`::The vm start process failed
Traceback (most recent call last):
File /usr/share/vdsm/vm.py, line 2092, in _startUnderlyingVm
self._run()
File /usr/share/vdsm/vm.py, line 2959, in _run
self._connection.createXML(domxml, flags),
File /usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py, line
76, in wrapper
ret = f(*args, **kwargs)
File /usr/lib64/python2.7/site-packages/libvirt.py, line 2920, in createXML
libvirtError: Child quit during startup handshake: Input/output error
Thread-60::ERROR::2014-01-03
13:52:23,111::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain 52cf84ce-6eda-4337-8c94-491d94f5a18d
Thread-60::ERROR::2014-01-03
13:52:23,111::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 52cf84ce-6eda-4337-8c94-491d94f5a18d
Thread-62::ERROR::2014-01-03
13:52:26,353::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for
unfetched domain 7841a1c0-181a-4d43-9a25-b707accb5c4b
Thread-62::ERROR::2014-01-03
13:52:26,355::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDomain)
looking for domain 7841a1c0-181a-4d43-9a25-b707accb5c4b
engine.log:
2014-01-03 14:52:06,976 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, IsVmDuringInitiatingVDSCommand( vmId =
d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6), log id: 5940cf72
2014-01-03 14:52:06,976 INFO
[org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, IsVmDuringInitiatingVDSCommand,
return: false, log id: 5940cf72
2014-01-03 14:52:07,057 INFO [org.ovirt.engine.core.bll.RunVmOnceCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] Running command: RunVmOnceCommand internal:
false. Entities affected : ID: d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 Type: VM,
ID: d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 Type: VM
2014-01-03 14:52:07,151 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, IsoPrefixVDSCommand(HostName = host02,
HostId = 6dc7fac6-149e-4445-ace1-3c334a24d52a,
storagePoolId=b33d1793-252b-44ac-9685-3fe56b83c4c9), log id: 1705b611
2014-01-03 14:52:07,152 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.IsoPrefixVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, IsoPrefixVDSCommand, return:
/rhev/data-center/mnt/vmmgmt:_var_lib_exports_iso/f74f052e-0dc6-456d-af95-248c2227c2e5/images/----,
log id: 1705b611
2014-01-03 14:52:07,170 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp--127.0.0.1-8702-3)
[2ab5cd2] START, CreateVmVDSCommand(HostName = host02, HostId =
6dc7fac6-149e-4445-ace1-3c334a24d52a,
vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6, vm=VM [TEST2]), log id: 27b504de
2014-01-03 14:52:07,190 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] START, CreateVDSCommand(HostName = host02,
HostId = 6dc7fac6-149e-4445-ace1-3c334a24d52a,
vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6, vm=VM [TEST2]), log id: 6ad0220
2014-01-03 14:52:08,472 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2]
org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand
spiceSslCipherSuite=DEFAULT,memSize=1024,kvmEnable=true,smp=1,vmType=kvm,emulatedMachine=pc-1.0,keyboardLayout=en-us,memGuaranteedSize=1024,pitReinjection=false,nice=0,display=qxl,smartcardEnable=false,smpCoresPerSocket=1,spiceSecureChannels=smain,sinputs,scursor,splayback,srecord,sdisplay,susbredir,ssmartcard,timeOffset=0,transparentHugePages=true,vmId=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6,devices=[Ljava.util.HashMap;@3692311a,acpiEnable=true,vmName=TEST2,cpuType=SandyBridge,custom={}
2014-01-03 14:52:08,476 INFO
[org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVDSCommand]
(ajp--127.0.0.1-8702-3) [2ab5cd2] FINISH, CreateVDSCommand, log id: 6ad0220
2014-01-03 14:52:08,484 INFO
[org.ovirt.engine.core.vdsbroker.CreateVmVDSCommand] (ajp--127.0.0.1-8702-3)
[2ab5cd2] FINISH, CreateVmVDSCommand, return: WaitForLaunch, log id: 27b504de
2014-01-03 14:52:08,497 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(ajp--127.0.0.1-8702-3)
Re: [Users] Host cannot access storage domains
Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C384C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5c4b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-8387-ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca992-b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not sure what you mean with this http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html. Do you want me to update libvirt with these repos on the oVirt-Node based installation? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:10 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: [Users] Host cannot access storage domains actually, looking at this again, it's a libvirt error and it can be related to selinux or sasl. can you also, look at libvirt log and the vm log under /var/log/libvirt? On 01/03/2014 02:00 PM, Albl, Oliver wrote: Dafna, please find the logs below: ERRORs in vdsm.log on host02: Thread-61::ERROR::2014-01-03 13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-61::ERROR::2014-01-03 13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDom ain) looking for domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-323::ERROR::2014-01-03 13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm) vmId=`d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6`::The vm start process failed Traceback (most recent call last): File /usr/share/vdsm/vm.py, line 2092, in _startUnderlyingVm self._run() File /usr/share/vdsm/vm.py, line 2959, in _run self._connection.createXML(domxml, flags), File /usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py, line 76, in wrapper ret = f(*args, **kwargs) File /usr/lib64/python2.7/site-packages/libvirt.py, line 2920, in createXML libvirtError: Child quit during startup handshake: Input/output error Thread-60::ERROR::2014-01-03 13:52:23,111::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain 52cf84ce-6eda-4337-8c94-491d94f5a18d Thread-60::ERROR::2014-01-03 13:52:23,111::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDom ain) looking for domain 52cf84ce-6eda-4337-8c94-491d94f5a18d Thread-62::ERROR::2014-01-03 13:52:26,353::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain
Re: [Users] Help - Cannot run VM. Invalid time zone for given OS type.
On 3 Jan 2014, at 15:04, Itamar Heim wrote: On 01/03/2014 12:22 PM, Sven Kieske wrote: Hi, I'm a little surprised by this development technique. its not a development technique. its a bug in upgrade or export/import of the change to the much more powerful config file based OsInfo implementation in 3.3. though i thought we already fixed it. michal/roy - isn't this fixed already? It is fixed for a long time. I think it's a TZ problem, not really osinfo. I may not recall this correctly but I think the problematic code wasn't even released, it was broken just for couple of weeks, that's why I'm curious what is the exact release where it was exported to confirm it's not related to osinfo unification of Other. In my world, when you change data formats in a not compatible way you should also write some sort of transition code to convert the old data to the new data format for all possible cases. And if this is not possible for some reason, at least document this prominent in the release notes. In which version did this change occur? With such bad behaviour, I doubt we will ever get to something like a stable release. I'm sorry when I missed the part of the release notes where this is described and I'm happy if I'm totally wrong and just didn't look good enough to find it. Please point me to some docs which mention this behaviour. Am 03.01.2014 10:54, schrieb Patrick Hurrelmann: Hi Dan, I had the very problem myself. The fix for it is quite easy, but requires manual editing of one database table. In table vm_static find your non-starting vms (they propably all have an empty string set as timezone in column time_zone) and update that column to null. There was a recent change in the timezone code and it now fails when the timezone is an empty string, but works fine if it null. Regards Patrick ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C384C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5c4b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-8387-ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca992-b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=native -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=channel2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel=main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-channel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usbredir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not sure what you mean with this http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html. Do you want me to update libvirt with these repos on the oVirt-Node based installation? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:10 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: [Users] Host cannot access storage domains actually, looking at this again, it's a libvirt error and it can be related to selinux or sasl. can you also, look at libvirt log and the vm log under /var/log/libvirt? On 01/03/2014 02:00 PM, Albl, Oliver wrote: Dafna, please find the logs below: ERRORs in vdsm.log on host02: Thread-61::ERROR::2014-01-03 13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-61::ERROR::2014-01-03 13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDom ain) looking for domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-323::ERROR::2014-01-03 13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm) vmId=`d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6`::The vm start process failed Traceback (most recent call last): File /usr/share/vdsm/vm.py, line 2092, in _startUnderlyingVm self._run() File /usr/share/vdsm/vm.py, line 2959, in _run self._connection.createXML(domxml, flags), File /usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py, line 76, in wrapper ret = f(*args, **kwargs) File /usr/lib64/python2.7/site-packages/libvirt.py, line 2920, in createXML libvirtError: Child quit during startup handshake: Input/output error Thread-60::ERROR::2014-01-03 13:52:23,111::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain 52cf84ce-6eda-4337-8c94-491d94f5a18d Thread-60::ERROR::2014-01-03
Re: [Users] Host cannot access storage domains
I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C384 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,serve r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5c4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-8387- ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca992- b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=nat ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=chann el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=chann el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel= main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-cha nnel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usb redir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr= 0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not sure what you mean with this http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html. Do you want me to update libvirt with these repos on the oVirt-Node based installation? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:10 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: [Users] Host cannot access storage domains actually, looking at this again, it's a libvirt error and it can be related to selinux or sasl. can you also, look at libvirt log and the vm log under /var/log/libvirt? On 01/03/2014 02:00 PM, Albl, Oliver wrote: Dafna, please find the logs below: ERRORs in vdsm.log on host02: Thread-61::ERROR::2014-01-03 13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-61::ERROR::2014-01-03 13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDo m ain) looking for domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-323::ERROR::2014-01-03 13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm) vmId=`d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6`::The vm start process failed Traceback (most recent call last): File /usr/share/vdsm/vm.py, line 2092, in _startUnderlyingVm self._run() File /usr/share/vdsm/vm.py, line 2959, in _run
[Users] VM MAC-Ranges and setting custom MACs via API
Hi, I got some questions regarding the MAC-Range in the engine and how to utilize the set custom mac feature via API: We want to set a custom MAC per VM via REST-API (JSON) The RSDL tells me, that this should be possible in general. However, I have two questions: Must the specified custom MAC be within the range defined in engine? I suppose not, as this range should just be a pool to take MACs from when engine itself acquires one for a vm. Also some users in IRC could use imported vms with custom macs, but using REST might yield different results? Does this work via JSON in ovirt-engine 3.3.2 ? I just learned that the JSON implementation is not feature complete until 3.4. so I wonder if I can use JSON instead of XML to achieve this. I can not wait for the 3.4. release anyway. We had so far no problem with using JSON beside a nasty Cloud-Init (documentation)bug (BZ 1045484) and we don't want to rewrite all our code to generate XML instead of JSON if we can avoid it. -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
ok, let's try to zoom in on the issue... can you run vm's on the first host or do you have issues only on the second host you added? can you run on both hosts? # egrep -v ^# /etc/libvirt/qemu-sanlock.conf can you run yum update on one of the hosts and see if there are newer packages? Thanks, Dafna On 01/03/2014 02:30 PM, Albl, Oliver wrote: I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C384 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,serve r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5c4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-8387- ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca992- b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=nat ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,id =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chann el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=chann el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=chann el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel= main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-cha nnel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=usb redir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr= 0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not sure what you mean with this http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html. Do you want me to update libvirt with these repos on the oVirt-Node based installation? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:10 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: [Users] Host cannot access storage domains actually, looking at this again, it's a libvirt error and it can be related to selinux or sasl. can you also, look at libvirt log and the vm log under /var/log/libvirt? On 01/03/2014 02:00 PM, Albl, Oliver wrote: Dafna, please find the logs below: ERRORs in vdsm.log on host02: Thread-61::ERROR::2014-01-03 13:51:48,956::sdc::137::Storage.StorageDomainCache::(_findDomain) looking for unfetched domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-61::ERROR::2014-01-03 13:51:48,959::sdc::154::Storage.StorageDomainCache::(_findUnfetchedDo m ain) looking for domain f404398a-97f9-474c-af2c-e8887f53f688 Thread-323::ERROR::2014-01-03 13:52:11,527::vm::2132::vm.Vm::(_startUnderlyingVm)
Re: [Users] Host cannot access storage domains
Dafna, yes, the VM starts on the first node, the issues are on the second node only. /etc/libvirt/qemu-sanlock.conf is identical on on both nodes: auto_disk_leases=0 require_lease_for_disks=0 yum updates reports Using yum is not supported... Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:39 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: [Users] Host cannot access storage domains ok, let's try to zoom in on the issue... can you run vm's on the first host or do you have issues only on the second host you added? can you run on both hosts? # egrep -v ^# /etc/libvirt/qemu-sanlock.conf can you run yum update on one of the hosts and see if there are newer packages? Thanks, Dafna On 01/03/2014 02:30 PM, Albl, Oliver wrote: I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C38 4 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,serv e r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5c 4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-8387 - ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca992 - b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=na t ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,i d =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a 2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chan n el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a 2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=chan n el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=chan n el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel = main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-ch a nnel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=us b redir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr = 0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not sure what you mean with this http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html. Do you want me to update libvirt with these repos on the oVirt-Node based installation? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:10 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: [Users] Host cannot access storage domains actually, looking at this again, it's a libvirt error and it can be related to selinux or
Re: [Users] qemu-img-rhev can't handle -s parameter
On 03.01.2014 13:45, Dafna Ron wrote: yes, there are bugs reported in openstack for the same issue on qemu-kvm: https://bugzilla.redhat.com/show_bug.cgi?id=1027074 https://bugzilla.redhat.com/show_bug.cgi?id=1016896 Hi and thanks, I cannot access https://bugzilla.redhat.com/show_bug.cgi?id=1016896 with my user. Care to sum it up, is there a resolution in sight? Regards, Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Host cannot access storage domains
Redirecting to /bin/systemctl reconfigure vdsmd.service Unknown operation 'reconfigure'. ... seems to me, I should get rid of the ovirt-node iso installation and move to a rpm based install? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:51 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: AW: [Users] Host cannot access storage domains can you run: service vdsmd reconfigure on the second host? On 01/03/2014 02:43 PM, Albl, Oliver wrote: Dafna, yes, the VM starts on the first node, the issues are on the second node only. /etc/libvirt/qemu-sanlock.conf is identical on on both nodes: auto_disk_leases=0 require_lease_for_disks=0 yum updates reports Using yum is not supported... Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:39 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: [Users] Host cannot access storage domains ok, let's try to zoom in on the issue... can you run vm's on the first host or do you have issues only on the second host you added? can you run on both hosts? # egrep -v ^# /etc/libvirt/qemu-sanlock.conf can you run yum update on one of the hosts and see if there are newer packages? Thanks, Dafna On 01/03/2014 02:30 PM, Albl, Oliver wrote: I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C3 8 4 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,ser v e r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5 c 4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-838 7 - ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca99 2 - b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=n a t ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0, i d =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb- a 2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=cha n n el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb- a 2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=cha n n el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=cha n n el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channe l = main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-c h a nnel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=u s b redir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,add r = 0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not
Re: [Users] Host cannot access storage domains
:) no, there are just different ways of dealing with things... don't give up now. lets try to re-install the host, perhaps the original issue cased a configuration problem and a re-install will solve it... On 01/03/2014 02:56 PM, Albl, Oliver wrote: Redirecting to /bin/systemctl reconfigure vdsmd.service Unknown operation 'reconfigure'. ... seems to me, I should get rid of the ovirt-node iso installation and move to a rpm based install? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:51 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: AW: [Users] Host cannot access storage domains can you run: service vdsmd reconfigure on the second host? On 01/03/2014 02:43 PM, Albl, Oliver wrote: Dafna, yes, the VM starts on the first node, the issues are on the second node only. /etc/libvirt/qemu-sanlock.conf is identical on on both nodes: auto_disk_leases=0 require_lease_for_disks=0 yum updates reports Using yum is not supported... Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:39 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: [Users] Host cannot access storage domains ok, let's try to zoom in on the issue... can you run vm's on the first host or do you have issues only on the second host you added? can you run on both hosts? # egrep -v ^# /etc/libvirt/qemu-sanlock.conf can you run yum update on one of the hosts and see if there are newer packages? Thanks, Dafna On 01/03/2014 02:30 PM, Albl, Oliver wrote: I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C3 8 4 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,ser v e r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5 c 4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-838 7 - ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca99 2 - b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=n a t ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0, i d =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb- a 2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=cha n n el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb- a 2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=cha n n el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=cha n n el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channe l = main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-c h a nnel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=u s b redir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,add r = 0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration:
Re: [Users] Host cannot access storage domains
can you run: service vdsmd reconfigure on the second host? On 01/03/2014 02:43 PM, Albl, Oliver wrote: Dafna, yes, the VM starts on the first node, the issues are on the second node only. /etc/libvirt/qemu-sanlock.conf is identical on on both nodes: auto_disk_leases=0 require_lease_for_disks=0 yum updates reports Using yum is not supported... Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:39 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: [Users] Host cannot access storage domains ok, let's try to zoom in on the issue... can you run vm's on the first host or do you have issues only on the second host you added? can you run on both hosts? # egrep -v ^# /etc/libvirt/qemu-sanlock.conf can you run yum update on one of the hosts and see if there are newer packages? Thanks, Dafna On 01/03/2014 02:30 PM, Albl, Oliver wrote: I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C38 4 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,serv e r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5c 4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-8387 - ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca992 - b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=na t ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0,i d =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a 2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=chan n el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb-a 2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=chan n el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=chan n el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channel = main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-ch a nnel=playback,tls-channel=record,tls-channel=smartcard,tls-channel=us b redir,seamless-migration=on -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,bus=pci.0,addr = 0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 libvirt: Lock Driver error : unsupported configuration: Read/write, exclusive access, disks were present, but no leases specified 2014-01-03 13:52:11.306+: shutting down Not sure what you mean with this http://forums.opensuse.org/english/get-technical-help-here/virtualization/492483-cannot-start-libvert-kvm-guests-after-update-tumbleweed.html. Do you want me to update libvirt with these repos on the oVirt-Node based installation? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:10 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: [Users] Host cannot access storage domains actually, looking at this again, it's a libvirt error and it can be related to selinux or
Re: [Users] Host cannot access storage domains
- Original Message - From: Oliver Albl oliver.a...@fabasoft.com To: d...@redhat.com Cc: users@ovirt.org Sent: Friday, January 3, 2014 4:56:33 PM Subject: Re: [Users] Host cannot access storage domains Redirecting to /bin/systemctl reconfigure vdsmd.service Unknown operation 'reconfigure'. /usr/lib/systemd/systemd-vdsmd reconfigure force ... seems to me, I should get rid of the ovirt-node iso installation and move to a rpm based install? Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:51 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: AW: [Users] Host cannot access storage domains can you run: service vdsmd reconfigure on the second host? On 01/03/2014 02:43 PM, Albl, Oliver wrote: Dafna, yes, the VM starts on the first node, the issues are on the second node only. /etc/libvirt/qemu-sanlock.conf is identical on on both nodes: auto_disk_leases=0 require_lease_for_disks=0 yum updates reports Using yum is not supported... Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:39 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: AW: [Users] Host cannot access storage domains ok, let's try to zoom in on the issue... can you run vm's on the first host or do you have issues only on the second host you added? can you run on both hosts? # egrep -v ^# /etc/libvirt/qemu-sanlock.conf can you run yum update on one of the hosts and see if there are newer packages? Thanks, Dafna On 01/03/2014 02:30 PM, Albl, Oliver wrote: I installed both hosts using the oVirt Node ISO image: OS Version: oVirt Node - 3.0.3 - 1.1.fc19 Kernel Version: 3.11.9 - 200.fc19.x86_64 KVM Version: 1.6.1 - 2.fc19 LIBVIRT Version: libvirt-1.1.3.1-2.fc19 VDSM Version: vdsm-4.13.0-11.fc19 Thanks, Oliver -Ursprüngliche Nachricht- Von: Dafna Ron [mailto:d...@redhat.com] Gesendet: Freitag, 03. Jänner 2014 15:24 An: Albl, Oliver Cc: users@ovirt.org Betreff: Re: AW: AW: AW: [Users] Host cannot access storage domains ignore the link :) so searching for this error I hit an old bug and it seemed to be an issue between libvirt/sanlock. https://bugzilla.redhat.com/show_bug.cgi?id=828633 are you using latest packages? On 01/03/2014 02:15 PM, Albl, Oliver wrote: Dafna, Libvirtd.log shows no errors, but VM log shows the following: 2014-01-03 13:52:11.296+: starting up LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name OATEST2 -S -machine pc-1.0,accel=kvm,usb=off -cpu SandyBridge -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=3.0.3-1.1.fc19,serial=30313436-3631-5A43-4A33-3332304C3 8 4 C,uuid=d2bddcdb-a2c8-4c77-b0cf-b83fa3c2a0b6 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/OATEST2.monitor,ser v e r,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=2014-01-03T13:52:11,driftfix=slew -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive if=none,id=drive-ide0-1-0,readonly=on,format=raw,serial= -device ide-cd,bus=ide.1,unit=0,drive=drive-ide0-1-0,id=ide0-1-0 -drive file=/rhev/data-center/mnt/blockSD/7841a1c0-181a-4d43-9a25-b707accb5 c 4 b/images/de7ca992-b1c1-4cb8-9470-2494304c9b69/cbf1f376-23e8-40f3-838 7 - ed299ee62607,if=none,id=drive-virtio-disk0,format=raw,serial=de7ca99 2 - b1c1-4cb8-9470-2494304c9b69,cache=none,werror=stop,rerror=stop,aio=n a t ive -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk0, i d =virtio-disk0,bootindex=1 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channels/d2bddcdb- a 2 c8-4c77-b0cf-b83fa3c2a0b6.com.redhat.rhevm.vdsm,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=cha n n el0,name=com.redhat.rhevm.vdsm -chardev socket,id=charchannel1,path=/var/lib/libvirt/qemu/channels/d2bddcdb- a 2 c8-4c77-b0cf-b83fa3c2a0b6.org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=cha n n el1,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel2,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=3,chardev=charchannel2,id=cha n n el2,name=com.redhat.spice.0 -spice tls-port=5900,addr=0,x509-dir=/etc/pki/vdsm/libvirt-spice,tls-channe l = main,tls-channel=display,tls-channel=inputs,tls-channel=cursor,tls-c h a
Re: [Users] qemu-img-rhev can't handle -s parameter
On 01/03/2014 02:43 PM, Nux! wrote: On 03.01.2014 13:45, Dafna Ron wrote: yes, there are bugs reported in openstack for the same issue on qemu-kvm: https://bugzilla.redhat.com/show_bug.cgi?id=1027074 https://bugzilla.redhat.com/show_bug.cgi?id=1016896 Hi and thanks, I cannot access https://bugzilla.redhat.com/show_bug.cgi?id=1016896 with my user. Care to sum it up, is there a resolution in sight? Regards, Lucian well, there was a decision in virt to no longer skip the -s and prompt an error message which was decided to be the correct way to go. I am adding some people to this, maybe they can help with some workaround for ovirt. -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] qemu-img-rhev can't handle -s parameter
On 03.01.2014 15:17, Dafna Ron wrote: On 01/03/2014 02:43 PM, Nux! wrote: On 03.01.2014 13:45, Dafna Ron wrote: yes, there are bugs reported in openstack for the same issue on qemu-kvm: https://bugzilla.redhat.com/show_bug.cgi?id=1027074 https://bugzilla.redhat.com/show_bug.cgi?id=1016896 Hi and thanks, I cannot access https://bugzilla.redhat.com/show_bug.cgi?id=1016896 with my user. Care to sum it up, is there a resolution in sight? Regards, Lucian well, there was a decision in virt to no longer skip the -s and prompt an error message which was decided to be the correct way to go. I am adding some people to this, maybe they can help with some workaround for ovirt. Thanks, I don't want to appear cheeky, but I did not need the feature for Ovirt. Currently KVM snapshots in Cloudstack are broken as well because the -s went away. I have found that qemu-img-rhev-0.12.1.2-2.355 still has the capability so that's what I'm stuck with on my hypervisor; thought you guys know more. Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] qemu-img-rhev can't handle -s parameter
On Fri, Jan 03, 2014 at 01:34:39PM +, Nux! wrote: Hello, I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s parameter, but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm) errors out with: convert: invalid option -- 's' Could you provide more context, preferably with the traceback from vdsm.log? ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] qemu-img-rhev can't handle -s parameter
On 03.01.2014 16:29, Dan Kenigsberg wrote: On Fri, Jan 03, 2014 at 01:34:39PM +, Nux! wrote: Hello, I used qemu-img-rhev-0.12.1.2-2.355.el6 successfully with -s parameter, but now qemu-img-rhev-0.12.1.2-2.415.el6 (latest atm) errors out with: convert: invalid option -- 's' Could you provide more context, preferably with the traceback from vdsm.log? Hello Dan, As stated previously I'm using this with Cloudstack, not Ovirt. The lack of -s switch breaks snapshot functionality, stock EL6 qemu-img worked fine with previous EL6 releases afaik. Current stock qemu-img as well as qemu-img-rhev are missing this. qemu-img-rhev-0.12.1.2-2.355 is the only recent version that I found which can be used; qemu-img-rhev-0.12.1.2-2.355 lost this feature weirdly. Sorry if I'm hijacking the ovirt-users with non-ovirt issue. Should I open a bug in the bz? Lucian -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Creation of preallocated disk with Gluster replication
Do you happen to notice what is consuming CPU? When I check with top, glusterfs and glusterfsd are the only process who use a significant amount of CPU. Load average is between 5 and 6, and I don't have any started VM. Since the same cluster does both virtualization and storage, a GigE network might get saturated very quickly. Is it possible to separate out the management and data/gluster traffic in this setup? Unfortunately, it's not possible. I only have two hosts, both for virtualization and storage. Why does glusterfs use so much CPU ? About the network traffic, the creation of a pre-allocated disk is not something which absolutely needs to be fast : if it takes 5 minutes, well... it takes 5 minutes. I guess that if there's a way to limit the bandwidth available for glusterfs, it'll still have an impact on production because glusterfs and VM will be in competition for bandwidth, right ? Is there a way to limit the bandwidth only for the creation of a pre-allocated disk ? Thank you, Regards, Grégoire Leroy ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] all hosts are Non responsive
When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
check iptables. in any case, you have a communication problem between the engine and the hosts. when engine cannot get status on the vdsm, hosts will move to non-responsive. On 01/03/2014 06:32 PM, Zach Underwood wrote: When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
I ran iptables -F on the engine and host no luck. The engine and the two hosts are on the same /24 layer 2 network. I can ping both ways. On Fri, Jan 3, 2014 at 1:33 PM, Dafna Ron d...@redhat.com wrote: check iptables. in any case, you have a communication problem between the engine and the hosts. when engine cannot get status on the vdsm, hosts will move to non-responsive. On 01/03/2014 06:32 PM, Zach Underwood wrote: When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
Here are the two errors from engine.log 2014-01-03 13:40:19,348 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-78) Command GetCapabilitiesVDS execution failed. Exception: VDSNetworkException: java.net.ConnectException: Connection refused 2014-01-03 13:40:20,459 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-86) Command GetCapabilitiesVDS execution failed. Exception: VDSNetworkException: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target I dont have a vdsm service on the nodes. I see a vhostmd is that the same? On Fri, Jan 3, 2014 at 1:39 PM, Dafna Ron d...@redhat.com wrote: before you wrote that you can't ping but you can ssh so that's a progress :) look at the engine log and check the vdsm service status on the host (you can even restart it) On 01/03/2014 06:37 PM, Zach Underwood wrote: I ran iptables -F on the engine and host no luck. The engine and the two hosts are on the same /24 layer 2 network. I can ping both ways. On Fri, Jan 3, 2014 at 1:33 PM, Dafna Ron d...@redhat.com mailto: d...@redhat.com wrote: check iptables. in any case, you have a communication problem between the engine and the hosts. when engine cannot get status on the vdsm, hosts will move to non-responsive. On 01/03/2014 06:32 PM, Zach Underwood wrote: When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using setenforce 0. Let me know if this helps. All the best, Oliver Von: users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] Im Auftrag von Zach Underwood Gesendet: Freitag, 03. Jänner 2014 19:32 An: users@ovirt.org Betreff: [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My websitehttp://zachunderwood.me My photoshttp://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
disable slinux=no change On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.comwrote: Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using “setenforce 0”. Let me know if this helps. All the best, Oliver *Von:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] *Im Auftrag von *Zach Underwood *Gesendet:* Freitag, 03. Jänner 2014 19:32 *An:* users@ovirt.org *Betreff:* [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
what do you mean you don't have vdsm service? did your host installation succeed? On 01/03/2014 06:44 PM, Zach Underwood wrote: Here are the two errors from engine.log 2014-01-03 13:40:19,348 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-78) Command GetCapabilitiesVDS execution failed. Exception: VDSNetworkException: java.net.ConnectException: Connection refused 2014-01-03 13:40:20,459 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.GetCapabilitiesVDSCommand] (DefaultQuartzScheduler_Worker-86) Command GetCapabilitiesVDS execution failed. Exception: VDSNetworkException: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target I dont have a vdsm service on the nodes. I see a vhostmd is that the same? On Fri, Jan 3, 2014 at 1:39 PM, Dafna Ron d...@redhat.com mailto:d...@redhat.com wrote: before you wrote that you can't ping but you can ssh so that's a progress :) look at the engine log and check the vdsm service status on the host (you can even restart it) On 01/03/2014 06:37 PM, Zach Underwood wrote: I ran iptables -F on the engine and host no luck. The engine and the two hosts are on the same /24 layer 2 network. I can ping both ways. On Fri, Jan 3, 2014 at 1:33 PM, Dafna Ron d...@redhat.com mailto:d...@redhat.com mailto:d...@redhat.com mailto:d...@redhat.com wrote: check iptables. in any case, you have a communication problem between the engine and the hosts. when engine cannot get status on the vdsm, hosts will move to non-responsive. On 01/03/2014 06:32 PM, Zach Underwood wrote: When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org mailto:Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
after reading logs on the node I found this vdsm vds error xml-rpc handler exception I installed the node from ISO named ovirt-node-iso-3.0.3-1.1.vdsm.fc19 On Fri, Jan 3, 2014 at 1:55 PM, Zach Underwood zunder1...@gmail.com wrote: disable slinux=no change On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.comwrote: Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using “setenforce 0”. Let me know if this helps. All the best, Oliver *Von:* users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] *Im Auftrag von *Zach Underwood *Gesendet:* Freitag, 03. Jänner 2014 19:32 *An:* users@ovirt.org *Betreff:* [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
is the service up? if vdsm is down or not installed than the engine will set host status as non-responsive. it seems as if there might have been an error during the host installation? please look at the engine log and you should also have deployment logs and see if everything was successful. On 01/03/2014 06:59 PM, Zach Underwood wrote: after reading logs on the node I found this vdsm vds error xml-rpc handler exception I installed the node from ISO named ovirt-node-iso-3.0.3-1.1.vdsm.fc19 On Fri, Jan 3, 2014 at 1:55 PM, Zach Underwood zunder1...@gmail.com mailto:zunder1...@gmail.com wrote: disable slinux=no change On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.com mailto:oliver.a...@fabasoft.com wrote: Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using “setenforce 0”. Let me know if this helps. All the best, Oliver *Von:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org [mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org] *Im Auftrag von *Zach Underwood *Gesendet:* Freitag, 03. Jänner 2014 19:32 *An:* users@ovirt.org mailto:users@ovirt.org *Betreff:* [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
oh! and Oliver had issues before which were solved by a reboot of the host - so were they rebooted after the installation? On 01/03/2014 07:03 PM, Dafna Ron wrote: is the service up? if vdsm is down or not installed than the engine will set host status as non-responsive. it seems as if there might have been an error during the host installation? please look at the engine log and you should also have deployment logs and see if everything was successful. On 01/03/2014 06:59 PM, Zach Underwood wrote: after reading logs on the node I found this vdsm vds error xml-rpc handler exception I installed the node from ISO named ovirt-node-iso-3.0.3-1.1.vdsm.fc19 On Fri, Jan 3, 2014 at 1:55 PM, Zach Underwood zunder1...@gmail.com mailto:zunder1...@gmail.com wrote: disable slinux=no change On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.com mailto:oliver.a...@fabasoft.com wrote: Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using “setenforce 0”. Let me know if this helps. All the best, Oliver *Von:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org [mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org] *Im Auftrag von *Zach Underwood *Gesendet:* Freitag, 03. Jänner 2014 19:32 *An:* users@ovirt.org mailto:users@ovirt.org *Betreff:* [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
I restarted the node and the engine and no change. Here is a list on the services on the node(sorry for the screenshot I am using idrac) [image: Inline image 1] On Fri, Jan 3, 2014 at 2:04 PM, Dafna Ron d...@redhat.com wrote: oh! and Oliver had issues before which were solved by a reboot of the host - so were they rebooted after the installation? On 01/03/2014 07:03 PM, Dafna Ron wrote: is the service up? if vdsm is down or not installed than the engine will set host status as non-responsive. it seems as if there might have been an error during the host installation? please look at the engine log and you should also have deployment logs and see if everything was successful. On 01/03/2014 06:59 PM, Zach Underwood wrote: after reading logs on the node I found this vdsm vds error xml-rpc handler exception I installed the node from ISO named ovirt-node-iso-3.0.3-1.1.vdsm.fc19 On Fri, Jan 3, 2014 at 1:55 PM, Zach Underwood zunder1...@gmail.commailto: zunder1...@gmail.com wrote: disable slinux=no change On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.com mailto:oliver.a...@fabasoft.com wrote: Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using “setenforce 0”. Let me know if this helps. All the best, Oliver *Von:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org [mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org] *Im Auftrag von *Zach Underwood *Gesendet:* Freitag, 03. Jänner 2014 19:32 *An:* users@ovirt.org mailto:users@ovirt.org *Betreff:* [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me image.png___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] all hosts are Non responsive
please re-install the hosts - I think your installation must have failed. On 01/03/2014 07:18 PM, Zach Underwood wrote: I restarted the node and the engine and no change. Here is a list on the services on the node(sorry for the screenshot I am using idrac) Inline image 1 On Fri, Jan 3, 2014 at 2:04 PM, Dafna Ron d...@redhat.com mailto:d...@redhat.com wrote: oh! and Oliver had issues before which were solved by a reboot of the host - so were they rebooted after the installation? On 01/03/2014 07:03 PM, Dafna Ron wrote: is the service up? if vdsm is down or not installed than the engine will set host status as non-responsive. it seems as if there might have been an error during the host installation? please look at the engine log and you should also have deployment logs and see if everything was successful. On 01/03/2014 06:59 PM, Zach Underwood wrote: after reading logs on the node I found this vdsm vds error xml-rpc handler exception I installed the node from ISO named ovirt-node-iso-3.0.3-1.1.vdsm.fc19 On Fri, Jan 3, 2014 at 1:55 PM, Zach Underwood zunder1...@gmail.com mailto:zunder1...@gmail.com mailto:zunder1...@gmail.com mailto:zunder1...@gmail.com wrote: disable slinux=no change On Fri, Jan 3, 2014 at 1:51 PM, Albl, Oliver oliver.a...@fabasoft.com mailto:oliver.a...@fabasoft.com mailto:oliver.a...@fabasoft.com mailto:oliver.a...@fabasoft.com wrote: Zach, I had a similar problem. I temporarily disabled SELinux on the hosts using “setenforce 0”. Let me know if this helps. All the best, Oliver *Von:*users-boun...@ovirt.org mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org [mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org mailto:users-boun...@ovirt.org] *Im Auftrag von *Zach Underwood *Gesendet:* Freitag, 03. Jänner 2014 19:32 *An:* users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org mailto:users@ovirt.org *Betreff:* [Users] all hosts are Non responsive When I try to activate a host to the engine I get the error non responsive. I can ping the hosts but I cant connect with ssh. oVirt Engine Version: 3.3.2-1.el6 ovirt-node-iso-3.0.3-1.1.vdsm.fc19 -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me ___ Users mailing list Users@ovirt.org mailto:Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Dafna Ron -- Zach Underwood (RHCE,RHCSA,RHCT,UACA) My website http://zachunderwood.me My photos http://zunder1990.openphoto.me -- Dafna Ron ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Almost there... I can't bring up a VM
Hi. I need some help to troubleshoot this. I can't find a log showing any hint for me to go forward with it. Any help is appreciated. Will Hi, Running oVirt 3.3.2-1.el6 on CentOS 6.5 I have oVirt installed on a test host (ovirt1) and two test visualization hosts (onode1, onode2) using GlusterFS. I have GlusterFS available on both onode1 and 2. Storage domain, networks are defined, ISO is uploaded to the ISO domain. I have been trying to create VM but all I get is a black spice console I'm not able to tell what's going on. I turned off all iptables also. I looked at /var/log/libvirt/qemu/testvm04.log. I got only the starting up line and a few lines for Spice. I also looked at engine.log for ERROR can anyone shed some light on this? I feel like I'm almost there to use oVirt instead of VMware for the next project. ERROR lines in engine.log: -- 2014-01-02 12:31:40,893 ERROR [org.ovirt.engine.core.vdsbroker.gluster.GlusterTasksListVDSCommand] (DefaultQuartzScheduler_Worker-76) Command GlusterTasksListVDS execution failed. Exception: VDSNetworkException: org.apache.xmlrpc.XmlRpcException: type 'exceptions.Exception':method glusterTasksList is not supported [org.ovirt.engine.core.vdsbroker.gluster.GlusterTasksListVDSCommand] (DefaultQuartzScheduler_Worker-76) FINISH, GlusterTasksListVDSCommand, log id: 3fa83c4f 2014-01-02 12:31:40,894 ERROR [org.ovirt.engine.core.utils.timer.SchedulerUtilQuartzImpl] (DefaultQuartzScheduler_Worker-76) Failed to invoke scheduled method gluster_async_task_poll_event: java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source) [:1.7.0_45] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_45] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_45] at org.ovirt.engine.core.utils.timer.JobWrapper.execute(JobWrapper.java:60) [scheduler.jar:] at org.quartz.core.JobRunShell.run(JobRunShell.java:213) [quartz.jar:] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557) [quartz.jar:] Caused by: org.ovirt.engine.core.common.errors.VdcBLLException: VdcBLLException: org.ovirt.engine.core.vdsbroker.vdsbroker.VDSNetworkException: org.apache.xmlrpc.XmlRpcException: type 'exceptions.Exception':method glusterTasksList is not supported (Failed with error VDS_NETWORK_ERROR and code 5022) at org.ovirt.engine.core.bll.VdsHandler.handleVdsResult(VdsHandler.java:122) [bll.jar:] at org.ovirt.engine.core.bll.VDSBrokerFrontendImpl.RunVdsCommand(VDSBrokerFrontendImpl.java:33) [bll.jar:] at org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService.runVdsCommand(GlusterTasksService.java:60) [bll.jar:] at org.ovirt.engine.core.bll.gluster.tasks.GlusterTasksService.getTaskListForCluster(GlusterTasksService.java:28) [bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterTasksSyncJob.updateTasksInCluster(GlusterTasksSyncJob.java:67) [bll.jar:] at org.ovirt.engine.core.bll.gluster.GlusterTasksSyncJob.updateGlusterAsyncTasks(GlusterTasksSyncJob.java:56) [bll.jar:] ... 6 more [org.ovirt.engine.core.bll.SetVmTicketCommand] (ajp--127.0.0.1-8702-8) [1d0c71de] Running command: SetVmTicketCommand internal: false. Entities affected : ID: b4867838-561e-491e-bb00-5c2ce3828b83 Type: VM [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-8) [1d0c71de] START, SetVmTicketVDSCommand(HostName = onode1., HostId = 5145362f-0f97-4edf-a23f-592ff2c74d3f, vmId=b4867838-561e-491e-bb00-5c2ce3828b83, ticket=IpVcENDWEgVN, validTime=120,m userName=admin@internal, userId=fdfc627c-d875-11e0-90f0-83df133b58cc), log id: 36bcf5a3 [org.ovirt.engine.core.vdsbroker.vdsbroker.SetVmTicketVDSCommand] (ajp--127.0.0.1-8702-8) [1d0c71de] FINISH, SetVmTicketVDSCommand, log id: 36bcf5a3 [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp--127.0.0.1-8702-8) [1d0c71de] Correlation ID: 1d0c71de, Call Stack: null, Custom Event ID: -1, Message: user admin@internal initiated console session for VM testvm04 qemu log: LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin QEMU_AUDIO_DRV=spice /usr/libexec/qemu-kvm -name testvm04 -S -M rhel6.4.0 -cpu Westmere -enable-kvm -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid b4867838-561e-491e-bb00-5c2ce3828b83 -smbios type=1,manufacturer=oVirt,product=oVirt Node,version=6-5.el6.centos.11.2,serial=42294BD4-962B-0F5E-9F28-0A96F491CB56,uuid=b4867838-561e-491e-bb00-5c2ce3828b83 -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/testvm04.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc
Re: [Users] engine reports and dwh setup in 3.3.2
On Wed, Dec 25, 2013 at 1:00 AM, Yaniv Dary wrote: Hi, We have found a few blockers on the setup of dwh and reports. We hope to resolve the issues in the next few days. If you restore your environment using the backups, you will be able to upgrade. I've put a note to let you know when new packages are available. Ok, I'll wait good news about these items Just a question: when you write about blockers, are you referring to updates only or also to new setups directly made in 3.3.2 environments? thanks in advance, Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Another issue - VM Networking
I've run into another issue with Ovirt 3.3.2. We have a 2 node VM cluster with Fibre Channel storage. After upgrade everything to FC 19 and installing Ovirt 3.3 from scratch one of the nodes has network issues. The issue is that when we start a VM on the node, the VM cannot access the network. No ping, no ssh, nothing. However, if I try to ping the VM, I can see the ICMP traffic on the ethernet VLAN interface and the bridge interface. I cannot see any traffic on the VM tap interface. If we migrate the VM from the faulty node to the other node that works, and then back, the network will start to work. However, if the VM is shut down the network will fail again when it's booted on the faulty node. Does anyone have any ideas about this particular problem? Thanks, Dan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Network issues - Bonding
Hello All, A little bit ago I wrote an email about network issues I was having. I found the problem... On the VM host, I had a bond set up between two network interfaces. The bond mode was set to mode 1 (active/passive). However when I look at the bond on the box, I get this: [root@node02 bonding]# cat bond4 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 0 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: em2 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: d4:ae:52:6d:c8:cc Slave queue ID: 0 Slave Interface: em3 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: d4:ae:52:6d:c8:ce Slave queue ID: 0 Somehow, the OS is not setting the bonding mode right. I verified that it was set to mode 1 in /etc/sysconfig/network-scripts/ifcfe-bond4 When I take the bond away, the host network works perfectly on both of the formerly bonded interfaces. So again, if anyone has any ideas, I'm open to suggestions. Thanks, Dan ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
