I''m a bit torn between asking here and asking on the Fedora test list. I''d like to use the latest xen (that''s what I''m testing), but I don''t want to upgrade to the entire development tree. I tried this, and was astonished at the number of packages to upgrade! [root@potoroo ~]# yum install --disablerepo=* --enable=development kernel-xen kernel-xen-2.6-doc xen xen-hypervisor xen-libs xenwatch | wc -l Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package kdemultimedia-extras-nonfree 845 [root@potoroo ~]# Those 845 lines represent upgrading pretty much all of KDE and all of Gnome. The package "xen" alone accounts for much of this: [root@potoroo ~]# yum install --disablerepo=* --enable=development xen | wc -l Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package kdemultimedia-extras-nonfree 844 [root@potoroo ~]# My idea of an ideal host for virtual machines is one that runs guests and precious little else, and certainly not a GUI and all the baggage that entails. Do these *xen* packages build on f8? What''s the easy way to get the source - I used to use up2date, but I fear the technolgogy''s getting ahead of me. -- John the Bewildered.
Daniel P. Berrange
2008-Jan-22 00:29 UTC
Re: [Fedora-xen] Upgrade to development xen on F8?
On Tue, Jan 22, 2008 at 09:22:15AM +0900, John Summerfield wrote:> I''m a bit torn between asking here and asking on the Fedora test list. > > I''d like to use the latest xen (that''s what I''m testing), but I don''t want to > upgrade to the entire development tree.By latest Xen do you mean ''3.2.0'' ? After discussions with upstream Xen developers we decide that Fedora will only ever support the version of Xen that ships at the same time as that Fedora release. eg F8 supports 3.1.x, and F9 support 3.2.x. Meanwhile upstream Xen will provide backports of new Xen releases for people who wish to try on existing Fedora. eg Xen provides a 3.2.0 RPM for Fedora 8 which you can get from xen.org. We co-operated to ensure the RPMs follow the same style so it ought to be reasonably painless. WRT to rawhide, I''d strongly recommend against upgrading to that any time soon. Its just going to be too unstable to usefully run Xen until we get the new kernel sorted. The existing kernel-xen in rawhide is known to be broken wrt to even basic things like X and the ''ip'' command.> I tried this, and was astonished at the number of packages to upgrade! > [root@potoroo ~]# yum install --disablerepo=* --enable=development kernel-xen > kernel-xen-2.6-doc xen xen-hypervisor xen-libs xenwatch | wc -l > Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package > kdemultimedia-extras-nonfree > 845 > [root@potoroo ~]# > > Those 845 lines represent upgrading pretty much all of KDE and all of Gnome.Hmm, the ''xen'' RPM still has a dep on ''python-virtinst'' which still has a dep on ''virt-viewer'' which uses GNOME. At very least we need to break the dep between xen and python-virtinst - its a historical thing to assist in upgrades from the FC5 days when ''virt-install'' was part of the ''xen'' RPM itself. Since FC5 and FC6 are long dead we can kill the dep. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
You could download and build the latest stable or test source from xen.org. This assumes you are familiar with that sort of thing, but if you want to test, you probably are... Dustin -----Original Message----- From: fedora-xen-bounces@redhat.com [mailto:fedora-xen-bounces@redhat.com] On Behalf Of John Summerfield Sent: Monday, January 21, 2008 19:22 To: fedora-xen@redhat.com Subject: [Fedora-xen] Upgrade to development xen on F8? I''m a bit torn between asking here and asking on the Fedora test list. I''d like to use the latest xen (that''s what I''m testing), but I don''t want to upgrade to the entire development tree. I tried this, and was astonished at the number of packages to upgrade! [root@potoroo ~]# yum install --disablerepo=* --enable=development kernel-xen kernel-xen-2.6-doc xen xen-hypervisor xen-libs xenwatch | wc -l Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package kdemultimedia-extras-nonfree 845 [root@potoroo ~]# Those 845 lines represent upgrading pretty much all of KDE and all of Gnome. The package "xen" alone accounts for much of this: [root@potoroo ~]# yum install --disablerepo=* --enable=development xen | wc -l Error: Missing Dependency: kdemultimedia3 >= 3.5.8 is needed by package kdemultimedia-extras-nonfree 844 [root@potoroo ~]# My idea of an ideal host for virtual machines is one that runs guests and precious little else, and certainly not a GUI and all the baggage that entails. Do these *xen* packages build on f8? What''s the easy way to get the source - I used to use up2date, but I fear the technolgogy''s getting ahead of me. -- John the Bewildered. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen
Dustin Henning wrote:> You could download and build the latest stable or test source from xen.org. This assumes you are familiar with that sort of thing, but if you want to test, you probably are... > Dustin >I''ve downloaded built and installed ian jackson''s xen 3.2 src.rpm from xen. I''ve downloaded, built and installed these: libvirt-0.4.0-4.fc9.src.rpm python-virtinst-0.300.2-2.fc9.src.rpm virt-manager-0.5.3-1.fc9.src.rpm virt-viewer-0.0.2-3.fc9.src.rpm xen-3.2.0-0xs.fc8.src.rpm I''m using this kernel: 2.6.21.7-2893.fc9xen When I try to start a guest that worked earlier: [root@potoroo ~]# virsh start DebianEtch libvir: Xen Daemon error : POST operation failed: (xend.err "long() argument must be a string or a number, not ''NoneType''") error: Failed to start domain DebianEtch [root@potoroo ~]# virsh version Compiled against library: libvir 0.4.0 Using library: libvir 0.4.0 Using API: Xen 3.0.1 Running hypervisor: Xen 3.2.0 [root@potoroo ~]# the obvious problem to my eyes is the API version, but of course the obvious isn''t always right. -- Cheers John -- spambait 1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-)
Daniel P. Berrange
2008-Jan-26 15:54 UTC
Re: [Fedora-xen] Upgrade to development xen on F8?
On Sat, Jan 26, 2008 at 09:17:32PM +0900, John Summerfield wrote:> Dustin Henning wrote: > > You could download and build the latest stable or test source from > > xen.org. This assumes you are familiar with that sort of thing, but > > if you want to test, you probably are... > > Dustin > > > > I''ve downloaded built and installed ian jackson''s xen 3.2 src.rpm from xen. > > I''ve downloaded, built and installed these: > libvirt-0.4.0-4.fc9.src.rpm > python-virtinst-0.300.2-2.fc9.src.rpm > virt-manager-0.5.3-1.fc9.src.rpm > virt-viewer-0.0.2-3.fc9.src.rpm > xen-3.2.0-0xs.fc8.src.rpm > > I''m using this kernel: > 2.6.21.7-2893.fc9xen > > When I try to start a guest that worked earlier: > > [root@potoroo ~]# virsh start DebianEtch > libvir: Xen Daemon error : POST operation failed: (xend.err "long() > argument must be a string or a number, not ''NoneType''") > error: Failed to start domain DebianEtchThis is a bug in Xen 3.2.0 http://xenbits.xensource.com/xen-3.2-testing.hg?rev/bf534df13095 Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
On Sun, 27 Jan 2008 12:54:27 am Daniel P. Berrange wrote:> > This is a bug in Xen 3.2.0 > > http://xenbits.xensource.com/xen-3.2-testing.hg?rev/bf534df13095Thanks for that, a little vim goes a long way. Now, my test system does not connect to the network; it starts, but it cannot obtain an IP address by dhcp. I have not yet tried manual configuuration. I added a second NIC with virt-manager. Here is the resultant XML: [root@potoroo ~]# virsh dumpxml DebianEtch <domain type=''xen'' id=''-1''> <name>DebianEtch</name> <uuid>deec1a9a-dea6-8de5-d6d0-79eb94be561c</uuid> <os> <type>hvm</type> <loader>/usr/lib/xen/boot/hvmloader</loader> <boot dev=''hd''/> </os> <memory>262144</memory> <vcpu>1</vcpu> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <features> <acpi/> <apic/> <pae/> </features> <clock offset=''utc''/> <devices> <emulator>/usr/lib64/xen/bin/qemu-dm</emulator> <interface type=''bridge''> <source bridge=''eth0''/> <target dev=''vif-1.0''/> <mac address=''00:16:3e:54:ba:6f''/> <script path=''vif-bridge''/> </interface> <interface type=''bridge''> <source bridge=''peth0 (Bridge eth0)''/> <target dev=''vif-1.1''/> <mac address=''00:16:3e:34:89:a2''/> </interface> <disk type=''file'' device=''disk''> <driver name=''file''/> <source file=''/var/lib/xen/images/DebianEtch.img''/> <target dev=''hda''/> </disk> <disk device=''cdrom''> <target dev=''hdc''/> <readonly/> </disk> <input type=''mouse'' bus=''ps2''/> <graphics type=''vnc'' port=''-1'' listen=''0.0.0.0''/> </devices> </domain> [root@potoroo ~]# [root@potoroo ~]# virsh start DebianEtch libvir: Xen Daemon error : POST operation failed: (xend.err ''Device 1 (vif) could not be connected. Could not find bridge device peth0 (Bridge eth0)'') error: Failed to start domain DebianEtch [root@potoroo ~]# This is selinux getting in the way (it does it all the time). (sealert popped up). or not: [root@potoroo ~]# setenforce 0 [root@potoroo ~]# virsh start DebianEtch libvir: Xen Daemon error : POST operation failed: (xend.err ''Device 1 (vif) could not be connected. Could not find bridge device peth0 (Bridge eth0)'') error: Failed to start domain DebianEtch [root@potoroo ~]# Here is the bridge information: [root@potoroo ~]# /usr/sbin/brctl show bridge name bridge id STP enabled interfaces eth0 8000.00187184a59e no peth0 virbr0 8000.000000000000 yes [root@potoroo ~]# /usr/sbin/brctl showmacs eth0 port no mac addr is local? ageing timer 1 00:0d:60:f0:ac:5c no 0.42 1 00:11:5b:e1:d8:5c no 0.42 1 00:11:d8:70:68:15 no 226.66 1 00:18:71:84:a5:9e yes 0.00 [root@potoroo ~]# /usr/sbin/brctl showmacs virbr0 port no mac addr is local? ageing timer [root@potoroo ~]# /usr/sbin/brctl showstp eth0 eth0 bridge id 8000.00187184a59e designated root 8000.00187184a59e root port 0 path cost 0 max age 19.99 bridge max age 19.99 hello time 1.99 bridge hello time 1.99 forward delay 0.00 bridge forward delay 0.00 ageing time 299.95 hello timer 0.28 tcn timer 0.00 topology change timer 0.00 gc timer 0.06 flags peth0 (0) port id 0000 state forwarding designated root 8000.00187184a59e path cost 19 designated bridge 8000.00187184a59e message age timer 0.00 designated port 8001 forward delay timer 0.00 designated cost 0 hold timer 0.00 flags [root@potoroo ~]# /usr/sbin/brctl showstp virbr0 virbr0 bridge id 8000.000000000000 designated root 8000.000000000000 root port 0 path cost 0 max age 19.99 bridge max age 19.99 hello time 1.99 bridge hello time 1.99 forward delay 14.99 bridge forward delay 14.99 ageing time 299.95 hello timer 0.93 tcn timer 0.00 topology change timer 0.00 gc timer 0.03 flags [root@potoroo ~]# and xend''s log: [2008-01-27 08:48:54 2815] INFO (image:139) buildDomain os=hvm dom=4 vcpus=1 [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vkbd : {''devid'': 0, ''uuid'': ''82b7a0a0-c238-98d8-36cd-96901eb712d1''} [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vfb : {''vncunused'': ''1'', ''vnclisten'': ''0.0.0.0'', ''uuid'': ''26d3bc94-7b41-186d-da60-6b4734407ccd'', ''devid'': 0, ''other_config'': {''vncunused'': ''1'', ''vnclisten'': ''0.0.0.0'', ''type'': ''vnc''}, ''location'': ''0.0.0.0:5901'', ''type'': ''vnc''} [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: console : {''location'': ''3'', ''devid'': 0, ''protocol'': ''vt100'', ''uuid'': ''0ea8b31a-4693-515a-a3d0-acb6fe4cef79'', ''other_config'': {}} [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vbd : {''uuid'': ''78d21254-b846-a9d4-f2eb-84b6ccddaf9d'', ''bootable'': 1, ''devid'': 768, ''driver'': ''paravirtualised'', ''dev'': ''hda:disk'', ''uname'': ''file:/var/lib/xen/images/DebianEtch.img'', ''mode'': ''w''} [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vbd : {''uuid'': ''08faae4e-1f81-e81a-ef71-8658ba92f163'', ''bootable'': 0, ''devid'': 5632, ''driver'': ''paravirtualised'', ''dev'': ''hdc:cdrom'', ''mode'': ''r''} [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vif : {''bridge'': ''eth0'', ''mac'': ''00:16:3e:54:ba:6f'', ''devid'': 0, ''uuid'': ''51cc67dd-753a-ef22-5e79-b0c021fa0b2e'', ''script'': ''vif-bridge''} [2008-01-27 08:48:54 2815] INFO (XendDomainInfo:1504) createDevice: vif : {''bridge'': ''peth0 (Bridge eth0)'', ''mac'': ''00:16:3e:34:89:a2'', ''devid'': 1, ''uuid'': ''cc27aac1-7f80-990d-4325-1d151101790e''} [2008-01-27 08:48:54 2815] INFO (image:283) spawning device models: /usr/lib64/xen/bin/qemu-dm [''/usr/lib64/xen/bin/qemu-dm'', ''-d'', ''4'', ''-domain-name'', ''DebianEtch'', ''-vnc'', ''0.0.0.0:0'', ''-vncunused'', ''-vcpus'', ''1'', ''-boot'', ''c'', ''-acpi'', ''-usb'', ''-net'', ''nic,vlan=1,macaddr=00:16:3e:54:ba:6f,model=rtl8139'', ''-net'', ''tap,vlan=1,bridge=eth0'', ''-net'', ''nic,vlan=2,macaddr=00:16:3e:34:89:a2,model=rtl8139'', ''-net'', ''tap,vlan=2,bridge=peth0 (Bridge eth0)'', ''-M'', ''xenfv''] [2008-01-27 08:48:54 2815] INFO (image:287) device model pid: 23649 [2008-01-27 08:48:56 2815] WARNING (XendDomain:1035) Failed to setup devices for <domain id=4 name=DebianEtch memory=268435456 state=paused>: Device 1 (vif) could not be connected. Could not find bridge device peth0 (Bridge eth0) [2008-01-27 08:48:57 2815] ERROR (SrvBase:88) Request start failed. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/SrvBase.py", line 85, in perform return op_method(op, req) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomain.py", line 77, in op_start return self.xd.domain_start(self.dom.getName(), paused) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 1033, in domain_start dominfo.waitForDevices() File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 581, in waitForDevices self.getDeviceController(devclass).waitForDevices() File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevController.py", line 151, in waitForDevices return map(self.waitForDevice, self.deviceIDs()) File "/usr/lib64/python2.5/site-packages/xen/xend/server/DevController.py", line 176, in waitForDevice "%s" % (devid, self.deviceClass, err)) VmError: Device 1 (vif) could not be connected. Could not find bridge device peth0 (Bridge eth0) [root@potoroo ~]#