Re: [Users] oVirt 3.3/F19 - Windows guest unable to access network
On 18-9-2013 23:08, SULLIVAN, Chris (WGK) wrote: Hi, I'm having network issues with a Windows Server 2008 R2 guest running on an F19 host. The guest has a static configuration and is able to ping itself and the host it is running on, however cannot ping the gateway, any other hosts on the local network, or external hosts. A RHEL 6.4 guest on the same host with a similar static configuration works normally. Iptables/firewalld on the host are switched off and the network definitions in the XML for each VM (Windows/RHEL) are the same. The virtio network drivers are installed in the guest. The guest was created from a Win 2008 R2 template, which was created from a VM imported from oVirt 3.2. Software versions below. Just to be sure, iptables/firewalld!=Windows Firewall. Is there a rule in the windows firewall to allow ping or is it disabled? Are there any manual configuration steps required on the host to support Windows guests? Are there any particular diagnostic steps I could take to try and narrow down the cause? Don't think so, just converted a Windows2008R2 datacenter guest from Vmware to oVirt and it ran, after adding virtio drivers or using e1000 and/or ide disks. Versions: -oVirt 3.3.0-4 -F19 3.10.11-200 -QEMU 1.4.2-9 -Libvirt 1.1.2-1 -VDSM 4.12.1-2 -virtio-win 0.1-52 Your problem looks like the problem René had with his Solaris guest, its a recent thread. Turned out that setting -cpu Nehalem by ovirt caused networking in the Solaris guest to fail. Don't think this is your problem though since lots of people run Windows guest without problems. Regards, Joop ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] API vm.statistics : memory.used value when changing balloon of VM
Hello
Context : oVirt Engine Version: 3.3.0-4.el6
Hypervisor VDSM : vdsm.x86_64 - 4.12.1-2.el6
A vm :
- Memory Size : 1024 Mo
- Physical Memory Guaranteed : 128 Mo ;)
- Memory balloon device enabled
the vm is running with nearly no activity to have a constant memory used
Testcase
1 : Initial run No change to the balloon
Total Memory = Balloon 1024 Mo
Data from vdsClient getVmStats
balloonInfo = {'balloon_max': '1048576', 'balloon_min': '131072',
'balloon_target': '1048576', 'balloon_cur': '1048576'}
memoryStats = {'swap_out': '0', 'majflt': '0', 'mem_free': '920308',
'swap_in': '0', 'pageflt': '7', 'mem_total': '1020576', 'mem_unused':
'863500'}
Here : mem_total - mem_unused = 157076 correct
Data get from api (REST or Python : statistics.'memory.used')
Memory used 128849018.0 = 123 Mo
--
If i modify the balloon by the command vdsClient setBalloonTarget 524288
(512*1024)
i got
vds
balloonInfo = {'balloon_max': '1048576', 'balloon_min': '131072',
'balloon_target': '524288', 'balloon_cur': '524288'}
memoryStats = {'swap_out': '0', 'majflt': '0', 'mem_free': '396044',
'swap_in': '0', 'pageflt': '7', 'mem_total': '496288', 'mem_unused':
'339228'}
mem_total - mem_unused = 157076 correct value
API.statistics
Memory used = 665719930.0 = 635 Mo == (512+123)
--
Setting a balloon to 262144 (256*1024)
balloonInfo = {'balloon_max': '1048576', 'balloon_min': '131072',
'balloon_target': '262144', 'balloon_cur': '262144'}
memoryStats = {'swap_out': '0', 'majflt': '0', 'mem_free': '133916',
'swap_in': '0', 'pageflt': '6', 'mem_total': '234144', 'mem_unused':
'76224'}
mem_total - mem_unused = correct value
API.statistics:
Memory used = 934155386.0 = 891 Mo (768+123)
To get the correct value from the api i need to fdo [ (Memory Used/1024)-
(Balloon Max - Balloon Current) ] / 1024
-
Of course display in manager is also wrong
No Balloon parameter modified
http://screencast.com/t/rGhKJgeB2ol
Balloon 512
http://screencast.com/t/L7geTfnI
Balloon 256
http://screencast.com/t/8jBllKXtGt7
Should we consider this as a bug ?
Do you plan to change the formula to compupte the memory used ?
Regards
Hervé Leclerc
CTO
Alter Way
1, rue royale
9 ème étage
92210 St Cloud
+33 1 78152407
+33 6 83979598
http://www.alterway.fr/signatures/url/1
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
[Users] virtio-scsi Windows/Linux VM performance
Hello, a few weeks ago I started investigating ovirt as an alterantive to a well known commercial virtualization center. Up to now I got great support through this mailing list. Thanks for that. With all the technical things sorted out I'm getting slowly to the performance related stuff. Lets start with a small explanation to the test landscape. I have two hypervisor machines (Intel Nehalem generation) that are attached to a NFS server via infiniband IPoIB connected mode (MTU 33000). They run Fedora 19 (kernel 3.11) and through newest repositories qemu version 1.6.0 - 7.fc19. To get an idea about the overhead of the VM disk layer I run a not very scientific direct I/O read test on the hypervisor onto a image file that resides on the NFS share. Access pattern is random, I use one thread, blocksize is 1K and the file (image that belongs to a VM) is fully cached on the NFS server. So no disk activity is going on in the NFS server but block reads are always sent over the network. The numbers read 13 MB/sec or 13000 IOs/sec. Just take that as a very synthetic reference value for the latency of the NFS layer. Now I relocate my test into one of the running VMs. Again a Fedora 19 that uses virtio-scsi based disk images on the NFS. The IOs drop to 9.5MB/sek or 9500 IOs/sec. I understand that virtualization costs performance so I'm still statisfied. With Windows 7 VM and the virtio-0.1-65 driver I get a real bad experience. Only 2MB/sek or 2000 IOs/sec left. That is not what one would expect. I read through articles/papers about the different approaches in the last years to increase VM IO performance: virtio-data-plane, virto-blk, ... But I'm not yet searching to increase the overall performance I'm just trying to get biggest mistakes sorted out. With the same devices and on the same platform I expect the performance of both VMs to be in a similar range and not a difference by a factor of 4-5. Any ideas? Markus Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Ãber das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Ovirt-engine
Hello Everyone , Can I use ovirt-engine to mange my already installed/running kvm host/guest ? If yes can someone guide me to the documentation/howto please ? Thanks Shantanu ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt-engine
Von: users-boun...@ovirt.org [users-boun...@ovirt.org] im Auftrag von kumar shantanu [k.shantanu2...@gmail.com] Gesendet: Donnerstag, 19. September 2013 14:49 An: users Betreff: [Users] Ovirt-engine Hello Everyone , Can I use ovirt-engine to mange my already installed/running kvm host/guest ? If yes can someone guide me to the documentation/howto please ? Thanks Shantanu Hello, welcome to the list. ovirt uses a central management server (ovirt-engine) that manages the machine definition in a database. It controls VMs on several hypervisor hosts with this information. To get a VM into the database you have to import it. virt-v2v helps me for VMWare sources and it should do the trick for you. Find more info in chapter A.1.2.4 of this page: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Administration_Guide/virt-v2v-scripts.html Markus Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Ãber das Internet versandte E-Mails können unter fremden Namen erstellt oder manipuliert werden. Deshalb ist diese als E-Mail verschickte Nachricht keine rechtsverbindliche Willenserklärung. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln Vorstand: Kadir Akin Dr. Michael Höhnerbach Vorsitzender des Aufsichtsrates: Hans Kristian Langva Registergericht: Amtsgericht Köln Registernummer: HRB 52 497 This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. e-mails sent over the internet may have been written under a wrong name or been manipulated. That is why this message sent as an e-mail is not a legally binding declaration of intention. Collogia Unternehmensberatung AG Ubierring 11 D-50678 Köln executive board: Kadir Akin Dr. Michael Höhnerbach President of the supervisory board: Hans Kristian Langva Registry office: district court Cologne Register number: HRB 52 497 ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Exception: ValueError(invalid literal for int() with base 10: ' ', )
Hmmm, I'm beginning to suspect the LSI MegaRaid chips.
I replaced the SSD of the first node with a brand new Samsung 256GB SSD and the
second node with a 1TB HDD.
When I change the SWAP size on both nodes to 4GB, it fails to install the
bootloader.
When I leave everything on default and just continue the steps, I get an error
30 read-only filesystem on BOTH nodes.
When I choose Other drive and select /dev/sda, I get the ValueError exception.
So I'm kinda stuck :-
Our RAID chip is LSI 2108 SAS
Kind regards,
Jorick Astrego
-Original Message-
From: Jorick Astrego j.astr...@netbulae.eu
To: Fabian Deutsch fabi...@redhat.com
Cc: users@ovirt.org
Date: 19/09/2013 12:53
Subject: Re: [Users] Exception: ValueError(invalid literal for int() with
base 10: ' ', )
Hi,
I'm using ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso and I tried reproducing on
two nodes. I thought maybe the first node's SSD had failed.
See screenshots attached (they are very small).
As the Local disk first only reported 1GB, i used Other device /dev/sda and
got the ValueError (xxx_144.png).
When using Local disk, I get a 'Read-only file system' error. (xxx_145.png)
This is on two identical nodes with a SSD connected through LSI MegaRAID. I
could try it without RAID, but I'll have to visit the datacenter and reflash
the LSI firmware for this.
Both nodes had an older 2.6 node image running on it before.
After a full RAID re-initialization that produced no errors, I now get yet
another faillure:
Exception: RuntimeError('Failed to set install bootloader'.) (xxx_147.png)
Can it be the SSD or RAID controller? I could swap out the SSD for a 2.5 hdd
to test it out.
Thanks in advance!
Jorick Astrego
Netbulae B.V.
-Original Message-
From: Fabian Deutsch fabi...@redhat.com
To: Jorick Astrego j.astr...@netbulae.eu
Cc: users@ovirt.org
Date: 18/09/2013 15:49
Subject: Re: [Users] Exception: ValueError(invalid literal for int() with
base 10: ' ', )
Hey,
Am Mittwoch, den 18.09.2013, 15:35 +0200 schrieb Jorick Astrego:
I'm trying to deploy the ovirt node 3.0.1-1.0.2 image. Because we only
have a small SSD and don't need overcommit I changed the swap file size
to a smaller value.
While installing I now get the following error and have to reboot:
Exception: ValueError(invalid literal for int() with base 10: ' ',)
I tried to reproduce this problem but couldn't trigger it using:
1. Enter the storage sizes page
2. Changed the swap value to 100 (allowed value depends on your hosts
mem size)
3. Saved page, went through the next pages and installed
Could you explain in detail how you triggered this problem?
And are you using the fc19 or el6 iso?
Greetings
fabian
If I don't change the value of the swap, I get a message that the
installer is unable to format/partition the disk.
Kind regards,
Jorick Astrego
___
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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Exception: ValueError(invalid literal for int() with base 10: ' ', )
Am Donnerstag, den 19.09.2013, 15:12 +0200 schrieb Jorick Astrego:
Hmmm, I'm beginning to suspect the LSI MegaRaid chips.
I replaced the SSD of the first node with a brand new Samsung 256GB SSD and
the second node with a 1TB HDD.
When I change the SWAP size on both nodes to 4GB, it fails to install the
bootloader.
When I leave everything on default and just continue the steps, I get an
error 30 read-only filesystem on BOTH nodes.
When I choose Other drive and select /dev/sda, I get the ValueError exception.
So I'm kinda stuck :-
Our RAID chip is LSI 2108 SAS
Hey Jorick,
thanks for the informations from this and your last e-mail.
I think we need some deeper debugging, could you please do the following
to get more debugging informations:
1. Boot the ISO as usual
2. When the installer TUI comes up, press F and drop to a shell
3. Set a password for root
4. Now run: ovirt-node-installer --debug
This will run the installer in debug mode (writing tons of infos
to /var/log/ovirt-node.debug.log).
5. Continue the installation as usual until you reach a problem, then:
6. Switch to a second console and login (the setup tui should come up)
7. Drop to shell by pressing F2
8. Please send the files
* /var/log/ovirt-node.debug.log
* /var/log/ovirt.log
* /tmp/ovirt.log (if available)
That would really help us to find out what the problem is.
I think we should also open a bug for this.
Thanks and greetings
fabian
Kind regards,
Jorick Astrego
-Original Message-
From: Jorick Astrego j.astr...@netbulae.eu
To: Fabian Deutsch fabi...@redhat.com
Cc: users@ovirt.org
Date: 19/09/2013 12:53
Subject: Re: [Users] Exception: ValueError(invalid literal for int() with
base 10: ' ', )
Hi,
I'm using ovirt-node-iso-3.0.1-1.0.2.vdsm.fc19.iso and I tried reproducing
on two nodes. I thought maybe the first node's SSD had failed.
See screenshots attached (they are very small).
As the Local disk first only reported 1GB, i used Other device /dev/sda and
got the ValueError (xxx_144.png).
When using Local disk, I get a 'Read-only file system' error. (xxx_145.png)
This is on two identical nodes with a SSD connected through LSI MegaRAID. I
could try it without RAID, but I'll have to visit the datacenter and
reflash the LSI firmware for this.
Both nodes had an older 2.6 node image running on it before.
After a full RAID re-initialization that produced no errors, I now get yet
another faillure:
Exception: RuntimeError('Failed to set install bootloader'.) (xxx_147.png)
Can it be the SSD or RAID controller? I could swap out the SSD for a 2.5
hdd to test it out.
Thanks in advance!
Jorick Astrego
Netbulae B.V.
-Original Message-
From: Fabian Deutsch fabi...@redhat.com
To: Jorick Astrego j.astr...@netbulae.eu
Cc: users@ovirt.org
Date: 18/09/2013 15:49
Subject: Re: [Users] Exception: ValueError(invalid literal for int()
with base 10: ' ', )
Hey,
Am Mittwoch, den 18.09.2013, 15:35 +0200 schrieb Jorick Astrego:
I'm trying to deploy the ovirt node 3.0.1-1.0.2 image. Because we only
have a small SSD and don't need overcommit I changed the swap file size
to a smaller value.
While installing I now get the following error and have to reboot:
Exception: ValueError(invalid literal for int() with base 10: ' ',)
I tried to reproduce this problem but couldn't trigger it using:
1. Enter the storage sizes page
2. Changed the swap value to 100 (allowed value depends on your hosts
mem size)
3. Saved page, went through the next pages and installed
Could you explain in detail how you triggered this problem?
And are you using the fc19 or el6 iso?
Greetings
fabian
If I don't change the value of the swap, I get a message that the
installer is unable to format/partition the disk.
Kind regards,
Jorick Astrego
___
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
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt-engine
Hello Markus, Thanks for coming back so quickly. I will read the document shortly. In the mean time my kvm hypervisor is already running and it's attached to iscsi storage. Do I need to convert all machines ? or I can simply mange all the stuff through ovirt-engine like I am managing with virt-manager for now. On Thu, Sep 19, 2013 at 6:33 PM, Markus Stockhausen stockhau...@collogia.de wrote: Von: users-boun...@ovirt.org [users-boun...@ovirt.org] im Auftrag von kumar shantanu [k.shantanu2...@gmail.com] Gesendet: Donnerstag, 19. September 2013 14:49 An: users Betreff: [Users] Ovirt-engine Hello Everyone , Can I use ovirt-engine to mange my already installed/running kvm host/guest ? If yes can someone guide me to the documentation/howto please ? Thanks Shantanu Hello, welcome to the list. ovirt uses a central management server (ovirt-engine) that manages the machine definition in a database. It controls VMs on several hypervisor hosts with this information. To get a VM into the database you have to import it. virt-v2v helps me for VMWare sources and it should do the trick for you. Find more info in chapter A.1.2.4 of this page: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Administration_Guide/virt-v2v-scripts.html Markus ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt-engine
On Thu, 2013-09-19 at 20:00 +0530, kumar shantanu wrote: Hello Markus, Thanks for coming back so quickly. I will read the document shortly. In the mean time my kvm hypervisor is already running and it's attached to iscsi storage. Do I need to convert all machines ? or I can simply mange all the stuff through ovirt-engine like I am managing with virt-manager for now. Your hypervisor must be CentOS 6 or Fedora 18/19 in order to be able to manage it with oVirt (other Linux distributions are still a wip). As oVirt has a totally different concept as virt-manager you have to import your machines into oVirt. As Markus already wrote this can be done using virt-v2v. Regards, René On Thu, Sep 19, 2013 at 6:33 PM, Markus Stockhausen stockhau...@collogia.de wrote: Von: users-boun...@ovirt.org [users-boun...@ovirt.org] im Auftrag von kumar shantanu [k.shantanu2...@gmail.com] Gesendet: Donnerstag, 19. September 2013 14:49 An: users Betreff: [Users] Ovirt-engine Hello Everyone , Can I use ovirt-engine to mange my already installed/running kvm host/guest ? If yes can someone guide me to the documentation/howto please ? Thanks Shantanu Hello, welcome to the list. ovirt uses a central management server (ovirt-engine) that manages the machine definition in a database. It controls VMs on several hypervisor hosts with this information. To get a VM into the database you have to import it. virt-v2v helps me for VMWare sources and it should do the trick for you. Find more info in chapter A.1.2.4 of this page: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization_for_Servers/2.2/html/Administration_Guide/virt-v2v-scripts.html Markus ___ 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
[Users] Ovirt 3.3 Fedora 19 add gluster storage permissions error
Hello,
New Ovirt 3.3 install on Fedora 19.
When I try to add a gluster storage domain I get the following:
*UI error:*
*Error while executing action Add Storage Connection: Permission settings
on the specified path do not allow access to the storage.*
*Verify permission settings on the specified storage path.*
*VDSM logs contain:*
Thread-393::DEBUG::2013-09-19
11:59:42,399::BindingXMLRPC::177::vds::(wrapper) client [10.0.0.34]
Thread-393::DEBUG::2013-09-19
11:59:42,399::task::579::TaskManager.Task::(_updateState)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state init -
state preparing
Thread-393::INFO::2013-09-19
11:59:42,400::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='----', conList=[{'port': '',
'connection': '192.168.1.1:/rep2-virt', 'iqn': '', 'portal': '', 'user':
'', 'vfs_type': 'glusterfs', 'password': '**', 'id':
'----'}], options=None)
Thread-393::DEBUG::2013-09-19
11:59:42,405::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n
/usr/bin/mount -t glusterfs 192.168.1.1:/rep2-virt
/rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)
Thread-393::DEBUG::2013-09-19
11:59:42,490::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n
/usr/bin/umount -f -l /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'
(cwd None)
Thread-393::ERROR::2013-09-19
11:59:42,505::hsm::2382::Storage.HSM::(connectStorageServer) Could not
connect to storageServer
Traceback (most recent call last):
File /usr/share/vdsm/storage/hsm.py, line 2379, in connectStorageServer
conObj.connect()
File /usr/share/vdsm/storage/storageServer.py, line 227, in connect
raise e
StorageServerAccessPermissionError: Permission settings on the specified
path do not allow access to the storage. Verify permission settings on the
specified storage path.: 'path =
/rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'
Thread-393::DEBUG::2013-09-19
11:59:42,506::hsm::2396::Storage.HSM::(connectStorageServer) knownSDs: {}
Thread-393::INFO::2013-09-19
11:59:42,506::logUtils::47::dispatcher::(wrapper) Run and protect:
connectStorageServer, Return response: {'statuslist': [{'status': 469,
'id': '----'}]}
Thread-393::DEBUG::2013-09-19
11:59:42,506::task::1168::TaskManager.Task::(prepare)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::finished: {'statuslist':
[{'status': 469, 'id': '----'}]}
Thread-393::DEBUG::2013-09-19
11:59:42,506::task::579::TaskManager.Task::(_updateState)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state preparing -
state finished
Thread-393::DEBUG::2013-09-19
11:59:42,506::resourceManager::939::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-393::DEBUG::2013-09-19
11:59:42,507::resourceManager::976::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-393::DEBUG::2013-09-19
11:59:42,507::task::974::TaskManager.Task::(_decref)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::ref 0 aborting False
*Other info:*
- I have two nodes, ovirt001, ovirt002 they are both Fedora 19.
- The gluster bricks are replicated and located on the nodes.
(ovirt001:rep2-virt, ovirt002:rep2-virt)
- Local directory for the mount, I changed permissions on glusterSD to 777,
it was 755, and there is nothing in that directory:
[root@ovirt001 mnt]# pwd
/rhev/data-center/mnt
[root@ovirt001 mnt]# ll
total 4
drwxrwxrwx. 2 vdsm kvm 4096 Sep 19 12:18 glusterSD
I find it odd that the UUID's listed in the vdsm logs are zero's..
Appreciate any help,
*Steve
*
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt 3.3 Fedora 19 add gluster storage permissions error
Il giorno 19/set/2013 19:10, Alexander Wels aw...@redhat.com ha scritto:
Steve,
Having just installed gluster on my local hosts and seeing the exact same
error in my setup. I am going to assume the following are true:
1. You made a partition just for gluster.
2. You followed oVirt 3.3, Glusterized article from Jason Brooks.
I got the exact same error because for some reason the owner of the
directory I put the gluster bricks in keep changing back to root instead of
kvm:kvm. Each time I reboot my host, that happens, so I am assuming I
didn't set up something correctly. But you can solve it by chowning the
directory and everything will work again.
If that doesn't help, well I don't know, I just started using it myself,
I just happen to have seen the same error at some point.
Alexander
On Thursday, September 19, 2013 12:26:52 PM Steve Dainard wrote:
Hello,
New Ovirt 3.3 install on Fedora 19.
When I try to add a gluster storage domain I get the following:
UI error:
Error while executing action Add Storage Connection: Permission settings
on the specified path do not allow access to the storage.
Verify permission settings on the specified storage path.
VDSM logs contain:
Thread-393::DEBUG::2013-09-19
11:59:42,399::BindingXMLRPC::177::vds::(wrapper) client [10.0.0.34]
Thread-393::DEBUG::2013-09-19
11:59:42,399::task::579::TaskManager.Task::(_updateState)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state init -
state preparing
Thread-393::INFO::2013-09-19
11:59:42,400::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='----', conList=[{'port': '',
'connection': '192.168.1.1:/rep2-virt', 'iqn': '', 'portal': '', 'user':
'', 'vfs_type': 'glusterfs', 'password': '**', 'id':
'----'}], options=None)
Thread-393::DEBUG::2013-09-19
11:59:42,405::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n
/usr/bin/mount -t glusterfs 192.168.1.1:/rep2-virt
/rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)
Thread-393::DEBUG::2013-09-19
11:59:42,490::mount::226::Storage.Misc.excCmd::(_runcmd) '/usr/bin/sudo -n
/usr/bin/umount -f -l /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'
(cwd None)
Thread-393::ERROR::2013-09-19
11:59:42,505::hsm::2382::Storage.HSM::(connectStorageServer) Could not
connect to storageServer
Traceback (most recent call last):
File /usr/share/vdsm/storage/hsm.py, line 2379, in
connectStorageServer
conObj.connect()
File /usr/share/vdsm/storage/storageServer.py, line 227, in connect
raise e
StorageServerAccessPermissionError: Permission settings on the specified
path do not allow access to the storage. Verify permission settings on the
specified storage path.: 'path =
/rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'
Thread-393::DEBUG::2013-09-19
11:59:42,506::hsm::2396::Storage.HSM::(connectStorageServer) knownSDs: {}
Thread-393::INFO::2013-09-19
11:59:42,506::logUtils::47::dispatcher::(wrapper) Run and protect:
connectStorageServer, Return response: {'statuslist': [{'status': 469,
'id': '----'}]}
Thread-393::DEBUG::2013-09-19
11:59:42,506::task::1168::TaskManager.Task::(prepare)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::finished: {'statuslist':
[{'status': 469, 'id': '----'}]}
Thread-393::DEBUG::2013-09-19
11:59:42,506::task::579::TaskManager.Task::(_updateState)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state preparing -
state finished
Thread-393::DEBUG::2013-09-19
11:59:42,506::resourceManager::939::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-393::DEBUG::2013-09-19
11:59:42,507::resourceManager::976::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-393::DEBUG::2013-09-19
11:59:42,507::task::974::TaskManager.Task::(_decref)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::ref 0 aborting False
Other info:
- I have two nodes, ovirt001, ovirt002 they are both Fedora 19.
- The gluster bricks are replicated and located on the nodes.
(ovirt001:rep2-virt, ovirt002:rep2-virt)
- Local directory for the mount, I changed permissions on glusterSD to
777, it was 755, and there is nothing in that directory:
[root@ovirt001 mnt]# pwd
/rhev/data-center/mnt
[root@ovirt001 mnt]# ll
total 4
drwxrwxrwx. 2 vdsm kvm 4096 Sep 19 12:18 glusterSD
I find it odd that the UUID's listed in the vdsm logs are zero's..
Appreciate any help,
Steve
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
I had a similar problem in gluster configuration for openstack and found
solution in this ovirt page:
http://www.ovirt.org/Features/GlusterFS_Storage_Domain#Setting_up_a_GlusterFS_storage_volume_for_using_it_as_a_storage_domain
In particular:
Re: [Users] Ovirt 3.3 Fedora 19 add gluster storage permissions error
Steve,
Having just installed gluster on my local hosts and seeing the exact same error
in my
setup. I am going to assume the following are true:
1. You made a partition just for gluster.
2. You followed oVirt 3.3, Glusterized article from Jason Brooks.
I got the exact same error because for some reason the owner of the directory I
put
the gluster bricks in keep changing back to root instead of kvm:kvm. Each time
I
reboot my host, that happens, so I am assuming I didn't set up something
correctly.
But you can solve it by chowning the directory and everything will work again.
If that doesn't help, well I don't know, I just started using it myself, I just
happen to
have seen the same error at some point.
Alexander
On Thursday, September 19, 2013 12:26:52 PM Steve Dainard wrote:
Hello,
New Ovirt 3.3 install on Fedora 19.
When I try to add a gluster storage domain I get the following:
*UI error:*
/Error while executing action Add Storage Connection: Permission settings on
the
specified path do not allow access to the storage./
/Verify permission settings on the specified storage path./
*VDSM logs contain:*
Thread-393::DEBUG::2013-09-19 11:59:42,399::BindingXMLRPC::177::vds::(wrapper)
client [10.0.0.34]
Thread-393::DEBUG::2013-09-19 11:59:42,399::task::579::TaskManager.Task::
(_updateState) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state
init - state preparing
Thread-393::INFO::2013-09-19 11:59:42,400::logUtils::44::dispatcher::(wrapper)
Run
and protect: connectStorageServer(domType=7,
spUUID='----', conList=[{'port': '',
'connection':
'192.168.1.1:/rep2-virt', 'iqn': '', 'portal': '', 'user': '', 'vfs_type':
'glusterfs', 'password':
'**', 'id': '----'}], options=None)
Thread-393::DEBUG::2013-09-19 11:59:42,405::mount::226::Storage.Misc.excCmd::
(_runcmd) '/usr/bin/sudo -n /usr/bin/mount -t glusterfs 192.168.1.1:/rep2-virt
/rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)
Thread-393::DEBUG::2013-09-19 11:59:42,490::mount::226::Storage.Misc.excCmd::
(_runcmd) '/usr/bin/sudo -n /usr/bin/umount -f -l /rhev/data-
center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)
Thread-393::ERROR::2013-09-19 11:59:42,505::hsm::2382::Storage.HSM::
(connectStorageServer) Could not connect to storageServer
Traceback (most recent call last):
File /usr/share/vdsm/storage/hsm.py, line 2379, in connectStorageServer
conObj.connect()
File /usr/share/vdsm/storage/storageServer.py, line 227, in connect
raise e
StorageServerAccessPermissionError: Permission settings on the specified path
do
not allow access to the storage. Verify permission settings on the specified
storage
path.: 'path = /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'
Thread-393::DEBUG::2013-09-19 11:59:42,506::hsm::2396::Storage.HSM::
(connectStorageServer) knownSDs: {}
Thread-393::INFO::2013-09-19 11:59:42,506::logUtils::47::dispatcher::(wrapper)
Run
and protect: connectStorageServer, Return response: {'statuslist': [{'status':
469, 'id':
'----'}]}
Thread-393::DEBUG::2013-09-19 11:59:42,506::task::1168::TaskManager.Task::
(prepare) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::finished: {'statuslist':
[{'status': 469, 'id': '----'}]}
Thread-393::DEBUG::2013-09-19 11:59:42,506::task::579::TaskManager.Task::
(_updateState) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state
preparing - state finished
Thread-393::DEBUG::2013-09-19
11:59:42,506::resourceManager::939::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-393::DEBUG::2013-09-19
11:59:42,507::resourceManager::976::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-393::DEBUG::2013-09-19
11:59:42,507::task::974::TaskManager.Task::(_decref)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::ref 0 aborting False
*Other info:*
- I have two nodes, ovirt001, ovirt002 they are both Fedora 19.
- The gluster bricks are replicated and located on the nodes.
(ovirt001:rep2-virt,
ovirt002:rep2-virt)
- Local directory for the mount, I changed permissions on glusterSD to 777, it
was
755, and there is nothing in that directory:
[root@ovirt001 mnt]# pwd
/rhev/data-center/mnt
[root@ovirt001 mnt]# ll
total 4
drwxrwxrwx. 2 vdsm kvm 4096 Sep 19 12:18 glusterSD
I find it odd that the UUID's listed in the vdsm logs are zero's..
Appreciate any help,
*Steve
*
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Ovirt 3.3 Fedora 19 add gluster storage permissions error
On Thursday, September 19, 2013 07:22:08 PM Gianluca Cecchi wrote:
aw...@redhat.com[1] ha scritto: Steve, Having just installed gluster
on
my local hosts and seeing the exact same error in my setup. I am going to
assume
the following are true: 1. You made a partition just for gluster. 2.
You
followed oVirt 3.3, Glusterized article from Jason Brooks. I got the
exact same
error because for some reason the owner of the directory I put the gluster
bricks in
keep changing back to root instead of kvm:kvm. Each time I reboot my host, that
happens, so I am assuming I didn't set up something correctly. But you can
solve it by
chowning the directory and everything will work again. If that doesn't
help, well
I don't know, I just started using it myself, I just happen to have seen the
same error
at some point. Alexander On Thursday, September 19, 2013 12:26:52
PM Steve Dainard wrote: Hello, New Ovirt 3.3 install on Fedora 19. When
I
try to add a gluster storage domain I get the following: UI error: Error
while
executing action Add Storage Connection: Permission settings on the specified
path
do not allow access to the storage. Verify permission settings on the
specified
storage path. VDSM logs contain: Thread-393::DEBUG::2013-09-19
11:59:42,399::BindingXMLRPC::177::vds::(wrapper) client [10.0.0.34]
Thread-393::DEBUG::2013-09-19 11:59:42,399::task::579::TaskManager.Task::
(_updateState) Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state
init - state preparing Thread-393::INFO::2013-09-19
11:59:42,400::logUtils::44::dispatcher::(wrapper) Run and protect:
connectStorageServer(domType=7,
spUUID='----', conList=[{'port': '',
'connection':
'192.168.1.1:/rep2-virt', 'iqn': '', 'portal': '', 'user': '', 'vfs_type':
'glusterfs', 'password':
'**', 'id': '----'}], options=None)
Thread-393::DEBUG::2013-09-19 11:59:42,405::mount::226::Storage.Misc.excCmd::
(_runcmd) '/usr/bin/sudo -n /usr/bin/mount -t glusterfs 192.168.1.1:/rep2-virt
/rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)
Thread-393::DEBUG::2013-09-19 11:59:42,490::mount::226::Storage.Misc.excCmd::
(_runcmd) '/usr/bin/sudo -n /usr/bin/umount -f -l /rhev/data-
center/mnt/glusterSD/192.168.1.1:_rep2-virt' (cwd None)
Thread-393::ERROR::2013-09-19 11:59:42,505::hsm::2382::Storage.HSM::
(connectStorageServer) Could not connect to storageServer Traceback (most
recent call last): File /usr/share/vdsm/storage/hsm.py, line 2379, in
connectStorageServer conObj.connect() File
/usr/share/vdsm/storage/storageServer.py, line 227, in connect raise
e
StorageServerAccessPermissionError: Permission settings on the specified path
do
not allow access to the storage. Verify permission settings on the specified
storage
path.: 'path = /rhev/data-center/mnt/glusterSD/192.168.1.1:_rep2-virt'
Thread-393::DEBUG::2013-09-19 11:59:42,506::hsm::2396::Storage.HSM::
(connectStorageServer) knownSDs: {} Thread-393::INFO::2013-09-19
11:59:42,506::logUtils::47::dispatcher::(wrapper) Run and protect:
connectStorageServer, Return response: {'statuslist': [{'status': 469, 'id':
'----'}]} Thread-393::DEBUG::2013-09-19
11:59:42,506::task::1168::TaskManager.Task::(prepare) Task=`12c38fec-0072-4974-
a8e3-9125b3908246`::finished: {'statuslist': [{'status': 469, 'id':
'----'}]} Thread-393::DEBUG::2013-09-19
11:59:42,506::task::579::TaskManager.Task::(_updateState)
Task=`12c38fec-0072-4974-a8e3-9125b3908246`::moving from state preparing -
state finished Thread-393::DEBUG::2013-09-19
11:59:42,506::resourceManager::939::ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {} Thread-393::DEBUG::2013-09-19
11:59:42,507::resourceManager::976::ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {} Thread-393::DEBUG::2013-09-19
11:59:42,507::task::974::TaskManager.Task::(_decref) Task=`12c38fec-0072-4974-
a8e3-9125b3908246`::ref 0 aborting False Other info: - I have two nodes,
ovirt001, ovirt002 they are both Fedora 19. - The gluster bricks are
replicated and
located on the nodes. (ovirt001:rep2-virt, ovirt002:rep2-virt) - Local
directory for
the mount, I changed permissions on glusterSD to 777, it was 755, and there is
nothing in that directory: [root@ovirt001 mnt]# pwd /rhev/data-center/mnt
[root@ovirt001 mnt]# ll total 4 drwxrwxrwx. 2 vdsm kvm 4096 Sep 19 12:18
glusterSD I find it odd that the UUID's listed in the vdsm logs are
zero's..
Appreciate any help, Steve
___ Users mailing list
Users@ovirt.org[2]
http://lists.ovirt.org/mailman/listinfo/users[3]
http://www.ovirt.org/Features/GlusterFS_Storage_Domain#Setting_up_a_GlusterFS_sto
rage_volume_for_using_it_as_a_storage_domain[4]
In particular:
If the GlusterFS volume was created manually, then ensure the below options are
set
on the
[Users] Unable to attach to storage domain (Ovirt 3.2)
Hi,
This is my first post to the list. I am happy to say that we have been
using Ovirt for 6 months with a few bumps, but it's mostly been ok.
Until tonight that is...
I had to do a maintenance that required rebooting both of our Hypervisor
nodes. Both of them run Fedora Core 18 and have been happy for months.
After rebooting them tonight, they will not attach to the storage. If
it matters, the storage is a server running LIO with a Fibre Channel target.
Vdsm log:
Thread-22::DEBUG::2013-09-19
21:57:09,392::misc::84::Storage.Misc.excCmd::(lambda) '/usr/bin/dd
iflag=direct if=/dev/b358e46b-635b-4c0e-8e73-0a494602e21d/metadata
bs=4096 count=1' (cwd None)
Thread-22::DEBUG::2013-09-19
21:57:09,400::misc::84::Storage.Misc.excCmd::(lambda) SUCCESS: err =
'1+0 records in\n1+0 records out\n4096 bytes (4.1 kB) copied,
0.000547161 s, 7.5 MB/s\n'; rc = 0
Thread-23::DEBUG::2013-09-19
21:57:16,587::lvm::368::OperationMutex::(_reloadvgs) Operation 'lvm
reload operation' got the operation mutex
Thread-23::DEBUG::2013-09-19
21:57:16,587::misc::84::Storage.Misc.excCmd::(lambda) u'/usr/bin/sudo
-n /sbin/lvm vgs --config devices { preferred_names =
[\\^/dev/mapper/\\] ignore_suspended_devices=1 write_cache_state=0
disable_after_error_count=3 filter = [
\\a%360014055193f840cb3743f9befef7aa3%\\, \\r%.*%\\ ] } global {
locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup {
retain_min = 50 retain_days = 0 } --noheadings --units b --nosuffix
--separator | -o
uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free
6cf7e7e9-3ae5-4645-a29c-fb17ecb38a50' (cwd None)
Thread-23::DEBUG::2013-09-19
21:57:16,643::misc::84::Storage.Misc.excCmd::(lambda) FAILED: err =
' Volume group 6cf7e7e9-3ae5-4645-a29c-fb17ecb38a50 not found\n';
rc = 5
Thread-23::WARNING::2013-09-19
21:57:16,649::lvm::373::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 []
[' Volume group 6cf7e7e9-3ae5-4645-a29c-fb17ecb38a50 not found']
Thread-23::DEBUG::2013-09-19
21:57:16,649::lvm::397::OperationMutex::(_reloadvgs) Operation 'lvm
reload operation' released the operation mutex
Thread-23::ERROR::2013-09-19
21:57:16,650::domainMonitor::208::Storage.DomainMonitorThread::(_monitorDomain)
Error while collecting domain 6cf7e7e9-3ae5-4645-a29c-fb17ecb38a50
monitoring information
Traceback (most recent call last):
File /usr/share/vdsm/storage/domainMonitor.py, line 182, in
_monitorDomain
self.domain = sdCache.produce(self.sdUUID)
File /usr/share/vdsm/storage/sdc.py, line 97, in produce
domain.getRealDomain()
File /usr/share/vdsm/storage/sdc.py, line 52, in getRealDomain
return self._cache._realProduce(self._sdUUID)
File /usr/share/vdsm/storage/sdc.py, line 121, in _realProduce
domain = self._findDomain(sdUUID)
File /usr/share/vdsm/storage/sdc.py, line 152, in _findDomain
raise se.StorageDomainDoesNotExist(sdUUID)
StorageDomainDoesNotExist: Storage domain does not exist:
(u'6cf7e7e9-3ae5-4645-a29c-fb17ecb38a50',)
vgs output (Note that I don't know what the device
(Wy3Ymi-J7bJ-hVxg-sg3L-F5Gv-MQmz-Utwv7z is) :
[root@node01 vdsm]# vgs
Couldn't find device with uuid Wy3Ymi-J7bJ-hVxg-sg3L-F5Gv-MQmz-Utwv7z.
VG #PV #LV #SN Attr VSize VFree
b358e46b-635b-4c0e-8e73-0a494602e21d 1 39 0 wz--n- 8.19t 5.88t
build 2 2 0 wz-pn- 299.75g 16.00m
fedora 1 3 0 wz--n- 557.88g 0
lvs output:
[root@node01 vdsm]# lvs
Couldn't find device with uuid Wy3Ymi-J7bJ-hVxg-sg3L-F5Gv-MQmz-Utwv7z.
LV VG
Attr LSizePool Origin Data% Move Log Copy% Convert
0b8cca47-313f-48da-84f2-154810790d5a
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 40.00g
0f6f7572-8797-4d84-831b-87dbc4e1aa48
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 100.00g
19a1473f-c375-411f-9a02-c6054b9a28d2
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 50.00g
221144dc-51dc-46ae-9399-c0b8e030f38a
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 40.00g
2386932f-5f68-46e1-99a4-e96c944ac21b
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 40.00g
3e027010-931b-43d6-9c9f-eeeabbdcd47a
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a2.00g
4257ccc2-94d5-4d71-b21a-c188acbf7ca1
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 200.00g
4979b2a4-04aa-46a1-be0d-f10be0a1f587
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 100.00g
4e1b8a1a-1704-422b-9d79-60f15e165cb7
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 40.00g
70bce792-410f-479f-8e04-a2a4093d3dfb
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 100.00g
791f6bda-c7eb-4d90-84c1-d7e33e73de62
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 100.00g
818ad6bc-8da2-4099-b38a-8c5b52f69e32
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 120.00g
861c9c44-fdeb-43cd-8e5c-32c00ce3cd3d
b358e46b-635b-4c0e-8e73-0a494602e21d -wi-a 100.00g
