Hi , guys, I have found in Fedora 10 Features , that there is still a
lot of work to provide xen kernel with dom0 support to Fedora 10 GA.
For my future project, which at 90 percent depends on virtualization
technology I am deciding between XEN or KVM virtualization. I am
experienced XEN user, KVM is new for me. But as I am aware of,
Qumranet was bought by RedHat which predicts something ...
Thanks in advance!
----- "Matt Cowan" <cowan(a)bnl.gov> wrote:
> On Sat, 13 Sep 2008, Fred Brier wrote:
> > Subject: Re: [Fedora-xen] problems with f9 guest on f8 dom0
> > I am using 32 bit and have the same issue you were. Did you ever
> solve the
> > problem? If so, how? Or should I just run Fedora 8 domU(s). Thank
> Haven't solved it yet, and have been totally unable to usefully run f9
> domU on an f8 dom0.
> We can get an f9 domU to install and run, but once it's shutdown,
> needs a reboot for virt-install or virt-manager to function again,
> which is basically useless except for testing. 'xm' seems to
> funtioning fine. Just tried again last week after installing the
> round of xen related updates... still no luck.
> Gonna try 64bit next, and if that doesn't work, centos dom0 :(
> Is *anyone* out there running 32bit f8 dom0 and f9 domU without
I'm continuing to run 64b F8 dom0 and F9 domU without any need to reboot the dom0 after bouncing a domU, but I do have to restart xend. My problem also affects F8 domUs. I've noticed, it seems, if I use xm commands to shutdown and startup then virt-manager retains track of the domU.
The last 2 libvirt updates have not been built for F8, so I'm not sure if there is any progress on the issue.
I'm not interested in switching to CentOS or RHEL until I'm "forced" by circumstances or rationality. I'd prefer to support Fedora. Theoretically F8 still gets updates until around Dec, 25 2008 right now.
There is a lot of impressive work going on with libvirt and virt in general from RedHat/Fedora, so I'm trying to be patient. I have a tenable workaround for now. Fingers crossed for F10.
Dale Bewley - Unix Administrator - Shields Library - UC Davis
GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3
Anytime I shutdown or restart (the guest will successfully restart) an
f9 guest on an f8 dom0 it causes virt-manager to hang and virt-install
to fail. Attempts to restart virt-manager hang at "Connecting". no
luck restarting xend, libvirtd, or even xenstored, only solution I've
found is a dom0 reboot! Same problem on 2 different host systems,
different hardware, dom0 installed by different people. I have no
trouble with <=f8 guests on either of these boxes.
more details at
I assume other people are successfully running f9 guests on f8 dom0?!
No one else having this issue?
A new problem for me. Since I was able to run guests with Xen, I'm
stuck with a time synchronization error each time system boot and
each time theses events occur, the VM seem to stop running (nothing is
displayed on screen) and after 5-10 minutes, normal `init` go on and
system work fine. After some search, I saw that's the problem comes
from `hwclock`. When i run it manually it display this error :
hwclock from util-linux-ng 2.13
hwclock: Open of /dev/rtc failed, errno=19: No such device. <<<<<
Using direct I/O instructions to ISA clock.
Last drift adjustment done at 1423924190 seconds after 1969
Last calibration done at 1423924190 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
I delete & recreate /dev/rtc but it does not solve the problem.
Maybe this problem was discussed before on this list but i was unable
to find any search tools on fedora/redhat website and manually search
against the subject for the 6 last month did not return me any good
So, maybe a quick solution about this veeeerrrryyyy long boot time exist.
Thanks for your help.
I updated virt-manager 0.6.0 and python-virtinst 0.400.0 and when i am
trying to start virt-manager i am getting Python syntax error:
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 346, in ?
File "/usr/share/virt-manager/virt-manager.py", line 287, in main
from virtManager.engine import vmmEngine
File "/usr/share/virt-manager/virtManager/engine.py", line 31, in ?
from virtManager.connection import vmmConnection
File "/usr/share/virt-manager/virtManager/connection.py", line 36, in ?
from virtManager.domain import vmmDomain
File "/usr/share/virt-manager/virtManager/domain.py", line 669
SyntaxError: invalid syntax
CentOS using default python (RPM = python-2.4.3-21.el5):
Python 2.4.3 (#1, May 24 2008, 13:57:05)
[GCC 4.1.2 20070626 (Red Hat 4.1.2-14)] on linux2
My python skills are somewhat non-existent so can anyone give any help how
to fix this?
Pekka Panula, Net Servant Oy
I finally achieve a goal to start a para-VM with xen. But i still experience
problem with networking inside the vm (domU).
There are no network interface shown. Maybe kernel module is not loaded for
the emulated NIC.
In domU i'm only able to see loopback interface. But, in dom0 i can see all
bridge interface and networking is OK.
Can someone help me ?
>> It is not an HVM "build" so, i tought virtualization extensions are
>> useless ? And i don't have intel-VT on my system.
> That may be the entire problem.
> My understanding is that the paravirtualized kernel needs those extensions
> so that the supervisor calls do not have to go through the hypervisor.
For me it wasn't =) !
For my knowledge, HVM extension was needed by xen only for
fully-virtualized OS. (like Microsoft OS and other closed source OS ;
because no modification can't be made to their kernel to make them
aware of "xen".). But maybe i'm wrong !
And if you're right, it will explain why networking don't work (and
will never on my system)
--> but keep in mind that xen exist a "long time" before hvm
extension do. And I thought that other people made networking works in
their xen VM. So, I tought that i can get rid of this problem without
hvm set on.
Someone can light me more about it ?
2008/9/15 lamont cranston <l.cranston(a)gmail.com>
> 1) verify that the virtualization extensions are turned on in the BIOS (in my case, a HP prolient server, the selection was actually named "virtualization")
It is not an HVM "build" so, i tought virtualization extensions are
useless ? And i don't have intel-VT on my system.
> 2) when you get to the end of your install of the guest OS, you should have the option to "share" the network device
I did not use any wizard to create the vm (i made a copy of an
actual system to an image file, and create the "xm" config file)
> 3) easiest way to verify the guest IP is to ask the guest - you can reason it out from the host ifconfig, but just asking the guest is a lot simplier and just "feels" right :)
I'm not so good in English, what do you mean ? :-D