qvm-run: improve consitency between HVM and AppVMs

[marmarek]

Reported by joanna on 5 Dec 2012 22:09 UTC
Currently the output generated by qvm-run (specifically with he '-p' switch) when used with HVM domains is not consistent with what it outputs when run for standard AppVMs. There is lots of (useless) stderr messages being output before the actual output from the HVM domain is provided, which is not the case for standard AppVMs. Would be nice to filter this out. The same applies to the annoying "...killed." output, this time present only in case of AppVMs.

Also, the --nogui switch, when used with an HVM domain, doesn't prevent GUI window from being opened for the VM.

Migrated-From: https://wiki.qubes-os.org/ticket/683

[marmarek]

Comment by marmarek on 6 Dec 2012 03:28 UTC
You meant qvm-start, right (or qvm-run -a)? As discussed in emails, this requires patch for libxl/libxc...

The qvm-run --nogui switch means "application will have no access to GUI", which is useful for launching background tasks like Qubes RPC services. This isn't the same as "qvm-start --no-guid", which does what I suppose you've expected. When VM is started with --no-guid, first qvm-run without --nogui will show the VM window (launch gui daemon).

Regarding "...killed" message it is fixed in systemd package in fc18 (an will not be backported to fc17 - I've linked somewhere redhat bug about this).

BTW It looks like there is no option to start guid for HVM without PV drivers installed (qrexec_installed=false) when VM was started with --no-guid. Anyway I see no practical use case of HVM with --no-guid - this option is for VMs started before X server (service VMs), but we do not support HVM as service VM.

[marmarek]

Comment by marmarek on 6 Dec 2012 03:28 UTC
You meant qvm-start, right (or qvm-run -a)? As discussed in emails, this requires patch for libxl/libxc...

The qvm-run --nogui switch means "application will have no access to GUI", which is useful for launching background tasks like Qubes RPC services. This isn't the same as "qvm-start --no-guid", which does what I suppose you've expected. When VM is started with --no-guid, first qvm-run without --nogui will show the VM window (launch gui daemon).

Regarding "...killed" message it is fixed in systemd package in fc18 (an will not be backported to fc17 - I've linked somewhere redhat bug about this).

BTW It looks like there is no option to start guid for HVM without PV drivers installed (qrexec_installed=false) when VM was started with --no-guid. Anyway I see no practical use case of HVM with --no-guid - this option is for VMs started before X server (service VMs), but we do not support HVM as service VM.

[marmarek]

Comment by marmarek on 12 Dec 2012 01:44 UTC
http://git.qubes-os.org/?p=marmarek/xen.git;a=commit;h=3cfbfa646e28a4d4e85829dfc0b21f9103b39479

[marmarek]

Comment by marmarek on 12 Dec 2012 01:44 UTC
http://git.qubes-os.org/?p=marmarek/xen.git;a=commit;h=3cfbfa646e28a4d4e85829dfc0b21f9103b39479