Cannot build kernel with qlxgbe on 10.2 RC2 (and probably 11-current)
Hi all, I have a problem with build kernel. You cannot use device qlxgbe in kernel config. I don't check but 11-current have same problem. It is caused by r284982 and r284741. New files were added but static files were not added. http://svnweb.freebsd.org/base?view=revisionrevision=284982 http://svnweb.freebsd.org/base?view=revisionrevision=284741 The patch is attached. Please check it. Thanks, -- Daisuke Aoyama qlxgbe-20150808.patch Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
hastctl hang
Hello, I'm trying to integrate HAST to NAS4Free (FreeBSD 9.1-RC3). Now I have created version 9.1.0.1.531. http://sourceforge.net/projects/nas4free/files/NAS4Free-9.1.0.1/9.1.0.1.531/ Basic CARP + HAST + iSCSI target setup can be done, but very frequently I get hastctl hang when called: /sbin/hastctl status /sbin/hastctl dump Is it better for this method not to call from a script? or somthing wrong to use it? Also, I don't know how to detect an error of writing to local device from hastd. Does anyone know about it? Thanks, Daisuke Aoyama -- the procstat shows like this: [root@nas4free-nodeb /tmp]# procstat -ka|grep hast 11668 100069 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep kern_wait sys_wait4 amd64_syscall Xfast_syscall 17981 100406 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17981 100559 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17981 100560 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17981 100561 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17984 100078 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 17984 100562 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17984 100563 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall 17984 100564 hastd-mi_switch sleepq_catch_signals sleepq_wait_sig _sleep do_wait __umtx_op_wait_uint_private amd64_syscall Xfast_syscall 18218 100145 hastctl -mi_switch sleepq_catch_signals sleepq_wait_sig _sleep soreceive_generic kern_recvit recvit sys_recvfrom amd64_syscall Xfast_syscall [root@nas4free-nodeb /tmp]# procstat -ta|grep hast 11668 100069 hastd- 0 120 sleep wait 17979 100557 hastd- 2 120 sleep g_waitid 17981 100406 hastd- 2 120 sleep uwait 17981 100559 hastd- 0 120 sleep sbwait 17981 100560 hastd- 0 120 sleep sbwait 17981 100561 hastd- 1 120 sleep uwait 17984 100078 hastd- 2 121 sleep uwait 17984 100562 hastd- 3 120 sleep sbwait 17984 100563 hastd- 2 120 sleep sbwait 17984 100564 hastd- 1 121 sleep uwait 18218 100145 hastctl - 2 152 sleep sbwait -- the procstat shows like this: ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Updated isboot 0.2.6 and FreeBSD 9.1-RC1
Hi, Thank you for reporting. It seems a bug of isboot. Your NIC is link down, but isboot never retry on first connection. Because of this, it failed to find the boot device. I have updated isboot and created 9.1-RC based image. Please try it: http://www.peach.ne.jp/archives/isboot/isboot-0.2.6.tar.gz http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-RC1-amd64-memstick-isboot-0.2.6.img I have a few questions for you (or other knowledgeable people on the list): 1) Does iBFT require hardware support in the NIC? 2) Does iBFT require NIC driver support? NO. You can use both iBFT software like gPXE and NIC's rom like Intel iSCSI boot agent. The isboot should work with any NIC supported by FreeBSD. 3) Is anything required in loader.conf besides isboot_load=YES? If your NIC driver is within the kernel, you need only isboot_load=YES. 4) Is it likely to work (better) if I find an em(4) card instead? I have tested with Intel cards/onboard. If you want the maximum performance, I recommend you to use Intel card, but other cards should work with isboot. This is my log of ASRock E350M1/USB3(re(4) + gPXE): -- iSCSI boot driver version 0.2.6 IS: Initiator name: iqn.2000-09.org.etherboot:e350m1 NIC0: IP address: 172.18.0.131 NIC0: Prefix: 16 NIC0: Gateway: 172.18.0.1 NIC0: MAC address: 00:25:22:b3:b7:a7 TGT0: Target IP address: 172.18.0.26 TGT0: Target Port: 3260 TGT0: Target LUN: 0 TGT0: Target name: iqn.2007-09.jp.ne.peach:aria:e350m1-boot Boot NIC: re0 Configure IPv4 by NIC0 (snip) da1 at isboot0 bus 0 scbus8 target 0 lun 0 da1: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device da1: 300.000MB/s transfers da1: 20480MB (41943040 512 byte sectors: 255H 63S/T 2610C) da0 at umass-sim0 bus 0 scbus7 target 0 lun 0 da0: USB Reader 0001 Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 1882MB (3854336 512 byte sectors: 255H 63S/T 239C) da2 at isboot0 bus 0 scbus8 target 0 lun 1 da2: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device da2: 300.000MB/s transfers da2: 681MB (1395264 512 byte sectors: 64H 32S/T 681C) Boot device: da1 SMP: AP CPU #1 Launched! Timecounter TSC-low frequency 12500234 Hz quality 800 GEOM: da0: the primary GPT table is corrupt or invalid. GEOM: da0: using the secondary instead -- recovery strongly advised. GEOM: da2: geometry does not match label (32h,63s != 64h,32s). GEOM: ufsid/5029dbce6b8b4567: geometry does not match label (32h,63s != 64h,32s). GEOM: ufs/FreeBSD_Install: geometry does not match label (32h,63s != 64h,32s). Trying to mount root from ufs:/dev/da1p2 [rw]... -- Thanks, Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
iSCSI boot driver 0.2.5 (isboot.ko) has been released.
You can download the source file from: http://www.peach.ne.jp/archives/isboot/isboot-0.2.5.tar.gz Also, you can download a demo version of 9.1-BETA1. http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-9.1-BETA1-amd64-memstick-isboot-0.2.5.img This demo version is added isboot.txz which includes isboot.ko and loader.conf and a syscons patched kernel for DN2800MT. You can use it as istgt's LUN extent like this: -- [LogicalUnit2800] TargetName iqn.2007-09.jp.ne.peach:aria:dn2800mt-boot Mapping PortalGroup4 InitiatorGroup2800 UnitType Disk QueueDepth 32 LUN0 Storage /tank/iscsi/istgt-DN2800MT.vdi Auto LUN1 Storage /tank/iscsi/FreeBSD-9.1-BETA1-amd64-memstick-isboot-0.2.5.img Auto -- Then, boot FreeBSD installer from LUN1 and install FreeBSD by normal way to LUN0. After installation, you have an iSCSI based diskless machine. I have tested it with iPXE(USB boot) and Intel Desktop Board DN2800MT without using SATA ports. For example, booting LUN1 by iPXE(just use :::1:): sanboot iscsi:172.18.0.26:::1:iqn.2007-09.jp.ne.peach:aria:dn2800mt-boot For more info of Japanese is here: http://shell.peach.ne.jp/aoyama/archives/2097 http://shell.peach.ne.jp/aoyama/archives/2100 Have fun! Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [Need Help]isboot (iSCSI boot driver) version 0.2.1
Updated to 0.2.2 I noticed a bug after writing previous mail. sosend was called from XPT_SCSI_IO with locked mutex. It caused sleeping thread owns a non-sleepable lock. What's new?: add auto sense. add maxio=1m. modify max tags by iSCSI command window. fix locked sleep problem. Download links: http://www.peach.ne.jp/archives/isboot/isboot-0.2.2.tar.gz Download links(for testing purpose only): http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.2.2.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.2.2.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC2-amd64-isboot-0.2.2.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC2-i386-isboot-0.2.2.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[Need Help]isboot (iSCSI boot driver) version 0.2.1
Hi all, I uploaded isboot 0.2.1. Now isboot supports R2T command and non-immediate mode. I believe that the compatibility of iSCSI target is improved. Please check it with your iSCSI target and NIC. Also this version supports task queue, which improves performance. My test machine got read 74MB/s, write 60MB/s (at bs=1m). Notes/Known Issues/Limitations: FreeBSD can't use transfer length 64KB. It seems CAM tag is used only 2 of 64 tags. I don't know a reason, but MAXPHYS limit? How to build/upgrade: # cd /usr/src # tar xvf /path/to/iscsi-2.2.4.tar.gz # tar xvf /path/to/isboot-0.2.1.tar.gz # make buildkernel # make installkernel or # cd /usr/src/sys/modules/iscsi/isboot # make obj # make depend # make clean # make all # make install After installation, please reboot the server to take effect. Confirm the log shows iSCSI boot driver version 0.2.1. What's new?: * support CHAP/Mutual CHAP * add task queue * R2T command and non-immediate mode Performance(without digest): # dd if=/dev/da4 of=/dev/null bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 14.374117 secs (74699672 bytes/sec) # dd if=/dev/zero of=/dev/da4 bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 17.823493 secs (60243064 bytes/sec) Download links: http://www.peach.ne.jp/archives/isboot/isboot-0.2.1.tar.gz Download links(for testing purpose only): http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC2-amd64-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC2-i386-isboot-0.2.1.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh gPXE + isboot + istgt(for reference): http://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004432.html Previous versions: http://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004431.html http://lists.freebsd.org/pipermail/freebsd-scsi/2010-June/004425.html I hope this helps you. Enjoy it. Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
isboot (iSCSI boot driver) version 0.1.3
Updated isboot to 0.1.3. Try this. How to build/upgrade: # cd /usr/src # tar xvf /path/to/iscsi-2.2.4.tar.gz # tar xvf /path/to/isboot-0.1.3.tar.gz # make buildkernel # make installkernel or # cd /usr/src/sys/modules/iscsi/isboot # make obj # make depend # make all # make install After installation, please reboot the server to take effect. Confirm the log shows iSCSI boot driver version 0.1.3. What's new?: * improve session recovery mode. * fix panic when socket is lost. Download links: http://www.peach.ne.jp/archives/isboot/isboot-0.1.3.tar.gz Download links(for testing purpose only): http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-amd64-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-i386-isboot-0.1.3.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh I hope this helps you. Enjoy it. Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iSCSI boot driver version 0.1.1 for iBFT
--- Notes: You have to configure DNS (/etc/resolv.conf) and hostname manually. Or must set exactly matched IP/mask/route in iBFT by sysinstall. This is current limitation. (sysintall breaks booted NIC parameter.) -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: iSCSI boot driver version 0.1.1 for iBFT
Sorry, isboot-0.1.1 was broken under i386 kernel + loader. The version 0.1.2 is uploaded in my blog. Also I uploaded isboot integrated FreeBSD 7.3 disc1, 8.1-RC1 dics1 and making script. Use at your own risk. You need only iBFT supported NIC and iSCSI target. Please see Intel's site about iBFT supported NIC. http://www.intel.com/support/network/adapter/pro100/sb/CS-028681.htm If you can connect to iSCSI target by NIC BIOS, isboot.ko shows the following log. In this case, em0 is configured automatically with NIC0 parameter in iBFT, and you can install FreeBSD to da1 directly and you can boot from da1. If you want to try to copy existing FreeBSD, then configure NIC and loading isboot.ko via loader.conf or kldload isboot.ko from shell. Then, use normal way such as dump/restore. Note: do not set IP to em0 when installation. it might be a problem. --- iSCSI boot driver version 0.1.2 IS: Initiator name: iqn.2007-09.jp.ne.peach:pluto NIC0: IP address: 192.168.3.48 NIC0: Prefix: 24 NIC0: Gateway: 0.0.0.0 NIC0: MAC address: 00:15:17:97:85:ab TGT0: Target IP address: 192.168.3.36 TGT0: Target Port: 3260 TGT0: Target LUN: 2 TGT0: Target name: iqn.2007-09.jp.ne.peach:isboot1 Boot NIC: em0 Configure IPv4 by NIC0 Attempting to login to iSCSI target and scan all LUNs. ... cut ... da0 at isboot0 bus 0 scbus0 target 0 lun 0 da0: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device da0: 40960MB (83886080 512 byte sectors: 255H 63S/T 5221C) da1 at isboot0 bus 0 scbus0 target 0 lun 2 da1: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device da1: 10240MB (20971520 512 byte sectors: 255H 63S/T 1305C) da2 at isboot0 bus 0 scbus0 target 0 lun 3 da2: FreeBSD iSCSI DISK 0001 Fixed Direct Access SCSI-5 device da2: 1024MB (2097152 512 byte sectors: 64H 32S/T 1024C) ... cut ... Boot device: da1 --- Download links: http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-amd64-isboot-0.1.2.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-7.3-RELEASE-i386-isboot-0.1.2.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-amd64-isboot-0.1.2.iso http://www.peach.ne.jp/archives/isboot/demo/FreeBSD-8.1-RC1-i386-isboot-0.1.2.iso http://www.peach.ne.jp/archives/isboot/demo/unionfs-mkisboot.sh Try it you self :) Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
iSCSI boot driver version 0.1.1 for iBFT
Hello, I made small device driver for the first time. It is published on my blog. Because it is written in Japanese, I try to write here. This module provides initial connection of the iSCSI target with setting via iBFT (iSCSI Boot Firmware Table). Currently, it is intended to use Intel NIC and istgt (iSCSI target). Any other cards, targets may not work. Also, I'm developing under FreeBSD 7.3. (build check under 8.1) Please refer to Microsoft website about iBFT: http://www.microsoft.com/whdc/system/platform/firmware/ibft.mspx I did't use iscsi_initiator.ko within kernel module. So, I'm creating a small version of initiator based on iscsi-2.2.4 and istgt-20100606. Now it have only one cmd holding space in the iSCSI session and use polling. It should be added the queuing/asynchronous operation :) After loading it via /boot/loader.conf, you can install to/boot from the iSCSI target as same as a local SCSI harddisk. Complex settings such as TFTP, NFS, DHCP and PXE are no longer needed. Just use /dev/da0 and so on. How to compile: isboot is a stand alone iSCSI initiator, but source code is depend on the header file of iscsi-2.2.4. You need to extract iscsi-2.2.4 before compiling isboot. # cd /usr/src # tar xvf /path/to/iscsi-2.2.4.tar.gz # tar xvf /path/to/isboot-0.1.1.tar.gz # make buildkernel # make installkernel or # cd /usr/src/sys/modules/iscsi/isboot # make obj # make depend # make all # make install After above install, you have /boot/kernel/isboot.ko. Using as module: Add isboot_load=YES to /boot/loader.conf. Setup iSCSI target. (recommend istgt-20100407 or later) Configure NIC BIOS to connect the target. Try to boot the server. If the NIC find the target, iBFT can be found by isboot. Then, isboot create own bus for CAM device with iBFT parameters. All LUNs in the target are appeared in the bus. Once FreeBSD + isboot is booted, you can handle it by camcontrol and other normal way as same as SCSI HDD. If you want full install and boot demo, please download FreeNAS 0.7.2 5226 p4 from my blog and try it without local harddisk. FYI: FreeNAS 0.7.1 5127 (stable) includes istgt-20100407. FYI: FreeNAS 0.7.2 5226 p3 includes istgt-20100606. FYI: FreeNAS 0.7.2 5226 p4 includes istgt-20100606 + isboot-0.1.1. sysctl MIBs (read only): net.isboot.version net.isboot.nic net.isboot.device hw.ibft.nic_gateway hw.ibft.nic_prefix hw.ibft.target_lun hw.ibft.target_port hw.ibft.target_address hw.ibft.target_name hw.ibft.initiator_address hw.ibft.initiator_name Performance (read from the target): All using Intel PRO/1000 PT Server Adapter. istgt 20100606 + isboot 0.1 with header/data digest(CRC32C): # dd if=/dev/da6 of=/dev/null bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 20.452429 secs (52499477 bytes/sec) istgt 20100606 + isboot 0.1 with header digest: # dd if=/dev/da6 of=/dev/null bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 17.684945 secs (60715022 bytes/sec) istgt 20100606 + isboot 0.1 without digest: # dd if=/dev/da6 of=/dev/null bs=1m count=1k 1024+0 records in 1024+0 records out 1073741824 bytes transferred in 17.508400 secs (61327239 bytes/sec) Notes/Known Issues/Limitations: bootup/reconnect time might be a little long. ifconfig(8),route(8),etc should not change booted NIC and critical path. Unload the module will cause to panic. IPv6 is not tested. DNS is not configured. Queuing is not supported at this time. CHAP is not supported at this time. Can't configure iSCSI parameter without modifing soure code. Can't reject running XPT command when the socket is lost. Can't exchange the session to iscsi_initiator.ko. The source code depend on iscsi initiator's structure. (first I tried to use it, but finally gave up) The controller such as iscontrol(8) is not provided. Documentation is not written. I'm new to the kernel land. If you have any suggestion, please tell me. Download here (the page is Japanese only): isboot-0.1.1 http://shell.peach.ne.jp/aoyama/archives/1179 FreeNAS 0.7.2 5226 p4 http://shell.peach.ne.jp/aoyama/archives/1181 FYI: danny's iscsi initiator: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.4.tar.gz Regards, Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[PATCH] VirtualBox headless VNC support by LibVNCServer (20100211)
Hi, all First, thank you for using my patch. This archive contains individual patch files and modified Makefile. Please select options you want before building. then make with normal way. What's new?: Send ScrollLock when press Ctrl+Scroll or Ctrl+Pause. Fixed 16bpp mode have incorrect settings. (it may cause the viewer confuse, now is send 32bpp instead of 16bpp) Show port 0 when VNC Server disabled. Code cleanup. # cd /usr/ports/emulators/virtualbox-ose # tar xvf /path/to/vboxvnc-20100211.tar.gz # make config # make It provides VNC server for guest OS console access in VBoxHeadless frontend. Supported Options: -v, -vnc, --vnc on|offEnable (default) or disable the VNC Server -a, -vncaddress, --vncaddress ipIP address the VNC server will bind to -p, -vncport, --vncport portPort number the VNC server will bind to -k, -vnckeymap, --vnckeymap keymap Keyboard mapfile (default: builtin US) -S, -vncsecret, --vncsecret secret VNC Authentication secret three options at one line is an equivalent option, for example: -v on, -vnc on, --vnc on are same feature. -v option specify whether VNC server starts in the machine. default is on (enable). -a and -p options specify IP address and port number of VNC server. default IP is wildcard, port is 5900. If you have multiple IPs(NICs) in your system, you can select the listen address of the server. -k option specify the keyboard layout convert from VNC keys to Scancodes. default is US standard 101keys. (I tested only US 101 keyboard) If you want another keyboard, you can spcify the path of kbdmap(5). In standard installation of FreeBSD, it's located in /usr/share/syscons/keymaps/. for example, -k /usr/share/syscons/keymaps/jp.106.kbd uses JP 106 keyboard. -S option specify the password of the VNC server. However, it have security risk in common server. It assumed used with FreeNAS (limited user environment). Please consider the risk by using command line. When starting the VM, the proctitle is changed like below (you can see by ps axww): VBoxHeadless: VM: TestVM4 Port: 5900 Auth: off (VBoxHeadless) Regards, Daisuke Aoyama vboxvnc-20100211.tar.gz Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [PATCH] VirtualBox headless VNC support by LibVNCServer
Thank you for your reply. I put VBox-VNC-20100127.patch in files an modified the paths to be acceptable to the ports tree and applied the Makefile patch and it works well. (I say this as IMO it's easier to try if you distribute it like that :) I think too. I have created it to use with FreeNAS. I assumed that it is used internally. The first mail of FreeBSD ML is here: http://lists.freebsd.org/pipermail/freebsd-emulation/2010-January/007336.html Next time, I will try to change you said. Is there any prospect of being able to build the VNC server extension in parallel with X11/QT4? There might not be problem. I'm not using X11. That is all of the reason. Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [PATCH] VirtualBox headless VNC support by LibVNCServer
Hi, all I updated for 3.1.2_1 and fixed bug of initial pixel format. Before building, install ports/net/libvncserver. I recommend you backup virtualbox-ose directory before doing. Uncheck QT4, X11, NLS by make config before extracting. Howto apply the patch: # cd /usr/ports/emulators/virtualbox-ose # make config # make extract # patch -p /path/to/VBox-VNC-Makefile.patch # patch -p /path/to/VBox-VNC-20100127.patch # make Regards, Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: [PATCH] VirtualBox headless VNC support by LibVNCServer
Sorry, I forgot attached files. - Original Message - From: Daisuke Aoyama aoy...@peach.ne.jp To: freebsd-emulat...@freebsd.org Cc: freebsd-curr...@freebsd.org; freebsd-stable@freebsd.org Sent: Wednesday, January 27, 2010 7:46 PM Subject: Re: [PATCH] VirtualBox headless VNC support by LibVNCServer Hi, all I updated for 3.1.2_1 and fixed bug of initial pixel format. Before building, install ports/net/libvncserver. I recommend you backup virtualbox-ose directory before doing. Uncheck QT4, X11, NLS by make config before extracting. Howto apply the patch: # cd /usr/ports/emulators/virtualbox-ose # make config # make extract # patch -p /path/to/VBox-VNC-Makefile.patch # patch -p /path/to/VBox-VNC-20100127.patch # make Regards, Daisuke Aoyama VBox-VNC-Makefile.patch.gz Description: Binary data VBox-VNC-20100127.patch.gz Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
istgt-20091211 was committed to ports (net/istgt)
Hi, all I released latest version of 0.2 branch. It's now in the ports tree. You can get with portsnap or other method. I also provide FreeNAS 0.7x updater. for more detail: (Japanese)http://shell.peach.ne.jp/aoyama/archives/641 (English)http://sourceforge.net/apps/phpbb/freenas/viewtopic.php?f=53t=4854start=10#p23770 If you use QueueDepth for ESX, recommend depth is more than 32. (below 20 except 0 is unsupported at this time) If your network card looks very slow, then try following setting: MaxBurstLength 65536 MaxRecvDataSegmentLength 4096 Major changes from 20090428(included in 8.0 release): added tested/supported initiators WS2008 R2, ESXi 4.0, XenServer 5.5, Ubuntu 9.10, VirtualBOX 3.0.12, iSCSI Remote Boot 2.3.81, FreeBSD 7.2 + iscsi 2.2.3. changed error messages for errno=54/60 to reset or timeout. fixed StatSN/CmdSN error. fixed crash bug(signal 11) after error has occurred.(include errno=54/60) changed iSCSI diskless boot warnings. fixed sense data bugs in DVD/tape type. added REQUEST_SENSE(SCSIOP=0x03) in disk type. added to support changer device(/dev/chX) in pass-through. fixed CAM timeout/error handling issues in pass-through. I hope this helps you. -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: istgt now supports command queuing in disk type
Hello, I sent change request of ports version. (just now was committed when I wrote mail) What's new? (from 20090323) o starting to support multipath I/O by VMware ESXi (Fix/MRU/RR) o wildcard address listen and translate IP (useful on DHCP) o utilization efficiency of the command queuing was improved o task abort handling in cluster nodes o reduce deadlock and timeout risk (from 20090314) o support command queuing o shrink pre-allocated SCSI sense data buffer from 64K to 4K. o allow full specify eui. and naa. like iqn. o if small PDU, write as one buffer. and many bug fixes The command queuing is disabled by default. If you want to use it, please add QueueDepth key in the LogicalUnit section of your configuration. for example: [LogicalUnit1] # Queuing 0=disabled, 1-255=enabled with specified depth. QueueDepth 16 If you have any problem with command queuing, comment out or specify 0 to disable it. Disabled version is about the same behavior as 20090314. To use wildcard address, edit your configuration like this: [PortalGroup1] # for IPv6 Portal DA1 [::]:3260 # for IPv4 Portal DA1 0.0.0.0:3260 Do not use mix with other IPs. After this change you can see TargetAddress as connected IP. IP address family connected by discovery session is important. If you need IPv6 target address, should use IPv6 in discovery. Also if you need IPv4 target address, should use IPv4. The istgt will reply only one IP address of multiple wildcard address to the initiator. Here is release 20090326: http://shell.peach.ne.jp/aoyama/archives/386 -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
istgt now supports command queuing in disk type
Hello. New release was uploaded in my blog. The command queuing improves especially sequential read by MCS(multiple connections per session) round robin. In my post, I uploaded the screen shots using CrystalDiskMark which is one of popular benchmark in Japan. You can download CrystalDiskMark(multilingual) from: http://crystalmark.info/?lang=en I got the result about 1.5x-3x faster than previous 20090314. If test data was cached, it reached over 200MB/s. Known Issue and Limitations: o queuing is only supported in single initiator environment. o LUN thread might have deadlock when an error has occurred. o write command is still slow. o timeout may occur when using MCS. o single connection may be slower than without queuing. Here is release 20090323: http://shell.peach.ne.jp/aoyama/archives/376 The screen shots show difference between QueueDepth 16 and 0 (disabled queuing). The command queuing is disabled by default. If you want to use it, please add QueueDepth key in the LogicalUnit section of your configuration. for example: [LogicalUnit1] # Queuing 0=disabled, 1-255=enabled with specified depth. QueueDepth 16 Thanks. -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tester wanted for multipath failover iSCSI target software
Oh dear doing the test again caused the client machine to panic, with the following message: panic: solaris assert: 0 == dmu_buf_hold(os, lr-lr_foid, boff, zgd, db), file /usr/src/sys/modules/zfs/../../cddl/controb/opensolaris/uts/common/fs/zfs/zfs_nops.c, line: 955 I have not read the message in my experience. Do you have encountered frequency? -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tester wanted for multipath failover iSCSI target software
Hi, Thank you for reporting. I have tested net/istgt for couple of days with Windows XP and it works more reliable than NetBSD net/iscsi-target. With NetBSD implementation sometimes I lost partition filesystem information after disconnecting server from network or rebooting my computer. Yes, it is one of differences. istgt reports connected information such as SCSI port to the initiator for discriminating multipath and failover path. As a side effect, perhaps more accurate identification is possible. Is there any particular testcases you want to perform? If you use it as usual, it is tested enough. If I had to say, I want to know how much a CPU usage on the target machine. Because istgt is more complicated than iscsi-target. Tested on FreeBSD 7.1-STABLE #0: Wed Mar 11 22:29:33 EET 2009 Did you use the target with ZFS? or UFS? Did you use MCS feature? Thanks, -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tester wanted for multipath failover iSCSI target software
Thank you for reporting. On the other hand I have got some errors that I am trying to get to the bottom of. I set up a zpool laast night on a remote disc using the netbsd initiator and copied about 50 gig of data to it as lots of small files. I then switched to the istgt initiator this morning and am running a scrub on the pool. But it is telling me that there are a sigificant number of errors on the disc, which I wasnt expecting. I am now trying to find out if that is due to write errors using the taret last night, or read errors with the new target this morning. I'm very interested in this case. BTW, is there any way to get istgt to accept connections without needing to specify the initator string ? I am new to all these options for iSCSI having only used the simple netbsd one before. sorry for no documents. special word ALL matches any initiator name/IPs. you can find more sample in istgt.large.conf.sample. [InitiatorGroup256] Comment ALL initiators from ALL IP InitiatorName ALL Netmask ALL Thanks, -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tester wanted for multipath failover iSCSI target software
Hi all, Now istgt is a part of ports. (net/istgt) FreeBSD issue is solved by danny's patch. After applying the patch, iscontrol can connect to istgt. Here is release 20090309 latest committed to ports. http://shell.peach.ne.jp/aoyama/archives/345 If you need anything other than Japanese, please use translation such as google translate. Thanks, -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tester wanted for multipath failover iSCSI target software
I am interested in giving this a try, though not immediately as I am away from the office at the moment. Do I need to apply a patch to iscontrol to make it work though ? I can't work it out from your statement above. Yes, you need. Than ks. Is the intent to integrate with the base system eventually rather than have it in ports ? It would be nice to have a native implementation which could then be integrated with ZFS. istgt is still under development. so I don't think integration. before thinking, I should work to fix more bugs. thank you. -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Tester wanted for multipath failover iSCSI target software
Hello, I'm looking for test users for new iSCSI target software designed for multipath failover cluster nodes. I'm very interested in the virtual machine such as Hyper-V. So I'm also tuning the target for using VMs. I need an environmental report in particular other than FreeBSD 7.1 RELEASE p3 i386/PAE kernel w/ZFS. I welcome the report with other initiators below. If you are interested in this software, please download it from the following site. The tarball contains configure script to build it. Please read README and INSTALL in the tarball for more detail. Tested Initiators: o Microsoft Windows Server 2008 (builtin) o Microsoft iSCSI Initiator 2.08 on WS2003 o Intel iSCSI Remote Boot 2.1.22 o Sun VirtualBOX 2.1.2 (builtin) o VMware ESXi 3.5 Update 3 (builtin) Key Features: o MCS/MPIO for failover (up to 255 concurrent sessions) o SPC-3 Persistent Reservation for cluster nodes o 64bit LBA for over 2TB o Header/Data digest by CRC32C o CHAP w/Mutual authentication o Multiple LUNs and ACLs for portals (experimental features) o iSCSI boot with Intel PRO/1000 Server Adapters o virtual DVDROM/DLT emulator o pass-through device via CAM Known Issues: o globalSAN iSCSI Initiator for Mac OSX does not establish data I/O because of unexpected data segment length. I will plan to fix it in the near future. o FreeBSD initiator can't connect to the target because of StatSN error. I don't know a reason. Here is release 20090308: http://shell.peach.ne.jp/aoyama/archives/342 Later version will be uploaded in this blog. If you need anything other than Japanese, please use translator service. Thanks, -- Daisuke Aoyama ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
