From jklein at saugus.k12.ca.us Fri Jun 1 21:20:00 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Fri, 1 Jun 2007 14:20:00 -0700 (PDT) Subject: [Fedora-xen] F7 and xenstore Message-ID: <8988542.1219371180732800700.JavaMail.root@do8> Is all the configuration for domu's now in xenstore? If so, then is there an easier way to manage it than the xenstore commands? /var/lib/xend/domains appears to contain config files, listed by uuid, but changes are ignored. What are the steps to edit a domain's configuration? Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri Jun 1 21:30:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 1 Jun 2007 22:30:24 +0100 Subject: [Fedora-xen] F7 and xenstore In-Reply-To: <8988542.1219371180732800700.JavaMail.root@do8> References: <8988542.1219371180732800700.JavaMail.root@do8> Message-ID: <20070601213024.GL6071@redhat.com> On Fri, Jun 01, 2007 at 02:20:00PM -0700, Jim Klein wrote: > Is all the configuration for domu's now in xenstore? If so, then is > there an easier way to manage it than the xenstore commands? > /var/lib/xend/domains appears to contain config files, listed by uuid, > but changes are ignored. What are the steps to edit a domain's > configuration? Thanks in advance. No, they're no kept in xenstore. The /var/lib/xend/domains directory is the location XenD uses for persistent storage of guest domain configs. It is in /var because it is not user editable - changes you make there will be ignored and/or overwritten by XenD at will. Not ideal, but that's just what upstream Xen decided to do... Thus we recommend using libvirt's virsh command for changing the config 1. Get dump of the existing config virsh dumpxml [guest name] > guest.xml 2. Edit it in vi/emacs vi guest.xml 3. Feed it back into Xend virsh define guest.xml For a description of various XML elements/attributes that are allowed in the config there is: http://libvirt.org/format.html Or if you are really feeling adventurous a Relax-NG schema http://libvirt.org/libvirt.rng Finally, virt-manager has some slightly increased capabilities for changing existing guests configs. You can use it to add/remove both disk and network devices - as well as previous UI for memory/max-memory & vcpus Regards, 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 -=| From jklein at saugus.k12.ca.us Fri Jun 1 21:35:06 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Fri, 1 Jun 2007 14:35:06 -0700 (PDT) Subject: [Fedora-xen] F7 and xenstore In-Reply-To: <20070601213024.GL6071@redhat.com> Message-ID: <23115681.1221621180733706973.JavaMail.root@do8> Ick. Thanks for your help! ----- Original Message ----- From: "Daniel P. Berrange" To: "Jim Klein" Cc: "fedora-xen" Sent: Friday, June 1, 2007 2:30:24 PM (GMT-0800) America/Los_Angeles Subject: Re: [Fedora-xen] F7 and xenstore On Fri, Jun 01, 2007 at 02:20:00PM -0700, Jim Klein wrote: > Is all the configuration for domu's now in xenstore? If so, then is > there an easier way to manage it than the xenstore commands? > /var/lib/xend/domains appears to contain config files, listed by uuid, > but changes are ignored. What are the steps to edit a domain's > configuration? Thanks in advance. No, they're no kept in xenstore. The /var/lib/xend/domains directory is the location XenD uses for persistent storage of guest domain configs. It is in /var because it is not user editable - changes you make there will be ignored and/or overwritten by XenD at will. Not ideal, but that's just what upstream Xen decided to do... Thus we recommend using libvirt's virsh command for changing the config 1. Get dump of the existing config virsh dumpxml [guest name] > guest.xml 2. Edit it in vi/emacs vi guest.xml 3. Feed it back into Xend virsh define guest.xml For a description of various XML elements/attributes that are allowed in the config there is: http://libvirt.org/format.html Or if you are really feeling adventurous a Relax-NG schema http://libvirt.org/libvirt.rng Finally, virt-manager has some slightly increased capabilities for changing existing guests configs. You can use it to add/remove both disk and network devices - as well as previous UI for memory/max-memory & vcpus Regards, 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 -=| -------------- next part -------------- An HTML attachment was scrubbed... URL: From poncho_vc at yahoo.com Fri Jun 1 22:45:11 2007 From: poncho_vc at yahoo.com (poncho valdes) Date: Fri, 1 Jun 2007 17:45:11 -0500 (CDT) Subject: [Fedora-xen] my guest(domU) doesnt boot up succesfully- Kernel panic: - not syncing: attempted to kill init! Message-ID: <442830.94219.qm@web61113.mail.yahoo.com> Hello list!. I hope somebody could help me, i will really apreciate. I dont know why, i made my first guest with virt-manager with rhel5, then i installed the guest, but when it boots , it stops in.. KERNEL PANIc. ........... 120. NET: Registered protocol family 1 121. NET: Registered protocol family 17 122. Using IPI No-Shortcut mode 123. XENBUS: Device with no driver: device/vbd/51712 124. XENBUS: Device with no driver: device/vif/0 125. Freeing unused kernel memory: 172k freed 126. Write protecting the kernel read-only data: 355k 127. USB Universal Host Controller Interface driver v3.0 128. SCSI subsystem initialized 129. device-mapper: ioctl: 4.11.0-ioctl (2006-09-14) initialised: dm-devel at redhat.com 130. Kernel panic - not syncing: Attempted to kill init! 131. [root at localhost images]# vim /etc/xen/rhel5 ..............END. - Somebody told me that im using the kernel and the initrd of the HOST (dom0) but i dont know where xen created the xen kernel for my domU's... - Here is my conf file of the guest (rhel5) # [root at localhost images]# cat /etc/xen/rhel5 # # Automatically generated xen config file # kernel = "/boot/vmlinuz-2.6.18-8.el5xen" # ramdisk ="/boot/initrd-2.6.18-8.el5xen.img" # name = "rhel5" # memory = "500" # disk = [ 'tap:aio:/var/lib/xen/images/rhel5Zim.img,xvda,w', ] # vif = [ 'mac=00:16:3e:18:bb:81, bridge=xenbr0', ] # vfb = ["type=vnc,vncunused=1"] # uuid = "ebed3188-3ef4-6e19-2973-590ff581f6fc" # #bootloader="/usr/bin/pygrub" # vcpus=1 # on_reboot = 'restart' # on_crash = 'restart' # extra = "console=tty1" ---------------end conf file---------- This is my partition [root at localhost domU]# df -h S.ficheros Tama?o Usado Disp Uso% Montado en /dev/mapper/ 31G 10G 20G 34% / /dev/sda1 99M 19M 75M 20% /boot tmpfs 501M 0 501M 0% /dev/shm in the logical volumen is where i have my image.img file that stores the VM files. - In the image.img has two partitions the first one is ext3, and the second one is LVM. THe last one, im getting troubles to mount it, cuz is LVM. I dont know what else am i missing ... to help me out to Fix this problme at bootin' time... Thanks in advancee! __________________________________________________ Correo Yahoo! Espacio para todos tus mensajes, antivirus y antispam ?gratis! Reg?strate ya - http://correo.espanol.yahoo.com/ From paul at xelerance.com Sat Jun 2 04:22:51 2007 From: paul at xelerance.com (Paul Wouters) Date: Sat, 2 Jun 2007 00:22:51 -0400 (EDT) Subject: [Fedora-xen] my guest(domU) doesnt boot up succesfully- Kernel panic: - not syncing: attempted to kill init! In-Reply-To: <442830.94219.qm@web61113.mail.yahoo.com> References: <442830.94219.qm@web61113.mail.yahoo.com> Message-ID: On Fri, 1 Jun 2007, poncho valdes wrote: > - Somebody told me that im using the kernel and the > initrd of the HOST (dom0) but i dont know where xen > created the xen kernel for my domU's... > - Here is my conf file of the guest (rhel5) http://www.mail-archive.com/fedora-xen at redhat.com/msg00676.html Paul From hangil at smu.ac.kr Mon Jun 4 06:16:52 2007 From: hangil at smu.ac.kr (=?ks_c_5601-1987?B?wPy788DP?=) Date: Mon, 4 Jun 2007 15:16:52 +0900 Subject: [Fedora-xen] Why I can't save and restore domU. In-Reply-To: <87iraa0y38.fsf@pike.pond.sub.org> References: <20070530093209.aspuriak.0000001305@smu.ac.kr> <87iraa0y38.fsf@pike.pond.sub.org> Message-ID: <002d01c7a66f$f1e7cef0$d5b76cd0$@ac.kr> >> I successed save/restore and migrate the virtual machine of gui. >Do you mean that migration worked, but the framebuffer didn't come up >correctly? Migration and save/restore worked. >Again: what does migration write to your dom0's /var/log/xen/? Attach >> But, the domU is not fedora core 6 but fedora 7(rc2). >> Someone said me that fedora core 6 is support old framebuffer. >> So, He guess that this situation appeared. >> I think that fedora 7 is support framebuffer more perfectly. >If it's broken in FC-6, it needs fixing. >> In fack, I'm not fix setting files at the success case. >Err, you lost me there. -------------- next part -------------- A non-text attachment was scrubbed... Name: xend.log Type: application/octet-stream Size: 46959 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xend-debug.log Type: application/octet-stream Size: 5070 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xen-hotplug.log Type: application/octet-stream Size: 72 bytes Desc: not available URL: From thomas.vonsteiger at bluewin.ch Mon Jun 4 22:28:37 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Tue, 5 Jun 2007 00:28:37 +0200 Subject: [Fedora-xen] automated disksetup after kickstart installation for xenguest ?? Message-ID: <001301c7a6f7$b1ad3540$3201a8c0@athlon> Hello, I have tested howto auto setup a xenguest after the kickstart job. For this i start a first script in /etc/rc.local when the xen guest makes the first boot. Special point howto make additional filesystems on additional xen guest disks. As disk's (xvd devices) we use dom0 lv's for xenguest. Dom0 is RHEL5 and domU RHEL4U5 para. I found several points about this: - using "sfdisk" to make the guest partition on xvdb. To write a partition table with sfdisk we need first the disk geometrie for calculation of the disksize. With "sfdisk -g /dev/xvdb" I get message "Disk /dev/xvdb: cannot get geometry". -> nok - using "parted", i'm able to write the partition table to /dev/xvdb. -> ok After this "partprobe" should reload partition table in the kernel. --> nok The problem, partprobe don't reload partition created with parted. The only way is to reboot again the guest. Because this is not practical for automated server setup. - to only way for now is to use /dev/xvdb without partition, direct "pvcreate /dev/xvdb". If dom0 reboots or vgscan is running on dom0, i found in dom0 all the vg's and lv's on disk's without partitions from the xen guest's. So I can vgchange -a y "xenguest vg" on dom0 and mount this lv because this lv is online in his xen guest. Maybe this is a feature to backup xenguests or a bug to corrupt filesystems if there is a wrong handling. I have not tested what happens if i have 10 xen guest's and each xenguest has a vg with the same name. Manual i can always use fdisk and partprobe to create vg,lv's and fs without reboot. xvd devices with a partition can not be detected from dom0. Has anybody tested similar setup's ? Should i open bugzilla's for this 3 points ? Many Tanks, Thomas No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.472 / Virus Database: 269.8.7/830 - Release Date: 03.06.2007 12:47 From adhikarexuss at gmail.com Tue Jun 5 13:23:59 2007 From: adhikarexuss at gmail.com (Adhika Widjaya) Date: Tue, 5 Jun 2007 20:23:59 +0700 Subject: [Fedora-xen] Laptop hang on kernel-xen-2.6.20-1.2948.fc6 Message-ID: Hi, Thank you Eduardo, I manage to install the kernel-xen-2.6.20-1.2952.fc6 and I also made it to install SLES10 in there. but the problem happened when I tried to install windows XP. the same thing happened again, it hangs. anybody know how to install win XP in xen? thank you, Adhika > Date: Mon, 28 May 2007 14:05:34 -0300 > From: Eduardo Habkost > Subject: Re: [Fedora-xen] Laptop hang on kernel-xen-2.6.20-1.2948.fc6 > To: Adhika Widjaya > Cc: fedora-xen at redhat.com > Message-ID: <20070528170534.GG3908 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > On Sun, May 27, 2007 at 11:31:30PM +0700, Adhika Widjaya wrote: > > Hi guys, > > > > I'm experiencing weird stuff when using kernel-xen-2.6.20-1.2948.fc6. > > I'm about to install SLED10 on top of my fc6. In the middle of > > installation, my laptop hangs and what I did is press the power button > > for 4 seconds. > > second time is getting worse, after I turned on the virtual-manager > > and I tried to navigate anywhere in the screen, my laptop hangs again. > > > > kernel-xen 2.6.20 (including 2.6.20-1.2948) has instability problems[1] that > were fixed on 2.6.20-1.2952, that is on FC6 updatest-testing repository. > > Could you test using kernel-xen-2.6.20-1.2952.fc6? > > > [1] https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234008 > > -- > Eduardo -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.reiter at gmx.net Tue Jun 5 16:58:31 2007 From: c.reiter at gmx.net (Christian Reiter) Date: Tue, 5 Jun 2007 18:58:31 +0200 Subject: [Fedora-xen] How is network bridging for Xen handled in F7? Message-ID: Hi! Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. All what i want is: xenbrINTERNET should bridge to eth1 xenbrLAN should bridge to eth0 eth0 and eth1 of my dom0 should also have an IP Address. I do not want routing or nat for my domUs. Thanks! regards, christian From berrange at redhat.com Tue Jun 5 17:23:57 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 5 Jun 2007 18:23:57 +0100 Subject: [Fedora-xen] How is network bridging for Xen handled in F7? In-Reply-To: References: Message-ID: <20070605172357.GI15012@redhat.com> On Tue, Jun 05, 2007 at 06:58:31PM +0200, Christian Reiter wrote: > Hi! > > > Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? > > Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. Previously there was a xen module called 'netloop' in use. So if you used network-bridge, you'd get 4 interfaces peth0 - physical device xenbr0 - bridge device vif0.0 - backend of virtual device eth0 - frontend of virtual device peth0 & vif0.0 would be part of xenbr0 In F7, use of netloop is removed to simplify dom0 config so you only get two interfaces peth0 - physical device eth0 - bridge device And peth0 is part of the eth0 bridge. In both cases, eth0 wouldbe the device that gets the IP addr. > All what i want is: > xenbrINTERNET should bridge to eth1 > xenbrLAN should bridge to eth0 Calling the bridge xenbrXXXX is deprecated, since we're moving towards a Dom0 config which is able to be the same for both Xen and KVM. Hence we have the generic peth0 & eth0 devices now. That's a minor naming detail though. You should be able to call network-bridge multiple times - once per device you have, just as with Fc6. Alternatively setup briding using the regular init scripts as per section 2 in this doc http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt 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 -=| From berrange at redhat.com Tue Jun 5 17:29:10 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 5 Jun 2007 18:29:10 +0100 Subject: [Fedora-xen] How is network bridging for Xen handled in F7? In-Reply-To: <20070605172357.GI15012@redhat.com> References: <20070605172357.GI15012@redhat.com> Message-ID: <20070605172910.GK15012@redhat.com> On Tue, Jun 05, 2007 at 06:23:57PM +0100, Daniel P. Berrange wrote: > On Tue, Jun 05, 2007 at 06:58:31PM +0200, Christian Reiter wrote: > > Hi! > > > > > > Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? > > > > Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. > > Previously there was a xen module called 'netloop' in use. So if you used > network-bridge, you'd get 4 interfaces > > peth0 - physical device > xenbr0 - bridge device > vif0.0 - backend of virtual device > eth0 - frontend of virtual device > > peth0 & vif0.0 would be part of xenbr0 > > > In F7, use of netloop is removed to simplify dom0 config so you only get > two interfaces > > peth0 - physical device > eth0 - bridge device > > And peth0 is part of the eth0 bridge. Oh btw, before anyone asks - we added compatability code to vif-bridge, so if you have any existing guest config files which refer to 'xenbr0' they will automatically join the eth0 bridge device instead. So existing guests are supposed to 'just work' even though the Dom0 network config changed a little. 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 -=| From c.reiter at gmx.net Tue Jun 5 17:42:27 2007 From: c.reiter at gmx.net (Christian Reiter) Date: Tue, 5 Jun 2007 19:42:27 +0200 Subject: [Fedora-xen] How is network bridging for Xen handled in =?UTF-8?B?Rjc/?= In-Reply-To: <20070605172357.GI15012@redhat.com> References: <20070605172357.GI15012@redhat.com> Message-ID: <1ffd8f56bf3fdb25b9b88764dfd314ed@10.0.0.254> Thanks Dan! I'll try as soon as i'm back in the Office and report here. christian From brian at brie.com Tue Jun 5 17:56:00 2007 From: brian at brie.com (Brian Lavender) Date: Tue, 5 Jun 2007 10:56:00 -0700 Subject: [Fedora-xen] How to migrate a QEMU VM to Xen? In-Reply-To: References: Message-ID: <20070605175600.GA17966@brie.com> On Mon, May 28, 2007 at 08:39:49AM -0400, Thomas Kocourek wrote: > I have been using QEMU for some time and the virtual machine works very > well. Is there a way to copy over the virtual machine from QEMU to XEN? I was just thinking about this. Did anyone give details? Seems like you ought to be able to create a config file, put a Xen kernel in, and be good to go. I am about to try it, but I thought I would ask if you had success, so I could avoid the similar mistakes. apt-get install xen-linux-system-2.6.18-4-xen-686 Oops, I just used the Debian way. This is a Fedora list. Let's just pretend you want a Debian image then. yum install kernel-xen.i686 and then create a config file for the image, similar to this howto. http://wiki.rpath.com/wiki/Xen_DomU_Guide I'll give it a shot and see if it works! brian -- Brian Lavender http://www.brie.com/brian/ From brian at brie.com Tue Jun 5 21:01:26 2007 From: brian at brie.com (Brian Lavender) Date: Tue, 5 Jun 2007 14:01:26 -0700 Subject: [Fedora-xen] How to migrate a QEMU VM to Xen? In-Reply-To: <20070605175600.GA17966@brie.com> References: <20070605175600.GA17966@brie.com> Message-ID: <20070605210126.GB17966@brie.com> On Tue, Jun 05, 2007 at 10:56:00AM -0700, Brian Lavender wrote: > On Mon, May 28, 2007 at 08:39:49AM -0400, Thomas Kocourek wrote: > > I have been using QEMU for some time and the virtual machine works very > > well. Is there a way to copy over the virtual machine from QEMU to XEN? > > I was just thinking about this. Did anyone give details? Seems like you > ought to be able to create a config file, put a Xen kernel in, and be > good to go. I am about to try it, but I thought I would ask if you had > success, so I could avoid the similar mistakes. > > apt-get install xen-linux-system-2.6.18-4-xen-686 > > Oops, I just used the Debian way. This is a Fedora list. Let's just > pretend you want a Debian image then. > > yum install kernel-xen.i686 > > and then create a config file for the image, similar to this howto. > > http://wiki.rpath.com/wiki/Xen_DomU_Guide > > I'll give it a shot and see if it works! I created the machine using QEMU using a raw file system and it booted in Xen, but I am not getting networking to come up. I don't see a networking device. How do I get networking to appear? [root at localhost xen]# xm create -c debian Using config file "./debian". WARNING:root:Unknown image directive savedefault WARNING:root:Unknown image directive savedefault WARNING:root:Unknown image directive savedefault Going to boot Debian GNU/Linux, kernel 2.6.18-4-xen-686 kernel: /boot/vmlinuz-2.6.18-4-xen-686 initrd: /boot/initrd.img-2.6.18-4-xen-686 Started domain debian Linux version 2.6.18-4-xen-686 (Debian 2.6.18.dfsg.1-12etch2) (dannf at debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu May 10 03:24:35 UTC 2007 After my Debian VM boots, I get this kernel message. debian:/lib/modules/2.6.18-4-xen-686# dmesg | grep eth netfront: Initialising virtual ethernet driver. netfront: device eth0 has flipping receive path. Here is my xen config file {{{ # Automatically generated xen config file name = "debian" memory = "512" disk = [ 'tap:aio:/var/lib/xen/images/debian2.img,hda,w', ] vif = [ 'mac=00:16:3e:5c:87:5f, bridge=xenbr0', ] uuid = "fc23be35-40d8-4fc4-8708-5f6ffb3f5e66" bootloader="/usr/bin/pygrub" vcpus=1 on_reboot = 'restart' on_crash = 'restart' }}} And the process I used to build the image using QEMU. {{{ qemu-img create -f raw debian.img 5G qemu -cdrom ../../iso/debian-40r0-i386-netinst.iso -hda debian.img -m 256 -boot d qemu -hda debian.img -m 384 }}} -- Brian Lavender http://www.brie.com/brian/ From tom.horsley at att.net Tue Jun 5 22:01:17 2007 From: tom.horsley at att.net (Tom Horsley) Date: Tue, 5 Jun 2007 18:01:17 -0400 Subject: [Fedora-xen] Fedora 7 bug? Message-ID: <20070605180117.204ae4f9@zooty> Here's the problem: Everything is x86_64, a Fedora 6 Dom0, and I tried to install Fedora 7 as a fully virtual HVM using the DVD iso image and the New button in the virt-manager: The installer that it doesn't have a driver for the CDROM and offers to let me do some other kind of install (I mounted the iso under /var/www/html and did a HTTP install and that worked). Is the kernel on the F7 DVD missing the driver for the kind of emulated dvd-rom that Xen provides? Should I report a bug? If so, what component should I report it against? From armbru at redhat.com Tue Jun 5 22:06:03 2007 From: armbru at redhat.com (Markus Armbruster) Date: Wed, 06 Jun 2007 00:06:03 +0200 Subject: [Fedora-xen] Why I can't save and restore domU. In-Reply-To: <002d01c7a66f$f1e7cef0$d5b76cd0$@ac.kr> (hangil@smu.ac.kr's message of "Mon, 4 Jun 2007 15:16:52 +0900") References: <20070530093209.aspuriak.0000001305@smu.ac.kr> <87iraa0y38.fsf@pike.pond.sub.org> <002d01c7a66f$f1e7cef0$d5b76cd0$@ac.kr> Message-ID: <87ejkqvyyc.fsf@pike.pond.sub.org> ?????? writes: >>> I successed save/restore and migrate the virtual machine of gui. > >>Do you mean that migration worked, but the framebuffer didn't come up >>correctly? > > Migration and save/restore worked. > >>Again: what does migration write to your dom0's /var/log/xen/? > > Attach [...] Your logs show more than just the save/restore, which makes it a bit difficult to find the relevant bits. I believe you saved domid 3, and it became domid 4 on restore. Output of xenstore-ls before save and after restore? Any xen-vncfb processes running before save and after restore? From brian at brie.com Tue Jun 5 23:29:57 2007 From: brian at brie.com (Brian Lavender) Date: Tue, 5 Jun 2007 16:29:57 -0700 Subject: [Fedora-xen] How to create a Debian VM? Message-ID: <20070605232956.GC17966@brie.com> My adventure creating a Debian VM on Fedora hit a snag. Is there another way to do a Debian VM on Fedora? brian -- Brian Lavender http://www.brie.com/brian/ From jtower at gmail.com Wed Jun 6 04:37:26 2007 From: jtower at gmail.com (Jason Tower) Date: Wed, 6 Jun 2007 00:37:26 -0400 Subject: [Fedora-xen] How to create a Debian VM? In-Reply-To: <20070605232956.GC17966@brie.com> References: <20070605232956.GC17966@brie.com> Message-ID: i have an ubuntu LTS domU that i can send you, works great on my fc5 dom0. it was created on a ubuntu system using debootstrap, installing into a loopback mounted file which i then copied to the xen server. be glad to send it to you if you want, it's only about 200mb compressed. On 6/5/07, Brian Lavender wrote: > My adventure creating a Debian VM on Fedora hit a snag. Is there another > way to do a Debian VM on Fedora? > > brian > -- > Brian Lavender > http://www.brie.com/brian/ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From jlagrue at gmail.com Wed Jun 6 09:25:27 2007 From: jlagrue at gmail.com (John Lagrue) Date: Wed, 6 Jun 2007 10:25:27 +0100 Subject: [Fedora-xen] Fedora 7 virtual machine problems Message-ID: I have at least two problems running a virtual machine on F7 1. When I run qemu from the command line I can create a virtual disk, run a virtual machine and install Windows XP on it. I can do this because it enables me to define the cdrom on the command line with "-cdrom /dev/cdrom". But I can't get any further because it keeps giving me an error saying "A problem is preventing Windows from accurately checking the license for this computer" If I run the same virtual machine from the virtual machine manager I don't get that error. But I don't get the CD ROM either 2. The above was obtained with QEMU. If I try to connect the Virtual Machine Manager to XEN I get an error that tells me that either I'm not running a XEN-enabled kernel, or the XEN service isn't running. Unfortunately, it is running! Any advice from anyone on either of these? I would love to do away with dual-booting my laptop and just run Vista in a VM when I need it, but so far I'm not having a lot of luck. JDL From berrange at redhat.com Wed Jun 6 13:29:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 6 Jun 2007 14:29:24 +0100 Subject: [Fedora-xen] Fedora 7 virtual machine problems In-Reply-To: References: Message-ID: <20070606132922.GA18020@redhat.com> On Wed, Jun 06, 2007 at 10:25:27AM +0100, John Lagrue wrote: > I have at least two problems running a virtual machine on F7 > > 1. When I run qemu from the command line I can create a virtual > disk, run a virtual machine and install Windows XP on it. I can do > this because it enables me to define the cdrom on the command line > with "-cdrom /dev/cdrom". But I can't get any further because it keeps > giving me an error saying "A problem is preventing Windows from > accurately checking the license for this computer" > > If I run the same virtual machine from the virtual machine manager I > don't get that error. But I don't get the CD ROM either Huh ? The new virtual machine wizard *requires* that you provide a ISO image or CDROM device to do a fullyvirtualized install in QEMU. I'm not sure how you'd create a QEMU vm without getting a CDROM ? > 2. The above was obtained with QEMU. If I try to connect the Virtual > Machine Manager to XEN I get an error that tells me that either I'm > not running a XEN-enabled kernel, or the XEN service isn't running. > Unfortunately, it is running! Check /root/.virt-manager/virt-manager.log for further details ? Also does virsh list work ? 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 -=| From nooroon at gmail.com Wed Jun 6 16:07:45 2007 From: nooroon at gmail.com (mathieu rohon) Date: Wed, 6 Jun 2007 18:07:45 +0200 Subject: [Fedora-xen] virt-manager and guest config file Message-ID: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> Hi, I've created a Windows XP guest on FC7 using xen 3.1 and virt-manager. the installation has been successful thanks to red-hat explanation found here : https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf but this installation guide is talking about the guest config file "winxp" placed in /etc/xen. It seems that building a guest with virt-manager doesn't create a config file. How can I forced virt-manager to generate a config file for my guest? -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.mcdonald at mcdees-specialties.com Wed Jun 6 16:08:24 2007 From: brian.mcdonald at mcdees-specialties.com (Brian McDonald) Date: Wed, 6 Jun 2007 12:08:24 -0400 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU Message-ID: <010601c7a854$e9adcff0$0201a8c0@Dell9200> I am having problems getting a fedora7 domu running under my Centos5 Dom0 (this is a centos5 server no graphical interface) I followed the same steps to created the fedora 7 domu as I have for creating the cenots5 domu that I have on the same box. I downloaded the vmlinux and initrd from here ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ images/xen/ Xm config: kernel = "/boot/vmlinuz-f7xeninstall" ramdisk = "/boot/initrd-f7xeninstall" extra = "text ks=http://www.mcdees-specialties.com/fed7/minimal-ks.cf" name = "fed7" memory = "230" disk = [ 'tap:aio:/var/lib/xen/images/fed7.img,xvda,w', ] #vif = [ '', ] vif = [ 'bridge=xenbr0', ] ip = "192.168.1.202" netmask = "255.255.255.0" gateway = "192.168.1.1" vcpus=1 on_reboot = 'destroy' on_crash = 'destroy' When I run xm create -c fed7inst it gets to here and stops ..................................... Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k Any and all ideas are welcome From berrange at redhat.com Wed Jun 6 16:11:16 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 6 Jun 2007 17:11:16 +0100 Subject: [Fedora-xen] virt-manager and guest config file In-Reply-To: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> References: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> Message-ID: <20070606161116.GJ18020@redhat.com> On Wed, Jun 06, 2007 at 06:07:45PM +0200, mathieu rohon wrote: > Hi, > > I've created a Windows XP guest on FC7 using xen 3.1 and virt-manager. > the installation has been successful thanks to red-hat explanation found > here : > https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf > > but this installation guide is talking about the guest config file "winxp" > placed in /etc/xen. > It seems that building a guest with virt-manager doesn't create a config > file. In Fedora 7 / Xen 3.1.0 config files no longer live in /etc/xen. They are managed internally by XenD itself so we have no direct access to them any longer. XenD will store them in /var/lib/xend/domains, but you can't edit those directly or your changes will be ignored/overwritten by XenD. 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 -=| From nooroon at gmail.com Wed Jun 6 16:19:39 2007 From: nooroon at gmail.com (mathieu rohon) Date: Wed, 6 Jun 2007 18:19:39 +0200 Subject: [Fedora-xen] virt-manager and guest config file In-Reply-To: <20070606161116.GJ18020@redhat.com> References: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> <20070606161116.GJ18020@redhat.com> Message-ID: <7675761b0706060919j2c5c3e78y5c44b9c55f712fbf@mail.gmail.com> Great, thanks for your answer Daniel. So the following logical question is : How can I modify my guests parameters? let's say, add usb support for example? More generally, can you tell me where this is documented? thanks 2007/6/6, Daniel P. Berrange : > > On Wed, Jun 06, 2007 at 06:07:45PM +0200, mathieu rohon wrote: > > Hi, > > > > I've created a Windows XP guest on FC7 using xen 3.1 and virt-manager. > > the installation has been successful thanks to red-hat explanation found > > here : > > > https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf > > > > but this installation guide is talking about the guest config file > "winxp" > > placed in /etc/xen. > > It seems that building a guest with virt-manager doesn't create a config > > file. > > In Fedora 7 / Xen 3.1.0 config files no longer live in /etc/xen. They > are managed internally by XenD itself so we have no direct access to > them any longer. XenD will store them in /var/lib/xend/domains, but you > can't edit those directly or your changes will be ignored/overwritten > by XenD. > > 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 -=| > -------------- next part -------------- An HTML attachment was scrubbed... URL: From c.reiter at gmx.net Wed Jun 6 16:27:24 2007 From: c.reiter at gmx.net (Christian Reiter) Date: Wed, 06 Jun 2007 18:27:24 +0200 Subject: [Fedora-xen] How is network bridging for Xen handled in F7? In-Reply-To: <20070605172910.GK15012@redhat.com> References: <20070605172357.GI15012@redhat.com> <20070605172910.GK15012@redhat.com> Message-ID: <4666E06C.8000305@gmx.net> Thanks Daniel, that worked perfect! One further Question: Is there any way to get rid of the virbr0 Interface? I've already deleted in the virt-manager GUI. chris Mit freundlichen Gr??en, /// Kind Regards, Christian Reiter -- Christian Reiter ||| c.reiter at gmx.net -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2840 bytes Desc: S/MIME Cryptographic Signature URL: From berrange at redhat.com Wed Jun 6 16:30:03 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 6 Jun 2007 17:30:03 +0100 Subject: [Fedora-xen] How is network bridging for Xen handled in F7? In-Reply-To: <4666E06C.8000305@gmx.net> References: <20070605172357.GI15012@redhat.com> <20070605172910.GK15012@redhat.com> <4666E06C.8000305@gmx.net> Message-ID: <20070606163003.GK18020@redhat.com> On Wed, Jun 06, 2007 at 06:27:24PM +0200, Christian Reiter wrote: > Thanks Daniel, that worked perfect! > > One further Question: > Is there any way to get rid of the virbr0 Interface? This is the libvirt provided virtual network, connected using NAT, so you can use the virt-manager UI to stop/start the network. Or from the command line you can: virsh net-destroy default And to make that permanent virsh net-autostart --disable default 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 -=| From tom.horsley at att.net Wed Jun 6 16:41:59 2007 From: tom.horsley at att.net (Tom Horsley) Date: Wed, 06 Jun 2007 16:41:59 +0000 Subject: [Fedora-xen] fedora 7 guest problems under fedora 6 host Message-ID: <060620071641.6364.4666E3D6000E3B96000018DC2160280748970A049C9D0108D203019B@att.net> I've been trying to install fedora 7 i386 as a guest using a fedora 6 x86_64 host (opteron). If I do a fully virtual HVM install, I always encounter this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237895 really early in the install, so it doesn't get very far. If I try to do a paravirt install from the fedora 7 DVD image (mounted under apache to be accessible on the network), the virt-manager app crashes as soon as it is about to start the install. Anyone have any tips for a successful f7 i386 install under an f6 dom0? From armbru at redhat.com Wed Jun 6 17:04:20 2007 From: armbru at redhat.com (Markus Armbruster) Date: Wed, 06 Jun 2007 19:04:20 +0200 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <010601c7a854$e9adcff0$0201a8c0@Dell9200> (Brian McDonald's message of "Wed, 6 Jun 2007 12:08:24 -0400") References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> Message-ID: <87myzdui97.fsf@pike.pond.sub.org> "Brian McDonald" writes: > I am having problems getting a fedora7 domu running under my Centos5 Dom0 > (this is a centos5 server no graphical interface) > > I followed the same steps to created the fedora 7 domu as I have for > creating the cenots5 domu that I have on the same box. > > I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/ > > Xm config: > > kernel = "/boot/vmlinuz-f7xeninstall" > ramdisk = "/boot/initrd-f7xeninstall" > extra = "text ks=http://www.mcdees-specialties.com/fed7/minimal-ks.cf" > name = "fed7" > memory = "230" > disk = [ 'tap:aio:/var/lib/xen/images/fed7.img,xvda,w', ] > #vif = [ '', ] > vif = [ 'bridge=xenbr0', ] > ip = "192.168.1.202" > netmask = "255.255.255.0" > gateway = "192.168.1.1" > vcpus=1 > on_reboot = 'destroy' > on_crash = 'destroy' > > When I run > xm create -c fed7inst > > it gets to here and stops > > ..................................... > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 180k freed > Write protecting the kernel read-only data: 762k > > Any and all ideas are welcome How exactly do you start your guest? What does starting your guest write to /var/log/xen/ and xm dmesg ? From paul at xelerance.com Wed Jun 6 17:07:35 2007 From: paul at xelerance.com (Paul Wouters) Date: Wed, 6 Jun 2007 13:07:35 -0400 (EDT) Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <010601c7a854$e9adcff0$0201a8c0@Dell9200> References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> Message-ID: On Wed, 6 Jun 2007, Brian McDonald wrote: > I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/ > When I run > xm create -c fed7inst > > it gets to here and stops > > ..................................... > Using IPI No-Shortcut mode > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 180k freed > Write protecting the kernel read-only data: 762k http://www.mail-archive.com/fedora-xen at redhat.com/msg00676.html Paul From jklein at saugus.k12.ca.us Wed Jun 6 17:14:12 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Wed, 6 Jun 2007 10:14:12 -0700 (PDT) Subject: [Fedora-xen] 32bit PV on 64bit Host In-Reply-To: <188039.1518731181149633796.JavaMail.root@do8> Message-ID: <27482248.1519721181150052769.JavaMail.root@do8> It's my understanding that 32bit PV vms would run on 64bit hosts with Xen 3.1. However, this doesn't seem to work. Attempting to use virt-install from 64bit using a 32bit source files (over http) dies almost instantly. Creating the 32bit PV vm on a 32-bit system and copying to 64bit also doesn't work (dies at start before even a hint of starting.) Same when migrating a 32bit to a 64 bit (again, dies instantly.) Am I wrong about 32bit on 64bit hosts? -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian.mcdonald at mcdees-specialties.com Wed Jun 6 17:21:58 2007 From: brian.mcdonald at mcdees-specialties.com (Brian McDonald) Date: Wed, 6 Jun 2007 13:21:58 -0400 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <87myzdui97.fsf@pike.pond.sub.org> References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> <87myzdui97.fsf@pike.pond.sub.org> Message-ID: <011701c7a85f$307f5840$0201a8c0@Dell9200> How exactly do you start your guest? What does starting your guest write to /var/log/xen/ and xm dmesg ? I start using the xm command xm create -c fed7inst Where fed7inst is the name of the config file Xend.log [2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'fed7'], ['memory', '230'], [' on_reboot', 'destroy'], ['on_crash', 'destroy'], ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-f7xeninstall'], ['ramdisk', '/boo t/initrd-f7xeninstall'], ['ip', '192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off'], ['args', 'text ks=http://www.mcdees-specialties. com/fed7/minimal-ks.cf']]], ['device', ['tap', ['uname', 'tap:aio:/var/lib/xen/images/fed7.img'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0']]]]) [2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'fed7'], ['memory', '230'], [ 'on_reboot', 'destroy'], ['on_crash', 'destroy'], ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-f7xeninstall'], ['ramdisk', '/bo ot/initrd-f7xeninstall'], ['ip', '192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off'], ['args', 'text ks=http://www.mcdees-specialties .com/fed7/minimal-ks.cf']]], ['device', ['tap', ['uname', 'tap:aio:/var/lib/xen/images/fed7.img'], ['dev', 'xvda'], ['mode', 'w']]], ['device' , ['vif', ['bridge', 'xenbr0']]]] [2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, ' uuid': None, 'on_crash': 'destroy', 'on_reboot': 'destroy', 'localtime': None, 'image': ['linux', ['kernel', '/boot/vmlinuz-f7xeninstall'], [' ramdisk', '/boot/initrd-f7xeninstall'], ['ip', '192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off'], ['args', 'text ks=http://www.mcde es-specialties.com/fed7/minimal-ks.cf']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'fed7', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 230, 'device': [('tap', ['tap', ['uname', 'tap:aio:/var/lib/xen/images/ fed7.img'], ['dev', 'xvda'], ['mode', 'w']]), ('vif', ['vif', ['bridge', 'xenbr0']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-06-06 13:18:41 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 28 1.0 [2007-06-06 13:18:41 xend 2642] DEBUG (balloon:127) Balloon: 236344 KiB free; need 235520; done. [2007-06-06 13:18:41 xend 2642] INFO (image:136) buildDomain os=linux dom=28 vcpus=1 [2007-06-06 13:18:41 xend 2642] DEBUG (image:199) dom = 28 [2007-06-06 13:18:41 xend 2642] DEBUG (image:200) image = /boot/vmlinuz-f7xeninstall [2007-06-06 13:18:41 xend 2642] DEBUG (image:201) store_evtchn = 1 [2007-06-06 13:18:41 xend 2642] DEBUG (image:202) console_evtchn = 2 [2007-06-06 13:18:41 xend 2642] DEBUG (image:203) cmdline = ip=192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off text ks=http: //www.mcdees-specialties.com/fed7/minimal-ks.cf [2007-06-06 13:18:41 xend 2642] DEBUG (image:204) ramdisk = /boot/initrd-f7xeninstall [2007-06-06 13:18:41 xend 2642] DEBUG (image:205) vcpus = 1 [2007-06-06 13:18:41 xend 2642] DEBUG (image:206) features = [2007-06-06 13:18:41 xend 2642] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' [2007-06-06 13:18:41 xend 2642] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '51712', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/tap/28/51712'} to /local/domain/28/device/vbd/51712. [2007-06-06 13:18:41 xend 2642] DEBUG (DevController:112) DevController: writing {'domain': 'fed7', 'frontend': '/local/domain/28/device/vbd/5 1712', 'dev': 'xvda', 'state': '1', 'params': 'aio:/var/lib/xen/images/fed7.img', 'mode': 'w', 'online': '1', 'frontend-id': '28', 'type': 'ta p'} to /local/domain/0/backend/tap/28/51712. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:4f:c2:71', 'handle': '0' , 'state': '1', 'backend': '/local/domain/0/backend/vif/28/0'} to /local/domain/28/device/vif/0. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'fed7', 'handle': '0', 'script ': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/28/device/vif/0', 'mac': '00:16:3e:4f:c2:71', 'online': '1', 'front end-id': '28'} to /local/domain/0/backend/vif/28/0. [2007-06-06 13:18:42 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '0', 'uuid': '4a437037-a07f-7c e9-4128-086fb2a1ae92', 'on_reboot': 'destroy', 'start_time': '1181150322.24', 'on_poweroff': 'destroy', 'name': 'fed7', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '230', 'on_crash': 'destroy', 'image': "(linux (kernel /boot/vmlinuz-f7xeninstall) (ramdisk /b oot/initrd-f7xeninstall) (ip 192.168.1.202:1.2.3.4:192.168.1.1:255.255.255.0::eth0:off) (args 'text ks=http://www.mcdees-specialties.com/fed7/ minimal-ks.cf'))", 'maxmem': '230'} [2007-06-06 13:18:42 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:750) Storing domain details: {'console/ring-ref': '103594', 'console/port ': '2', 'name': 'fed7', 'console/limit': '1048576', 'vm': '/vm/4a437037-a07f-7ce9-4128-086fb2a1ae92', 'domid': '28', 'cpu/0/availability': 'on line', 'memory/target': '235520', 'store/ring-ref': '103595', 'store/port': '1'} [2007-06-06 13:18:42 xend.XendDomainInfo 2642] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices vif. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:149) Waiting for 0. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/28/0/hotplug-status. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices usb. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices vbd. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices irq. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices vkbd. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices vfb. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices pci. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices ioports. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices tap. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:149) Waiting for 51712. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/tap/28/51712/hotplug-status. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-06 13:18:42 xend 2642] DEBUG (DevController:143) Waiting for devices vtpm. [2007-06-06 13:18:42 xend 2642] INFO (XendDomain:370) Domain fed7 (28) unpaused. From clalance at redhat.com Wed Jun 6 17:28:10 2007 From: clalance at redhat.com (Chris Lalancette) Date: Wed, 06 Jun 2007 13:28:10 -0400 Subject: [Fedora-xen] 32bit PV on 64bit Host In-Reply-To: <27482248.1519721181150052769.JavaMail.root@do8> References: <27482248.1519721181150052769.JavaMail.root@do8> Message-ID: <4666EEAA.2040708@redhat.com> Jim Klein wrote: > It's my understanding that 32bit PV vms would run on 64bit hosts with > Xen 3.1. However, this doesn't seem to work. Attempting to use > virt-install from 64bit using a 32bit source files (over http) dies > almost instantly. Creating the 32bit PV vm on a 32-bit system and > copying to 64bit also doesn't work (dies at start before even a hint of > starting.) Same when migrating a 32bit to a 64 bit (again, dies > instantly.) Am I wrong about 32bit on 64bit hosts? > > Yes and no. The problem is that F7 kernel side is based on 3.0.4, while the hypervisor and the userland tools are based on 3.1. Without the kernel being updated to 3.1, 32 pv on 64 HV won't work. Luckily, that kernel is forthcoming for F7. Chris Lalancette From armbru at redhat.com Wed Jun 6 17:51:24 2007 From: armbru at redhat.com (Markus Armbruster) Date: Wed, 06 Jun 2007 19:51:24 +0200 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <010601c7a854$e9adcff0$0201a8c0@Dell9200> (Brian McDonald's message of "Wed, 6 Jun 2007 12:08:24 -0400") References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> Message-ID: <87abvdug2r.fsf@pike.pond.sub.org> "Brian McDonald" writes: > I am having problems getting a fedora7 domu running under my Centos5 Dom0 > (this is a centos5 server no graphical interface) > > I followed the same steps to created the fedora 7 domu as I have for > creating the cenots5 domu that I have on the same box. > > I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/ Wait a sec! You simply plunked kernel & initrd into your /boot? That bypasses the scripts in the rpms, and you know, those are there for a reason. Can you try installing kernel-xen with yum? [...] From berrange at redhat.com Wed Jun 6 17:52:52 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 6 Jun 2007 18:52:52 +0100 Subject: [Fedora-xen] 32bit PV on 64bit Host In-Reply-To: <27482248.1519721181150052769.JavaMail.root@do8> References: <188039.1518731181149633796.JavaMail.root@do8> <27482248.1519721181150052769.JavaMail.root@do8> Message-ID: <20070606175252.GP18020@redhat.com> On Wed, Jun 06, 2007 at 10:14:12AM -0700, Jim Klein wrote: > > It's my understanding that 32bit PV vms would run on 64bit hosts with > Xen 3.1. However, this doesn't seem to work. Attempting to use > virt-install from 64bit using a 32bit source files (over http) dies > almost instantly. Creating the 32bit PV vm on a 32-bit system and > copying to 64bit also doesn't work (dies at start before even a hint > of starting.) Same when migrating a 32bit to a 64 bit (again, dies > instantly.) Am I wrong about 32bit on 64bit hosts? We weren't too clear in the release notes unfortunately. When we updated to the Xen 3.1.0 hypervisor & userspace we gained the ability to run 32-bit guests on 64-bit HV in theory. To make it work in practice we're waiting on some updates to the kernel Dom0 drivers. Hopefully we'll get these into an update kernel-xen without too much delay... 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 -=| From brian.mcdonald at mcdees-specialties.com Wed Jun 6 18:00:34 2007 From: brian.mcdonald at mcdees-specialties.com (Brian McDonald) Date: Wed, 6 Jun 2007 14:00:34 -0400 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <87abvdug2r.fsf@pike.pond.sub.org> References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> <87abvdug2r.fsf@pike.pond.sub.org> Message-ID: <011901c7a864$950d6ef0$0201a8c0@Dell9200> -----Original Message----- From: Markus Armbruster [mailto:armbru at redhat.com] Sent: Wednesday, June 06, 2007 1:51 PM To: Brian McDonald Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU "Brian McDonald" writes: > I am having problems getting a fedora7 domu running under my Centos5 Dom0 > (this is a centos5 server no graphical interface) > > I followed the same steps to created the fedora 7 domu as I have for > creating the cenots5 domu that I have on the same box. > > I downloaded the vmlinux and initrd from here > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ > images/xen/ >>Wait a sec! You simply plunked kernel & initrd into your /boot? That >>bypasses the scripts in the rpms, and you know, those are there for a >>reason. Can you try installing kernel-xen with yum? You can not use yum if the operating system is not installed in the domU This is a centos5 server that I am trying to load a fedora7 domU From armbru at redhat.com Wed Jun 6 18:32:37 2007 From: armbru at redhat.com (Markus Armbruster) Date: Wed, 06 Jun 2007 20:32:37 +0200 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <011901c7a864$950d6ef0$0201a8c0@Dell9200> (Brian McDonald's message of "Wed, 6 Jun 2007 14:00:34 -0400") References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> <87abvdug2r.fsf@pike.pond.sub.org> <011901c7a864$950d6ef0$0201a8c0@Dell9200> Message-ID: <87y7ixszlm.fsf@pike.pond.sub.org> "Brian McDonald" writes: > -----Original Message----- > From: Markus Armbruster [mailto:armbru at redhat.com] > Sent: Wednesday, June 06, 2007 1:51 PM > To: Brian McDonald > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU > > "Brian McDonald" writes: > >> I am having problems getting a fedora7 domu running under my Centos5 Dom0 >> (this is a centos5 server no graphical interface) >> >> I followed the same steps to created the fedora 7 domu as I have for >> creating the cenots5 domu that I have on the same box. >> >> I downloaded the vmlinux and initrd from here >> > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os/ >> images/xen/ > >>>Wait a sec! You simply plunked kernel & initrd into your /boot? That >>>bypasses the scripts in the rpms, and you know, those are there for a >>>reason. Can you try installing kernel-xen with yum? > > You can not use yum if the operating system is not installed in the domU > This is a centos5 server that I am trying to load a fedora7 domU Why can't you simply create the guest with virt-install? From brian at brie.com Wed Jun 6 19:48:41 2007 From: brian at brie.com (Brian Lavender) Date: Wed, 6 Jun 2007 12:48:41 -0700 Subject: [Fedora-xen] Debian VM progress Message-ID: <20070606194841.GE17966@brie.com> It turns out I was able to get my Debian VM to boot. My Dom0 is actually a Centos 5. What I did is I created a Debian install using QEMU, then I placed the Centos kernel into Debian. I created an initrd for the Debian using the Centos kernel. I also told the kernel that the console was xvc0. I added xvc0 to the /etc/inittab and securetty. The system boots, things start, and I get a login for the console. But.... I don't see an eth0. The only indication I see of an eth0 is the following. netfront: Initialising virtual ethernet driver. netfront: device eth0 has flipping receive path. But, I don't see any evidence when I type ifconfig. So, what do I need to do to get this eth0 going? brian -- Brian Lavender http://www.brie.com/brian/ From paul at xelerance.com Wed Jun 6 19:58:51 2007 From: paul at xelerance.com (Paul Wouters) Date: Wed, 6 Jun 2007 15:58:51 -0400 (EDT) Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <011801c7a85f$82b22160$0201a8c0@Dell9200> References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> <011801c7a85f$82b22160$0201a8c0@Dell9200> Message-ID: On Wed, 6 Jun 2007, Brian McDonald wrote: > I am using the new fedora 7 image, you mean fedora 7 does not like to be a > DOMU? This does make any sense. The Fedora initrd on the Dom0 cannot be used to start xenu's because the initrd is lacking xenblk and xennet. Basically, you can only use pygrub with the dom0 and unchanged initrd's, which means that you can only run FC6 and/or F7 machines. As soon as you need to brung up other OSes (eg FC3 or RHEL4 or Centos or Debian), you will need a custom made initrd. Paul From tom.horsley at att.net Wed Jun 6 20:44:44 2007 From: tom.horsley at att.net (Tom Horsley) Date: Wed, 6 Jun 2007 16:44:44 -0400 Subject: [Fedora-xen] fedora 7 guest problems under fedora 6 host In-Reply-To: <060620071641.6364.4666E3D6000E3B96000018DC2160280748970A049C9D0108D203019B@att.net> References: <060620071641.6364.4666E3D6000E3B96000018DC2160280748970A049C9D0108D203019B@att.net> Message-ID: <20070606164444.787d5e17@zooty> On Wed, 06 Jun 2007 16:41:59 +0000 tom.horsley at att.net (Tom Horsley) wrote: > If I try to do a paravirt install from the fedora 7 DVD image > (mounted under apache to be accessible on the network), the > virt-manager app crashes as soon as it is about to start the > install. Right. I forgot the Xen version on fc6 can't do paravirt to different arch, this one is explained :-). Anyone ever done something like a dd from the fc7 live dvd to the virtual machine's filesystem in a file to get fc7 installed entirely from the dom0 without booting the VM at all till everything already exists on the VM's filesystem? From brian at brie.com Wed Jun 6 20:48:36 2007 From: brian at brie.com (Brian Lavender) Date: Wed, 6 Jun 2007 13:48:36 -0700 Subject: [Fedora-xen] fedora 7 guest problems under fedora 6 host In-Reply-To: <20070606164444.787d5e17@zooty> References: <060620071641.6364.4666E3D6000E3B96000018DC2160280748970A049C9D0108D203019B@att.net> <20070606164444.787d5e17@zooty> Message-ID: <20070606204836.GF17966@brie.com> On Wed, Jun 06, 2007 at 04:44:44PM -0400, Tom Horsley wrote: > On Wed, 06 Jun 2007 16:41:59 +0000 > tom.horsley at att.net (Tom Horsley) wrote: > > > If I try to do a paravirt install from the fedora 7 DVD image > > (mounted under apache to be accessible on the network), the > > virt-manager app crashes as soon as it is about to start the > > install. > > Right. I forgot the Xen version on fc6 can't do paravirt to > different arch, this one is explained :-). > > Anyone ever done something like a dd from the fc7 live dvd to > the virtual machine's filesystem in a file to get fc7 installed > entirely from the dom0 without booting the VM at all till > everything already exists on the VM's filesystem? What if you use QEMU to create the image, and then put the support in? Copy the kernel from Dom0, make a new initrd, and then boot. Now, if I could only figure out where my network is located!!! qemu-img create -f raw debian.img 5G qemu -cdrom ../../iso/debian-40r0-i386-netinst.iso -hda debian.img -m 256 -boot d qemu -hda debian.img -m 384 brian -- Brian Lavender http://www.brie.com/brian/ From lamont at gurulabs.com Wed Jun 6 21:04:20 2007 From: lamont at gurulabs.com (Lamont Peterson) Date: Wed, 6 Jun 2007 15:04:20 -0600 Subject: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU In-Reply-To: <011901c7a864$950d6ef0$0201a8c0@Dell9200> References: <010601c7a854$e9adcff0$0201a8c0@Dell9200> <87abvdug2r.fsf@pike.pond.sub.org> <011901c7a864$950d6ef0$0201a8c0@Dell9200> Message-ID: <200706061504.26168.lamont@gurulabs.com> On Wednesday 06 June 2007 12:00pm, Brian McDonald wrote: > -----Original Message----- > From: Markus Armbruster [mailto:armbru at redhat.com] > Sent: Wednesday, June 06, 2007 1:51 PM > To: Brian McDonald > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Centos5 Dom0 and Fedora7 DomU > > "Brian McDonald" writes: > > I am having problems getting a fedora7 domu running under my Centos5 Dom0 > > (this is a centos5 server no graphical interface) > > > > I followed the same steps to created the fedora 7 domu as I have for > > creating the cenots5 domu that I have on the same box. > > > > I downloaded the vmlinux and initrd from here > > ftp://download.fedora.redhat.com/pub/fedora/linux/releases/7/Fedora/i386/os >/ > > > images/xen/ > > > >>Wait a sec! You simply plunked kernel & initrd into your /boot? That > >>bypasses the scripts in the rpms, and you know, those are there for a > >>reason. Can you try installing kernel-xen with yum? > > You can not use yum if the operating system is not installed in the domU > This is a centos5 server that I am trying to load a fedora7 domU Yes, you can. Loopback mount (or whatever) the F7 domU to /mnt/temp/ (or whatever), run "chroot /mnt/temp/" (as root) and then you can run yum and do all kinds of other things from within there. I haven't tried this yet with F7 or C5, but I have gotten things working just fine to create F6 and SLES10 on RHEL5. -- Lamont Peterson Senior Instructor Guru Labs, L.C. [ http://www.GuruLabs.com/ ] NOTE: All messages from this email address should be digitally signed with my 0xDC0DD409 GPG key. It is available on the pgp.mit.edu keyserver as well as other keyservers that sync with MIT's. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From brian at brie.com Wed Jun 6 23:13:25 2007 From: brian at brie.com (Brian Lavender) Date: Wed, 6 Jun 2007 16:13:25 -0700 Subject: [Fedora-xen] Debian VM progress In-Reply-To: <20070606194841.GE17966@brie.com> References: <20070606194841.GE17966@brie.com> Message-ID: <20070606231325.GG17966@brie.com> On Wed, Jun 06, 2007 at 12:48:41PM -0700, Brian Lavender wrote: > It turns out I was able to get my Debian VM to boot. My Dom0 is actually > a Centos 5. What I did is I created a Debian install using QEMU, then I > placed the Centos kernel into Debian. I created an initrd for the Debian > using the Centos kernel. I also told the kernel that the console was > xvc0. I added xvc0 to the /etc/inittab and securetty. > > The system boots, things start, and I get a login for the console. > But.... I don't see an eth0. The only indication I see of an eth0 is > the following. > > netfront: Initialising virtual ethernet driver. > netfront: device eth0 has flipping receive path. > > But, I don't see any evidence when I type ifconfig. So, what do I need > to do to get this eth0 going? I discovered my server supports full virtualization. It just wasn't turned on in the BIOS. So, I went that way. brian -- Brian Lavender http://www.brie.com/brian/ From johan.dewit at external.thalesaleniaspace.com Thu Jun 7 07:18:02 2007 From: johan.dewit at external.thalesaleniaspace.com (Johan De Wit) Date: Thu, 07 Jun 2007 09:18:02 +0200 Subject: [Fedora-xen] building boot/xen/vmlinuz and intrd docs Message-ID: <1181200682.3503.3.camel@localhost.hobsite.be> Hi, Running FC7, on a non PAE laptop. Rebuilded the xen kernels, but when installing guests using virt-install, this doesn't work. So I'm looking for some docs/howto to rebuild the /boot/xen from the installation CD without the PAE feature. I dit copy the kernel-xen vmlinuz to the boot. But then i have to load some drivers manually. Thanks a lot Johan From rjones at redhat.com Thu Jun 7 14:31:47 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 07 Jun 2007 15:31:47 +0100 Subject: [Fedora-xen] virt-manager and guest config file In-Reply-To: <7675761b0706060919j2c5c3e78y5c44b9c55f712fbf@mail.gmail.com> References: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> <20070606161116.GJ18020@redhat.com> <7675761b0706060919j2c5c3e78y5c44b9c55f712fbf@mail.gmail.com> Message-ID: <466816D3.4040400@redhat.com> mathieu rohon wrote: > Great, thanks for your answer Daniel. > > So the following logical question is : How can I modify my guests > parameters? let's say, add usb support for example? Using virsh, you can do this on an inactive (not running) domain: virsh dumpxml DOMAINNAME > guest.xml vi guest.xml virsh define guest.xml or if you've got a really recent version of virsh and you want to just attach a device to a running domain, try the 'virsh attach-device' command. > More generally, can you tell me where this is documented? The XML is documented here: http://libvirt.org/format.html Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From alexander.samad at hp.com Fri Jun 8 05:21:20 2007 From: alexander.samad at hp.com (Samad, Alex) Date: Fri, 8 Jun 2007 15:21:20 +1000 Subject: [Fedora-xen] Problem Installing Fedora 7 as a Guest on Xen machine Message-ID: Hi I have run into a problem installing fedora 7 as a guest on a Xen machine. The host machine is a amd64 - Debian lenny install. Running 2.6.20-1-xen-amd64 xm info host : debxen release : 2.6.20-1-xen-amd64 version : #1 SMP Tue Apr 24 22:23:22 UTC 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2800 hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f total_memory : 8191 free_memory : 1 xen_major : 3 xen_minor : 0 xen_extra : .3-1 xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : Tue Oct 17 22:09:52 2006 +0100 cc_compiler : gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19) cc_compile_by : ultrotter cc_compile_domain : debian.org cc_compile_date : Fri Nov 3 00:21:27 CET 2006 xend_config_format : 2 I have downloaded the fedora 7 DVD, I have extracted the xen vmlinuz and zen initrd.img This is my fedora7.cfg # # Kernel + memory size # kernel = '/etc/xen/data/fedora7/vmlinuz' ramdisk = '/etc/xen/data/fedora7/initrd.img' memory = '1024' extra = 'pnpacpi=off sync_console vnc vncpassword=qwerty text vncconnect=16.144.29.11' #bootloader = '/usr/lib/xen-3.0.3-1/bin/pygrub' # # Disk device(s). # disk = [ 'phy:vglocal/fedora7-disk,xvda,w' ] # # Hostname # name = 'fedora7' # # Networking # dhcp = 'dhcp' #vif = [ 'type=ioemu, bridge=xenbr0' ] vif = [ '' ] # # Behaviour # on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' serial = "pty" localtime = 0 vcpus = 2 I tried something similar with RHEL5 and it worked, fedora7 is getting stuck >From xm console fedora7 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 938k I not sure what is mean to come after here for me to guess where it might be getting stuck. Can any one provide any hints or know what is going wrong. Maybe there is a mis match of the xen versions ??? Thanks Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: From jprats at cesca.es Sun Jun 10 22:34:21 2007 From: jprats at cesca.es (Jordi Prats) Date: Mon, 11 Jun 2007 00:34:21 +0200 Subject: [Fedora-xen] read-only acces to a filesystem on a xen guest Message-ID: <466C7C6D.9070400@cesca.es> Hi, Which is the best way to acces a the data on a live xen guest to do backups? It's safe enought to mount it as read-only? I supose it is not, isn't it? If it's on a logical volume of LVM I could do a snapshot. Would it be consistent with the filesystem without being mounted on the dom0? So LVM is smart enought to tell to the xen guest to flush all cache buffers before to do the snapshot? Thanks, Jordi -- ...................................................................... __ / / Jordi Prats Catal? C E / S / C A Departament de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... pgp:0x5D0D1321 ...................................................................... From zayfod at yahoo.com Mon Jun 11 10:34:22 2007 From: zayfod at yahoo.com (Kaloyan Tenchov) Date: Mon, 11 Jun 2007 03:34:22 -0700 (PDT) Subject: [Fedora-xen] Problem Installing Fedora 7 as a Guest on Xen machine In-Reply-To: Message-ID: <151838.56964.qm@web54504.mail.re2.yahoo.com> Hello, You do not specify your exact problem with the installation. Are you using the kernel and initrd from the images/xen/ directory of the Fedora 7 installation tree? If so, most probably your guest is running ok and the Anaconda loader has started and is waiting for input on the guest's local console. The local console is differrent from the serial console accessed by "xm console" and it is a new feature in Xen 3.1 and Fedora 7. The guests now have a "real" monitor which can be accessed remotely by VNC. This VNC server is not the Anaconda VNC server for network installation of Fedora that you are trying to start with the "vnc", "vncpassword", and "vncconnect" kernel options. It is started by xend on the Xen host. Have a look at all vnc related configuration variables by issuing "xm create --help_config". Try to configure and connect to the guests's monitor and see if Anaconda is running and waiting for some user input. Have in mind that there are problems related to VNC network installations of Fedora 7: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243265 ____________________________________________________________________________________ Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php From tom.horsley at att.net Mon Jun 11 18:25:03 2007 From: tom.horsley at att.net (Tom Horsley) Date: Mon, 11 Jun 2007 14:25:03 -0400 Subject: [Fedora-xen] Problem Installing Fedora 7 as a Guest on Xen machine In-Reply-To: <151838.56964.qm@web54504.mail.re2.yahoo.com> References: <151838.56964.qm@web54504.mail.re2.yahoo.com> Message-ID: <20070611142503.7fa98c6b@zooty> On Mon, 11 Jun 2007 03:34:22 -0700 (PDT) Kaloyan Tenchov wrote: > You do not specify your exact problem with the installation. Anaconda has started, but soon goes into a completely frozen hung state using 100% cpu (according to the vm monitor on the dom0). Everything is totally non-responsive. Even the little comet orbiting the cursor in the console freezes up (along with the cursor). It acts exactly like this bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=237895 except "random time" always happens before I can even get it through an install :-). The dom0 is running Xen in fedora core 6 (x86_64), I'm trying to install an i386 guest fedora 7 (fully virtual). I also have to use the noisapnp=1 kernel boot parameter to even get this far, otherwise it hangs when booting the kernel to do the install at the "scanning for isa pnp cards" step. And, in addition to that, the fedora 7 kernel apparently doesn't have (or can't find) a driver for the emulated cdrom, so I have to do a network install rather than installing completely from the DVD iso image. I can work around most of these, but the freezing during install is harder (though I've seen some folks using the livecd builder to build images for xen guests, which might be an approach, but I haven't looked at trying to figure that out yet). From ben at muppethouse.com Mon Jun 11 21:51:17 2007 From: ben at muppethouse.com (Ben Russo) Date: Mon, 11 Jun 2007 17:51:17 -0400 Subject: [Fedora-xen] XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won't start after install finishes. Message-ID: I have many boxes running rh-7.2 (these are stripped down, minimal installs, for appliances on a private network that isn't routable) I want to run VIRTUAL images of the same setup for testing purposes. I read the Fedora 6 XEN getting started guide and skimmed through the FAQ. I browsed through this mailing list to see if I could find my problem here as well. No luck. I have a Dell-2950 with Quad Core XEON processors, PAE, VMX, and it is enabled in BIOS. 8GB RAM, 2GB assigned to Dom0 Booted into RHEL-5 Xen kernel, installed all the latest patches as of 6/11/2007, and rebooted. Then Started Virtual Machine Manager GUI Selected "New..." from File menu and followed the wizard. then installed FULLY VIRTUALIZED RH-72 from original Red Hat 7.2 CD's this went fine with the Virtual Machine Manager GUI "New Machine" wizard. The only non-usual thing I did for an RH72 install was to give it the kernel boot option mem=500M After the install completed, the DomU guest said it was now going to reboot and I should remove any CD's. Then the DomU disappeared. It took me forever to figure out that I couldn't use the virt-manager GUI to restore a DomU configuration file. There really should be a more intuitive way for this to work. I am not a dummy, and it took me forever to figure out how to start the DomU again. Now that I figured out that I have to go to a command line prompt and type "xm create -c /etc/xen/rh72-test", I find out that the new guest gets a kernel panic on bootup after the bootup menu Unfortunately the messages scroll by really fast, and I can't catch them all, but at the end, the last page visible in the VNC console says: ==================================================================== Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX Unable to handle kernel paging request at virtual address ffffffff printing eip: c0204a00 *pde = 00001063 *pte = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010202 eax: fffffff ebx: 00000000 ecx: 00000004 edx: 00000004 esi: fffffff edi: c0229972 ebp: 0008e000 esp: c0257fb4 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c0257000) Stack: c026d6e8 0000000 c024.... ... ... Call Trace: [<.... Code: f3 a6 ... <0>Kernel panic: Attempted to kill the idle task! In idle task - not syncing ==================================================================== The console where I ran the "xm create..." command shows nothing out of the ordinary. xm dmesg shows: ####### START xm dmesg ############# (XEN) (file=hvm.c, line=197) Allocated port 3 for hvm. (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83fc (pseudophys a0): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83fb (pseudophys a1): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83fa (pseudophys a2): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f9 (pseudophys a3): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f8 (pseudophys a4): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f7 (pseudophys a5): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f6 (pseudophys a6): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f5 (pseudophys a7): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f4 (pseudophys a8): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f3 (pseudophys a9): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f2 (pseudophys aa): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f1 (pseudophys ab): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f0 (pseudophys ac): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ef (pseudophys ad): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ee (pseudophys ae): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ed (pseudophys af): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ec (pseudophys b0): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83eb (pseudophys b1): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ea (pseudophys b2): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e9 (pseudophys b3): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e8 (pseudophys b4): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e7 (pseudophys b5): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e6 (pseudophys b6): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e5 (pseudophys b7): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e4 (pseudophys b8): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e3 (pseudophys b9): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e2 (pseudophys ba): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e1 (pseudophys bb): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e0 (pseudophys bc): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83df (pseudophys bd): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83de (pseudophys be): count=2 type=0 (XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83dd (pseudophys bf): count=2 type=0 (XEN) vmx_do_launch(): GUEST_CR3<=001adda0, HOST_CR3<=001adca0 (XEN) (GUEST: 7) HVM Loader (XEN) (GUEST: 7) Detected Xen v3.0.3-rc5-8.1.4.el (XEN) (GUEST: 7) Writing SMBIOS tables ... (XEN) (GUEST: 7) Loading ROMBIOS ... (XEN) (GUEST: 7) Creating MP tables ... (XEN) (GUEST: 7) Loading Cirrus VGABIOS ... (XEN) (GUEST: 7) Loading ACPI ... (XEN) (GUEST: 7) Loading VMXAssist ... (XEN) (GUEST: 7) VMX go ... (XEN) (GUEST: 7) VMXAssist (Mar 8 2007) (XEN) (GUEST: 7) Memory size 500 MB (XEN) (GUEST: 7) E820 map: (XEN) (GUEST: 7) 0000000000000000 - 000000000009F000 (RAM) (XEN) (GUEST: 7) 000000000009F000 - 00000000000A0000 (Reserved) (XEN) (GUEST: 7) 00000000000A0000 - 00000000000C0000 (Type 16) (XEN) (GUEST: 7) 00000000000F0000 - 0000000000100000 (Reserved) (XEN) (GUEST: 7) 0000000000100000 - 000000001F3F0000 (RAM) (XEN) (GUEST: 7) 000000001F3F0000 - 000000001F3FA000 (ACPI Data) (XEN) (GUEST: 7) 000000001F3FA000 - 000000001F3FD000 (ACPI NVS) (XEN) (GUEST: 7) 000000001F3FD000 - 000000001F3FE000 (Type 19) (XEN) (GUEST: 7) 000000001F3FE000 - 000000001F3FF000 (Type 18) (XEN) (GUEST: 7) 000000001F3FF000 - 000000001F400000 (Type 17) (XEN) (GUEST: 7) 00000000FEC00000 - 0000000100000000 (Type 16) (XEN) (GUEST: 7) (XEN) (GUEST: 7) Start BIOS ... (XEN) (GUEST: 7) Starting emulated 16-bit real-mode: ip=F000:FFF0 (XEN) (GUEST: 7) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $ (XEN) (GUEST: 7) Remapping master: ICW2 0x8 -> 0x20 (XEN) (GUEST: 7) Remapping slave: ICW2 0x70 -> 0x28 (XEN) (GUEST: 7) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50 vruppert Exp $ (XEN) (GUEST: 7) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date: 2005/05/07 15: 55:26 $ (XEN) (GUEST: 7) (XEN) (GUEST: 7) ata0-0: PCHS=12190/16/63 translation=none LCHS=1024/16/63 (XEN) (GUEST: 7) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (6000 MBytes) (XEN) (GUEST: 7) ata0 slave: Unknown device (XEN) (GUEST: 7) (XEN) (GUEST: 7) Booting from Hard Disk... (XEN) (GUEST: 7) int13_harddisk: function 41, unmapped device for ELDL=81 (XEN) (GUEST: 7) int13_harddisk: function 08, unmapped device for ELDL=81 (XEN) (GUEST: 7) *** int 15h function AX=00C0, BX=0000 not yet supported! (XEN) (GUEST: 7) int13_harddisk: function 15, unmapped device for ELDL=81 (XEN) (GUEST: 7) KBD: unsupported int 16h function 03 (XEN) (GUEST: 7) int13_harddisk: function 15, unmapped device for ELDL=81 ################## end xm dmesg There is nothing in /var/log/xen/xend-debug.log This is what is in the /var/log/xen/xend.log ##### START xend.log [2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'rh72_test1'], ['memory', '500'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['uuid', 'f7dff459-6b52-4d6f-d40f-087cdbf08b05'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boot', 'c'], ['serial', 'pty'], ['vnc', 1], ['vncunused', 1], ['display', ':0.0'], ['xauthority', '/tmp/.gdm82ZSTT'], ['acpi', 1], ['apic', 1], ['vncpasswd', None]]], ['device', ['vbd', ['uname', 'file:/opt/xen-machines/rh72-test/rh72_test1.disk1'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:26:f0:37'], ['type', 'ioemu']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['xauthority', '/tmp/.gdm82ZSTT'], ['display', ':0.0']]]]) [2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'rh72_test1'], ['memory', '500'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['uuid', 'f7dff459-6b52-4d6f-d40f-087cdbf08b05'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boot', 'c'], ['serial', 'pty'], ['vnc', 1], ['vncunused', 1], ['display', ':0.0'], ['xauthority', '/tmp/.gdm82ZSTT'], ['acpi', 1], ['apic', 1], ['vncpasswd', None]]], ['device', ['vbd', ['uname', 'file:/opt/xen-machines/rh72-test/rh72_test1.disk1'], ['dev', 'hda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:26:f0:37'], ['type', 'ioemu']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['xauthority', '/tmp/.gdm82ZSTT'], ['display', ':0.0']]]] [2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': 'f7dff459-6b52-4d6f-d40f-087cdbf08b05', 'on_crash': 'restart', 'on_reboot': 'restart', 'localtime': None, 'image': ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib/xen/bin/qemu-dm'], ['pae', 1], ['vcpus', 1], ['boot', 'c'], ['serial', 'pty'], ['vnc', 1], ['vncunused', 1], ['display', ':0.0'], ['xauthority', '/tmp/.gdm82ZSTT'], ['acpi', 1], ['apic', 1], ['vncpasswd', None]], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'rh72_test1', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 500, 'device': [('vbd', ['vbd', ['uname', 'file:/opt/xen-machines/rh72-test/rh72_test1.disk1'], ['dev', 'hda'], ['mode', 'w']]), ('vif', ['vif', ['bridge', 'xenbr0'], ['mac', '00:16:3e:26:f0:37'], ['type', 'ioemu']]), ('vkbd', ['vkbd']), ('vfb', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['xauthority', '/tmp/.gdm82ZSTT'], ['display', ':0.0']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 7 1.0 [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: boot, val: c [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: fda, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: fdb, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: soundhw, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: localtime, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: serial, val: pty [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: std-vga, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: isa, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: vcpus, val: 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: acpi, val: 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: usb, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: usbdevice, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: k, val: None [2007-06-11 17:31:22 xend 3251] DEBUG (balloon:127) Balloon: 6216092 KiB free; need 528560; done. [2007-06-11 17:31:22 xend 3251] INFO (image:136) buildDomain os=hvm dom=7 vcpus=1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:282) dom = 7 [2007-06-11 17:31:22 xend 3251] DEBUG (image:283) image = /usr/lib/xen/boot/hvmloader [2007-06-11 17:31:22 xend 3251] DEBUG (image:284) store_evtchn = 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:285) memsize = 500 [2007-06-11 17:31:22 xend 3251] DEBUG (image:286) vcpus = 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:287) pae = 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:288) acpi = 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:289) apic = 1 [2007-06-11 17:31:22 xend 3251] DEBUG (image:435) hvm shutdown watch registered [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/7/768'} to /local/domain/7/device/vbd/768. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController: writing {'domain': 'rh72_test1', 'frontend': '/local/domain/7/device/vbd/768', 'dev': 'hda', 'state': '1', 'params': '/opt/xen-machines/rh72-test/rh72_test1.disk1', 'mode': 'w', 'online': '1', 'frontend-id': '7', 'type': 'file'} to /local/domain/0/backend/vbd/7/768. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/7/0'} to /local/domain/7/device/vif/0. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'rh72_test1', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/7/device/vif/0', 'mac': '00:16:3e:26:f0:37', 'online': '1', 'frontend-id': '7', 'type': 'ioemu'} to /local/domain/0/backend/vif/7/0. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vkbd/7/0'} to /local/domain/7/device/vkbd/0. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController: writing {'frontend-id': '7', 'domain': 'rh72_test1', 'frontend': '/local/domain/7/device/vkbd/0', 'state': '1', 'online': '1'} to /local/domain/0/backend/vkbd/7/0. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/7/0'} to /local/domain/7/device/vfb/0. [2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController: writing {'vncunused': '1', 'domain': 'rh72_test1', 'frontend': '/local/domain/7/device/vfb/0', 'xauthority': '/tmp/.gdm82ZSTT', 'state': '1', 'online': '1', 'frontend-id': '7', 'type': 'vnc', 'display': ':0.0'} to /local/domain/0/backend/vfb/7/0. [2007-06-11 17:31:22 xend 3251] DEBUG (vfbif:92) No VNC passwd configured for vfb access [2007-06-11 17:31:22 xend 3251] INFO (image:418) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '7', '-m', '500', '-boot', 'c', '-serial', 'pty', '-vcpus', '1', '-acpi', '-domain-name', 'rh72_test1', '-net', 'nic,vlan=1,macaddr=00:16:3e:26:f0:37,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vncunused', '-vnclisten', '127.0.0.1'] [2007-06-11 17:31:22 xend 3251] INFO (image:420) device model pid: 6463 [2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '3', 'uuid': 'f7dff459-6b52-4d6f-d40f-087cdbf08b05', 'on_reboot': 'restart', 'start_time': '1181597482.26', 'on_poweroff': 'destroy', 'name': 'rh72_test1', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '500', 'on_crash': 'restart', 'image': "(hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm) (pae 1) (vcpus 1) (boot c) (serial pty) (vnc 1) (vncunused 1) (display :0.0) (xauthority /tmp/.gdm82ZSTT) (acpi 1) (apic 1) (vncpasswd 'None'))", 'maxmem': '500'} [2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:750) Storing domain details: {'console/port': '2', 'name': 'rh72_test1', 'console/limit': '1048576', 'vm': '/vm/f7dff459-6b52-4d6f-d40f-087cdbf08b05', 'domid': '7', 'cpu/0/availability': 'online', 'memory/target': '512000', 'store/ring-ref': '757982', 'store/port': '1'} [2007-06-11 17:31:22 xend 3251] DEBUG (image:458) hvm_shutdown fired, shutdown reason=None [2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices vif. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 0. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices usb. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices vbd. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 768. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/7/768/hotplug-status. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vbd/7/768/hotplug-status. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices irq. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices vkbd. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 0. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vkbd/7/0/hotplug-status. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices vfb. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 0. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471) hotplugStatusCallback /local/domain/0/backend/vfb/7/0/hotplug-status. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485) hotplugStatusCallback 1. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices pci. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices ioports. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices tap. [2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for devices vtpm. [2007-06-11 17:31:23 xend 3251] INFO (XendDomain:370) Domain rh72_test1 (7) unpaused. [2007-06-11 17:41:01 xend 3251] DEBUG (image:458) hvm_shutdown fired, shutdown reason=halt [2007-06-11 17:41:01 xend.XendDomainInfo 3251] INFO (XendDomainInfo:899) Domain has shutdown: name=rh72_test1 id=7 reason=halt. [2007-06-11 17:41:01 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=7 [2007-06-11 17:41:01 xend.XendDomainInfo 3251] DEBUG (XendDomainInfo:1471) XendDomainInfo.destroyDomain(7) [2007-06-11 17:41:01 xend 3251] DEBUG (image:447) hvm shutdown watch unregistered ########### end xend.log My config file looks like this: [root at testxen xen]# cat /etc/xen/rh72_test1 # Automatically generated xen config file name = "rh72_test1" builder = "hvm" memory = "500" disk = [ 'file:/opt/xen-machines/rh72-test/rh72_test1.disk1,hda,w', ] vif = [ 'type=ioemu, mac=00:16:3e:26:f0:37, bridge=xenbr0', ] uuid = "f7dff459-6b52-4d6f-d40f-087cdbf08b05" device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" #kernel = "/opt/xen-machines/rh72-test/vmlinuz-2.4.7-10" #ramdisk = "/opt/xen-machines/rh72-test/initrd-2.4.7-10.img" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 vcpus=1 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' #--- END CONFIG FILE Any ideas? I would have thought that a fully virtualized host would be pretty foolproof? From berrange at redhat.com Tue Jun 12 14:15:15 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 12 Jun 2007 15:15:15 +0100 Subject: [Fedora-xen] XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won't start after install finishes. In-Reply-To: References: Message-ID: <20070612141515.GG3031@redhat.com> On Mon, Jun 11, 2007 at 05:51:17PM -0400, Ben Russo wrote: > I have many boxes running rh-7.2 > (these are stripped down, minimal installs, for appliances on a private > network that isn't routable) I want to run VIRTUAL images of the > same setup for testing purposes. > > I read the Fedora 6 XEN getting started guide and skimmed through the > FAQ. I browsed through this mailing list to see if I could find my > problem here as well. No luck. > > I have a Dell-2950 with Quad Core XEON processors, PAE, VMX, and it is > enabled in BIOS. 8GB RAM, 2GB assigned to Dom0 > > Booted into RHEL-5 Xen kernel, installed all the latest patches as of > 6/11/2007, and rebooted. > > Then Started Virtual Machine Manager GUI > Selected "New..." from File menu and followed the wizard. > then installed FULLY VIRTUALIZED > RH-72 from original Red Hat 7.2 CD's > this went fine with the > Virtual Machine Manager GUI "New Machine" wizard. > The only non-usual thing I did for an RH72 install was > to give it the kernel boot option mem=500M > > After the install completed, the DomU guest said it was now going to > reboot and I should remove any CD's. > > Then the DomU disappeared. > > It took me forever to figure out that I couldn't use the virt-manager > GUI to restore a DomU configuration file. There really should be > a more intuitive way for this to work. I am not a dummy, and it took > me forever to figure out how to start the DomU again. The virt-manager release in Fedora 7 can now start existing inactive guests. We recently pushed an update to Fedora 6 updates-testing which can do the same. > Now that I figured out that I have to go to a command line prompt and > type "xm create -c /etc/xen/rh72-test", That is no longer neccessary. Virt-manager can do that. You can also do it with 'virsh' which is the preferred tool for command line usage virsh start rh72-test > Unable to handle kernel paging request at virtual address ffffffff > printing eip: > c0204a00 > *pde = 00001063 > *pte = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[] > EFLAGS: 00010202 > eax: fffffff ebx: 00000000 ecx: 00000004 edx: 00000004 > esi: fffffff edi: c0229972 ebp: 0008e000 esp: c0257fb4 > ds: 0018 es: 0018 ss: 0018 > Process swapper (pid: 0, stackpage=c0257000) > Stack: c026d6e8 0000000 c024.... > ... > ... > Call Trace: [<.... > > Code: f3 a6 ... > <0>Kernel panic: Attempted to kill the idle task! Please file BZ reports for any kernel panic issues - mailing lists are a very bad way to track kernel bugs. 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 -=| From ben at muppethouse.com Tue Jun 12 15:38:14 2007 From: ben at muppethouse.com (Ben Russo) Date: Tue, 12 Jun 2007 11:38:14 -0400 Subject: [Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won't start after install finishes. In-Reply-To: <20070612141515.GG3031@redhat.com> References: <20070612141515.GG3031@redhat.com> Message-ID: <466EBDE6.2050408@muppethouse.com> >> Now that I figured out that I have to go to a command line prompt and >> type "xm create -c /etc/xen/rh72-test", > > That is no longer neccessary. Virt-manager can do that. You can also > do it with 'virsh' which is the preferred tool for command line usage > > virsh start rh72-test Thanks Dan, that helps. I'm glad the Virt-Manager GUI is being updated. >> <0>Kernel panic: Attempted to kill the idle task! > > Please file BZ reports for any kernel panic issues - mailing lists > are a very bad way to track kernel bugs. The virtual machine kernel is the one panicking. Do you think anybody is going to care about a RH7.2 kernel panic? Nobody will care, right? They would close the BZ report just saying it is old, unsupported in this configuration (running that old 7.2 kernel in a Xen environment). Isn't "fully-virtualized" Xen supposed to be able to run any i386 system that can utilize the virtual hardware presented? -Ben. From ben at muppethouse.com Tue Jun 12 15:38:14 2007 From: ben at muppethouse.com (Ben Russo) Date: Tue, 12 Jun 2007 11:38:14 -0400 Subject: [Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won't start after install finishes. In-Reply-To: <20070612141515.GG3031@redhat.com> References: <20070612141515.GG3031@redhat.com> Message-ID: <466EBDE6.2050408@muppethouse.com> >> Now that I figured out that I have to go to a command line prompt and >> type "xm create -c /etc/xen/rh72-test", > > That is no longer neccessary. Virt-manager can do that. You can also > do it with 'virsh' which is the preferred tool for command line usage > > virsh start rh72-test Thanks Dan, that helps. I'm glad the Virt-Manager GUI is being updated. >> <0>Kernel panic: Attempted to kill the idle task! > > Please file BZ reports for any kernel panic issues - mailing lists > are a very bad way to track kernel bugs. The virtual machine kernel is the one panicking. Do you think anybody is going to care about a RH7.2 kernel panic? Nobody will care, right? They would close the BZ report just saying it is old, unsupported in this configuration (running that old 7.2 kernel in a Xen environment). Isn't "fully-virtualized" Xen supposed to be able to run any i386 system that can utilize the virtual hardware presented? -Ben. From steve at atc-nycorp.com Tue Jun 12 18:17:20 2007 From: steve at atc-nycorp.com (Steve Brueckner) Date: Tue, 12 Jun 2007 14:17:20 -0400 Subject: [Fedora-xen] Xen kernel missing drivers? Message-ID: <60D45469A1AAD311A04C009027B6BF68061E5655@SERVER20> I have a Dell Optiplex 745, which is new enough that it uses the Intel 965 chipset and SATA optical drives. Due to this newness, no Fedora versions prior to 7 will even install on it. I believe this is because of drivers missing in Anaconda. Anyway, Fedora 7 will install, but when I install the Xen rpms (xen-3.1.0-0.rc7.1.rc7 and kernel-xen.2.6.20-2925.9.fc7) and try to reboot using the xen kernel, the machine freezes. It freezes shortly after a series of timeouts and errors that look like this: ata1.00: qc timeout (cmd 0xef) ata1.00: failed to set xfermode (err_mask=0x4) ata1.00: limiting speed to PIO0 failed to recover some devices, retrying in 5 secs ata1.00: disabled (repeat above series a few times) ata2.00... (similar set of errors) ... No volume groups found VG_host not found Why might the standard Fedora7 kernel work OK, but the Fedora7 xen kernel not work? Is it perhaps because of missing drivers in the xen kernel? How can I fix this problem? Do I need to give up on the xen rpms, and try to compile xen from source, but using the Fedora7 kernel instead of a vanilla Linux kernel? Thanks for any thoughts. Steve Brueckner, ATC-NY From treddy at rallydev.com Tue Jun 12 18:16:44 2007 From: treddy at rallydev.com (Tarun Reddy) Date: Tue, 12 Jun 2007 12:16:44 -0600 Subject: [Fedora-xen] Formatting pauses during install Message-ID: <166347C2-10C5-47B0-B1AE-87A740216B2B@rallydev.com> I'm using Centos 5 dom0 on an x86_64 machine with 12GB of RAM. Tried to use virt-manager to install a Centos 4 domU (also tried with Centos 5 domU) but the tool limits the disk to 16000 MB. So switch to using virt-install and specified an 80GB disk. Everything proceed well until "Formatting / file system" which stops at 11% (~8GB of the 74GB / partition). Are there hard limits here that I'm missing? Thank you, Tarun Rally Software From felix.schwarz at web.de Tue Jun 12 18:49:58 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Tue, 12 Jun 2007 20:49:58 +0200 Subject: [Fedora-xen] Re: Xen kernel missing drivers? In-Reply-To: <60D45469A1AAD311A04C009027B6BF68061E5655@SERVER20> References: <60D45469A1AAD311A04C009027B6BF68061E5655@SERVER20> Message-ID: <466EEAD6.5070204@web.de> Steve Brueckner wrote: > Why might the standard Fedora7 kernel work OK, but the Fedora7 xen kernel > not work? Is it perhaps because of missing drivers in the xen kernel? I can not say something specific regarding your hardware but I had a similar problem with Fedora 6 and a Dell Dimension system about 7 months ago. The problem was that the broadcom network chipset has some internal limitations regarding the memory address size it can address. At that time, Xen did not have a workaround for this so the linux driver (b44) won't work with a Xen kernel while working well with an standard kernel. So in essence, it may be a combination of hardware limitations and/or Xen that your hardware does not work with Xen. Maybe incomplete Linux drivers. Searching bugzilla helped me at that time :-) fs From ben at muppethouse.com Tue Jun 12 22:22:18 2007 From: ben at muppethouse.com (Ben Russo) Date: Tue, 12 Jun 2007 18:22:18 -0400 Subject: [Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won't start after install finishes. In-Reply-To: References: Message-ID: Ben Russo wrote: > Then Started Virtual Machine Manager GUI > Selected "New..." from File menu and followed the wizard. > then installed FULLY VIRTUALIZED > RH-72 from original Red Hat 7.2 CD's > this went fine with the > Virtual Machine Manager GUI "New Machine" wizard. > The only non-usual thing I did for an RH72 install was > to give it the kernel boot option mem=500M > > After the install completed, the DomU guest said it was now going to > reboot and I should remove any CD's. > > Then the DomU disappeared. > type "xm create -c /etc/xen/rh72-test", > I find out that the new guest gets a kernel panic on bootup > after the bootup menu > I found out that if I add the kernel option "nomxt" to the grub.conf kernel command for the DomU it gets much farther in the boot process. Now I get this on the console: ixmiestr2.9620000731 (Red Hat Linux 7.1 2.96-98)) #1 Thu Sep 6 17:27:27 EDT 2001 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) 0 - 00 000000003ff000 type 18 000000000a000 (e000000000 0000f000(sabe) BIOS-e820: 000000001f3ff000 - 000000001f400000 type 17 op... 18ghmem)000000fec00000 - 0000000100000000 tycngi Df Tiar D(20010327) Richard Goch (rgoochatnf.ciro.a) mrr: dtected mtrr type: Intel PC:CBSePCI: Probing PCI hardware CI: Using IRQ router PIIX [8086/7000] at 00:01.0 PCI: PIIX3: Enabling Passive Release on 00:01.0 Limiting direct PCI/PCI transfers. Activating ISA DMA hang workarounds. isapnp: Scanig orPn ad.un inx ET.0fo Lnu 24 BaedupnSwnsa nvesiy omutr ocet NT303 am:BIS erio .2Flg 003(rve vrson11) mx_san_bios: enter Starting kswapd v1.8 erwth MAY_PORTSMLTIPORTSHR_Q EA_I Sme lock Drive v.0dUnix98 ptysconfigured bk,102 lts per ueue RAMDISK driver n iserd tidebus=xx PIIX: IDE controller on PCI bus 00 dev 09 PIIX3: chipset revisn 0 PIIX3: nt 100% nativemode: iha:pio, hdb:pio ide1: BM-DM a0f d0 C/H/S=610/63fomha Then it hangs right there. From tom.horsley at att.net Tue Jun 12 22:56:15 2007 From: tom.horsley at att.net (Tom Horsley) Date: Tue, 12 Jun 2007 18:56:15 -0400 Subject: [Fedora-xen] Formatting pauses during install In-Reply-To: <166347C2-10C5-47B0-B1AE-87A740216B2B@rallydev.com> References: <166347C2-10C5-47B0-B1AE-87A740216B2B@rallydev.com> Message-ID: <20070612185615.6c8ccb21@zooty> On Tue, 12 Jun 2007 12:16:44 -0600 Tarun Reddy wrote: > I'm using Centos 5 dom0 on an x86_64 machine with 12GB of RAM. > > Tried to use virt-manager to install a Centos 4 domU (also tried with > Centos 5 domU) but the tool limits the disk to 16000 MB. So switch to > using virt-install and specified an 80GB disk. Everything proceed > well until "Formatting / file system" which stops at 11% (~8GB of the > 74GB / partition). Seems likely it might be the same bug as: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234160 If you look at the VM you are trying to install in the virt-manager app, is it using as much CPU as it can get? From treddy at rallydev.com Wed Jun 13 02:08:19 2007 From: treddy at rallydev.com (Tarun Reddy) Date: Tue, 12 Jun 2007 20:08:19 -0600 Subject: [Fedora-xen] Formatting pauses during install In-Reply-To: <20070612185615.6c8ccb21@zooty> References: <166347C2-10C5-47B0-B1AE-87A740216B2B@rallydev.com> <20070612185615.6c8ccb21@zooty> Message-ID: <509E1123-18F0-4A1E-9608-CD686088BFCF@rallydev.com> On Jun 12, 2007, at 4:56 PM, Tom Horsley wrote: > On Tue, 12 Jun 2007 12:16:44 -0600 > Tarun Reddy wrote: > >> I'm using Centos 5 dom0 on an x86_64 machine with 12GB of RAM. >> >> Tried to use virt-manager to install a Centos 4 domU (also tried with >> Centos 5 domU) but the tool limits the disk to 16000 MB. So switch to >> using virt-install and specified an 80GB disk. Everything proceed >> well until "Formatting / file system" which stops at 11% (~8GB of the >> 74GB / partition). > > Seems likely it might be the same bug as: > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234160 > > If you look at the VM you are trying to install in the virt-manager > app, is it using as much CPU as it can get? > Thank you for the pointer! The load on the host shows 1 x number of guest hosts during those pauses. It did eventually finish the install but it took almost 2 hours with a local Centos mirror! So looking at the bugzilla report, I noticed I didn't mention that I was using paravirtualized guest domains. Of course, the bug in bugzilla originally references fully virtualized guests. So, on a whim, I try a Centos 4.5 guest os fully virtualized. Apart from having to add noapic to my kernel boot line, it seems much more stable with no pauses at all. Go figure. I was hoping to use a paravirtualized since I thought it might be faster. Of course on a 32 bit Intel box (older Xeons), I have no issues with paravirtualized hosts, either Centos 5 or 4.5. Baffled, Tarun From cochranb at speakeasy.net Wed Jun 13 03:38:23 2007 From: cochranb at speakeasy.net (Robert L Cochran) Date: Tue, 12 Jun 2007 23:38:23 -0400 Subject: [Fedora-xen] Making Xen Guest Console Bigger Message-ID: <466F66AF.9010600@speakeasy.net> I'm brand new to using Xen. I've just successfully installed Fedora 7 as a guest system named F7guest with 618 Mb of memory and approximately 35 Gb of disk space. How do I make the console bigger so that I can actually work on applications? The default console is way too small -- the whole desktop window is about 6X6 inches. I need the actual desktop and application windows to fill my 19" monitor and be resizeable for them to be any good to me. Thanks Bob Cochran Greenbelt, Maryland, USA From itamar at ispbrasil.com.br Wed Jun 13 03:42:43 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Wed, 13 Jun 2007 00:42:43 -0300 Subject: [Fedora-xen] Making Xen Guest Console Bigger References: <466F66AF.9010600@speakeasy.net> Message-ID: <001801c7ad6c$e8dba350$fe01a8c0@ispbrasil> why you don't use putty or other ssh client? -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "Robert L Cochran" To: Sent: Wednesday, June 13, 2007 12:38 AM Subject: [Fedora-xen] Making Xen Guest Console Bigger > I'm brand new to using Xen. I've just successfully installed Fedora 7 as > a guest system named F7guest with 618 Mb of memory and approximately 35 > Gb of disk space. How do I make the console bigger so that I can > actually work on applications? The default console is way too small -- > the whole desktop window is about 6X6 inches. I need the actual desktop > and application windows to fill my 19" monitor and be resizeable for > them to be any good to me. > > Thanks > > Bob Cochran > Greenbelt, Maryland, USA > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From armbru at redhat.com Wed Jun 13 14:04:34 2007 From: armbru at redhat.com (Markus Armbruster) Date: Wed, 13 Jun 2007 16:04:34 +0200 Subject: [Fedora-xen] Making Xen Guest Console Bigger In-Reply-To: <466F66AF.9010600@speakeasy.net> (Robert L. Cochran's message of "Tue, 12 Jun 2007 23:38:23 -0400") References: <466F66AF.9010600@speakeasy.net> Message-ID: <87fy4wkl1p.fsf@pike.pond.sub.org> Robert L Cochran writes: > I'm brand new to using Xen. I've just successfully installed Fedora 7 as a guest system named F7guest with 618 Mb of memory and approximately 35 Gb of disk space. How do I make the console bigger so that I can actually work on applications? The default console is way too small -- > the whole desktop window is about 6X6 inches. I need the actual > desktop and application windows to fill my 19" monitor and be > resizeable for them to be any good to me. Assuming your talking about the graphical console (a.k.a. para-virtual framebuffer): sorry, that one isn't resizable, yet. From treddy at rallydev.com Wed Jun 13 16:13:55 2007 From: treddy at rallydev.com (Tarun Reddy) Date: Wed, 13 Jun 2007 10:13:55 -0600 Subject: [Fedora-xen] Formatting pauses during install In-Reply-To: <509E1123-18F0-4A1E-9608-CD686088BFCF@rallydev.com> References: <166347C2-10C5-47B0-B1AE-87A740216B2B@rallydev.com> <20070612185615.6c8ccb21@zooty> <509E1123-18F0-4A1E-9608-CD686088BFCF@rallydev.com> Message-ID: <4D923FDB-8B1D-4EE2-9E81-07355833348A@rallydev.com> On Jun 12, 2007, at 8:08 PM, Tarun Reddy wrote: > > On Jun 12, 2007, at 4:56 PM, Tom Horsley wrote: > >> On Tue, 12 Jun 2007 12:16:44 -0600 >> Tarun Reddy wrote: >> >>> I'm using Centos 5 dom0 on an x86_64 machine with 12GB of RAM. >>> >>> Tried to use virt-manager to install a Centos 4 domU (also tried >>> with >>> Centos 5 domU) but the tool limits the disk to 16000 MB. So >>> switch to >>> using virt-install and specified an 80GB disk. Everything proceed >>> well until "Formatting / file system" which stops at 11% (~8GB of >>> the >>> 74GB / partition). >> >> Seems likely it might be the same bug as: >> >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234160 >> >> If you look at the VM you are trying to install in the virt-manager >> app, is it using as much CPU as it can get? >> > Thank you for the pointer! The load on the host shows 1 x number of > guest hosts during those pauses. It did eventually finish the > install but it took almost 2 hours with a local Centos mirror! > > So looking at the bugzilla report, I noticed I didn't mention that > I was using paravirtualized guest domains. Of course, the bug in > bugzilla originally references fully virtualized guests. So, on a > whim, I try a Centos 4.5 guest os fully virtualized. Apart from > having to add noapic to my kernel boot line, it seems much more > stable with no pauses at all. Go figure. > > I was hoping to use a paravirtualized since I thought it might be > faster. > > Of course on a 32 bit Intel box (older Xeons), I have no issues > with paravirtualized hosts, either Centos 5 or 4.5. > Less baffled now. The difference between the pause state and non-paused state is *not* para versus fully virtualized systems as I thought. Rather it was sparse versus non-sparse disk images. I had started using virt-install since I couldn't get virt-manager to set up a disk image bigger that 16GB. By default virt-install uses sparse disks (versus virt-manager which defaults to non-sparse disks). Hence, the dramatic pauses that involved anything large I/O to the disk. Fortunately, there are nice command line switches that allow changing of that and I am now running paravirtualized Centos 5 guest without pauses (Centos 4.5 installing as we speak). Thanks for your help! Tarun From ghuber at vanteon.com Wed Jun 13 14:44:04 2007 From: ghuber at vanteon.com (Greg Huber) Date: Wed, 13 Jun 2007 10:44:04 -0400 Subject: [Fedora-xen] F7 guest on a F7 host Message-ID: <467002B4.2040608@vanteon.com> I'm trying to install a F7 guest on a fresh F7 host. I get all the way through virt-install and then open the guest. I see a blip of text and then the screen goes blank and nothing further happens, no disk or CDROM activity, and certainly no install screen. After I 'shutdown' and 'run' I get.... HVMAssist BIOS, 1 cpu, $Revision: 1.38 $ $Date: 2005/05/07 15:55:26 $ ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (16400 MBytes) ata0 slave: Unknown device Booting from Hard Disk Boot from Hard Disk failed: not a bootable disk FATAL: No Bootable device. Which I assume means that nothing got loaded to the guest. The same happens in text mode also. If, however, I use a Fedora Core 6 install disk or a Windows XP install disk, I can complete the install. I used the F7 install disk to build the host system and the media has been checked. I also tried NFS mounting the image from another machine. Thank You. -- Greg Huber Principal Engineer Vanteon Corporation 255 Woodcliff Drive, Suite 200 Fairport, NY 14450 Office: (585) 419-9564 Fax: (585) 248-0537 www.vanteon.com - Embedded for Your Future From edward.pasek at carspotpro.com Wed Jun 13 20:23:37 2007 From: edward.pasek at carspotpro.com (Edward Pasek) Date: Wed, 13 Jun 2007 15:23:37 -0500 Subject: [Fedora-xen] fedora core 7 and Xen Message-ID: <1181766217.5332.18.camel@futhark> After numerous attempts to get anything running as a guest OS I continue to run into errors. I have tried each install method atleast 4 times from the quickstart guide. So far my results under fedora 7 and Xen have failed. So far if I try to install core 6 or fedora 7 i386 I get kernel panics and this dump ?????????? Loading SCSI driver ??????????? ? ? ? Loading xenblk driver...Oops: 0000 [#1]? SMP ? ? last sysfs file: ?????????????????????????????????????????? Modules linked in: xenblk xennet iscsi_tcp libiscsi scsi_transport_iscsi sr_mod sd_mod scsi_mod ide_cd cdrom ipv6 squashfs pcspkr loop nfs nfs_acl fscache lockd sunrpc vfat fat cramfs CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010887 (2.6.18-1.2798.fc6xen #1) EIP is at blkif_int+0x5a/0x16b [xenblk] eax: 18009c00 ebx: ed736000 ecx: c1948e0c edx: 00000002 esi: 00000000 edi: ca000100 ebp: ed7210ac esp: c078afa0 ds: 007b es: 007b ss: 0069 Process init (pid: 225, ti=c078a000 task=c1946660 task.ti=c1948000)screen Stack: f72a0aa6 00000001 00000002 00000000 fffee3b3 c0e2dd80 00000000 00000000 00000106 c0441be6 c1948e0c c06d3700 00000106 c1948e0c c06d3728 c0441ca6 c0735f80 c1948e0c c0e2dd80 c1948dd0 00000106 c1948e0c fffffffe c0406ca8 Call Trace: [] handle_IRQ_event+0x27/0x51 [] __do_IRQ+0x96/0xf2 [] do_IRQ+0x9e/0xbc ======================= Code: e8 89 f6 8b 43 20 89 44 24 04 e9 c3 00 00 00 8b 43 24 31 f6 48 23 44 24 04 6b c0 6c 8d 68 40 03 6b 28 8b 7d 00 69 c7 9c 00 00 00 <8b> 94 18 e8 00 00 00 8d 44 18 7c 89 44 24 10 89 14 24 eb 12 8b EIP: [] blkif_int+0x5a/0x16b [xenblk] SS:ESP 0069:c if I install the x86_64 it just hangs and I get this in xm dmesg (XEN) *** Serial input -> DOM0 (type \047CTRL-a\047 three times to switch input to Xen). (XEN) grant_table.c:265:d0 Bad flags (0) or dom (0). (expected dom 0) I've disabled selinux, tried building my image in /var/lib/xen/images/ and several other places. I've removed and reinstalled xen virt-maanger kernel-xen, I've tried an upgrade from 6-7, changed settings in my config for cpus, mem, ethernet bridging. I'm running Xen on a dell 2900 with 4 Xeons (x86_64) with the vt flags, 8 gb ram and a 1000 gigs of disk space. From cyoung at cascadiasoftware.com Thu Jun 14 00:45:44 2007 From: cyoung at cascadiasoftware.com (Chris Young) Date: Wed, 13 Jun 2007 17:45:44 -0700 Subject: [Fedora-xen] multiple CD ISO image files with qemu-kvm and virt-manager on F7 Message-ID: <46708FB8.2010706@cascadiasoftware.com> I can't seem to get access to the qemu monitor console to change the location of the cdrom and point it to the next iso image file using virt-manager. Ctrl-Alt-2 sends me to the serial0 console and Ctrl-Alt-3 sends me to the parallel0 console, both of which don't respond to keyboard events as far as I can tell. Is there any other way of connecting to the qemu monitor console? -- Chris Young President Cascadia Software tel 253-896-4000 x103 cel 425-260-4942 cyoung at cascadiasoftware.com http://cascadiasoftware.com From m3freak at thesandhufamily.ca Fri Jun 15 01:29:10 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Thu, 14 Jun 2007 21:29:10 -0400 Subject: [Fedora-xen] can't create domU after failed install Message-ID: <1181870950.18059.7.camel@krs> Hello Everyone, I'm trying to use virt-install for the first time to create a paravirtualized CentOS 5 domU on a Fedora Core 6 dom0. Here's the command I used: virt-install -n pbx -r 256 --vcpus=1 -m 00:16:3E:66:94:5D --vnc krs -p -l http://blizzard/mirror/centos/5/os/i386 I'm then prompted to enter the disk I want to use, at which point I enter "/dev/vg00/asterisk" (a LV I previously created). At this point, the install appears to start, but eventually fails, giving this reason: Starting install... ERROR: Domain named pbx already exists! There was a "pbx" config file in /etc/xen, but even after deleting it, I get the same error when I try to recreate the domU. I assume I can clear this from "memory", but how? Rebooting dom0 doesn't help, so I'm assuming virt-install is pulling that info from somewhere. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 21:11:04 up 5 days, 11:59, 5 users, load average: 0.71, 0.64, 0.54 From berrange at redhat.com Fri Jun 15 02:22:47 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 15 Jun 2007 03:22:47 +0100 Subject: [Fedora-xen] can't create domU after failed install In-Reply-To: <1181870950.18059.7.camel@krs> References: <1181870950.18059.7.camel@krs> Message-ID: <20070615022247.GB18778@redhat.com> On Thu, Jun 14, 2007 at 09:29:10PM -0400, Kanwar Ranbir Sandhu wrote: > Hello Everyone, > > I'm trying to use virt-install for the first time to create a > paravirtualized CentOS 5 domU on a Fedora Core 6 dom0. Here's the > command I used: > > virt-install -n pbx -r 256 --vcpus=1 -m 00:16:3E:66:94:5D --vnc krs -p What is this 'krs' arg you're providing ^^^^^^ ? > -l http://blizzard/mirror/centos/5/os/i386 > > I'm then prompted to enter the disk I want to use, at which point I > enter "/dev/vg00/asterisk" (a LV I previously created). At this point, > the install appears to start, but eventually fails, giving this reason: BTW, you can use --file /dev/vg00/asterisk to specify the disk on the command line. > Starting install... > ERROR: Domain named pbx already exists! > > There was a "pbx" config file in /etc/xen, but even after deleting it, I > get the same error when I try to recreate the domU. Try 'virsh undefine pbx' to ensure all trace is removed. Regards, 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 -=| From m3freak at thesandhufamily.ca Fri Jun 15 02:55:33 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Thu, 14 Jun 2007 22:55:33 -0400 Subject: [Fedora-xen] can't create domU after failed install In-Reply-To: <20070615022247.GB18778@redhat.com> References: <1181870950.18059.7.camel@krs> <20070615022247.GB18778@redhat.com> Message-ID: <1181876133.18059.16.camel@krs> On Fri, 2007-06-15 at 03:22 +0100, Daniel P. Berrange wrote: > > virt-install -n pbx -r 256 --vcpus=1 -m 00:16:3E:66:94:5D --vnc krs -p > > What is this 'krs' arg you're providing ^^^^^^ ? That's me being gay. I thought I could specify an argument to "--vnc" to get the vnc connection on my local desktop (I ssh'ed to the dom0 machine to start a remote install). Eventually I figured out what the --vnc option was for, and removed the "krs" (my laptop's hostname). > BTW, you can use --file /dev/vg00/asterisk to specify the disk > on the command line. Yep - started to do that after reading the man page again. > > There was a "pbx" config file in /etc/xen, but even after deleting it, I > > get the same error when I try to recreate the domU. > > Try 'virsh undefine pbx' to ensure all trace is removed. Is that in the man page? Anyway, I noticed that the pbx domU was actually running - that is, the install had started, but since I had ssh'ed to the dom0 machine, DISPLAY wasn't set. So, the vnc session couldn't start. It was waiting for me to connect to "localhost:5900". I destroyed the pbx domU, forwarded vnc ports over ssh, restarted the install, and connected to "localhost:5900" on my laptop. I proceeded with the install at that point. Yeah! Only hang up: the graphical install failed, which forced me to do a text install via the vnc session. I'm not sure why that happened. Any ideas? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 22:53:51 up 5 days, 13:42, 5 users, load average: 0.72, 0.59, 0.61 From m3freak at thesandhufamily.ca Fri Jun 15 03:10:38 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Thu, 14 Jun 2007 23:10:38 -0400 Subject: [Fedora-xen] virt-manager and guest config file In-Reply-To: <466816D3.4040400@redhat.com> References: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> <20070606161116.GJ18020@redhat.com> <7675761b0706060919j2c5c3e78y5c44b9c55f712fbf@mail.gmail.com> <466816D3.4040400@redhat.com> Message-ID: <1181877038.18059.20.camel@krs> On Thu, 2007-06-07 at 15:31 +0100, Richard W.M. Jones wrote: > Using virsh, you can do this on an inactive (not running) domain: > > virsh dumpxml DOMAINNAME > guest.xml > vi guest.xml > virsh define guest.xml I just tried this, and it didn't work. I had to "undefine" the guest before I could define it again: ... virsh undefine DOMAINNAME virsh define guest.xml Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 23:07:00 up 5 days, 13:55, 5 users, load average: 0.48, 0.66, 0.64 From johan.dewit at external.thalesaleniaspace.com Fri Jun 15 06:02:52 2007 From: johan.dewit at external.thalesaleniaspace.com (Johan De Wit) Date: Fri, 15 Jun 2007 08:02:52 +0200 Subject: [Fedora-xen] Removing PAE support in kernel-xen Message-ID: <1181887372.6745.12.camel@localhost.hobsite.be> Hi all, I want to use xen and the virtualisation tools provided in FC7. This will be running on my laptop, which has no PAE support, since the max ram = 2GB. I already rebuilded the kerne-xen package, and removed pae support. kernel-xen.spec line 94 %ifarch i686 %define buildpae 0 %define builddebug 0 # we build always xen HV with pae %define xen_flags verbose=y crash_debug=y <--- change this line, remove the pae bit %endif And in SOURCES/kernel-2.6.20-i686-xen.config at the end # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM4G=y But when installing an new xen guest with virt-manager, this doesn't work. I've setup a local repo, and now i'm looking to get rid of the pae stuff that is builtin the /images/xen/[vmlinuz| initrd.img] Overwriting the vmlinuz with the kernel I rebuild with the above steps doesnt't work well. Searching the web didn't get me to a solution. Could someone please direct me to a solution ? I've looked into anaconda, revision etc, but still cannot figure out how to fix my problem. Thanks Johan From berrange at redhat.com Fri Jun 15 11:51:07 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 15 Jun 2007 12:51:07 +0100 Subject: [Fedora-xen] can't create domU after failed install In-Reply-To: <1181876133.18059.16.camel@krs> References: <1181870950.18059.7.camel@krs> <20070615022247.GB18778@redhat.com> <1181876133.18059.16.camel@krs> Message-ID: <20070615115106.GA4011@redhat.com> On Thu, Jun 14, 2007 at 10:55:33PM -0400, Kanwar Ranbir Sandhu wrote: > On Fri, 2007-06-15 at 03:22 +0100, Daniel P. Berrange wrote: > > > virt-install -n pbx -r 256 --vcpus=1 -m 00:16:3E:66:94:5D --vnc krs -p > > > > What is this 'krs' arg you're providing ^^^^^^ ? > > That's me being gay. I thought I could specify an argument to "--vnc" > to get the vnc connection on my local desktop (I ssh'ed to the dom0 > machine to start a remote install). Eventually I figured out what the > --vnc option was for, and removed the "krs" (my laptop's hostname). > > > BTW, you can use --file /dev/vg00/asterisk to specify the disk > > on the command line. > > Yep - started to do that after reading the man page again. > > > > There was a "pbx" config file in /etc/xen, but even after deleting it, I > > > get the same error when I try to recreate the domU. > > > > Try 'virsh undefine pbx' to ensure all trace is removed. > > Is that in the man page? Anyway, I noticed that the pbx domU was > actually running - that is, the install had started, but since I had > ssh'ed to the dom0 machine, DISPLAY wasn't set. So, the vnc session > couldn't start. It was waiting for me to connect to "localhost:5900". > > I destroyed the pbx domU, forwarded vnc ports over ssh, restarted the > install, and connected to "localhost:5900" on my laptop. I proceeded > with the install at that point. Yeah! > > Only hang up: the graphical install failed, which forced me to do a text > install via the vnc session. I'm not sure why that happened. Any > ideas? Not enough RAM probably - try increasing to 300-400 MB just for the install time. 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 -=| From armbru at redhat.com Fri Jun 15 13:15:49 2007 From: armbru at redhat.com (Markus Armbruster) Date: Fri, 15 Jun 2007 15:15:49 +0200 Subject: [Fedora-xen] multiple CD ISO image files with qemu-kvm and virt-manager on F7 In-Reply-To: <46708FB8.2010706@cascadiasoftware.com> (Chris Young's message of "Wed, 13 Jun 2007 17:45:44 -0700") References: <46708FB8.2010706@cascadiasoftware.com> Message-ID: <878xalfjei.fsf@pike.pond.sub.org> Chris Young writes: > I can't seem to get access to the qemu monitor console to change the > location of the cdrom and point it to the next iso image file using > virt-manager. Ctrl-Alt-2 sends me to the serial0 console and > Ctrl-Alt-3 > sends me to the parallel0 console, both of which don't respond to > keyboard events as far as I can tell. > > Is there any other way of connecting to the qemu monitor console? You might find this thread helpful: http://lists.xensource.com/archives/html/xen-devel/2007-06/msg00437.html From ben at muppethouse.com Fri Jun 15 14:44:51 2007 From: ben at muppethouse.com (Ben Russo) Date: Fri, 15 Jun 2007 10:44:51 -0400 Subject: [Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won't start after install finishes. In-Reply-To: References: Message-ID: Ben Russo wrote: > Ben Russo wrote: >> installed FULLY VIRTUALIZED >> RH-72 from original Red Hat 7.2 CD's >> this went fine >> type "xm create -c /etc/xen/rh72-test", >> I find out that the new guest gets a kernel panic on bootup >> after the bootup menu > I found out that if I add the kernel option "nomxt" to the > grub.conf kernel command for the DomU it gets much farther > in the boot process. > > Now I get this on the console: > > console hangs at scanning QEMU HARDDISK ide drive > > > Then it hangs right there. I give up. Looks like running fully virtualized old versions of Linux just isn't going to work smoothly. I'm going to use VMware ESX server instead. From kjs.pub at gmail.com Fri Jun 15 19:40:57 2007 From: kjs.pub at gmail.com (Karl J South) Date: Fri, 15 Jun 2007 21:40:57 +0200 Subject: [Fedora-xen] Removing PAE support in kernel-xen In-Reply-To: <1181887372.6745.12.camel@localhost.hobsite.be> References: <1181887372.6745.12.camel@localhost.hobsite.be> Message-ID: Hi, On 6/15/07, Johan De Wit wrote: > Hi all, > > I want to use xen and the virtualisation tools provided in FC7. This > will be running on my laptop, which has no PAE support, since the max > ram = 2GB. I'm in the same situation and just wanted to wish you good luck with this project and kindly ask you to make the necessary changes available in one way or another to everyone else that is in the same situation. > I already rebuilded the kerne-xen package, and removed pae support. > > kernel-xen.spec line 94 > > %ifarch i686 > %define buildpae 0 > %define builddebug 0 > # we build always xen HV with pae > %define xen_flags verbose=y crash_debug=y <--- change this line, > remove the pae bit > %endif > > And in SOURCES/kernel-2.6.20-i686-xen.config at the end > > # CONFIG_HIGHMEM64G is not set > CONFIG_HIGHMEM4G=y > > But when installing an new xen guest with virt-manager, this doesn't > work. I've setup a local repo, and now i'm looking to get rid of the > pae stuff that is builtin the /images/xen/[vmlinuz| > initrd.img] > > Overwriting the vmlinuz with the kernel I rebuild with the above steps > doesnt't work well. > > Searching the web didn't get me to a solution. > > Could someone please direct me to a solution ? I've looked into > anaconda, revision etc, but still cannot figure out how to fix my > problem. > > Thanks > > Johan /kjs From John.Sanabria at ece.uprm.edu Sat Jun 16 12:20:19 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Sat, 16 Jun 2007 08:20:19 -0400 (AST) Subject: [Fedora-xen] network problem after upgrade... Message-ID: <45668.74.213.77.173.1181996419.squirrel@ece.uprm.edu> hi, i had two machines (shutdown and init) dedicated as domain0 with fc6 and xen installed. Both machines has guest domains deployed. Last days, i decided to update the shutdown machine with kernel and xen packages, using update software tool (aka. pup). As consequence my old guest domains in shutdown machine has network problems, cannot communicate outside, then i decide to deploy a new guest domain, after to updating process, and it does not have any problems. The problem appear with old guest domains. :-( But, the old guest domains in init machine (with no updates) work properly. any suggestion? thanks a lot. init xen-packages and kernel running version kernel-xen.i686 2.6.19-1.2911.6.5.fc6 installed kernel-xen.i686 2.6.18-1.2798.fc6 installed xen.i386 3.0.3-6.fc6 installed xen-libs.i386 3.0.3-6.fc6 installed (uname -a) Linux init 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux shutdown xen-packages and kernel running version kernel-xen.i686 2.6.20-1.2952.fc6 installed kernel-xen.i686 2.6.19-1.2911.6.4.fc6 installed xen.i386 3.0.3-9.fc6 installed xen-libs.i386 3.0.3-9.fc6 installed (uname -a) Linux shutdown 2.6.19-1.2911.6.4.fc6xen #1 SMP Sat Feb 24 14:57:17 EST 2007 i686 i686 i386 GNU/Linux http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From m3freak at thesandhufamily.ca Sat Jun 16 13:30:27 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Sat, 16 Jun 2007 09:30:27 -0400 Subject: [Fedora-xen] resizing Xen para-virtualized guest partition In-Reply-To: References: <463F5E53.80600@redhat.com> Message-ID: <1182000627.18059.29.camel@krs> On Mon, 2007-05-07 at 15:07 -0400, Paul Wouters wrote: > You do not need LVM for that provided you have the disk space on the dom0: > > dd if=/dev/zero bs=1M count=1024 >> /var/lib/xen/images/guest.dsk > e2fsck -f /var/lib/xen/images/guest.dsk > resize2fs /var/lib/xen/images/guest.dsk > e2fsck -f /var/lib/xen/images/guest.dsk How do you do this if one installs the domU in a LV on dom0? I thought I could simply lvextend the dom0 LV, boot the domU, and then lv/vg/pv extend inside the domU, but that didn't work. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 09:22:03 up 7 days, 10 min, 2 users, load average: 0.09, 0.29, 0.33 From m3freak at thesandhufamily.ca Sat Jun 16 13:48:32 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Sat, 16 Jun 2007 09:48:32 -0400 Subject: [Fedora-xen] resizing Xen para-virtualized guest partition In-Reply-To: <1182000627.18059.29.camel@krs> References: <463F5E53.80600@redhat.com> <1182000627.18059.29.camel@krs> Message-ID: <1182001712.18059.34.camel@krs> On Sat, 2007-06-16 at 09:30 -0400, Kanwar Ranbir Sandhu wrote: > How do you do this if one installs the domU in a LV on dom0? I thought > I could simply lvextend the dom0 LV, boot the domU, and then lv/vg/pv > extend inside the domU, but that didn't work. Let me add that I realize the domU file system needs to be resized now, but I haven't been able to figure out how to do that with "virt-install" created domUs. I also haven't figured out how to mount the LV domU file system in dom0. This only mounts /boot (which is in the domU) on dom0: lomount -t lvm -diskimage /dev/vg00/asterisk -partition 2 /mnt/xen/ Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 09:44:44 up 7 days, 32 min, 2 users, load average: 0.29, 0.49, 0.39 From John.Sanabria at ece.uprm.edu Sat Jun 16 02:24:54 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Fri, 15 Jun 2007 22:24:54 -0400 (AST) Subject: [Fedora-xen] network problem after upgrade... Message-ID: <52710.74.213.77.173.1181960694.squirrel@ece.uprm.edu> hi, i had two machines (shutdown and init) dedicated as domain0 with fc6 and xen installed. Both machines has guest domains deployed. Last days, i decided to update the shutdown machine with kernel and xen packages, using update software tool (aka. pup). As consequence my old guest domains in shutdown machine has network problems, cannot communicate outside, then i decide to deploy a new guest domain, after to updating process, and it does not have any problems. The problem appear with old guest domains. :-( But, the old guest domains in init machine (with no updates) work properly. any suggestion? thanks a lot. init xen-packages and kernel running version kernel-xen.i686 2.6.19-1.2911.6.5.fc6 installed kernel-xen.i686 2.6.18-1.2798.fc6 installed xen.i386 3.0.3-6.fc6 installed xen-libs.i386 3.0.3-6.fc6 installed (uname -a) Linux init 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux shutdown xen-packages and kernel running version kernel-xen.i686 2.6.20-1.2952.fc6 installed kernel-xen.i686 2.6.19-1.2911.6.4.fc6 installed xen.i386 3.0.3-9.fc6 installed xen-libs.i386 3.0.3-9.fc6 installed (uname -a) Linux shutdown 2.6.19-1.2911.6.4.fc6xen #1 SMP Sat Feb 24 14:57:17 EST 2007 i686 i686 i386 GNU/Linux http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From m3freak at thesandhufamily.ca Sat Jun 16 16:44:45 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Sat, 16 Jun 2007 12:44:45 -0400 Subject: [Fedora-xen] resizing Xen para-virtualized guest partition In-Reply-To: <1182001712.18059.34.camel@krs> References: <463F5E53.80600@redhat.com> <1182000627.18059.29.camel@krs> <1182001712.18059.34.camel@krs> Message-ID: <1182012285.18059.43.camel@krs> On Sat, 2007-06-16 at 09:48 -0400, Kanwar Ranbir Sandhu wrote: > Let me add that I realize the domU file system needs to be resized now, > but I haven't been able to figure out how to do that with "virt-install" > created domUs. > > I also haven't figured out how to mount the LV domU file system in dom0. > This only mounts /boot (which is in the domU) on dom0: > > lomount -t lvm -diskimage /dev/vg00/asterisk -partition 2 /mnt/xen/ I figured how to use kpartx to mount the domU LV in dom0. I'm still clued out on how to actually get the LV in the domU to see the bigger dom0 LV it's installed in. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 11:19:55 up 7 days, 2:08, 2 users, load average: 0.51, 0.39, 0.26 From m3freak at thesandhufamily.ca Sun Jun 17 05:53:49 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Sun, 17 Jun 2007 01:53:49 -0400 Subject: [Fedora-xen] virt-manager and guest config file In-Reply-To: <467299DE.8010403@redhat.com> References: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> <20070606161116.GJ18020@redhat.com> <7675761b0706060919j2c5c3e78y5c44b9c55f712fbf@mail.gmail.com> <466816D3.4040400@redhat.com> <1181877038.18059.20.camel@krs> <467299DE.8010403@redhat.com> Message-ID: <1182059629.18059.51.camel@krs> On Fri, 2007-06-15 at 09:53 -0400, Hugh Brock wrote: > >> virsh dumpxml DOMAINNAME > guest.xml > >> vi guest.xml > >> virsh define guest.xml > > > > I just tried this, and it didn't work. I had to "undefine" the guest > > before I could define it again: > > > > Hmm, it should work... what do you mean by "it didn't work?" Error message? Here's what happens: 1. I do a a xml dump of the domU: [root at xenmaster xen]# virsh dumpxml asterisk > guest.xml libvir: error : failed to read configuration file /etc/xen/guest.xml Though there's an error, guest.xml is created and looks okay. 2. I try to define the domU with the xml file I just dumped (after editing the RAM parameters): [root at xenmaster xen]# virsh define guest.xml libvir: error : configuration file syntax error: expecting a name libvir: Xen Daemon error : internal error domain with name already exists error: Failed to define domain from guest.xml I check domU config file, and nothing has changed: the define really did fail. 3. I undefine said domU: [root at xenmaster xen]# virsh undefine asterisk libvir: error : configuration file syntax error: expecting a name Domain asterisk has been undefined The asterisk config has been deleted, so it looks good so far. 4. I again try to define the asterisk domU with the xml file I dumped earlier: [root at xenmaster xen]# virsh define guest.xml libvir: error : configuration file syntax error: expecting a name Domain asterisk defined from guest.xml I check the domU config, and it's been updated with the changes I made to the xml dump. I hope that helps. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 01:47:34 up 7 days, 16:35, 1 user, load average: 0.78, 0.50, 0.40 From jlayton at redhat.com Sun Jun 17 10:26:59 2007 From: jlayton at redhat.com (Jeff Layton) Date: Sun, 17 Jun 2007 06:26:59 -0400 Subject: [Fedora-xen] resizing Xen para-virtualized guest partition In-Reply-To: <1182000627.18059.29.camel@krs> References: <463F5E53.80600@redhat.com> <1182000627.18059.29.camel@krs> Message-ID: <20070617062659.15e34645.jlayton@redhat.com> On Sat, 16 Jun 2007 09:30:27 -0400 Kanwar Ranbir Sandhu wrote: > On Mon, 2007-05-07 at 15:07 -0400, Paul Wouters wrote: > > You do not need LVM for that provided you have the disk space on the dom0: > > > > dd if=/dev/zero bs=1M count=1024 >> /var/lib/xen/images/guest.dsk > > e2fsck -f /var/lib/xen/images/guest.dsk > > resize2fs /var/lib/xen/images/guest.dsk > > e2fsck -f /var/lib/xen/images/guest.dsk > > How do you do this if one installs the domU in a LV on dom0? I thought > I could simply lvextend the dom0 LV, boot the domU, and then lv/vg/pv > extend inside the domU, but that didn't work. > > Regards, > > Ranbir So your entire xen disk is a LV in dom0, and the domU is using that disk for the /boot partition and a PV for its own VG... Resize the LV in dom0: root at dom0# lvresize -L +5G /dev/VolGroup00/xendisk ...boot the domU. Run fdisk or some other partitioning utility in the domU. Resize the partition there: root at domU# fdisk /dev/xvda ...reboot the domU, since it'll still be in use. When it comes back, it should see the new partition table. Now (assuming the PV for the domU volgroup is /dev/xvda2): root at domU# pvresize /dev/xvda2 ...now the volgroup in the domU should see the new PE's. Resize the LV's and extend the filesystem in the domU as you normally would. I've done this several times and it's worked fine for me. There should be no reason to import the VG into the dom0, unless you want to shrink the domU root partition or something. -- Jeff Layton From oehmes at de.ibm.com Sun Jun 17 14:12:10 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Sun, 17 Jun 2007 16:12:10 +0200 Subject: [Fedora-xen] F7 System crash with high network load Message-ID: Hi, i experienced it now a couple of time that my Dom0 will get unstable if i copy a lot of files over a gigabit link using rsync into the dom0. That happens even, when there is no workload on the system beside this process at all. How to reproduce : rsync -avuzP --delete --progress /home/user1 xenhost:/home/user1 the rsync will start and after a few minutes the remote host (xen) is no longer responding on the network. when i look at the console of the xen host, it prints millions of : [] syscall_call+0x7/0xb only a hard reset helps now .. environment : xen-libs-3.1.0-2.fc7 xen-3.1.0-2.fc7 kernel-xen-2.6.20-2925.11.fc7 kernel-xen-devel-2.6.20-2925.11.fc7 so i assume it is a f7 kernel-xen bug .. is this known, as i haven't found anything in bugzilla .. should i open a ticket against f7 ? thanks . Sven -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Sun Jun 17 16:13:56 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 17 Jun 2007 17:13:56 +0100 Subject: [Fedora-xen] virt-manager and guest config file In-Reply-To: <1182059629.18059.51.camel@krs> References: <7675761b0706060907t354f2966u68e83f45a2730322@mail.gmail.com> <20070606161116.GJ18020@redhat.com> <7675761b0706060919j2c5c3e78y5c44b9c55f712fbf@mail.gmail.com> <466816D3.4040400@redhat.com> <1181877038.18059.20.camel@krs> <467299DE.8010403@redhat.com> <1182059629.18059.51.camel@krs> Message-ID: <20070617161356.GB12121@redhat.com> On Sun, Jun 17, 2007 at 01:53:49AM -0400, Kanwar Ranbir Sandhu wrote: > On Fri, 2007-06-15 at 09:53 -0400, Hugh Brock wrote: > > >> virsh dumpxml DOMAINNAME > guest.xml > > >> vi guest.xml > > >> virsh define guest.xml > > > > > > I just tried this, and it didn't work. I had to "undefine" the guest > > > before I could define it again: > > > > > > > Hmm, it should work... what do you mean by "it didn't work?" Error message? > > Here's what happens: > > 1. I do a a xml dump of the domU: > > [root at xenmaster xen]# virsh dumpxml asterisk > guest.xml > libvir: error : failed to read configuration file /etc/xen/guest.xml > > Though there's an error, guest.xml is created and looks okay. Were you in the /etc/xen directory when you ran that command ? It looks like you were since it mentions /etc/xen/guest.xml Basically /etc/xen should only ever contain the master Xen config files. Never create any other type of files in there. In this case the guest.xml file is getting parsed as if it were a Xen config file & thus you see the error. > 2. I try to define the domU with the xml file I just dumped (after editing the RAM parameters): > > [root at xenmaster xen]# virsh define guest.xml > libvir: error : configuration file syntax error: expecting a name > libvir: Xen Daemon error : internal error domain with name already exists > error: Failed to define domain from guest.xml > > I check domU config file, and nothing has changed: the define really did fail. That's a bug. If you update to the recently released 0.2.3 libvirt RPMs it should be fixed. We pushed them to Fedora last week IIRC, although its possible they're still only in updates-testing. With the new version you should be able to define the VM, without first having to undefine it. 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 -=| From johan.dewit at external.thalesaleniaspace.com Mon Jun 18 06:13:27 2007 From: johan.dewit at external.thalesaleniaspace.com (Johan De Wit) Date: Mon, 18 Jun 2007 08:13:27 +0200 Subject: [Fedora-xen] Removing PAE support in kernel-xen In-Reply-To: References: <1181887372.6745.12.camel@localhost.hobsite.be> Message-ID: <1182147207.6345.21.camel@localhost.hobsite.be> Hi, Seems I,m a litle bit closer now. I can now start the installation process using virt-manager. I tried to update the installation kernel-xen RPMS in the installation tree wuith the nopae version. Installation then hangs on the preparing installation - could take some tiem" screen. (left it running overnight.) The quest consules cpu, and netstat reviels a lot of http traffic. Before i did the update, installation did work, except after the reboot, the PAE kernel is installed with the obvious result that the guest aborts. Did this on both CentOS5.0 and FC7 Suspecting i did something wrong updatuing the installation tree. (- Replacing the RPMS - Ran createrepo --> seems soemthing else needs to be done also. Need to google for it) ) removing the PAE support in the /images/xen : cp /boot/vmlnuz-nopae /images/xen/vmlinuz Modify the initrd modules: mkdir /tmp/image cd /tmp/image gzip -cd //i386/images/xen/initrd.img | cpio -imd --quiet cd modules mkdir modimage cd modimage gzip -cd ../modules.cgz | cpio -imd --quiet !! we have the pae enabled kernel modules here. mkdir 'uname -r' (eg 2.6.20-2925.9.nopae.fc7xen) cd 'uname -r' mkdir i686 cd i686 for i in ../../2.6.20-2925.9.fc7xen/i686/*; do find /lib/modules/2.6.20-2925.9.nopae.fc7xen -name `basename $i` -exec cp {} . \; ; done Copy the pae disabled kernelmodules ! cd ../.. rm pae anabled kernelmodules find . |cpio --quiet -c -o | gzip -9 -n > ../modules.cgz cd .. rm -rf modimages find . |cpio --quiet -c -o | gzip -9 -n > //i386/images/xen/initrd.img cleanup Sorry for the mess. I will put it in some proper text later on. Wish me luck Johan On Fri, 2007-06-15 at 21:40 +0200, Karl J South wrote: > Hi, > > On 6/15/07, Johan De Wit wrote: > > Hi all, > > > > I want to use xen and the virtualisation tools provided in FC7. This > > will be running on my laptop, which has no PAE support, since the max > > ram = 2GB. > > I'm in the same situation and just wanted to wish you good luck with > this project and kindly ask you to make the necessary changes > available in one way or another to everyone else that is in the same > situation. > > > I already rebuilded the kerne-xen package, and removed pae support. > > > > kernel-xen.spec line 94 > > > > %ifarch i686 > > %define buildpae 0 > > %define builddebug 0 > > # we build always xen HV with pae > > %define xen_flags verbose=y crash_debug=y <--- change this line, > > remove the pae bit > > %endif > > > > And in SOURCES/kernel-2.6.20-i686-xen.config at the end > > > > # CONFIG_HIGHMEM64G is not set > > CONFIG_HIGHMEM4G=y > > > > But when installing an new xen guest with virt-manager, this doesn't > > work. I've setup a local repo, and now i'm looking to get rid of the > > pae stuff that is builtin the /images/xen/[vmlinuz| > > initrd.img] > > > > Overwriting the vmlinuz with the kernel I rebuild with the above steps > > doesnt't work well. > > > > Searching the web didn't get me to a solution. > > > > Could someone please direct me to a solution ? I've looked into > > anaconda, revision etc, but still cannot figure out how to fix my > > problem. > > > > Thanks > > > > Johan > > /kjs From frenken at informatik.fh-wiesbaden.de Mon Jun 18 08:41:31 2007 From: frenken at informatik.fh-wiesbaden.de (Thomas Frenken) Date: Mon, 18 Jun 2007 08:41:31 +0000 Subject: [Fedora-xen] Fedora 7 HVM Guest Message-ID: <200706180841.31797.frenken@informatik.fh-wiesbaden.de> Hi all, some days ago I upgraded from FC6 to F7. Machine details: [root at fettemoehre ~]# uname -a Linux fettemoehre.XXXX 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 09:29:36 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux [root at fettemoehre ~]# grep vmx /proc/cpuinfo flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr dca lahf_lm [root at fettemoehre ~]# cat /sys/hypervisor/properties/capabilities xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 --- I already managed in FC6 to run various fully virtualized guests including Windows XP / Server 2003 and FC6 32/64. However whenever I try to fully virtualize a F7 guest the installation failes. This happens independantly on whether I use virt-manager, virt-install or xm create [config] to create the guest. After creating the domu the system hangs before any installer shows up. E.g. a sample session using virt-install: [root at fettemoehre ~]# virt-install Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. yes What is the name of your virtual machine? F7_Gast1 How much RAM should be allocated (in megabytes)? 8092 What would you like to use as the disk (path)? /dev/VolGroup00/f7gast2 Would you like to enable graphics support? (yes or no) no What is the virtual CD image, CD device or install location? /tmp/F-7-x86_64-DVD.iso Starting install... libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:07 --- The installation doesn't continue, using a graphical installer I only see a black screen. Has anyone already managed to virtualize F7 or solved this or a similar issue? Thank! Thomas -------- LOGILES -------- Content of logifle qemu*: domid: 10 qemu: the number of cpus is 1 Watching /local/domain/10/logdirty/next-active qemu_map_cache_init nr_buckets = 10000 shared page at pfn effff buffered io page at pfn efffd xs_read(/vm/3404b719-29f4-bb90-986c-64f18e20e9e0/rtc/timeoffset): read error xs_read(): vncpasswd get error. /vm/3404b719-29f4-bb90-986c-64f18e20e9e0/vncpasswd. char device redirected to /dev/pts/4 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 Triggered log-dirty buffer switch Content of logile xend.log: [2007-06-18 10:02:09 2892] DEBUG (XendDomainInfo:78) XendDomainInfo.create(['vm', ['name', 'F7_GUEST'], ['memory', '8192'], ['maxmem', '8192'], ['vcpus', '1'], ['uuid', '3404b719-29f4-bb90-986c-64f18e20e9e0'], ['on_poweroff', 'destroy'], ['on_reboot', 'destroy'], ['on_crash', 'destroy'], ['image', ['hvm', ['kernel', '/usr/lib/xen/boot/hvmloader'], ['device_model', '/usr/lib64/xen/bin/qemu-dm'], ['vcpus', '1'], ['boot', 'd'], ['pae', '1'], ['serial', 'pty']]], ['device', ['vbd', ['dev', 'hda:disk'], ['uname', 'phy:/dev/VolGroup00/f7gast2'], ['mode', 'w']]], ['device', ['vbd', ['dev', 'hdc:cdrom'], ['uname', 'file:/tmp/F-7-x86_64-DVD.iso'], ['mode', 'r']]], ['device', ['vif', ['mac', '00:16:3e:28:9f:fc'], ['bridge', 'eth0'], ['type', 'ioemu']]]]) [2007-06-18 10:02:09 2892] DEBUG (XendDomainInfo:1460) XendDomainInfo.constructDomain [2007-06-18 10:02:09 2892] DEBUG (balloon:113) Balloon: 8362784 KiB free; need 2048; done. [2007-06-18 10:02:09 2892] DEBUG (XendDomain:443) Adding Domain: 10 [2007-06-18 10:02:09 2892] DEBUG (XendDomainInfo:1514) XendDomainInfo.initDomain: 10 256 [2007-06-18 10:02:09 2892] DEBUG (image:330) args: boot, val: d [2007-06-18 10:02:09 2892] DEBUG (image:330) args: fda, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: fdb, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: soundhw, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: localtime, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: serial, val: pty [2007-06-18 10:02:09 2892] DEBUG (image:330) args: std-vga, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: isa, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: acpi, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: usb, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: usbdevice, val: None [2007-06-18 10:02:09 2892] DEBUG (image:330) args: k, val: None [2007-06-18 10:02:09 2892] DEBUG (XendDomainInfo:1546) _initDomain:shadow_memory=0x0, memory_static_max=0x200000000, memory_static_min=0x0. [2007-06-18 10:02:09 2892] DEBUG (balloon:119) Balloon: 8361748 KiB free; 0 to scrub; need 8463360; retries: 20. [2007-06-18 10:02:09 2892] DEBUG (balloon:134) Balloon: setting dom0 target to 15982 MiB. [2007-06-18 10:02:09 2892] DEBUG (XendDomainInfo:581) Setting memory target of domain Domain-0 (0) to 15982 MiB. [2007-06-18 10:02:09 2892] DEBUG (XendDomainInfo:873) Storing domain details: {'cpu/3/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '16365568', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/7/availability': 'online', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'cpu/5/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1', 'cpu/6/availability': 'online', 'cpu/4/availability': 'online'} [2007-06-18 10:02:09 2892] DEBUG (balloon:113) Balloon: 8464148 KiB free; need 8463360; done. [2007-06-18 10:02:09 2892] INFO (image:129) buildDomain os=hvm dom=10 vcpus=1 [2007-06-18 10:02:09 2892] DEBUG (image:278) domid = 10 [2007-06-18 10:02:09 2892] DEBUG (image:279) image = /usr/lib/xen/boot/hvmloader [2007-06-18 10:02:09 2892] DEBUG (image:280) store_evtchn = 2 [2007-06-18 10:02:09 2892] DEBUG (image:281) memsize = 8192 [2007-06-18 10:02:09 2892] DEBUG (image:282) vcpus = 1 [2007-06-18 10:02:09 2892] DEBUG (image:283) pae = 1 [2007-06-18 10:02:09 2892] DEBUG (image:284) acpi = 0 [2007-06-18 10:02:09 2892] DEBUG (image:285) apic = 0 [2007-06-18 10:02:10 2892] INFO (XendDomainInfo:1362) createDevice: vbd : {'uuid': '0d69061d-fdeb-b7fe-f3bd-d73d472a3c8a', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'hda:disk', 'uname': 'phy:/dev/VolGroup00/f7gast2', 'mode': 'w'} [2007-06-18 10:02:10 2892] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/10/768'} to /local/domain/10/device/vbd/768. [2007-06-18 10:02:10 2892] DEBUG (DevController:117) DevController: writing {'domain': 'F7_GUEST', 'frontend': '/local/domain/10/device/vbd/768', 'uuid': '0d69061d-fdeb-b7fe-f3bd-d73d472a3c8a', 'dev': 'hda', 'state': '1', 'params': '/dev/VolGroup00/f7gast2', 'mode': 'w', 'online': '1', 'frontend-id': '10', 'type': 'phy'} to /local/domain/0/backend/vbd/10/768. [2007-06-18 10:02:10 2892] INFO (XendDomainInfo:1362) createDevice: vbd : {'uuid': 'a3b0b798-be08-a3c3-d69d-1e5237acb964', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'hdc:cdrom', 'uname': 'file:/tmp/F-7-x86_64-DVD.iso', 'mode': 'r'} [2007-06-18 10:02:10 2892] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'virtual-device': '5632', 'device-type': 'cdrom', 'state': '1', 'backend': '/local/domain/0/backend/vbd/10/5632'} to /local/domain/10/device/vbd/5632. [2007-06-18 10:02:10 2892] DEBUG (DevController:117) DevController: writing {'domain': 'F7_GUEST', 'frontend': '/local/domain/10/device/vbd/5632', 'uuid': 'a3b0b798-be08-a3c3-d69d-1e5237acb964', 'dev': 'hdc', 'state': '1', 'params': '/tmp/F-7-x86_64-DVD.iso', 'mode': 'r', 'online': '1', 'frontend-id': '10', 'type': 'file'} to /local/domain/0/backend/vbd/10/5632. [2007-06-18 10:02:10 2892] INFO (XendDomainInfo:1362) createDevice: vif : {'bridge': 'eth0', 'mac': '00:16:3e:28:9f:fc', 'type': 'ioemu', 'uuid': 'add6d423-d0a7-5e7c-76b7-5fe7248c4dba'} [2007-06-18 10:02:10 2892] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/10/0'} to /local/domain/10/device/vif/0. [2007-06-18 10:02:10 2892] DEBUG (DevController:117) DevController: writing {'bridge': 'eth0', 'domain': 'F7_GUEST', 'handle': '0', 'uuid': 'add6d423-d0a7-5e7c-76b7-5fe7248c4dba', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/10/device/vif/0', 'mac': '00:16:3e:28:9f:fc', 'online': '1', 'frontend-id': '10', 'type': 'ioemu'} to /local/domain/0/backend/vif/10/0. [2007-06-18 10:02:10 2892] INFO (image:445) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', '10', '-vcpus', '1', '-boot', 'd', '-serial', 'pty', '-domain-name', 'F7_GUEST', '-net', 'nic,vlan=1,macaddr=00:16:3e:28:9f:fc,model=rtl8139', '-net', 'tap,vlan=1,bridge=eth0', '-nographic'] [2007-06-18 10:02:10 2892] INFO (image:449) device model pid: 15638 [2007-06-18 10:02:10 2892] DEBUG (XendDomainInfo:2019) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '65', 'uuid': '3404b719-29f4-bb90-986c-64f18e20e9e0', 'on_reboot': 'destroy', 'start_time': '1182153730.57', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'destroy', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'image': '(hvm (kernel /usr/lib/xen/boot/hvmloader) (boot d) (device_model /usr/lib64/xen/bin/qemu-dm) (pae 1) (serial pty) (notes (SUSPEND_CANCEL 1)))', 'name': 'F7_GUEST'} [2007-06-18 10:02:10 2892] DEBUG (XendDomainInfo:873) Storing domain details: {'console/port': '3', 'name': 'F7_GUEST', 'console/limit': '1048576', 'vm': '/vm/3404b719-29f4-bb90-986c-64f18e20e9e0', 'domid': '10', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'memory/target': '8388608', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '983038', 'store/port': '2'} [2007-06-18 10:02:10 2892] DEBUG (XendDomainInfo:873) Storing domain details: {'name': 'F7_GUEST', 'console/limit': '1048576', 'image/suspend-cancel': '1', 'domid': '10', 'vm': '/vm/3404b719-29f4-bb90-986c-64f18e20e9e0', 'cpu/0/availability': 'online', 'memory/target': '8388608', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '983038', 'store/port': '2'} [2007-06-18 10:02:10 2892] DEBUG (XendDomainInfo:954) XendDomainInfo.handleShutdownWatch [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices vif. [2007-06-18 10:02:11 2892] DEBUG (DevController:153) Waiting for 0. [2007-06-18 10:02:11 2892] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/10/0/hotplug-status. [2007-06-18 10:02:11 2892] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices usb. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices vbd. [2007-06-18 10:02:11 2892] DEBUG (DevController:153) Waiting for 768. [2007-06-18 10:02:11 2892] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/10/768/hotplug-status. [2007-06-18 10:02:11 2892] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-06-18 10:02:11 2892] DEBUG (DevController:153) Waiting for 5632. [2007-06-18 10:02:11 2892] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/10/5632/hotplug-status. [2007-06-18 10:02:11 2892] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/10/5632/hotplug-status. [2007-06-18 10:02:11 2892] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices irq. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices vkbd. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices vfb. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices console. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices pci. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices ioports. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices tap. [2007-06-18 10:02:11 2892] DEBUG (DevController:148) Waiting for devices vtpm. [2007-06-18 10:02:11 2892] INFO (XendDomain:1117) Domain F7_GUEST (10) unpaused. [2007-06-18 10:02:11 2892] DEBUG (XendDomainInfo:233) XendDomainInfo.createDormant({'vcpus_params': {}, 'PV_args': '', 'features': '', 'cpus': [], 'devices': {'ebdb8802-92ab-2393-d58a-f7e6bd4d5302': ('vbd', {'uuid': 'ebdb8802-92ab-2393-d58a-f7e6bd4d5302', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'hda:disk', 'uname': 'phy:/dev/VolGroup00/f7gast2', 'mode': 'w'}), 'dd75b195-189f-1df1-99c4-2bfd4cc88e64': ('vif', {'bridge': 'eth0', 'mac': '00:16:3e:28:9f:fc', 'type': 'ioemu', 'uuid': 'dd75b195-189f-1df1-99c4-2bfd4cc88e64'})}, 'vcpu_avail': 1, 'VCPUs_live': 1, 'PV_bootloader': '', 'actions_after_crash': 'restart', 'vbd_refs': ['ebdb8802-92ab-2393-d58a-f7e6bd4d5302'], 'PV_ramdisk': '', 'is_control_domain': False, 'name_label': 'F7_GUEST', 'VCPUs_at_startup': 1, 'HVM_boot_params': {'order': 'c'}, 'platform': {'device_model': '/usr/lib64/xen/bin/qemu-dm', 'serial': 'pty', 'boot': 'c', 'pae': '1'}, 'cpu_weight': 256, 'console_refs': [], 'cpu_cap': 0, 'on_xend_stop': 'ignore', 'memory_static_min': 0, 'HVM_boot_policy': 'BIOS order', 'VCPUs_max': 1, 'memory_static_max': 8589934592, 'actions_after_shutdown': 'destroy', 'on_xend_start': 'ignore', 'memory_dynamic_max': 8589934592, 'actions_after_suspend': '', 'is_a_template': False, 'memory_dynamic_min': 8589934592, 'uuid': '3404b719-29f4-bb90-986c-64f18e20e9e0', 'PV_kernel': '/usr/lib/xen/boot/hvmloader', 'shadow_memory': 0, 'PV_bootloader_args': '', 'other_config': {}, 'actions_after_reboot': 'restart', 'vif_refs': ['dd75b195-189f-1df1-99c4-2bfd4cc88e64'], 'vtpm_refs': [], 'security': None}) [2007-06-18 10:02:11 2892] DEBUG (XendDomain:960) Creating new managed domain: F7_GUEST Content of lofile xend-debug.log: Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: From rjones at redhat.com Mon Jun 18 11:18:01 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 18 Jun 2007 12:18:01 +0100 Subject: [Fedora-xen] F7 System crash with high network load In-Reply-To: References: Message-ID: <467669E9.4040505@redhat.com> Sven Oehme wrote: > > Hi, > > i experienced it now a couple of time that my Dom0 will get unstable if > i copy a lot of files over a gigabit link using rsync into the dom0. > That happens even, when there is no workload on the system beside this > process at all. > > How to reproduce : > > rsync -avuzP --delete --progress /home/user1 xenhost:/home/user1 > > the rsync will start and after a few minutes the remote host (xen) is no > longer responding on the network. > when i look at the console of the xen host, it prints millions of : > > [] syscall_call+0x7/0xb > > only a hard reset helps now .. > > environment : > > xen-libs-3.1.0-2.fc7 > xen-3.1.0-2.fc7 > kernel-xen-2.6.20-2925.11.fc7 > kernel-xen-devel-2.6.20-2925.11.fc7 > > so i assume it is a f7 kernel-xen bug .. is this known, as i haven't > found anything in bugzilla .. > should i open a ticket against f7 ? Could it be the same as this one? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 Do you get a full stack trace? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From John.Sanabria at ece.uprm.edu Mon Jun 18 22:29:35 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Mon, 18 Jun 2007 18:29:35 -0400 (AST) Subject: [Fedora-xen] problem doing provision... Message-ID: <35322.136.145.116.114.1182205775.squirrel@ece.uprm.edu> Hi, i have two systems with fc6: shutdown.ece.uprm.edu (with updates) -> Linux shutdown 2.6.20-1.2952.fc6xen #1 SMP Wed May 16 19:19:04 EDT 2007 i686 i686 i386 GNU/Linux init.ece.uprm.edu (no recent updates) -> Linux init 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux my problems appear when i decide update packages in shutdown machine. When execute the next command: cobbler enchant --virt=yes --address=shutdown.ece.uprm.edu --profile="base-box" i got the message at the end of this e-mail. However, everything works properly when execute this command: cobbler enchant --virt=yes --address=init.ece.uprm.edu --profile="base-box" What probably udpate crash the shutdown system? Do you need some specific details of the system in order to give a suggestion? thanks a lot for your attention, regards. +-------------+ |message error| +-------------+ - url=http://136.145.116.11libvir: error : configuration file syntax error: expecting a name Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/koan/app.py", line 97, in main k.run() File "/usr/lib/python2.4/site-packages/koan/app.py", line 152, in run self.do_virt() File "/usr/lib/python2.4/site-packages/koan/app.py", line 297, in do_virt return self.do_net_install("/tmp",after_download) File "/usr/lib/python2.4/site-packages/koan/app.py", line 253, in do_net_install after_download(self, distro_data, profile_data) File "/usr/lib/python2.4/site-packages/koan/app.py", line 296, in after_download self.do_virt_net_install(profile_data, distro_data) File "/usr/lib/python2.4/site-packages/koan/app.py", line 600, in do_virt_net_install extra=kextra File "/usr/lib/python2.4/site-packages/koan/virtcreate.py", line 102, in start_paravirt_install guest.start_install() File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 643, in start_install meter = progress.BaseMeter() 4/cobbler/images/xentemplate/vmlinuz - kernel saved = /tmp/vmlinuz - initrd saved = /tmp/initrd.img NameError: global name 'progress' is not defined returns: 3 Traceback (most recent call last): File "/usr/lib/python2.4/site-packages/cobbler/action_enchant.py", line 101, in run self.ssh_exec("koan %s --profile=%s --server=%s" % (operation, self.profile, self.settings.server)) File "/usr/lib/python2.4/site-packages/cobbler/action_enchant.py", line 57, in ssh_exec raise cexceptions.CobblerException("enchant_failed","ssh failure") CobblerException: 'enchant failed (ssh failure)' enchant failed (exception) http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From oehmes at de.ibm.com Mon Jun 18 23:52:33 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Tue, 19 Jun 2007 01:52:33 +0200 Subject: [Fedora-xen] F7 System crash with high network load In-Reply-To: <467669E9.4040505@redhat.com> Message-ID: no, as there is no USB involved at all ... Sven "Richard W.M. Jones" 06/18/07 01:18 PM To Sven Oehme/Germany/IBM at IBMDE cc fedora-xen at redhat.com Subject Re: [Fedora-xen] F7 System crash with high network load Sven Oehme wrote: > > Hi, > > i experienced it now a couple of time that my Dom0 will get unstable if > i copy a lot of files over a gigabit link using rsync into the dom0. > That happens even, when there is no workload on the system beside this > process at all. > > How to reproduce : > > rsync -avuzP --delete --progress /home/user1 xenhost:/home/user1 > > the rsync will start and after a few minutes the remote host (xen) is no > longer responding on the network. > when i look at the console of the xen host, it prints millions of : > > [] syscall_call+0x7/0xb > > only a hard reset helps now .. > > environment : > > xen-libs-3.1.0-2.fc7 > xen-3.1.0-2.fc7 > kernel-xen-2.6.20-2925.11.fc7 > kernel-xen-devel-2.6.20-2925.11.fc7 > > so i assume it is a f7 kernel-xen bug .. is this known, as i haven't > found anything in bugzilla .. > should i open a ticket against f7 ? Could it be the same as this one? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 Do you get a full stack trace? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- An HTML attachment was scrubbed... URL: From oehmes at de.ibm.com Mon Jun 18 23:53:05 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Tue, 19 Jun 2007 01:53:05 +0200 Subject: [Fedora-xen] F7 System crash with high network load In-Reply-To: <467669E9.4040505@redhat.com> Message-ID: no, as there is no USB involved at all ... Sven "Richard W.M. Jones" 06/18/07 01:18 PM To Sven Oehme/Germany/IBM at IBMDE cc fedora-xen at redhat.com Subject Re: [Fedora-xen] F7 System crash with high network load Sven Oehme wrote: > > Hi, > > i experienced it now a couple of time that my Dom0 will get unstable if > i copy a lot of files over a gigabit link using rsync into the dom0. > That happens even, when there is no workload on the system beside this > process at all. > > How to reproduce : > > rsync -avuzP --delete --progress /home/user1 xenhost:/home/user1 > > the rsync will start and after a few minutes the remote host (xen) is no > longer responding on the network. > when i look at the console of the xen host, it prints millions of : > > [] syscall_call+0x7/0xb > > only a hard reset helps now .. > > environment : > > xen-libs-3.1.0-2.fc7 > xen-3.1.0-2.fc7 > kernel-xen-2.6.20-2925.11.fc7 > kernel-xen-devel-2.6.20-2925.11.fc7 > > so i assume it is a f7 kernel-xen bug .. is this known, as i haven't > found anything in bugzilla .. > should i open a ticket against f7 ? Could it be the same as this one? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 Do you get a full stack trace? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ianbrn at gmail.com Tue Jun 19 10:44:36 2007 From: ianbrn at gmail.com (Ian Brown) Date: Tue, 19 Jun 2007 13:44:36 +0300 Subject: [Fedora-xen] virt-install on FC7 gives errors - why ? Message-ID: Helllo, 1) I had installed FC7 on x86_64 machine; I am running the default FC7 Xen domain 0 on it. I tried to install FC7 guest (also x86_64) by virt-install. This guest should be paravirualized (I don't have support for full virtualization on this CPU). What I did was: virt-install -b --vcpus=1 -n guset4 -r 256 -s 4 -f /mnt/sda5/xenguest/guest4 -l http://192.168.0.131/ftp/ -p --nographics on http://192.168.0.131/ftp/ there is the FC7 installation tree ; This machines runs an apache http server. What I see on the screen is: ... ... Starting install... libvir: Xen Daemon error : GET operation failed: libvir: error : configuration file syntax error: expecting a name libvir: error : configuration file syntax error: expecting a name libvir: error : configuration file syntax error: expecting a name Retrieving Fedora... 491 kB 00:00 Retrieving vmlinuz... 100% |=========================| 1.8 MB 00:01 Retrieving initrd.img... 100% |=========================| 5.4 MB 00:01 libvir: Xen Daemon error : GET operation failed: Creating storage file... 100% |=========================| 4.0 GB 00:00 ... >From where do these libvir errors come ? What should I do to avoid them (eventually the guest ** is not ** created).? about which configuration file is this error message? 2) A second question: from running "virt-install --help" I see that I can choose -b (for bridging) optionally with a bridge name. I can also choose -w NETWORK for connecting to a nic. My question is: must I add "-b" or "-w" ? or is there some default behaviour if I don't select any of these options? Regards, Ian From mdehaan at redhat.com Tue Jun 19 14:20:21 2007 From: mdehaan at redhat.com (Michael DeHaan) Date: Tue, 19 Jun 2007 10:20:21 -0400 Subject: [Fedora-xen] Re: [et-mgmt-tools] problem doing provision... In-Reply-To: <35322.136.145.116.114.1182205775.squirrel@ece.uprm.edu> References: <35322.136.145.116.114.1182205775.squirrel@ece.uprm.edu> Message-ID: <4677E625.7010006@redhat.com> "NameError: global name 'progress' is not defined" What versions of virtinst does this machine have? This was fixed in virtinst some time ago, as I recall. John Sanabria wrote: > Hi, > > i have two systems with fc6: > > shutdown.ece.uprm.edu (with updates) -> Linux shutdown > 2.6.20-1.2952.fc6xen #1 SMP Wed May 16 19:19:04 EDT 2007 i686 i686 i386 > GNU/Linux > > init.ece.uprm.edu (no recent updates) -> Linux init > 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 > GNU/Linux > > > my problems appear when i decide update packages in shutdown machine. When > execute the next command: > > cobbler enchant --virt=yes --address=shutdown.ece.uprm.edu > --profile="base-box" > > i got the message at the end of this e-mail. However, everything works > properly when execute this command: > > cobbler enchant --virt=yes --address=init.ece.uprm.edu --profile="base-box" > > What probably udpate crash the shutdown system? Do you need some specific > details of the system in order to give a suggestion? > > thanks a lot for your attention, regards. > > +-------------+ > |message error| > +-------------+ > - url=http://136.145.116.11libvir: error : configuration file syntax > error: expecting a name > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/koan/app.py", line 97, in main > k.run() > File "/usr/lib/python2.4/site-packages/koan/app.py", line 152, in run > self.do_virt() > File "/usr/lib/python2.4/site-packages/koan/app.py", line 297, in do_virt > return self.do_net_install("/tmp",after_download) > File "/usr/lib/python2.4/site-packages/koan/app.py", line 253, in > do_net_install > after_download(self, distro_data, profile_data) > File "/usr/lib/python2.4/site-packages/koan/app.py", line 296, in > after_download > self.do_virt_net_install(profile_data, distro_data) > File "/usr/lib/python2.4/site-packages/koan/app.py", line 600, in > do_virt_net_install > extra=kextra > File "/usr/lib/python2.4/site-packages/koan/virtcreate.py", line 102, in > start_paravirt_install > guest.start_install() > File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 643, in > start_install > meter = progress.BaseMeter() > 4/cobbler/images/xentemplate/vmlinuz > - kernel saved = /tmp/vmlinuz > - initrd saved = /tmp/initrd.img > NameError: global name 'progress' is not defined > returns: 3 > Traceback (most recent call last): > File "/usr/lib/python2.4/site-packages/cobbler/action_enchant.py", line > 101, in run > self.ssh_exec("koan %s --profile=%s --server=%s" % (operation, > self.profile, self.settings.server)) > File "/usr/lib/python2.4/site-packages/cobbler/action_enchant.py", line > 57, in ssh_exec > raise cexceptions.CobblerException("enchant_failed","ssh failure") > CobblerException: 'enchant failed (ssh failure)' > enchant failed (exception) > > > http://ece.uprm.edu/~s047267 > http://del.icio.us/josanabr > http://blog-grid.blogspot.com > > _______________________________________________ > et-mgmt-tools mailing list > et-mgmt-tools at redhat.com > https://www.redhat.com/mailman/listinfo/et-mgmt-tools > From alexander.samad at hp.com Mon Jun 18 06:17:24 2007 From: alexander.samad at hp.com (Samad, Alex) Date: Mon, 18 Jun 2007 16:17:24 +1000 Subject: [Fedora-xen] Problem Installing Fedora 7 as a Guest on Xen machine Message-ID: Hi Resending message not sure if it made through the first time Hi I have run into a problem installing fedora 7 as a guest on a Xen machine. The host machine is a amd64 - Debian lenny install. Running 2.6.20-1-xen-amd64 xm info?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? host?????????????????? : debxen??????????????????????????????????????????????????????????????????????????????????????????????????????????????? release??????????????? : 2.6.20-1-xen-amd64??????????????????????????????????????????????????????????????????????????????????????????????????? version??????????????? : #1 SMP Tue Apr 24 22:23:22 UTC 2007?????????????????????????????????????????????????????????????????????????????????? machine??????????????? : x86_64??????????????????????????????????????????????????????????????????????????????????????????????????????????????? nr_cpus??????????????? : 4???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? nr_nodes?????????????? : 1???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? sockets_per_node?????? : 2???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? cores_per_socket?????? : 2???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? threads_per_core?????? : 1???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? cpu_mhz??????????????? : 2800????????????????????????????????????????????????????????????????????????????????????????????????????????????????? hw_caps??????????????? : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f??????????????????????????????????????????????????????? total_memory?????????? : 8191????????????????????????????????????????????????????????????????????????????????????????????????????????????????? free_memory??????????? : 1???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? xen_major????????????? : 3???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? xen_minor????????????? : 0???????????????????????????????????????????????????????????????????????????????????????????????????????????????????? xen_extra????????????? : .3-1????????????????????????????????????????????????????????????????????????????????????????????????????????????????? xen_caps?????????????? : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64????????????????????????????????????????????????????????? xen_pagesize?????????? : 4096????????????????????????????????????????????????????????????????????????????????????????????????????????????????? platform_params??????? : virt_start=0xffff800000000000???????????????????????????????????????????????????????????????????????????????????????? xen_changeset????????? : Tue Oct 17 22:09:52 2006 +0100??????????????????????????????????????????????????????????????????????????????????????? cc_compiler??????????? : gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19)???????????????????????????????????????????????????????????? cc_compile_by????????? : ultrotter???????????????????????????????????????????????????????????????????????????????????????????????????????????? cc_compile_domain????? : debian.org??????????????????????????????????????????????????????????????????????????????????????????????????????????? cc_compile_date??????? : Fri Nov? 3 00:21:27 CET 2006????????????????????????????????????????????????????????????????????????????????????????? xend_config_format???? : 2?? I have downloaded the fedora 7 DVD, I have extracted the xen vmlinuz and zen initrd.img This is my fedora7.cfg #????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #? Kernel + memory size??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? kernel????? = '/etc/xen/data/fedora7/vmlinuz'????????????????????????????????????????????????????????????????????????????????????????????????? ramdisk???? = '/etc/xen/data/fedora7/initrd.img'?????????????????????????????????????????????????????????????????????????????????????????????? memory????? = '1024'?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? extra?????????? = 'pnpacpi=off sync_console vnc vncpassword=qwerty text vncconnect=16.144.29.11'?????????????????????????????????????????????? #bootloader???? = '/usr/lib/xen-3.0.3-1/bin/pygrub'??????????????????????????????????????????????????????????????????????????????????????????? ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #? Disk device(s).???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? disk??????? = [ 'phy:vglocal/fedora7-disk,xvda,w' ]??????????????????????????????????????????????????????????????????????????????????????????? ?????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #? Hostname??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? #????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? name??????? = 'fedora7'??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? # #? Networking # dhcp??????? = 'dhcp' #vif???????? = [ 'type=ioemu, bridge=xenbr0' ] vif???????? = [ '' ] # #? Behaviour # on_poweroff = 'destroy' on_reboot?? = 'restart' on_crash??? = 'restart' serial = "pty" localtime = 0 vcpus = 2 I tried something similar with RHEL5 and it worked, fedora7 is getting stuck >From xm console fedora7 io scheduler noop registered?????????????????????????????????????????????????????????????????????????????????????????????????????????????????? io scheduler anticipatory registered?????????????????????????????????????????????????????????????????????????????????????????????????????????? io scheduler deadline registered?????????????????????????????????????????????????????????????????????????????????????????????????????????????? io scheduler cfq registered (default)????????????????????????????????????????????????????????????????????????????????????????????????????????? pci_hotplug: PCI Hot Plug PCI Core version: 0.5??????????????????????????????????????????????????????????????????????????????????????????????? rtc: IRQ 8 is not free.??????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Non-volatile memory driver v1.2??????????????????????????????????????????????????????????????????????????????????????????????????????????????? Linux agpgart interface v0.101 (c) Dave Jones????????????????????????????????????????????????????????????????????????????????????????????????? RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize???????????????????????????????????????????????????????????????????????? input: Macintosh mouse button emulation as /class/input/input0???????????????????????????????????????????????????????????????????????????????? Xen virtual console successfully installed as xvc0???????????????????????????????????????????????????????????????????????????????????????????? Event-channel device installed.??????????????????????????????????????????????????????????????????????????????????????????????????????????????? usbcore: registered new interface driver libusual????????????????????????????????????????????????????????????????????????????????????????????? usbcore: registered new interface driver hiddev??????????????????????????????????????????????????????????????????????????????????????????????? usbcore: registered new interface driver usbhid??????????????????????????????????????????????????????????????????????????????????????????????? drivers/usb/input/hid-core.c: v2.6:USB HID core driver???????????????????????????????????????????????????????????????????????????????????????? PNP: No PS/2 controller found. Probing ports directly.???????????????????????????????????????????????????????????????????????????????????????? i8042.c: No controller found.????????????????????????????????????????????????????????????????????????????????????????????????????????????????? mice: PS/2 mouse device common for all mice??????????????????????????????????????????????????????????????????????????????????????????????????? TCP bic registered???????????????????????????????????????????????????????????????????????????????????????????????????????????????????????????? Initializing XFRM netlink socket?????????????????????????????????????????????????????????????????????????????????????????????????????????????? NET: Registered protocol family 1????????????????????????????????????????????????????????????????????????????????????????????????????????????? NET: Registered protocol family 17???????????????????????????????????????????????????????????????????????????????????????????????????????????? XENBUS: Device with no driver: device/vbd/51712??????????????????????????????????????????????????????????????????????????????????????????????? XENBUS: Device with no driver: device/vif/0??????????????????????????????????????????????????????????????????????????????????????????????????? Write protecting the kernel read-only data: 938k I not sure what is mean to come after here for me to guess where it might be getting stuck.? Can any one provide any hints or know what is going wrong.? Maybe there is a mis match of the xen versions ??? Thanks Alex -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT1539348.txt URL: From John.Sanabria at ece.uprm.edu Tue Jun 19 15:00:37 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Tue, 19 Jun 2007 11:00:37 -0400 (AST) Subject: [Fedora-xen] how to startup a new virtual box... Message-ID: <34185.136.145.116.114.1182265237.squirrel@ece.uprm.edu> hi, i'm using xen 3.1 from fc7. In fc6 i can startup a virtual box with: xm create name_virtual_box, for example: xm create 00_16_3E_32_0F_0F. When i try to run the same command in fc7, it does not work. Thank you. output: Error: Unable to open config file: 00_16_3E_32_0F_0F http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From berrange at redhat.com Tue Jun 19 15:02:56 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 19 Jun 2007 16:02:56 +0100 Subject: [Fedora-xen] how to startup a new virtual box... In-Reply-To: <34185.136.145.116.114.1182265237.squirrel@ece.uprm.edu> References: <34185.136.145.116.114.1182265237.squirrel@ece.uprm.edu> Message-ID: <20070619150256.GD1455@redhat.com> On Tue, Jun 19, 2007 at 11:00:37AM -0400, John Sanabria wrote: > hi, > > i'm using xen 3.1 from fc7. In fc6 i can startup a virtual box with: xm > create name_virtual_box, for example: xm create 00_16_3E_32_0F_0F. > > When i try to run the same command in fc7, it does not work. Thank you. > > output: Error: Unable to open config file: 00_16_3E_32_0F_0F Use virsh list --all to see what guests are defined and then start one up with virsh start [name or uuid] 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 -=| From mc-al34luc at sbcglobal.net Tue Jun 19 15:52:09 2007 From: mc-al34luc at sbcglobal.net (Mike) Date: Tue, 19 Jun 2007 08:52:09 -0700 Subject: [Fedora-xen] Problem Installing Fedora 7 as a Guest on Xen machine In-Reply-To: References: Message-ID: <4677FBA9.5020402@sbcglobal.net> Samad, Alex wrote: > Hi > > Resending message not sure if it made through the first time > > > > Hi > I have run into a problem installing fedora 7 as a guest on a Xen machine. > The host machine is a amd64 - Debian lenny install. Running 2.6.20-1-xen-amd64 > xm info > host : debxen > release : 2.6.20-1-xen-amd64 > version : #1 SMP Tue Apr 24 22:23:22 UTC 2007 > machine : x86_64 > nr_cpus : 4 > nr_nodes : 1 > sockets_per_node : 2 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 2800 > hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000001f > total_memory : 8191 > free_memory : 1 > xen_major : 3 > xen_minor : 0 > xen_extra : .3-1 > xen_caps : xen-3.0-x86_64 hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : Tue Oct 17 22:09:52 2006 +0100 > cc_compiler : gcc version 4.1.2 20061028 (prerelease) (Debian 4.1.1-19) > cc_compile_by : ultrotter > cc_compile_domain : debian.org > cc_compile_date : Fri Nov 3 00:21:27 CET 2006 > xend_config_format : 2 > I have downloaded the fedora 7 DVD, I have extracted the xen vmlinuz and zen initrd.img > This is my fedora7.cfg > # > # Kernel + memory size > # > kernel = '/etc/xen/data/fedora7/vmlinuz' > ramdisk = '/etc/xen/data/fedora7/initrd.img' > memory = '1024' > extra = 'pnpacpi=off sync_console vnc vncpassword=qwerty text vncconnect=16.144.29.11' > #bootloader = '/usr/lib/xen-3.0.3-1/bin/pygrub' > > # > # Disk device(s). > # > disk = [ 'phy:vglocal/fedora7-disk,xvda,w' ] > > # > # Hostname > # > name = 'fedora7' > # > # Networking > # > dhcp = 'dhcp' > #vif = [ 'type=ioemu, bridge=xenbr0' ] > vif = [ '' ] > # > # Behaviour > # > on_poweroff = 'destroy' > on_reboot = 'restart' > on_crash = 'restart' > > serial = "pty" > localtime = 0 > vcpus = 2 > I tried something similar with RHEL5 and it worked, fedora7 is getting stuck >>From xm console fedora7 > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > Linux agpgart interface v0.101 (c) Dave Jones > RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize > input: Macintosh mouse button emulation as /class/input/input0 > Xen virtual console successfully installed as xvc0 > Event-channel device installed. > usbcore: registered new interface driver libusual > usbcore: registered new interface driver hiddev > usbcore: registered new interface driver usbhid > drivers/usb/input/hid-core.c: v2.6:USB HID core driver > PNP: No PS/2 controller found. Probing ports directly. > i8042.c: No controller found. > mice: PS/2 mouse device common for all mice > TCP bic registered > Initializing XFRM netlink socket > NET: Registered protocol family 1 > NET: Registered protocol family 17 > XENBUS: Device with no driver: device/vbd/51712 > XENBUS: Device with no driver: device/vif/0 > Write protecting the kernel read-only data: 938k > > I not sure what is mean to come after here for me to guess where it might be getting stuck. Can any one provide any hints or know what is going wrong. Maybe there is a mis match of the xen versions ??? > Thanks > Alex Hi Alex, It *is* working. I ran into this myself with F7, and it took me a bit to figure out what was going on. Your console has been redirected to the graphical console from the serial console at that point in the guest boot process. Here's what to do: 1) Fire up virt-manager in dom-0. You'll see your guest running (xm and virsh will show it as blocked). From the 'view' menu, select the graphical console and you'll get your guest's login screen. 2) In order to have the output of your guest appear in both consoles, add the following to your guest's kernel line in grub.conf: console=tty console=xvc0,9600n8 Now you'll see all the output in both the text and the graphical console. Note that you'll also need to edit /etc/securetty and add 'xvc0', and check /etc/inittab and make sure you have a line like: co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav as well. Good luck. Mike > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From tom.horsley at att.net Tue Jun 19 19:14:08 2007 From: tom.horsley at att.net (Tom Horsley) Date: Tue, 19 Jun 2007 19:14:08 +0000 Subject: [Fedora-xen] 32 bit F7 HVM hangs under 64 bit F6 host Message-ID: <061920071914.24375.46782B0000080F8F00005F372160376021970A049C9D0108D203019B@att.net> All my attempts to install a Fedora 7 HVM under the x86_64 Fedora 6 host I have have gone into 100% cpu use hangs during the install. Today I tried something new - I installed Fedora Core 6 as an HVM, then built a repo from the F7 dvd image and updated all the packages. That actually ran, but it only works if I boot the old Fedora Core 6 kernel. Any attempt to boot any F7 kernel I've tried gets far enough to print: PCI: PIIX3: Enabling Passive Release on 0000:00:01.0 then it is hung in the same ol 100% cpu usage state. Anyone know what is happening right there (or right after there)? Any good kernel boot parameters to try? From berrange at redhat.com Tue Jun 19 19:27:41 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 19 Jun 2007 20:27:41 +0100 Subject: [Fedora-xen] 32 bit F7 HVM hangs under 64 bit F6 host In-Reply-To: <061920071914.24375.46782B0000080F8F00005F372160376021970A049C9D0108D203019B@att.net> References: <061920071914.24375.46782B0000080F8F00005F372160376021970A049C9D0108D203019B@att.net> Message-ID: <20070619192741.GA5970@redhat.com> On Tue, Jun 19, 2007 at 07:14:08PM +0000, Tom Horsley wrote: > All my attempts to install a Fedora 7 HVM under the x86_64 Fedora 6 > host I have have gone into 100% cpu use hangs during the install. > > Today I tried something new - I installed Fedora Core 6 as an HVM, > then built a repo from the F7 dvd image and updated all the packages. > > That actually ran, but it only works if I boot the old Fedora Core 6 > kernel. Any attempt to boot any F7 kernel I've tried gets far enough > to print: > > PCI: PIIX3: Enabling Passive Release on 0000:00:01.0 > > then it is hung in the same ol 100% cpu usage state. > > Anyone know what is happening right there (or right after there)? The GA baremetal kernel was screwed up with last minute dynamic tick patches which make it impossible to boot under Xen HVM. > Any good kernel boot parameters to try? Use the paravirt kernel instead. 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 -=| From tom.horsley at att.net Tue Jun 19 22:02:43 2007 From: tom.horsley at att.net (Tom Horsley) Date: Tue, 19 Jun 2007 18:02:43 -0400 Subject: [Fedora-xen] 32 bit F7 HVM hangs under 64 bit F6 host In-Reply-To: <20070619192741.GA5970@redhat.com> References: <061920071914.24375.46782B0000080F8F00005F372160376021970A049C9D0108D203019B@att.net> <20070619192741.GA5970@redhat.com> Message-ID: <20070619180243.6b924009@zooty> On Tue, 19 Jun 2007 20:27:41 +0100 "Daniel P. Berrange" wrote: > > kernel. Any attempt to boot any F7 kernel I've tried gets far enough > > to print: > > > > PCI: PIIX3: Enabling Passive Release on 0000:00:01.0 > > > > then it is hung in the same ol 100% cpu usage state. > > > > Anyone know what is happening right there (or right after there)? > > The GA baremetal kernel was screwed up with last minute dynamic tick > patches which make it impossible to boot under Xen HVM. > > > Any good kernel boot parameters to try? > > Use the paravirt kernel instead. Does that mean just run the kernel-xen in the HVM? Or does it mean do a paravirt install of F7? (The paravirt install is kinda difficult with the FC6 host still being xen 3.0.3 and 64 bit 3.0.3 not knowing how to talk down to a 32 bit VM :-). Though running the FC6 kernel seems to work OK for now. Eventually I imagine a new kernel will show up on F7 that actually works, so perhaps I'll just wait for that. From naoki at valuecommerce.com Wed Jun 20 07:14:16 2007 From: naoki at valuecommerce.com (Naoki) Date: Wed, 20 Jun 2007 16:14:16 +0900 Subject: [Fedora-xen] Flash 9 (ff) dies under Xen (2.6.20-2925.11.fc7xen) Message-ID: <1182323657.3463.66.camel@dellt-ysonohara.w2k.intra> Do we already know about this, or is a bz needed ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Wed Jun 20 10:24:21 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 20 Jun 2007 11:24:21 +0100 Subject: [Fedora-xen] Flash 9 (ff) dies under Xen (2.6.20-2925.11.fc7xen) In-Reply-To: <1182323657.3463.66.camel@dellt-ysonohara.w2k.intra> References: <1182323657.3463.66.camel@dellt-ysonohara.w2k.intra> Message-ID: <46790055.2010106@redhat.com> Naoki wrote: > Do we already know about this, or is a bz needed ? Can you explain a bit more - I'm not sure I understand what exactly is dying. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From John.Sanabria at ece.uprm.edu Wed Jun 20 17:20:31 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Wed, 20 Jun 2007 13:20:31 -0400 (AST) Subject: [Fedora-xen] (no subject) Message-ID: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> Hi, i'm interested to "clone" a xen vm. i read an article (1) where suggest use the command "xe" for clone a vm. However, the article does not specify where get the tool. i want two vm with same software installed but different MAC address. How to achieve it? Thanks. (1)http://searchservervirtualization.techtarget.com/tip/0,289483,sid94_gci1245957,00.html http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From berrange at redhat.com Wed Jun 20 17:34:14 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 20 Jun 2007 18:34:14 +0100 Subject: [Fedora-xen] (no subject) In-Reply-To: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> References: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> Message-ID: <20070620173414.GD21208@redhat.com> On Wed, Jun 20, 2007 at 01:20:31PM -0400, John Sanabria wrote: > Hi, > > i'm interested to "clone" a xen vm. i read an article (1) where suggest > use the command "xe" for clone a vm. However, the article does not specify > where get the tool. Sounds like its refering to XenEnterprise - a big money closed source product from XenSource. > i want two vm with same software installed but different MAC address. How > to achieve it? Copy the disk image for the machine. Then copy the config, changing the MAC address, name, UUID and path to the disk image. We have a tool pending release in a few weeks that will automate this... 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 -=| From John.Sanabria at ece.uprm.edu Wed Jun 20 18:38:13 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Wed, 20 Jun 2007 14:38:13 -0400 (AST) Subject: [Fedora-xen] (no subject) In-Reply-To: <20070620173414.GD21208@redhat.com> References: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> <20070620173414.GD21208@redhat.com> Message-ID: <33410.136.145.116.114.1182364693.squirrel@ece.uprm.edu> Thanks Daniel for the answer, according to Xen Documentation (3.0), you can start a domain using: xm create The must be located in /etc/xen directory. However, for Xen 3.1 the configuration file is not "necessary", then, you can submit the command, virsh start and the domain is created. The must be a file located in /var/lib/xen/images directory. But, where is located the configuration file for a domain in xen 3.1? Thanks. > > Copy the disk image for the machine. Then copy the config, changing the > MAC address, name, UUID and path to the disk image. > http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From berrange at redhat.com Wed Jun 20 18:45:20 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 20 Jun 2007 19:45:20 +0100 Subject: [Fedora-xen] (no subject) In-Reply-To: <33410.136.145.116.114.1182364693.squirrel@ece.uprm.edu> References: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> <20070620173414.GD21208@redhat.com> <33410.136.145.116.114.1182364693.squirrel@ece.uprm.edu> Message-ID: <20070620184520.GE21208@redhat.com> On Wed, Jun 20, 2007 at 02:38:13PM -0400, John Sanabria wrote: > Thanks Daniel for the answer, > > according to Xen Documentation (3.0), you can start a domain using: > > xm create > > The must be located in /etc/xen directory. However, for Xen > 3.1 the configuration file is not "necessary", then, you can submit the > command, > > virsh start > > and the domain is created. The must be a file located in > /var/lib/xen/images directory. But, where is located the configuration > file for a domain in xen 3.1? Thanks. Use virsh dumpxml to get it And once you've edited the XML, use virsh define to load in the new config. Regards, 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 -=| From John.Sanabria at ece.uprm.edu Wed Jun 20 20:00:07 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Wed, 20 Jun 2007 16:00:07 -0400 (AST) Subject: [Fedora-xen] (no subject) In-Reply-To: <20070620184520.GE21208@redhat.com> References: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu><20070620173414.GD21208@redhat.com><33410.136.145.116.114.1182364693.squirrel@ece.uprm.edu> <20070620184520.GE21208@redhat.com> Message-ID: <55412.136.145.116.114.1182369607.squirrel@ece.uprm.edu> Thanks Daniel, i did the next: 1- use dd command to get a copy from a vm: dd if=00_16_3E_32_0F_0F of=copia-00_16_3E_32_0F_0F 2- then, ( probably big mistake :-( ) use virsh command: virsh dumpxml 00_16_3E_32_0F_0F > ~/copia-vm.cfg 3- i modify the copia-vm.cfg and change the name field and remove the mac address field, defined inside of the interface tag: --------------------- virsh dumpxml output --------------------- copia-00_16_3E_32_0F_0F dd9fe09e1155f9223779b6c28bf43488 /usr/bin/pygrub linux 262144 1 destroy restart restart --------------------- virsh dumpxml output --------------------- 4- virsh define copia-00_16_3E_32_0F_0F, (am i (re-)define the domain 00_16_3E_32_0F_0F ???) 5- virsh start copia-00_16_3E_32_0F_0F (boot ok!, can get into the root account, ping google.com, works! :-D) 6- but i don't need this domain anymore 'virsh undefine copia-00_16_3E_32_0F_0F' 7- boot again the original vm: [root at shutdown ~]# virsh start 00_16_3E_32_0F_0F libvir: Xen Daemon error : GET operation failed: error: failed to get domain '00_16_3E_32_0F_0F' 8- oops! :-( 9- i try to "recreate" the xml file, a- [root at shutdown ~]# virsh dumpxml /var/lib/xen/images/00_16_3E_32_0F_0F > original-vm.cfg libvir: Xen Daemon error : GET operation failed: error: failed to get domain '/var/lib/xen/images/00_16_3E_32_0F_0F' b- [root at shutdown ~]# virsh dumpxml 00_16_3E_32_0F_0F > original-vm.cfg libvir: Xen Daemon error : GET operation failed: error: failed to get domain '00_16_3E_32_0F_0F' is possible bring to alive the domain 00_16_3E_32_0F_0F? thanks! > On Wed, Jun 20, 2007 at 02:38:13PM -0400, John Sanabria wrote: >> Thanks Daniel for the answer, >> according to Xen Documentation (3.0), you can start a domain using: xm create >> The must be located in /etc/xen directory. However, for Xen >> 3.1 the configuration file is not "necessary", then, you can submit the command, >> virsh start >> and the domain is created. The must be a file located in >> /var/lib/xen/images directory. But, where is located the configuration file for a domain in xen 3.1? Thanks. > > Use virsh dumpxml to get it > > And once you've edited the XML, use virsh define to load in the new config. > > Regards, > 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 > -=| > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From berrange at redhat.com Wed Jun 20 20:05:15 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 20 Jun 2007 21:05:15 +0100 Subject: [Fedora-xen] (no subject) In-Reply-To: <55412.136.145.116.114.1182369607.squirrel@ece.uprm.edu> References: <20070620184520.GE21208@redhat.com> <55412.136.145.116.114.1182369607.squirrel@ece.uprm.edu> Message-ID: <20070620200515.GF21208@redhat.com> On Wed, Jun 20, 2007 at 04:00:07PM -0400, John Sanabria wrote: > Thanks Daniel, > > i did the next: > > 1- use dd command to get a copy from a vm: > dd if=00_16_3E_32_0F_0F of=copia-00_16_3E_32_0F_0F > 2- then, ( probably big mistake :-( ) use virsh command: > virsh dumpxml 00_16_3E_32_0F_0F > ~/copia-vm.cfg > 3- i modify the copia-vm.cfg and change the name field and remove the mac > address field, defined inside of the interface tag: > --------------------- virsh dumpxml output --------------------- > > copia-00_16_3E_32_0F_0F > dd9fe09e1155f9223779b6c28bf43488 > /usr/bin/pygrub > > linux > > 262144 > 1 > destroy > restart > restart > > > > > > > dev='xvda'/> > > > > --------------------- virsh dumpxml output --------------------- > 4- virsh define copia-00_16_3E_32_0F_0F, (am i (re-)define the domain > 00_16_3E_32_0F_0F ???) > > 5- virsh start copia-00_16_3E_32_0F_0F (boot ok!, can get into the root > account, ping google.com, works! :-D) > > 6- but i don't need this domain anymore 'virsh undefine > copia-00_16_3E_32_0F_0F' > > 7- boot again the original vm: > > [root at shutdown ~]# virsh start 00_16_3E_32_0F_0F > libvir: Xen Daemon error : GET operation failed: > error: failed to get domain '00_16_3E_32_0F_0F' > > 8- oops! :-( Did you change the field in the XML when you cloned it ? If not that's probably where the mistake was. > > 9- i try to "recreate" the xml file, > a- [root at shutdown ~]# virsh dumpxml /var/lib/xen/images/00_16_3E_32_0F_0F > > original-vm.cfg > libvir: Xen Daemon error : GET operation failed: > error: failed to get domain '/var/lib/xen/images/00_16_3E_32_0F_0F' > b- [root at shutdown ~]# virsh dumpxml 00_16_3E_32_0F_0F > original-vm.cfg > libvir: Xen Daemon error : GET operation failed: > error: failed to get domain '00_16_3E_32_0F_0F' > > is possible bring to alive the domain 00_16_3E_32_0F_0F? Just edit your original dump ~/copia-vm.cfg and put back the original parameters when virsh define ~/copia-vm.cfg 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 -=| From Ralf.Koenig at itiv.uni-karlsruhe.de Wed Jun 20 16:30:26 2007 From: Ralf.Koenig at itiv.uni-karlsruhe.de (=?iso-8859-1?Q?K=F6nig=2C_Ralf?=) Date: Wed, 20 Jun 2007 18:30:26 +0200 Subject: [Fedora-xen] FC7 Xen not running properly on HP Compaq dc5750 MT Message-ID: Hi all, I have problems running the FC7 XEN kernel (2.60.20-2925.11.fc7xen) properly on a HP Compaq dc5750 MT machine. The udev service does not seem to start up, the CDROM is not working and I receive a lot of ata2.00 errors, similar to those described here http://lists.debian.org/debian-amd64/2007/04/msg00016.html If I am using the latest 2.6.21 kernel (2.6.21-1.3194.fc7) without XEN support these problems do not occur. However, this is not an alternative to me, since I need XEN. So what can I do? Is there a realistic possibility to compile a 2.6.21-1.3194 XEN enabled kernel or what other solutions to this problem do exist? Ralf From John.Sanabria at ece.uprm.edu Wed Jun 20 20:12:21 2007 From: John.Sanabria at ece.uprm.edu (John Sanabria) Date: Wed, 20 Jun 2007 16:12:21 -0400 (AST) Subject: [Fedora-xen] (no subject) In-Reply-To: <20070620184520.GE21208@redhat.com> References: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> <20070620173414.GD21208@redhat.com> <33410.136.145.116.114.1182364693.squirrel@ece.uprm.edu> <20070620184520.GE21208@redhat.com> Message-ID: <45071.136.145.116.114.1182370341.squirrel@ece.uprm.edu> Thanks ;-) > On Wed, Jun 20, 2007 at 02:38:13PM -0400, John Sanabria wrote: >> Thanks Daniel for the answer, >> >> according to Xen Documentation (3.0), you can start a domain using: >> >> xm create >> >> The must be located in /etc/xen directory. However, for >> Xen >> 3.1 the configuration file is not "necessary", then, you can submit the >> command, >> >> virsh start >> >> and the domain is created. The must be a file located >> in >> /var/lib/xen/images directory. But, where is located the configuration >> file for a domain in xen 3.1? Thanks. > > Use virsh dumpxml to get it > > And once you've edited the XML, use virsh define to load in > the new config. > > Regards, > 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 > -=| > http://ece.uprm.edu/~s047267 http://del.icio.us/josanabr http://blog-grid.blogspot.com From rjones at redhat.com Thu Jun 21 09:54:27 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 21 Jun 2007 10:54:27 +0100 Subject: [Fedora-xen] Flash 9 (ff) dies under Xen (2.6.20-2925.11.fc7xen) In-Reply-To: <1182412073.8272.53.camel@dellt-ysonohara.w2k.intra> References: <1182323657.3463.66.camel@dellt-ysonohara.w2k.intra> <46790055.2010106@redhat.com> <1182412073.8272.53.camel@dellt-ysonohara.w2k.intra> Message-ID: <467A4AD3.4080101@redhat.com> Naoki wrote: > Very sorry. Flash video is about the only thing I've tested (youtube, > google, metacafe).. > > And this will load, buffer, and then play a second and stop. Reloading > repeats the results. Metacafe seems to be slightly more tolerant and > will stall a long time, play a second, stall a long time, play a second, > and so on. > > Can't find a single thing in messages of firefox outputs. I still don't understand. This is in a guest? In dom0? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Thu Jun 21 09:57:45 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 21 Jun 2007 10:57:45 +0100 Subject: [Fedora-xen] (no subject) In-Reply-To: <20070620173414.GD21208@redhat.com> References: <44749.136.145.116.114.1182360031.squirrel@ece.uprm.edu> <20070620173414.GD21208@redhat.com> Message-ID: <467A4B99.30503@redhat.com> Daniel P. Berrange wrote: > Copy the disk image for the machine. Then copy the config, changing the > MAC address, name, UUID and path to the disk image. The other thing to add is that you probably shouldn't copy the disk image if the guest is running. To be safe, completely shut the guest down before starting the copy. I have also had good results by syncing the disks on a guest, pausing it, then copying, but I guess there are cases where that might fail. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From Travis.Formoso at blueslate.net Thu Jun 21 20:03:34 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 21 Jun 2007 16:03:34 -0400 Subject: [Fedora-xen] Problem installing xen guest on Fedora Core 7 Message-ID: All, I am trying to do a guest install using virt-install on Fedora Core 7. This is a fresh install of 7. Here is what I am getting when I try to do the install: What is the name of your virtual machine? www How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /xen/www How large would you like the disk (/xen/www) to be (in gigabytes)? 40 Would you like to enable graphics support? (yes or no) no What is the install location? nfs:172.20.1.138:/data/network-install/RPM Starting install... libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : GET operation failed: Creating storage file... 100% |=========================| 40 GB 00:00 Creating domain... 0 B 00:00 Linux version 2.6.20-2925.9.fc7xen (kojibuilder at xenbuilder4.fedora.phx.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 08:53:03 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000010800000 end: 0000000010800000 type: 1 Xen: 0000000000000000 - 0000000010800000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection Zone PFN ranges: DMA 0 -> 67584 Normal 67584 -> 67584 HighMem 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 67056 Kernel command line: method=nfs:172.20.1.138:/data/network-install/RPM Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c135f000 soft=c133f000 PID hash table entries: 2048 (order: 11, 8192 bytes) Xen reported: 2800.092 MHz processor. Console: colour dummy device 80x25 Lock dependency validator: Copyright (c) 2006 Red Hat, Inc., Ingo Molnar ... MAX_LOCKDEP_SUBCLASSES: 8 ... MAX_LOCK_DEPTH: 30 ... MAX_LOCKDEP_KEYS: 2048 ... CLASSHASH_SIZE: 1024 ... MAX_LOCKDEP_ENTRIES: 8192 ... MAX_LOCKDEP_CHAINS: 16384 ... CHAINHASH_SIZE: 8192 memory used by lock dependency info: 1064 kB per task-struct memory footprint: 1200 bytes Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Software IO TLB disabled vmalloc area: d1000000-f4ffe000, maxmem 2d7fe000 Memory: 245120k/270336k available (2030k kernel code, 16724k reserved, 1079k data, 180k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xd1000000 - 0xf4ffe000 ( 575 MB) lowmem : 0xc0000000 - 0xd0800000 ( 264 MB) .init : 0xc130e000 - 0xc133b000 ( 180 kB) .data : 0xc11fb8b9 - 0xc1309714 (1079 kB) .text : 0xc1000000 - 0xc11fb8b9 (2030 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 7007.88 BogoMIPS (lpj=14015769) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 11k freed Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 7, 524288 bytes) TCP bind hash table entries: 8192 (order: 6, 262144 bytes) TCP: Hash tables configured (established 16384 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7264k freed IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1182440856.653:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize input: Macintosh mouse button emulation as /class/input/input0 Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 180k freed Write protecting the kernel read-only data: 762k After the Write protecting it jams up and does not go any further. Anyone else run into this problem? Thanks ________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso at blueslate.net . This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From mc-al34luc at sbcglobal.net Thu Jun 21 23:29:29 2007 From: mc-al34luc at sbcglobal.net (Mike) Date: Thu, 21 Jun 2007 16:29:29 -0700 Subject: [Fedora-xen] Problem installing xen guest on Fedora Core 7 In-Reply-To: References: Message-ID: <467B09D9.3060009@sbcglobal.net> Hi Travis, It *is* working. It's just that the console has gone graphical at that point. >From a recent response I gave to someone with the same problem: Hi Alex, It *is* working. I ran into this myself with F7, and it took me a bit to figure out what was going on. Your console has been redirected to the graphical console from the serial console at that point in the guest boot process. Here's what to do: 1) Fire up virt-manager in dom-0. You'll see your guest running (xm and virsh will show it as blocked). From the 'view' menu, select the graphical console and you'll get your guest's login screen. 2) In order to have the output of your guest appear in both consoles, add the following to your guest's kernel line in grub.conf: console=tty console=xvc0,9600n8 Now you'll see all the output in both the text and the graphical console. Note that you'll also need to edit /etc/securetty and add 'xvc0', and check /etc/inittab and make sure you have a line like: co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav as well. Good luck. Mike From Travis.Formoso at blueslate.net Fri Jun 22 01:27:59 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 21 Jun 2007 21:27:59 -0400 (EDT) Subject: [Fedora-xen] Problem installing xen guest on Fedora Core 7 Message-ID: <9146243.20341182475679063.JavaMail.root@mars.blueslate.net> Mike - Is there a way to do this w/out using Virt-manager? I do not have a GUI installed on the server and the IT team does not put them on the servers. If not I guess I can install the GUI and do the installs if I have to. Thanks, Travis >Hi Travis, >It *is* working. It's just that the console has gone graphical at that >point. >From a recent response I gave to someone with the same problem: >1) Fire up virt-manager in dom-0. You'll see your guest running (xm and >virsh will show it as blocked). From the 'view' menu, select the >graphical console and you'll get your guest's login screen. Mike This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From rjones at redhat.com Fri Jun 22 10:20:15 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 22 Jun 2007 11:20:15 +0100 Subject: [Fedora-xen] Flash 9 (ff) dies under Xen (2.6.20-2925.11.fc7xen) In-Reply-To: <1182483879.17686.8.camel@dellt-ysonohara.w2k.intra> References: <1182323657.3463.66.camel@dellt-ysonohara.w2k.intra> <46790055.2010106@redhat.com> <1182412073.8272.53.camel@dellt-ysonohara.w2k.intra> <467A4AD3.4080101@redhat.com> <1182483879.17686.8.camel@dellt-ysonohara.w2k.intra> Message-ID: <467BA25F.70407@redhat.com> Naoki wrote: > On Thu, 2007-06-21 at 10:54 +0100, Richard W.M. Jones wrote: >> Naoki wrote: >>> Very sorry. Flash video is about the only thing I've tested (youtube, >>> google, metacafe).. >>> >>> And this will load, buffer, and then play a second and stop. Reloading >>> repeats the results. Metacafe seems to be slightly more tolerant and >>> will stall a long time, play a second, stall a long time, play a second, >>> and so on. >>> >>> Can't find a single thing in messages of firefox outputs. >> I still don't understand. This is in a guest? In dom0? > > Simply dom0, just boot to a xen enabled kernel and flash9 goes wonky. > Funny thing is that it's the only thing screwy with the entire system > that I can find. > > The kernel is x86_64, Firefox is i386. My best suggestion is that X isn't using acceleration in the Xen case. Try comparing the output of xdpyinfo command and also looking at /var/log/Xorg.0.log in the Xen and non-Xen cases. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From beres.laszlo at sys-admin.hu Sat Jun 23 06:14:28 2007 From: beres.laszlo at sys-admin.hu (BERES Laszlo) Date: Sat, 23 Jun 2007 08:14:28 +0200 Subject: [Fedora-xen] Live migration of full virtualized guests Message-ID: <467CBA44.8070301@sys-admin.hu> Hello there, I am totally sure I read months ago that the above is not supported, but now I don't find infos about it. So, is it true? Is any kind of full virtualized guests' migration possible in Fedora or RHEL5? Thanks, Laszlo From m3freak at thesandhufamily.ca Sat Jun 23 22:34:17 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Sat, 23 Jun 2007 18:34:17 -0400 Subject: [Fedora-xen] CentOS 4.5 domU on FC6 dom0 won't boot Message-ID: <1182638057.15475.7.camel@krs> Hi, I'm running some test to see if I can take a physical CentOS 4.5 server and convert it to a domU on a FC6 dom0 machine - a completely different server. I created a LV for the domU, and restored the CentOS 4.5 system from a backup on the LV - that was the basic install. I then cleaned up /etc/fstab accordingly (on the domU), and made sure the domU's /boot was set up properly. When I run "xm create -c webster" or "virsh start webster", the boot process gets to the point where SElinux starts, but than freezes. I've let the domU sit there for 2 hours, but it won't continue booting. I've tried setting SElinux in the domU to disabled or permissive, but neither have helped fix the boot issue. I'm not sure what's wrong. Searching for similar problems hasn't turned anything up either. Does anyone have an idea about what the problem could be? Here's the domU's config: name = "webster" bootloader = "/usr/bin/pygrub" memory = 256 disk = [ "phy:vg00/webster,sda1,w","phy:vg00/swap2,sda2,w" ] vif = [ '' ] #vnc = "1" #vncunused = "1" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" And here's the boot log: [root at xenmaster ~]# xm create -c webster Using config file "/etc/xen/webster". Going to boot CentOS (2.6.9-55.ELxenU) kernel: /boot/vmlinuz-2.6.9-55.ELxenU initrd: /boot/custom-initrd-2.6.9-55.ELxenU.img Started domain webster Linux version 2.6.9-55.ELxenU (mockbuild at builder6.centos.org) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Wed May 2 14:49:26 EDT 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010000000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection IRQ lockup detection disabled Built 1 zonelists Kernel command line: ro root=/dev/sda1 3 Initializing CPU#0 CPU 0 irqstacks, hard=c0338000 soft=c0318000 PID hash table entries: 2048 (order: 11, 32768 bytes) Xen reported: 2392.028 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) vmalloc area: d1000000-f4ffe000, maxmem 2d800000 Memory: 253728k/270336k available (1450k kernel code, 8388k reserved, 539k data, 124k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 1189k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 VCPUs xen_mem: Initialising balloon driver. audit: initializing netlink socket (disabled) audit(1182637492.361:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key FBAD6F8AE400BF26 - User ID: CentOS (Kernel Module GPG key) rtc: IRQ 8 is not free. i8042.c: No controller found. RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.9-55.ELxenU (mockbuild at builder6.centos.org) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-8)) #1 SMP Wed May 2 14:49:26 EDT 2007 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010000000 (usable) 0MB HIGHMEM available. 264MB LOWMEM available. Using x86 segment limits to approximate NX protection IRQ lockup detection disabled Built 1 zonelists Kernel command line: ro root=/dev/sda1 3 Initializing CPU#0 CPU 0 irqstacks, hard=c0338000 soft=c0318000 PID hash table entries: 2048 (order: 11, 32768 bytes) Xen reported: 2392.028 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) vmalloc area: d1000000-f4ffe000, maxmem 2d800000 Memory: 253728k/270336k available (1450k kernel code, 8388k reserved, 539k data, 124k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Security Scaffold v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode There is already a security framework initialized, register_security failed. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 1189k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 VCPUs xen_mem: Initialising balloon driver. audit: initializing netlink socket (disabled) audit(1182637492.361:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key FBAD6F8AE400BF26 - User ID: CentOS (Kernel Module GPG key) rtc: IRQ 8 is not free. i8042.c: No controller found. RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. mice: PS/2 mouse device common for all mice md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 6, 262144 bytes) TCP bind hash table entries: 16384 (order: 5, 196608 bytes) TCP: Hash tables configured (established 16384 bind 16384) Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 124k freed Red Hat nash version 4.2.1.10 starting Mounted /proc filesystem Mounting sysfs Creating /dev Starting udev Loading xenblk.ko module Registering block device major 8 Using cfq io scheduler Loading jbd.ko module Loading ext3.ko module Creating root device Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. mount: error 2 mounting none Switching to new root security: 3 users, 4 roles, 355 types, 26 bools security: 55 classes, 22610 rules SELinux: Completing initialization. SELinux: Setting up existing superblocks. SELinux: initialized (dev sda1, type ext3), uses xattr SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev selinuxfs, type selinuxfs), uses genfs_contexts SELinux: initialized (dev mqueue, type mqueue), not configured for labeling SELinux: initialized (dev devpts, type devpts), uses transition SIDs SELinux: initialized (dev eventpollfs, type eventpollfs), uses genfs_contexts SELinux: initialized (dev pipefs, type pipefs), uses task SIDs SELinux: initialized (dev tmpfs, type tmpfs), uses transition SIDs SELinux: initialized (dev futexfs, type futexfs), uses genfs_contexts SELinux: initialized (dev sockfs, type sockfs), uses task SIDs SELinux: initialized (dev proc, type proc), uses genfs_contexts SELinux: initialized (dev bdev, type bdev), uses genfs_contexts SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts Thanks, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 18:25:35 up 14 days, 9:12, 2 users, load average: 0.18, 0.47, 0.46 From clalance at redhat.com Sun Jun 24 02:13:26 2007 From: clalance at redhat.com (Chris Lalancette) Date: Sat, 23 Jun 2007 22:13:26 -0400 Subject: [Fedora-xen] CentOS 4.5 domU on FC6 dom0 won't boot In-Reply-To: <1182638057.15475.7.camel@krs> References: <1182638057.15475.7.camel@krs> Message-ID: <467DD346.5020900@redhat.com> Kanwar Ranbir Sandhu wrote: > > When I run "xm create -c webster" or "virsh start webster", the boot > process gets to the point where SElinux starts, but than freezes. I've > let the domU sit there for 2 hours, but it won't continue booting. I've > tried setting SElinux in the domU to disabled or permissive, but neither > have helped fix the boot issue. > Are you sure that it is "frozen", and just not showing a login console? If you boot the domain with kernel parameter "console=xvc0", do you then see more init messages, and eventually a console? Chris Lalancette From alpot at mylinuxsite.com Sun Jun 24 12:57:28 2007 From: alpot at mylinuxsite.com (Alfredo P. Ricafort) Date: Sun, 24 Jun 2007 20:57:28 +0800 Subject: [Fedora-xen] Can't find CDROM after installing Win2k Message-ID: <1182689848.5680.4.camel@mylinuxsite.com> Hi, I installed Win2k as guest os in my FC7 host. When win2k performed setup post installation it tries to look for some files in GLOBALROOT\DEVICE \CDROM\i386 which it cannot find. How do I configure my guest os to see my CDROM device and continue on with my installation? Tks. From songtao.liu at mytum.de Sun Jun 24 15:09:31 2007 From: songtao.liu at mytum.de (Songtao Liu) Date: Sun, 24 Jun 2007 17:09:31 +0200 Subject: =?iso-8859-1?q?Re=3A_=5BFedora-xen=5D_Can=27t_find_CDROM_after_installing?= =?iso-8859-1?q?_Win2k?= Message-ID: Hi, I have also encountered this problem before in Fedora6 :) but I use Windows image, not CD, here is my steps, maybe will give you some hints 1. Open the VM and do it via wizard step by step. 2. After the Virtual Machine Console pops up, install the OS as normal installation. 3. When the system says to press F6, make sure to Press F5 and select "standard PC" and continue. 4. Choose to format the C:\ partition in FAT file system format because Linux isn't compatible with NTFS kernel modules(in fact it works). Mounting or writing files to Xen guest image may not be as straight-forward if you were to format in NTFS. 5. After reboot, we should fix the WinXP image in order to avoid the coming problem by installation. #losetup -f #losetup /dev/loop0 /xen/winxp #kpartx -av /dev/loop0 #mount /dev/mapper/loop0p1 /mnt/winxp #mount /WinXPimage/winxp.iso /mnt/tmp/ #cp -prv /mnt/tmp/I386 /mnt/winxp #umount /mnt/winxp #umount /mnt/tmp/ 6. Restart the guest OS with 'xm create winxp'. When the 'file needed' dialog window comes up, input the path as c:\i386. Then everything should be smooth. Maybe you should input the path c:\i386 many times, as it the path will not be remembered. Hope it helps. Songtao Original Message: Hi,

I installed Win2k as guest os in my FC7 host. When win2k performed setup
post installation it tries to look for some files in GLOBALROOT\DEVICE
\CDROM\i386 which it cannot find.

How do I configure my guest os to see my CDROM device and continue on
with my installation?

Tks.




--
Fedora-xen mailing list
Fedora-xen at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-xen
-- From chris at tylers.info Sun Jun 24 22:44:14 2007 From: chris at tylers.info (Chris Tyler) Date: Sun, 24 Jun 2007 18:44:14 -0400 Subject: [Fedora-xen] F7 x86_64 Xen - Can't start xend - wrong ELF class In-Reply-To: <20070624160009.BFE65731ED@hormel.redhat.com> References: <20070624160009.BFE65731ED@hormel.redhat.com> Message-ID: <1182725054.9787.9.camel@concord3.proximity.on.ca> I've been using Xen under FC6 for some time. I have an FC6 domU that I want to migrate to a new box, which is running F7 x86_64. I'm having an awful time getting Xen up on the new box; the problem that I'm seeing looks like it may be a FAQ but I haven't find any other mentions of it. I have the hypervisor and dom0 running fine, but I can't run xend: ----------------------------------------------------------------- # service xend start Starting xend: Traceback (most recent call last): File "/usr/sbin/xend", line 34, in from xen.xend.server import SrvDaemon File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py", line 20, in import xen.lowlevel.xc ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: wrong ELF class: ELFCLASS32 (...snip...) ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: wrong ELF class: ELFCLASS32 .Traceback (most recent call last): File "/usr/sbin/xend", line 34, in from xen.xend.server import SrvDaemon File "/usr/lib/python2.5/site-packages/xen/xend/server/SrvDaemon.py", line 20, in import xen.lowlevel.xc ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: wrong ELF class: ELFCLASS32 ----------------------------------------------------------------- Looks like that file is expected to be a 64-bit binary but is 32-bit (?). Not sure how to get a 64-bit version; the file is owned by package 'xen' (3.1.0-0.rc7.1.fc7) but the only version available appears to be i386. Any pointers would be appreciated!-- -Chris From m3freak at thesandhufamily.ca Mon Jun 25 00:07:06 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Sun, 24 Jun 2007 20:07:06 -0400 Subject: [Fedora-xen] CentOS 4.5 domU on FC6 dom0 won't boot In-Reply-To: <467DD346.5020900@redhat.com> References: <1182638057.15475.7.camel@krs> <467DD346.5020900@redhat.com> Message-ID: <1182730026.15475.12.camel@krs> On Sat, 2007-06-23 at 22:13 -0400, Chris Lalancette wrote: > Are you sure that it is "frozen", and just not showing a login console? > If you boot the domain with kernel parameter "console=xvc0", do you > then see more init messages, and eventually a console? That didn't change anything, unfortunately. It still appears to be pausing at the same spot. Kind of confused at this point. The xen logs don't have anything useful in them either. Perhaps it's just a SElinux problem in the domU. I may eventually just install a brand new CentOS 5 domU, but I'd much, much, much rather transfer the physical CentOS 4.5 server to a domU. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 19:54:45 up 15 days, 10:41, 2 users, load average: 0.12, 0.10, 0.09 From markryde at gmail.com Mon Jun 25 14:50:12 2007 From: markryde at gmail.com (Mark Ryden) Date: Mon, 25 Jun 2007 17:50:12 +0300 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? Message-ID: Hello, I have Fedora Core 6 on x86_64 machine. I want to build the virt-manager latest from mercurial repository. I follwed the instructions on the web: http://virt-manager.et.redhat.com/scmrepo.html I had performed "hg clone http://hg.et.redhat.com/virt/applications/virt-manager--devel" and them ran: ./autobuild.sh make: *** No rule to make target `distclean'. aclocal:configure.ac:6: warning: macro `AM_GNU_GETTEXT_VERSION' not found in library aclocal:configure.ac:7: warning: macro `AM_GNU_GETTEXT' not found in library configure.ac: installing `./install-sh' configure.ac: installing `./missing' src/graphWidgets/Makefile.am: installing `./compile' src/graphWidgets/Makefile.am: installing `./depcomp' configure.ac:6: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:7: error: possibly undefined macro: AM_GNU_GETTEXT I have on this FC6: gettext-0.14.6-3.fc6, (from rpm of the original installation) , intltool-0.35.5 (build from source). Why is it so ? what should I do ? Regards, Mark From berrange at redhat.com Mon Jun 25 15:00:44 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 25 Jun 2007 16:00:44 +0100 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? In-Reply-To: References: Message-ID: <20070625150044.GB23311@redhat.com> On Mon, Jun 25, 2007 at 05:50:12PM +0300, Mark Ryden wrote: > Hello, > > I have Fedora Core 6 on x86_64 machine. > I want to build the virt-manager latest from mercurial repository. > I follwed the instructions on the web: > http://virt-manager.et.redhat.com/scmrepo.html > > I had performed > "hg clone http://hg.et.redhat.com/virt/applications/virt-manager--devel" > > and them ran: > > ./autobuild.sh > make: *** No rule to make target `distclean'. > aclocal:configure.ac:6: warning: macro `AM_GNU_GETTEXT_VERSION' not > found in library > aclocal:configure.ac:7: warning: macro `AM_GNU_GETTEXT' not found in library > configure.ac: installing `./install-sh' > configure.ac: installing `./missing' > src/graphWidgets/Makefile.am: installing `./compile' > src/graphWidgets/Makefile.am: installing `./depcomp' > configure.ac:6: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure.ac:7: error: possibly undefined macro: AM_GNU_GETTEXT > > I have on this FC6: gettext-0.14.6-3.fc6, (from rpm of > the original installation) , intltool-0.35.5 (build from source). > > Why is it so ? what should I do ? Sounds like you are missing the 'gettext-devel' package $ grep -l AM_GNU_GETTEXT_VERSION /usr/share/aclocal/*.m4 /usr/share/aclocal/gettext.m4 $ rpm -qf /usr/share/aclocal/gettext.m4 gettext-devel-0.14.6-4.fc6 Regards, 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 -=| From jcastro at instant.com.br Mon Jun 25 15:45:42 2007 From: jcastro at instant.com.br (Juan Carlos Castro y Castro) Date: Mon, 25 Jun 2007 12:45:42 -0300 Subject: [Fedora-xen] Confused on how to have each guest reach a VLAN Message-ID: <467FE326.3040005@instant.com.br> Both my host and guests are Fedora 6. My first, naive thought, was to just configure eth0.N within each guest OS. For testing purposes, I created eth0.69 both within guest01 and guest02, with addresses 10.11.12.101 and 10.1.12.102 respectively. But guest01 and guest02 can't ping one another through these new addresses. I read http://wiki.xensource.com/xenwiki/XenNetworking and, in its last paragraph, it suggests I have to configure VLAN in the host OS, and add virtual interfaces to a bridge. But I'm confused about how to do that. Which interfaces do I have to create? Do I have to add them to the xenbr0 bridge? Can I have this start automagically upon "xm create"? Below are my ifconfig on the host machine, and the config files for the two guests (they have IDs 5 and 6): ---------------------------------------------------------------------- eth0 Link encap:Ethernet HWaddr 00:15:17:23:7D:6D inet addr:192.168.0.195 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::215:17ff:fe23:7d6d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:159825 errors:0 dropped:0 overruns:0 frame:0 TX packets:62265 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:41732783 (39.7 MiB) TX bytes:61710095 (58.8 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:4123270 errors:0 dropped:0 overruns:0 frame:0 TX packets:4123270 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:377591540 (360.0 MiB) TX bytes:377591540 (360.0 MiB) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1552519 errors:0 dropped:0 overruns:0 frame:0 TX packets:324298 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:2101900272 (1.9 GiB) TX bytes:84510344 (80.5 MiB) Base address:0x2000 Memory:48180000-481a0000 tap0 Link encap:Ethernet HWaddr CA:C9:C4:AB:3E:A6 inet6 addr: fe80::c8c9:c4ff:feab:3ea6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:349 errors:0 dropped:0 overruns:0 frame:0 TX packets:1710 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:104729 (102.2 KiB) TX bytes:928665 (906.8 KiB) tap1 Link encap:Ethernet HWaddr 0E:3E:CA:31:FB:7A inet6 addr: fe80::c3e:caff:fe31:fb7a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37 errors:0 dropped:0 overruns:0 frame:0 TX packets:1195 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:2922 (2.8 KiB) TX bytes:874780 (854.2 KiB) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:62278 errors:0 dropped:0 overruns:0 frame:0 TX packets:159837 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:61715017 (58.8 MiB) TX bytes:41733575 (39.8 MiB) vif5.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif6.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:6844 (6.6 KiB) xenbr0 Link encap:Ethernet HWaddr 0E:3E:CA:31:FB:7A UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:97424 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:25040439 (23.8 MiB) TX bytes:0 (0.0 b) ---------------------------------------------------------------------- name = "guest01" uuid = "6ab45a27-0718-5dc1-d235-1704e4273870" maxmem = 192 memory = 192 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 0 apic = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "file:/var/lib/xen/images/guest01,hda,w" ] vif = [ "mac=00:16:3e:13:61:c3,bridge=xenbr0,type=ioemu" ] serial = "pty" ---------------------------------------------------------------------- name = "guest02" uuid = "6ab45a27-0718-5dc1-d235-1704e4273871" maxmem = 192 memory = 192 vcpus = 1 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 0 apic = 0 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "file:/var/lib/xen/images/guest02,hda,w" ] vif = [ "mac=00:16:3e:13:61:c4,bridge=xenbr0,type=ioemu" ] serial = "pty" ---------------------------------------------------------------------- From chris at tylers.info Mon Jun 25 16:12:36 2007 From: chris at tylers.info (Chris Tyler) Date: Mon, 25 Jun 2007 12:12:36 -0400 Subject: [Fedora-xen] F7 x86_64 Xen - Can't start xend - wrong ELF class In-Reply-To: <20070625160010.6AB767369B@hormel.redhat.com> References: <20070625160010.6AB767369B@hormel.redhat.com> Message-ID: <1182787956.28145.18.camel@concord3.proximity.on.ca> > ImportError: /usr/lib/python2.5/site-packages/xen/lowlevel/xc.so: wrong > ELF class: ELFCLASS32 > ----------------------------------------------------------------- > > Looks like that file is expected to be a 64-bit binary but is 32-bit > (?). Not sure how to get a 64-bit version; the file is owned by package > 'xen' (3.1.0-0.rc7.1.fc7) but the only version available appears to be > i386. Solved - problem with a local repo mirror (red face!). -- Chris Tyler From m3freak at thesandhufamily.ca Mon Jun 25 16:24:53 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Mon, 25 Jun 2007 12:24:53 -0400 Subject: [Fedora-xen] CentOS 4.5 domU on FC6 dom0 won't boot In-Reply-To: <1182638057.15475.7.camel@krs> References: <1182638057.15475.7.camel@krs> Message-ID: <1182788693.15475.23.camel@krs> On Sat, 2007-06-23 at 18:34 -0400, Kanwar Ranbir Sandhu wrote: > When I run "xm create -c webster" or "virsh start webster", the boot > process gets to the point where SElinux starts, but than freezes. I've > let the domU sit there for 2 hours, but it won't continue booting. I've > tried setting SElinux in the domU to disabled or permissive, but neither > have helped fix the boot issue. Does anyone have any ideas on this? I'm stumped. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 12:23:57 up 16 days, 3:10, 3 users, load average: 0.19, 0.19, 0.18 From m3freak at thesandhufamily.ca Mon Jun 25 16:28:39 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Mon, 25 Jun 2007 12:28:39 -0400 Subject: [Fedora-xen] resizing Xen para-virtualized guest partition In-Reply-To: <20070617062659.15e34645.jlayton@redhat.com> References: <463F5E53.80600@redhat.com> <1182000627.18059.29.camel@krs> <20070617062659.15e34645.jlayton@redhat.com> Message-ID: <1182788920.15475.27.camel@krs> On Sun, 2007-06-17 at 06:26 -0400, Jeff Layton wrote: > ...reboot the domU, since it'll still be in use. When it comes back, it > should see the new partition table. Now (assuming the PV for the domU > volgroup is /dev/xvda2): > > root at domU# pvresize /dev/xvda2 Damn! I figured everything else out, and this step completely escaped me! I figured I had to resize the LV, but didn't realize that the fdisk bit actually changed the size of the "disk". Thanks for the pointer. I'm going to try it out - I'm sure it will work. -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 12:28:31 up 16 days, 3:15, 3 users, load average: 0.37, 0.27, 0.20 From dlbewley at lib.ucdavis.edu Mon Jun 25 17:29:52 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Mon, 25 Jun 2007 10:29:52 -0700 (PDT) Subject: [Fedora-xen] f7 trunk dom0 ifcfg startup creates 2 bridge no vlan int Message-ID: <594565068.1618851182792592766.JavaMail.root@zebra.lib.ucdavis.edu> I'm trying to configure Fedora 7 to support a 802.1q trunk in dom0 using https://www.redhat.com/archives/fedora-xen/2007-June/msg00008.html and http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt for clues. Since the network-bridge script doesn't seem capable of doing to VLAN work and I prefer the normal OS scripts, I have the following in xend-config.sxp: (network-script /bin/true) (vif-script /bin/true) It seems that the Fedora goal is to take the original name for an interface, in this case eth0.6 and make that a bridge and move its guts to something like peth0.6. I don't wanna be deprecated so I tried to play along and setup the ifcfg files like so: [root at helix network-scripts]# cat ifcfg-eth0 # Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet DEVICE=eth0 MTU=1504 BOOTPROTO=dhcp ONBOOT=yes [root at helix network-scripts]# cat ifcfg-vlan6br DEVICE=eth0.6 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=19.27.25.134 NETMASK=255.255.255.192 NETWORK=19.27.25.128 BROADCAST=19.27.25.191 [root at helix network-scripts]# cat ifcfg-vlan6phy DEVICE=peth0.6 BRIDGE=eth0.6 VLAN=yes ONBOOT=yes BOOTPROTO=none But, this creates a bridge under both names and no vlan interface [root at helix ~]# brctl show bridge name bridge id STP enabled interfaces eth0.6 8000.000000000000 no peth0.6 8000.000000000000 no [root at helix network-scripts]# ls /proc/net/vlan ls: cannot access /proc/net/vlan: No such file or directory I'll dissect the ifup scripts when I get a second, but am I swimming upstream or just making a dumb mistake somewhere? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From berrange at redhat.com Mon Jun 25 17:34:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 25 Jun 2007 18:34:24 +0100 Subject: [Fedora-xen] f7 trunk dom0 ifcfg startup creates 2 bridge no vlan int In-Reply-To: <594565068.1618851182792592766.JavaMail.root@zebra.lib.ucdavis.edu> References: <594565068.1618851182792592766.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <20070625173424.GE23311@redhat.com> On Mon, Jun 25, 2007 at 10:29:52AM -0700, Dale Bewley wrote: > I'm trying to configure Fedora 7 to support a 802.1q trunk > in dom0 using > https://www.redhat.com/archives/fedora-xen/2007-June/msg00008.html > and > http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt > for clues. > > Since the network-bridge script doesn't seem capable of doing to VLAN work > and I prefer the normal OS scripts, I have the following in xend-config.sxp: > (network-script /bin/true) This is good. > (vif-script /bin/true) This still needs to be vif-bridge - since this is the script used to connect the guest interface to the bridge device for the VLAN you're creating later. > It seems that the Fedora goal is to take the original name for an > interface, in this case eth0.6 and make that a bridge and move its > guts to something like peth0.6. > I don't wanna be deprecated so I tried to play along and setup > the ifcfg files like so: > > [root at helix network-scripts]# cat ifcfg-eth0 > # Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet > DEVICE=eth0 > MTU=1504 > BOOTPROTO=dhcp > ONBOOT=yes > > [root at helix network-scripts]# cat ifcfg-vlan6br > DEVICE=eth0.6 > TYPE=Bridge > BOOTPROTO=static > ONBOOT=yes > IPADDR=19.27.25.134 > NETMASK=255.255.255.192 > NETWORK=19.27.25.128 > BROADCAST=19.27.25.191 > > [root at helix network-scripts]# cat ifcfg-vlan6phy > DEVICE=peth0.6 > BRIDGE=eth0.6 > VLAN=yes > ONBOOT=yes > BOOTPROTO=none Hmm, does it make any difference if you make the ifcfg-XXX script name match the DEVICE= name, eg instead of ifcfg-vlan6phy have ifcfg-peth0.6 And instead of ifcfg-vlan6br have ifcfg-eth0.6 > > But, this creates a bridge under both names and no vlan interface > > [root at helix ~]# brctl show > bridge name bridge id STP enabled interfaces > eth0.6 8000.000000000000 no > peth0.6 8000.000000000000 no > > [root at helix network-scripts]# ls /proc/net/vlan > ls: cannot access /proc/net/vlan: No such file or directory > > I'll dissect the ifup scripts when I get a second, but am I swimming > upstream or just making a dumb mistake somewhere? 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 -=| From dlbewley at lib.ucdavis.edu Mon Jun 25 17:53:25 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Mon, 25 Jun 2007 10:53:25 -0700 (PDT) Subject: [Fedora-xen] f7 trunk dom0 ifcfg startup creates 2 bridge no vlan int In-Reply-To: <20070625173424.GE23311@redhat.com> Message-ID: <615546864.1619931182794005636.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Daniel P. Berrange" wrote: > On Mon, Jun 25, 2007 at 10:29:52AM -0700, Dale Bewley wrote: > > (vif-script /bin/true) > > This still needs to be vif-bridge - since this is the script used to > connect > the guest interface to the bridge device for the VLAN you're creating > later. Thanks > > It seems that the Fedora goal is to take the original name for an > > interface, in this case eth0.6 and make that a bridge and move its > > guts to something like peth0.6. > > > I don't wanna be deprecated so I tried to play along and setup > > the ifcfg files like so: > > > > Hmm, does it make any difference if you make the ifcfg-XXX script > name > match the DEVICE= name, eg instead of ifcfg-vlan6phy have > ifcfg-peth0.6 > And instead of ifcfg-vlan6br have ifcfg-eth0.6 Seems not. Still 2 bridges with no interfaces assigned to them. bridge name bridge id STP enabled interfaces eth0.6 8000.000000000000 no peth0.6 8000.000000000000 no And still no /proc/net/vlan. Yes, VLANs do work if I configure them normally. i.e. # ifup vlan16 # ls /proc/net/vlan/ config eth0.16 -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From dlbewley at lib.ucdavis.edu Mon Jun 25 20:25:02 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Mon, 25 Jun 2007 13:25:02 -0700 (PDT) Subject: [Fedora-xen] Confused on how to have each guest reach a VLAN In-Reply-To: <467FE326.3040005@instant.com.br> Message-ID: <1494994057.1624081182803102151.JavaMail.root@zebra.lib.ucdavis.edu> You could create each vlan in your dom0 like this # cat ifcfg-vlan20 DEVICE=eth0.20 BOOTPROTO=static ONBOOT=yes VLAN=yes BRIDGE=xenbr20 And define a bridge for each one like this # cat ifcfg-xenbr20 DEVICE=xenbr20 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=172.19.20.253 NETMASK=255.255.255.128 NETWORK=172.19.20.128 BROADCAST=172.19.20.255 Then edit your domU config to use xenbr20 etc.* Comment out the network-bridge script in your xend config. When you fire up the instance Xen will create the virtual interface on the fly. The domU doesn't know or care what broadcast domain (VLAN) it is in. It only knows it's subnet information. You might put a dhcp server on VLAN 20 above and tell all your domU's to use BOOTPROTO=dhcp. *This format for the bridge name is deprecated in Fedora 7, but it works. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From markryde at gmail.com Tue Jun 26 06:35:12 2007 From: markryde at gmail.com (Mark Ryden) Date: Tue, 26 Jun 2007 09:35:12 +0300 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? In-Reply-To: <20070625150044.GB23311@redhat.com> References: <20070625150044.GB23311@redhat.com> Message-ID: Hello, - Thanks all. - Ok, I ran: "yum install gettext-devel" and installed gettext-devel-0.14.6-4.fc6. Now: running: ./autobuild.sh gives: make: *** No rule to make target `distclean'. libtoolize: `config.guess' exists: use `--force' to overwrite libtoolize: `config.sub' exists: use `--force' to overwrite libtoolize: `ltmain.sh' exists: use `--force' to overwrite checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes ../configure: line 1977: syntax error near unexpected token `0.35.0,' ../configure: line 1977: `IT_PROG_INTLTOOL(0.35.0, no-xml)' line 1977 includes : where: IT_PROG_INTLTOOL(0.35.0, no-xml) As I said, I have intltool-0.35.5 on this machine (built and installed from source tar file). Any ideas ? Regards, Mark On 6/25/07, Daniel P. Berrange wrote: > On Mon, Jun 25, 2007 at 05:50:12PM +0300, Mark Ryden wrote: > > Hello, > > > > I have Fedora Core 6 on x86_64 machine. > > I want to build the virt-manager latest from mercurial repository. > > I follwed the instructions on the web: > > http://virt-manager.et.redhat.com/scmrepo.html > > > > I had performed > > "hg clone http://hg.et.redhat.com/virt/applications/virt-manager--devel" > > > > and them ran: > > > > ./autobuild.sh > > make: *** No rule to make target `distclean'. > > aclocal:configure.ac:6: warning: macro `AM_GNU_GETTEXT_VERSION' not > > found in library > > aclocal:configure.ac:7: warning: macro `AM_GNU_GETTEXT' not found in library > > configure.ac: installing `./install-sh' > > configure.ac: installing `./missing' > > src/graphWidgets/Makefile.am: installing `./compile' > > src/graphWidgets/Makefile.am: installing `./depcomp' > > configure.ac:6: error: possibly undefined macro: AM_GNU_GETTEXT_VERSION > > If this token and others are legitimate, please use m4_pattern_allow. > > See the Autoconf documentation. > > configure.ac:7: error: possibly undefined macro: AM_GNU_GETTEXT > > > > I have on this FC6: gettext-0.14.6-3.fc6, (from rpm of > > the original installation) , intltool-0.35.5 (build from source). > > > > Why is it so ? what should I do ? > > Sounds like you are missing the 'gettext-devel' package > > $ grep -l AM_GNU_GETTEXT_VERSION /usr/share/aclocal/*.m4 > /usr/share/aclocal/gettext.m4 > > $ rpm -qf /usr/share/aclocal/gettext.m4 > gettext-devel-0.14.6-4.fc6 > > > Regards, > 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 -=| > From rjones at redhat.com Tue Jun 26 15:35:44 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 26 Jun 2007 16:35:44 +0100 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? In-Reply-To: References: <20070625150044.GB23311@redhat.com> Message-ID: <46813250.2060306@redhat.com> Mark Ryden wrote: > Hello, > - Thanks all. > > - Ok, I ran: "yum install gettext-devel" and installed > gettext-devel-0.14.6-4.fc6. > Now: > running: > ./autobuild.sh > gives: > make: *** No rule to make target `distclean'. > libtoolize: `config.guess' exists: use `--force' to overwrite > libtoolize: `config.sub' exists: use `--force' to overwrite > libtoolize: `ltmain.sh' exists: use `--force' to overwrite > checking for a BSD-compatible install... /usr/bin/install -c > checking whether build environment is sane... yes > checking for gawk... gawk > checking whether make sets $(MAKE)... yes > ../configure: line 1977: syntax error near unexpected token `0.35.0,' > ../configure: line 1977: `IT_PROG_INTLTOOL(0.35.0, no-xml)' > line 1977 includes : > where: IT_PROG_INTLTOOL(0.35.0, no-xml) > > As I said, I have intltool-0.35.5 on this machine (built and installed > from source tar file). Couple of questions: Does your aclocal.m4 file contain a definition of IT_PROG_INTLTOOL? The definition starts like this: dnl IT_PROG_INTLTOOL([MINIMUM-VERSION], [no-xml]) # serial 35 IT_PROG_INTLTOOL AC_DEFUN([IT_PROG_INTLTOOL], [AC_PREREQ([2.50])dnl etc. You mentioned in your first email that you're trying to compile this on FC6, in which case you should have all these tools available through yum, ie: yum install intltool You shouldn't need to rebuild anything (except the latest virt-manager) from source ... Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From tom.horsley at att.net Tue Jun 26 17:04:56 2007 From: tom.horsley at att.net (Tom Horsley) Date: Tue, 26 Jun 2007 13:04:56 -0400 Subject: [Fedora-xen] FC6 xen bugfixes planned? Message-ID: <20070626130456.72c98136@zooty> Just ran into a bug with all the HVMs I have running under Xen with a 64 bit AMD host (FC6). Apparently the int3 debugger trap instruction gets the wrong PC reported in the VMs, so it is a pain in the patoot to do debugger development on Xen guests :-). (Search google for "hvm int3 amd" and you can find references to patches that are fairly recent - a lot more recent than the version of Xen provided with FC6). Any planned bugfixes in the pipe for Xen on FC6, or should I look at swapping in some completely different host? From phil at pricom.com.au Tue Jun 26 19:07:48 2007 From: phil at pricom.com.au (Phil Rhoades) Date: Wed, 27 Jun 2007 05:07:48 +1000 Subject: [Fedora-xen] Problem installing xen guest on Fedora Core 7 In-Reply-To: <467B09D9.3060009@sbcglobal.net> References: <467B09D9.3060009@sbcglobal.net> Message-ID: <1182884868.19080.0.camel@prix.pricom.com.au> Mike, On Thu, 2007-06-21 at 16:29 -0700, Mike wrote: > Hi Travis, > > It *is* working. It's just that the console has gone graphical at that > point. > > >From a recent response I gave to someone with the same problem: > > Hi Alex, > > It *is* working. I ran into this myself with F7, and it took me a bit to > figure out what was going on. Your console has been redirected to the > graphical console from the serial console at that point in the guest > boot process. Here's what to do: > > 1) Fire up virt-manager in dom-0. You'll see your guest running (xm and > virsh will show it as blocked). Correct so far. > From the 'view' menu, select the > graphical console and you'll get your guest's login screen. I get: "The console is currently unavailable" The serial console just shows a black screen with the cursor flashing in the top-left corner . . So I can't get to the stuff below . . Thanks, Phil. > 2) In order to have the output of your guest appear in both consoles, > add the following to your guest's kernel line in grub.conf: > > console=tty console=xvc0,9600n8 > > Now you'll see all the output in both the text and the graphical console. > > Note that you'll also need to edit /etc/securetty and add 'xvc0', and > check /etc/inittab and make sure you have a line like: > > co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav > > as well. > > Good luck. > > Mike > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Fax: +61:(0)2-8221-9599 E-mail: phil at pricom.com.au From mc-al34luc at sbcglobal.net Tue Jun 26 19:34:37 2007 From: mc-al34luc at sbcglobal.net (Mike) Date: Tue, 26 Jun 2007 12:34:37 -0700 Subject: [Fedora-xen] FWIW: Howto for building F7 and FC6 xen kernels + xen w/o PAE ... Message-ID: <46816A4D.5020602@sbcglobal.net> Hi All, I've successfully built the F7 source RPMS for the xen kernel + xen 3.1 w/o PAE, and it works ok on my PAE-capable dual Xeon w/ 1GB ram. I'm able to run the following non-pae guests: freeBSD, NetBSD, as well as my non-PAE F6 and F7 Guests of course. I followed the wiki instructions here: http://fedoraproject.org/wiki/Docs/CustomKernel With the following modifications: F7: Using kernel-xen-2.6-2.6.20-2925.11.fc7.src.rpm: a) with menuconfig, in "processor type and features", "High Memory Support", I selected "off" (I only have 1GB of memory. Selecting "4GB" would also work just as well). I also turned off "64 bit Memory and IO resources (EXPERIMENTAL)". b) Just before starting the final rpmbuild, I edited the spec file and set pae=n. The difference between the standard xen spec file and mine were: 591B> diff kernel-xen.spec *pae* 35c35 < %define release %(R="$Revision: 2925.11 $"; RR="${R##: }"; echo ${RR%%?})%{?dist} --- > %define release %(R="$Revision: 2925.11 $"; RR="${R##: }"; echo ${RR%%?}).NO_PAE%{?dist} 97,98c97,98 < # we build always xen HV with pae < %define xen_flags verbose=y crash_debug=y pae=y --- > # we build always xen HV with pae - No we don't. > %define xen_flags verbose=y crash_debug=y pae=n I installed the resultant RPM on Dom0 and my F7 guests. Note you'll need to specify --oldpackage, since rpm thinks the currently installed, redhat-built 2925.11 version is newer for some reason. Reboot ... Now you're non-PAE, and can utilize all those non-PAE guests out there. And you can switch back and forth between PAE/non-PAE, by choosing the appropriate versions of the kernel on dom0 and guests. FC6 (built for use by my FC6 guest): Just like F7, with the following exceptions: a) I used kernel-2.6.20-1.2962.fc6.src.rpm b) Spec file changes (kernel-2.6.spec) look like: 36c36,37 < %define with_xenonly %{?_with_xenonly: 1} %{?!_with_xenonly: 0} --- > #%define with_xenonly %{?_with_xenonly: 1} %{?!_with_xenonly: 0} > %define with_xenonly 1 64c65 < %define release %(R="$Revision: 1.2962 $"; RR="${R##: }"; echo ${RR%%?})%{?dist}%{?buildid} --- > %define release %(R="$Revision: 1.2962 $"; RR="${R##: }"; echo > ${RR%%?}).NO_PAE.%{?dist}%{?buildid} 178,179c179,180 < # we build always xen i686 HV with pae < %define xen_flags verbose=y crash_debug=y pae=y --- > # we build always xen i686 HV with pae - No we don't. > %define xen_flags verbose=y crash_debug=y pae=n I haven't tried to see if FC5 guests work - I suspect they will. Enjoy, Mike From mc-al34luc at sbcglobal.net Wed Jun 27 00:48:33 2007 From: mc-al34luc at sbcglobal.net (Mike) Date: Tue, 26 Jun 2007 17:48:33 -0700 Subject: [Fedora-xen] FC6 guest save/restore: serious clock drift... Message-ID: <4681B3E1.6010103@sbcglobal.net> Hi folks, I had a FC6 guest which was doing a kernel build while running on a F7 system. Due to a power outage and waning UPS battery capacity, I saved the FC6 image. Once power was restored a few hours later, I restored the FC6 guest, and observed it picked up in its build right were it left off. Cool, I thought - until the build crashed because the FC6 guest's clock was almost 24 hours in the past when compared to the correct time on the F7 system it was hosted on. Has anyone else observed this guest clock drift behavior with save/restore? TIA, Mike From xcheney at allette.com.au Wed Jun 27 02:59:24 2007 From: xcheney at allette.com.au (Xin Chen) Date: Wed, 27 Jun 2007 12:59:24 +1000 Subject: [Fedora-xen] Domain 0 reboot when network flow is heavy Message-ID: <4681D28C.1060600@allette.com.au> Hi All, I am not sure about this, just wondering anyone has the similar situation with me:: I was using scp command on a remote server, copying a 20G file into Domain 0 server. the speed displayed is around 8Mb/s waiting... waiting... at 67%, it stopped, why? because Domain 0 reboot..... I check the log, nothing useful. I guess it is because the network flowing, because the domain 0 has been running for 3 weeks until today I do the copying. I attached some info, please give me some advice, thanks a lot!! xin [root at XenServer xen]# uname -a Linux XenServer 2.6.18-1.2798.fc6xen #1 SMP Mon Oct 16 15:11:19 EDT 2006 i686 i686 i386 GNU/Linux [root at XenServer xen]# xm info host : XenServer release : 2.6.18-1.2798.fc6xen version : #1 SMP Mon Oct 16 15:11:19 EDT 2006 machine : i686 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 4 threads_per_core : 1 cpu_mhz : 1600 hw_caps : bfebfbff:20100000:00000000:00000140:0004e33d:00000000:00000001 total_memory : 4094 free_memory : 0 xen_major : 3 xen_minor : 0 xen_extra : .3-rc3-1.2798.f xen_caps : xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) cc_compile_by : brewbuilder cc_compile_domain : build.redhat.com cc_compile_date : Mon Oct 16 14:34:31 EDT 2006 xend_config_format : 2 /var/log/xend.log [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:149) Waiting for 51712. [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/tap/6/51712/hotplug-status. [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:486) hotplugStatusCallback 1. [2007-06-24 01:08:55 xend 3125] DEBUG (DevController:143) Waiting for devices vt pm. [2007-06-24 01:08:55 xend 3125] INFO (XendDomain:370) Domain stimpy (6) unpaused . *[2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:283) Xend Daemon started -> here is the place reboot.* [2007-06-26 17:18:55 xend 3154] INFO (SrvDaemon:287) Xend changeset: unavailable . [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG (XendDomainInfo:212) XendDo mainInfo.recreate({'paused': 0, 'cpu_time': 29578464995L, 'ssidref': 0, 'handle' : [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'shutdown_reason': 0, 'dying ': 0, 'dom': 0, 'mem_kb': 4012156, 'maxmem_kb': -4, 'max_vcpu_id': 3, 'crashed': 0, 'running': 1, 'shutdown': 0, 'online_vcpus': 4, 'blocked': 0}) [2007-06-26 17:18:55 xend.XendDomainInfo 3154] INFO (XendDomainInfo:224) Recreat ing domain 0, UUID 00000000-0000-0000-0000-000000000000. [2007-06-26 17:18:55 xend.XendDomainInfo 3154] WARNING (XendDomainInfo:246) No v m path in store for existing domain 0 [2007-06-26 17:18:55 xend.XendDomainInfo 3154] DEBUG (XendDomainInfo:715) Storin g VM details: {'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-0000000000 00', 'on_reboot': 'restart', 'on_poweroff': 'destroy', 'name': 'Domain-0', 'xend /restart_count': '0', 'vcpus': '4', 'vcpu_avail': '15', 'memory': '3919', 'on_cr ash': 'restart', 'maxmem': '3919'} [2007-06-26 17:18:56 xend.XendDomainInfo 3154] DEBUG (XendDomainInfo:750) Storin g domain details: {'cpu/1/availability': 'online', 'cpu/3/availability': 'online ', 'name': 'Domain-0', 'console/limit': '1048576', 'cpu/2/availability': 'online ', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availa bility': 'online', 'memory/target': '4013056'} [2007-06-26 17:18:56 xend 3154] DEBUG (XendDomain:153) number of vcpus to use is 0 [2007-06-26 17:18:56 xend 3154] INFO (SrvServer:116) unix path=/var/lib/xend/xen d-socket /var/log/message: Jun 26 17:14:58 XenServer kernel: peth1: received packet with own address as so urce address Jun 26 17:15:57 XenServer last message repeated 2 times Jun 26 17:15:57 XenServer kernel: peth0: received packet with own address as so urce address Jun 26 17:16:01 XenServer kernel: peth1: received packet with own address as so urce address Jun 26 17:17:00 XenServer kernel: peth1: received packet with own address as so urce address *Jun 26 17:18:38 XenServer syslogd 1.4.1: restart. --> here is the place reboot* Jun 26 17:18:38 XenServer kernel: klogd 1.4.1, log source = /proc/kmsg started. Jun 26 17:18:38 XenServer kernel: Linux version 2.6.18-1.2798.fc6xen (brewbuilde r at hs20-bc2-4.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) # 1 SMP Mon Oct 16 15:11:19 EDT 2006 Jun 26 17:18:38 XenServer kernel: BIOS-provided physical RAM map: Jun 26 17:18:38 XenServer kernel: Xen: 0000000000000000 - 00000000f575f000 (usa ble) Jun 26 17:18:38 XenServer kernel: 3199MB HIGHMEM available. Jun 26 17:18:38 XenServer kernel: 727MB LOWMEM available. Jun 26 17:18:38 XenServer kernel: NX (Execute Disable) protection: active Jun 26 17:18:38 XenServer kernel: found SMP MP-table at 000f5f20 Jun 26 17:18:38 XenServer kernel: DMI present. Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enab led) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enab led) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enab led) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enab led) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[ 0x1]) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[ 0x1]) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[ 0x1]) Jun 26 17:18:38 XenServer kernel: ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[ 0x1]) Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x04] address[0xfec00000] gsi _base[0]) Jun 26 17:18:38 XenServer kernel: IOAPIC[0]: apic_id 4, version 32, address 0xfe c00000, GSI 0-23 Jun 26 17:18:38 XenServer kernel: ACPI: IOAPIC (id[0x05] address[0xfec80000] gsi _base[24]) attach the network details of domain 0: [root at XenServer ~]# ifconfig -a eth0 Link encap:Ethernet HWaddr 00:30:48:32:4F:94 inet addr:192.168.200.120 Bcast:192.168.200.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe32:4f94/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2286450 errors:0 dropped:0 overruns:0 frame:0 TX packets:1118771 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3457059468 (3.2 GiB) TX bytes:74013507 (70.5 MiB) eth1 Link encap:Ethernet HWaddr 00:30:48:32:4F:95 inet addr:192.168.200.121 Bcast:192.168.200.255 Mask:255.255.255.0 inet6 addr: fe80::230:48ff:fe32:4f95/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4211 errors:0 dropped:0 overruns:0 frame:0 TX packets:39 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:410017 (400.4 KiB) TX bytes:8485 (8.2 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:14 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1008 (1008.0 b) TX bytes:1008 (1008.0 b) peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:2282062 errors:0 dropped:0 overruns:0 frame:0 TX packets:1116125 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:3458070625 (3.2 GiB) TX bytes:78308773 (74.6 MiB) Base address:0x2000 Memory:d8400000-d8420000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:7627 errors:0 dropped:0 overruns:0 frame:0 TX packets:4103 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:893944 (872.9 KiB) TX bytes:523855 (511.5 KiB) Base address:0x2020 Memory:d8420000-d8440000 sit0 Link encap:IPv6-in-IPv4 NOARP MTU:1480 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth2 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) veth3 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1118785 errors:0 dropped:0 overruns:0 frame:0 TX packets:2286472 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:74014879 (70.5 MiB) TX bytes:3457092776 (3.2 GiB) vif0.1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:39 errors:0 dropped:0 overruns:0 frame:0 TX packets:4211 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8485 (8.2 KiB) TX bytes:410017 (400.4 KiB) vif0.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif0.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:4100 errors:0 dropped:0 overruns:0 frame:0 TX packets:5265 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:440557 (430.2 KiB) TX bytes:652881 (637.5 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:472 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:59881 (58.4 KiB) TX bytes:0 (0.0 b) xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:1348 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:96255 (93.9 KiB) TX bytes:0 (0.0 b) From rjones at redhat.com Wed Jun 27 03:54:05 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 27 Jun 2007 04:54:05 +0100 Subject: [Fedora-xen] Domain 0 reboot when network flow is heavy In-Reply-To: <4681D28C.1060600@allette.com.au> References: <4681D28C.1060600@allette.com.au> Message-ID: <4681DF5D.5050109@redhat.com> Xin Chen wrote: > Hi All, > > I am not sure about this, just wondering anyone has the similar > situation with me:: Is this similar? https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From xcheney at allette.com.au Wed Jun 27 05:23:02 2007 From: xcheney at allette.com.au (Xin Chen) Date: Wed, 27 Jun 2007 15:23:02 +1000 Subject: [Fedora-xen] Domain 0 reboot when network flow is heavy In-Reply-To: <4681DF5D.5050109@redhat.com> References: <4681D28C.1060600@allette.com.au> <4681DF5D.5050109@redhat.com> Message-ID: <4681F436.6010006@allette.com.au> Thanks for quick response, Richard. Yes, it is similar but two differences: 1, instead of cpu lock, my domain 0 simply just reboot itself~~ 2, I can't find any error message in the log, it is like a power off the machine. I thought it might be network I/O, but if using ftp, then there is no errors~, maybe a disk I/O, then I try cp a 10gb file to local drive on domain 0, it works as well. I would try to find usb in bios and turn it off later. Thanks! x Richard W.M. Jones wrote: > Xin Chen wrote: > >> Hi All, >> >> I am not sure about this, just wondering anyone has the similar >> situation with me:: > > > Is this similar? > > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=190636 > > Rich. > From thewird at yahoo.com Wed Jun 27 06:05:07 2007 From: thewird at yahoo.com (thewird) Date: Wed, 27 Jun 2007 02:05:07 -0400 (EDT) Subject: [Fedora-xen] 32bit guests on 64bit FC7 Message-ID: <984252.98190.qm@web88302.mail.re4.yahoo.com> FC7 64bit doesn't work with 32bit guests yet even though it was supposed to. Does anyone know when a yum update will be possible to make it work? I'm currently building a machine with 32GB of ram and need to run 32bit guests. I have about 4-5 weeks before the server needs to go live so will it be updated by then? Thanks. From rjones at redhat.com Wed Jun 27 08:25:20 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 27 Jun 2007 09:25:20 +0100 Subject: [Fedora-xen] Domain 0 reboot when network flow is heavy In-Reply-To: <4681F436.6010006@allette.com.au> References: <4681D28C.1060600@allette.com.au> <4681DF5D.5050109@redhat.com> <4681F436.6010006@allette.com.au> Message-ID: <46821EF0.2030305@redhat.com> Xin Chen wrote: > Thanks for quick response, Richard. > > Yes, it is similar but two differences: > > 1, instead of cpu lock, my domain 0 simply just reboot itself~~ The default configuration of Xen is that it will reboot if it detects that dom0 has crashed. To stop it doing this (so you can see any console messages), add noreboot to the Xen hypervisor command line. ie. in /boot/grub/menu.lst, locate the line which says: kernel /xen.gz-XXX.fc6 and add: kernel /xen.gz-XXX.fc6 noreboot > 2, I can't find any error message in the log, it is like a power off the > machine. > > I thought it might be network I/O, but if using ftp, then there is no > errors~, maybe a disk I/O, then I try cp a 10gb file to local drive on > domain 0, it works as well. From the other reports, it does look like it has something to do with network I/O. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From thewird at yahoo.com Wed Jun 27 09:00:13 2007 From: thewird at yahoo.com (thewird) Date: Wed, 27 Jun 2007 05:00:13 -0400 (EDT) Subject: [Fedora-xen] More then 16GB with FC6 or FC7? Message-ID: <556898.18709.qm@web88307.mail.re4.yahoo.com> Is there any way to make the xen kernel see more then 16GB of ram when its installed on a 32bit OS (either FC6 or FC7)? I tried FC7 64bit since it can see all the ram, however the only 32bit OS I was able to install successfully was windows XP. Every other distro (FC6, FC7, and CentOS 4.5 & 5.0) would freeze up at some point in the installation or bootup section. I have a machine with 28GB of ram and have a month to get it running. Marco Jorge From markryde at gmail.com Wed Jun 27 13:09:32 2007 From: markryde at gmail.com (Mark Ryden) Date: Wed, 27 Jun 2007 16:09:32 +0300 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? In-Reply-To: <46813250.2060306@redhat.com> References: <20070625150044.GB23311@redhat.com> <46813250.2060306@redhat.com> Message-ID: Hello, Thanks; After uninstalling intltool and "yum install intltool" everything went ok on FC6. I have a machine with FC7 on which I tried the same and ./autogen.sh fails, giving the following message (required file `./config.rpath' not found). (see below full log). On this machine I have: gettext-0.16.1-8.fc7 gettext-devel-0.16.1-8.fc7 pygtk2-devel-2.10.4-2.fc7 gtk2-devel-2.10.11-7.fc7 intltool-0.35.5-3.fc7 Does anybody know: what is this "config.rpath" error ? I googled for it but could not find a satisfiable error. I want to add that on the FC6 , a config.rpath file is not generated. Did anybody have success with building on FC7 machines after downloading from repositories ? Here is the full output on the FC7 machine: ./autogen.sh configure.ac:7: required file `./config.rpath' not found configure.ac:2: installing `./missing' configure.ac:2: installing `./install-sh' pixmaps/Makefile.am:3: wildcard $(srcdir: non-POSIX variable name pixmaps/Makefile.am:3: (probably a GNU make extension) src/Makefile.am:15: wildcard $(srcdir: non-POSIX variable name src/Makefile.am:15: (probably a GNU make extension) src/Makefile.am:35: `%'-style pattern rules are a GNU make extension src/Makefile.am:38: `%'-style pattern rules are a GNU make extension src/Makefile.am:41: `%'-style pattern rules are a GNU make extension src/Makefile.am:44: `%'-style pattern rules are a GNU make extension src/Makefile.am:26: variable `schema_SOURCES' is defined but no program or src/Makefile.am:26: library has `schema' as canonic name (possible typo) src/Makefile.am:11: variable `libexec_SOURCES' is defined but no program or src/Makefile.am:11: library has `libexec' as canonic name (possible typo) src/Makefile.am:4: variable `bin_SOURCES' is defined but no program or src/Makefile.am:4: library has `bin' as canonic name (possible typo) src/Makefile.am:18: variable `desktop_SOURCES' is defined but no program or src/Makefile.am:18: library has `desktop' as canonic name (possible typo) src/Makefile.am:8: variable `python_SOURCES' is defined but no program or src/Makefile.am:8: library has `python' as canonic name (possible typo) src/Makefile.am:22: variable `dbus_SOURCES' is defined but no program or src/Makefile.am:22: library has `dbus' as canonic name (possible typo) src/graphWidgets/Makefile.am:5: `:='-style assignments are not portable src/graphWidgets/Makefile.am:5: shell pkg-config --variable=codegendir pygtk-2.0: non-POSIX variable name src/graphWidgets/Makefile.am:5: (probably a GNU make extension) src/graphWidgets/Makefile.am:6: `:='-style assignments are not portable src/graphWidgets/Makefile.am:6: shell pkg-config --variable=defsdir pygtk-2.0: non-POSIX variable name src/graphWidgets/Makefile.am:6: (probably a GNU make extension) src/graphWidgets/Makefile.am: installing `./depcomp' src/virtManager/Makefile.am:3: wildcard $(srcdir: non-POSIX variable name src/virtManager/Makefile.am:3: (probably a GNU make extension) src/virtManager/Makefile.am:7: python_DATA:$(srcdir: non-POSIX variable name src/virtManager/Makefile.am:15: `%'-style pattern rules are a GNU make extension src/vncViewer/Makefile.am:3: wildcard $(srcdir: non-POSIX variable name src/vncViewer/Makefile.am:3: (probably a GNU make extension) Regards, Mark On 6/26/07, Richard W.M. Jones wrote: > Mark Ryden wrote: > > Hello, > > - Thanks all. > > > > - Ok, I ran: "yum install gettext-devel" and installed > > gettext-devel-0.14.6-4.fc6. > > Now: > > running: > > ./autobuild.sh > > gives: > > make: *** No rule to make target `distclean'. > > libtoolize: `config.guess' exists: use `--force' to overwrite > > libtoolize: `config.sub' exists: use `--force' to overwrite > > libtoolize: `ltmain.sh' exists: use `--force' to overwrite > > checking for a BSD-compatible install... /usr/bin/install -c > > checking whether build environment is sane... yes > > checking for gawk... gawk > > checking whether make sets $(MAKE)... yes > > ../configure: line 1977: syntax error near unexpected token `0.35.0,' > > ../configure: line 1977: `IT_PROG_INTLTOOL(0.35.0, no-xml)' > > line 1977 includes : > > where: IT_PROG_INTLTOOL(0.35.0, no-xml) > > > > As I said, I have intltool-0.35.5 on this machine (built and installed > > from source tar file). > > Couple of questions: > > Does your aclocal.m4 file contain a definition of IT_PROG_INTLTOOL? The > definition starts like this: > > dnl IT_PROG_INTLTOOL([MINIMUM-VERSION], [no-xml]) > # serial 35 IT_PROG_INTLTOOL > AC_DEFUN([IT_PROG_INTLTOOL], > [AC_PREREQ([2.50])dnl > etc. > > You mentioned in your first email that you're trying to compile this on > FC6, in which case you should have all these tools available through > yum, ie: yum install intltool > > You shouldn't need to rebuild anything (except the latest virt-manager) > from source ... > > Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 > > From berrange at redhat.com Wed Jun 27 13:35:32 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 27 Jun 2007 14:35:32 +0100 Subject: [Fedora-xen] FC6 xen bugfixes planned? In-Reply-To: <20070626130456.72c98136@zooty> References: <20070626130456.72c98136@zooty> Message-ID: <20070627133532.GB23350@redhat.com> On Tue, Jun 26, 2007 at 01:04:56PM -0400, Tom Horsley wrote: > Just ran into a bug with all the HVMs I have running under > Xen with a 64 bit AMD host (FC6). > > Apparently the int3 debugger trap instruction gets the > wrong PC reported in the VMs, so it is a pain in the > patoot to do debugger development on Xen guests :-). > > (Search google for "hvm int3 amd" and you can find > references to patches that are fairly recent - a lot > more recent than the version of Xen provided with > FC6). > > Any planned bugfixes in the pipe for Xen on FC6, or should > I look at swapping in some completely different host? FC6 is basically going to stay on Xen 3.0.3, because upstream Xen totally fails to provide a stable ABI between the hypervisor & userspace tools so upgrades during course of a Fedora release will be very painful. For an example, consider if for every kernel upgrade you did, you needed to upgrade your glibc, and the new glibc wasn't compatible with your old kernel. Well that's the situation we're in with Xen & it utterly sucks. So FC6 will stay on Xen 3.0.3. If you have HVM issues the best bet is to switch to Fedora 7 whcih is baed on Xen 3.1.0 which has much more advanced HVM support. Regards, 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 -=| From berrange at redhat.com Wed Jun 27 13:43:38 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 27 Jun 2007 14:43:38 +0100 Subject: [Fedora-xen] More then 16GB with FC6 or FC7? In-Reply-To: <556898.18709.qm@web88307.mail.re4.yahoo.com> References: <556898.18709.qm@web88307.mail.re4.yahoo.com> Message-ID: <20070627134338.GD23350@redhat.com> On Wed, Jun 27, 2007 at 05:00:13AM -0400, thewird wrote: > Is there any way to make the xen kernel see more then > 16GB of ram when its installed on a 32bit OS (either > FC6 or FC7)? No it is an architectural limitation of Xen that 32-bit is limited to a maximum of 16 GB, even with PAE. > I tried FC7 64bit since it can see all the ram, > however the only 32bit OS I was able to install > successfully was windows XP. Every other distro (FC6, > FC7, and CentOS 4.5 & 5.0) would freeze up at some > point in the installation or bootup section. > > I have a machine with 28GB of ram and have a month to > get it running. 64-bit is the way to go. Try toggleing the 'acpi' and 'apic' settings for the HVM guests as this often helps with lockups. 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 -=| From rjones at redhat.com Wed Jun 27 13:55:09 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 27 Jun 2007 14:55:09 +0100 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? In-Reply-To: References: <20070625150044.GB23311@redhat.com> <46813250.2060306@redhat.com> Message-ID: <46826C3D.9060508@redhat.com> Mark Ryden wrote: > Hello, > Thanks; > After uninstalling intltool and "yum install intltool" everything went > ok on FC6. > I have a machine with FC7 on which I tried the same and ./autogen.sh fails, > giving the following message (required file `./config.rpath' not found). > (see below full log). > > On this machine I have: > gettext-0.16.1-8.fc7 > gettext-devel-0.16.1-8.fc7 Not sure about this one. On my machine I have config.rpath in the libvirt directory (not in the virt-manager directory however), and I also have: $ rpm -qf /usr/share/gettext/config.rpath gettext-devel-0.14.6-4.fc6 If you have it there, try copying it to the build directory? I have no idea if that will work, but it's worth a try. BTW, Fedora and Debian (rightly IMO) deprecate use of rpaths, see: http://people.debian.org/~che/personal/rpath-considered-harmful and http://fedoraproject.org/wiki/Packaging/Guidelines#head-a1dfb5f46bf4098841e31a75d833e6e1b3e72544 On the other hand, the GNU toolchain seems to prefer to add it to libraries. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From berrange at redhat.com Wed Jun 27 14:11:25 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 27 Jun 2007 15:11:25 +0100 Subject: [Fedora-xen] Tryimg to build virt-manager from mercurial: getting error: possibly undefined macro: AM_GNU_GETTEXT - why ? In-Reply-To: References: <20070625150044.GB23311@redhat.com> <46813250.2060306@redhat.com> Message-ID: <20070627141125.GF23350@redhat.com> On Wed, Jun 27, 2007 at 04:09:32PM +0300, Mark Ryden wrote: > Hello, > Thanks; > After uninstalling intltool and "yum install intltool" everything went > ok on FC6. > I have a machine with FC7 on which I tried the same and ./autogen.sh fails, > giving the following message (required file `./config.rpath' not found). > (see below full log). > > On this machine I have: > gettext-0.16.1-8.fc7 > gettext-devel-0.16.1-8.fc7 > pygtk2-devel-2.10.4-2.fc7 > gtk2-devel-2.10.11-7.fc7 > intltool-0.35.5-3.fc7 > > Does anybody know: what is this "config.rpath" error ? I googled for > it but could not find a satisfiable error. I want to add that > on the FC6 , a config.rpath file is not generated. > Did anybody have success with building on FC7 machines after downloading > from > repositories ? Its a bug in current virt-manager code. The workaround is to simply run 'touch config.rpath' We'll figure out a real fix... 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 -=| From kraxel at redhat.com Wed Jun 27 14:48:22 2007 From: kraxel at redhat.com (Gerd Hoffmann) Date: Wed, 27 Jun 2007 16:48:22 +0200 Subject: [Fedora-xen] More then 16GB with FC6 or FC7? In-Reply-To: <20070627134338.GD23350@redhat.com> References: <556898.18709.qm@web88307.mail.re4.yahoo.com> <20070627134338.GD23350@redhat.com> Message-ID: <468278B6.4060408@redhat.com> Daniel P. Berrange wrote: > On Wed, Jun 27, 2007 at 05:00:13AM -0400, thewird wrote: >> Is there any way to make the xen kernel see more then >> 16GB of ram when its installed on a 32bit OS (either >> FC6 or FC7)? > > No it is an architectural limitation of Xen that 32-bit is limited to > a maximum of 16 GB, even with PAE. Well, there is one from the dirty tricks department: Install 32bit fc7, pull 64bit xen kernel from the 64bit kernel-xen rpm, boot that with the 32bit linux kernel. Mixing 32bit and 64bit guests isn't going to work for the time being (needs a kernel update). But with the 64bit hypervisor underneath the system should be able use all memory, even with 32bit guests only. cheers, Gerd From tom.horsley at att.net Wed Jun 27 21:14:44 2007 From: tom.horsley at att.net (Tom Horsley) Date: Wed, 27 Jun 2007 17:14:44 -0400 Subject: [Fedora-xen] FC6 xen bugfixes planned? In-Reply-To: <20070627133532.GB23350@redhat.com> References: <20070626130456.72c98136@zooty> <20070627133532.GB23350@redhat.com> Message-ID: <20070627171444.5aee5aed@zooty> On Wed, 27 Jun 2007 14:35:32 +0100 "Daniel P. Berrange" wrote: > So FC6 will stay on Xen 3.0.3. If you have HVM issues the best bet > is to switch to Fedora 7 whcih is baed on Xen 3.1.0 which has much more > advanced HVM support. Well, I just tried installing SLES10 sp1 on the host today (xen 3.0.4 and whatever novell patches have been crammed in with it :-), and it seems to have solved my HVM problem, so I guess I'll use if for now. I was astounded when I simply copied the VM config files from the old FC6 partition to the new sles partition and the VMs just booted with no alterations to the configs. That is so contrary to the normal linux experience :-). From rmigh at hotmail.com Thu Jun 28 00:16:13 2007 From: rmigh at hotmail.com (Mig H) Date: Thu, 28 Jun 2007 00:16:13 +0000 Subject: [Fedora-xen] CURSOR STUCK ALONG THE Y Message-ID: I'm currently attempting to running the Fedora 7 XEN kernel on a Dell 390. Specs: Intel Core 2 Duo E6600 2.40GHz/1066MHz/4MB L2/Dual-core/VT. 128MB PCIe x16 nVidia Quadro NVS 285 Graphics 2GB, 667MHz, DDR2 SDRAM Memory 80GB SATA 3.0Gb/s with NCQ and 8MB DataBurst Cache Problem: Whenever launching the virtual machine (virt-manager) the cursor gets stuck on along the Y-axis. I can freely move along the Y-axis but moving along the X-axis is almost impossible. If I slowly move the mouse it sometimes works, but normally I just get frustrated and reboot the box. Is there a configuration issue I've missed or is this a bug? From jeevanullas at gmail.com Thu Jun 28 09:03:26 2007 From: jeevanullas at gmail.com (Deependra Singh Shekhawat) Date: Thu, 28 Jun 2007 14:33:26 +0530 Subject: [Fedora-xen] fedora7 xen questions Message-ID: <1183021406.2975.5.camel@localhost.localdomain> Hi, I am using Fedora7 xen kernel version: kernel-xen-2.6.20-2925.11.fc7 and my xen version is: xen-3.1.0-2.fc7 and I am experiencing two difficulties. First is that my wireless network card is not working (intel 3945 a/b/g). I am using ipw3945 driver. It is loaded as a module when I check via lsmod. But /sbin/ipw3945d says: No Intel Pro/Wireless Device Found. It works perfectly with the non-xen kernel that is: 2.6.21-1.3228.fc7 The next thing that annoys me is that when I shut down the machine with the xen kernel it does stops all the process and at last shows my "System Halted" and it stays right there. Doesn't really shut it down. With the non-xen kernel I don't have any such problem. So are these problems are a unknown bugs ? And what steps do I need to take to eradicate these problems. Thanks Deependra Singh Shekhawat -- http://freeshells.ch/~source/ From rjones at redhat.com Thu Jun 28 12:41:45 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 28 Jun 2007 13:41:45 +0100 Subject: [Fedora-xen] fedora7 xen questions In-Reply-To: <1183021406.2975.5.camel@localhost.localdomain> References: <1183021406.2975.5.camel@localhost.localdomain> Message-ID: <4683AC89.8060807@redhat.com> Deependra Singh Shekhawat wrote: > The next thing that annoys me is that when I shut down the machine with > the xen kernel it does stops all the process and at last shows my > "System Halted" > > and it stays right there. Doesn't really shut it down. With the non-xen > kernel I don't have any such problem. This sounds a lot like: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241381 If this is the case, can you add a report to that bugzilla please. It would be useful to know some details of your machine since this doesn't seem to happen to everyone, and it also doesn't happen on RHEL 5 either. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rmigh at hotmail.com Thu Jun 28 17:34:55 2007 From: rmigh at hotmail.com (Mig H) Date: Thu, 28 Jun 2007 17:34:55 +0000 Subject: [Fedora-xen] RE: FC7 SYSTEM SHUTDOWN PROBLEMS In-Reply-To: <20070628160011.D519C73A29@hormel.redhat.com> Message-ID: I experienced the same problem on a Dell Latitude D620, a Dell Inspiron 8500, and 4 Dell 390s. I resolved my issues by updating by bios with the latest from dell and reloading the OS. I found and resolved this issue this way with Fedora 7 and Red Hat Enterprise Edition 5. I believe the BIOS is V 2.3.0.. Hope this helps. Good Day Mig H >From: fedora-xen-request at redhat.com >Reply-To: fedora-xen at redhat.com >To: fedora-xen at redhat.com >Subject: Fedora-xen Digest, Vol 19, Issue 34 >Date: Thu, 28 Jun 2007 12:00:11 -0400 (EDT) > >Send Fedora-xen mailing list submissions to > fedora-xen at redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-xen >or, via email, send a message with subject or body 'help' to > fedora-xen-request at redhat.com > >You can reach the person managing the list at > fedora-xen-owner at redhat.com > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Fedora-xen digest..." > > >Today's Topics: > > 1. Re: FC6 xen bugfixes planned? (Tom Horsley) > 2. CURSOR STUCK ALONG THE Y (Mig H) > 3. fedora7 xen questions (Deependra Singh Shekhawat) > 4. Re: fedora7 xen questions (Richard W.M. Jones) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Wed, 27 Jun 2007 17:14:44 -0400 >From: Tom Horsley >Subject: Re: [Fedora-xen] FC6 xen bugfixes planned? >To: Fedora Xen >Message-ID: <20070627171444.5aee5aed at zooty> >Content-Type: text/plain; charset=US-ASCII > >On Wed, 27 Jun 2007 14:35:32 +0100 >"Daniel P. Berrange" wrote: > > > So FC6 will stay on Xen 3.0.3. If you have HVM issues the best bet > > is to switch to Fedora 7 whcih is baed on Xen 3.1.0 which has much more > > advanced HVM support. > >Well, I just tried installing SLES10 sp1 on the host today (xen 3.0.4 >and whatever novell patches have been crammed in with it :-), and it >seems to have solved my HVM problem, so I guess I'll use if for now. > >I was astounded when I simply copied the VM config files from the >old FC6 partition to the new sles partition and the VMs just booted >with no alterations to the configs. That is so contrary to the >normal linux experience :-). > > > >------------------------------ > >Message: 2 >Date: Thu, 28 Jun 2007 00:16:13 +0000 >From: "Mig H" >Subject: [Fedora-xen] CURSOR STUCK ALONG THE Y >To: fedora-xen at redhat.com >Message-ID: >Content-Type: text/plain; format=flowed > >I'm currently attempting to running the Fedora 7 XEN kernel on a Dell 390. >Specs: Intel Core 2 Duo E6600 2.40GHz/1066MHz/4MB L2/Dual-core/VT. > 128MB PCIe x16 nVidia Quadro NVS 285 Graphics > 2GB, 667MHz, DDR2 SDRAM Memory > 80GB SATA 3.0Gb/s with NCQ and 8MB DataBurst Cache > >Problem: Whenever launching the virtual machine (virt-manager) the cursor >gets stuck on along the Y-axis. I can freely move along the Y-axis but >moving along the X-axis is almost impossible. If I slowly move the mouse it >sometimes works, but normally I just get frustrated and reboot the box. Is >there a configuration issue I've missed or is this a bug? > > > > >------------------------------ > >Message: 3 >Date: Thu, 28 Jun 2007 14:33:26 +0530 >From: Deependra Singh Shekhawat >Subject: [Fedora-xen] fedora7 xen questions >To: fedora-xen at redhat.com >Message-ID: <1183021406.2975.5.camel at localhost.localdomain> >Content-Type: text/plain > >Hi, > >I am using Fedora7 xen kernel version: >kernel-xen-2.6.20-2925.11.fc7 > >and my xen version is: >xen-3.1.0-2.fc7 > >and I am experiencing two difficulties. First is that my wireless >network card is not working (intel 3945 a/b/g). I am using ipw3945 >driver. It is loaded as a module when I check via lsmod. >But /sbin/ipw3945d says: > >No Intel Pro/Wireless Device Found. > >It works perfectly with the non-xen kernel that is: >2.6.21-1.3228.fc7 > >The next thing that annoys me is that when I shut down the machine with >the xen kernel it does stops all the process and at last shows my >"System Halted" > >and it stays right there. Doesn't really shut it down. With the non-xen >kernel I don't have any such problem. > >So are these problems are a unknown bugs ? And what steps do I need to >take to eradicate these problems. > >Thanks >Deependra Singh Shekhawat >-- >http://freeshells.ch/~source/ > > > >------------------------------ > >Message: 4 >Date: Thu, 28 Jun 2007 13:41:45 +0100 >From: "Richard W.M. Jones" >Subject: Re: [Fedora-xen] fedora7 xen questions >To: Deependra Singh Shekhawat >Cc: fedora-xen at redhat.com >Message-ID: <4683AC89.8060807 at redhat.com> >Content-Type: text/plain; charset="utf-8" > >Deependra Singh Shekhawat wrote: > > The next thing that annoys me is that when I shut down the machine with > > the xen kernel it does stops all the process and at last shows my > > "System Halted" > > > > and it stays right there. Doesn't really shut it down. With the non-xen > > kernel I don't have any such problem. > >This sounds a lot like: > >http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241381 > >If this is the case, can you add a report to that bugzilla please. It >would be useful to know some details of your machine since this doesn't >seem to happen to everyone, and it also doesn't happen on RHEL 5 either. > >Rich. > >-- >Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ >Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod >Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in >England and Wales under Company Registration No. 03798903 >-------------- next part -------------- >A non-text attachment was scrubbed... >Name: smime.p7s >Type: application/x-pkcs7-signature >Size: 3237 bytes >Desc: S/MIME Cryptographic Signature >Url : >https://www.redhat.com/archives/fedora-xen/attachments/20070628/12031307/smime.bin > >------------------------------ > >-- >Fedora-xen mailing list >Fedora-xen at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-xen > > >End of Fedora-xen Digest, Vol 19, Issue 34 >****************************************** From jeevanullas at gmail.com Fri Jun 29 01:20:17 2007 From: jeevanullas at gmail.com (Deependra Singh Shekhawat) Date: Fri, 29 Jun 2007 06:50:17 +0530 Subject: [Fedora-xen] fedora7 xen questions In-Reply-To: <4683AC89.8060807@redhat.com> References: <1183021406.2975.5.camel@localhost.localdomain> <4683AC89.8060807@redhat.com> Message-ID: <1183080017.614.2.camel@localhost.localdomain> Thanks. I have added my cpu configuration and hardware details into that bug (241381). Hope it helps. As pointed by someone in this list updating the BIOS solved the problem. Well I am using Lenovo and I have the latest BIOS update. Maybe it's related to the BIOS but at the moment I don't have a update option available. Maybe when a update comes up I get the issue resolved. Once again Thanks. Deependra Singh Shekhawat On Thu, 2007-06-28 at 13:41 +0100, Richard W.M. Jones wrote: > Deependra Singh Shekhawat wrote: > > The next thing that annoys me is that when I shut down the machine with > > the xen kernel it does stops all the process and at last shows my > > "System Halted" > > > > and it stays right there. Doesn't really shut it down. With the non-xen > > kernel I don't have any such problem. > > This sounds a lot like: > > http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=241381 > > If this is the case, can you add a report to that bugzilla please. It > would be useful to know some details of your machine since this doesn't > seem to happen to everyone, and it also doesn't happen on RHEL 5 either. > > Rich. > -- http://freeshells.ch/~source/ From info at vsic.net Fri Jun 29 18:24:12 2007 From: info at vsic.net (Frank Morane) Date: Fri, 29 Jun 2007 12:24:12 -0600 Subject: [Fedora-xen] Xen status for FC7 Message-ID: <46854E4C.8030107@vsic.net> Hi all, I just did a fresh install of FC7 to see if xen would work out of the box. Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU boots but are unseable (after recompiling the initrd image with the xen driver preloaded) up to the famous long lasting error message "4gb seg fixup". At that point it is dead My question: what id the status of Xen for Fc7? Will it ever fly? Is there a Linux distro that works out of the box ? The last usable version I saw was for FC5 as of May 2006, after that all version were badly broken and never fixed, I tested ALL of them for fc5/fc6 and not a single one worked as published. Only home brewed compiled version would work after weeks of trial and error. Here what the log says from my out of the box install: [root at paine xen]# cat xend.log [2007-06-29 08:08:34 2567] INFO (SrvDaemon:331) Xend Daemon started [2007-06-29 08:08:34 2567] INFO (SrvDaemon:335) Xend changeset: unavailable. [2007-06-29 08:08:34 2567] INFO (SrvDaemon:342) Xend version: Unknown. [2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:126) XendDomainInfo.recreate({'max_vcpu_id': 0, 'cpu_time': 35199342574L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 1, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 4294967292L, 'shutdown': 0, 'mem_kb': 962164L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) [2007-06-29 08:08:35 2567] INFO (XendDomainInfo:143) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 [2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:2022) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'name': 'Domain-0'} [2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:873) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'memory/target': '962164', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-06-29 08:08:35 2567] DEBUG (XendDomain:443) Adding Domain: 0 [2007-06-29 08:08:35 2567] DEBUG (XendDomain:379) number of vcpus to use is 0 [2007-06-29 08:08:35 2567] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket [2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:873) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'memory/target': '962164', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-06-29 08:08:35 2567] DEBUG (XendDomainInfo:957) XendDomainInfo.handleShutdownWatch [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VBD.set_device not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VBD.set_mode not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VBD.set_type not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VM.set_VCPUs_max not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VM.set_VCPUs_at_startup not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: debug.get_all not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: console.get_other_config not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: console.set_other_config not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VIF.get_network not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VIF.set_device not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VIF.set_MAC not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: VIF.set_MTU not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: session.get_all_records not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: event.get_record not found [2007-06-29 08:08:35 2567] WARNING (XendAPI:672) API call: event.get_all not found [2007-06-29 08:08:46 2567] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. [2007-06-29 08:08:46 2567] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. Regards, -- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org From rjones at redhat.com Fri Jun 29 19:32:28 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 29 Jun 2007 20:32:28 +0100 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <46854E4C.8030107@vsic.net> References: <46854E4C.8030107@vsic.net> Message-ID: <46855E4C.5010905@redhat.com> Frank Morane wrote: > Hi all, > > I just did a fresh install of FC7 to see if xen would work out of the box. > Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU > boots but are unseable (after recompiling the initrd image with the xen > driver preloaded) up to the famous long lasting error message "4gb seg > fixup". At that point it is dead I don't understand what you mean by "dead". Does the dom0 hang? > My question: what id the status of Xen for Fc7? Will it ever fly? > Is there a Linux distro that works out of the box ? I've been running FC7's Xen here quite well with a Centos 5 guest (amongst others). I haven't tried RHEL4 or Centos 4 as a guest though. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From mc-al34luc at sbcglobal.net Fri Jun 29 21:36:12 2007 From: mc-al34luc at sbcglobal.net (Mike) Date: Fri, 29 Jun 2007 14:36:12 -0700 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <46854E4C.8030107@vsic.net> References: <46854E4C.8030107@vsic.net> Message-ID: <46857B4C.5010102@sbcglobal.net> Frank Morane wrote: > Hi all, > > I just did a fresh install of FC7 to see if xen would work out of the box. > Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU > boots but are unseable (after recompiling the initrd image with the xen > driver preloaded) up to the famous long lasting error message "4gb seg > fixup". At that point it is dead > > My question: what id the status of Xen for Fc7? Will it ever fly? > Is there a Linux distro that works out of the box ? Hmm. I'm running a F7 dom0 with the following domUs: NetBSD 3.1, FC6, F7, and a very shaky Solaris 10 b44. Xen 3.1 + F7 seems rock solid. > > The last usable version I saw was for FC5 as of May 2006, after that all > version were badly broken and never fixed, I tested ALL of them for > fc5/fc6 and not a single one worked as published. Only home brewed > compiled version would work after weeks of trial and error. > > Here what the log says from my out of the box install: > > Are you sure you're not missing the domU's console? I noticed that with at least the FC6 and F7 domUs, the boot output starts on the serial console, then transfers to the graphical console. I'm not familiar with the Centos domU's behavior, but it might be something to check. From fcxen at itsbeen.sent.com Sat Jun 30 02:17:54 2007 From: fcxen at itsbeen.sent.com (FCXen) Date: Fri, 29 Jun 2007 19:17:54 -0700 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <46857B4C.5010102@sbcglobal.net> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> Message-ID: <4685BD52.2030601@itsbeen.sent.com> Mike wrote: > Frank Morane wrote: >> Hi all, >> >> I just did a fresh install of FC7 to see if xen would work out of the box. >> Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU >> boots but are unseable (after recompiling the initrd image with the xen >> driver preloaded) up to the famous long lasting error message "4gb seg >> fixup". At that point it is dead >> >> My question: what id the status of Xen for Fc7? Will it ever fly? >> Is there a Linux distro that works out of the box ? > > Hmm. I'm running a F7 dom0 with the following domUs: NetBSD 3.1, FC6, > F7, and a very shaky Solaris 10 b44. > > Xen 3.1 + F7 seems rock solid. > >> The last usable version I saw was for FC5 as of May 2006, after that all >> version were badly broken and never fixed, I tested ALL of them for >> fc5/fc6 and not a single one worked as published. Only home brewed >> compiled version would work after weeks of trial and error. >> >> Here what the log says from my out of the box install: >> >> > > Are you sure you're not missing the domU's console? I noticed that with > at least the FC6 and F7 domUs, the boot output starts on the serial > console, then transfers to the graphical console. I'm not familiar with > the Centos domU's behavior, but it might be something to check. > I think this is a big problem, it happened to me.* Unfortunately, I was trying on FC6 Test 2/3 so I was told to get the F7 release version and try that. There is no clear step by step how to on how to build GUI-less domUs for FC6 or F7 (or more frustratingly, no notices that it is not possible), so many people seem to be trying it and asking variations of the same question here, the IRC channels for Fedora and Xen, the libvir mailing list, the Xen mailing list, etc. Can someone with the access rights put a clear unequivocal checklists or statements on the libvir site and the F7 site with the steps that work and/or don't work for creating domUs for normal people? Lots of people are in GUI-less situations and trying F7/Xen and failing unnecessarily, its bad PR for Xen and F7. And kudos to those running everything under the sun on an F7 dom0, but can someone give those of us who aren't in the secret club a break and publish a full step-by-step of how you did it and some config files/settings. Did you use a copy of the DVD** exactly as it was or change some magical files after copying to disk? Has GUI-less domU installs or installs using a manually assigned IPv4 address ever worked for anyone using an F7 dom0, if so how? * [Along with the problem that the installer was crashing when manually configuring an IPv4 address for an interface.] The released one still seems to want the subnet mask in 32s rather than 255s. ** I also didn't know that a remote repo would fail during domU installs until someone mentioned it among some other attempts at troubleshooting my install failures. Thanks to anyone who can help with this. From thewird at yahoo.com Sat Jun 30 05:05:48 2007 From: thewird at yahoo.com (thewird) Date: Sat, 30 Jun 2007 01:05:48 -0400 (EDT) Subject: [Fedora-xen] 64bit Hypervisor on 32bit OS Message-ID: <262023.82747.qm@web88304.mail.re4.yahoo.com> I've been reading about how to make Xen show more then 16GB of ram and still support 32bit but so far all my attempts have not worked. FC7 was supposed to be able to run 32bit guests on its 64bit OS but because of a feature freeze, this was not possible even though it still says you can do it in the release notes which I find ridiculous. Anyway, someone told me if I replace the hypervisor with the 64bit counterpart, then I should be able to see more the 16GB of memory and be able to run 32bit guests. I did this by extracting the files from the 64bit RPM and replaced the xen.gz-2.6.20-2925.11.fc7 file with the one from the 64bit RPM and rebooted. The OS booted fine, however, when I tried running/installing a 32bit domU the console would not load or would lock up almost immediately. I can't think of anything else to try and any help would be greatly appreciated. thewird From info at vsic.net Sat Jun 30 15:05:35 2007 From: info at vsic.net (Frank Morane) Date: Sat, 30 Jun 2007 09:05:35 -0600 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <46855E4C.5010905@redhat.com> References: <46854E4C.8030107@vsic.net> <46855E4C.5010905@redhat.com> Message-ID: <4686713F.2050303@vsic.net> Richard W.M. Jones wrote: > Frank Morane wrote: >> Hi all, >> >> I just did a fresh install of FC7 to see if xen would work out of the >> box. >> Dom0 boots (with errors in the log - see below) and some Centos 4.4 >> domU boots but are unseable (after recompiling the initrd image with >> the xen driver preloaded) up to the famous long lasting error message >> "4gb seg fixup". At that point it is dead > > I don't understand what you mean by "dead". Does the dom0 hang? No, just the domU. It does nothing more once the "4gb seg fixup" start spiting. > >> My question: what id the status of Xen for Fc7? Will it ever fly? >> Is there a Linux distro that works out of the box ? > > I've been running FC7's Xen here quite well with a Centos 5 guest > (amongst others). I haven't tried RHEL4 or Centos 4 as a guest though. That is my next step to test BUT I have a bunch of older Centos to migrate so I would like to see them work on newer Xen version. Thanks. > > Rich. > -- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org From info at vsic.net Sat Jun 30 15:12:12 2007 From: info at vsic.net (Frank Morane) Date: Sat, 30 Jun 2007 09:12:12 -0600 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <46857B4C.5010102@sbcglobal.net> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> Message-ID: <468672CC.50601@vsic.net> Mike wrote: > Frank Morane wrote: > >> Hi all, >> >> I just did a fresh install of FC7 to see if xen would work out of the box. >> Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU >> boots but are unseable (after recompiling the initrd image with the xen >> driver preloaded) up to the famous long lasting error message "4gb seg >> fixup". At that point it is dead >> >> My question: what id the status of Xen for Fc7? Will it ever fly? >> Is there a Linux distro that works out of the box ? >> > > Hmm. I'm running a F7 dom0 with the following domUs: NetBSD 3.1, FC6, > F7, and a very shaky Solaris 10 b44. > > Xen 3.1 + F7 seems rock solid. > > >> The last usable version I saw was for FC5 as of May 2006, after that all >> version were badly broken and never fixed, I tested ALL of them for >> fc5/fc6 and not a single one worked as published. Only home brewed >> compiled version would work after weeks of trial and error. >> >> Here what the log says from my out of the box install: >> >> >> > > Are you sure you're not missing the domU's console? I noticed that with > at least the FC6 and F7 domUs, the boot output starts on the serial > console, then transfers to the graphical console. I'm not familiar with > the Centos domU's behavior, but it might be something to check. > Ah!? This could be it, I will dig to unearth this topic as if what you say is right, this could be it. Thanks > > > -- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org From berrange at redhat.com Sat Jun 30 14:56:20 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 30 Jun 2007 15:56:20 +0100 Subject: [Fedora-xen] More then 16GB with FC6 or FC7? In-Reply-To: <952807.37207.qm@web88311.mail.re4.yahoo.com> References: <20070627134338.GD23350@redhat.com> <952807.37207.qm@web88311.mail.re4.yahoo.com> Message-ID: <20070630145620.GA17731@redhat.com> On Sat, Jun 30, 2007 at 01:59:34AM -0400, thewird wrote: > How do I do that with the new xml configuration files > for xen in Fedora 7? I tried 0 but when I > define it back into the database, it gets rid of my > change. I suspect I'm using the wrong syntax but > theres no documentation at all on the new xml format. Check out this http://libvirt.org/format.html In the section 'Fuly virtualized guests'. To turn it on try: Or to turn it off, just leave out the tag Regards, 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 -=|