Re: LAN connectivity via VirtualBox to MS Win
On 03/29/2016 12:05 PM, Stephen John Smoogen wrote: On 29 March 2016 at 12:41, Yasha Karantwrote: My understanding is that 802.11 NAT, etc., connectivity from SL 7 to VirtualBox to MS Win does not work because the kernel releases for SL 7 no longer support this possibility. I know it functions in SL 6 because my spouse still has SL 6 on her laptop (her machine is underprovisioned effectively to run a 64 bit OS and it is not cost effective to re-provision the machine, although the CPU is an X86-64) and this works. This is necessary to run an application that must connect to the Internet and is not available for native Linux, only MS Win and Mac OS X. (For those who are curious, the application is an USA income tax preparation/paying program of which we have used an annual edition for many years under MS Win under VirtualBox under SL.) I have migrated my machines to SL 7. Given this, if I instead connect using 802.3 to a 802.3 port and do not use 802.11, will the standard NAT I mention above work? My understanding from previous responses/posts to this list is that the SL7 kernel series still does provide this necessary support for 802.3 but not 802.11. I have attempted to use a USB port 802.11 WNIC that is supported under Linux and purportedly under MS Win 7; VirtualBox does redirect the USB device to MS Win and MS Win "sees" it. However, the MS Win driver is lacking, and unless I have Internet MS Win connectivity, I do not know how to get the MS Win driver. Under MS Win, the driver seems to be gotten automagically from some MS Win repository, possibly one from Microsoft. If at all possible, I do not want to do any non-automagic systems work on MS Win, particularly as in most cases this seems to involve regedit (editing the MS Win 'registry", a poorly constructed and documented structure). Any information will be appreciated; otherwise, I will need to use my wife's SL 6 machine. Yasha Karant Virtual machines should be able to nat through the system to 802.11 networks. They cannot bridge to the 802.11 network. I regret to state that what you suggest, NAT, works fine with VirtualBox under SL 6 but does not work with SL 7. In fact, when I upgraded from SL 6 to SL 7 is when I first discovered this -- and the information that I believe I received on this SL list indicated that NAT to a 802.11 WNIC on the host SL machine would not work because of changes in the kernel from SL 6 to SL 7. If I am incorrect, please indicate how this is to be configured on the host, VirtualBox, and the MS Win 7 guest. On my wife's SL 6 machine, what you suggest works seamlessly with no configuration work on my part other than to specify NAT for VirtualBox via the VirtualBox GUI configuration screens.
Identical disks, different # sectors
General Linux question, y'all seem very helpful generally, hope this is o.k. I noticed that a disk in an mdadm software RAID10 array had been automatically removed. I pulled it, popped in a new disk that is the EXACT same model as several disks already in the system and the array... ran fdisk on it, created a partition, put a disk label on it, then tried to add it, and got "not large enough to join array" as an error message. It seems like the new disk is one sector smaller. Am I just out of luck with this disk, because the firmware has decided to nuke one sector? Makes buying spares, and having them on hand, pretty dicey if such is the case. Have two on order at the moment. This is the second time I've been led a merry go round simply trying to replace a disk in this array, it is seriously souring me on mdadm and software RAID in general (not that I was a big fan of it anyway). Any suggestions? This is part of a dual clustered system, two RAID10 arrays in a glusterfs, so one missing drive isn't a crisis, but obviously less than ideal. Regards, Thomas Leavitt [root@system1 ~]# fdisk -l /dev/sdb1 Disk /dev/sdb1: 1000.2 GB, 1000203837440 bytes 255 heads, 63 sectors/track, 121601 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x [root@system1 ~]# fdisk -l /dev/sdk1 Disk /dev/sdk1: 1000.2 GB, 1000202241024 bytes 255 heads, 63 sectors/track, 121600 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x lshw description: ATA Disk product: WDC WD1003FBYX-0 vendor: Western Digital physical id: 0.b.0 bus info: scsi@0:0.11.0 logical name: /dev/sdb version: 1V02 serial: WD-WCAW35919858 size: 931GiB (1TB) capacity: 931GiB (1TB) description: ATA Disk product: WDC WD1003FBYX-0 vendor: Western Digital physical id: 0.e.0 bus info: scsi@0:0.14.0 logical name: /dev/sdk version: 1V02 serial: WD-WCAW33395036 size: 931GiB (1TB) capacity: 931GiB (1TB) [root@sapphire ~]# mdadm --manage /dev/md3 --add /dev/sdk1 mdadm: /dev/sdk1 not large enough to join array -- Thomas Leavitt (tleav...@eag.com) Interim Sr. Linux IT Consultant (880 IT Services) 831-469-3382 (Google Voice forwards to 880 IT cell, accepts SMS) 1-408-454-4569 (desk) This e-mail may contain privileged or confidential information. If you are not the intended recipient: (1) you may not disclose, use, distribute, copy or rely upon this message or attachment(s); and (2) please notify the sender by reply e-mail, and then delete this message and its attachment(s). EAG, Inc. and its affiliates disclaim all liability for any errors, omissions, corruption or virus in this message or any attachments.
Re: LAN connectivity via VirtualBox to MS Win
On 29 March 2016 at 12:41, Yasha Karantwrote: > My understanding is that 802.11 NAT, etc., connectivity from SL 7 to > VirtualBox to MS Win does not work because the kernel releases for SL 7 no > longer support this possibility. I know it functions in SL 6 because my > spouse still has SL 6 on her laptop (her machine is underprovisioned > effectively to run a 64 bit OS and it is not cost effective to re-provision > the machine, although the CPU is an X86-64) and this works. This is > necessary to run an application that must connect to the Internet and is not > available for native Linux, only MS Win and Mac OS X. (For those who are > curious, the application is an USA income tax preparation/paying program of > which we have used an annual edition for many years under MS Win under > VirtualBox under SL.) I have migrated my machines to SL 7. > > Given this, if I instead connect using 802.3 to a 802.3 port and do not use > 802.11, will the standard NAT I mention above work? My understanding > from previous responses/posts to this list is that the SL7 kernel series > still does provide this necessary support for 802.3 but not 802.11. > > I have attempted to use a USB port 802.11 WNIC that is supported under Linux > and purportedly under MS Win 7; VirtualBox does redirect the USB device to > MS Win and MS Win "sees" it. However, the MS Win driver is lacking, and > unless I have Internet MS Win connectivity, I do not know how to get the MS > Win driver. Under MS Win, the driver seems to be gotten automagically from > some MS Win repository, possibly one from Microsoft. If at all possible, I > do not want to do any non-automagic systems work on MS Win, particularly as > in most cases this seems to involve regedit (editing the MS Win 'registry", > a poorly constructed and documented structure). > > Any information will be appreciated; otherwise, I will need to use my wife's > SL 6 machine. > > Yasha Karant Virtual machines should be able to nat through the system to 802.11 networks. They cannot bridge to the 802.11 network. -- Stephen J Smoogen.