Re: [Fedora-xen] Goodbye Xen on RH/Fedora?
by Daniel P. Berrange
On Wed, Jan 21, 2009 at 01:40:38PM -0500, Dustin Henning wrote:
> Also, while I'm on the topic, PCI-passthrough was a factor in my
> decision as well. Unfortunately, I'm stuck on F8 as well, because I can't
> get networking to work on CentOS Xen with my hardware. However, I
> understand what is going on, so I'm just holding my breath.
PCI passthrough for KVM is now available, and will be supported in the
next libvirt....which reminds me that we never supported PCI pasthrough
for Xen in libvirt...
Daniel
--
|: 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 :|
15 years, 3 months
Migration from Xen to KVM
by jean-Noël Chardron
Hello,
rjones(a)redhat.com wrotes about migration :
>Install a recent Linux kernel in the guest, adjust the configuration
>file[1], and reboot. You only need Xenner if you want to run the Xen
>PV guest unchanged (ie. without installing a new guest kernel).
>
>Rich.
>[1] 'virsh edit domname', and edit the domain type, <os> and
><emulator> fields, as detailed here: http://libvirt.org/drvqemu.html
I tried an centos5.2 dom0 with a domu centos5.2
It is not trivial
the tools virsh and xm are not functional to start the domain
So how do you start the domu
As When I launch the command : #qemu-kvm /etc/xen/domuAKVM
as domuAKVM is a new configuration file simply like the configuration of
the old xen domu
in the console the message is "Boot from hard disk failed : no bootable
disk"
So I have no more domU
15 years, 3 months
f10 x86_64 xen VM guests fail to boot on f8 host
by Jon Swanson
This is a cross post of the same subject on the Fedora Forums. If this
is bad practice let me know and i'll never do it again.
Additional log info is available at
http://forums.fedoraforum.org/showthread.php?p=1149972&posted=1#post1149
972
I have two machines running fresh installs of f8 with the xen. Kernel
and all software versions are the same on both.
Specifically:
[root@machineA boot]# uname -a
Linux machineA 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux
[root@machineA boot]# virsh version
Compiled against library: libvir 0.4.4
Using library: libvir 0.4.4
Using API: Xen 3.0.1
Running hypervisor: Xen 3.1.0
And:
[root@machineB ~]# uname -a
Linux machineB 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008
x86_64 x86_64 x86_64 GNU/Linux
[root@machineB ~]# virsh version
Compiled against library: libvir 0.4.4
Using library: libvir 0.4.4
Using API: Xen 3.0.1
Running hypervisor: Xen 3.1.0
MachineA has two AMD Opteron 275s. MachineB has four Intel(R) Xeon(TM)
CPU 2.80GHz processors.
Both machines are as up to date as possible.
I can boot or create x86_64 f10 guests on MachineA with no trouble
whatsoever.
MachineB will not boot/create x86_64 f10 guests.
The configuration files are created in the same manner, but as soon as
Xen tries to unpause the newly created domain, it crashes pretty much
instantly.
/var/log/xen/xend.log relevant output:
[2009-01-16 14:45:32 4120] DEBUG (DevController:150) Waiting for devices
vtpm.
[2009-01-16 14:45:32 4120] INFO (XendDomain:1130) Domain f10testB (21)
unpaused.
[2009-01-16 14:45:32 4120] WARNING (XendDomainInfo:1203) Domain has
crashed: name=f10testB id=21.
[2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1802)
XendDomainInfo.destroy: domid=21
[2009-01-16 14:45:32 4120] DEBUG (XendDomainInfo:1821)
XendDomainInfo.destroyDomain(21)
I've also tried moving a functional guest from MachineA to MachineB to
boot it there, with the same results. Guest will not boot on MachineB.
f8 64bit guests will boot on MachineB with no problems.
f10 32bit guests will boot on MachineB with no problems.
Only 64bit machines seem to be borked.
Any information / help / insight as to why this is happening would be
very much appreciated. The machines are pretty similar, and since the
guests are paravirtualized it does not really make sense for the
processors to be the cause of the problem.
Thanks,
jon
15 years, 3 months
FC10 domu FC8 x86_64 with/without HVM support (possible bug)
by Phillip Bertolus
Hi list,
Just finished confirming that a PV FC10 domu won't run on FC8 without VT
support.
Background:
Create FC8 domu x86_64. Yum upgrade to FC10 x86_64.
FC8 domu runs on both hosts.
FC10 domu runs only on host with VT support.
FC10 runs on both with the old FC8 kernel.
Both hosts indicate they are running pvm images:
xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches
however (and this may have nothing to do with anything):
elf_xen_parse_note: HV_START_LOW = 0xffff800000000000
Any help most appreciated.
We have lots of 64 bit servers without hardware virtualization support.
Cheers
Phill
Machine host 1) Doesn't work (no VT in this processor).
Linux office64 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 4
model name : Intel(R) Xeon(TM) CPU 3.00GHz
stepping : 3
cpu MHz : 3000.106
cache size : 2048 KB
physical id : 1
siblings : 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc up pni monitor ds_cpl cid cx16 xtpr
bogomips : 6007.27
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
[ root@office64 xen ]# rpm -qa | grep xen
kernel-xen-devel-2.6.21.7-5.fc8
xen-libs-3.1.2-5.fc8
kernel-xen-2.6.21.7-5.fc8
xen-3.1.2-5.fc8
Some lines from the domain-builder-ng.log:
arch_setup_bootearly: doing nothing
xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches
xc_dom_compat_check: supported guest type: xen-3.0-x86_32p
xc_dom_update_guest_p2m: dst 64bit, pages 0x40000
xend.log
[2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0',
'uuid': '839a0c0f-a332-f38c-63ef-834563cde36a', 'on_reboot': 'restart', 'start_time': '1232088953.4', 'on_poweroff': 'destr
oy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel ) (notes (H
V_START_LOW 18446603336221196288) (FEATURES '!writable_page_tables|pae_pgdir_above_4gb') (VIRT_BASE 18446744071562067968) (G
UEST_VERSION 2.6) (PADDR_OFFSET 0) (GUEST_OS linux) (HYPERCALL_PAGE 18446744071578882048) (LOADER generic) (SUSPEND_CANCEL 1
) (PAE_MODE yes) (ENTRY 18446744071584739840) (XEN_VERSION xen-3.0)))", 'name': 'f10.reference'}
[2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:956) Storing domain details: {'console/ring-ref': '1347740', 'image/entry'
: '18446744071584739840', 'console/port': '2', 'store/ring-ref': '1347741', 'image/loader': 'generic', 'vm': '/vm/839a0c0f-a
332-f38c-63ef-834563cde36a', 'control/platform-feature-multiprocessor-suspend': '1', 'image/hv-start-low': '1844660333622119
6288', 'image/guest-os': 'linux', 'image/virt-base': '18446744071562067968', 'memory/target': '1048576', 'image/guest-versio
n': '2.6', 'image/pae-mode': 'yes', 'console/limit': '1048576', 'image/paddr-offset': '0', 'image/hypercall-page': '18446744
071578882048', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'image/features/pae-pgdir-above-4gb': '1', 'imag
e/features/writable-page-tables': '0', 'name': 'f10.reference', 'domid': '110', 'image/xen-version': 'xen-3.0', 'store/port'
: '1'}
[2009-01-16 17:55:53 30586] WARNING (XendDomainInfo:1203) Domain has crashed: name=f10.reference id=110.
[2009-01-16 17:55:53 30586] ERROR (XendDomainInfo:1317) Xend failed during restart of domain 110. Refusing to restart to av
oid loops.
[2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=110
[2009-01-16 17:55:53 30586] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch
===========================
Machine host 2) Does work.
Linux seanl64 2.6.21.7-5.fc8xen #1 SMP Thu Aug 7 12:44:22 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 107
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 3600+
stepping : 1
cpu MHz : 1908.705
cache size : 512 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy misalignsse
bogomips : 3819.31
TLB size : 1024 4K pages
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps
[root@seanl64 ~]# rpm -qa | grep xen
kernel-xen-2.6.21.7-3.fc8
xen-libs-3.1.2-5.fc8
xen-3.1.2-5.fc8
kernel-xen-2.6.21.7-5.fc8
Some lines from the domain-builder-ng.log:
arch_setup_bootearly: doing nothing
xc_dom_compat_check: supported guest type: xen-3.0-x86_64 <= matches
xc_dom_compat_check: supported guest type: xen-3.0-x86_32p
xc_dom_compat_check: supported guest type: hvm-3.0-x86_32
xc_dom_compat_check: supported guest type: hvm-3.0-x86_32p
xc_dom_compat_check: supported guest type: hvm-3.0-x86_64
xc_dom_update_guest_p2m: dst 64bit, pages 0x40000
>From the domu:
Fedora release 10 (Cambridge)
Kernel 2.6.27.9-159.fc10.x86_64 on an x86_64 (/dev/hvc0)
localhost.localdomain login:
15 years, 3 months
Turning off virt-manager dhcp and dns
by Stephen Johnston
Hi
I have virt-manager with a static ip'ed windows server 2003 and a win xp
client so I can play with active directory etc for work. All under
Fedora 10 beta.
Can someone tell me if I can turn off the dhcp and dns in the
virt-manager framework (vibr0) as it is handing out an ip to my client
before the virtual windows server does. I believe this is confusing the
issue when I try to join the client to my virtual windows domain.
I only wish the virt-manager to nat vibr0 to my physical nic so i can
provide the other config items from within my virtual network.
Thank you.
Stephen
--
Stephen Johnston 8 Lime Grove
Tel. +44 (0)1506 437766 Craigshill
Mob. 07786 733 150 Livingston
West Lothian
EH54 5FB
15 years, 3 months
Xen disks are read-only after some time.
by Ján ONDREJ (SAL)
Hello,
I have problems to run Fedora 10 guests on Fedora 8 dom0. My servers are
running some time, but then they was unable to write changes to disks. There
is nothing special in logs or dmesg. This happens aprox 24-48 hours after
restart. When trying to log anything to disk, after reboot this is gone. I
can log it over network, but don't know what to log. Can somebody help me to
debug this problem?
My problem was reported on RH and kernel bugzillas:
https://bugzilla.redhat.com/show_bug.cgi?id=478414
http://bugzilla.kernel.org/show_bug.cgi?id=12331
but without any answer. :(
May be there is something similar like in this thread:
http://lkml.indiana.edu/hypermail/linux/kernel/0901.0/00121.html,
just on my server there is only ext3, not ext4. Also trying to turn off
daily backups (which uses snapshots) without success.
After reboot to fc8 kernel everything is running fine again, but running
fc8 kernel on fc10 is not a good solution (except that F8 is EOL).
Thank you.
SAL
15 years, 3 months
unsubscribe
by Christian Reiter
Mit freundlichen Grüßen, /// Kind Regards,
Christian Reiter
--
Christian Reiter ||| c.reiter(a)gmx.net
15 years, 3 months
Re: [Fedora-xen] NTP problem in PAE kernel
by Lamont Peterson
On Saturday 03 January 2009 07:44:41 am Norman NTP wrote:
> Hello,
>
> I have a question that we are using Fedora-8 as DOM0 and Fedora-10 as
> DomU, how DomU can use by default clock of DOM0 so in that way if i
> want to change the time on DomU it wont allow me to change the time on
> DomU.I am using Xen Kernel on DOM0 and PAE Kernel on DomU.
[snip]
The system clock in a paravirtualized kernel cannot be set. The hardware
clock in an HVM domU also cannot be set. The hadware clock and the system
clock for paravirtualized domUs is controlled in dom0.
I really like this, as I can set up NTP in dom0 and all of the clocks will be
in sync in my domUs, just like that.
I don't know of any way to configure a domU to be able to control it's own
clock separately, other than taking out the source and updating the code to
give you that option. I wouldn't bother.
--
Lamont Peterson <lamont(a)lamontpeterson.org>
[ http://lamontpeterson.org/ ]
GPG Key fingerprint: C51E DD83 B03F D147 A974 939C 5D13 289C 17F1 FFBE
15 years, 3 months
New Fedora virtualization list: fedora-virt
by Daniel Veillard
As the initiator for this list, I must admit I made a mistake
3 years ago, I should have picked a list name agnostic from the
hypervisor name. With the current state of Xen in Fedora recent
releases it really make sense to try to correct that mistake ...
it's never too late ! So
https://www.redhat.com/mailman/listinfo/fedora-virt
is born, I don't want to mass-subscribe people, especially as
I think the current list should survive with its Xen centric
focus. You can subscribe directly to the new URL above.
The topic is everything concerning Fedora and virtualization
including Xen.
I think the current list would be a good place for people
still using Fedora <= 8 with Xen, but it's just a suggestion :-)
Daniel
--
Daniel Veillard | libxml Gnome XML XSLT toolkit http://xmlsoft.org/
daniel(a)veillard.com | Rpmfind RPM search engine http://rpmfind.net/
http://veillard.com/ | virtualization library http://libvirt.org/
15 years, 3 months
Updating Xen to 3.3.1
by Pasi Kärkkäinen
Hello!
Xen 3.3.1 has been released with a lot a of fixes so it would be nice to get
xen hypervisor/tools/libs packages updated in fedora.
Xen 3.3.1 does not yet contain pv_ops dom0 support fixes/patches from
xen-unstable, so those backported patches in 3.3.0-2 are still needed for
3.3.1.
-- Pasi
15 years, 3 months