Re: [gentoo-user] Problem starting VM image on QEMU

[Alexander Kapshuk]

On Fri, Jul 14, 2017 at 7:43 PM, Mick  wrote:
> On Friday 14 Jul 2017 19:02:55 Alexander Kapshuk wrote:
>> On Fri, Jul 14, 2017 at 6:31 PM, Mick  wrote:
>
>> > Trying to start it gives:
>> >
>> > $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  --
>> > -
>> > curses
>> > -bash: ./coreos_production_qemu.sh: Permission denied
>
>> Try running the script in trace mode as yourself:
>> bash -x coreos_production_qemu.sh etc.
>>
>> See if that reveals anything useful.
>
> Ha!  What do you know?  Running it with bash -x in front I was able to execute
> it ... hmmm ... OK ... it seems the partition had been mounted as noexec ...
>
> /dev/sda11 on /data type ext4 (rw,nosuid,nodev,noexec,noatime,data=ordered)
> none on /run/user/1000 type tmpfs (rw,relatime,mode=700,uid=1000)
>
> A clear case of mea culpa!
>
> Thanks for helping me spot this.  :-)
>
> --
> Regards,
> Mick

No worries at all.
Good to hear it worked out for you.

Re: [gentoo-user] Problem starting VM image on QEMU

[Mick]

On Friday 14 Jul 2017 19:02:55 Alexander Kapshuk wrote:
> On Fri, Jul 14, 2017 at 6:31 PM, Mick  wrote:

> > Trying to start it gives:
> > 
> > $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  --
> > -
> > curses
> > -bash: ./coreos_production_qemu.sh: Permission denied

> Try running the script in trace mode as yourself:
> bash -x coreos_production_qemu.sh etc.
> 
> See if that reveals anything useful.

Ha!  What do you know?  Running it with bash -x in front I was able to execute 
it ... hmmm ... OK ... it seems the partition had been mounted as noexec ...

/dev/sda11 on /data type ext4 (rw,nosuid,nodev,noexec,noatime,data=ordered)
none on /run/user/1000 type tmpfs (rw,relatime,mode=700,uid=1000)

A clear case of mea culpa!

Thanks for helping me spot this.  :-)

-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Problem starting VM image on QEMU

[Alexander Kapshuk]

On Fri, Jul 14, 2017 at 6:31 PM, Mick  wrote:
> I have followed the gentoo wiki to install and setup QEMU:
>
> https://wiki.gentoo.org/wiki/QEMU
>
>
> Then I tried to start up a CoreOS image following this guide, but I must be
> doing something wrong:
>
> https://coreos.com/os/docs/latest/booting-with-qemu.html
>
>
> This is the script's ownership and access rights:
>
> $ stat coreos_production_qemu.sh
>   File: 'coreos_production_qemu.sh'
>   Size: 6635Blocks: 24 IO Block: 4096   regular file
> Device: 80bh/2059d  Inode: 13631491Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ michael)   Gid: ( 1002/ michael)
> Access: 2017-07-14 09:21:18.0 +0100
> Modify: 2017-07-06 19:41:30.0 +0100
> Change: 2017-07-14 14:38:55.104862083 +0100
>  Birth: -
>
> Trying to start it gives:
>
> $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  -- -
> curses
> -bash: ./coreos_production_qemu.sh: Permission denied
>
> Any idea what permissions it refers to?  I have not tried to run the above as
> root.
> --
> Regards,
> Mick

Try running the script in trace mode as yourself:
bash -x coreos_production_qemu.sh etc.

See if that reveals anything useful.

Re: [gentoo-user] Problem starting VM image on QEMU

[R0b0t1]

On Fri, Jul 14, 2017 at 10:54 AM, Mick  wrote:
> On Friday 14 Jul 2017 10:43:23 R0b0t1 wrote:
>> On Fri, Jul 14, 2017 at 10:31 AM, Mick  wrote:
>> > I have followed the gentoo wiki to install and setup QEMU:
>> >
>> > https://wiki.gentoo.org/wiki/QEMU
>> >
>> >
>> > Then I tried to start up a CoreOS image following this guide, but I must
>> > be
>> > doing something wrong:
>> >
>> > https://coreos.com/os/docs/latest/booting-with-qemu.html
>> >
>> >
>> > This is the script's ownership and access rights:
>> >
>> > $ stat coreos_production_qemu.sh
>> >
>> >   File: 'coreos_production_qemu.sh'
>> >   Size: 6635Blocks: 24 IO Block: 4096   regular file
>> >
>> > Device: 80bh/2059d  Inode: 13631491Links: 1
>> > Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ michael)   Gid: ( 1002/ michael)
>> > Access: 2017-07-14 09:21:18.0 +0100
>> > Modify: 2017-07-06 19:41:30.0 +0100
>> > Change: 2017-07-14 14:38:55.104862083 +0100
>> >
>> >  Birth: -
>> >
>> > Trying to start it gives:
>> >
>> > $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  --
>> > -
>> > curses
>> > -bash: ./coreos_production_qemu.sh: Permission denied
>> >
>> > Any idea what permissions it refers to?  I have not tried to run the above
>> > as root.
>>
>> What options are you passing to QEMU? Are you using hardware
>> virtualization? If running it as root solves the problem you need to
>> add yourself to any virtualization groups QEMU or your manager
>> expects, like "kvm."
>>
>> You might also need to chmod +x the script.
>>
>> R0b0t1.
>
> Thanks R0b0t1, I am not passing any options directly to QEMU other than what
> the script does.
>

Okay, you should probably look at the script considering it's not working.

> I'd rather not run it as root, because there is no mention of needing to run
> it as root in the URLs I have listed above.

If I don't know what options are being to passed to QEMU then I can't
help you figure out what you don't have the permission to do.

Re: [gentoo-user] Problem starting VM image on QEMU

[Mick]

On Friday 14 Jul 2017 10:43:23 R0b0t1 wrote:
> On Fri, Jul 14, 2017 at 10:31 AM, Mick  wrote:
> > I have followed the gentoo wiki to install and setup QEMU:
> > 
> > https://wiki.gentoo.org/wiki/QEMU
> > 
> > 
> > Then I tried to start up a CoreOS image following this guide, but I must
> > be
> > doing something wrong:
> > 
> > https://coreos.com/os/docs/latest/booting-with-qemu.html
> > 
> > 
> > This is the script's ownership and access rights:
> > 
> > $ stat coreos_production_qemu.sh
> > 
> >   File: 'coreos_production_qemu.sh'
> >   Size: 6635Blocks: 24 IO Block: 4096   regular file
> > 
> > Device: 80bh/2059d  Inode: 13631491Links: 1
> > Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ michael)   Gid: ( 1002/ michael)
> > Access: 2017-07-14 09:21:18.0 +0100
> > Modify: 2017-07-06 19:41:30.0 +0100
> > Change: 2017-07-14 14:38:55.104862083 +0100
> > 
> >  Birth: -
> > 
> > Trying to start it gives:
> > 
> > $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  --
> > -
> > curses
> > -bash: ./coreos_production_qemu.sh: Permission denied
> > 
> > Any idea what permissions it refers to?  I have not tried to run the above
> > as root.
> 
> What options are you passing to QEMU? Are you using hardware
> virtualization? If running it as root solves the problem you need to
> add yourself to any virtualization groups QEMU or your manager
> expects, like "kvm."
> 
> You might also need to chmod +x the script.
> 
> R0b0t1.

Thanks R0b0t1, I am not passing any options directly to QEMU other than what 
the script does.

The script is already chmod'ed as you can see above.

I have added my user to the kvm group.

I'd rather not run it as root, because there is no mention of needing to run 
it as root in the URLs I have listed above.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Grant Edwards]

On 2017-07-14, Jigme Datse Yli-RAsku  wrote:
>
> On 2017-07-14 08:15, Andrew Tselischev wrote:
>> On Fri, Jul 14, 2017 at 08:42:01PM +0700, Vadim A. Misbakh-Soloviov wrote:
>> >> when time_t reaches 2 billion.
>> >
>> > He meant 2k38 problem, when time_t will overflow int32 :)
>>
>> I would bet that somewhere there is a quick-job shell script that parses
>> unix timestamps with regular expressions and assumes they start with a 1. :D
>>

> Why do I feel that we've already gone through at least one upgrade
> of "Unix Time" already.  I'm not sure if it was something like going
> from int16 to int32, or more that it went from signed int32 to
> unsigned int32.

Well, the return type for time() changed from "int" (or was it long?)
to "time_t" many years back.  That said, the actual underlying
representation has never changed on 32-bit Linux systems.  Posix
requires it to be signed, and on 32-bit Linux systems, it's still
going to overflow in 2038 -- same as it ever was.

NetBSD and OpenBSD both changed to signed-64 on both 32-bit and 64-bit
archetectures.  Maybe that's what you're thinking of?


-- 
Grant Edwards   grant.b.edwardsYow! Here I am in the
  at   POSTERIOR OLFACTORY LOBULE
  gmail.combut I don't see CARL SAGAN
   anywhere!!

Re: [gentoo-user] Problem starting VM image on QEMU

[R0b0t1]

On Fri, Jul 14, 2017 at 10:31 AM, Mick  wrote:
> I have followed the gentoo wiki to install and setup QEMU:
>
> https://wiki.gentoo.org/wiki/QEMU
>
>
> Then I tried to start up a CoreOS image following this guide, but I must be
> doing something wrong:
>
> https://coreos.com/os/docs/latest/booting-with-qemu.html
>
>
> This is the script's ownership and access rights:
>
> $ stat coreos_production_qemu.sh
>   File: 'coreos_production_qemu.sh'
>   Size: 6635Blocks: 24 IO Block: 4096   regular file
> Device: 80bh/2059d  Inode: 13631491Links: 1
> Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ michael)   Gid: ( 1002/ michael)
> Access: 2017-07-14 09:21:18.0 +0100
> Modify: 2017-07-06 19:41:30.0 +0100
> Change: 2017-07-14 14:38:55.104862083 +0100
>  Birth: -
>
> Trying to start it gives:
>
> $ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  -- -
> curses
> -bash: ./coreos_production_qemu.sh: Permission denied
>
> Any idea what permissions it refers to?  I have not tried to run the above as
> root.

What options are you passing to QEMU? Are you using hardware
virtualization? If running it as root solves the problem you need to
add yourself to any virtualization groups QEMU or your manager
expects, like "kvm."

You might also need to chmod +x the script.

R0b0t1.

[gentoo-user] Problem starting VM image on QEMU

[Mick]

I have followed the gentoo wiki to install and setup QEMU:

https://wiki.gentoo.org/wiki/QEMU


Then I tried to start up a CoreOS image following this guide, but I must be 
doing something wrong:

https://coreos.com/os/docs/latest/booting-with-qemu.html


This is the script's ownership and access rights:

$ stat coreos_production_qemu.sh
  File: 'coreos_production_qemu.sh'
  Size: 6635Blocks: 24 IO Block: 4096   regular file
Device: 80bh/2059d  Inode: 13631491Links: 1
Access: (0755/-rwxr-xr-x)  Uid: ( 1000/ michael)   Gid: ( 1002/ michael)
Access: 2017-07-14 09:21:18.0 +0100
Modify: 2017-07-06 19:41:30.0 +0100
Change: 2017-07-14 14:38:55.104862083 +0100
 Birth: -

Trying to start it gives:

$ ./coreos_production_qemu.sh -a /home/michael/.ssh/id_rsa.pub -p  -- -
curses
-bash: ./coreos_production_qemu.sh: Permission denied

Any idea what permissions it refers to?  I have not tried to run the above as 
root.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Jigme Datse Yli-RAsku]

On 2017-07-14 08:15, Andrew Tselischev wrote:
> On Fri, Jul 14, 2017 at 08:42:01PM +0700, Vadim A. Misbakh-Soloviov wrote:
> >> when time_t reaches 2 billion.
> >
> > He meant 2k38 problem, when time_t will overflow int32 :)
>
> I would bet that somewhere there is a quick-job shell script that parses
> unix timestamps with regular expressions and assumes they start with a 1. :D
>
Why do I feel that we've already gone through at least one upgrade of "Unix 
Time" already.  I'm not sure if it was something like going from int16 to 
int32, or more that it went from signed int32 to unsigned int32.

Jigme Datse Yli-Rasku

-- 
Jigme Datse Yli-Rasku
jigme.da...@datsemultimedia.com (Preferred address for new messages)

Jigme Datse Yli-Rasku
PO Box 270
Rossland, BC V0G 1Y0
Canada

...
... This message should be electronically signed, and if the sender ...
... has your public key, may also be encrypted. ...
... If you have any questions about this, please email, or call. ...
...

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Andrew Tselischev]

On Fri, Jul 14, 2017 at 08:42:01PM +0700, Vadim A. Misbakh-Soloviov wrote:
> > when time_t reaches 2 billion.
> 
> He meant 2k38 problem, when time_t will overflow int32 :)

I would bet that somewhere there is a quick-job shell script that parses
unix timestamps with regular expressions and assumes they start with a 1. :D

[gentoo-user] Re: grub error I've never seen in many installs

[Harry Putnam]

Hinnerk van Bruinehsen  writes:

>> Has something changed regarding using that kind of technique?
>> 
>> I can't figure out why grub would be looking for a GRUB drive on
>> /dev/sda1 as the error says:
>> 
>>   grub-install: error: cannot find a GRUB drive for /dev/sda1
>
>
> Did you mount /boot from inside the chroot environment? IIRC I got a
> similar failure when mounting /boot from outside the chroot...

Egad, that is almost certainly what is going on.

However, before seeing your post I came up with what I thought might
be a way to get around the whole problem presented in the errors.

I preserved my install on the initial disk created in vbox for the
install.

Shutdown the vbox vm, created a set of new disks but this time using
whole disks rather than carving up partitions.

So instead of 1 disk carved up... I now had 4 disks in the same sizes
as the original partitions.

Booted the install media.. copied the installed OS over to the new
disks.  But this time I was asking grub to intall itself on a disk
with a single whole disk partition.

It all worked, ... but I think now, after your comment, I probably
mounted boot in the proscribed way this time around.  That is, from
inside a chrooted terminal.

Probably didn't need all the disk switching and copying at all.

Thanks for your input...

I'll know not to think I remember all about how to do this and pay
more attention to the install instructions. Even though I have done
this quite a few times... its usually been separated by along enough
time period that I might will have forgotten some of the necessary
steps.

Thanks again for taking time to post your thoughts.

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Vadim A. Misbakh-Soloviov]

> when time_t reaches 2 billion.

He meant 2k38 problem, when time_t will overflow int32 :)

signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Joerg Schilling]

Matthias Hanft  wrote:

> Neil Bothwick wrote:
> > 
> > That's a relief, I though we were in for another Y2K-like apocalypse.
>
> As far as I know, next apocalypse is scheduled for January 19th, 2038,
> 03:14:08 UTC, isn't it?
>
> At that time, I'll be 73 years old, and I hope I'm not gonna be sysadmin
> any more... :-)

The next apocalypse is:

2033 May 18 03:33:20 GMT

when time_t reaches 2 billion.



Jörg

-- 
 EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin
joerg.schill...@fokus.fraunhofer.de (work) Blog: http://schily.blogspot.com/
 URL: http://cdrecord.org/private/ http://sf.net/projects/schilytools/files/'

[gentoo-user] Intel IPTS

[Bill Kenworthy]

Hi, is anyone using the Intel IPTS touchscreen successfully with a MS
Surface Pro 4?

I am not sure how usable it is with Gentoo:
https://github.com/ipts-linux-org/ipts-linux

BillK

Re: [gentoo-user] Re: Wayland - too early to try?

[Marc Joliet]

Am Freitag, 14. Juli 2017, 00:34:33 CEST schrieb Mick:
> Interestingly, selecting Plasma to run with Wayland won't launch either.  It
> drops me back into the LoginDM screen.

I recall from the announcement of Plasma 5.10 that that is the first version 
for which 
the developers consider Wayland support good enough for *testing*.  AFAIK, it's 
not 
recommended for daily usage yet.

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup



signature.asc
Description: This is a digitally signed message part.

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Matthias Hanft]

Neil Bothwick wrote:
> 
> That's a relief, I though we were in for another Y2K-like apocalypse.

As far as I know, next apocalypse is scheduled for January 19th, 2038,
03:14:08 UTC, isn't it?

At that time, I'll be 73 years old, and I hope I'm not gonna be sysadmin
any more... :-)

-Matt

Re: [gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Neil Bothwick]

On Fri, 14 Jul 2017 05:00:38 +0200, wabe wrote:

> > What a big coincidence. I read this threat about half a minute
> > before   
> 
> Sorry. Of course I meant "thread" and not "threat". ;-)

That's a relief, I though we were in for another Y2K-like apocalypse.


-- 
Neil Bothwick

If at first you don't succeed, redefine success.


pgpYZIVORblzL.pgp
Description: OpenPGP digital signature

Re: [gentoo-user] AMDGPU KMS Problems

[P Levine]

On Fri, Jul 14, 2017 at 12:52 AM, jdm  wrote:
> On Thu, 13 Jul 2017 23:29:39 +0100
> jdm  wrote:
>
>> On Thu, 13 Jul 2017 03:12:49 -0400
>> P Levine  wrote:
>>
>> > On Wed, Jul 12, 2017 at 5:34 PM, jdm  wrote:
>> > > Any thouhgts much appreciated.
>> >
>> > I tried helping to diagnose a similar problem for a user on Reddit
>> > recently, blackscreen/freeze with AMDGPU on boot. After trying
>> > everything else he switched the PCI slot the card was in and it
>> > booted up fine.  He then switched the card back to the original PCI
>> > slot and it still booted up fine.  It seemed to be some weird kind
>> > of hardware/bios hiccup.  If you've tried everything else, it
>> > wouldn't hurt to fumble around with the graphics card just to see
>> > if it makes a difference.
>> >
>>
>> Well, well, well.
>>
>> Bizarre. took out my old radeon r9 280 card and put the RX480 amdgpu
>> back in and rebooted to a kernel which I had configured for amdgpu
>> and booted with no issues, not needing modeset and xorg working fine
>> and dandy.
>>
>> Never seen anything like this before. Bring back the days when you had
>> a primary and secondary hard drives on a serial bus. Far easier when
>> you have to configure your own IRQs.
>>
>> Thanks for the advice.
>>
>> John.
>>
>>
> To prove that reseating the graphics has sorted the issue I have tried
> a few other distros and had no problems.
>
> John
>

Not sure what it is with AMDGPU that makes it so quirky.  Similar problem as
​ ​
https://www.reddit.com/r/Gentoo/comments/6gd4xh/having_kernel_and_xorg_issues_on_new_install_can/dj07pyl/

[gentoo-user] Re: Don't miss the 1 500 000 000 Unix second!

[Nikos Chantziaras]

On 14/07/17 05:40, R0b0t1 wrote:

On Thu, Jul 13, 2017 at 8:01 AM, Andrew Savchenko  wrote:

Hi all!

I'd like to remind you that
   $ date -d @15
is drawing close!

Don't miss the moment :)


Here it is!


I missed it. Damn sleep. I need to quit sleeping, waste of time.