3:49 a.m.
hi,
this strange bug always happened with me on centos-5 with virt-manager.
our setup:
- host:
- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
- Intel S3000AHV
- 8GB RAM
- CentOS-5.2
- kernel-2.6.18-92.1.22.el5 x86_64 64bit
- guest-1:
- CentOS-5.2 - 4 vcpu
- kernel-2.6.18-92.1.22.el5 i386 32bit
- guest-2:
- CentOS-5.2 - 4 vcpu
- kernel-2.6.18-92.1.22.el5 x86_64 64bit
- guest-3:
- Mandrake-9 - 1 vcpu
- kernel-2.4.19.16mdk-1-1mdk 32bit
- guest-4:
- Mandrake-10 - 1 vcpu
- kernel-2.6.14.2-p4-smp 32bit
- guest-5:
- Windows XP Professional 32bit - 2 vcpu
- guest-7:
- Fedora-9 - 4 vcpu
- kernel-2.6.25.14-108.fc9.i686
if i restart libvirt i can start as the first guest the
guest-4/mandrake-10 but if i start any of the other guest i no longer
able to start guest-4.
now the most strange thing happened with guest-7 (fedora-9).
i use these packages build myself:
http://www.lfarkas.org/linux/packages/centos/5/
libvirt-0.6.0-1.x86_64.rpm
libvirt-python-0.6.0-1.x86_64.rpm
virt-manager-0.6.1-1.x86_64.rpm
python-virtinst-0.400.1-1.noarch.rpm
kvm-83-1.x86_64.rpm
and what've got from virt-manager is not too useful for me:
------------------------------------
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 498, in
run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 508, in startup
self.vm.create()
File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest:
------------------------------------
is there any way to find the reason?
thanks.
--
Levente "Si vis pacem para bellum!"
8:43 a.m.
On Tue, Feb 03, 2009 at 10:49:38AM +0100, Farkas Levente wrote:
if i restart libvirt i can start as the first guest the
guest-4/mandrake-10 but if i start any of the other guest i no longer
able to start guest-4.
It sounds like you have a resource conflict between the guests. Probably
something like having 2 guests configured to use the same VNC port, or
something along those lines.
------------------------------------
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 498, in
run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 508, in startup
self.vm.create()
File "/usr/lib64/python2.4/site-packages/libvirt.py", line 287, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error unable to start guest:
------------------------------------
is there any way to find the reason?
The $HOME//.virt-manager/virt-manager.log, or try starting the guest
from virsh command line.
Regards,
Dainel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
9:45 a.m.
Daniel P. Berrange wrote:
On Tue, Feb 03, 2009 at 10:49:38AM +0100, Farkas Levente wrote:
> if i restart libvirt i can start as the first guest the
> guest-4/mandrake-10 but if i start any of the other guest i no longer
> able to start guest-4.
It sounds like you have a resource conflict between the guests. Probably
something like having 2 guests configured to use the same VNC port, or
something along those lines.
ok, all of these xml files was generated with different version of
virt-manager, but anyway what should have to be the right
<graphics... line in libvirt's xml config file?
port='-1' autoport='yes'
or
port='-1'
or?
i'll change them and retest it.
--
Levente "Si vis pacem para bellum!"
5806
days inactive
5806
days old
2 comments
2 participants
participants (2)
-
Daniel P. Berrange -
Farkas Levente