Problem to using virt-install
by Margusja
Hello, can somebody give me some hint how to resolve my problem?
[root@bacula ~]# uname -a
Linux bacula 2.6.21.7-3.fc8xen #1 SMP Thu Mar 20 14:57:53 EDT 2008 i686
i686 i386 GNU/Linux
kernel-xen.i686 2.6.21.7-3.fc8
installed
kernel-xen-devel.i686 2.6.21.7-3.fc8
installed
xen.i386 3.1.2-2.fc8
installed
xen-devel.i386 3.1.2-2.fc8
installed
xen-libs.i386 3.1.2-2.fc8 installed
libvirt.i386 0.4.4-1.fc8
installed
libvirt-python.i386 0.4.4-1.fc8
installed
python-virtinst.noarch 0.300.2-4.fc8
installed
virt-manager.i386 0.5.3-2.fc8 installed
[root@bacula ~]# virt-install -f /var/xen/xen1 -r 512
libvir: Remote error : Connection refused
libvir: warning : Failed to find the network: Is the daemon running ?
libvir: Remote error : Connection refused
What is the name of your virtual machine? xen1
libvir: Xen Daemon error : GET operation failed: xend_get: error from
xen daemon:
Would you like to enable graphics support? (yes or no) no
What is the install location?
ftp://ftp.linux.ee/pub/fedora/linux/releases/8/Fedora/i386/os/
Starting install...
libvir: Xen Daemon error : GET operation failed: xend_get: error from
xen daemon:
Retrieving file .treeinfo 100% |=========================| 430 B
00:00
Retrieving file vmlinuz.. 100% |=========================| 2.1 MB
00:04
Retrieving file initrd.im 100% |=========================| 6.4 MB
00:17
libvir: Xen Daemon error : GET operation failed: xend_get: error from
xen daemon:
libvir: Xen Daemon error : GET operation failed: xend_get: error from
xen daemon:
virDomainLookupByID() failed GET operation failed: xend_get: error from
xen daemon:
Domain installation may not have been successful.
If it was, you can restart your domain by running 'virsh start xen1';
otherwise, please restart your installation.
Fri, 11 Jul 2008 10:30:21 ERROR virDomainLookupByID() failed GET
operation failed: xend_get: error from xen daemon
Traceback (most recent call last)
File "/usr/sbin/virt-install", line 502, in <module>
main()
File "/usr/sbin/virt-install", line 462, in main
dom = guest.start_install(conscb,progresscb)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 813, in
start_install
return self._do_install(consolecb, meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 829, in
_do_install
self._create_devices(meter)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in
_create_devices
nic.setup(self.conn)
File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 281, in
setup
vm = conn.lookupByID(id)
File "/usr/lib/python2.5/site-packages/libvirt.py", line 920, in lookupByID
if ret is None:raise libvirtError('virDomainLookupByID() failed',
conn=self)
libvirtError: virDomainLookupByID() failed GET operation failed:
xend_get: error from xen daemon
[root@bacula ~]# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 489 1 r-----
738.2
--
---
Margusja
+3725148780
skype: margusja
msn: margusja(a)kodila.ee
homepage: http://margusja.pri.ee
15 years, 9 months
In case this helps.
by Jack
I've been fighting xen for a few weeks now so sorry if this is old news but
here's what I 've found, hope it helps a few.
1) You cant run xen dom0 in vmware - not true it seems...?
Yes you can. I did a lot of searching and found lots of 'you cant' it has
to be bare metal to work but its not true.
BTW - you can search for days and not find anything on fedora / xen /
clustering its really a hard time at the moment we
need to sort it out...
I was installing FC8 on VMware and trying everything but xen says on boot
"relinquishing vga console". This is bad and means
when you later run virt-manager you will be only be offered qemu emulation
and paravirtualization will not be available because
XEN didn't really boot.
So I installed FC8 native straight on the hardware, and still the same thing
happened, Xen wouldn't boot properly and virt-manager
only offered my qemu emulation. Some searching suggested machines with 4gb
may be the problem so maybe it works for you but
FC8 out of the box does not work on my AMD 64X2 Nforce motherboard system
with 5Gb ram.
My working machine ran FC7, and the kernel-xen was kernel-xen......7.rpm
My FC8 was running kernel-xen.....7.3. I removed
kernel-xen .....7.3 and installed the kernel-xen .....7.rpm from website
rpmfind and now it booted and xen emulation was
available in virt-manager. Virt-manger didn't work first time so I had to
give it a push with:
virt-manager -c xen:///system
and then all was good. No longer was qemu the only option and I could
create proper paravirtualized machines.
I wondered if the 'vmware doesn't work with xen' was really true after this
and sure enough, replacing
the FC8 kernel with the kernel-xen ....7 from fc7 also gave me proper dom0
emulation in vmware too.
Hope this helps someone. Basically - its not always your fault you need
the right mix of kernel and xen to support your hardware
and if you get the "xen relingquishing vga console" message on boot it means
you don't have xen working properly and need to
explore a different build for your hardware.
J.
15 years, 9 months
Cannot start HVM DomU
by Robert Locke
This has newly started, so I am presuming that it is perhaps related to
some recently updated package on F8 in say the last week or so.
I have a WindowsXP DomU that when I try to start from virt-manager gives
the following error:
Error starting domain: virDomainCreate() failed POST operation failed:
(xend.err 'int argument required')
Details shows:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/engine.py", line 472, in
run_domain
vm.startup()
File "/usr/share/virt-manager/virtManager/domain.py", line 379, in
startup
self.vm.create()
File "/usr/lib/python2.5/site-packages/libvirt.py", line 240, in
create
if ret == -1: raise libvirtError ('virDomainCreate() failed',
dom=self)
libvirtError: virDomainCreate() failed POST operation failed: (xend.err
'int argument required')
I have no idea what other information to supply or where to particularly
find it since this has generally "just worked" for the occasional
running of a Windows instance that I have needed for the last several
months.
Thanks for any help,
--Rob
15 years, 10 months
Xen and disaster recovery / redundancy / failover
by Jack
Hi All,
Forgive me if this was discussed last week I'm new...
I currently run two servers, one for mail, one for web + db, but will be
expanding
In future so a virtual architecture seems a good idea, especially if I can
run the VM's
on any of the physical machines on the fly as load / failures dictate.
Ideally this would
all be automatic and the VM's would share processor / storage transparently
amongst
available machines, and I would also like to add extra storage as necessary
without having
to rebuild arrays or reinstall stuff.
I'd like to replace the os on both physical machines with minimal fedora 8 +
xen and
run the mail / web / db services inside VM's. I've got a F9 system running
inside a VM
on the mailserver now but don't know how to get it running on both machines
as I'm
not sure what's possible with exporting / sharing VM settings.
For now, What I need is to be able to run the image of the F9 system on my
web box
when the mail server crashes so that the mail server is still available
should the physical
mail server break.
My thinking was if both machines just run a minimal system + the VM's then
the
other disks in the machines can be running a raided gfs across both machines
to
provide a redundant storage system that can survive a machine failure.
Hopefully then should a box pack up I can still run all my services in VM's
on a single
machine since the VM images will be available to both machines on the shared
filesystem.
I don't even know which parts of this are possible or whether its a bad
strategy, perhaps
there's a better approach to all of this, ideas welcome,
Thanks,
Jack
15 years, 10 months
FW: VNC clash with virt-manager installer
by Jack
Hi All,
I connect to my machine remotely over vnc, if I install a new VM through
Virt-manager, it gives me a flashing screen complaining or TCP errors and
connection refused to the VNC service. I'm guessing virt manager is
clashing
with my remote VNC connection so it cant display the booting os.
Is there a way to get virt-manager to use a different VNC port? Or some
other
way to get them to play nicely?
Thanks,
Jack.
15 years, 10 months
XEN configuration
by Luca
Hi all,
I'm using XEN on Fedora 8. I tried building a rootfilesystem over ram disk,
but when I use it to boot XEN I got the following error:
(XEN) Panic on CPU 0:
(XEN) Domain 0 allocation is too small for kernel
image.
(XEN)
****************************************
(XEN)
If instead I use a normal initial filesystem, I noticed (looking at XEN's
boot output) that
(XEN) PHYSICAL MEMORY ARRANGMENT:
(XEN) Dom0 alloc.: 000000003c000000->000000003e000000 (470953 pages to be
allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel:
c1000000->c1401000
(XEN) Init. ramdisk:
c1401000->c1afe800
(XEN) Phys-Mach map:
c1aff000->c1cd2ea4
(XEN) Start info:
c1cd3000->c1cd346c
(XEN) Page tables:
c1cd4000->c1ce9000
(XEN) Boot stack:
c1ce9000->c1cea000
(XEN) TOTAL:
c0000000->c2000000
(XEN) ENTRY ADDRESS: c1000000
(XEN) Dom0 has maximum 2 VCPUs
So it seems that if my root filesystem is too big (more than 33M) there is
no space for XEN to load the kernel and the root filesystem in memory.
Is there a way to change the XEN physical memory arrangement (in order to
have enough space for the kernel and the root filesystem)?
My system has 2G of RAM. My root filesystem is 250M and I'm planning to
assign 512M to domain 0.
Thanks,
Gianluca
15 years, 10 months
