Bug 806984
Summary: | libvirt doesn't fill in <console> pty path for xen guest, virsh console errors with: Unable to open stream for '(null)': Bad address | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | WSchleicher <wolfgang_schleicher> | ||||||||
Component: | libvirt | Assignee: | Libvirt Maintainers <libvirt-maint> | ||||||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 17 | CC: | berrange, clalancette, crobinso, dougsland, itamar, jforbes, jyang, laine, libvirt-maint, veillard, virt-maint | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | i686 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2012-06-06 11:22:37 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: | |||||||||||
Attachments: |
|
Description
WSchleicher
2012-03-26 17:06:35 UTC
Created attachment 572814 [details]
virt-install logfile
Created attachment 572816 [details]
logfile 1
attaching some more xen related logfiles.
Created attachment 572817 [details]
logfile 2
attaching some more xen related logfiles.
Hmm, looks like libvirt is generating console XML like: <console type='pty'> <target type='xen' port='0'/> </console> There should be a pty path in there. That error message: error: Unable to open stream for '(null)': Bad address Is coming from virsh console. So this is a libvirt issue Thanks for additional info and bug redirection. Today, I installed 17-Beta.RC4 which includes latest "libvirt-0.9.11-1.fc17.i686" and still faced the same problem. Seems that from first Fedora 17-TC libvirt does not play together with python-virtinst tool. Meanwhile I used xen old deployment style (xl create -c domu.cfg) with creates a working domU image but does not include 'smart configuration switches' as offered by python-virtinst (xml). Hopefully we'll see a working solution when Fedora 17 Final is released. If current 17.RC4 will become GOLD/FINAL release the reported problem still exists... No sure if fedora distribution is a suitable choice when it comes to xen as bare metal hypervisor. B.t.w., after installing xen packages, fedora's bootloader configuration (grub2.cfg / grub-install) ist not modified to boot in xen-environment. 'Problem' solved, xenconsoled was not running... daemon had to be started by hand |