Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #87944 > unrolled thread
| Started by | rbowman <bowman@montana.com> |
|---|---|
| First post | 2026-06-14 01:07 +0000 |
| Last post | 2026-06-14 22:35 -0400 |
| Articles | 20 on this page of 128 — 10 participants |
Back to article view | Back to comp.os.linux.misc
MX Linux rbowman <bowman@montana.com> - 2026-06-14 01:07 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 00:10 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-14 06:16 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 03:19 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-14 18:11 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 23:00 -0400
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-14 10:33 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-14 18:20 +0000
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-14 19:45 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-14 23:49 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-15 01:41 -0400
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-15 01:34 -0400
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-15 07:23 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-15 07:02 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-15 12:36 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-16 03:39 -0400
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-16 11:52 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-16 22:05 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-17 02:59 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-16 23:55 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-17 07:00 +0000
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-17 08:14 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-18 04:10 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-18 19:26 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-18 03:20 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-18 18:45 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-19 02:50 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-19 16:56 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-20 03:41 -0400
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-20 10:19 +0200
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 01:06 -0400
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-21 12:34 +0200
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 22:41 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-20 17:36 +0000
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-20 20:01 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-21 03:19 +0000
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-21 12:29 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-21 17:34 +0000
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-21 19:49 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-21 23:22 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-22 01:08 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 06:34 +0000
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-22 09:27 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 13:46 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-23 04:32 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-23 17:26 +0000
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-23 18:36 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-23 21:57 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-24 01:34 +0000
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-24 11:51 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-24 18:07 +0000
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-25 12:02 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-25 17:11 +0000
Re: MX Linux "Carlos E. R." <robin_listas@es.invalid> - 2026-06-26 10:52 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-26 17:58 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-26 21:59 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-26 22:04 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-27 09:35 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-28 00:29 -0400
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-27 23:48 -0400
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-26 01:50 -0400
Re: MX Linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-23 07:20 +0000
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-22 09:22 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 23:51 -0400
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-21 17:49 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-22 02:19 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-22 01:13 -0400
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-22 10:20 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-22 05:25 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 13:54 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-22 17:28 +0100
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-22 17:07 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-23 04:23 +0100
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-23 04:49 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-23 05:10 -0400
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-22 00:11 -0400
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-22 17:07 +0000
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 20:36 +0000
Re: MX Linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-23 07:18 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-23 05:03 -0400
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-23 10:27 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-23 17:39 +0000
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-23 17:36 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 22:39 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 03:50 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-22 01:16 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 06:29 +0000
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-22 09:55 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-22 13:50 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 02:34 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-21 06:44 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 03:35 -0400
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-21 17:30 +0000
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-21 23:31 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-21 23:22 -0400
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-22 17:07 +0000
Re: MX Linux John Ames <commodorejohn@gmail.com> - 2026-06-17 15:50 -0700
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-18 04:53 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-16 17:52 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-16 23:19 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-17 07:07 +0000
Re: MX Linux The Natural Philosopher <tnp@invalid.invalid> - 2026-06-17 11:06 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-18 04:02 -0400
Re: MX Linux Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2026-06-18 18:26 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-19 02:37 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-18 19:23 +0000
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-19 04:46 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-19 05:55 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-19 02:56 -0400
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-19 02:59 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-19 17:00 +0000
Re: MX Linux Lawrence D’Oliveiro <ldo@nz.invalid> - 2026-06-15 08:01 +0000
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-15 07:00 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 23:05 -0400
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 22:32 -0400
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-15 07:21 +0100
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-15 02:50 -0400
Re: MX Linux Andy Burns <usenet@andyburns.uk> - 2026-06-15 13:19 +0100
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-15 06:52 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-16 03:37 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-16 17:00 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-16 22:40 -0400
Re: MX Linux Marc Haber <mh+usenetspam2616@zugschl.us> - 2026-06-15 13:09 +0200
Re: MX Linux 🇵🇱Jacek Marcin Jaworski🇵🇱 <jmj@energokod.gda.pl> - 2026-06-14 11:50 +0200
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-14 18:16 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 23:04 -0400
Re: MX Linux rbowman <bowman@montana.com> - 2026-06-15 06:56 +0000
Re: MX Linux c186282 <c186282@nnada.net> - 2026-06-14 22:35 -0400
Page 3 of 7 — ← Prev page 1 2 [3] 4 5 6 7 Next page →
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-22 01:08 -0400 |
| Message-ID | <MZecnVFo0dYQXqX3nZ2dnZfqn_qdnZ2d@giganews.com> |
| In reply to | #88164 |
On 6/21/26 19:22, rbowman wrote: > On Sun, 21 Jun 2026 19:49:32 +0200, Carlos E. R. wrote: > >> virtualization repo has 7.2.10 > > I tried the 7.2.10 rpm from the virtualbox site. Same deal, some user > assembly is required. kvm/QEMU works for what I do so I'm not highly > motivated to put it on the Leap laptop. As KVM is now, it heavily resists what I usually want to do. First up, VMs should easily be on MY local network. This can sort-of work IF all yer boxes are wire-connected ... but these days almost nothing out of central office building IS. Now ALL my boxes are wifi ... KVM does NOT like that one bit. Was able to kind of FAKE it, using a wifi 'extender' and plugging in the cable tap. NOT best. VBox ... check the "Bridged" box and set "promiscuous" mode. KVM was useful on my old office network - but because most everything WAS hard wired ... and that's because I wanted it to be that way.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-22 06:34 +0000 |
| Message-ID | <n9s3b8F9jmdU16@mid.individual.net> |
| In reply to | #88176 |
On Mon, 22 Jun 2026 01:08:25 -0400, c186282 wrote: > As KVM is now, it heavily resists what I usually want to do. First > up, VMs should easily be on MY local network. Connecting to it from the host is good enough for me. I'll admit that a clean, up to date document on creating a bridge for QEMU would be nice. Screwing around with 'sudo ip link ....' makes me nervous. It took a bit to get rid of the bridge on the Fedora box. That part isn't covered.
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2026-06-22 09:27 +0100 |
| Message-ID | <n9s9ubFp458U1@mid.individual.net> |
| In reply to | #88182 |
rbowman wrote: > a clean, up to date document on creating a bridge for QEMU would be > nice. Screwing around with 'sudo ip link ....' makes me nervous. It > took a bit to get rid of the bridge on the Fedora box. What's wrong with bridged networking (for wired ethernet)? Adding a switch is exactly what you'd do in the world of physical networks, a L2 switch is just a multi-port bridge ...
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-22 13:46 +0000 |
| Message-ID | <n9ssm8F9jmdU19@mid.individual.net> |
| In reply to | #88186 |
On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote: > rbowman wrote: > >> a clean, up to date document on creating a bridge for QEMU would be >> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >> took a bit to get rid of the bridge on the Fedora box. > > What's wrong with bridged networking (for wired ethernet)? > > Adding a switch is exactly what you'd do in the world of physical > networks, a L2 switch is just a multi-port bridge ... Nothing would be wrong if it had worked. Perhaps I didn't create the bridge correctly.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-23 04:32 -0400 |
| Message-ID | <Mf6cnYe5w4g_2af3nZ2dnZfqn_udnZ2d@giganews.com> |
| In reply to | #88196 |
On 6/22/26 09:46, rbowman wrote: > On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote: > >> rbowman wrote: >> >>> a clean, up to date document on creating a bridge for QEMU would be >>> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >>> took a bit to get rid of the bridge on the Fedora box. >> >> What's wrong with bridged networking (for wired ethernet)? >> >> Adding a switch is exactly what you'd do in the world of physical >> networks, a L2 switch is just a multi-port bridge ... > > Nothing would be wrong if it had worked. Perhaps I didn't create the > bridge correctly. VBox, it Just Works first time :-)
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-23 17:26 +0000 |
| Message-ID | <n9vttqFbvhkU1@mid.individual.net> |
| In reply to | #88255 |
On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote: > On 6/22/26 09:46, rbowman wrote: >> On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote: >> >>> rbowman wrote: >>> >>>> a clean, up to date document on creating a bridge for QEMU would be >>>> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >>>> took a bit to get rid of the bridge on the Fedora box. >>> >>> What's wrong with bridged networking (for wired ethernet)? >>> >>> Adding a switch is exactly what you'd do in the world of physical >>> networks, a L2 switch is just a multi-port bridge ... >> >> Nothing would be wrong if it had worked. Perhaps I didn't create the >> bridge correctly. > > VBox, it Just Works first time :-) After you find a distro where it will work at all...
[toc] | [prev] | [next] | [standalone]
| From | Charlie Gibbs <cgibbs@kltpzyxm.invalid> |
|---|---|
| Date | 2026-06-23 18:36 +0000 |
| Message-ID | <umA_R.2$3ova.1@fx11.iad> |
| In reply to | #88276 |
On 2026-06-23, rbowman <bowman@montana.com> wrote: > On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote: > >> On 6/22/26 09:46, rbowman wrote: >> >>> On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote: >>> >>>> rbowman wrote: >>>> >>>>> a clean, up to date document on creating a bridge for QEMU would be >>>>> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >>>>> took a bit to get rid of the bridge on the Fedora box. >>>> >>>> What's wrong with bridged networking (for wired ethernet)? >>>> >>>> Adding a switch is exactly what you'd do in the world of physical >>>> networks, a L2 switch is just a multi-port bridge ... >>> >>> Nothing would be wrong if it had worked. Perhaps I didn't create the >>> bridge correctly. >> >> VBox, it Just Works first time :-) > > After you find a distro where it will work at all... I've occasionally had it work on my Debian/VBox setup, but generally it doesn't. I haven't worried much about it because most of the time when I need it there's a handy Ethernet cable I can plug in. -- /~\ Charlie Gibbs | No artificial \ / <cgibbs@kltpzyxm.invalid> | intelligence was X I'm really at ac.dekanfrus | used in the creation / \ if you read it the right way. | of this post.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2026-06-23 21:57 +0100 |
| Message-ID | <111es0m$2hojc$10@dont-email.me> |
| In reply to | #88276 |
On 23/06/2026 18:26, rbowman wrote: > On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote: > >> On 6/22/26 09:46, rbowman wrote: >>> On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote: >>> >>>> rbowman wrote: >>>> >>>>> a clean, up to date document on creating a bridge for QEMU would be >>>>> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >>>>> took a bit to get rid of the bridge on the Fedora box. >>>> >>>> What's wrong with bridged networking (for wired ethernet)? >>>> >>>> Adding a switch is exactly what you'd do in the world of physical >>>> networks, a L2 switch is just a multi-port bridge ... >>> >>> Nothing would be wrong if it had worked. Perhaps I didn't create the >>> bridge correctly. >> >> VBox, it Just Works first time :-) > > After you find a distro where it will work at all... > As usual Linux Mint seems to be OK Although I haven't installed it recently -- “Politics is the art of looking for trouble, finding it everywhere, diagnosing it incorrectly and applying the wrong remedies.” ― Groucho Marx
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-24 01:34 +0000 |
| Message-ID | <na0qgdFg0fjU1@mid.individual.net> |
| In reply to | #88297 |
On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote: > On 23/06/2026 18:26, rbowman wrote: >> On Tue, 23 Jun 2026 04:32:24 -0400, c186282 wrote: >> >>> On 6/22/26 09:46, rbowman wrote: >>>> On Mon, 22 Jun 2026 09:27:22 +0100, Andy Burns wrote: >>>> >>>>> rbowman wrote: >>>>> >>>>>> a clean, up to date document on creating a bridge for QEMU would be >>>>>> nice. Screwing around with 'sudo ip link ....' makes me nervous. It >>>>>> took a bit to get rid of the bridge on the Fedora box. >>>>> >>>>> What's wrong with bridged networking (for wired ethernet)? >>>>> >>>>> Adding a switch is exactly what you'd do in the world of physical >>>>> networks, a L2 switch is just a multi-port bridge ... >>>> >>>> Nothing would be wrong if it had worked. Perhaps I didn't create the >>>> bridge correctly. >>> >>> VBox, it Just Works first time :-) >> >> After you find a distro where it will work at all... >> > As usual Linux Mint seems to be OK > > Although I haven't installed it recently The last time I tried VB would start but would fail with missing dependencies. I just installed virtualbox-7.10.16. It loaded DKMS files, built, and installed two modules. lsmod shows vboxnetsdp, vboxnetflt, vboxdrv. The interesting one when grepping for vbox 'kvm vboxdrv, kvm_intel' shows up. I had the Leap 16 offline iso handy and it is installing at the moment. That will take a while. Interesting that it builds the modules for the 6.17.0.14-generic kernel while it seems to be a DIY process for Leap 16. Among other things the error dialog on Leap 16 says it requires make, gcc, and kernel-devel headers. The Mint box does not have make.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-06-24 11:51 +0200 |
| Message-ID | <na1nksFki3lU1@mid.individual.net> |
| In reply to | #88308 |
On 2026-06-24 03:34, rbowman wrote:
> On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
> Interesting that it builds the modules for the 6.17.0.14-generic kernel
> while it seems to be a DIY process for Leap 16. Among other things the
> error dialog on Leap 16 says it requires make, gcc, and kernel-devel
> headers. The Mint box does not have make.
There is a new iso, announced yesterday.
--
Cheers,
Carlos E.R.
ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-24 18:07 +0000 |
| Message-ID | <na2kmiFop6sU1@mid.individual.net> |
| In reply to | #88336 |
On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote: > On 2026-06-24 03:34, rbowman wrote: >> On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote: > > >> Interesting that it builds the modules for the 6.17.0.14-generic kernel >> while it seems to be a DIY process for Leap 16. Among other things the >> error dialog on Leap 16 says it requires make, gcc, and kernel-devel >> headers. The Mint box does not have make. > > There is a new iso, announced yesterday. I got further with 7.0.16 on Mint but it still wasn't a success. My first attempt was TrixiePup64. The VM started up but was a terminal, not a desktop and reported it had exited from labwc. startlabwc also exited immediately. Next up was the Leap 16 offline iso. The initial screen had 4 options, boot from a DVD, install Leap, safely install Leap or exit. Choosing install brought up the familiar Agama installer. I selected Xfce for variety and started the install. The Mint machine isn't the fastest so that took a while before the screen announced it had been successfully installed and to reboot. Rebooting brought up the initial installation screen, not Leap 16. To make sure the new VB modules hadn't affected kvm_intel I created a TrixiePup64 VM which started up with labwc. So in my experience the RPMFusion version on Fedora 44 is the only one that installs correctly and works. It is 7.2.8, not the 7.0.16 Ubuntu version. fwiw lsmod on Fedora also shows the vbox* modules.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-06-25 12:02 +0200 |
| Message-ID | <na4cmcF2a6tU4@mid.individual.net> |
| In reply to | #88354 |
On 2026-06-24 20:07, rbowman wrote:
> On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote:
>
>> On 2026-06-24 03:34, rbowman wrote:
>>> On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
>>
>>
>>> Interesting that it builds the modules for the 6.17.0.14-generic kernel
>>> while it seems to be a DIY process for Leap 16. Among other things the
>>> error dialog on Leap 16 says it requires make, gcc, and kernel-devel
>>> headers. The Mint box does not have make.
>>
>> There is a new iso, announced yesterday.
>
> I got further with 7.0.16 on Mint but it still wasn't a success. My first
> attempt was TrixiePup64. The VM started up but was a terminal, not a
> desktop and reported it had exited from labwc. startlabwc also exited
> immediately.
>
> Next up was the Leap 16 offline iso. The initial screen had 4 options,
> boot from a DVD, install Leap, safely install Leap or exit. Choosing
> install brought up the familiar Agama installer. I selected Xfce for
> variety and started the install. The Mint machine isn't the fastest so
> that took a while before the screen announced it had been successfully
> installed and to reboot. Rebooting brought up the initial installation
> screen, not Leap 16.
Did you remove the DVD/USB first?
>
> To make sure the new VB modules hadn't affected kvm_intel I created a
> TrixiePup64 VM which started up with labwc.
>
> So in my experience the RPMFusion version on Fedora 44 is the only one
> that installs correctly and works. It is 7.2.8, not the 7.0.16 Ubuntu
> version. fwiw lsmod on Fedora also shows the vbox* modules.
>
>
--
Cheers,
Carlos E.R.
ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-25 17:11 +0000 |
| Message-ID | <na55qmF6l0rU1@mid.individual.net> |
| In reply to | #88396 |
On Thu, 25 Jun 2026 12:02:52 +0200, Carlos E. R. wrote: > 2026-06-24 20:07, rbowman wrote: >> On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote: >> >>> On 2026-06-24 03:34, rbowman wrote: >>>> On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote: >>> >>> >>>> Interesting that it builds the modules for the 6.17.0.14-generic >>>> kernel while it seems to be a DIY process for Leap 16. Among other >>>> things the error dialog on Leap 16 says it requires make, gcc, and >>>> kernel-devel headers. The Mint box does not have make. >>> >>> There is a new iso, announced yesterday. >> >> I got further with 7.0.16 on Mint but it still wasn't a success. My >> first attempt was TrixiePup64. The VM started up but was a terminal, >> not a desktop and reported it had exited from labwc. startlabwc also >> exited immediately. >> >> Next up was the Leap 16 offline iso. The initial screen had 4 options, >> boot from a DVD, install Leap, safely install Leap or exit. Choosing >> install brought up the familiar Agama installer. I selected Xfce for >> variety and started the install. The Mint machine isn't the fastest so >> that took a while before the screen announced it had been successfully >> installed and to reboot. Rebooting brought up the initial installation >> screen, not Leap 16. > > Did you remove the DVD/USB first? That's the fun part. There never was a DVD/USB. The first screen of creating a new VM in VirtualBox asks for an ISO image. That image is in a directory on the host machine. I tried to create a Leap 16 VM on the Fedora box. I got as far as the Agama screen where you select the Leap 16 install. VB was using 100% of the CPU and I ran out of patience waiting for the button to become active. I then tried TrixiePup64. Like on the Mint machine it comes up as a terminal session because labwc won't start. Both work with kvm/QEMU. As I said before if VirtualBox works for someone they should use it. For me it fails to cleanly install on Leap 16, and doesn't work on Fedora or Mint.
[toc] | [prev] | [next] | [standalone]
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Date | 2026-06-26 10:52 +0200 |
| Message-ID | <na6susFejesU2@mid.individual.net> |
| In reply to | #88400 |
On 2026-06-25 19:11, rbowman wrote:
> On Thu, 25 Jun 2026 12:02:52 +0200, Carlos E. R. wrote:
>
>> 2026-06-24 20:07, rbowman wrote:
>>> On Wed, 24 Jun 2026 11:51:24 +0200, Carlos E. R. wrote:
>>>
>>>> On 2026-06-24 03:34, rbowman wrote:
>>>>> On Tue, 23 Jun 2026 21:57:58 +0100, The Natural Philosopher wrote:
>>>>
>>>>
>>>>> Interesting that it builds the modules for the 6.17.0.14-generic
>>>>> kernel while it seems to be a DIY process for Leap 16. Among other
>>>>> things the error dialog on Leap 16 says it requires make, gcc, and
>>>>> kernel-devel headers. The Mint box does not have make.
>>>>
>>>> There is a new iso, announced yesterday.
>>>
>>> I got further with 7.0.16 on Mint but it still wasn't a success. My
>>> first attempt was TrixiePup64. The VM started up but was a terminal,
>>> not a desktop and reported it had exited from labwc. startlabwc also
>>> exited immediately.
>>>
>>> Next up was the Leap 16 offline iso. The initial screen had 4 options,
>>> boot from a DVD, install Leap, safely install Leap or exit. Choosing
>>> install brought up the familiar Agama installer. I selected Xfce for
>>> variety and started the install. The Mint machine isn't the fastest so
>>> that took a while before the screen announced it had been successfully
>>> installed and to reboot. Rebooting brought up the initial installation
>>> screen, not Leap 16.
>>
>> Did you remove the DVD/USB first?
>
> That's the fun part. There never was a DVD/USB. The first screen of
> creating a new VM in VirtualBox asks for an ISO image. That image is in a
> directory on the host machine.
Ok, same thing. You have to disconnect that ISO from VB.
>
> I tried to create a Leap 16 VM on the Fedora box. I got as far as the
> Agama screen where you select the Leap 16 install. VB was using 100% of
> the CPU and I ran out of patience waiting for the button to become active.
> I then tried TrixiePup64. Like on the Mint machine it comes up as a
> terminal session because labwc won't start.
>
> Both work with kvm/QEMU. As I said before if VirtualBox works for someone
> they should use it. For me it fails to cleanly install on Leap 16, and
> doesn't work on Fedora or Mint.
>
--
Cheers,
Carlos E.R.
ES🇪🇸, EU🇪🇺;
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-26 17:58 +0000 |
| Message-ID | <na7sumF6l0rU6@mid.individual.net> |
| In reply to | #88418 |
On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote: > Ok, same thing. You have to disconnect that ISO from VB. However you're supposed to do that. I'm done. I don't need VB.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2026-06-26 21:59 +0100 |
| Message-ID | <111mp7n$qk78$7@dont-email.me> |
| In reply to | #88432 |
On 26/06/2026 18:58, rbowman wrote: > On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote: > >> Ok, same thing. You have to disconnect that ISO from VB. > > However you're supposed to do that. I'm done. I don't need VB. That is sad. It's actually extremely good at what it does I never had any trouble with it -- There is nothing a fleet of dispatchable nuclear power plants cannot do that cannot be done worse and more expensively and with higher carbon emissions and more adverse environmental impact by adding intermittent renewable energy.
[toc] | [prev] | [next] | [standalone]
| From | rbowman <bowman@montana.com> |
|---|---|
| Date | 2026-06-26 22:04 +0000 |
| Message-ID | <na8bbcFn14bU1@mid.individual.net> |
| In reply to | #88438 |
On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote: > On 26/06/2026 18:58, rbowman wrote: >> On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote: >> >>> Ok, same thing. You have to disconnect that ISO from VB. >> >> However you're supposed to do that. I'm done. I don't need VB. > > That is sad. It's actually extremely good at what it does > > I never had any trouble with it You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it installed on various distros, and once installed it is quirky. Apparently it can handle labwc at all. MX starts but never gets past the splash screen. otoh virt-manager works on all distros including Raspberry Pi OS.
[toc] | [prev] | [next] | [standalone]
| From | The Natural Philosopher <tnp@invalid.invalid> |
|---|---|
| Date | 2026-06-27 09:35 +0100 |
| Message-ID | <111o1vs$14qc4$2@dont-email.me> |
| In reply to | #88439 |
On 26/06/2026 23:04, rbowman wrote: > On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote: > >> On 26/06/2026 18:58, rbowman wrote: >>> On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote: >>> >>>> Ok, same thing. You have to disconnect that ISO from VB. >>> >>> However you're supposed to do that. I'm done. I don't need VB. >> >> That is sad. It's actually extremely good at what it does >> >> I never had any trouble with it > > You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it > installed on various distros, and once installed it is quirky. Apparently > it can handle labwc at all. MX starts but never gets past the splash > screen. > Back in the day those options did not exist. QEMU was a way to run windows on a power PC! > otoh virt-manager works on all distros including Raspberry Pi OS. Well, as long as you have what works for you, that's all right -- Climate is what you expect but weather is what you get. Mark Twain
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-28 00:29 -0400 |
| Message-ID | <xbicnevxTLSCPt33nZ2dnZfqnPqdnZ2d@giganews.com> |
| In reply to | #88452 |
On 6/27/26 04:35, The Natural Philosopher wrote: > On 26/06/2026 23:04, rbowman wrote: >> On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote: >> >>> On 26/06/2026 18:58, rbowman wrote: >>>> On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote: >>>> >>>>> Ok, same thing. You have to disconnect that ISO from VB. >>>> >>>> However you're supposed to do that. I'm done. I don't need VB. >>> >>> That is sad. It's actually extremely good at what it does >>> >>> I never had any trouble with it >> >> You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it >> installed on various distros, and once installed it is quirky. Apparently >> it can handle labwc at all. MX starts but never gets past the splash >> screen. >> > Back in the day those options did not exist. QEMU was a way to run > windows on a power PC! > > >> otoh virt-manager works on all distros including Raspberry Pi OS. > > Well, as long as you have what works for you, that's all right The PROBLEM is that what works NOW may not be there for even the near future. Only, crude, 'fix' may be to partition and install an older Linux with yer fav virtual solution that actually WORKS. Very clunky. OR you can pay VMware loads of $$$ .... Recently downloaded VMware 'Workstation' (26h1) which they CLAIM is free to use. NOT sure if they've stuffed it with spyware though. Will install it pretty soon in one of those mini-boxes (Trixie-based MX host) that's just been sitting around burning watts for awhile. Bought a number of those mini-boxes just before the prices went up. One, still with Winders on it, is still in the plastic wrap box. For Linux these are plenty powerful (N-95 to N-100 chips) with enough RAM onboard. Was HOPING to get an n-150 or n-200 version but that's when the trade wars started. Anyway, NOT in biz any more, no corporate credit card to burn, no biz-wide important uses. However being able to test new distros, even run ancient systems, is important to me.
[toc] | [prev] | [next] | [standalone]
| From | c186282 <c186282@nnada.net> |
|---|---|
| Date | 2026-06-27 23:48 -0400 |
| Message-ID | <HvmcnaH8Nf0HBN33nZ2dnZfqnPidnZ2d@giganews.com> |
| In reply to | #88439 |
On 6/26/26 18:04, rbowman wrote: > On Fri, 26 Jun 2026 21:59:35 +0100, The Natural Philosopher wrote: > >> On 26/06/2026 18:58, rbowman wrote: >>> On Fri, 26 Jun 2026 10:52:44 +0200, Carlos E. R. wrote: >>> >>>> Ok, same thing. You have to disconnect that ISO from VB. >>> >>> However you're supposed to do that. I'm done. I don't need VB. >> >> That is sad. It's actually extremely good at what it does >> >> I never had any trouble with it > > You are fortunate. Unlike kvm/QEMU I have had difficulty even getting it > installed on various distros, and once installed it is quirky. Apparently > it can handle labwc at all. MX starts but never gets past the splash > screen. > > otoh virt-manager works on all distros including Raspberry Pi OS. Didn't solve my Leap problems. And SO clunky to deal with ! VBox all in all IS the better solution - but something serious IS wrong at Oracle now and likely explains the fragmented/incomplete versions both there and in the distros. The MX Liberetto disto has a good one, but the quality seems to be getting worse fast. Dunno if an "OpenVirtualbox" is possible now. Oracle ... IF they fix it ... it will probably come back as a For-$$$ version with similar rip-off schemes to VMware and such.
[toc] | [prev] | [next] | [standalone]
Page 3 of 7 — ← Prev page 1 2 [3] 4 5 6 7 Next page →
Back to top | Article view | comp.os.linux.misc
csiph-web