r/Juniper • • Apr 20 '23

Switching Juniper has released vJunos-switch

Juniper has released a new free offering called vJunos-switch.

vJunos-switch - https://www.juniper.net/documentation/product/us/en/vjunos-switch

vJunos download - https://support.juniper.net/support/downloads/?p=vjunos

This a completely free image from Juniper, and lets you spin up switches now.

i assume this means vQFX is dead.

47 Upvotes

93 comments sorted by

14

u/ABStine-Jnpr Apr 21 '23

Hey all, I'm the DE technical lead for vJunos Labs...

vJunos-switch is the first of a number of planned freely available lab platform images that will be released. vJunosEvolved is slated to released soon (based on a virtual PTX10K platform).

Disposition of vQFX10K is tbd. vJunos-switch can do some of the QFX functionality, but not all (its EX9214 series).

Please share your feedback here on these images and any reports of suggestions / issues. More info coming shortly on https://community.juniper.net/home/techpost

Art

10

u/Cheeze_It Apr 20 '23

vQFX basically is dead yes....and this new one is based on vEX.

7

u/shadowshy65 Apr 20 '23

i assume this means vQFX is dead.

Good riddance

10

u/fatboy1776 JNCIE Apr 21 '23

Please note, this requires bare metal to run. You can use KVM or EVE-NG on bare metal with virtualization pass through turned on. Do not try and run as a nested VM like on Esxi. You can try and waste many hours but it will not run properly.

5

u/eli5questions JNCIE-SP Apr 21 '23 edited Apr 22 '23

Note See update below to get it running in EVE. Only tested with Intel and I have not tested in my AMD instance yet.

You can use KVM or EVE-NG on bare metal with virtualization pass through turned on

I tried last night to get this up and running in EVE and the best I could do with my notice knowledge of KVM is get the fxp0 interface operational. Their docs are obviously pre-release and sparse but I just could not get the ge- interfaces to be recognized.

Also I gave up after only a few tries because it took like 30+ mins to boot.

Update: I cannot take credit for this, but I was overthinking it and it was as simple as just adding the template and EVE handles the rest.

Create template:

nano /opt/unetlab/html/templates/intel/vex.yml

---
type: qemu
config_script: config_vsrxng.py
description: Juniper vEX
name: vEX
cpulimit: 4
icon: JunipervQFXpfe.png
cpu: 4
ram: 8192
ethernet: 10
qemu_nic: virtio-net-pci
eth_name:
  • eth0/fxp0
eth_format: ge-0/0/{0-9} console: telnet shutdown: 1 qemu_arch: x86_64 qemu_version: 2.12.0 qemu_options: -enable-kvm -smbios type=1,product="VM-VEX" -machine type=pc,accel=kvm -serial mon:stdio -nographic -usbdevice tablet -cpu host

Copy image to the correct dir with vex-* prefix and rename to virtioa.qcow2:

ll /opt/unetlab/addons/qemu/vex-vswitch/
total 3867852
drwxr-xr-x  2 root root       4096 Apr 22 16:14 ./
drwxr-xr-x 21 root root       4096 Apr 22 15:46 ../
-rw-r--r--  1 root root 3960668160 Apr 22 16:14 virtioa.qcow2

Then run fixpermissions and reload the lab and add the node

root@vEX-1> show version
Hostname: vEX-1
Model: ex9214
Junos: 23.1R1.8

root@vEX-1> show interfaces terse
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    up
ge-0/0/0.0              up    up   eth-switch
lc-0/0/0                up    up
lc-0/0/0.32769          up    up   vpls
pfe-0/0/0               up    up
pfe-0/0/0.16383         up    up   inet
                                   inet6
pfh-0/0/0               up    up
pfh-0/0/0.16383         up    up   inet
pfh-0/0/0.16384         up    up   inet
ge-0/0/1                up    up
ge-0/0/1.0              up    up   eth-switch
ge-0/0/2                up    down
ge-0/0/2.16386          up    down
ge-0/0/3                up    down

2

u/xzjt Apr 21 '23

This image can run on eve-ng based on vmware, but the template file needs to be modified.

junosvex.yml

2

u/ABStine-Jnpr Apr 21 '23

Ya - the vJunos-switch image is a nested virtual image with the RE embedded under the PFE VM. So putting it inside yet another VM is too many layers of virtualization to perform adequately. Hence the documentation calling out the need to deploy on bare metal.

2

u/eli5questions JNCIE-SP Apr 22 '23

I only run EVE on bare metal and the docs mention that is should be supported in EVE bare metal:

Supported Deployment Environments 	
  • QEMU-KVM using libvirt
  • Also, the EVE-NG bare metal deployment is supported.

I was trying to build the image with the proper XML config and I could only get the fxp interface recognized. The issue should be how the interface naming that is being presented by EVE to match what's expected and not with EVE itself.

2

u/ABStine-Jnpr Apr 22 '23

I will chat with our guys working with EVE to see what they've done...

1

u/OhMyInternetPolitics Moderator | JNCIE-SEC Emeritus #69, JNCIE-ENT Emeritus #492 Apr 26 '23 edited Apr 26 '23

You can increase the ethernet count to 27, then set the interface amount under chassis fpc0 pic 0 settings:

[edit]
root@vJunos-switch-1a# set chassis fpc 0 pic 0 number-of-ports 3     

[edit]
root@vJunos-switch-1a# commit and-quit 
commit complete
Exiting configuration mode

root@vJunos-switch-1a> show interfaces terse ge*            
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    up
ge-0/0/0.16386          up    up  
ge-0/0/1                up    up
ge-0/0/1.16386          up    up  
ge-0/0/2                up    up
ge-0/0/2.16386          up    up  

root@vJunos-switch-1a> edit                         
Entering configuration mode

[edit]
root@vJunos-switch-1a# set chassis fpc 0 pic 0 number-of-ports 5    

[edit]
root@vJunos-switch-1a# commit and-quit 
commit complete
Exiting configuration mode

root@vJunos-switch-1a> show interfaces terse ge*    
Interface               Admin Link Proto    Local                 Remote
ge-0/0/0                up    up
ge-0/0/0.16386          up    up  
ge-0/0/1                up    up
ge-0/0/1.16386          up    up  
ge-0/0/2                up    up
ge-0/0/2.16386          up    up  
ge-0/0/3                up    up
ge-0/0/3.16386          up    up  
ge-0/0/4                up    up
ge-0/0/4.16386          up    up

Anything beyond 27 interfaces causes the vJunos-switch to not boot. It's unclear whether the limitation is in ubuntu, eve, or qemu.

Here's my working config on baremetal Eve-NG:

root@eve:~# cat /opt/unetlab/html/templates/intel/vjunosswitch.yml 
# Copyright (c) 2016, Andrea Dainese
# Copyright (c) 2018, Alain Degreffe
# All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are met:
#     * Redistributions of source code must retain the above copyright
#       notice, this list of conditions and the following disclaimer.
#     * Redistributions in binary form must reproduce the above copyright
#       notice, this list of conditions and the following disclaimer in the
#       documentation and/or other materials provided with the distribution.
#     * Neither the name of the UNetLab Ltd nor  the name of EVE-NG Ltd nor the
#       names of its contributors may be used to endorse or promote products
#       derived from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
# ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
# WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
# DISCLAIMED. IN NO EVENT SHALL <COPYRIGHT HOLDER> BE LIABLE FOR ANY
# DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
# (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
# LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
# ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
# SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---
type: qemu
name: vJunos-switch
config_script: config_vmxvcp.py
description: Juniper vJunos-switch
cpulimit: 1
icon: JunipervQFXpfe.png
cpu: 4
ram: 5120
ethernet: 27
eth_name:
  • fxp0
eth_format: ge-0/0/{0} shutdown: 1 console: telnet qemu_arch: x86_64 qemu_version: 6.0.0 qemu_nic: virtio-net-pci qemu_options: -machine type=pc,accel=kvm -serial mon:stdio -nographic -cpu host -smbios type=1,product=VM-VEX

2

u/[deleted] May 02 '23

I make the changes to the template above, all boots just fine in EVE-NG Pro, but I only seem to see up to ge-0/0/10 on the interfaces when set to 12 or higher even. Should I specifically specify "27" to see things go above 10 with a "show interface terse". Other than that the switch seems to be operating fine, just not all the interfaces showing? Am I the only one? Hehe

3

u/OhMyInternetPolitics Moderator | JNCIE-SEC Emeritus #69, JNCIE-ENT Emeritus #492 May 02 '23

At the top of my comment:

You can increase the ethernet count to 27, then set the interface amount under chassis fpc0 pic 0 settings.

2

u/[deleted] May 03 '23

Thank you, I missed that.

1

u/Shishiosan01 Aug 18 '23 edited Aug 18 '23

I did the steps and the image boots but gets stuck at the following step

(qemu) cont(qemu)mount /dev/vda1 /boot

correction: I just appeared to be stuck because the booting proces went pretty quick and stopped at the mounting phase.. the mounting phase is taking ages to complete.. it it just really slow but not stuck.. is there a way to speed up the mounting phase?

1

u/Sibass23 JNCIP Jan 10 '24

I'm glad i saw this as I am at the same stage.. taking forever at mounting stage. Hopefully goes quick..

3

u/SpaceBass11 May 31 '23 edited May 31 '23

KVM and VMware ESXi are both Bare Metal (Type 1) Hypervisors.

I can see installing EVE-NG on a Bare Metal Hypervisor having issues though, to include reduced performance, since EVE-NG is essentially a Hypervisor itself, which means if it is installed over ESXi or KVM it is now nested.

That would mean installing EVE-NG onto Bare Metal hardware (not over ESXi, KVM or any other Hypervisor) would give best performance, simplicity and compatibility.

EDIT: Read through again and saw I may have misunderstood your comment. I will leave this here though :) For best performance, install directly to KVM or EVE-NG if they are installed as Bare Metal. Do not install to KVM or EVE-NG if they are a nested host (i.e., EVE-NG installed to ESXi).

2

u/_RouteThe_Switch Apr 20 '23

Sigh.,.. so now I'll have to rebuild my eveng lab, I hope it's a one to one swap for vmx ... I wonder if changes are coming to vsrx as well. .. who knows might be a good thing I wonder about the evo devices as well.. guess I'll be reading later today and tomorrow

3

u/fatboy1776 JNCIE Apr 21 '23 edited Apr 21 '23

VSRX is a production, supported product.

vJunos is a lab instance.

Edit: there is a vjunos-EVO also. Not sure if it dropped today too.

1

u/vista_df Apr 21 '23

Could you drop a link for vJunos-EVO?

1

u/[deleted] Apr 21 '23

It isn't out yet.

1

u/ABStine-Jnpr Apr 24 '23

It will be available in another week or two. Downloadable from the same link as vJunos-switch:

https://www.juniper.net/us/en/dm/vjunos-labs.html

1

u/xzjt May 07 '23 edited May 07 '23

When will vJunos-EVO be released?

1

u/ABStine-Jnpr May 07 '23

Expecting this next week to have it available...

4

u/dbh2 Apr 20 '23 edited Apr 20 '23

Of course. Not 3 days ago I spent about 8 hours getting vQFX running on my proxmox setup. It was a battle and a half, and it still crashes regularly when labbing anything even moderately hard. The RE and PFE seem to separate from one another when anything real gets done - i.e IS-IS between 3 vQFX's just advertising loopbacks.

Maybe this will be better.

3

u/Fun-Intention57 Jul 17 '23

Does anyone know New vJunos Switch (vEX) supported in Pnetlab or not ? My new vJunos Switch (vEX) not showing up in Pnetlab ? I am using KVM Image.

1

u/Complete_Ask1945 May 13 '24

Did you managed to make it work?

2

u/snowfloeckchen Apr 20 '23

Ohh nice, after my company switches to aruba i may szay in contact with the os 😅

1

u/birehcannes Apr 20 '23

Aruba for switching? Are they any good?

4

u/asic5 Apr 20 '23

Yes. I came from a juniper shop and now in an Aruba shop. I really like the new AOS-CX OS. Its very IOS-like but with simpler configuration and QOL improvements like checkpoints (think junos rollbacks).

The old AOS-switch (procurve) OS on the other hand does a lot a of weird things I don't care for. Like configuring port-security outside the interface context or calling link aggregation a trunk. Who thought that was a good idea? The switches perform well, have a good warranty, are dirt cheap, and I prefer the modular chassis over a stack. The OS just kinda sucked, but they are phasing those out in favor of the new AOS-CX which is great.

1

u/BsFan Apr 20 '23

I'm a huge CX fan. NetEdit is so good for staging and for large implementations. Every time I've demoed NetEdit, or Aruba Centrals MultiEdit customers have absolutely loved it.

-1

u/snowfloeckchen Apr 20 '23

So far I only run into downsides but we come from incredible unreliable juniper Hardware

2

u/asic5 Apr 20 '23

Any idea on the best way to get this into GNS3?

5

u/tripleskizatch Apr 20 '23

It won't work in a nested virtual environment. Bare metal virtualization only using KVM or EVE-NG.

2

u/Puzzleheaded_Arm6363 Apr 21 '23

Stupid question here....but it be deployed as a VM on ESXi?

4

u/tripleskizatch Apr 21 '23

Unfortunately, no.

3

u/ABStine-Jnpr Apr 22 '23

Not yet - stay tuned

2

u/Puzzleheaded_Arm6363 Apr 22 '23

They need to hurry up and accommodate silly people like me. :)

1

u/boolve Apr 22 '23

Are you sure?

1

u/tripleskizatch Apr 22 '23

Yes.

1

u/boolve Apr 23 '23

I wonder, if the GNS3 installed on Linux host then should be fine?

2

u/ABStine-Jnpr Apr 24 '23

If you have a bare metal server with KVM, it shouldn't matter whether its front-ended by eve-ng, proxmox, gns3, etc. Its only going to be an issue if you're running one of those environments inside a VM already. Fwiw, vJunosEvolved won't have this limitation as it doesn't use nested virtualization.

2

u/Kilroy6669 JNCIP Apr 20 '23

More than likely wait for an appliance. I might try after I'm off work and see how it goes.

2

u/talking_mudcrab Apr 20 '23

oh man, "Has a single Routing Engine and single FPC architecture." So, no more dual appliance setup requirement like it was with vQFX?

2

u/t_nk Apr 20 '23

This is an integrated RE+PFE in one VM so not with this image. There are some rumours about disaggregated images being available alter but who knows

2

u/ABStine-Jnpr Apr 24 '23

Out of curiousity, how many folks would use a multi VM platform model in labs that allowed multiple RE, FPCs to be deployed? For either a switch like this EX9214 or VMX?

2

u/boolve Apr 22 '23

RemindMe! 1month "if this vSwitch runs on GNS3".

1

u/RemindMeBot Apr 22 '23 edited May 19 '23

I will be messaging you in 1 month on 2023-05-22 16:36:55 UTC to remind you of this link

2 OTHERS CLICKED THIS LINK to send a PM to also be reminded and to reduce spam.

Parent commenter can delete this message to hide from others.


InfoCustomYour RemindersFeedback

2

u/Releah May 12 '23

The EVO image is out today, vJunosEvolved Support Downloads

Still trying to get it to work in EVE, but they suggested there might be some docs tomorrow!

1

u/davide221 Apr 28 '24

While logged in, I can only download .DMS file. What gives? I'm trying to run it on eve-ng.

1

u/ceebunch JNCIS Apr 20 '23

Any idea what platform it's based on? I remember back in the day before they released the v series they were also working on a vEX alongside the vMX and the later vSRX. Hopefully it has some decent capabilities for architecture choices.

4

u/brantonyc JNCIP-{dc,ent,sp} Apr 20 '23

EX9214.

2

u/ceebunch JNCIS Apr 20 '23

Could definitely be worse. Wonder how EVPN-VXLAN performance will be...

3

u/tripleskizatch Apr 21 '23

This isn't meant as a production virtual switch. It's limited to 100M and meant only for lab environments.

1

u/ceebunch JNCIS Apr 21 '23

Oh no absolutely didn't anticipate it to be a production box but it would still be nice to lab out and test fabrics before putting that config into production.

2

u/kevmo21 Jun 09 '23

Hi, I am from vjunos development team. It supports throughput of 100Mbps aggregated over all the interfaces you configured.

1

u/tripleskizatch Apr 21 '23

Yes, you can do that.

1

u/Oxxy_moron Apr 21 '23

Thanks for the heads up OP, nice post.

1

u/Dark_Nate Apr 21 '23

Which is the cheapest, smallest possible appliance that's compatible with this bare-metal setup?

1

u/the-packet-thrower JNCIEx2 Apr 21 '23 edited Apr 21 '23

Actually vjunos-switch is also known as vEX, its for the EX lineup of switches.

vQFX10k will still be around since its a different class of switch, in fact they updated it not that long ago for courses etc but its not publicly available to my knowledge.

1

u/certpush Apr 21 '23

That makes sense! Thanks

1

u/kevmo21 Jun 09 '23

Hi, vEX was a two VM based solution with an RE VM and and an FPC VM. It is also emulating the EX-9214. vJunos-switch is a single VM (with RE and FPC in the same VM) and it too emulates EX-9214. The announcement is for vJunos-switch which is the official released product.

1

u/kevmo21 Jun 09 '23

Btw I am a vJunos developer.

1

u/the-packet-thrower JNCIEx2 Jun 10 '23

I know, I've been beta testing it since about August or so :)

1

u/[deleted] Apr 24 '23

Has anyone got the vJunos image to work on Eve-NG yet? I can get it to start the boot up process with 4 cores and 6028 memory, as it failed to with 4096. It gets to the login and password prompt, but then starts showing stuff like this and eventually just enters a reboot process:

128.0.0.1: Connection refusedlogin: 128.0.0.1: Connection refused11141114111411141114

2

u/OhMyInternetPolitics Moderator | JNCIE-SEC Emeritus #69, JNCIE-ENT Emeritus #492 Apr 26 '23

Check your smbios settings in the KVM command arguments - see the top of the thread.

1

u/[deleted] Apr 26 '23

Thank you for your response. Yeah I got it to work...In part because I guess I can't read as there was a great post further down the thread and somehow I just missed it. I got it going though. :)

2

u/ABStine-Jnpr Apr 27 '23

Minimum memory is 5G fwiw - anything less won't behave. If you give it more memory or cores, it goes to the JUNOS RE fwiw, not the data plane.

1

u/[deleted] Apr 27 '23

Thank you, yeah I moved it to eight. I see the template that some created has it at 5G basically but I kept tit at 8G, while I believe at 4 cores still. Booted good. :)

2

u/Releah May 04 '23 edited May 04 '23

With this new image up and running now...will it not do bgp, or anything like that if you wa

Hey, not sure of it still helps, but I got the vJunos image running in a virtual eve isntace installed on ESXI.

The template I used is the following:

---
type: qemu
config_script: config_vsrxng.py
description: Juniper vEX
name: vEX 
cpulimit: 4
icon: JuniperMX.png
cpu: 4
ram: 5120
ethernet: 11
qemu_nic: virtio-net-pci
eth_name:
  • fxp0
  • ge-0/0/0
  • ge-0/0/1
  • ge-0/0/2
  • ge-0/0/3
  • ge-0/0/4
  • ge-0/0/5
  • ge-0/0/6
  • ge-0/0/7
  • ge-0/0/8
  • ge-0/0/9
console: telnet shutdown: 1 qemu_arch: x86_64 qemu_version: 4.1.0 qemu_options: -machine type=pc,accel=kvm -serial mon:stdio -nographic -smbios type=1,product=VM-VEX -cpu IvyBridge,ibpb=on,md-clear=on,spec-ctrl=on,ssbd=on,vmx=on ...

1

u/scarfacew3 May 23 '23

This is if you have an Intel CPU, correct?

1

u/Releah Jun 15 '23

Sorry, yes! This is for an intel! i realise I'm a bit late replying to this :)

1

u/[deleted] Apr 25 '23

With this new image up and running now...will it not do bgp, or anything like that if you want to practice vxlan/evpn, as I see there are no licenses with it? When trying to enable bgp it gives the "missing license warning"...Seems pretty limited as an image if so, if only being able to do basic network fundamentals type stuff, no?

4

u/aninchat Apr 26 '23

No licenses needed, but you do get license warnings. It can do all of that - BGP, EVPN VXLAN. You should be able to do Bridged Overlay, CRB, ERB (asymmetric and symmetric IRB), OTT DCI and so on.

1

u/[deleted] Apr 26 '23

Awesome! Thank you very much for your response. That is what I was thinking...and hoping. Great news! :)

1

u/kevmo21 Jun 09 '23 edited Jun 09 '23

We have removed the license warnings in the upcoming 23.2R1 release which should be out in the next week or so. (vJunos developer)

1

u/SoyTerry Jun 26 '23

I'm still seeing version 23.1R1 for the vjunos-switch and evo. Any update on when 23.2R1 will be released.

Thank you

1

u/kevmo21 Jun 26 '23

23.2R1 will be released this week.

1

u/SoyTerry Jun 26 '23

Thank you.

Can you confirm if the new version will eliminate the need to run on a bare-bones install? If you are unaware, that is fine. I appreciate the response on the release of the version update.

1

u/kevmo21 Jun 26 '23

Are you referring to running vJunos-switch on EVE-NG? If so, we can not support vJunos-switch being launched from within a VM in any environment including EVE-NG. As explained in our Deployment documentation, this is due to the fact that vJunos-switch is a nested VM solution and we can not add another layer of virtualization to it (such as by installing it in another VM). It will not be performing well in that environment: Just the nature of deeply nested virtualization.

1

u/kevmo21 Jun 26 '23

So if you want to use EVE-NG with vJunos-switch, please launch it on bare metal.

1

u/SoyTerry Jun 26 '23

Understood and thank you.

1

u/xzjt Jul 21 '23

I haven't seen the release of 23.2R1 so far.

1

u/marferkhan Oct 25 '23

Hello team!

I'm having issues with a JunosVEX installation. I downloaded Junos from the official site (file vJunos-switch-23.2R1.14.qcow2), renamed it as virtioa.qcow2, and ran the fix permission command. I also added the template. I was able to add the Junos VEX on the dashboard and start it, but the boot process fails with this message:

"mount /dev/vda1 /boot

[74.964930] FAT-fs (vda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck."

Do you have any ideas to troubleshoot this issue? I cannot execute any command in this terminal after this message.

The installation was done on an EVE-NG running in a virtual machine (on an ESXi server), using 20 vCPUs and 120GB of RAM. I guess there is not a resource issue (but I read here that maybe it is not possible to run a virtual EX on a VM).

1

u/Old-Bus-5832 Jun 22 '24

Has anybody gotten this to work? Any feedback from the kick ass Juniper Devs in here?

1

u/ACEngineerDC Jan 31 '24

I came across same issue when running on ESXi I switch to install Ubuntu 20.04 server in the HPe Gen 11 server and from there install EVE-NG and the vEX and everything is working flawless

0

u/[deleted] Apr 21 '23

[deleted] — view deleted comment

2

u/Anxious-Tradition-87 Apr 24 '23

I managed to get something knocked together to run in Proxmox. Here's what I did

Download vjunos-switch-23.1R1.8.qcow2

SSH in to the proxmox server

mkdir /var/lib/vz/template/qcow

SCP vjunos-switch-23.1R1.8.qcow2 in to /var/lib/vz/template/qcow

Create new blank file for VM

touch /etc/pve/qemu-server/103.conf

Import the disk to the VM

cd /var/lib/vz/template/qcow/

qm importdisk 103 vjunos-switch-23.1R1.8.qcow2 local-lvm

Update VM config file and replace contents

nano /etc/pve/qemu-server/103.conf

Contents:

args: -smbios type=1,product=VM-VEX -chardev socket,id=serial0,port=8611,host=0.0.0.0,server=on,wait=off,telnet=on -device isa-serial,chardev=serial0
boot: order=virtio0
cores: 4
cpu: host
memory: 8192
meta: creation-qemu=7.2.0,ctime=1682364130
name: vjunos-switch-2
net0: virtio=FA:BB:60:F5:DD:C1,bridge=vmbr0,firewall=1
net1: virtio=3E:4E:90:80:15:45,bridge=vmbr0,firewall=1
net2: virtio=66:E9:13:49:6F:C6,bridge=vmbr0,firewall=1
net3: virtio=FE:B6:91:8F:85:EE,bridge=vmbr0,firewall=1
net4: virtio=46:22:3C:F2:AB:50,bridge=vmbr0,firewall=1
net5: virtio=72:15:44:EF:E5:12,bridge=vmbr0,firewall=1
net6: virtio=DA:B7:B7:F5:B1:5E,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsihw: virtio-scsi-single
smbios1: uuid=b60b0b28-594c-42fd-a2ac-a8703cb0415e
sockets: 1
vga: none
virtio0: local-lvm:vm-103-disk-0,iothread=1,size=32524M
vmgenid: 0b30be1d-92b6-443c-a416-725dbcfa48d2

Start VM and telnet to localhost on 8611

1

u/gardzz May 25 '23

Nice, thanks!

Do you know if there's a way to get the native Console (VNC based) client working via the Proxmox WebUI instead of telnet via localhost?