Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux.mageia > #14247 > unrolled thread

Further Suggestions on Dual-Boot with Win10 solicited

Back to article view | Back to alt.os.linux.mageia

Contents

  Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 01:29 +0000
    Re: Further Suggestions on Dual-Boot with Win10 solicited Bobbie Sellers <bliss@mouse-potato.com> - 2016-11-03 19:51 -0700
      Re: Further Suggestions on Dual-Boot with Win10 solicited dlbendigo  <laidlaws@hotkey.net.au> - 2016-11-04 16:07 +1100
        Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 15:21 +0000
      Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 14:11 +0000
        Re: Further Suggestions on Dual-Boot with Win10 solicited Bobbie Sellers <bliss@mouse-potato.com> - 2016-11-04 07:28 -0700
    Re: Further Suggestions on Dual-Boot with Win10 solicited Bit Twister <BitTwister@mouse-potato.com> - 2016-11-04 04:57 +0000
      Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-04 15:45 +0000
    Re: Further Suggestions on Dual-Boot with Win10 solicited Jim Beard <jim.beard@verizon.net> - 2016-11-05 18:46 +0000
      Re: Further Suggestions on Dual-Boot with Win10 solicited Bit Twister <BitTwister@mouse-potato.com> - 2016-11-05 20:25 +0000

#14247 — Further Suggestions on Dual-Boot with Win10 solicited

For a brief period of time, I had Mageia 5 installed on sda1 and win10 on 
sdb, and could switch from one to the other by rebooting and selecting 
which to boot from in the UEFI Bios choices.
I tried to get fancy, and get Grub 2 to present both choices on reboot.  
This too worked, briefly.  Then, I lost the ability to select and boot to 
Win10, followed by loss of ability to boot Mageia 5.
I restored the Grub 2 bootloader, and it now works fine in booting Mageia 
5, but the EFI partition that once held the Microsoft UEFI boot software 
now contains nothing but a path that leads to mageia/grub64.efi.

My belief I could simply reinstall Win10 if things went wrong has proved 
in error.  My attempts to install to /dev/sdb where Win10 had been 
installed fails, with one error message saying the partition is locked.  
I do not know how to "unlock" it, or how to force an install.  I have 
tried disconnecting the disk that has Mageia 5 and installing to Win10 
on /dev/sdb by itself, but too this continues to fail.

Next possibility:  Try to install Win10 under VirtualBox.  The first 
question is whether I should try to install virtualbox and then use a 
Win10 image available from Microsoft (about 4 GB, iso, which I have 
downloaded) or try to install from my Win10 install usb drive (usbstick).

In the first case, I start up virtualbox, tell it to create a new OS, and 
point it to the iso image.  In the second case, I would start up 
virtualbox, tell it to create a new OS, and point to to the usb drive.

Would virtualbox then install from the usb drive?  Or do I need a magic 
incantation to start things off?  How do I enter it, if I do?

So far, I am leaning to using the Mageia virtual box packages and I think 
I need the following mageia rpm packages:
virtualbox-
virtualbox-kernel-
vboxadditions-kernel-
virtualbox-guest-additions-
plus virtualbox-extensions available only from the virtualbox website.

I think all but virtualbox-guest-additions- should be installed before 
trying to create the Win10 virtual machine, and the virtualbox-guest-
additions installed afterward.  Right?

Has anyone done this, or succeeded with a different method?
Does the above sound right?  Have I overlooked something?  

Where should I put the new virtual Win10? I am inclined to put it in the 
ext4 partition I intend to use for Mageia 6 for the moment, and then move 
it elsewhere if it works.  I understand this is possible.  Correct?

I am dithering as usual when I really do not know what I am doing, or 
should be doing.  Any suggestions would be welcome.

Cheers!

jim b.

-- 
UNIX is not user-unfriendly, it merely expects users to be computer-
friendly.

[toc] | [next] | [standalone]

#14248

On 11/03/2016 06:29 PM, Jim Beard wrote:
> For a brief period of time, I had Mageia 5 installed on sda1 and win10 on
> sdb, and could switch from one to the other by rebooting and selecting
> which to boot from in the UEFI Bios choices.
> I tried to get fancy, and get Grub 2 to present both choices on reboot.
> This too worked, briefly.  Then, I lost the ability to select and boot to
> Win10, followed by loss of ability to boot Mageia 5.
> I restored the Grub 2 bootloader, and it now works fine in booting Mageia
> 5, but the EFI partition that once held the Microsoft UEFI boot software
> now contains nothing but a path that leads to mageia/grub64.efi.

	You probably should have had just one EFI partition. Switching
boots though the BIOS is the wrong way to go.
	Have you tried running the grub-organizer?
>
> My belief I could simply reinstall Win10 if things went wrong has proved
> in error.  My attempts to install to /dev/sdb where Win10 had been
> installed fails, with one error message saying the partition is locked.
> I do not know how to "unlock" it, or how to force an install.  I have
> tried disconnecting the disk that has Mageia 5 and installing to Win10
> on /dev/sdb by itself, but too this continues to fail.

	Microsoft really hates anyone messing about, in case you had
not figured that out.
	Have you booted up a GParted and tried to look at the Windows 10
SSD?  You might be able to get past that lock.
>
> Next possibility:  Try to install Win10 under VirtualBox.  The first
> question is whether I should try to install virtualbox and then use a
> Win10 image available from Microsoft (about 4 GB, iso, which I have
> downloaded) or try to install from my Win10 install usb drive (usbstick).
>
> In the first case, I start up virtualbox, tell it to create a new OS, and
> point it to the iso image.  In the second case, I would start up
> virtualbox, tell it to create a new OS, and point to to the usb drive.
>
> Would virtualbox then install from the usb drive?  Or do I need a magic
> incantation to start things off?  How do I enter it, if I do?
>
> So far, I am leaning to using the Mageia virtual box packages and I think
> I need the following mageia rpm packages:
> virtualbox-
> virtualbox-kernel-
> vboxadditions-kernel-
> virtualbox-guest-additions-
> plus virtualbox-extensions available only from the virtualbox website.
>
> I think all but virtualbox-guest-additions- should be installed before
> trying to create the Win10 virtual machine, and the virtualbox-guest-
> additions installed afterward.  Right?
>
> Has anyone done this, or succeeded with a different method?
> Does the above sound right?  Have I overlooked something?
>
> Where should I put the new virtual Win10? I am inclined to put it in the
> ext4 partition I intend to use for Mageia 6 for the moment, and then move
> it elsewhere if it works.  I understand this is possible.  Correct?
>
> I am dithering as usual when I really do not know what I am doing, or
> should be doing.  Any suggestions would be welcome.
>
> Cheers!
>
> jim b.
>

	Wish I could offer more than suggestions but since I won't have Windows 
10 for an indefinite time to mess around with that is all I
can do.

	bliss

-- 
bliss dash SF 4 ever at dslextreme dot com

[toc] | [prev] | [next] | [standalone]

#14253

Bobbie Sellers <bliss@mouse-potato.com> Wrote in message:
> On 11/03/2016 06:29 PM, Jim Beard wrote:
>> For a brief period of time, I had Mageia 5 installed on sda1 and win10 on
>> sdb, and could switch from one to the other by rebooting and selecting
>> which to boot from in the UEFI Bios choices.
>> I tried to get fancy, and get Grub 2 to present both choices on reboot.
>> This too worked, briefly.  Then, I lost the ability to select and boot to
>> Win10, followed by loss of ability to boot Mageia 5.
>> I restored the Grub 2 bootloader, and it now works fine in booting Mageia
>> 5, but the EFI partition that once held the Microsoft UEFI boot software
>> now contains nothing but a path that leads to mageia/grub64.efi.
> 
> 	You probably should have had just one EFI partition. Switching
> boots though the BIOS is the wrong way to go.
> 	Have you tried running the grub-organizer?
>>
>> My belief I could simply reinstall Win10 if things went wrong has proved
>> in error.  My attempts to install to /dev/sdb where Win10 had been
>> installed fails, with one error message saying the partition is locked.
>> I do not know how to "unlock" it, or how to force an install.  I have
>> tried disconnecting the disk that has Mageia 5 and installing to Win10
>> on /dev/sdb by itself, but too this continues to fail.
> 
> 	Microsoft really hates anyone messing about, in case you had
> not figured that out.
> 	Have you booted up a GParted and tried to look at the Windows 10
> SSD?  You might be able to get past that lock.
>>
>> Next possibility:  Try to install Win10 under VirtualBox.  The first
>> question is whether I should try to install virtualbox and then use a
>> Win10 image available from Microsoft (about 4 GB, iso, which I have
>> downloaded) or try to install from my Win10 install usb drive (usbstick).
>>
>> In the first case, I start up virtualbox, tell it to create a new OS, and
>> point it to the iso image.  In the second case, I would start up
>> virtualbox, tell it to create a new OS, and point to to the usb drive.
>>
>> Would virtualbox then install from the usb drive?  Or do I need a magic
>> incantation to start things off?  How do I enter it, if I do?
>>
>> So far, I am leaning to using the Mageia virtual box packages and I think
>> I need the following mageia rpm packages:
>> virtualbox-
>> virtualbox-kernel-
>> vboxadditions-kernel-
>> virtualbox-guest-additions-
>> plus virtualbox-extensions available only from the virtualbox website.
>>
>> I think all but virtualbox-guest-additions- should be installed before
>> trying to create the Win10 virtual machine, and the virtualbox-guest-
>> additions installed afterward.  Right?
>>
>> Has anyone done this, or succeeded with a different method?
>> Does the above sound right?  Have I overlooked something?
>>
>> Where should I put the new virtual Win10? I am inclined to put it in the
>> ext4 partition I intend to use for Mageia 6 for the moment, and then move
>> it elsewhere if it works.  I understand this is possible.  Correct?
>>
>> I am dithering as usual when I really do not know what I am doing, or
>> should be doing.  Any suggestions would be welcome.
>>
>> Cheers!
>>
>> jim b.
>>
> 
> 	Wish I could offer more than suggestions but since I won't have Windows 
> 10 for an indefinite time to mess around with that is all I
> can do.
> 
> 	bliss
> 
> -- 
> bliss dash SF 4 ever at dslextreme dot com
> 

I agree with Bobbie.  They used to say that Windows needed to be 
on /dev/sda1, but I don't think that it is strictly true any longer.

My set-up is:

/dev/sda 1 &3 :Windows machinery.
/dev/sda2 :/boot/EFI for Windows and everything else.
/dev/sda4 :Windows C:
/dev/sda5 :Mageia /.
(etc.)

On sdb, I have:

Sdb1 & 2 : EFI system partitions created by other distros.
The balance is OpenSuse.

update-grub finds what it needs from sdb, and creates a
special kind of link.  I saw its name when update-grub
was running, but it doesn't appear in grub.cfg.  For a while, 
it worked only in Cauldron, although Mga5 had the same
version of Grub2.  Now I have Cauldron as default.

I recently reinstalled Win10, and the only problem was 
a new UUID.

HTH,

Doug.
-- 

[toc] | [prev] | [next] | [standalone]

#14262

On Fri, 04 Nov 2016 16:07:54 +1100, dlbendigo wrote:
> Bobbie Sellers <bliss@mouse-potato.com> Wrote in message:
>> On 11/03/2016 06:29 PM, Jim Beard wrote:
<snip>

> I agree with Bobbie.  They used to say that Windows needed to be on
> /dev/sda1, but I don't think that it is strictly true any longer.
> 
> My set-up is:
> /dev/sda 1 &3 :Windows machinery.
> /dev/sda2 :/boot/EFI for Windows and everything else.
> /dev/sda4 :Windows C:
> /dev/sda5 :Mageia /.
> (etc.)

MicroCenter installed Win10 to what became /dev/sdb.  Due to problems 
trying to install Mageia 5, all drives were disconnected except the ssd 
that became /dev/sda. I installed Mageia5 UEFI, and things looked like 
this.

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 232.9G  0 disk
├─sda1   8:1    0   500M  0 part /boot/EFI #not used by Grub 2 ?
├─sda2   8:2    0  39.1G  0 part /      # mageia5
├─sda3   8:3    0  73.2G  0 part /home  # mageia5home
├─sda4   8:4    0  34.2G  0 part   # mageia6
├─sda5   8:5    0  73.2G  0 part   # mageia6home
└─sda6   8:6    0  12.7G  0 part
sdb      8:16   0 232.9G  0 disk
├─sdb1   8:17   0   450M  0 part #Windows recover
├─sdb2   8:18   0   100M  0 part #Windows & Grub EFI System partition
├─sdb3   8:19   0    16M  0 part #Compaq diagnostics
└─sdb4   8:20   0 232.3G  0 part #/media/win_c2
sdc      8:32   0   1.8T  0 disk
├─sdc1   8:33   0  33.6G  0 part [SWAP]
├─sdc2   8:34   0 150.9G  0 part .....

After reconnecting all drives, the above would dual boot, but I had to 
hit DEL or F2 upon rebooting and select which ssd and partition to boot 
to, each time I wished to reboot to the non-default. 

In trying to put all UEFI boot stuff in the /dev/sda EFI partition and 
boot my choice of Win10 or Linux from a grub2 menu, I did not know the 
range of commands I would need and what to do with them, and somewhere in 
the process the Win10 boot files were deleted.  I have been unable to 
reinstall Win10 to get them back.

At this point, rather than learn new commands including (but probably not 
limited to) efibootmgr, grub2-mkconfig, gdisk -l, and use a suitably 
modified version of /etc/grub.d/40_custom (below) with grub2-mkconfig to 
set up a Win10 entry in the grub2 menu, I think I will try for the 
virtualbox approach.

Among other problems, the /dev/sdb was originally split into two 
partitions, and Win10 installed as it wished in the first.  Win10 created 
four partitions, leaving 232GB unallocated.  But now, all the unallocated 
space appears to be part of a single partion that includes the original 
sdb4.  I can't start Win10, but anticipate that would be a problem if I 
could.  If I can make vbox work, simply erasing the /dev/sdb ssd and 
creating ext partitions on it may be the best thing to do.
 
Anyway, part of the recipe for adding an entry to the grub2 menu (that I 
did not know) seems to be,

edit /etc/grub.d/40_custom and add:
menuentry 'Windows' {
     insmod part_gpt
     insmod fat
     insmod chain
     set root='hd0,gpt2'
     chainloader ($root)/EFI/Microsoft/Boot/bootmgfw.efi
}
 

> On sdb, I have:
> 
> Sdb1 & 2 : EFI system partitions created by other distros.
> The balance is OpenSuse.
> 
> update-grub finds what it needs from sdb, and creates a special kind of
> link.  I saw its name when update-grub was running, but it doesn't
> appear in grub.cfg.  For a while,
> it worked only in Cauldron, although Mga5 had the same version of Grub2.
>  Now I have Cauldron as default.
> 
> I recently reinstalled Win10, and the only problem was a new UUID.

??? Sdb1 & 2 : EFI system partitions created by other distros.

Do you have a separate EFI partition for each distro?  How do you keep 
them separate and choose among them?  Do all show on your grub2




-- 
UNIX is not user-unfriendly, it merely expects users to be computer-
friendly.

[toc] | [prev] | [next] | [standalone]

#14260

On Thu, 03 Nov 2016 19:51:37 -0700, Bobbie Sellers wrote:

> On 11/03/2016 06:29 PM, Jim Beard wrote:
>> For a brief period of time, I had Mageia 5 installed on sda1 and win10
>> on sdb, and could switch from one to the other by rebooting and
>> selecting which to boot from in the UEFI Bios choices.
>> I tried to get fancy, and get Grub 2 to present both choices on reboot.
>> This too worked, briefly.  Then, I lost the ability to select and boot
>> to Win10, followed by loss of ability to boot Mageia 5.
>> I restored the Grub 2 bootloader, and it now works fine in booting
>> Mageia 5, but the EFI partition that once held the Microsoft UEFI boot
>> software now contains nothing but a path that leads to
>> mageia/grub64.efi.
> 
> 	You probably should have had just one EFI partition. Switching
> boots though the BIOS is the wrong way to go.
> 	Have you tried running the grub-organizer?

Concur on just one EFI partition.  The Win10 ESP created by the 
MicroCenter install was only 100MB, and I had seen recommendations for 
300MB.  In addition, the tools I used to try to see how full the Win10 
ESP was looked like it was full.  Either I was using the wrong tools or 
misreading, as later looks at it showed only 21MB.

I had hoped to move the Win10 ESP contents to the Mageia5 ESP vfat 
partition, but copying them over did not work, and my attempts to use 
grub2-update to integrate the two ultimately failed.

>>
>> My belief I could simply reinstall Win10 if things went wrong has
>> proved in error.  My attempts to install to /dev/sdb where Win10 had
>> been installed fails, with one error message saying the partition is
>> locked. I do not know how to "unlock" it, or how to force an install. 
>> I have tried disconnecting the disk that has Mageia 5 and installing to
>> Win10 on /dev/sdb by itself, but too this continues to fail.
> 
> 	Microsoft really hates anyone messing about, in case you had
> not figured that out.
> 	Have you booted up a GParted and tried to look at the Windows 10
> SSD?  You might be able to get past that lock.

Yes, I had booted with gparted two or three times trying to look at 
things.  No joy, perhaps because I was not familiar with gparted or the 
correct commands to use.

>> Next possibility:  Try to install Win10 under VirtualBox.  The first
>> question is whether I should try to install virtualbox and then use a
>> Win10 image available from Microsoft (about 4 GB, iso, which I have
>> downloaded) or try to install from my Win10 install usb drive
>> (usbstick).
>>
>> In the first case, I start up virtualbox, tell it to create a new OS,
>> and point it to the iso image.  In the second case, I would start up
>> virtualbox, tell it to create a new OS, and point to to the usb drive.
>>
>> Would virtualbox then install from the usb drive?  Or do I need a magic
>> incantation to start things off?  How do I enter it, if I do?
>>
>> So far, I am leaning to using the Mageia virtual box packages and I
>> think I need the following mageia rpm packages:
>> virtualbox-
>> virtualbox-kernel-
>> vboxadditions-kernel-
>> virtualbox-guest-additions-
>> plus virtualbox-extensions available only from the virtualbox website.
>>
>> I think all but virtualbox-guest-additions- should be installed before
>> trying to create the Win10 virtual machine, and the virtualbox-guest-
>> additions installed afterward.  Right?
>>
>> Has anyone done this, or succeeded with a different method?
>> Does the above sound right?  Have I overlooked something?
>>
>> Where should I put the new virtual Win10? I am inclined to put it in
>> the ext4 partition I intend to use for Mageia 6 for the moment, and
>> then move it elsewhere if it works.  I understand this is possible. 
>> Correct?
>>
>> I am dithering as usual when I really do not know what I am doing, or
>> should be doing.  Any suggestions would be welcome.
>>
>> Cheers!
>>
>> jim b.
>>
>>
> 	Wish I could offer more than suggestions but since I won't have 
Windows
> 10 for an indefinite time to mess around with that is all I can do.
> 
> 	bliss





-- 
UNIX is not user-unfriendly, it merely expects users to be computer-
friendly.

[toc] | [prev] | [next] | [standalone]

#14261

On 11/04/2016 07:11 AM, Jim Beard wrote:
> On Thu, 03 Nov 2016 19:51:37 -0700, Bobbie Sellers wrote:
>
>> On 11/03/2016 06:29 PM, Jim Beard wrote:
>>> For a brief period of time, I had Mageia 5 installed on sda1 and win10
>>> on sdb, and could switch from one to the other by rebooting and
>>> selecting which to boot from in the UEFI Bios choices.
>>> I tried to get fancy, and get Grub 2 to present both choices on reboot.
>>> This too worked, briefly.  Then, I lost the ability to select and boot
>>> to Win10, followed by loss of ability to boot Mageia 5.
>>> I restored the Grub 2 bootloader, and it now works fine in booting
>>> Mageia 5, but the EFI partition that once held the Microsoft UEFI boot
>>> software now contains nothing but a path that leads to
>>> mageia/grub64.efi.
>>
>> 	You probably should have had just one EFI partition. Switching
>> boots though the BIOS is the wrong way to go.
>> 	Have you tried running the grub-organizer?
>
> Concur on just one EFI partition.  The Win10 ESP created by the
> MicroCenter install was only 100MB, and I had seen recommendations for
> 300MB.  In addition, the tools I used to try to see how full the Win10
> ESP was looked like it was full.  Either I was using the wrong tools or
> misreading, as later looks at it showed only 21MB.
>
> I had hoped to move the Win10 ESP contents to the Mageia5 ESP vfat
> partition, but copying them over did not work, and my attempts to use
> grub2-update to integrate the two ultimately failed.
>
>>>
>>> My belief I could simply reinstall Win10 if things went wrong has
>>> proved in error.  My attempts to install to /dev/sdb where Win10 had
>>> been installed fails, with one error message saying the partition is
>>> locked. I do not know how to "unlock" it, or how to force an install.
>>> I have tried disconnecting the disk that has Mageia 5 and installing to
>>> Win10 on /dev/sdb by itself, but too this continues to fail.
>>
>> 	Microsoft really hates anyone messing about, in case you had
>> not figured that out.
>> 	Have you booted up a GParted and tried to look at the Windows 10
>> SSD?  You might be able to get past that lock.
>
> Yes, I had booted with gparted two or three times trying to look at
> things.  No joy, perhaps because I was not familiar with gparted or the
> correct commands to use.

	You have to spend some time with it.  You can learn to use it.
After all I did that and I am 79 years old though I may have learned 
about GPartEd a bit earlier.  While Mandriva worked on my old machines
I preferred to use it's tools.
In addition <http://gparted.org/display-doc.php?name=help-manual&lang=C>

>
>>> Next possibility:  Try to install Win10 under VirtualBox.  The first
>>> question is whether I should try to install virtualbox and then use a
>>> Win10 image available from Microsoft (about 4 GB, iso, which I have
>>> downloaded) or try to install from my Win10 install usb drive
>>> (usbstick).
>>>
>>> In the first case, I start up virtualbox, tell it to create a new OS,
>>> and point it to the iso image.  In the second case, I would start up
>>> virtualbox, tell it to create a new OS, and point to to the usb drive.
>>>
>>> Would virtualbox then install from the usb drive?  Or do I need a magic
>>> incantation to start things off?  How do I enter it, if I do?
>>>
>>> So far, I am leaning to using the Mageia virtual box packages and I
>>> think I need the following mageia rpm packages:
>>> virtualbox-
>>> virtualbox-kernel-
>>> vboxadditions-kernel-
>>> virtualbox-guest-additions-
>>> plus virtualbox-extensions available only from the virtualbox website.
>>>
>>> I think all but virtualbox-guest-additions- should be installed before
>>> trying to create the Win10 virtual machine, and the virtualbox-guest-
>>> additions installed afterward.  Right?
>>>
>>> Has anyone done this, or succeeded with a different method?
>>> Does the above sound right?  Have I overlooked something?
>>>
>>> Where should I put the new virtual Win10? I am inclined to put it in
>>> the ext4 partition I intend to use for Mageia 6 for the moment, and
>>> then move it elsewhere if it works.  I understand this is possible.
>>> Correct?
>>>
>>> I am dithering as usual when I really do not know what I am doing, or
>>> should be doing.  Any suggestions would be welcome.
>>>
>>> Cheers!
>>>
>>> jim b.

	Other posters have given you good information on setting it up.
	
	Good luck or as the Japanese prefer"Do your Best".

	bliss

-- 
bliss dash SF 4 ever at dslextreme dot com

[toc] | [prev] | [next] | [standalone]

#14251

On Fri, 4 Nov 2016 01:29:29 -0000 (UTC), Jim Beard wrote:
>
>
> Next possibility:  Try to install Win10 under VirtualBox.  The first 
> question is whether I should try to install virtualbox and then use a 
> Win10 image available from Microsoft (about 4 GB, iso, which I have 
> downloaded) or try to install from my Win10 install usb drive (usbstick).

You need to use the KISS methodology. Use the downloaded iso. There is
no good reason to add in another layer of possible failure.


> In the first case, I start up virtualbox, tell it to create a new OS, and 
> point it to the iso image.  In the second case, I would start up 
> virtualbox, tell it to create a new OS, and point to to the usb drive.
>
> Would virtualbox then install from the usb drive?  Or do I need a magic 
> incantation to start things off?  How do I enter it, if I do?

One more time. Forget about a usb drive VirtualBox guest install.
Just select the downloaded iso.

Please at least glance through
  https://itsfoss.com/install-windows-10-virtualbox-linux/
before trying the w10 install.

> So far, I am leaning to using the Mageia virtual box packages and I think 
> I need the following mageia rpm packages:
> virtualbox-
> virtualbox-kernel-
> vboxadditions-kernel-
> virtualbox-guest-additions-
> plus virtualbox-extensions available only from the virtualbox website.

If you pick the virtualbox rpm it will drag the required kernels and
whatnot to create your first guest.

Do yourself a favor, install virtualbox rpm. Reboot, create your new
guest and pick your mageia5 iso and play around. Once that works, you
can download/install the extension pack, reboot, verify you know how
to enable the usb drive in the guest and see what happens when you
jack in the device.

At this point, you would know everything does work, and any problems
from this point forward will be self-induced, or quirks with the new
guest OS.



> Where should I put the new virtual Win10? I am inclined to put it in the 
> ext4 partition I intend to use for Mageia 6 for the moment, and then move 
> it elsewhere if it works.  I understand this is possible.  Correct?

Yes, but why screw around shuffling stuff around. Sit down, draw
pictures if needed, plan your disk usage, build desired partitions
then proceed.


> I am dithering as usual when I really do not know what I am doing, or 
> should be doing.  Any suggestions would be welcome.

A standard Mageia VB install will have you creating your Virtual guest
machines in your login account.

Not a good default as far as being able to backup $HOME.

I created a separate partition for all VM guest storage and pointed
$HOME/.VirtualBox at the storage partition.

$ ls -al $HOME/.VirtualBox
lrwxrwxrwx 1 bittwister bittwister 11 Jul 31 18:12 /home/bittwister/.VirtualBox -> /vmguest

$ df -h /vmguest
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda9       357G  251G  102G  72% /vmguest

$ ls
CentOS_6.5_64     md2010_2             mga5_64            slack_4_02
debian_7_6_0_64   md2011_0             mga5_64_Clone      suse_42_2
del_me            md2011_0_64_install  mga6_64            test_iso
fedora_23_10_64   mga2_64              mga6_64_Clone      ubuntu_14_04
kubuntu_14_04_64  mga3_64              mga6_base          ubuntu_15_04
kubuntu_15_04     mga4_64              pcl64_kde_2013_04  win_7

[toc] | [prev] | [next] | [standalone]

#14263

On Fri, 04 Nov 2016 04:57:55 +0000, Bit Twister wrote:

> On Fri, 4 Nov 2016 01:29:29 -0000 (UTC), Jim Beard wrote:

> You need to use the KISS methodology. Use the downloaded iso. There is
> no good reason to add in another layer of possible failure.

> One more time. Forget about a usb drive VirtualBox guest install.
> Just select the downloaded iso.
> 
> Please at least glance through
>   https://itsfoss.com/install-windows-10-virtualbox-linux/
> before trying the w10 install.

An excellent set of instructions.

> If you pick the virtualbox rpm it will drag the required kernels and
> whatnot to create your first guest.
> 
> Do yourself a favor, install virtualbox rpm. Reboot, create your new
> guest and pick your mageia5 iso and play around. Once that works, you
> can download/install the extension pack, reboot, verify you know how to
> enable the usb drive in the guest and see what happens when you jack in
> the device.
> 
> At this point, you would know everything does work, and any problems
> from this point forward will be self-induced, or quirks with the new
> guest OS.
> 
> 
> 
>> Where should I put the new virtual Win10? I am inclined to put it in
>> the ext4 partition I intend to use for Mageia 6 for the moment, and
>> then move it elsewhere if it works.  I understand this is possible. 
>> Correct?
> 
> Yes, but why screw around shuffling stuff around. Sit down, draw
> pictures if needed, plan your disk usage, build desired partitions then
> proceed.
w
> A standard Mageia VB install will have you creating your Virtual guest
> machines in your login account.
> 
> Not a good default as far as being able to backup $HOME.
> 
> I created a separate partition for all VM guest storage and pointed
> $HOME/.VirtualBox at the storage partition.
> 
> $ ls -al $HOME/.VirtualBox lrwxrwxrwx 1 bittwister bittwister 11 Jul 31
> 18:12 /home/bittwister/.VirtualBox -> /vmguest
> 
> $ df -h /vmguest Filesystem      Size  Used Avail Use% Mounted on
> /dev/sda9       357G  251G  102G  72% /vmguest
> 
> $ ls CentOS_6.5_64     md2010_2             mga5_64 .....         

The above saved and printed out.  Now to decide when to take the plunge.

Cheers!

jim

-- 
UNIX is not user-unfriendly, it merely expects users to be computer-
friendly.

[toc] | [prev] | [next] | [standalone]

#14267

Windows 10 is now installed under VirtualBox, thanks to the guidance from 
BitTwister.

Getting the details ironed out will take some time.  Some settings I 
expected to be available are grayed out, but the vmWin10 is working.  
Minimal goal appears to be accomplished.  (Of course, I thought that 
about dual-install of Win10 to one SSD and Mageia5 to another, until all 
the Win10 boot files disappeared...)  

Scuttlebutt has it I have 30 days grace before I have to register the 
"new" Win10.  I tried registering but was told the product was already in 
use.  If needed, I have the phone number of the MS people that deal with 
that, but will try things out for a time before trying to officially 
register and clean up the account.

Cheers!

jim b.

-- 
UNIX is not user-unfriendly, it merely expects users to be computer-
friendly.

[toc] | [prev] | [next] | [standalone]

#14268

On Sat, 5 Nov 2016 18:46:13 -0000 (UTC), Jim Beard wrote:

> Getting the details ironed out will take some time.  Some settings I 
> expected to be available are grayed out, but the vmWin10 is working.  

We can only guess that would be things like USB device access.
They will work when extension pack is installed.

Please note that everything will play nice if you keep VBox release
and extension release the same. 

> Scuttlebutt has it I have 30 days grace before I have to register the 
> "new" Win10.  I tried registering but was told the product was already in 
> use.

Yep, product number of original install was tied to hardware it was
originally installed.

I was afraid a large update to WIN7 might crash w7 so I cloned it did
the update. I decided what the heck, just run with the clone.
Day or so lager got the notification new install on different hardware
and I lost one of my licenses.

> If needed, I have the phone number of the MS people that deal with 
> that,

Yep, otherwise it will quit working.

> but will try things out for a time before trying to officially 
> register and clean up the account.

Well, I would suggest getting updates and whatnot done as soon as
possible, collect all paperwork, serial numbers, product number,,,,,
and be prepared to pay M$ $$$.$$ for your new w10 virtual box installation.

[toc] | [prev] | [standalone]

Back to top | Article view | alt.os.linux.mageia

csiph-web