Skip to content

Conversation

@markgoddard
Copy link

No description provided.

For the engine and emulator configuration, some level of autodetection
is supported - if KVM is supported, this will be used, otherwise QEMU
will be used.

Much of the logic added here has been adapted from the ironic devstack
plugin's tooling.
Machine default is pc-1.0. Perhaps this should be none by default?

Mode default is 'host-passthrough' for KVM, 'host-model' otherwise.
@markgoddard markgoddard self-assigned this Aug 2, 2018
<serial type='pty'/>
<console type='file'>
<source path='{{ libvirt_vm_console_log_path }}'/>
<target type='serial'/>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is probably the main change I'm concerned about as it changes the behaviour from interactive serial console to file logging.

@markgoddard markgoddard force-pushed the support-virt-engine branch from 3e886a7 to da56e8c Compare August 2, 2018 15:41
@markgoddard markgoddard merged commit 33f5f72 into master Aug 2, 2018
@markgoddard markgoddard deleted the support-virt-engine branch August 2, 2018 15:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants