Virtual Machine - Revision history

Thp: Mouse cursor in QEMU

2025-10-10T19:47:56Z

Mouse cursor in QEMU

← Older revision		Revision as of 19:47, 10 October 2025
Line 50:		Line 50:
	And then log in like this (password: <code>toor</code>):		And then log in like this (password: <code>toor</code>):
	ssh root@localhost -p 7722		ssh root@localhost -p 7722

			==== Mouse ====

	If the mouse pointer is grabbed and no cursor shows, you can add:		If the mouse pointer is grabbed and no cursor shows, you can add:
	-usb -device usb-tablet		-usb -device usb-tablet
	to the command line. Alternatively if that ~~dose~~ not work you can instead add:
			to the command line. Alternatively if that does not work you can instead add:
	-usb -device usb-mouse -machine vmport=off		-usb -device usb-mouse -machine vmport=off

			Alternatively, see https://git.maemo.org/thp/fakecursor for a user-space solution

			==== Modem ====

	If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:		If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:

Thp: /* Connectivity */ Dummy ICD2 configuration

2025-10-10T08:12:02Z

Connectivity: Dummy ICD2 configuration

← Older revision		Revision as of 08:12, 10 October 2025
Line 105:		Line 105:

	== Connectivity ==		== Connectivity ==

			=== Dummy Network Connection ===

			By default, QEMU provides internet access, but some UI apps like Application Manager won't work until ICD2 says there's a network connection<ref>https://github.com/diejuse/chroot_maemo-leste_on_android?tab=readme-ov-file#6-enabling-hildon-application-manager-installing-dummy-network</ref>:

			<pre>
			sudo apt install libicd-network-dummy
			gconftool-2 -s -t string /system/osso/connectivity/IAP/DUMMY/type DUMMY
			gconftool-2 -s -t string /system/osso/connectivity/IAP/DUMMY/name 'Dummy network'
			gconftool-2 -s -t boolean /system/osso/connectivity/IAP/DUMMY/autoconnect true
			sudo /etc/init.d/icd2 restart
			</pre>

			=== Modem ===

	If you have a modem exposed to QEMU, you still need to do some steps manually to get connectivity.		If you have a modem exposed to QEMU, you still need to do some steps manually to get connectivity.

Sicelo: /* VirtualBox */

2023-07-20T18:54:00Z

VirtualBox

← Older revision		Revision as of 18:54, 20 July 2023
Line 35:		Line 35:
	Create new Virtual Machine, select "Debian (64-bit)" and 1024MB RAM. Use the downloaded file as virtual hard disk.		Create new Virtual Machine, select "Debian (64-bit)" and 1024MB RAM. Use the downloaded file as virtual hard disk.
	You are done!		You are done!

			==== Mouse ====

			Since the UI is meant for touchscreens, it does not show the mouse by default. If it does not appear in the VM, you can change the Pointing Device to "USB Tablet" under "System > Motherboard" settings. Additionally, you may have to disable Virtualbox mouse integration

	=== QEMU ===		=== QEMU ===

Flok: /* virt-manager */

2022-10-15T16:24:37Z

virt-manager

← Older revision		Revision as of 16:24, 15 October 2022
Line 78:		Line 78:
	* In some situations changing from QVA to VGA may be required (see [https://github.com/maemo-leste/bugtracker/issues/291 the previously linked] issue.		* In some situations changing from QVA to VGA may be required (see [https://github.com/maemo-leste/bugtracker/issues/291 the previously linked] issue.
	* Make sure you have a USB (not ps/2) mouse configured		* Make sure you have a USB (not ps/2) mouse configured

			When the screensaver kicks in, press the virt-manager power button to unlock.

	== Initial configuration ==		== Initial configuration ==

Flok at 16:22, 15 October 2022

2022-10-15T16:22:19Z

← Older revision		Revision as of 16:22, 15 October 2022
Line 77:		Line 77:
	* Change the disk driver from VirtIO to sata; there is an [https://github.com/maemo-leste/bugtracker/issues/291 outstanding bug] with how drives are mounted.		* Change the disk driver from VirtIO to sata; there is an [https://github.com/maemo-leste/bugtracker/issues/291 outstanding bug] with how drives are mounted.
	* In some situations changing from QVA to VGA may be required (see [https://github.com/maemo-leste/bugtracker/issues/291 the previously linked] issue.		* In some situations changing from QVA to VGA may be required (see [https://github.com/maemo-leste/bugtracker/issues/291 the previously linked] issue.
			* Make sure you have a USB (not ps/2) mouse configured

	== Initial configuration ==		== Initial configuration ==

	On the first run you may want to generate ssh host keys and set the timezone. To do so open the "X Terminal" application and run:		On the first run you may want to generate ssh host keys and set the timezone. To do so open the "X Terminal" application and run:
	sudo su -		sudo -i
	dpkg-reconfigure openssh-server		dpkg-reconfigure openssh-server
	dpkg-reconfigure tzdata		dpkg-reconfigure tzdata

Meridion: Add warning about screen locking in the VM image.

2021-10-09T21:40:53Z

Add warning about screen locking in the VM image.

← Older revision		Revision as of 21:40, 9 October 2021
Line 94:		Line 94:
	sudo ifconfig eth0 up		sudo ifconfig eth0 up
	sudo dhclient eth0		sudo dhclient eth0

			A fresh Maemo VM image will also lock the device screen by default. In Qemu this means the only way to gain access to the VM again is either via SSH or by sending the power button command. This happens after 30 seconds of no activity on the device. We recommend disabling this behaviour by going to the settings and then open the "display" applet - uncheck "Lock screen automatically".

	== Connectivity ==		== Connectivity ==

Kgoetz: expand on virt manager

2021-01-06T10:26:59Z

expand on virt manager

← Older revision		Revision as of 10:26, 6 January 2021
Line 71:		Line 71:
	=== virt-manager ===		=== virt-manager ===

	~~See~~ [https://github.com/maemo-leste/bugtracker/issues/291~~#issuecomment~~-~~575952497 here~~].		Virt-manager can use multiple virtualisation backends via libvirt and its default is QEMU/KVM, allowing easy importing of the QEMU image.

			The following tweaks need to be done when importing (before starting the instance) to ensure the qemu image works correctly.

			* Change the disk driver from VirtIO to sata; there is an [https://github.com/maemo-leste/bugtracker/issues/291 outstanding bug] with how drives are mounted.
			* In some situations changing from QVA to VGA may be required (see [https://github.com/maemo-leste/bugtracker/issues/291 the previously linked] issue.

	== Initial configuration ==		== Initial configuration ==

Uvos at 13:39, 29 May 2020

2020-05-29T13:39:06Z

← Older revision		Revision as of 13:39, 29 May 2020
Line 38:		Line 38:
	=== QEMU ===		=== QEMU ===

	In general something like		In general something like:
	qemu-system-x86_64 -hda maemo-leste-1.0-amd64.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024		qemu-system-x86_64 -hda maemo-leste-1.0-amd64.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024
	should work. But there seem to be issues with some QEMU versions, for more details see [https://github.com/maemo-leste/bugtracker/issues/198 issue#198].		should work. But there seem to be issues with some QEMU versions, for more details see [https://github.com/maemo-leste/bugtracker/issues/198 issue#198].
Line 47:		Line 47:
	ssh root@localhost -p 7722		ssh root@localhost -p 7722

	If the mouse pointer is grabbed and no cursor shows, you can add		If the mouse pointer is grabbed and no cursor shows, you can add:
	-usb -device usb-tablet		-usb -device usb-tablet
	to the command line		to the command line. Alternatively if that dose not work you can instead add:

	Alternatively if that dose not work you can instead add
	-usb -device usb-mouse -machine vmport=off		-usb -device usb-mouse -machine vmport=off

Uvos at 13:38, 29 May 2020

2020-05-29T13:38:19Z

← Older revision		Revision as of 13:38, 29 May 2020
Line 50:		Line 50:
	-usb -device usb-tablet		-usb -device usb-tablet
	to the command line		to the command line

			Alternatively if that dose not work you can instead add
			-usb -device usb-mouse -machine vmport=off

	If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:		If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:

Uvos at 13:27, 29 May 2020

2020-05-29T13:27:56Z

← Older revision		Revision as of 13:27, 29 May 2020
Line 39:		Line 39:

	In general something like		In general something like
	qemu-system-x86_64 -hda maemo-leste-1.0-amd64.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024 ~~-usb -device usb-mouse -machine vmport=off~~		qemu-system-x86_64 -hda maemo-leste-1.0-amd64.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024
	should work. But there seem to be issues with some QEMU versions, for more details see [https://github.com/maemo-leste/bugtracker/issues/198 issue#198].		should work. But there seem to be issues with some QEMU versions, for more details see [https://github.com/maemo-leste/bugtracker/issues/198 issue#198].

Line 52:		Line 52:

	If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:		If you have a USB modem you can also use that in QEMU. You can either use sudo to elevate your privileges to be able to use it:
	sudo qemu-system-x86_64 -hda maemo-leste-1.0-amd64-virtual-20200324.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024 ~~-usb -device usb-mouse -machine vmport=off~~ \		sudo qemu-system-x86_64 -hda maemo-leste-1.0-amd64-virtual-20200324.qcow2 -enable-kvm -cpu host -smp cores=2 -m 1024 \
	-nic user,hostfwd=tcp:127.0.0.1:7722-:22 \		-nic user,hostfwd=tcp:127.0.0.1:7722-:22 \
	-usb -device usb-ehci,id=ehci \		-usb -device usb-ehci,id=ehci \