Re: Openbsd VMM with VLAN
Thank you David Gwynne
Irshad
> On 2 Jun 2021, at 3:00 AM, David Gwynne wrote:
>
> Hi Irshad,
>
> Assuming I understand your layout correctly, you should be able to use
> hostname.if configurations files like the following:
>
> $ cat hostname.em0:
> up
>
> $ cat hostname.vlan20
> description "Trusted (L2+L3)"
> vnetid 20 parent em0
> inet aa.bb.cc.dd 255.255.255.0
> up
>
> $ cat hostname.vlan10:
> description "IoT (L2)"
> vnetid 10 parent em0
> up
>
> $ cat hostname.veb10
> description "IoT bridge"
> add vlan10
> add vport10
> up
>
> $ cat hostname.vport10
> description "IoT (L3)"
> inet ee.bb.cc.dd 255.255.255.0
> up
>
> With the above, vlan10 on the wire will be connected using veb10 to the IP
> stack on your firewall on vport10. To have the virtual machine also plug into
> that VLAN 10 Ethernet segment, you can use veb10 as your "uplink" switch
> interface in vmm.conf.
>
> dlg
>
>> On 31 May 2021, at 05:44, Irshad wrote:
>>
>> Hi all
>>
>>
>> i have two Openbsd box Running Like Below one As Firewall and Another one As
>> VMM
>> With two VLAN's
>>
>> OPENBSD_FIREWALL
>>
>> IoT_AP (VLAN10) . -VLAN10
>> |--OpenWRT-em0---| ---pf --em1--Internet
>> ||- VLAN20
>> trusted_AP(VLAN20)
>> this Works fine
>>
>>
>> Another Separate OpenBSD Box for VM
>>
>> openbsd(vmGuest)---vether0---openbsdHost——NAT—em0--OpenBSD_FW--Internet
>>
>> is it possible Add openbsd(vmguest) to VLAN10 network
>>
>>
>> this is MY vm config [HomeAssistance]
>>
>>
>>
>> switch "uplink" {
>> interface bridge1
>> }
>> vm "hass" {
>> disable
>> owner irshad
>> memory 2G
>> disk "/home/irshad/iso/disk.qcow2"
>>
>> interface {
>> switch "uplink"
>> lladdr fe:e1:bb:01:01:01
>> }
>> }
>>
>>
>>
>
Re: Openbsd VMM with VLAN
Hi Irshad,
Assuming I understand your layout correctly, you should be able to use
hostname.if configurations files like the following:
$ cat hostname.em0:
up
$ cat hostname.vlan20
description "Trusted (L2+L3)"
vnetid 20 parent em0
inet aa.bb.cc.dd 255.255.255.0
up
$ cat hostname.vlan10:
description "IoT (L2)"
vnetid 10 parent em0
up
$ cat hostname.veb10
description "IoT bridge"
add vlan10
add vport10
up
$ cat hostname.vport10
description "IoT (L3)"
inet ee.bb.cc.dd 255.255.255.0
up
With the above, vlan10 on the wire will be connected using veb10 to the IP
stack on your firewall on vport10. To have the virtual machine also plug into
that VLAN 10 Ethernet segment, you can use veb10 as your "uplink" switch
interface in vmm.conf.
dlg
> On 31 May 2021, at 05:44, Irshad wrote:
>
> Hi all
>
>
> i have two Openbsd box Running Like Below one As Firewall and Another one As
> VMM
> With two VLAN's
>
>OPENBSD_FIREWALL
>
> IoT_AP (VLAN10) . -VLAN10
>|--OpenWRT-em0---| ---pf --em1--Internet
>||- VLAN20
> trusted_AP(VLAN20)
> this Works fine
>
>
> Another Separate OpenBSD Box for VM
>
> openbsd(vmGuest)---vether0---openbsdHost——NAT—em0--OpenBSD_FW--Internet
>
> is it possible Add openbsd(vmguest) to VLAN10 network
>
>
> this is MY vm config [HomeAssistance]
>
>
>
> switch "uplink" {
>interface bridge1
> }
> vm "hass" {
>disable
>owner irshad
>memory 2G
>disk "/home/irshad/iso/disk.qcow2"
>
>interface {
>switch "uplink"
>lladdr fe:e1:bb:01:01:01
>}
> }
>
>
>
Openbsd VMM with VLAN
Hi all
i have two Openbsd box Running Like Below one As Firewall and Another one As
VMM
With two VLAN's
OPENBSD_FIREWALL
IoT_AP (VLAN10) . -VLAN10
|--OpenWRT-em0---| ---pf --em1--Internet
||- VLAN20
trusted_AP(VLAN20)
this Works fine
Another Separate OpenBSD Box for VM
openbsd(vmGuest)---vether0---openbsdHost——NAT—em0--OpenBSD_FW--Internet
is it possible Add openbsd(vmguest) to VLAN10 network
this is MY vm config [HomeAssistance]
switch "uplink" {
interface bridge1
}
vm "hass" {
disable
owner irshad
memory 2G
disk "/home/irshad/iso/disk.qcow2"
interface {
switch "uplink"
lladdr fe:e1:bb:01:01:01
}
}
Re: OpenBSD vmm
taylormlp writes: > Hello, > Is there plan to add graphics support to vmm/vmd? I'm sure there is. Matthew
OpenBSD vmm
Hello, Is there plan to add graphics support to vmm/vmd?
Re: OpenBSD VMM VMs Crash
On Tue, Apr 10, 2018 at 02:31:15PM +, Olivier Cherrier wrote: > On Sat, Apr 07, 2018 at 11:46:42AM -0700, mlar...@azathoth.net wrote: > > > So i looked up logs and stuff and came to the point that my issues are > > > exactly this ones: > > > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html > > > > > > It seems the issue was not further discussed and/or fixed? > > > > > > Regards, > > > Aaron > > > > > > -- > > > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > > > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > > > GPG: 0x7A65E38D55BE96FE > > > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > > > > > > > You are jumping to conclusions. > > > > All we know is that your VMs failed to run at some point. Whether or not it > > is "exactly the same" as that other post is unknown, since you didn't run > > with > > VMM_DEBUG and give us any more info. Or even submit a proper bug report. > > > > For what it's worth, I'm still working on that other issue. > > For me, the issue never went away. > I would say it is even more frequent now than before (end of 2017). > > > -- > Olivier Cherrier > Phone: +352691754777 > mailto:o...@symacx.com > I have a diff locally that I am testing now that might fix this. Stay tuned. -ml
Re: OpenBSD VMM VMs Crash
On Tue, Apr 10, 2018 at 02:31:15PM +, Olivier Cherrier wrote: > On Sat, Apr 07, 2018 at 11:46:42AM -0700, mlar...@azathoth.net wrote: > > > So i looked up logs and stuff and came to the point that my issues are > > > exactly this ones: > > > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html > > > > > > It seems the issue was not further discussed and/or fixed? > > > > > > Regards, > > > Aaron > > > > > > -- > > > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > > > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > > > GPG: 0x7A65E38D55BE96FE > > > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > > > > > > > You are jumping to conclusions. > > > > All we know is that your VMs failed to run at some point. Whether or not it > > is "exactly the same" as that other post is unknown, since you didn't run > > with > > VMM_DEBUG and give us any more info. Or even submit a proper bug report. > > > > For what it's worth, I'm still working on that other issue. > > For me, the issue never went away. > I would say it is even more frequent now than before (end of 2017). > > > -- > Olivier Cherrier > Phone: +352691754777 > mailto:o...@symacx.com Yep, I dusted off that tree and spent a few hours on it last night. Hopefully have a working diff soon; the EPT misconfigurations are gone but I'm running into a uvm page list accounting error now that results in panics when the VMs are torn down. I know why it's happening but the alternative approach is a bit more messy and I'd hoped to stay away from that. But maybe I'll have no choice. -ml
Re: OpenBSD VMM VMs Crash
On Sat, Apr 07, 2018 at 11:46:42AM -0700, mlar...@azathoth.net wrote: > > So i looked up logs and stuff and came to the point that my issues are > > exactly this ones: > > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html > > > > It seems the issue was not further discussed and/or fixed? > > > > Regards, > > Aaron > > > > -- > > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > > GPG: 0x7A65E38D55BE96FE > > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > > > > You are jumping to conclusions. > > All we know is that your VMs failed to run at some point. Whether or not it > is "exactly the same" as that other post is unknown, since you didn't run > with > VMM_DEBUG and give us any more info. Or even submit a proper bug report. > > For what it's worth, I'm still working on that other issue. For me, the issue never went away. I would say it is even more frequent now than before (end of 2017). -- Olivier Cherrier Phone: +352691754777 mailto:o...@symacx.com
Re: OpenBSD VMM VMs Crash
On Sat, Apr 07, 2018 at 11:46:50AM +0200, Aaron Marcher wrote: > So i looked up logs and stuff and came to the point that my issues are > exactly this ones: > http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html > > It seems the issue was not further discussed and/or fixed? > > Regards, > Aaron > > -- > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > GPG: 0x7A65E38D55BE96FE > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > You are jumping to conclusions. All we know is that your VMs failed to run at some point. Whether or not it is "exactly the same" as that other post is unknown, since you didn't run with VMM_DEBUG and give us any more info. Or even submit a proper bug report. For what it's worth, I'm still working on that other issue. -ml
Re: OpenBSD VMM VMs Crash
So i looked up logs and stuff and came to the point that my issues are exactly this ones: http://openbsd-archive.7691.n7.nabble.com/vmd-VMs-are-stopping-with-vcpu-0-run-ioctl-failed-Invalid-argument-td333259.html It seems the issue was not further discussed and/or fixed? Regards, Aaron -- Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion GPG: 0x7A65E38D55BE96FE Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE
Re: OpenBSD VMM VMs Crash
On Fri, Apr 06, 2018 at 06:55:05PM +0200, Aaron Marcher wrote: > Ohai, > > for me OpenBSD VMM VMs crash after some (undefined) time while logging the > following on the host: > vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument > Apart from that VMM works es expected. > > Regards, > Aaron > > -- > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > GPG: 0x7A65E38D55BE96FE > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > Aaron, This is not a very good bug report. Please provide the following information: * dmesg of host * vm.conf * Guest information (dmesg if OpenBSD) * What is the guest doing when it dies? * What is the host doing when the guest dies? +--+ Carlos
Re: OpenBSD VMM VMs Crash
On Fri, Apr 06, 2018 at 06:55:05PM +0200, Aaron Marcher wrote: > Ohai, > > for me OpenBSD VMM VMs crash after some (undefined) time while logging the > following on the host: > vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument > Apart from that VMM works es expected. > > Regards, > Aaron > > -- > Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ > Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion > GPG: 0x7A65E38D55BE96FE > Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE > could be anything. enable VMM_DEBUG and send me what you see in dmesg after the crash.
OpenBSD VMM VMs Crash
Ohai, for me OpenBSD VMM VMs crash after some (undefined) time while logging the following on the host: vcpu_run_loop: vm 3 / vcpu 0 run ioctl failed: Invalid argument Apart from that VMM works es expected. Regards, Aaron -- Web: https://drkhsh.at/ or http://drkhsh5rv6pnahas.onion/ Gopher: gopher://drkhsh.at or gopher://drkhsh5rv6pnahas.onion GPG: 0x7A65E38D55BE96FE Fingerprint: 4688 907C 8720 3318 0D9F AFDE 7A65 E38D 55BE 96FE
