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

Groups > linux.debian.user > #233360 > unrolled thread

Running a FreeBSD guest

Back to article view | Back to linux.debian.user

Contents

  Running a FreeBSD guest Victor Sudakov <vas@sibptus.ru> - 2021-03-23 03:30 +0100
    Re: Running a FreeBSD guest Robbi Nespu <robbinespu@gmail.com> - 2021-03-23 05:10 +0100
      Re: Running a FreeBSD guest Victor Sudakov <vas@sibptus.ru> - 2021-03-23 11:00 +0100
        Re: Running a FreeBSD guest didier gaumet <didier.gaumet@gmail.com> - 2021-03-23 11:50 +0100
          Re: Running a FreeBSD guest Victor Sudakov <vas@sibptus.ru> - 2021-03-24 03:20 +0100
            Re: Running a FreeBSD guest didier gaumet <didier.gaumet@gmail.com> - 2021-03-24 10:00 +0100
              Re: Running a FreeBSD guest john doe <johndoe65534@mail.com> - 2021-03-24 10:30 +0100
        Re: Running a FreeBSD guest Dan Ritter <dsr@randomstring.org> - 2021-03-23 11:50 +0100
          Re: Running a FreeBSD guest Victor Sudakov <vas@sibptus.ru> - 2021-03-24 03:30 +0100
            Re: Running a FreeBSD guest Andrei POPESCU <andreimpopescu@gmail.com> - 2021-03-24 10:10 +0100
            Re: Running a FreeBSD guest Dan Ritter <dsr@randomstring.org> - 2021-03-24 12:00 +0100
    Re: Running a FreeBSD guest David Christensen <dpchrist@holgerdanske.com> - 2021-03-23 08:50 +0100
      Re: Running a FreeBSD guest <tomas@tuxteam.de> - 2021-03-23 09:50 +0100
    Re: Running a FreeBSD guest didier gaumet <didier.gaumet@gmail.com> - 2021-03-23 09:40 +0100
      Re: Running a FreeBSD guest Victor Sudakov <vas@sibptus.ru> - 2021-03-23 11:10 +0100
        Re: Running a FreeBSD guest didier gaumet <didier.gaumet@gmail.com> - 2021-03-23 11:30 +0100
          Re: Running a FreeBSD guest Victor Sudakov <vas@sibptus.ru> - 2021-03-23 11:50 +0100
        Re: Running a FreeBSD guest Liam O'Toole <liam.p.otoole@gmail.com> - 2021-03-23 23:00 +0100

#233360 — Running a FreeBSD guest

[Multipart message — attachments visible in raw view] — view raw

Dear Colleagues,

What's the minimum software kit to run a couple of FreeBSD guests
(serial console, no graphics needed) on a Debian 10 host?

I don't need any fancy management GUI like that of VirtualBox, would
just prefer some minimalistic hypervisor managed from the CLI. The
ability to access the host's raw disk devices from the guest would be a
great advantage.

Please don't just say "kvm" or any other single word but give a pointer
to a good step-by-step document.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

[toc] | [next] | [standalone]

#233363

On 3/23/21 10:20 AM, Victor Sudakov wrote:
> Dear Colleagues,
> 
> What's the minimum software kit to run a couple of FreeBSD guests
> (serial console, no graphics needed) on a Debian 10 host?
> 
> I don't need any fancy management GUI like that of VirtualBox, would
> just prefer some minimalistic hypervisor managed from the CLI. The
> ability to access the host's raw disk devices from the guest would be a
> great advantage.
> 
> Please don't just say "kvm" or any other single word but give a pointer
> to a good step-by-step document.
> 

I think qemu is fast and simple,

$ qemu-img create freebsd.img 4G

$ qemu-system-x86_64 -hda freebsd.img -cdrom 
FreeBSD-12.2-RELEASE-amd64-bootonly.iso -boot d -m 512

do the installation and then try boot it with

$ qemu-system-x86_64 -hda freebsd.img -m 512

-- 
Email : Robbi Nespu <robbinespu AT SPAMFREE gmail DOT com>
PGP fingerprint : D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA
PGP key : https://keybase.io/robbinespu/pgp_keys.asc

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

#233371

[Multipart message — attachments visible in raw view] — view raw

Robbi Nespu wrote:
> On 3/23/21 10:20 AM, Victor Sudakov wrote:
> > Dear Colleagues,
> > 
> > What's the minimum software kit to run a couple of FreeBSD guests
> > (serial console, no graphics needed) on a Debian 10 host?
> > 
> > I don't need any fancy management GUI like that of VirtualBox, would
> > just prefer some minimalistic hypervisor managed from the CLI. The
> > ability to access the host's raw disk devices from the guest would be a
> > great advantage.
> > 
> > Please don't just say "kvm" or any other single word but give a pointer
> > to a good step-by-step document.
> > 
> 
> I think qemu is fast and simple,
> 
> $ qemu-img create freebsd.img 4G
> 
> $ qemu-system-x86_64 -hda freebsd.img -cdrom
> FreeBSD-12.2-RELEASE-amd64-bootonly.iso -boot d -m 512
> 
> do the installation and then try boot it with
> 
> $ qemu-system-x86_64 -hda freebsd.img -m 512

Really, a nice thing. Thank you. A couple of questions if you please:

1. Does qemu use hardware virtualization (VT-d, whatever is in the CPU)?

2. Can qemu present the NIC and drives to the guest paravirtualized?
FreeBSD understands VirtIO Block Adapter, VirtIO Ethernet and VMware
VMXNET3 and some other paravirtualized devices.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

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

#233376

Le 23/03/2021 à 10:54, Victor Sudakov a écrit :

> 1. Does qemu use hardware virtualization (VT-d, whatever is in the CPU)?

Yes, I think that basically, KVM requires it (and that Qemu does not)

> 2. Can qemu present the NIC and drives to the guest paravirtualized?
> FreeBSD understands VirtIO Block Adapter, VirtIO Ethernet and VMware
> VMXNET3 and some other paravirtualized devices.

there is an introduction to Virtio in kvm:
https://www.linux-kvm.org/page/Virtio

and you can search for virtio on the qemu-system manpage:
https://helpmanual.io/man1/qemu-system/

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

#233404

[Multipart message — attachments visible in raw view] — view raw

didier gaumet wrote:
> Le 23/03/2021 à 10:54, Victor Sudakov a écrit :
> 
> > 1. Does qemu use hardware virtualization (VT-d, whatever is in the CPU)?
> 
> Yes, I think that basically, KVM requires it (and that Qemu does not)

The relation between qemu and kvm confuses me. "apt install qemu-kvm" is
trying to install a ton of X11 packages including Mesa drivers etc, I
would not really want that. And "apt install kvm" does not find such a
package.

> 
> > 2. Can qemu present the NIC and drives to the guest paravirtualized?
> > FreeBSD understands VirtIO Block Adapter, VirtIO Ethernet and VMware
> > VMXNET3 and some other paravirtualized devices.
> 
> there is an introduction to Virtio in kvm:
> https://www.linux-kvm.org/page/Virtio

This is also confusing, as the document is written about kvm but cites
qemu as an example.

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

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

#233410

Le 24/03/2021 à 03:12, Victor Sudakov a écrit :

> The relation between qemu and kvm confuses me. "apt install qemu-kvm" is
> trying to install a ton of X11 packages including Mesa drivers etc, I
> would not really want that. And "apt install kvm" does not find such a
> package.

QEMU/KVM relationship:

as I see it (but someone with a real understanding of the subject -that 
I do not have- could be horrified by what I say):
- KVM is roughly a Linux(-only) kernel module that permits the use the 
Linux Kernel as the basis of an hypervisor and the access to hardware 
acceleration. But it is not by itself a whole virtualization solution
- QEMU is a multi-platform virtualization solution that does not require 
hardware acceleration and does not by itseelf provide a way to use this 
acceleration. In the past many accelerators had been available
- today a common way to virtualize a guest in a linux host is to use 
Qemu with the KVM kernel module (and invoking KVM is really invoking Qemu)

more (and more pertinent) info here:
  https://en.wikipedia.org/wiki/QEMU
  https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine

QEMU/X11 relationship:
- I do not really know how to install Qemu without X11 nor if it 
possible without the loss of CLI features. Possible solutions could be 
to install packages with the "without recommended" option, to forbid 
installation of packages by establishing preferences (cf apt_preferences 
manpage). A possible culprit is qemu-system-gui and you could forbid its 
installation. I do not know if running Qemu immplies that a X11 server 
is running or simply installed
- the Qemu package in Debian is an all-architectures one: if you want to 
emulate/virtualize only X86/X86_64 hardware, qemu-systemx-86 is sufficient
- if you do not want to install X11 and can not avoid it with Qemu, 
perhaps you could look at Xen. I do not know if it could be of interest 
in your case. My opinion (but I am not knowledgeable on this) is that 
Xen is perhaps more modular than Qemu but with an added (to me at least) 
complexity. Another element: I seem to recall that Xen is welle 
used/known is the NetBSD world and that could translate in your FreeBSD 
approach?

>> https://www.linux-kvm.org/page/Virtio
> 
> This is also confusing, as the document is written about kvm but cites
> qemu as an example.

see above :-)

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

#233412

On 3/24/2021 9:55 AM, didier gaumet wrote:
> Le 24/03/2021 à 03:12, Victor Sudakov a écrit :
>
>> The relation between qemu and kvm confuses me. "apt install qemu-kvm" is
>> trying to install a ton of X11 packages including Mesa drivers etc, I
>> would not really want that. And "apt install kvm" does not find such a
>> package.
>
> QEMU/KVM relationship:
>
> as I see it (but someone with a real understanding of the subject -that
> I do not have- could be horrified by what I say):
> - KVM is roughly a Linux(-only) kernel module that permits the use the
> Linux Kernel as the basis of an hypervisor and the access to hardware
> acceleration. But it is not by itself a whole virtualization solution
> - QEMU is a multi-platform virtualization solution that does not require
> hardware acceleration and does not by itseelf provide a way to use this
> acceleration. In the past many accelerators had been available
> - today a common way to virtualize a guest in a linux host is to use
> Qemu with the KVM kernel module (and invoking KVM is really invoking Qemu)
>
> more (and more pertinent) info here:
>   https://en.wikipedia.org/wiki/QEMU
>   https://en.wikipedia.org/wiki/Kernel-based_Virtual_Machine
>
> QEMU/X11 relationship:
> - I do not really know how to install Qemu without X11 nor if it
> possible without the loss of CLI features. Possible solutions could be
> to install packages with the "without recommended" option, to forbid
> installation of packages by establishing preferences (cf apt_preferences
> manpage). A possible culprit is qemu-system-gui and you could forbid its
> installation. I do not know if running Qemu immplies that a X11 server

The Debian's wiki (1) suggest one way to install qemu-kvm with Libvirt
for a server.
Note that if you go this way, you might require some pkgs along the way.


1)  https://wiki.debian.org/KVM#Installation

--
John Doe

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

#233377

Victor Sudakov wrote: 
> Robbi Nespu wrote:
> > On 3/23/21 10:20 AM, Victor Sudakov wrote:
> > > Dear Colleagues,
> > > 
> > > What's the minimum software kit to run a couple of FreeBSD guests
> > > (serial console, no graphics needed) on a Debian 10 host?
> > > 
> > > I don't need any fancy management GUI like that of VirtualBox, would
> > > just prefer some minimalistic hypervisor managed from the CLI. The
> > > ability to access the host's raw disk devices from the guest would be a
> > > great advantage.
> > > 
> > > Please don't just say "kvm" or any other single word but give a pointer
> > > to a good step-by-step document.
> > > 
> > 
> > I think qemu is fast and simple,
> > 
> > $ qemu-img create freebsd.img 4G
> > 
> > $ qemu-system-x86_64 -hda freebsd.img -cdrom
> > FreeBSD-12.2-RELEASE-amd64-bootonly.iso -boot d -m 512
> > 
> > do the installation and then try boot it with
> > 
> > $ qemu-system-x86_64 -hda freebsd.img -m 512
> 
> Really, a nice thing. Thank you. A couple of questions if you please:
> 
> 1. Does qemu use hardware virtualization (VT-d, whatever is in the CPU)?

If qemu-kvm is installed, yes, that will be the default. qemu
will fall back to emulation if a non-x86 guest is requested or
the CPU of the host is incapable.


> 2. Can qemu present the NIC and drives to the guest paravirtualized?
> FreeBSD understands VirtIO Block Adapter, VirtIO Ethernet and VMware
> VMXNET3 and some other paravirtualized devices.

Yes.

Most other tools for virtualization on Linux are built on top of
qemu/kvm, largely to expose features that qemu already has but
can required very long command lines, or to do management of
multiple VMs. The libvirtd infrastructure is probably the
simplest such management system. Although there is an X11 GUI
included with it, the command line tools can do everything.

Here's a typical non-libvirtd qemu/kvm invocation:

cd /var/spool/kvm
export VNAME=virtualmachinename
export CPUS=2
export RAM=4096
export MAC=00:15:f1:c1:a2:01
export VNC=:1
export IMAGE=/var/spool/kvm/images/$VNAME.img

kvm -m $RAM -smp $CPUS -name $VNAME -rtc base=utc -boot menu=on -drive file=$IMAGE,if=none,id=drive-virtio-disk0,boot=on,cache=writeback -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -device virtio-net-pci,vlan=0,id=net0,mac=$MAC,bus=pci.0,addr=0x3 -net
tap -usbdevice tablet -vnc $VNC &


libvirtd tooling is more comprehensive, but in the end gets
invoked with

virsh start virtualmachinename

-dsr-

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

#233405

[Multipart message — attachments visible in raw view] — view raw

Dan Ritter wrote:
> > > > 
> > > > What's the minimum software kit to run a couple of FreeBSD guests
> > > > (serial console, no graphics needed) on a Debian 10 host?
> > > > 
> > > > I don't need any fancy management GUI like that of VirtualBox, would
> > > > just prefer some minimalistic hypervisor managed from the CLI. The
> > > > ability to access the host's raw disk devices from the guest would be a
> > > > great advantage.
> > > > 
> > > > Please don't just say "kvm" or any other single word but give a pointer
> > > > to a good step-by-step document.
> > > > 
> > > 
> > > I think qemu is fast and simple,
> > > 
> > > $ qemu-img create freebsd.img 4G
> > > 
> > > $ qemu-system-x86_64 -hda freebsd.img -cdrom
> > > FreeBSD-12.2-RELEASE-amd64-bootonly.iso -boot d -m 512
> > > 
> > > do the installation and then try boot it with
> > > 
> > > $ qemu-system-x86_64 -hda freebsd.img -m 512
> > 
> > Really, a nice thing. Thank you. A couple of questions if you please:
> > 
> > 1. Does qemu use hardware virtualization (VT-d, whatever is in the CPU)?
> 
> If qemu-kvm is installed, yes, that will be the default. qemu
> will fall back to emulation if a non-x86 guest is requested or
> the CPU of the host is incapable.

Do you think I can install qemu-kvm without installing the 230 X11
packages is requires?

> 
> 
> > 2. Can qemu present the NIC and drives to the guest paravirtualized?
> > FreeBSD understands VirtIO Block Adapter, VirtIO Ethernet and VMware
> > VMXNET3 and some other paravirtualized devices.
> 
> Yes.

That's great.

> 
> Most other tools for virtualization on Linux are built on top of
> qemu/kvm, largely to expose features that qemu already has but
> can required very long command lines, or to do management of
> multiple VMs. The libvirtd infrastructure is probably the
> simplest such management system. Although there is an X11 GUI
> included with it, the command line tools can do everything.
> 
> Here's a typical non-libvirtd qemu/kvm invocation:
> 
> cd /var/spool/kvm
> export VNAME=virtualmachinename
> export CPUS=2
> export RAM=4096
> export MAC=00:15:f1:c1:a2:01
> export VNC=:1
> export IMAGE=/var/spool/kvm/images/$VNAME.img
> 
> kvm -m $RAM -smp $CPUS -name $VNAME -rtc base=utc -boot menu=on -drive file=$IMAGE,if=none,id=drive-virtio-disk0,boot=on,cache=writeback -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -device virtio-net-pci,vlan=0,id=net0,mac=$MAC,bus=pci.0,addr=0x3 -net
> tap -usbdevice tablet -vnc $VNC &

The "kvm" run in the line above is just a wrapper script that runs "qemu -enable-kvm", isn't it?


-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

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

#233411

[Multipart message — attachments visible in raw view] — view raw

On Mi, 24 mar 21, 09:22:32, Victor Sudakov wrote:
> 
> Do you think I can install qemu-kvm without installing the 230 X11
> packages is requires?

It is possible.

It should be relatively easy to do so if some packages are only 
recommended instead of depended on.

Does 'apt install --no-install-recommends' want to install significantly 
less packages?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser

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

#233416

Victor Sudakov wrote: 
> Dan Ritter wrote:
> > Here's a typical non-libvirtd qemu/kvm invocation:
> > 
> > cd /var/spool/kvm
> > export VNAME=virtualmachinename
> > export CPUS=2
> > export RAM=4096
> > export MAC=00:15:f1:c1:a2:01
> > export VNC=:1
> > export IMAGE=/var/spool/kvm/images/$VNAME.img
> > 
> > kvm -m $RAM -smp $CPUS -name $VNAME -rtc base=utc -boot menu=on -drive file=$IMAGE,if=none,id=drive-virtio-disk0,boot=on,cache=writeback -device virtio-blk-pci,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0 -device virtio-net-pci,vlan=0,id=net0,mac=$MAC,bus=pci.0,addr=0x3 -net
> > tap -usbdevice tablet -vnc $VNC &
> 
> The "kvm" run in the line above is just a wrapper script that runs "qemu -enable-kvm", isn't it?

$ cat /usr/bin/kvm
#! /bin/sh
exec qemu-system-x86_64 -enable-kvm "$@"

-dsr-

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

#233365

On 3/22/21 7:20 PM, Victor Sudakov wrote:
> Dear Colleagues,
> 
> What's the minimum software kit to run a couple of FreeBSD guests
> (serial console, no graphics needed) on a Debian 10 host?
> 
> I don't need any fancy management GUI like that of VirtualBox, would
> just prefer some minimalistic hypervisor managed from the CLI. The
> ability to access the host's raw disk devices from the guest would be a
> great advantage.
> 
> Please don't just say "kvm" or any other single word but give a pointer
> to a good step-by-step document.


I have been using VirtualBox on Debian for the past several years.  My 
Debian 9 graphical workstation has VirtualBox 6.1 and is currently 
running a FreeBSD 12.2-RELEASE-p4 guest for development.  It just works.


VirtualBox is a very professional product -- reliable, performant, well 
designed GUI and CLI, good documentation, etc..  Installation 
instructions are here:

 
https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/install-linux-host.html


I like that VirtualBox runs on the most common platforms -- Windows, 
macOS, Linux, and Solaris.  I  want this feature, in case I need to move 
a guest between platforms:

 
https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/hostossupport.html


I typically use the GUI, but there is a CLI that can do everything the 
GUI can do and more.  Or, you can install the headless version if you do 
not need or use graphics.


I have shared host directories with guests in the past:

 
https://docs.oracle.com/en/virtualization/virtualbox/6.0/user/sharedfolders.html


VirtualBox can also share raw drives:

 
https://docs.oracle.com/en/virtualization/virtualbox/6.0/admin/adv-storage-config.html


STFW "linux kvm vs. virtualbox 2021", this article made some interesting 
points:

 
https://linuxconfig.org/virtualization-solutions-on-linux-systems-kvm-and-virtualbox#h3-kvm-or-virtualbox


David

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

#233369

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 23, 2021 at 12:42:17AM -0700, David Christensen wrote:
> On 3/22/21 7:20 PM, Victor Sudakov wrote:
> >Dear Colleagues,
> >
> >What's the minimum software kit to run a couple of FreeBSD guests
> >(serial console, no graphics needed) on a Debian 10 host?
> >
> >I don't need any fancy management GUI like that of VirtualBox, would

[...]
                                              
> I have been using VirtualBox on Debian for the past several years.

Heh. Exactly what the OP *didn't* ask for :-)
[...]

> VirtualBox is a very professional product -- reliable, performant,

Thanks for the ad.

Note that VirtualBox is (in part) not free [1]. Some base "core"
is free, the "extension pack" (including usb > 1.1 support) isn't.

Cheers

[1] https://www.virtualbox.org/wiki/VirtualBox_PUEL

 - t

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

#233368

Le 23/03/2021 à 03:20, Victor Sudakov a écrit :
> Dear Colleagues,
> 
> What's the minimum software kit to run a couple of FreeBSD guests
> (serial console, no graphics needed) on a Debian 10 host?
> 
> I don't need any fancy management GUI like that of VirtualBox, would
> just prefer some minimalistic hypervisor managed from the CLI. The
> ability to access the host's raw disk devices from the guest would be a
> great advantage.

- if your last sentance is correctly enounced, I do not understand your 
usecase nor did I know that it is possible
- if the matter is for a Linux host to access the raw filesystem of a 
FreeBSD guest, you probably need:
a) to choose a virtualization that proposes this raw option (for 
KVM/qemu I know that it is possible, for Virtualbox, I think so, too, 
and I do not know for the others)
b) to use ZFS instead of UFS in FreeBSD (UFS read acces in Linux is not 
very convenient and for write access you need (needed?) to rebuild the 
kernel and it is (was?) rather dangerous). I have never used ZFS, so 
take this with a grain of salt.

> Please don't just say "kvm" or any other single word but give a pointer
> to a good step-by-step document.

This one will probably do:
  https://wiki.debian.org/SystemVirtualization
(particularly the 3rd chapter "System Virtualization" if I understand 
your usecase)

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

#233372

[Multipart message — attachments visible in raw view] — view raw

didier gaumet wrote:
> > 
> > What's the minimum software kit to run a couple of FreeBSD guests
> > (serial console, no graphics needed) on a Debian 10 host?
> > 
> > I don't need any fancy management GUI like that of VirtualBox, would
> > just prefer some minimalistic hypervisor managed from the CLI. The
> > ability to access the host's raw disk devices from the guest would be a
> > great advantage.
> 
> - if your last sentance is correctly enounced, I do not understand your
> usecase 

My usecase would be, among other things, to access external media
attached to the host from inside the guest, e.g. those partitioned and
encrypted in FreeBSD-specific ways (geli encryption, gbde etc).

> nor did I know that it is possible

It is quite possible in bhyve (FreeBSD's hypervisor). You just tell the
hypervisor that this guest's disk is not a file but a device in /dev/.

> 
> > Please don't just say "kvm" or any other single word but give a pointer
> > to a good step-by-step document.
> 
> This one will probably do:
>  https://wiki.debian.org/SystemVirtualization
> (particularly the 3rd chapter "System Virtualization" if I understand your
> usecase)

This is a comprehensive document. In your opinion, what's the best,
simplest and most convenient CLI management tool around kvm?

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

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

#233374

Le 23/03/2021 à 11:06, Victor Sudakov a écrit :

> My usecase would be, among other things, to access external media
> attached to the host from inside the guest, e.g. those partitioned and
> encrypted in FreeBSD-specific ways (geli encryption, gbde etc).

this link, albeit a little old should be of interest, concerning this 
scenario managed by kvm:
  https://www.linux-kvm.org/page/USB_Host_Device_Assigned_to_Guest

[...]
> In your opinion, what's the best,
> simplest and most convenient CLI management tool around kvm?

Sorry, I use VirtManager (GUI) so I do not know but the kvm website has 
a list of management tools:
  https://www.linux-kvm.org/page/Management_Tools

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

#233375

[Multipart message — attachments visible in raw view] — view raw

didier gaumet wrote:
> Le 23/03/2021 à 11:06, Victor Sudakov a écrit :
> 
> > My usecase would be, among other things, to access external media
> > attached to the host from inside the guest, e.g. those partitioned and
> > encrypted in FreeBSD-specific ways (geli encryption, gbde etc).
> 
> this link, albeit a little old should be of interest, concerning this
> scenario managed by kvm:
>  https://www.linux-kvm.org/page/USB_Host_Device_Assigned_to_Guest

Not as hardcore as USB passthrough, but
qemu -drive file=/dev/sdb 
should do the trick if I understand correctly.

> 
> [...]
> > In your opinion, what's the best,
> > simplest and most convenient CLI management tool around kvm?
> 
> Sorry, I use VirtManager (GUI) so I do not know but the kvm website has a
> list of management tools:
>  https://www.linux-kvm.org/page/Management_Tools
> 
> 

Thank you!

-- 
Victor Sudakov VAS4-RIPE
http://vas.tomsk.ru/
2:5005/49@fidonet

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

#233402

On Tue, 23 Mar, 2021 at 17:06:47 +0700, Victor Sudakov wrote:
> didier gaumet wrote:

[...]

> > This one will probably do:
> >  https://wiki.debian.org/SystemVirtualization
> > (particularly the 3rd chapter "System Virtualization" if I understand your
> > usecase)
> 
> This is a comprehensive document. In your opinion, what's the best,
> simplest and most convenient CLI management tool around kvm?

I recommend libvirt, in particular the Debian package libvirt-clients.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web