Re: [OmniOS-discuss] Missing /devices/pseudo/kvm* with Intel Xeon E3-1240 v3
Sorry Dan, forgot to reply to the mailing list. On 02.09.2016 16:06, Dan McDonald wrote: Please do this: pkg list kvm [...] Are those packages missing? If so, "pkg install" them both. Both are installed. Here's the output: NAME (PUBLISHER) VERSION IFO driver/virtualization/kvm 1.0.5.11-0.151014 i-- system/kvm 1.0.5.11-0.151014 i-- [...] If they are there in "pkg list", you may wish to "pkg verify driver/virtualization/kvm system/kvm" to make sure. Now it's getting interesting. Here's the error the verification is telling me: PACKAGE STATUS pkg://omnios/drive/virtualization/kvm ERROR driver: kvm etc/name_to_major: 'kvm' entry not present I checked the file and indeed there's no such entry. I mounted a few older boot environments. There's no 'kvm' entry in any of the /etc/name_to_major files. Do you have any idea how to tackle this? Hanno ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
[OmniOS-discuss] Missing /devices/pseudo/kvm* with Intel Xeon E3-1240 v3
Hey guys!
I run OmniOS r151014 on a SuperMicro server with an Intel Xeon E3-1240
v3 CPU. We need kvm for a qemu-kvm machine but the kvm device is missing.
The symlink /dev/kvm is there but there's no /devices/pseudo/kvm@0:kvm
where it's pointing. I enabled Intel VT-x on the mainboard. The kernel
module files are present but OmniOS is unable to load them ("file not
found" - obviously). So I'm stuck now and don't know how to analyze this
further. Please help me out!
Do you have any hints or encountered a similar problem? Is the processor
unsupported by any chance?
The mainboard is a Supermicro Server Board X10SLM-F. Let me know if you
need anything.
Best regards,
Hanno
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] 4kn or 512e with ashift=12
On 21.03.2016 08:00, Fred Liu wrote: So that means illumos can handle 512n and 4kn automatically and properly? Not necessarily as far as I know. Sometime drives are emulating 512 blocks and don't properly tell the OS about that and Illumos ZFS is aligning the drives with ashift=9 which leads to enormous performance issues. Also forcing the system to handle drives with a specific sector size with the sd.conf doesn't turn out to be reliable in some cases (at least on my workstations). Here's what I do to ensure ashift=12 values: Reboot the system with a Linux live disk of your choice and install ZoL in the live session. Then create the ZFS pool, export it and reboot the machine. OmniOS / Illumos can import the new pool without problems and the ashift value is correctly set. There was a fixed zpool binary (Solaris 11 binary) flying around the internet which can handle the "-o shift=12" parameter and works with OmniOS but unfortunately I can't find it again right now. This would make the reboot into a live session obsolete. Does anyone know if the "ashift" parameter will be implemented in the OmniOS / Illumos zpool binary in the near future? Best regards Hanno ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] Maildir: ACLs/Unix perms: unlink(...) failed: Permission denied
On 10.10.2015 18:09, Olaf Marzocchi wrote: I'm not sure why I cannot see in Thunderbird any folder "Trash" but if I try to create one it fails with "Folder already existing", but I will find out Had the same problem before so let's give it a try! Are all the folders subscribed in Thunderbird? Right click on the mail account name in the mailbox list and go to "Subscribe...". See if the checkbox on the "Trash" entry is activated. Regards, Hanno ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
Re: [OmniOS-discuss] iSCSI poor write performance
Hi Martin, On 23.09.2015 10:51, Martin Truhlář wrote: Tests revealed, that problem is somewhere in disk array itself. are you familiar with the ashift problem on 4k drives? My best guess would be that the 1 TB WD drives are emulating a block size of 512 bytes while using 4k sectors internally. OmniOS is using a ashift value of 9 then to align the data efficiently (on 512 byte sectors!). This slows the whole pool down - I had the same problem before. The ashift value has to be 12 on 4k drives! Try the command 'zdb' to gather the values for your drives. Look for 'ashift: 9' oder 'ashift: 12'. Regards, Hanno ___ OmniOS-discuss mailing list OmniOS-discuss@lists.omniti.com http://lists.omniti.com/mailman/listinfo/omnios-discuss
