thanks, i will look it up and yes, the night is my kingdom
2018-03-12 0:50 GMT+01:00 <linux....@gmail.com>: > Did you turn on update during install? If off, you could be suffering from > an installer bug that I found by searching for the string you gave. Look > here > https://forums.linuxmint.com/viewtopic.php?t=241723 > > Here's the search string that I used > > "package Grub-efi-amd64-signed" cannot be written to /target > > There were other hits. While Linux Mint is discussed, the big could be > more generic to ubuntu - of this is the cause. > > I did turn on downloading of updates during installation. > > It looks like you are staying up very late! High luck. > > -- Roger B. > linux....@gmail.com > > -----Original Message----- > From: Teach <pbrte...@gmail.com> > To: Xubuntu Support and User Discussions <xubuntu-users@lists.ubuntu.com> > Sent: Sun, 11 Mar 2018 19:13 > Subject: Re: [xubuntu-users] Xubuntu 17.10.1 for Virtualbox to run > Windows10 > > Thanks to all for the reactions on my request. > With your help and advices I decided to start with simply dual boot, as I > indeed do not have to use booth on regulary base. > So i check the Bios and find that bios is running EUFI and that > virtualization is ON, and Fastboot is OFF, and SecureBoot is OFF. > I started with xubuntu-16.04-desktop-amd64.iso on DVD, choose my language > (nederlands) and keyboard (belgian), fill in name, and password, and > everything was running fine till the screen showed the message "thank you > for choosing Xubuntu" and I had > the errot message "*package Grub-efi-amd64-signed" cannot be written to > /target" *and *"please understand that the system will not reboot in > Xubuntu, we will end this installation"* (as it was written in Dutch I > give you a tranlation ;-). > > I repeat this installation twice, but with the same result. > > Any ideas why? > > Paul > > 2018-03-11 21:47 GMT+01:00 Ralf Mardorf <silver.bul...@zoho.com>: > >> On Sun, 11 Mar 2018 21:26:19 +0100, Antoine Pitrou wrote: >> >And, yes, of course a SSD makes things massively better for any VM. >> >> That's the whole point. The reason I'm using vbox with QCOW instead of >> VDI was the plan to migrate from vbox to KVM. As a side joke, it would >> require QCOW2 or RAW to migrate directly, however, while on my old >> machine SSD under SATA2 wasn't that much of an enhancement, it became a >> pleasure when migrating to my new SATA3 machine ;). Indeed, vbox still >> has got disadvantages, KVM unlikely does has got, but IMO it's no worse >> the hassle to prefer a less user friendly VM over vbox, unless there >> should be a really, really good reason to do this. Regarding >> performance the bottleneck were HDDs as well as SDD drives run under >> SATA2 instead of SATA3. Once you are using SATA3 and SSDs there is no >> performance issue. Just for very, very specific usage, vbox is utter >> crap and it's really worse to consider to migrate to a VM that >> requieres much more maintenance. YMMV! >> >> >> -- >> xubuntu-users mailing list >> xubuntu-users@lists.ubuntu.com >> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm >> an/listinfo/xubuntu-users >> > > > -- > xubuntu-users mailing list > xubuntu-users@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/xubuntu-users > >
-- xubuntu-users mailing list xubuntu-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users