Hi Guido, the bug has two separate parts now, the initial fault on leny (1), and a recurrence of the supposedly resolved console issue we referred to, which occured on other lenny.
re the first;
I've had to make severall attempts to re-invoke the bug. I did finally do so.
I did an install of karmic successfully. Initially, the fault occurred trying
to install hardy, from the cdrom, a full virt install. I then tried karmic,
and it occurred. I managed to create a couple more vms from the cdrom, fairly
old systems.
I retried hardy, which was difficult. Then retried karmic. What needs to be
done is to fully allocate any /dev/pts that are made on boot to vms, so none
are spare. Now seeing I couldn't trigger it using SimplyMepis or fedora, it
may be a bug or glitch to do with hardy and karmic installers, an ubuntu issue.
If I had selected fedora initially, it may not have occurred, just an unknown.
* the full install log from virt-manager --debug
* the versions of xen, virt-manager/virtinst and libvirt0 you're
actually using.
* any output from libvirt in syslog
The trouble is, I couldn't get a log, and you can tell me why because I don't
know. I ensured .virt-manager was had no virt-manager.log, and removed dmesg
and syslog to captire only related info. All were empty. dmesg and syslog I
can understand, but what's going on with virt-manager??
So, if it's a bug, it's normal or minor, since it doesn't happen every time. It
may be an issue with ubuntu's installer, but being difficult to replicate, it's
not a pckage breaker. Take that as you will.
re the second,
This isn't a paraviert install I guess? Please provide the information
as requested in the bug report.
this is more challenging and odd since it's supposedly already resolved. It
only occurs in other lenny, and does currently occur every time. It's not a
paravirt, it's a hvm. I gave up trying to do a paravirt install from a cd long
ago. The stringent network install requirements seem to exclude and cd or dvd
prepared system.
* the full install log from virt-manager --debug
* the versions of xen, virt-manager/virtinst and libvirt0 you're
actually using.
* any output from libvirt in syslog
* the full install log from virt-manager --debug
See attached logs. One is as regular user, the other as root, so that's not
the issue.
* the versions of xen, virt-manager/virtinst and libvirt0 you're
actually using.
virt-manager 0.6.0-6
xen 3.2-1
virtinst and libvirt0 0.7.6-1~bpo50+1
* any output from libvirt in syslog
None to provide.
Please also check if this applies to your case:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508139
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520641
No, they don't seem to.
Please try to create a hvm machine withouth virtinst/virt-manager so we
can be sure your XEN installation works as expected.
ide...@debian:~$ sudo virsh -c xen
Welcome to virsh, the virtualization interactive terminal.
Type: 'help' for help with commands
'quit' to quit
virsh # list
Id Name State
----------------------------------
0 Domain-0 running
3 fedora12 no state
virsh # shutdown fedora12
Domain fedora12 is being shutdown
virsh # create /mnt/lenny-xen/etc/xen/karmic.xml
Domain karmic created from /mnt/lenny-xen/etc/xen/karmic.xml
virsh # list
Id Name State
----------------------------------
0 Domain-0 running
5 karmic no state
See attached xml file.
I might try the first in lenny (1) to get a log/
Would xend.log not help too?
_________________________________________________________________
Need a new place to live? Find it on Domain.com.au
http://clk.atdmt.com/NMN/go/157631292/direct/01/
virt-manager.log-fedora
Description: Binary data
virt-manager.log-root
Description: Binary data
<domain type='xen' id='5'>
<name>karmic</name>
<uuid>c5553a73-3a93-b6bc-3ba7-f2093cc15495</uuid>
<memory>300032</memory>
<currentMemory>262144</currentMemory>
<vcpu>2</vcpu>
<os>
<type>hvm</type>
<loader>/usr/lib/xen-default/boot/hvmloader</loader>
<boot dev='hd'/>
</os>
<features>
<acpi/>
<apic/>
<pae/>
</features>
<clock offset='utc'/>
<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>restart</on_crash>
<devices>
<emulator>/usr/lib/xen/bin/qemu-dm</emulator>
<disk type='file' device='disk'>
<driver name='file'/>
<source file='/mnt/images/xen/images/ubuntu/karmic.img'/>
<target dev='hda' bus='ide'/>
</disk>
<disk type='file' device='cdrom'>
<target dev='hdc' bus='ide'/>
<readonly/>
</disk>
<interface type='bridge'>
<mac address='00:16:36:37:e2:c8'/>
<source bridge='eth0'/>
<script path='vif-bridge'/>
<target dev='vif5.0'/>
</interface>
<serial type='pty'>
<source path='/dev/pts/0'/>
<target port='0'/>
</serial>
<console type='pty' tty='/dev/pts/0'>
<source path='/dev/pts/0'/>
<target port='0'/>
</console>
<input type='mouse' bus='ps2'/>
<graphics type='vnc' port='5900' autoport='yes' keymap='en-us'/>
<sound model='es1370'/>
</devices>
</domain>
