summaryrefslogtreecommitdiffstats
path: root/features/domains
Commit message (Collapse)AuthorAgeFilesLines
* Remove support for filesystem shares.anonym2016-11-081-6/+0
| | | | | | | We don't use them any more due to their incompatibility with snapshots, which we rely heavily on. Will-fix: #5571
* Don't ever add a cdrom device with an empty ISO image path.anonym2016-10-191-1/+0
| | | | | | While libvirt can handle it, it does so with a workaround. The correct way to configure a (<driver name='qemu' type='raw'/>) cdrom device to not contain any media is to not have the <source ..> tag at all.
* Plug CDROM only when used by the scenario.bertagaz2016-10-182-6/+6
| | | | | | | | Since QEMU 2.6, VMs can't boot if the CDROM has no ISO file provided in the source field. We have to unplug and plug the whole CDROM device to workaround this. Will-fix: #11874
* Revert "Revert "Test suite: give the system under testing 2 vCPUs.""intrigeri2016-07-311-1/+1
| | | | | | This reverts commit 110557baa6bcee48a02f24cb466ae35ae929f249. refs: #6729
* Test suite: use more recent virtual hardware, i.e. USB 3.0 (nec-xhci) on a ↵intrigeri2016-07-291-7/+4
| | | | | | | | | | | | | | | | | | pc-i440fx-2.5 machine. I have some vague hope that switching USB controllers might help with problems we see on Jenkins when booting from USB (refs: #11588). This change requires upgrading the machine type as well, QEMU otherwise won't boot from this USB 3.0 controller. And while we're at it, let's migrate from IDE to SATA, in order to reflect better hardware Tails is being used with. Also, there are chances that more recent virtual hardware sees more testing these days, so it sounds potentially useful to "upgrade". Note that I've initially tried the more modern pc-q35-2.5 machine type, which worked fine when running the test suite on a sid host, but when running on Jessie the VM under testing crashed when logging into GNOME. I'll file a ticket about trying this again once Stretch is out.
* Revert "Test suite: give the system under testing 2 vCPUs."intrigeri2016-07-211-1/+1
| | | | | | | This reverts commit 8ad96a3558908a1aabd1456e06bf6b06e36ea923. Whenever we go back to that experiment (#6729), we should do it in another branch.
* Test suite: give the system under testing 2 vCPUs.intrigeri2016-01-191-1/+1
| | | | refs: #10971
* Remove silly executable bit.anonym2015-12-071-1/+1
|
* Merge remote-tracking branch 'origin/devel' into feature/jessieanonym2015-10-202-21/+5
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: config/chroot_local-includes/usr/local/bin/tor-browser config/chroot_local-includes/usr/local/sbin/tails-spoof-mac config/chroot_local-includes/usr/local/sbin/tails-unblock-network features/checks.feature features/domains/default.xml features/images/USBCloneAndInstall.png features/images/USBCloneAndUpgrade.png features/images/USBUpgradeFromISO.png features/step_definitions/apt.rb features/step_definitions/checks.rb features/step_definitions/common_steps.rb features/step_definitions/erase_memory.rb features/step_definitions/firewall_leaks.rb features/step_definitions/tor.rb features/step_definitions/usb.rb features/support/helpers/misc_helpers.rb wiki/src/contribute/design.mdwn Notes: * The feature-9672-rework-installer-wording-on-wheezy (of #9572) APT overlay was removed, as was the corresponding automated tests suite images. * We now also use masking of the NetworkManager services in tails-spoof-mac and tails-unblock-network for disabling them.
| * Merge branch 'test/wip-improved-snapshots' into test/6094-improved-snapshotsanonym2015-08-132-22/+5
| |\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: features/domains/default.xml features/evince.feature features/step_definitions/checks.rb features/step_definitions/common_steps.rb features/step_definitions/tor.rb features/step_definitions/unsafe_browser.rb features/step_definitions/usb.rb features/unsafe_browser.feature
| | * Clean up the default domain XML template.anonym2015-05-191-20/+5
| | | | | | | | | | | | Let Libvirt do the work for determining the addresses to be used.
| | * Merge branch 'test/9425-enable-spice-and-asbolute-pointing-device' into ↵anonym2015-05-181-2/+11
| | |\ | | | | | | | | | | | | | | | | | | | | | | | | test/wip-improved-snapshots Conflicts: features/domains/default.xml
| | * | Move domain/network name/uuid to configuration.anonym2015-04-142-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | It's more convenient than parsing it from the XML, and it's one step close to making it possible to run multiple test suites on the same system by making them unique in local.yml.
| | * | Remove unnecessary device.anonym2015-04-141-1/+0
| | | | | | | | | | | | | | | | | | | | It's not used, and I've seen it cause trouble when 2+ USB devices are plugged before booting the domain.
| | * | Use same uuid for domain.anonym2015-04-101-0/+1
| | | |
* | | | Merge remote-tracking branch 'origin/testing' into feature/jessieanonym2015-08-071-2/+2
|\ \ \ \ | |/ / / | | | | | | | | | | | | | | | | | | | | Conflicts: config/base_branch config/chroot_apt/preferences features/totem.feature
| * | | Test suite: bump memory allocated to the system under test to 2 GB.intrigeri2015-08-061-2/+2
| | |/ | |/| | | | | | | Refs: #9883
* | | Test suite: bump video memory allocated to the system under test.intrigeri2015-07-081-1/+1
| | | | | | | | | | | | | | | | | | | | | GNOME Shell crashes on the "old pentium without the PAE extension". Without this change, I see out of video memory errors in the logs. With this change, GNOME Shell still crashes, but at least it's not because of a lack of video memory.
* | | Merge branch 'devel' into feature/jessieintrigeri2015-05-291-2/+10
|\ \ \ | |/ / | | | | | | | | | Conflicts: config/chroot_local-hooks/98-remove_unwanted_files
| * | Blacklist the psmouse kernel module.anonym2015-05-181-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At least when two "relative" pointing devices are present at the same time, like a ps2 mouse and usb mouse, I've seen major breakage caused by host mouse events being used for each such device in virt-viewer, effectively doubling all mouse events inside the guest (i.e. one click => double click, mouse movements are doubled, etc). Hence it feels safer to disable the ps2 mouse and only rely on the ("absolute") tablet device (which has further improvements via Spice). Unfortunately it seems impossible to remove the ps2 mouse since it's part of all QEMU machine templates, including the one we use, presumably with the exception of 'none', which should be an empty machine. However, I've so far not been able to come up with a config that works based on 'none' (generally I get alias errors with the PCI controller). So we also have to blacklist the module. Will-fix: #9425
| * | Enable Spice in the guest.anonym2015-05-181-1/+10
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This seems to help with the issues we have with lost mouse events, in particular in combination with an absolute pointing device, like the 'tablet' we already have. There are some interesting bits about this mentioned in the Spice manual: https://elmarco.fedorapeople.org/manual.html So currently we use mouse mode='client' which "is appropriate for ... a loaded server, since cursor has smooth motion and responsiveness", which we have some data suggestion have been affecting us (see discussion on #8928). However, it also says "the cursor might lose synchronization (position and shape) for a while" but it's not mentioned what may cause this (when there's high load?). It could be interesting to test mouse mode='server' too, just for comparison. Will-fix: #9425
* | Clone the host CPU for the test suite guests (Will-fix: #8778).Tails developers2015-01-231-0/+1
|/
* Use qemu-system-x86_64 directly, instead of kvm, for running the automated ↵Tails developers2014-07-181-1/+1
| | | | | | | | | | test suite (Closes: #7605). This allows libvirt to correctly detect the qemu capabilities, and thus to avoid this error: Call to virDomainCreateWithFlags failed: unsupported configuration: ich9-usb-ehci1 not supported in this QEMU binary (Libvirt::Error)
* Switch from cirrus to QXL graphics device.Tails developers2014-05-071-1/+1
| | | | This works around #7171.
* Bump the tester VM's RAM by 256 MiB.Tails developers2014-04-041-2/+2
| | | | | There is not enough free RAM to run Tails Upgrader with just 1 GiB of RAM after the migration to Wheezy.
* Use IPv6 private address as of RFC 4193 for the test suite virtualTails developers2013-12-241-1/+1
| | | | | | | network. Otherwise dnsmasq from Wheezy complains, as it is not capable of handling public IPv6 addresses.
* Reorganise features/, unifying both test suites.Tails developers2013-03-276-0/+108
Now all .feature:s reside directly in the root of features/, and they are differentiated with tags: source tests are tagged '@source' and product (i.e. Tails ISO image) tests are tagged '@product'. These tags then set up the appropriate environment on a feature-by-feature basis.