Bug 490032
Summary: | Support configuration of character devices (serial, parallel, pv console) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Darryl L. Pierce <dpierce> |
Component: | python-virtinst | Assignee: | Cole Robinson <crobinso> |
Status: | CLOSED WONTFIX | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.3 | CC: | j.golderer, tross, xen-maint |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-10-13 15:05:29 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Darryl L. Pierce
2009-03-12 21:38:48 UTC
That is not really practical, because as part of provisioning the guest we often have to create temporary files for kernel/initrd/isos that we download. The initial XML config points to these temporary files for install, and once installed the config is updated. These temporary files are immediately deleted. So if we created, but didn't start the VM, then you wouldn't be able to start it later, because the temporary files are gone. Can you explain the general use case / scenario you are trying to deal with, rather than a specific solution. We're creating virtual machines that are used for testing purposes, using virt-install which is easier for creating the VM from a script. One limitation we've found to this process is that virt-install does not allow us to define serial ports for the VM. So what we've done in the short term is: 1. use virt-install to define the vm 2. immediately kill the vm 3. edit the XML to inject a serial port 4. restart the vm Perhaps an option to virt-install to create a serial port would be more practical? Yes, if you need serial device configuration, we should definitely add that support natively instead of hacking around it. How important is this for RHEL5? This functionality is upstream, but it would be a pretty substancial backport, so I don't think it's the best idea for 5.5. Since you currently have a working solution, I'm closing this WONTFIX. Please reopen if this is important for 5.5 |