Re: Installing truble with Netbsd 6.1.5 on Windows8.1 with HyperV
Old story. Have a look at https://mail-index.netbsd.org/current-users/2013/04/24/msg022584.html . Basically you have to disable ACPI and SMP (stop to boot prompt and do 'boot netbsd -12). Nevertheless the emulated Tulip is not that great, and with SMP not working the options become less and less. FreeBSD 10.1 has Hyper-V support out of the box; Freebsd 9.3 - after a minor setup. I guess the issue is not that important for NetBSD development, porting of the whole FreeBSD suite would not be trivial as far as I can see it. I can try -current later. Chavdar Ivanov On Wed, 29 Apr 2015 at 14:50 Maurizio Caloro mau...@gmx.ch wrote: Hello i want to Install NetBsd6.1.5 on Windows 8.1 Hyper-V and i have two diffrent problems if i Login to session and i write anything: sssooo ee nnnttt rr liii thhh eemplle. Also me interface tlp0 dont become any IP dmesg ¦ grep tlp tlp0 at pci0 dev 19 function 0: DECchip 21240A Ethernet, pass 2.0 tlp: flags=8802=Broadcast,Simplex,Multicast mtu 1500 Address: xx:xx:xx:xx:xx:xx Medi: Ethernet 100BaxeTX Status: Active lo0: flags=8049=Broadcast,Running,Multicast mtu 33192 inet 127.0.0.1 ACPI are Disabled
RAID and GPT
Right now most of my systems have disks = 2T, and disklabel, except for data-only external drives that are GPT. I realize that booting off gpt and gpt/raid is perhaps too hard, so all of this is asked in the context of loading a kernel from a USB stick that will then have root on a parition on a RAID1 set. Normally I - use a pair of identical disks - set up a disklabel with a single partition of type raid - configure a RAID1 set, marked -A root - within the /dev/raid0d, disklabel, with a as root at 0, b swap, and so on I am wondering about: - a pair of identical 4T disks - GPT, with each having a single partition starting at 64, type 'raid' - a RAID1 of what will be configured as /dev/dk0 and /dev/dk1, marked as -A root - within raid0, gpt label, and partitions index 1 start=64 size=8G root index 2 size=64G /usr index 3 size=rest /home or something like that. Specifically, I wonder if the raid autoconf will find a ffs root only at 0 offset, because it doesn't parse the label, or if it recurses. Will the inner GPT partitions just show up (as dk2/3/4?)? Can I configure a kernel with root on /dev/dk2 (but that seems non-robust if half of my raidset is missing)? And I wonder how much of this works on netbsd5 or netbsd6, vs 7/current. Alternatively, if I have 2 x 4T disks, and wants to run NetBSD in something functionally similar to the above, what should I do? (It seems obvious that the thing to do is buy 2 x 240G SSD, make them into a raid1 pair with good old-fashioned disklabel, marked -A root, and put root/usr on them, and use the spinning disks for /home as a second -A yes pair, except that this is for a system that can only take 2 disks.) Apologies if I have been asking this before and I'm being fuzzy, but I think my previous query was about gpt booting. pgpDevK4TVXrR.pgp Description: PGP signature
Installing truble with Netbsd 6.1.5 on Windows8.1 with HyperV
Hello i want to Install NetBsd6.1.5 on Windows 8.1 Hyper-V and i have two diffrent problems if i Login to session and i write anything: sssooo ee nnnttt rr liii thhh eemplle. Also me interface tlp0 dont become any IP dmesg ¦ grep tlp tlp0 at pci0 dev 19 function 0: DECchip 21240A Ethernet, pass 2.0 tlp: flags=8802=Broadcast,Simplex,Multicast mtu 1500 Address: xx:xx:xx:xx:xx:xx Medi: Ethernet 100BaxeTX Status: Active lo0: flags=8049=Broadcast,Running,Multicast mtu 33192 inet 127.0.0.1 ACPI are Disabled
Re: RAID and GPT
g...@ir.bbn.com (Greg Troxel) writes: I am wondering about: - a pair of identical 4T disks - GPT, with each having a single partition starting at 64, type 'raid' - a RAID1 of what will be configured as /dev/dk0 and /dev/dk1, marked as -A root - within raid0, gpt label, and partitions index 1 start=64 size=8G root index 2 size=64G /usr index 3 size=rest /home or something like that. Specifically, I wonder if the raid autoconf will find a ffs root only at 0 offset, because it doesn't parse the label, or if it recurses. RAID autoconf will tell the kernel to use partition 'a' of the RAID device as root, assuming you configured with -A forceroot (-A softroot won't work if you didn't boot from the raid). If that partition 'a' corresponds to a wedge (same device, offset, size), that wedge will be automatically used instead, the underlying device would fail with EBUSY. But you don't have a disklabel on the raid device, so the default (faked) disklabel will be checked which puts partition 'a' at offset 0 and spans the whole disk (clamped to 2TB with netbsd-7). There won't be any corresponding wedge, and the attempt to use partition 'a' will fail. One option is to put multiple RAID sets on the disks and use one small enough for a disklabel for the root partition. Using multiple RAID sets has the advantage that recovering can be faster, but you need to be careful to avoid parallel fsck runs. Will the inner GPT partitions just show up (as dk2/3/4?)? Can I configure a kernel with root on /dev/dk2 (but that seems non-robust if half of my raidset is missing)? You can build a kernel to boot from a wedge by name with some hacking since config(8) doesn't parse such a configuration yet. You could also try to use multiboot and tell the kernel to use a named wedge as root device. My last experience with multiboot (with our bootloader) wasn't successful, but grub could work. And I wonder how much of this works on netbsd5 or netbsd6, vs 7/current. netbsd-5/-6 have further issues with disks 2TB. Alternatively, if I have 2 x 4T disks, and wants to run NetBSD in something functionally similar to the above, what should I do? Here are some of my experiences with using large disks: http://wiki.netbsd.org/users/mlelstv/using-large-disks/ -- -- Michael van Elst Internet: mlel...@serpens.de A potential Snark may lurk in every tree.
