New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
builder/qemu: packer sends the wrong key code for "<" #5769
Comments
|
Code 60 is the correct keycode for <. Most likely you have a (software) keymap in the VM remapping this key to the > character. |
|
FWIW, with This appears to come from xkeyboard-config: |
|
@rickard-von-essen When I type the "<" manually it works out. So I don't think I have the wrong keymap in the VM. |
|
|
|
The template: https://github.com/archlinux/arch-boxes/blob/master/vagrant.json The keycode in the vnc session is wrong. The packer_log says that the right code is submitted but the VNC session shows another key on that position. How is that even possible? I guess it has something todo with the qemu version: 2.11 |
|
Don't your single quotes (') look like apostrophes (’) too? |
|
@rickard-von-essen mhhh not sure. Maybe the font? I will check this. |
|
@foutrelis do you have the same problem? If so what's you OS version (guest and host) qemu, and packer version? |
|
@shibumi haven't had time to read repro this yet. |
|
Any update on this? |
|
@vtolstov It would be great if you could repro this? |
|
In qemu builder i can't reproduce this issue: packer log: guest os: debian jessie 8.10.0 |
|
Hi @vtolstov , And did you verify the right char? It seems for me you looked only on the packer log. I had the same line when running packer.. Here is my packer configuration: https://github.com/archlinux/arch-boxes/blob/master/vagrant.json Keep in mind that you need to change some variables in vagrant.json |
|
i'm not confirm this issue. fedora 27: |
|
Is it possible that this has something to do with the host system or the locale settings on the host system? On my Laptop (Arch Linux) I get keycode "60" as well for ">":
Here is an additional screenshot of the problem You can see at 20:10:48 the key "<" in packer but on the VNC session you can clearly see a ">". Any way I can override the key code? I have no clue why this behaviour exists only on Arch Linux host systems. Maybe newer software? If so all other distributions will run in the same error in the future. |
|
|
|
i think that you can experiment with qemu keyboard lang for vnc... |
|
@vtolstov Well on VNC it works pretty well. When I press ">" I will get ">" (same for "<"). The problem is packer.. packer seems to send the wrong keycode. I would need a way to override the keycodes for packer. But I guess thats not possible without changing the go code directly. (If everything fails I think I will just patch the code.. do you mind to show me the mapping in your? Then I will just apply the patch for all packer images in arch linux. I maintain packer on arch linux.) |
|
@shibumi sorry for my question, but does you use qemu builder directly or use vagrant/virtualbox? |
|
I'm interesting of part of echo in boot_command ... |
|
This is part of my config when i'm build arch image for our vps hosting |
|
also, please send full qemu cmdline from ps command when you running packer build with you config |
|
@vtolstov Same result as my vagrant.json: You can see the output in the packer log looks ok.. but in the vncviewer you can clearly see again that the result is just: |
|
You use packer binary from release page or build by hand? If by hand - what go version you have? |
|
does it possible to unset x11 layout when running packer? |
|
@vtolstov As VNC client I use gvncviewer, but this really doesn't matter. Because I attach the gvncviewer AFTER i saw the debug lines in the PACKER_LOG output. So it's impossible that any key has been sent to the process. What you see on the screenshot is exactly what packer is producing. As I said.. it seems like the keycode for "<". (When I type "<" normally via VNC in the machine it works btw...) I am pretty sure that the keycode has changed due to some new version of software. (Arch Linux is running new stable releases of every software). Therefore I am pretty sure that you will run in this behaviour with every other distribution in the future. It's just a matter of time.. |
|
I'm try to understand why exactly same packer version sends exactly same keycode that produced on you host different key inside vnc.. Question about viewer - because i need to know what message sends you client when you see right symbol. |
|
@vtolstov I would also like to test some other things (thanks to @bastelfreak for this):
|
|
@vtolstov |
|
@shibumi yes, and this is strange too, because i have 60 for < and 62 for > |
|
@shibumi you can use docker alpine image, i'm build my images from privileged docker container. |
|
any news? |
|
sorry, I haven't time yet. I will probably test it this weekend and can say more. |
|
@vtolstov I have some issues with trying packer on alpine linux. Any idea? |
|
I am running into the same symptoms on macOS 10.12.6. Cannot repro on Ubuntu 17.10. I have qemu from MacPorts on macOS. Here's snippet of my config: As can be seen in the screenshot,
$ env PACKER_LOG=1 ~/bin/packer build openbsd-6.2-x86_64.json
2018/02/27 13:46:39 [INFO] Packer version: 1.2.1
2018/02/27 13:46:39 Packer Target OS/Arch: darwin amd64
2018/02/27 13:46:39 Built with Go Version: go1.10
2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 Using internal plugin for digitalocean
2018/02/27 13:46:39 Using internal plugin for hyperv-iso
2018/02/27 13:46:39 Using internal plugin for vmware-vmx
2018/02/27 13:46:39 Using internal plugin for amazon-instance
2018/02/27 13:46:39 Using internal plugin for virtualbox-ovf
2018/02/27 13:46:39 Using internal plugin for vmware-iso
2018/02/27 13:46:39 Using internal plugin for azure-arm
2018/02/27 13:46:39 Using internal plugin for cloudstack
2018/02/27 13:46:39 Using internal plugin for virtualbox-iso
2018/02/27 13:46:39 Using internal plugin for parallels-pvm
2018/02/27 13:46:39 Using internal plugin for amazon-ebsvolume
2018/02/27 13:46:39 Using internal plugin for googlecompute
2018/02/27 13:46:39 Using internal plugin for oracle-classic
2018/02/27 13:46:39 Using internal plugin for triton
2018/02/27 13:46:39 Using internal plugin for docker
2018/02/27 13:46:39 Using internal plugin for lxd
2018/02/27 13:46:39 Using internal plugin for ncloud
2018/02/27 13:46:39 Using internal plugin for profitbricks
2018/02/27 13:46:39 Using internal plugin for qemu
2018/02/27 13:46:39 Using internal plugin for amazon-chroot
2018/02/27 13:46:39 Using internal plugin for amazon-ebssurrogate
2018/02/27 13:46:39 Using internal plugin for oracle-oci
2018/02/27 13:46:39 Using internal plugin for oneandone
2018/02/27 13:46:39 Using internal plugin for openstack
2018/02/27 13:46:39 Using internal plugin for parallels-iso
2018/02/27 13:46:39 Using internal plugin for scaleway
2018/02/27 13:46:39 Using internal plugin for amazon-ebs
2018/02/27 13:46:39 Using internal plugin for hyperv-vmcx
2018/02/27 13:46:39 Using internal plugin for lxc
2018/02/27 13:46:39 Using internal plugin for alicloud-ecs
2018/02/27 13:46:39 Using internal plugin for file
2018/02/27 13:46:39 Using internal plugin for null
2018/02/27 13:46:39 Using internal plugin for converge
2018/02/27 13:46:39 Using internal plugin for file
2018/02/27 13:46:39 Using internal plugin for powershell
2018/02/27 13:46:39 Using internal plugin for shell
2018/02/27 13:46:39 Using internal plugin for windows-restart
2018/02/27 13:46:39 Using internal plugin for ansible-local
2018/02/27 13:46:39 Using internal plugin for chef-client
2018/02/27 13:46:39 Using internal plugin for puppet-server
2018/02/27 13:46:39 Using internal plugin for windows-shell
2018/02/27 13:46:39 Using internal plugin for ansible
2018/02/27 13:46:39 Using internal plugin for chef-solo
2018/02/27 13:46:39 Using internal plugin for puppet-masterless
2018/02/27 13:46:39 Using internal plugin for salt-masterless
2018/02/27 13:46:39 Using internal plugin for shell-local
2018/02/27 13:46:39 Using internal plugin for artifice
2018/02/27 13:46:39 Using internal plugin for docker-save
2018/02/27 13:46:39 Using internal plugin for docker-push
2018/02/27 13:46:39 Using internal plugin for manifest
2018/02/27 13:46:39 Using internal plugin for shell-local
2018/02/27 13:46:39 Using internal plugin for amazon-import
2018/02/27 13:46:39 Using internal plugin for checksum
2018/02/27 13:46:39 Using internal plugin for compress
2018/02/27 13:46:39 Using internal plugin for docker-tag
2018/02/27 13:46:39 Using internal plugin for vagrant
2018/02/27 13:46:39 Using internal plugin for vagrant-cloud
2018/02/27 13:46:39 Using internal plugin for vsphere-template
2018/02/27 13:46:39 Using internal plugin for alicloud-import
2018/02/27 13:46:39 Using internal plugin for atlas
2018/02/27 13:46:39 Using internal plugin for docker-import
2018/02/27 13:46:39 Using internal plugin for googlecompute-export
2018/02/27 13:46:39 Using internal plugin for vsphere
2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 Attempting to open config file: /Users/REDACTED/.packerconfig
2018/02/27 13:46:39 [WARN] Config file doesn't exist: /Users/REDACTED/.packerconfig
2018/02/27 13:46:39 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[hyperv-iso:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-iso triton:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-triton docker:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-docker alicloud-ecs:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-alicloud-ecs vmware-iso:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-iso hyperv-vmcx:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-hyperv-vmcx virtualbox-iso:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-iso amazon-ebssurrogate:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebssurrogate lxc:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-lxc parallels-pvm:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-pvm oracle-classic:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oracle-classic openstack:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-openstack amazon-ebs:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebs ncloud:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-ncloud amazon-chroot:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-chroot scaleway:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-scaleway vmware-vmx:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-vmware-vmx amazon-instance:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-instance virtualbox-ovf:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-virtualbox-ovf cloudstack:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-cloudstack parallels-iso:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-parallels-iso null:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-null azure-arm:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-azure-arm googlecompute:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-googlecompute lxd:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-lxd oneandone:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oneandone amazon-ebsvolume:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-amazon-ebsvolume profitbricks:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-profitbricks oracle-oci:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-oracle-oci digitalocean:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-digitalocean qemu:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-qemu file:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-builder-file] PostProcessors:map[vagrant:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant shell-local:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-shell-local docker-tag:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-tag googlecompute-export:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-googlecompute-export checksum:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-checksum docker-push:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-push manifest:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-manifest compress:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-compress alicloud-import:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-alicloud-import atlas:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-atlas docker-import:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-import docker-save:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-docker-save amazon-import:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-amazon-import vagrant-cloud:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vagrant-cloud vsphere-template:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere-template vsphere:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-vsphere artifice:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-post-processor-artifice] Provisioners:map[ansible:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible puppet-masterless:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-masterless salt-masterless:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-salt-masterless chef-client:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-client windows-shell:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-shell chef-solo:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-chef-solo shell:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell puppet-server:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-puppet-server converge:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-converge file:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-file powershell:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-powershell windows-restart:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-windows-restart ansible-local:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-ansible-local shell-local:/Users/REDACTED/bin/packer-PACKERSPACE-plugin-PACKERSPACE-packer-provisioner-shell-local]}
2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 Setting cache directory: /Users/REDACTED/repos/packer-configs/packer_cache
2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 Loading builder: qemu
2018/02/27 13:46:39 Plugin could not be found. Checking same directory as executable.
2018/02/27 13:46:39 Current exe path: /Users/REDACTED/bin/packer
2018/02/27 13:46:39 Creating plugin client for path: /Users/REDACTED/bin/packer
2018/02/27 13:46:39 Starting plugin: /Users/REDACTED/bin/packer []string{"/Users/REDACTED/bin/packer", "plugin", "packer-builder-qemu"}
2018/02/27 13:46:39 Waiting for RPC address for: /Users/REDACTED/bin/packer
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 [INFO] Packer version: 1.2.1
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Packer Target OS/Arch: darwin amd64
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Built with Go Version: go1.10
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Attempting to open config file: /Users/REDACTED/.packerconfig
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 [WARN] Config file doesn't exist: /Users/REDACTED/.packerconfig
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]}
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Setting cache directory: /Users/REDACTED/repos/packer-configs/packer_cache
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 args: []string{"packer-builder-qemu"}
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Plugin minimum port: 10000
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Plugin maximum port: 25000
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Plugin address: unix /var/folders/cd/59vmvhd93_g042_b779256jw00bdld/T/packer-plugin090374948
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Waiting for connection...
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Serving a plugin connection...
2018/02/27 13:46:39 Loading provisioner: shell
2018/02/27 13:46:39 Plugin could not be found. Checking same directory as executable.
2018/02/27 13:46:39 Current exe path: /Users/REDACTED/bin/packer
2018/02/27 13:46:39 Creating plugin client for path: /Users/REDACTED/bin/packer
2018/02/27 13:46:39 Starting plugin: /Users/REDACTED/bin/packer []string{"/Users/REDACTED/bin/packer", "plugin", "packer-provisioner-shell"}
2018/02/27 13:46:39 Waiting for RPC address for: /Users/REDACTED/bin/packer
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 [INFO] Packer version: 1.2.1
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Packer Target OS/Arch: darwin amd64
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Built with Go Version: go1.10
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Attempting to open config file: /Users/REDACTED/.packerconfig
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 [WARN] Config file doesn't exist: /Users/REDACTED/.packerconfig
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Packer config: &{DisableCheckpoint:false DisableCheckpointSignature:false PluginMinPort:10000 PluginMaxPort:25000 Builders:map[] PostProcessors:map[] Provisioners:map[]}
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Setting cache directory: /Users/REDACTED/repos/packer-configs/packer_cache
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Detected home directory from env var: /Users/REDACTED
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 args: []string{"packer-provisioner-shell"}
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Plugin minimum port: 10000
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Plugin maximum port: 25000
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Plugin address: unix /var/folders/cd/59vmvhd93_g042_b779256jw00bdld/T/packer-plugin087824806
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Waiting for connection...
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 Serving a plugin connection...
2018/02/27 13:46:39 ui: qemu output will be in this color.
2018/02/27 13:46:39 ui:
2018/02/27 13:46:39 Build debug mode: false
2018/02/27 13:46:39 Force build: false
2018/02/27 13:46:39 On error:
2018/02/27 13:46:39 Preparing build: qemu
qemu output will be in this color.
2018/02/27 13:46:39 packer: 2018/02/27 13:46:39 use detected accelerator: tcg |
|
@aikchar as i see in you case not << and nor >> passed to vnc |
|
@shibumi you need to recheck you iso url means that web server on other side returns witout Accept-Range=bytes or not status code 200 |
|
@vtolstov Now I get the following error: Sorry I am really not a docker guy :S. I guess I have to run the container with all privileges to get kernel KVM_Intel support.. although |
|
This seems to be caused by qemu/qemu@a7815fa and thus reproducible only with QEMU 2.11. Whereas the old The new one contains: Those I filed a bug against QEMU; hopefully they can figure out what went wrong during the keymap updates: |
|
Thanks @foutrelis but it's still weird because @vtolstov said he has tested it on fedora with Qemu 2.11 |
|
@foutrelis thank you so so much for debugging this! |
|
@foutrelis thanks again! :) I should have searched earlier for this bug. |
|
Thanks for the work, all. Going to close this and add a note to the qemu docs |
|
for feature reference https://lists.gnu.org/archive/html/qemu-devel/2018-12/msg04631.html |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |

packer version: 1.1.3
qemu version: 2.11
Host platform: Arch Linux
Hello,
packer sends the wrong keycode for "<". My vagrant.json line looks like this:
With
PACKER_LOG=1I see this line:but in my VNC session in my qemu I see this line:
The text was updated successfully, but these errors were encountered: