From slbubba at charter.net Fri Oct 5 15:17:25 2007 From: slbubba at charter.net (Warren Sypteras) Date: Fri, 05 Oct 2007 11:17:25 -0400 Subject: [Fedora-xen] Xen Virt-Manager odd reaction Message-ID: <47065585.1000606@charter.net> Folks; I have a small problem here that perhaps someone knows the answer to. I'm running the following: kernel xen 2.6.18-8.1.14.el5 xen 3.0.3-25.0.4.el5 virt-manager-0.2.6-7.0.2.el5 When using virt-manager to add a new VM (in this case Fedora core 6) the installation moves along smoothly and the VM is displayed in the main virt-manager window under dom-0. At the end of the VM installation the screen to remove all disks and click the reboot button appears. Clicking on "reboot" in the VM window starts the reboot process. However, the VM entry in the virt-manager window disappears, the VM console disappears, and the VM never comes back. The VM flat file is there (in my case it's /opt/vm01a) and the correct size but virt-manager does not see the VM, only dom-0. I've gone through this multiple times and now have 3 VM's but no way to access them. Where is the data for the VM kept that virt-manager uses? Why is virt-manager acting this way? Any patches, fixes, different revs? Thanks Warren From mnielsen at redhat.com Fri Oct 5 15:49:57 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Fri, 05 Oct 2007 11:49:57 -0400 Subject: [Fedora-xen] Xen Virt-Manager odd reaction In-Reply-To: <47065585.1000606@charter.net> References: <47065585.1000606@charter.net> Message-ID: <47065D25.3000609@redhat.com> xm create /etc/xen/ /etc/xen/ is where your configuration files for your VM are stored. One would think that after an install the Xen dom-U would actually "reboot" when you say "reboot" after install, but they just shut down. xm create will start them back up. Mark Warren Sypteras wrote: > Folks; > > I have a small problem here that perhaps someone knows the answer to. > I'm running the following: > kernel xen 2.6.18-8.1.14.el5 > xen 3.0.3-25.0.4.el5 > virt-manager-0.2.6-7.0.2.el5 > > When using virt-manager to add a new VM (in this case Fedora core 6) > the installation moves along smoothly and the VM is displayed in the > main virt-manager window under dom-0. > > At the end of the VM installation the screen to remove all disks and > click the reboot button appears. > > Clicking on "reboot" in the VM window starts the reboot process. > However, the VM entry in the virt-manager window disappears, the VM > console disappears, and the VM never comes back. > > The VM flat file is there (in my case it's /opt/vm01a) and the > correct size but virt-manager does not see the VM, only dom-0. > > I've gone through this multiple times and now have 3 VM's but no way > to access them. > > Where is the data for the VM kept that virt-manager uses? Why is > virt-manager acting this way? Any patches, fixes, different revs? > Thanks > > Warren > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- A non-text attachment was scrubbed... Name: mnielsen.vcf Type: text/x-vcard Size: 231 bytes Desc: not available URL: From slbubba at charter.net Fri Oct 5 15:56:40 2007 From: slbubba at charter.net (Warren Sypteras) Date: Fri, 05 Oct 2007 11:56:40 -0400 Subject: [Fedora-xen] Xen Virt-Manager odd reaction In-Reply-To: <47065D25.3000609@redhat.com> References: <47065585.1000606@charter.net> <47065D25.3000609@redhat.com> Message-ID: <47065EB8.7040409@charter.net> BINGO! thanks Warren Mark Nielsen wrote: > xm create /etc/xen/ > > /etc/xen/ is where your configuration files for your VM are stored. > One would think that after an install the Xen dom-U would actually > "reboot" when you say "reboot" after install, but they just shut down. > xm create will start them back up. > > Mark > > > > Warren Sypteras wrote: > >> Folks; >> >> I have a small problem here that perhaps someone knows the answer to. >> I'm running the following: >> kernel xen 2.6.18-8.1.14.el5 >> xen 3.0.3-25.0.4.el5 >> virt-manager-0.2.6-7.0.2.el5 >> >> When using virt-manager to add a new VM (in this case Fedora core 6) >> the installation moves along smoothly and the VM is displayed in the >> main virt-manager window under dom-0. >> >> At the end of the VM installation the screen to remove all disks and >> click the reboot button appears. >> >> Clicking on "reboot" in the VM window starts the reboot process. >> However, the VM entry in the virt-manager window disappears, the VM >> console disappears, and the VM never comes back. >> >> The VM flat file is there (in my case it's /opt/vm01a) and the >> correct size but virt-manager does not see the VM, only dom-0. >> >> I've gone through this multiple times and now have 3 VM's but no way >> to access them. >> >> Where is the data for the VM kept that virt-manager uses? Why is >> virt-manager acting this way? Any patches, fixes, different revs? >> Thanks >> >> Warren >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen > From fedora.lists at burns.me.uk Fri Oct 5 19:00:22 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Fri, 5 Oct 2007 20:00:22 +0100 Subject: [Fedora-xen] virt-manager "Cannot allocate memory" creating Win2K3 HVM Message-ID: Configuration of dom0 is as follows 8GB memory 2 x dual core Xeon kernel-xen.x86_64 2.6.20-2931.fc7 xen.x86_64 3.1.0-2.fc7 xen-libs.x86_64 3.1.0-2.fc7 libvirt.x86_64 0.3.2-1.fc7 virt-manager-0.4.0-2.fc7 I'm trying to install a win2K3 32bit HVM domU using /cd.iso file local to dom0 LVM partition /dev/vgmirror/win2k3 as domU disk bridged eth0 network 1024MB memory for domU (have tried with lower memory) Fails with POST operation failed: (xend.err "Error creating domain: (12, 'Cannot allocate memory')") Rebooting the dom0 is to be avoided if possible due to other paravirt domU guests running, any suggestions or extra info that might help? I have managed to successfully create a win2K3 64bit HVM domU on an identical dom0 server. From fedora.lists at burns.me.uk Fri Oct 5 20:16:03 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Fri, 5 Oct 2007 21:16:03 +0100 Subject: [Fedora-xen] Re: virt-manager "Cannot allocate memory" creating Win2K3 HVM In-Reply-To: References: Message-ID: On 05/10/2007, Andy Burns wrote: > Rebooting the dom0 is to be avoided if possible Couldn't think of anything else, so I did have to reboot, started a couple of important domU guests and then installed the Win2K3 ok. One question about windows HVM installation, given that virt-manager has the hint that windows is the os being installed, why does the installer delete the CD-DROM driver after the text part of install? this guarantees that the GUI part will fail due to being unable to copy remaining files from CD, the error message windows gives is none to helpful either (can't blame xen/virt-manager for that I guess) My way around this problem is to virsh dumpxml the domU to a file while the text part of install is on-going, then when it reboots I virsh undefine it and virsh define it back from the file again. Is there any prospect of this being handled in a more user-friendly way with FC8? From arnokarner at yahoo.com Mon Oct 8 03:46:15 2007 From: arnokarner at yahoo.com (Arno Karner) Date: Sun, 7 Oct 2007 20:46:15 -0700 (PDT) Subject: [Fedora-xen] xen, revisor Message-ID: <960713.72261.qm@web57111.mail.re3.yahoo.com> ok I make a new dvd iso image with revisor, modify the isolinux.cfg so it boots, and installs with my kickstart file. I look at the anaconda.ks.cfg and none of my rpm packaes, which were installed show up. Now I'm trying to trouble shoot the post install section of a few of my packages, which didn't seem to be executed, so is there some where to look. install log didn't show anything useful. How do I get my rpm-keys installed, doing it from an rpm is not possible because rpm does not support nested transactions, any Ideas here welcome also. the key files are in the root directory od the install image, but that is not good enough. I looked at the spec file of the package in question and it had a Requires: but the packages were not installed, or complained about. Hence other packages that were installed gave warning messages about user xxx, group yyyy not defined using root:root not what I wanted........ I'm reducing the install ks.cfg file, to make trouble shooting this in xen faster, and including a second menu option for a full install of what I want. Sorry for the cross post but this issue deals with revisor, xen, anaconda. I'll be looking into the anaconda emailing list next. I am using bleeding edge rpms, git fc7.testing revisor:git pull, and I should expect this. So I thought I'd ask while I try and reduce my loop time from 4+ hours build iso image, xen.new virt machine + play free civ, update scripts and ks.list(s)....repeat Ideas, flames, constructive criticizing welcome. Arno ____________________________________________________________________________________ Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's updated for today's economy) at Yahoo! Games. http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanarip at kanarip.com Mon Oct 8 08:44:45 2007 From: kanarip at kanarip.com (Jeroen van Meeuwen) Date: Mon, 08 Oct 2007 10:44:45 +0200 Subject: [Fedora-xen] Re: [Revisor-devel] xen, revisor In-Reply-To: <960713.72261.qm@web57111.mail.re3.yahoo.com> References: <960713.72261.qm@web57111.mail.re3.yahoo.com> Message-ID: <4709EDFD.40004@kanarip.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Arno, May we know what version of Fedora you are using, and what version/distribution it is you're trying to create? Arno Karner wrote: > ok I make a new dvd iso image with revisor, modify the isolinux.cfg so > it boots, and installs with my kickstart file. Revisor does that already, so what is it you edit? Further on in the message I see you add another option but also you want to troubleshoot really fast. Manually adding in an option doesn't seem like the most efficient thing to do. > I look at the anaconda.ks.cfg and none of my rpm packages, which were > installed show up. > Depending on what is in your original kickstart I'm sure the sample kickstart anaconda writes out after install is much different. In particular when any of the packages fail to install. > Now I'm trying to trouble shoot the post install section of a few of my > packages, which didn't seem to be executed, > so is there some where to look. install log didn't show anything useful. > I think the %post scripts of your packages is an OK point to start troubleshooting. > How do I get my rpm-keys installed, doing it from an rpm is not possible > because rpm does not support nested transactions, > any Ideas here welcome also. the key files are in the root directory od > the install image, but that is not good enough. > > I looked at the spec file of the package in question and it had a > Requires: but the packages were not installed, > or complained about. Hence other packages that were installed gave > warning messages about user xxx, group yyyy not defined using root:root > not what I wanted........ > Are you saying yum and anaconda are having difficulties eating your packages, or any package? I remember something called PreRequires to indicate the package being required should be actually installed before the package requiring is installed. Did you check any Provides: user(foo), group(bar), against any Requires: user(foo), group(bar)? Are these your very own packages? Have you tested excluding your own packages see how that goes? > I'm reducing the install ks.cfg file, to make trouble shooting this in > xen faster, and including a second menu option for a full install of > what I want. > > Sorry for the cross post but this issue deals with revisor, xen, > anaconda. I'll be looking into the anaconda emailing list next. > I really don't think this has anything to do with xen. > I am using bleeding edge rpms, git fc7.testing revisor:git pull, and I > should expect this. So I thought I'd ask while I try and reduce my loop > time from 4+ hours > build iso image, xen.new virt machine + play free civ, update scripts > and ks.list(s)....repeat > > Ideas, flames, constructive criticizing welcome. Here's an idea. The average desktop floating around any company will beat you to the 4+ hours of composing time (~30 minutes) and another will brighten your day doing installs in 15 minutes or less. Kind regards, Jeroen van Meeuwen - -kanarip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHCe39KN6f2pNCvwgRAkkDAJ42TGT1FVUZP4LNkmXFMv2Gpbap5wCgkCj9 g3SfZdWP+TD5EOnvu2T+DgU= =j7R8 -----END PGP SIGNATURE----- From arnokarner at yahoo.com Tue Oct 9 07:41:27 2007 From: arnokarner at yahoo.com (Arno Karner) Date: Tue, 9 Oct 2007 00:41:27 -0700 (PDT) Subject: [Fedora-xen] Re: xen, revisor Message-ID: <36226.14638.qm@web57107.mail.re3.yahoo.com> Arno, May we know what version of Fedora you are using, and what version/distribution it is you're trying to create? * fc7 with test repos + my repos Arno Karner wrote: > ok I make a new dvd iso image with revisor, modify the isolinux.cfg so > it boots, and installs with my kickstart file. Revisor does that already, so what is it you edit? Further on in the message I see you add another option but also you want to troubleshoot really fast. Manually adding in an option doesn't seem like the most efficient thing to do. * revisor doesn't do the default kickstart file right, corectectly at the moment, and * certainly doesn't do multiple kickstart files boot menu options yet * so i deconstuct the image, copy my kick start files to the iso image * copy my isolinux.cfg menu, reconstruct the image > I look at the anaconda.ks.cfg and none of my rpm packages, which were > installed show up. > Depending on what is in your original kickstart I'm sure the sample kickstart anaconda writes out after install is much different. In particular when any of the packages fail to install. * my kickstart ran too comletion, but none of my packages which were * installed showed up in the anaconda.ks.cfg, I'd really like to * get some kind of feed back loop working so dep packages show up > Now I'm trying to trouble shoot the post install section of a few of my > packages, which didn't seem to be executed, > so is there some where to look. install log didn't show anything useful. > I think the %post scripts of your packages is an OK point to start troubleshooting. * well the first package I'm trouble shooting is not a simple one * its a multiple package spec file unfortanlly Requires: is not a * %command format command > How do I get my rpm-keys installed, doing it from an rpm is not possible > because rpm does not support nested transactions, > any Ideas here welcome also. the key files are in the root directory od > the install image, but that is not good enough. > > I looked at the spec file of the package in question and it had a > Requires: but the packages were not installed, > or complained about. Hence other packages that were installed gave > warning messages about user xxx, group yyyy not defined using root:root > not what I wanted........ > Are you saying yum and anaconda are having difficulties eating your packages, or any package? I remember something called PreRequires to indicate the package being required should be actually installed before the package requiring is installed. Did you check any Provides: user(foo), group(bar), against any Requires: user(foo), group(bar)? Are these your very own packages? Have you tested excluding your own packages see how that goes? * PreRequires theres something worth looking into, because * yes I want certain of my packages to be installed before others > I'm reducing the install ks.cfg file, to make trouble shooting this in > xen faster, and including a second menu option for a full install of > what I want. > > Sorry for the cross post but this issue deals with revisor, xen, > anaconda. I'll be looking into the anaconda emailing list next. > I really don't think this has anything to do with xen. * your right I apologize, I left out the parts about how do I get * my virtual machine to reboot off the cd the second, third time I restart it * to test the different install menu items without deleting the virt machine and recreating * how do I change the cd/dvd isoimage to handle the second piece of media > I am using bleeding edge rpms, git fc7.testing revisor:git pull, and I > should expect this. So I thought I'd ask while I try and reduce my loop > time from 4+ hours > build iso image, xen.new virt machine + play free civ, update scripts > and ks.list(s)....repeat > > Ideas, flames, constructive criticizing welcome. Here's an idea. The average desktop floating around any company will beat you to the 4+ hours of composing time (~30 minutes) and another will brighten your day doing installs in 15 minutes or less. * soon that might be an option, but using xen, is where some of this is going * kickstart files for different virt machine configurations, kind of hard to test those on * a desktop machine, without running xen which brings me to where I am. Kind regards, Jeroen van Meeuwen - -kanarip -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFHCe39KN6f2pNCvwgRAkkDAJ42TGT1FVUZP4LNkmXFMv2Gpbap5wCgkCj9 g3SfZdWP+TD5EOnvu2T+DgU= =j7R8 -----END PGP SIGNATURE----- sorry for the poor quoting, but yahoo does lack common features, like quoting replies Arno ____________________________________________________________________________________ Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. http://mobile.yahoo.com/go?refer=1GNXIC -------------- next part -------------- An HTML attachment was scrubbed... URL: From accarlson at gmail.com Thu Oct 11 13:35:18 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Thu, 11 Oct 2007 10:35:18 -0300 Subject: [Fedora-xen] Install, backup and recover Message-ID: Hi! I will have to install almost 30 servers with xen. Each server will host two guests. Both host and guests OS will be fedora 7. One hard disk partition will be allocated to each guest, for example: host -> /dev/sda1 guest1 -> /dev/sda2 guest2 -> /dev/sda3 I did some search in the list archives and google, but found what I was looking for. I would like to have some suggestion about the following: 1) The best approach to install all these hosts and guest? Cobbler? I'm not sure if the server configuration will be all the same. 2) If the hard disk fail, which is the best approach to recover the host and guests? Don't care about users data and server config files, as there will be user data and config backup. 3) If only one of the guests fail, which is the best approach to recover this guest? 4) If only the host fail, which is the best approach to recover this host and do not lost access to guest using to such as virt-manager/virsh/xm? I can provide more info if needed. Thanks in advance. Regards, -- Augusto Castelan Carlson From hehaifeng2nd at gmail.com Thu Oct 11 17:43:22 2007 From: hehaifeng2nd at gmail.com (Haifeng He) Date: Thu, 11 Oct 2007 10:43:22 -0700 Subject: [Fedora-xen] VFS: Cannot open root device "sda1" or unknown-block(0, 0) Message-ID: Hi, All I followed the steps in Fedora7VirtQuickStart to install Xen on Fedora 7. I downloaded couples of file system image from http://jailtime.org/. However, every time I tried to create guest OS using those file system image, I got error messages: VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) An example of Xen configure is: kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" memory = 256 name = "fedora.fc6" vif = [ '' ] dhcp = "dhcp" disk = ['file:/xen/fedora/fedora.fc6.img,sda1,w', 'file:/xen/fedora/fedora.swap, sda2,w'] root = "/dev/sda1 ro" Having been googling on this topic for a while, but still not getting the right answer for it. Any help will be appreciated. Thanks Haifeng From ehabkost at redhat.com Thu Oct 11 20:48:25 2007 From: ehabkost at redhat.com (Eduardo Habkost) Date: Thu, 11 Oct 2007 17:48:25 -0300 Subject: [Fedora-xen] VFS: Cannot open root device "sda1" or unknown-block(0, 0) In-Reply-To: References: Message-ID: <20071011204824.GL18282@blackpad.ctb.virtua.com.br> On Thu, Oct 11, 2007 at 10:43:22AM -0700, Haifeng He wrote: > Hi, All > > I followed the steps in Fedora7VirtQuickStart to install Xen on Fedora 7. > I downloaded couples of file system image from http://jailtime.org/. However, > every time I tried to create guest OS using those file system image, I got error > messages: > > VFS: Cannot open root device "sda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > An example of Xen configure is: > > kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" You don't have a initrd image that contains the block device and filesystem modules. I expect the images you have downloaded have a valid grub configuration inside it. If they have it, you can use: bootloader = "/usr/bin/pygrub" Instead of specifying a kernel that is outside the disk image. Pygrub will be able to read grub configuration and kernel/initrd images from inside the disk image. -- Eduardo From ierland at mail.be Wed Oct 10 07:11:54 2007 From: ierland at mail.be (progressdll) Date: Wed, 10 Oct 2007 00:11:54 -0700 (PDT) Subject: [Fedora-xen] are dropped packets a sign of network problem? Message-ID: <13130626.post@talk.nabble.com> in a xen environment , i see a lot op dropped packets via netstat -i Is this a sign of network problems, or is it normal to see this kind of numbers? i'm not sure how to interprete the data. is this normal, bad, critical. What are your stats on this? I guess i have a xen issue of some sort, but not sure what yet # netstat -i Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 0 53999491 0 0 0 6234874 0 0 0 BMRU lo 16436 0 9247734 0 0 0 9247734 0 0 0 LRU peth0 1500 0 135679270 0 0 0 95455766 0 0 0 BORU tap0 1500 0 5411876 0 0 0 35071803 0 0 0 BMRU vif-vmdeb 1500 0 0 0 0 0 35 0 333350 0 BORU vif0.0 1500 0 6234874 0 0 0 53999492 0 0 0 BORU vif6.0 1500 0 55813641 0 0 0 98482968 0 482338 0 BORU vif6.1 1500 0 0 0 0 0 39 0 46875771 0 BORU vif68.0 1500 0 0 0 0 0 0 0 0 0 BOU vif69.0 1500 0 9349348 0 0 0 30571290 0 3282 0 BORU vif69.1 1500 0 0 0 0 0 44 0 18947590 0 BORU vif70.0 1500 0 129605 0 0 0 460256 0 702 0 BORU vif70.1 1500 0 0 0 0 0 35 0 333350 0 BORU xenbr0 1500 0 46298695 0 0 0 0 0 0 0 BORU -- View this message in context: http://www.nabble.com/are-dropped-packets-a-sign-of-network-problem--tf4598987.html#a13130626 Sent from the Fedora Xen mailing list archive at Nabble.com. From hehaifeng2nd at gmail.com Fri Oct 12 17:06:43 2007 From: hehaifeng2nd at gmail.com (Haifeng He) Date: Fri, 12 Oct 2007 10:06:43 -0700 Subject: [Fedora-xen] VFS: Cannot open root device "sda1" or unknown-block(0, 0) In-Reply-To: <20071011204824.GL18282@blackpad.ctb.virtua.com.br> References: <20071011204824.GL18282@blackpad.ctb.virtua.com.br> Message-ID: On 10/11/07, Eduardo Habkost wrote: > On Thu, Oct 11, 2007 at 10:43:22AM -0700, Haifeng He wrote: > > Hi, All > > > > I followed the steps in Fedora7VirtQuickStart to install Xen on Fedora 7. > > I downloaded couples of file system image from http://jailtime.org/. However, > > every time I tried to create guest OS using those file system image, I got error > > messages: > > > > VFS: Cannot open root device "sda1" or unknown-block(0,0) > > Please append a correct "root=" boot option > > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > > > An example of Xen configure is: > > > > kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" > > You don't have a initrd image that contains the block device and > filesystem modules. > > I expect the images you have downloaded have a valid grub configuration > inside it. If they have it, you can use: > > bootloader = "/usr/bin/pygrub" > > Instead of specifying a kernel that is outside the disk image. Pygrub > will be able to read grub configuration and kernel/initrd images from > inside the disk image. > Thank you for your reply. I tried to include bootloader = "/usr/bin/pygrub" in my configuration but I got an error message "Error: Boot loader didn't return any data!". I was able to boot the same image on a Ubuntu system with Xen installed from source. Do I need to do something special on Fedora-Xen? Or there is a way that I can add block device and filesystem modules into the initrd image? Thanks Haifeng > -- > Eduardo > From rstevens at internap.com Fri Oct 12 17:32:58 2007 From: rstevens at internap.com (Rick Stevens) Date: Fri, 12 Oct 2007 10:32:58 -0700 Subject: [Fedora-xen] No agpgart? What? Message-ID: <1192210378.24062.40.camel@prophead.corp.publichost.com> Hi, gang. I'm trying to get an F7-based Xen dom0 running on my laptop (so I can run the "Dark Lord's" Vista as a domU). The laptop is an HP dv6000 with an Intel Duo Core proc and has the Intel graphics chipset. It all works well under F7, but the xen kernel doesn't create the agpgart devices as witnessed by the Xorg.0.log: (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (WW) intel(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. and hence, I can't use X (which makes Xen fairly useless to me). This is a fully updated F7. Relevant modules: kernel-xen-2.6.20-2936.fc7 xen-libs-3.1.0-6.fc7 xen-3.1.0-6.fc7 Any ideas? ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Denial. It ain't just a river in Egypt anymore! - ---------------------------------------------------------------------- From gabriel at intercastingcorp.com Fri Oct 12 17:35:25 2007 From: gabriel at intercastingcorp.com (Gabriel M. Schuyler) Date: Fri, 12 Oct 2007 10:35:25 -0700 Subject: [Fedora-xen] are dropped packets a sign of network problem? In-Reply-To: <13130626.post@talk.nabble.com> References: <13130626.post@talk.nabble.com> Message-ID: <4E47BAF1-05A5-486B-B2A4-E3F1C3794991@intercastingcorp.com> We've had some network problems that were resolved by disabling tcp checksum offloading on all the domUs. Our symptom was we couldn't ssh (or do much else) between two domUs on the same physical host. So on each domU we run: sudo /sbin/ethtool -K eth0 tx off Hope this helps! Gabe -- Gabriel M. Schuyler, sysop Intercasting Corporation On Oct 10, 2007, at 12:11 AM, progressdll wrote: > > in a xen environment , i see a lot op dropped packets via netstat -i > > Is this a sign of network problems, or is it normal to see this > kind of > numbers? i'm not sure how to interprete the data. is this normal, bad, > critical. What are your stats on this? > > I guess i have a xen issue of some sort, but not sure what yet > > # netstat -i > Kernel Interface table > Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR > TX-DRP > TX-OVR Flg > eth0 1500 0 53999491 0 0 0 6234874 > 0 0 > 0 BMRU > lo 16436 0 9247734 0 0 0 9247734 > 0 0 > 0 LRU > peth0 1500 0 135679270 0 0 0 95455766 > 0 0 > 0 BORU > tap0 1500 0 5411876 0 0 0 35071803 > 0 0 > 0 BMRU > vif-vmdeb 1500 0 0 0 0 0 35 0 > 333350 > 0 BORU > vif0.0 1500 0 6234874 0 0 0 53999492 > 0 0 > 0 BORU > vif6.0 1500 0 55813641 0 0 0 98482968 0 > 482338 > 0 BORU > vif6.1 1500 0 0 0 0 0 39 0 > 46875771 > 0 BORU > vif68.0 1500 0 0 0 0 0 0 > 0 0 > 0 BOU > vif69.0 1500 0 9349348 0 0 0 30571290 0 > 3282 > 0 BORU > vif69.1 1500 0 0 0 0 0 44 0 > 18947590 > 0 BORU > vif70.0 1500 0 129605 0 0 0 460256 > 0 702 > 0 BORU > vif70.1 1500 0 0 0 0 0 35 0 > 333350 > 0 BORU > xenbr0 1500 0 46298695 0 0 0 0 > 0 0 > 0 BORU > > -- > View this message in context: http://www.nabble.com/are-dropped- > packets-a-sign-of-network-problem--tf4598987.html#a13130626 > Sent from the Fedora Xen mailing list archive at Nabble.com. > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri Oct 12 17:44:02 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 12 Oct 2007 18:44:02 +0100 Subject: [Fedora-xen] are dropped packets a sign of network problem? In-Reply-To: <4E47BAF1-05A5-486B-B2A4-E3F1C3794991@intercastingcorp.com> References: <13130626.post@talk.nabble.com> <4E47BAF1-05A5-486B-B2A4-E3F1C3794991@intercastingcorp.com> Message-ID: <20071012174402.GA29689@redhat.com> On Fri, Oct 12, 2007 at 10:35:25AM -0700, Gabriel M. Schuyler wrote: > We've had some network problems that were resolved by disabling tcp > checksum offloading on all the domUs. Our symptom was we couldn't > ssh (or do much else) between two domUs on the same physical host. That should be neccessary at all - there were some bugs in this respect a long time ago, but it works fine now, assuming you keep your kernels up2date with errata. Turning off checksum offload will destroy network performance/throughput for your guests - particularly guest<->guest networking, but also guest -> network. 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 amos.shapira at gmail.com Mon Oct 15 01:09:27 2007 From: amos.shapira at gmail.com (Amos Shapira) Date: Mon, 15 Oct 2007 11:09:27 +1000 Subject: [Fedora-xen] installing FC7 under Debian Etch Message-ID: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> Hello, I'm trying to install Fedora 7 under Debian Etch running on Intel Xeon 3050 (i.e. with hardware virtualization) and x86_64 kernel (2.6.18-4-xen-amd64) with 4Gb RAM (the hardware supports up to 8Gb). I configured it this way: kernel = '/usr/lib/xen-3.0.3-1/boot/hvmloader' builder = 'linux' memory = '256' name = 'fc7-01' vif = ['type=ioemu, bridge=xenbr0'] disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] cdrom = 'file://root/iso/fc7/x86_64/boot.iso' device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' ne2000='0' boot='d' sdl='1' And when I try to run "xm create" I get: Using config file "/etc/xen/fc7-01.cfg". Error: (22, 'Invalid argument') And xend-debug.log contains: ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS >From googl'ing around for this error it looks like the FC kernel is PAE enabled but maybe the debian kernel isn't and this is the problem. (the hardware itself supports PAE according to /proc/cpuinfo) I get the same results trying to boot the i386 version of Fedora 7. Does anyone know whether this is the case? If so - what can I do to get things running? I couldn't find a non-pae Fedora installation image or a PAE-enabled Debian Etch kernel (I'm not sure it makes sense on x86_64 architecture). Also this Xen host runs Windows 2003 Server as a guest, in case this matters. Thanks, --Amos -------------- next part -------------- An HTML attachment was scrubbed... URL: From Nicola.Sabbi at poste.it Mon Oct 15 16:15:57 2007 From: Nicola.Sabbi at poste.it (Nico Sabbi) Date: Mon, 15 Oct 2007 18:15:57 +0200 Subject: [Fedora-xen] Can't ping windows HVM machine Message-ID: <200710151815.57418.Nicola.Sabbi@poste.it> Hi, using fc8-test2 updated with all packages available I could successfully install a windows xp machine, but I can't even ping it (although windows can ping my fedora and internet overall). The ip assigned to windows is in the range 192.168.122.x (assigned to a virtual nic) while the ip assigned to fedora is 192.168.2.102. route -n shows everything correctly set up (192.168.122.0/24 going through the virtual interface (virbr0 IIRC)), but still I can't ping the virtual machine, even if I run $ /etc/init.d/iptables stop What did I do wrong? BTW, since it's well known that in the virtual machine the usb mouse must be replace with a usb tablet to make the pointer work correctly, I guess that this option should be set by default rather than making users swear for hours :) Thanks, Nico From ehabkost at redhat.com Mon Oct 15 16:17:00 2007 From: ehabkost at redhat.com (Eduardo Pereira Habkost) Date: Mon, 15 Oct 2007 14:17:00 -0200 Subject: [Fedora-xen] VFS: Cannot open root device "sda1" or unknown-block(0, 0) In-Reply-To: References: <20071011204824.GL18282@blackpad.ctb.virtua.com.br> Message-ID: <20071015161700.GC7278@blackpad.ctb.virtua.com.br> On Fri, Oct 12, 2007 at 10:06:43AM -0700, Haifeng He wrote: > > > > I expect the images you have downloaded have a valid grub configuration > > inside it. If they have it, you can use: > > > > bootloader = "/usr/bin/pygrub" > > > > Instead of specifying a kernel that is outside the disk image. Pygrub > > will be able to read grub configuration and kernel/initrd images from > > inside the disk image. > > > > Thank you for your reply. I tried to include bootloader = "/usr/bin/pygrub" > in my configuration but I got an error message "Error: Boot loader > didn't return any data!". > I was able to boot the same image on a Ubuntu system with Xen > installed from source. > Do I need to do something special on Fedora-Xen? Or there is a way that I > can add block device and filesystem modules into the initrd image? I took a look at the config file shipped with Fedora images on the site you mentioned. It looks like it expects you to have a pre-compiled domU kernel that contains all needed modules, on you host /boot directory. I don't know which kernel image the author of those images expects you to use. Some things you can try: - Checking the instructions on the README.txt inside the image, as noted on . Maybe there are some clues there; or - Try to generate a initrd that will contain all needed modules. You can play with the --omit-* and --with options of mkinitrd to get a initrd with the right modules; or - Try using the Xen kernel and initrd from the FC-6 repository: http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/images/xen/ or - Get a domU kernel with all needed modules compiled as builtin (so you don't need a initrd) from somewhere, or compile a domU kernel this way; or - Put a valid grub configuration (and a kernel-xen package) inside the image, to get pygrub to work; or - Use virt-manager and install your own FC-6 system instead of using the downloaded image. -- Eduardo From rstevens at internap.com Mon Oct 15 18:56:13 2007 From: rstevens at internap.com (Rick Stevens) Date: Mon, 15 Oct 2007 11:56:13 -0700 Subject: [Fedora-xen] No agpgart? What? Message-ID: <1192474573.5991.33.camel@prophead.corp.publichost.com> This is a repost, since I got some weird message from the mail server that it thought it was spam. Forgive me if you've seen it before. I'm trying to get an F7-based Xen dom0 running on my laptop (I need to run Vista as a domU, ugh!). The laptop is an HP dv6000 with an Intel Duo Core proc and has the Intel graphics chipset. The laptop runs perfectly fine under standard F7, but the xen kernel doesn't create the agpgart devices as witnessed by the Xorg.0.log: (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (WW) intel(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. and hence, I can't use X (which makes Xen fairly useless to me). This is a fully updated F7. Relevant modules: kernel-xen-2.6.20-2936.fc7 xen-libs-3.1.0-6.fc7 xen-3.1.0-6.fc7 Any ideas? ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Denial. It ain't just a river in Egypt anymore! - ---------------------------------------------------------------------- From steve at atc-nycorp.com Mon Oct 15 19:17:57 2007 From: steve at atc-nycorp.com (Steve Brueckner) Date: Mon, 15 Oct 2007 15:17:57 -0400 Subject: [Fedora-xen] Can't ping windows HVM machine Message-ID: <60D45469A1AAD311A04C009027B6BF68062EFB4B@SERVER20> Just in case you haven't already checked this: I think Windows comes with the firewall configured to block icmp echo requests by default. At least, that's bitten me in your exact situation in the past. Steve Brueckner, ATC-NY -----Original Message----- From: Nico Sabbi [mailto:Nicola.Sabbi at poste.it] Sent: Monday, October 15, 2007 12:16 PM To: Fedora-xen at redhat.com Subject: [Fedora-xen] Can't ping windows HVM machine Hi, using fc8-test2 updated with all packages available I could successfully install a windows xp machine, but I can't even ping it (although windows can ping my fedora and internet overall). The ip assigned to windows is in the range 192.168.122.x (assigned to a virtual nic) while the ip assigned to fedora is 192.168.2.102. route -n shows everything correctly set up (192.168.122.0/24 going through the virtual interface (virbr0 IIRC)), but still I can't ping the virtual machine, even if I run $ /etc/init.d/iptables stop What did I do wrong? BTW, since it's well known that in the virtual machine the usb mouse must be replace with a usb tablet to make the pointer work correctly, I guess that this option should be set by default rather than making users swear for hours :) Thanks, Nico -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From rjones at redhat.com Tue Oct 16 15:21:41 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 16 Oct 2007 16:21:41 +0100 Subject: [Fedora-xen] No agpgart? What? In-Reply-To: <1192210378.24062.40.camel@prophead.corp.publichost.com> References: <1192210378.24062.40.camel@prophead.corp.publichost.com> Message-ID: <4714D705.5050903@redhat.com> Rick Stevens wrote: > Hi, gang. I'm trying to get an F7-based Xen dom0 running on my laptop > (so I can run the "Dark Lord's" Vista as a domU). The laptop is an > HP dv6000 with an Intel Duo Core proc and has the Intel graphics > chipset. > > It all works well under F7, but the xen kernel doesn't create the > agpgart devices as witnessed by the Xorg.0.log: > > (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) > (WW) intel(0): /dev/agpgart is either not available, or no memory is > available > for allocation. Using pre-allocated memory only. > > and hence, I can't use X (which makes Xen fairly useless to me). This > is a fully updated F7. Relevant modules: So X doesn't start? Can you post the full Xorg logfile please. 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 slbubba at charter.net Tue Oct 16 17:17:48 2007 From: slbubba at charter.net (slbubba at charter.net) Date: Tue, 16 Oct 2007 10:17:48 -0700 Subject: [Fedora-xen] xmlrpc python and session login Message-ID: <20071016131748.M75YO.79255.root@fepweb03> Folks; I'm trying to see what's available (working) in xen for remote management. I thought I'd try something simple using xmlrpclib and python. I tried establishing a session and logging in but I'm not getting anywhere fast. It appears that either xend isn't functional in this area or something (perhaps) is not set correctly in the xend-config.sxp file. Has anyone been able to login to a xen system successfully? Are any of the facilities in the xend-config file functional with this RH version of xend? OS: RHEL5.0 latest update kernel: 2.6.18-8.1.14.el5xen RPM's: xen-libs-3.0.3-25.0.4.el5 xen-3.0.3-25.0.4.el5 python-2.4.3-19.el5 ----------- python >>> import xmlrpclib >>> xen = xmlrpclib.Server("http://mysys.com:8006") >>> asess = xen.session.login_with_password("batman", "monkeypus") socket.error: (111, 'Connection refused') Thanks Warren From rstevens at internap.com Tue Oct 16 22:26:15 2007 From: rstevens at internap.com (Rick Stevens) Date: Tue, 16 Oct 2007 15:26:15 -0700 Subject: [Fedora-xen] Follow up to "No agpgart? What?" Message-ID: <1192573575.3438.2.camel@prophead.corp.publichost.com> Rich Jones offered to post this for me (because I sent it to him directly by accident). However, I'll post it myself. On Tue, 2007-10-16 at 16:21 +0100, Richard W.M. Jones wrote: > Rick Stevens wrote: > > Hi, gang. I'm trying to get an F7-based Xen dom0 running on my laptop > > (so I can run the "Dark Lord's" Vista as a domU). The laptop is an > > HP dv6000 with an Intel Duo Core proc and has the Intel graphics > > chipset. > > > > It all works well under F7, but the xen kernel doesn't create the > > agpgart devices as witnessed by the Xorg.0.log: > > > > (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) > > (WW) intel(0): /dev/agpgart is either not available, or no memory is > > available > > for allocation. Using pre-allocated memory only. > > > > and hence, I can't use X (which makes Xen fairly useless to me). This > > is a fully updated F7. Relevant modules: > > So X doesn't start? Can you post the full Xorg logfile please. Attached below, and I apologize for the length of the post, gang! -------------------------- CUT HERE ------------------------------ X Window System Version 1.3.0 Release Date: 19 April 2007 X Protocol Version 11, Revision 0, Release 1.3 Build Operating System: Fedora Core 7 Red Hat, Inc. Current Operating System: Linux golem3.ssssc.com 2.6.20-2936.fc7xen #1 SMP Fri Sep 21 11:56:20 EDT 2007 x86_64 Build Date: 11 June 2007 Build ID: xorg-x11-server 1.3.0.0-9.fc7 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Oct 10 16:15:45 2007 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "" (**) | |-->Device "Videocard0" (WW) No monitor specified for screen "Screen0". Using a default monitor configuration. (**) |-->Input Device "Keyboard0" (**) |-->Input Device "Synaptics" (II) No default mouse found, adding one (**) |-->Input Device "" (WW) No FontPath specified. Using compiled-in default. (==) FontPath set to: unix/:7100, built-ins (==) RgbPath set to "/usr/share/X11/rgb" (==) ModulePath set to "/usr/lib64/xorg/modules" (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Loader magic: 0x7be760 (II) Module ABI versions: X.Org ANSI C Emulation: 0.3 X.Org Video Driver: 1.2 X.Org XInput driver : 0.7 X.Org Server Extension : 0.3 X.Org Font Renderer : 0.5 (II) Loader running on linux (II) LoadModule: "pcidata" (II) Loading /usr/lib64/xorg/modules//libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (++) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,2a00 card 103c,30cc rev 0c class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,2a02 card 103c,30cc rev 0c class 03,00,00 hdr 80 (II) PCI: 00:02:1: chip 8086,2a03 card 103c,30cc rev 0c class 03,80,00 hdr 80 (II) PCI: 00:1a:0: chip 8086,2834 card 103c,30cc rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1a:1: chip 8086,2835 card 103c,30cc rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1a:7: chip 8086,283a card 103c,30cc rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1b:0: chip 8086,284b card 103c,30cc rev 03 class 04,03,00 hdr 00 (II) PCI: 00:1c:0: chip 8086,283f card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:1: chip 8086,2841 card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1c:5: chip 8086,2849 card 0000,0000 rev 03 class 06,04,00 hdr 81 (II) PCI: 00:1d:0: chip 8086,2830 card 103c,30cc rev 03 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,2831 card 103c,30cc rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,2832 card 103c,30cc rev 03 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,2836 card 103c,30cc rev 03 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,2448 card 0000,0000 rev f3 class 06,04,01 hdr 01 (II) PCI: 00:1f:0: chip 8086,2815 card 103c,30cc rev 03 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,2850 card 103c,30cc rev 03 class 01,01,8a hdr 00 (II) PCI: 00:1f:2: chip 8086,2829 card 103c,30cc rev 03 class 01,06,01 hdr 00 (II) PCI: 00:1f:3: chip 8086,283e card 103c,30cc rev 03 class 0c,05,00 hdr 00 (II) PCI: 02:00:0: chip 8086,4229 card 8086,1100 rev 61 class 02,80,00 hdr 00 (II) PCI: 06:00:0: chip 10ec,8136 card 103c,30cc rev 01 class 02,00,00 hdr 00 (II) PCI: 07:09:0: chip 1180,0832 card 103c,30cc rev 05 class 0c,00,10 hdr 80 (II) PCI: 07:09:1: chip 1180,0822 card 103c,30cc rev 22 class 08,05,00 hdr 80 (II) PCI: 07:09:2: chip 1180,0843 card 103c,30cc rev 12 class 08,80,00 hdr 80 (II) PCI: 07:09:3: chip 1180,0592 card 103c,30cc rev 12 class 08,80,00 hdr 80 (II) PCI: 07:09:4: chip 1180,0852 card 103c,30cc rev 12 class 08,80,00 hdr 80 (II) PCI: End of PCI scan (II) Intel Bridge workaround enabled (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,7), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 2: bridge is at (0:28:0), (0,2,3), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 2 non-prefetchable memory range: [0] -1 0 0xf8200000 - 0xf82fffff (0x100000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 4: bridge is at (0:28:1), (0,4,5), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 4 I/O range: [0] -1 0 0x00002000 - 0x000020ff (0x100) IX[B] [1] -1 0 0x00002400 - 0x000024ff (0x100) IX[B] [2] -1 0 0x00002800 - 0x000028ff (0x100) IX[B] [3] -1 0 0x00002c00 - 0x00002cff (0x100) IX[B] (II) Bus 4 non-prefetchable memory range: [0] -1 0 0xf4000000 - 0xf7ffffff (0x4000000) MX[B] (II) Bus 4 prefetchable memory range: [0] -1 0 0xf0000000 - 0xf3ffffff (0x4000000) MX[B] (II) PCI-to-PCI bridge: (II) Bus 6: bridge is at (0:28:5), (0,6,6), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 6 I/O range: [0] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [1] -1 0 0x00003400 - 0x000034ff (0x100) IX[B] [2] -1 0 0x00003800 - 0x000038ff (0x100) IX[B] [3] -1 0 0x00003c00 - 0x00003cff (0x100) IX[B] (II) Bus 6 non-prefetchable memory range: [0] -1 0 0xf8300000 - 0xf83fffff (0x100000) MX[B] (II) Bus 6 prefetchable memory range: [0] -1 0 0x88000000 - 0x880fffff (0x100000) MX[B] (II) Subtractive PCI-to-PCI bridge: (II) Bus 7: bridge is at (0:30:0), (0,7,7), BCTRL: 0x0004 (VGA_EN is cleared) (II) Bus 7 non-prefetchable memory range: [0] -1 0 0xf8400000 - 0xf84fffff (0x100000) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:31:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(0:2:0) Intel Corporation Mobile Integrated Graphics Controller rev 12, Mem @ 0xf8000000/20, 0xd0000000/28, I/O @ 0x1800/3 (--) PCI: (0:2:1) Intel Corporation Mobile Integrated Graphics Controller rev 12, Mem @ 0xf8100000/20 (II) Addressable bus resource ranges are [0] -1 0 0x00000000 - 0xffffffff (0x100000000) MX[B] [1] -1 0 0x00000000 - 0x0000ffff (0x10000) IX[B] (II) OS-reported resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B] [1] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B] [2] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B] [3] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B] [4] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B] [5] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B] [6] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B] [7] -1 0 0x88100000 - 0x881000ff (0x100) MX[B] [8] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B] [9] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B] [10] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B] [11] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B] [12] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B) [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [14] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B) [15] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [16] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [17] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B] [18] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B] [19] -1 0 0x000018d8 - 0x000018df (0x8) IX[B] [20] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B] [21] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B] [22] -1 0 0x00001810 - 0x0000181f (0x10) IX[B] [23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [25] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [26] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [27] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [28] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [31] -1 0 0x00001820 - 0x0000183f (0x20) IX[B] [32] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) Active PCI resource ranges after removing overlaps: [0] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B] [1] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B] [2] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B] [3] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B] [4] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B] [5] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B] [6] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B] [7] -1 0 0x88100000 - 0x881000ff (0x100) MX[B] [8] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B] [9] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B] [10] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B] [11] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B] [12] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B) [13] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [14] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B) [15] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [16] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [17] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B] [18] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B] [19] -1 0 0x000018d8 - 0x000018df (0x8) IX[B] [20] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B] [21] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B] [22] -1 0 0x00001810 - 0x0000181f (0x10) IX[B] [23] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [24] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [25] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [26] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [27] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [28] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [29] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [30] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [31] -1 0 0x00001820 - 0x0000183f (0x20) IX[B] [32] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) OS-reported resource ranges after removing overlaps with PCI: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [5] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] (II) All system resource ranges: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B] [5] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B] [6] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B] [7] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B] [8] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B] [9] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B] [10] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B] [11] -1 0 0x88100000 - 0x881000ff (0x100) MX[B] [12] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B] [13] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B] [14] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B] [15] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B] [16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B) [19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [21] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [22] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [23] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B] [24] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B] [25] -1 0 0x000018d8 - 0x000018df (0x8) IX[B] [26] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B] [27] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B] [28] -1 0 0x00001810 - 0x0000181f (0x10) IX[B] [29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [30] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [31] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [32] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [34] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [35] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [36] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [37] -1 0 0x00001820 - 0x0000183f (0x20) IX[B] [38] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) LoadModule: "vnc" (II) Loading /usr/lib64/xorg/modules/extensions//libvnc.so (II) Module vnc: vendor="RealVNC Ltd" compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 0.3 (II) Loading extension VNC (II) LoadModule: "intel" (II) Loading /usr/lib64/xorg/modules/drivers//intel_drv.so (II) Module intel: vendor="X.Org Foundation" compiled for 1.3.0, module version = 2.0.0 Module class: X.Org Video Driver ABI class: X.Org Video Driver, version 1.2 (II) LoadModule: "kbd" (II) Loading /usr/lib64/xorg/modules/input//kbd_drv.so (II) Module kbd: vendor="X.Org Foundation" compiled for 7.2.0, module version = 1.1.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) LoadModule: "synaptics" (II) Loading /usr/lib64/xorg/modules/input//synaptics_drv.so (II) Module synaptics: vendor="X.Org Foundation" compiled for 4.3.99.902, module version = 1.0.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) LoadModule: "mouse" (II) Loading /usr/lib64/xorg/modules/input//mouse_drv.so (II) Module mouse: vendor="X.Org Foundation" compiled for 7.2.0, module version = 1.1.1 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 0.6 (II) intel: Driver for Intel Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, 965G, 965G, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33 (II) Primary Device is: PCI 00:02:0 (--) Assigning device section with no busID to primary device (WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found (--) Chipset 965GM found (II) resource ranges after xf86ClaimFixedResources() call: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B] [5] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B] [6] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B] [7] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B] [8] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B] [9] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B] [10] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B] [11] -1 0 0x88100000 - 0x881000ff (0x100) MX[B] [12] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B] [13] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B] [14] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B] [15] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B] [16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B) [19] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [20] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [21] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [22] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [23] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B] [24] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B] [25] -1 0 0x000018d8 - 0x000018df (0x8) IX[B] [26] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B] [27] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B] [28] -1 0 0x00001810 - 0x0000181f (0x10) IX[B] [29] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [30] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [31] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [32] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [33] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [34] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [35] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [36] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [37] -1 0 0x00001820 - 0x0000183f (0x20) IX[B] [38] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) (II) resource ranges after probing: [0] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [4] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B] [5] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B] [6] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B] [7] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B] [8] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B] [9] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B] [10] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B] [11] -1 0 0x88100000 - 0x881000ff (0x100) MX[B] [12] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B] [13] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B] [14] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B] [15] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B] [16] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B) [17] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [18] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B) [19] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B] [20] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B] [21] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B] [22] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [23] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [24] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [25] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [26] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B] [27] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B] [28] -1 0 0x000018d8 - 0x000018df (0x8) IX[B] [29] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B] [30] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B] [31] -1 0 0x00001810 - 0x0000181f (0x10) IX[B] [32] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [33] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [34] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [35] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [36] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [37] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [38] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [39] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [40] -1 0 0x00001820 - 0x0000183f (0x20) IX[B] [41] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) [42] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B] [43] 0 0 0x000003c0 - 0x000003df (0x20) IS[B] (II) Setting vga for screen 0. (II) Enabling PCI device (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Loading /usr/lib64/xorg/modules//libint10.so (II) Module int10: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 1.2 (II) Loading sub module "vbe" (II) LoadModule: "vbe" (II) Loading /usr/lib64/xorg/modules//libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.1.0 ABI class: X.Org Video Driver, version 1.2 (II) Loading sub module "vgahw" (II) LoadModule: "vgahw" (II) Loading /usr/lib64/xorg/modules//libvgahw.so (II) Module vgahw: vendor="X.Org Foundation" compiled for 1.3.0, module version = 0.1.0 ABI class: X.Org Video Driver, version 1.2 (**) intel(0): Depth 24, (--) framebuffer bpp 32 (==) intel(0): RGB weight 888 (==) intel(0): Default visual is TrueColor (II) intel(0): Integrated Graphics Chipset: Intel(R) 965GM (--) intel(0): Chipset: "965GM" (--) intel(0): Linear framebuffer at 0xD0000000 (--) intel(0): IO registers at addr 0xF8000000 (II) intel(0): 2 display pipes available. (==) intel(0): Using XAA for acceleration (--) intel(0): Will try to allocate texture pool for old Mesa 3D driver. (II) intel(0): Will try to reserve 32768 kiB of AGP aperture space for the DRM memory manager. (II) Loading sub module "ddc" (II) LoadModule: "ddc"(II) Module already built-in (II) Loading sub module "i2c" (II) LoadModule: "i2c"(II) Module already built-in (II) intel(0): Output VGA has no monitor section (II) intel(0): I2C bus "CRTDDC_A" initialized. (II) intel(0): Output LVDS has no monitor section (II) intel(0): I2C bus "LVDSDDC_C" initialized. (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): EDID for output LVDS (II) intel(0): Manufacturer: SEC Model: 3345 Serial#: 0 (II) intel(0): Year: 2004 Week: 0 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max H-Image Size [cm]: horiz.: 33 vert.: 21 (II) intel(0): Gamma: 2.20 (II) intel(0): No DPMS capabilities specified; RGB/Color Display (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.580 redY: 0.340 greenX: 0.310 greenY: 0.550 (II) intel(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329 (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 68.9 MHz Image Size: 331 x 207 mm (II) intel(0): h_active: 1280 h_sync: 1296 h_sync_end 1344 h_blank_end 1408 h_border: 0 (II) intel(0): v_active: 800 v_sync: 801 v_sync_end 804 v_blanking: 816 v_border: 0 (II) intel(0): SAMSUNG (II) intel(0): LTN154X3-L01 (II) intel(0): EDID (in hex): (II) intel(0): 00ffffffffffff004ca3453300000000 (II) intel(0): 000e0103802115780a87f594574f8c27 (II) intel(0): 27505400000001010101010101010101 (II) intel(0): 010101010101ee1a0080502010301030 (II) intel(0): 13004bcf100000190000000f00000000 (II) intel(0): 00000000002387026401000000fe0053 (II) intel(0): 414d53554e470a2020202020000000fe (II) intel(0): 004c544e31353458332d4c30310a0068 (II) intel(0): EDID vendor "SEC", prod id 13125 (II) Loading sub module "int10" (II) LoadModule: "int10" (II) Reloading /usr/lib64/xorg/modules//libint10.so (II) intel(0): initializing int10 (WW) intel(0): Bad V_BIOS checksum (II) intel(0): Primary V_BIOS segment is: 0xc000 (II) intel(0): VESA BIOS detected (II) intel(0): VESA VBE Version 3.0 (II) intel(0): VESA VBE Total Mem: 7616 kB (II) intel(0): VESA VBE OEM: Intel(r)Crestline Graphics Chip Accelerated VGA BIOS (II) intel(0): VESA VBE OEM Software Rev: 1.0 (II) intel(0): VESA VBE OEM Vendor: Intel Corporation (II) intel(0): VESA VBE OEM Product: Intel(r)Crestline Graphics Controller (II) intel(0): VESA VBE OEM Product Rev: Hardware Version 0.0 (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" registered at address 0x70. (II) intel(0): No SDVO device found on SDVOB (II) intel(0): I2C device "SDVOCTRL_E for SDVOB:SDVO Controller B" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOB" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" initialized. (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" registered at address 0x72. (II) intel(0): No SDVO device found on SDVOC (II) intel(0): I2C device "SDVOCTRL_E for SDVOC:SDVO Controller C" removed. (II) intel(0): I2C bus "SDVOCTRL_E for SDVOC" removed. (II) intel(0): Output TV has no monitor section (II) intel(0): Output VGA disconnected (II) intel(0): EDID for output VGA (II) intel(0): Output LVDS connected (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): EDID for output LVDS (II) intel(0): Manufacturer: SEC Model: 3345 Serial#: 0 (II) intel(0): Year: 2004 Week: 0 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max H-Image Size [cm]: horiz.: 33 vert.: 21 (II) intel(0): Gamma: 2.20 (II) intel(0): No DPMS capabilities specified; RGB/Color Display (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.580 redY: 0.340 greenX: 0.310 greenY: 0.550 (II) intel(0): blueX: 0.155 blueY: 0.155 whiteX: 0.313 whiteY: 0.329 (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 68.9 MHz Image Size: 331 x 207 mm (II) intel(0): h_active: 1280 h_sync: 1296 h_sync_end 1344 h_blank_end 1408 h_border: 0 (II) intel(0): v_active: 800 v_sync: 801 v_sync_end 804 v_blanking: 816 v_border: 0 (II) intel(0): SAMSUNG (II) intel(0): LTN154X3-L01 (II) intel(0): EDID (in hex): (II) intel(0): 00ffffffffffff004ca3453300000000 (II) intel(0): 000e0103802115780a87f594574f8c27 (II) intel(0): 27505400000001010101010101010101 (II) intel(0): 010101010101ee1a0080502010301030 (II) intel(0): 13004bcf100000190000000f00000000 (II) intel(0): 00000000002387026401000000fe0053 (II) intel(0): 414d53554e470a2020202020000000fe (II) intel(0): 004c544e31353458332d4c30310a0068 (II) intel(0): EDID vendor "SEC", prod id 13125 (II) intel(0): Not using default mode "640x350" (vrefresh out of range) (II) intel(0): Not using default mode "640x400" (vrefresh out of range) (II) intel(0): Not using default mode "720x400" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1280x960" (hsync out of range) (II) intel(0): Not using default mode "1280x960" (vrefresh out of range) (II) intel(0): Not using default mode "1280x1024" (hsync out of range) (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) (II) intel(0): Not using default mode "1600x1200" (hsync out of range) (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1600x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1792x1344" (hsync out of range) (II) intel(0): Not using default mode "1792x1344" (vrefresh out of range) (II) intel(0): Not using default mode "1856x1392" (hsync out of range) (II) intel(0): Not using default mode "1856x1392" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1440" (hsync out of range) (II) intel(0): Not using default mode "1920x1440" (vrefresh out of range) (II) intel(0): Not using default mode "832x624" (vrefresh out of range) (II) intel(0): Not using default mode "1152x768" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (exceeds panel dimensions) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1280x720" (vrefresh out of range) (II) intel(0): Not using default mode "1280x720" (vrefresh out of range) (II) intel(0): Not using default mode "1280x720" (vrefresh out of range) (II) intel(0): Not using default mode "1280x800" (vrefresh out of range) (II) intel(0): Not using default mode "1280x800" (vrefresh out of range) (II) intel(0): Not using default mode "1280x800" (vrefresh out of range) (II) intel(0): Not using default mode "1280x768" (vrefresh out of range) (II) intel(0): Not using default mode "1280x768" (vrefresh out of range) (II) intel(0): Not using default mode "1280x768" (vrefresh out of range) (II) intel(0): Not using default mode "1360x768" (exceeds panel dimensions) (II) intel(0): Not using default mode "1360x768" (exceeds panel dimensions) (II) intel(0): Not using default mode "1400x1050" (hsync out of range) (II) intel(0): Not using default mode "1400x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1400x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1400x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1400x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1400x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1440x900" (hsync out of range) (II) intel(0): Not using default mode "1600x1024" (hsync out of range) (II) intel(0): Not using default mode "1680x1050" (hsync out of range) (II) intel(0): Not using default mode "1680x1050" (hsync out of range) (II) intel(0): Not using default mode "1680x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1680x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1680x1050" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1080" (hsync out of range) (II) intel(0): Not using default mode "1920x1080" (hsync out of range) (II) intel(0): Not using default mode "1920x1080" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1080" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1080" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1200" (hsync out of range) (II) intel(0): Not using default mode "1920x1200" (hsync out of range) (II) intel(0): Not using default mode "1920x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1200" (vrefresh out of range) (II) intel(0): Not using default mode "1920x1440" (vrefresh out of range) (II) intel(0): Not using default mode "2048x1536" (hsync out of range) (II) intel(0): Not using default mode "2048x1536" (vrefresh out of range) (II) intel(0): Not using default mode "2048x1536" (vrefresh out of range) (II) intel(0): Not using default mode "2560x1600" (hsync out of range) (II) intel(0): Printing probed modes for output LVDS (II) intel(0): Modeline "1280x800"x60.0 68.94 1280 1296 1344 1408 800 801 804 816 -hsync -vsync (49.0 kHz) (II) intel(0): Modeline "1280x800"x60.0 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync (49.7 kHz) (II) intel(0): Modeline "1280x768"x60.0 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync (47.7 kHz) (II) intel(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz) (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) intel(0): Output TV disconnected (II) intel(0): EDID for output TV (II) intel(0): Output VGA disconnected (II) intel(0): Output LVDS connected (II) intel(0): Output TV disconnected (II) intel(0): Output LVDS using initial mode 1280x800 (II) intel(0): Monitoring connected displays enabled (II) intel(0): detected 512 kB GTT. (II) intel(0): detected 7676 kB stolen memory. (==) intel(0): video overlay key set to 0x101fe (==) intel(0): Will not try to enable page flipping (==) intel(0): Triple buffering disabled (==) intel(0): Using gamma correction (1.0, 1.0, 1.0) (==) intel(0): DPI set to (75, 75) (II) Loading sub module "fb" (II) LoadModule: "fb" (II) Loading /usr/lib64/xorg/modules//libfb.so (II) Module fb: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.0.0 ABI class: X.Org ANSI C Emulation, version 0.3 (II) Loading sub module "xaa" (II) LoadModule: "xaa" (II) Loading /usr/lib64/xorg/modules//libxaa.so (II) Module xaa: vendor="X.Org Foundation" compiled for 1.3.0, module version = 1.2.0 ABI class: X.Org Video Driver, version 1.2 (II) Loading sub module "ramdac" (II) LoadModule: "ramdac"(II) Module already built-in (II) intel(0): Comparing regs from server start up to After PreInit (==) Depth 24 pixmap format is 32 bpp (II) do I need RAC? No, I don't. (II) resource ranges after preInit: [0] 0 0 0xd0000000 - 0xdfffffff (0x10000000) MS[B] [1] 0 0 0xf8000000 - 0xf80fffff (0x100000) MS[B] [2] -1 0 0x00100000 - 0x3fffffff (0x3ff00000) MX[B]E(B) [3] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[B] [4] -1 0 0x000c0000 - 0x000effff (0x30000) MX[B] [5] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[B] [6] -1 0 0xf8401400 - 0xf84014ff (0x100) MX[B] [7] -1 0 0xf8401000 - 0xf84010ff (0x100) MX[B] [8] -1 0 0xf8400c00 - 0xf8400cff (0x100) MX[B] [9] -1 0 0xf8400800 - 0xf84008ff (0x100) MX[B] [10] -1 0 0xf8400000 - 0xf84007ff (0x800) MX[B] [11] -1 0 0xf8300000 - 0xf8300fff (0x1000) MX[B] [12] -1 0 0xf8200000 - 0xf8201fff (0x2000) MX[B] [13] -1 0 0x88100000 - 0x881000ff (0x100) MX[B] [14] -1 0 0xf8704000 - 0xf87047ff (0x800) MX[B] [15] -1 0 0xf8704c00 - 0xf8704fff (0x400) MX[B] [16] -1 0 0xf8700000 - 0xf8703fff (0x4000) MX[B] [17] -1 0 0xf8704800 - 0xf8704bff (0x400) MX[B] [18] -1 0 0xf8100000 - 0xf81fffff (0x100000) MX[B](B) [19] -1 0 0xd0000000 - 0xdfffffff (0x10000000) MX[B](B) [20] -1 0 0xf8000000 - 0xf80fffff (0x100000) MX[B](B) [21] 0 0 0x000a0000 - 0x000affff (0x10000) MS[B](OprD) [22] 0 0 0x000b0000 - 0x000b7fff (0x8000) MS[B](OprD) [23] 0 0 0x000b8000 - 0x000bffff (0x8000) MS[B](OprD) [24] 0 0 0x00001800 - 0x00001807 (0x8) IS[B] [25] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[B] [26] -1 0 0x00000000 - 0x000000ff (0x100) IX[B] [27] -1 0 0x00003000 - 0x000030ff (0x100) IX[B] [28] -1 0 0x00001c20 - 0x00001c3f (0x20) IX[B] [29] -1 0 0x000018e0 - 0x000018ff (0x20) IX[B] [30] -1 0 0x000018d0 - 0x000018d3 (0x4) IX[B] [31] -1 0 0x000018d8 - 0x000018df (0x8) IX[B] [32] -1 0 0x000018d4 - 0x000018d7 (0x4) IX[B] [33] -1 0 0x00001c00 - 0x00001c07 (0x8) IX[B] [34] -1 0 0x00001810 - 0x0000181f (0x10) IX[B] [35] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [36] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [37] -1 0 0x000001f0 - 0x000001f0 (0x1) IX[B] [38] -1 0 0x000001f0 - 0x000001f7 (0x8) IX[B] [39] -1 0 0x000018a0 - 0x000018bf (0x20) IX[B] [40] -1 0 0x00001880 - 0x0000189f (0x20) IX[B] [41] -1 0 0x00001860 - 0x0000187f (0x20) IX[B] [42] -1 0 0x00001840 - 0x0000185f (0x20) IX[B] [43] -1 0 0x00001820 - 0x0000183f (0x20) IX[B] [44] -1 0 0x00001800 - 0x00001807 (0x8) IX[B](B) [45] 0 0 0x000003b0 - 0x000003bb (0xc) IS[B](OprU) [46] 0 0 0x000003c0 - 0x000003df (0x20) IS[B](OprU) (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) (WW) intel(0): /dev/agpgart is either not available, or no memory is available for allocation. Using pre-allocated memory only. (==) intel(0): VideoRam: 7676 KB (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded (II) intel(0): Allocating 255 scanlines for pixmap cache (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too low? (EE) intel(0): Couldn't allocate video memory Fatal server error: AddScreen/ScreenInit failed for driver 0 -------------------------- CUT HERE ------------------------------ ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Which is worse: ignorance or apathy? I don't know. Who cares? - ---------------------------------------------------------------------- From debian at herakles.homelinux.org Tue Oct 16 23:59:30 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 17 Oct 2007 07:59:30 +0800 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> Message-ID: <47155062.2030200@herakles.homelinux.org> Amos Shapira wrote: > Hello, > > I'm trying to install Fedora 7 under Debian Etch running on Intel Xeon 3050 > (i.e. with hardware virtualization) and x86_64 kernel (2.6.18-4-xen-amd64) > with 4Gb RAM (the hardware supports up to 8Gb). > > I configured it this way: > > kernel = '/usr/lib/xen-3.0.3-1/boot/hvmloader' > builder = 'linux' > memory = '256' > name = 'fc7-01' > vif = ['type=ioemu, bridge=xenbr0'] > disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] > cdrom = 'file://root/iso/fc7/x86_64/boot.iso' > device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' > ne2000='0' > boot='d' > sdl='1' > > And when I try to run "xm create" I get: > Using config file "/etc/xen/fc7-01.cfg". > Error: (22, 'Invalid argument') > > And xend-debug.log contains: > > ERROR: Kernel not a Xen-compatible Elf image. > ERROR: Error constructing guest OS > >>From googl'ing around for this error it looks like the FC kernel is PAE > enabled but maybe the debian kernel isn't and this is the problem. > (the hardware itself supports PAE according to /proc/cpuinfo) > > I get the same results trying to boot the i386 version of Fedora 7. > > Does anyone know whether this is the case? If so - what can I do to get > things running? I couldn't find a non-pae Fedora installation image or a > PAE-enabled Debian Etch kernel (I'm not sure it makes sense on x86_64 > architecture). > > Also this Xen host runs Windows 2003 Server as a guest, in case this > matters. Since you're running Debian's implementation of xen, probably you should ask on a Debian list, where those knowledgeable about Debian hang out and can help. Fedora's support tools are quite different from Debian's. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From berrange at redhat.com Wed Oct 17 00:07:48 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 17 Oct 2007 01:07:48 +0100 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> Message-ID: <20071017000748.GS30866@redhat.com> On Mon, Oct 15, 2007 at 11:09:27AM +1000, Amos Shapira wrote: > Hello, > > I'm trying to install Fedora 7 under Debian Etch running on Intel Xeon 3050 > (i.e. with hardware virtualization) and x86_64 kernel (2.6.18-4-xen-amd64) > with 4Gb RAM (the hardware supports up to 8Gb). > > I configured it this way: > > kernel = '/usr/lib/xen-3.0.3-1/boot/hvmloader' > builder = 'linux' ^^^^^^^ This needs to be 'hvm' since the rest of your config file is for an HVM guest. > memory = '256' > name = 'fc7-01' > vif = ['type=ioemu, bridge=xenbr0'] > disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] > cdrom = 'file://root/iso/fc7/x86_64/boot.iso' > device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' > ne2000='0' > boot='d' > sdl='1' Or you need to configure it to be a paravirt guest - ie point the 'kernel' param to the Xen kernel & get rid of the cdrom & device_model args. 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 amos.shapira at gmail.com Wed Oct 17 00:53:28 2007 From: amos.shapira at gmail.com (Amos Shapira) Date: Wed, 17 Oct 2007 10:53:28 +1000 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <20071017000748.GS30866@redhat.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> <20071017000748.GS30866@redhat.com> Message-ID: <9c2cca270710161753r7c2f510ch987245b37bcd44b8@mail.gmail.com> On 17/10/2007, Daniel P. Berrange wrote: > > On Mon, Oct 15, 2007 at 11:09:27AM +1000, Amos Shapira wrote: > > Hello, > > > > I'm trying to install Fedora 7 under Debian Etch running on Intel Xeon > 3050 > > (i.e. with hardware virtualization) and x86_64 kernel ( > 2.6.18-4-xen-amd64) > > with 4Gb RAM (the hardware supports up to 8Gb). > > > > I configured it this way: > > > > kernel = '/usr/lib/xen-3.0.3-1/boot/hvmloader' > > builder = 'linux' > > ^^^^^^^ > > This needs to be 'hvm' since the rest of your config file > is for an HVM guest. OK, thanks. > memory = '256' > > name = 'fc7-01' > > vif = ['type=ioemu, bridge=xenbr0'] > > disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] > > cdrom = 'file://root/iso/fc7/x86_64/boot.iso' > > device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' > > ne2000='0' > > boot='d' > > sdl='1' > > > Or you need to configure it to be a paravirt guest - ie point the 'kernel' > param to the Xen kernel & get rid of the cdrom & device_model args. Does this mean I have to get hold of a different kernel for FC7 which is paravirtualized? Can you help me find such a kernel or do I have to compile one myself? Is this the "kernel-xen" package or is kernel-xen intended to be used for Dom0 (i.e. when fc7 is the host, not the guest)? Thanks, --Amos -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Oct 17 01:01:00 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 17 Oct 2007 02:01:00 +0100 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <9c2cca270710161753r7c2f510ch987245b37bcd44b8@mail.gmail.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> <20071017000748.GS30866@redhat.com> <9c2cca270710161753r7c2f510ch987245b37bcd44b8@mail.gmail.com> Message-ID: <20071017010100.GA14015@redhat.com> On Wed, Oct 17, 2007 at 10:53:28AM +1000, Amos Shapira wrote: > On 17/10/2007, Daniel P. Berrange wrote: > > > > On Mon, Oct 15, 2007 at 11:09:27AM +1000, Amos Shapira wrote: > > > Hello, > > > > > > I'm trying to install Fedora 7 under Debian Etch running on Intel Xeon > > 3050 > > > (i.e. with hardware virtualization) and x86_64 kernel ( > > 2.6.18-4-xen-amd64) > > > with 4Gb RAM (the hardware supports up to 8Gb). > > > > > > I configured it this way: > > > > > > kernel = '/usr/lib/xen-3.0.3-1/boot/hvmloader' > > > builder = 'linux' > > > > ^^^^^^^ > > > > This needs to be 'hvm' since the rest of your config file > > is for an HVM guest. > > > OK, thanks. > > > memory = '256' > > > name = 'fc7-01' > > > vif = ['type=ioemu, bridge=xenbr0'] > > > disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] > > > cdrom = 'file://root/iso/fc7/x86_64/boot.iso' > > > device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' > > > ne2000='0' > > > boot='d' > > > sdl='1' > > > > > > Or you need to configure it to be a paravirt guest - ie point the 'kernel' > > param to the Xen kernel & get rid of the cdrom & device_model args. > > > Does this mean I have to get hold of a different kernel for FC7 which is > paravirtualized? Yes. > Can you help me find such a kernel or do I have to compile one myself? > Is this the "kernel-xen" package or is kernel-xen intended to be used for > Dom0 (i.e. when fc7 is the host, not the guest)? For the purposes of installing a brand new paravirt guest use the kernel and initrd files from the directory '$TREE/images/xen/', where $TREE is the mounted CDROM image, or Fedora HTTP download site. Once installation is complete, remove the kernel & ramdisk from the guest config and add bootloader="/usr/bin/pygrub" 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 amos.shapira at gmail.com Wed Oct 17 01:48:28 2007 From: amos.shapira at gmail.com (Amos Shapira) Date: Wed, 17 Oct 2007 11:48:28 +1000 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <20071017010100.GA14015@redhat.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> <20071017000748.GS30866@redhat.com> <9c2cca270710161753r7c2f510ch987245b37bcd44b8@mail.gmail.com> <20071017010100.GA14015@redhat.com> Message-ID: <9c2cca270710161848j522bc6ecr660a9455021d42bb@mail.gmail.com> On 17/10/2007, Daniel P. Berrange wrote: > > > Does this mean I have to get hold of a different kernel for FC7 which is > > paravirtualized? > > Yes. > > > Can you help me find such a kernel or do I have to compile one myself? > > Is this the "kernel-xen" package or is kernel-xen intended to be used > for > > Dom0 (i.e. when fc7 is the host, not the guest)? > > For the purposes of installing a brand new paravirt guest use the kernel > and initrd files from the directory '$TREE/images/xen/', where $TREE is > the mounted CDROM image, or Fedora HTTP download site. Once installation > is complete, remove the kernel & ramdisk from the guest config and add > bootloader="/usr/bin/pygrub" OK, I got the files from http://mirror.bytemark.co.uk/fedora/linux/releases/7/Fedora/x86_64/os/images/xen/ and put them both under /boot of the host (Debian) and the guest (FC7) and used the following config file: kernel = '/boot/fc7-xen-vmlinuz' ramdisk = '/boot/fc7-xen-initrd.img' memory = 256 name = 'fc7-01' root = '/dev/hda1 ro' vif = ['type=ioemu, bridge=xenbr0'] disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] cdrom = 'file://root/iso/fc7/i386/boot.iso' device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' boot='d' sdl='1' And it seems to run - device started, "xm list" lists it at "blocked" state, xend.log file ends like: [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices irq. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices pci. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices ioports. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices tap. [2007-10-17 21:44:29 xend 2358] DEBUG (__init__:1072) Waiting for devices vtpm. [2007-10-17 21:44:29 xend 2358] INFO (__init__:1072) Domain fc7-01 (36) unpaused. But I don't get any console window and don't see how to reach the console. Just in case this is relevant - the Xen machine is a headless rack-mounted box in our machine room, no local desktop. I open ssh to it with X11 forwarding and manage to run VNC viewer into the console of the Windows Xen guest. Thanks very much for your help. --Amos -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Oct 17 01:50:34 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 17 Oct 2007 02:50:34 +0100 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <9c2cca270710161848j522bc6ecr660a9455021d42bb@mail.gmail.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> <20071017000748.GS30866@redhat.com> <9c2cca270710161753r7c2f510ch987245b37bcd44b8@mail.gmail.com> <20071017010100.GA14015@redhat.com> <9c2cca270710161848j522bc6ecr660a9455021d42bb@mail.gmail.com> Message-ID: <20071017015034.GB14015@redhat.com> On Wed, Oct 17, 2007 at 11:48:28AM +1000, Amos Shapira wrote: > On 17/10/2007, Daniel P. Berrange wrote: > > > > > Does this mean I have to get hold of a different kernel for FC7 which is > > > paravirtualized? > > > > Yes. > > > > > Can you help me find such a kernel or do I have to compile one myself? > > > Is this the "kernel-xen" package or is kernel-xen intended to be used > > for > > > Dom0 (i.e. when fc7 is the host, not the guest)? > > > > For the purposes of installing a brand new paravirt guest use the kernel > > and initrd files from the directory '$TREE/images/xen/', where $TREE is > > the mounted CDROM image, or Fedora HTTP download site. Once installation > > is complete, remove the kernel & ramdisk from the guest config and add > > bootloader="/usr/bin/pygrub" > > > OK, I got the files from > http://mirror.bytemark.co.uk/fedora/linux/releases/7/Fedora/x86_64/os/images/xen/ > and put them both under /boot of the host (Debian) and the guest (FC7) and > used the following config file: > > kernel = '/boot/fc7-xen-vmlinuz' > ramdisk = '/boot/fc7-xen-initrd.img' > memory = 256 > name = 'fc7-01' > root = '/dev/hda1 ro' > vif = ['type=ioemu, bridge=xenbr0'] > disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] > cdrom = 'file://root/iso/fc7/i386/boot.iso' > device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' > boot='d' > sdl='1' Change this to 'sdl=0' and add 'vnc=1'. This will make Xen start a VNC server in the Dom0 host to which you can connect & view the guest installer. 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 amos.shapira at gmail.com Wed Oct 17 06:27:53 2007 From: amos.shapira at gmail.com (Amos Shapira) Date: Wed, 17 Oct 2007 16:27:53 +1000 Subject: [Fedora-xen] installing FC7 under Debian Etch In-Reply-To: <20071017015034.GB14015@redhat.com> References: <9c2cca270710141809t287053b3p98e4c6adc0830b96@mail.gmail.com> <20071017000748.GS30866@redhat.com> <9c2cca270710161753r7c2f510ch987245b37bcd44b8@mail.gmail.com> <20071017010100.GA14015@redhat.com> <9c2cca270710161848j522bc6ecr660a9455021d42bb@mail.gmail.com> <20071017015034.GB14015@redhat.com> Message-ID: <9c2cca270710162327j5c00e525ja75112bcde5224a2@mail.gmail.com> On 17/10/2007, Daniel P. Berrange wrote: > > Change this to 'sdl=0' and add 'vnc=1'. This will make Xen start a > VNC server in the Dom0 host to which you can connect & view the guest > installer. It didn't start anything that listens on any port on the Dom0 machine. I added "vncviewer=1" and that started a vncviewer but I'm not clear how am I supposed to connect to it. Anyway, from more googl'ing I was reminded about "xm console" and attached below is the output from when I invoke it - it looks like the guest kernel doesn't find some important devices and then just sits there without completing the boot process. >From Googl'ing the error it sounds like the initrd (or the /lib/modules directory on the Xen Guest's filesystem?) is missing some xen-related device modules but installing kernel-xen-2.6.20-2925.9.fc7.x86_64.rpmand trying to use the kernel and initrd image from there just causes the guest to boot in a loop too fast and causing Xen to just destroy it. What could be the problem now? Here is my current config file: kernel = '/boot/fc7-xen-vmlinuz' ramdisk = '/boot/fc7-xen-initrd.img' memory = 256 name = 'fc7-01' root = '/dev/hda ro' vif = ['type=ioemu, bridge=xenbr0'] disk = ['phy:/dev/xen/fc7-01,ioemu:hda,w'] cdrom = 'file://root/iso/fc7/i386/boot.iso' device_model='/usr/lib/xen-3.0.3-1/bin/qemu-dm' boot='d' Thanks, --Amos # xm console 46 Linux version 2.6.20-2925.9.fc7xen ( kojibuilder at xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 09:29:36 EDT 2007 Command line: root=/dev/hda ro BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000010800000 (usable) end_pfn_map = 67584 Zone PFN ranges: DMA 0 -> 67584 DMA32 67584 -> 67584 Normal 67584 -> 67584 early_node_map[1] active PFN ranges 0: 0 -> 67584 No mptable found. PERCPU: Allocating 26368 bytes of per cpu data Built 1 zonelists. Total pages: 65427 Kernel command line: root=/dev/hda ro Initializing CPU#0 PID hash table entries: 1024 (order: 10, 8192 bytes) Xen reported: 2133.408 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) Software IO TLB disabled Memory: 244900k/270336k available (2207k kernel code, 16928k reserved, 1347k data, 192k init) Calibrating delay using timer specific routine.. 5335.94 BogoMIPS (lpj=10671882)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: 256 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU: Processor Core ID: 0 (SMP-)alternatives turned off 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 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: 2048 (order: 2, 16384 bytes) TCP established hash table entries: 8192 (order: 6, 262144 bytes) TCP bind hash table entries: 4096 (order: 5, 131072 bytes) TCP: Hash tables configured (established 8192 bind 4096) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7233k freed IA-32 Microcode Update Driver: v1.14-xen audit: initializing netlink socket (disabled) audit(1192635835.496:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 512 (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 XENBUS: Device with no driver: device/vbd/768 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 938k -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Wed Oct 17 06:41:30 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 17 Oct 2007 07:41:30 +0100 Subject: [Fedora-xen] Follow up to "No agpgart? What?" In-Reply-To: <1192573575.3438.2.camel@prophead.corp.publichost.com> References: <1192573575.3438.2.camel@prophead.corp.publichost.com> Message-ID: <4715AE9A.90401@redhat.com> Rick Stevens wrote: > (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) > (WW) intel(0): /dev/agpgart is either not available, or no memory is > available > for allocation. Using pre-allocated memory only. > (==) intel(0): VideoRam: 7676 KB > (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded > (II) intel(0): Allocating 255 scanlines for pixmap cache > (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too > low? > (EE) intel(0): Couldn't allocate video memory Are you starting X immediately after booting, or some time later? I don't think the agpgart message is relevant. What I think is happening is that the driver cannot allocate enough videoram, or perhaps cannot allocate it contiguously in physical RAM or something along those lines. In any case you should read the i810 manpage (`man i810') and see if any of the many tips / configuration settings in that page makes any difference at all. (Particularly play with increasing or decreasing VideoRam, and disabling DRI). If that doesn't help then it's probably a general Xen problem, so asking about this upstream on xen-users[1] or xen-devel[2] lists could help. In any case, if you find a way to fix it please let us know. Rich. [1] http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users [2] http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel -- 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 Wed Oct 17 06:42:40 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 17 Oct 2007 07:42:40 +0100 Subject: [Fedora-xen] xmlrpc python and session login In-Reply-To: <20071016131748.M75YO.79255.root@fepweb03> References: <20071016131748.M75YO.79255.root@fepweb03> Message-ID: <4715AEE0.9020903@redhat.com> slbubba at charter.net wrote: > Folks; > > I'm trying to see what's available (working) in xen for remote management. I thought I'd try something simple using xmlrpclib and python. I tried establishing a session and logging in but I'm not getting anywhere fast. It appears that either xend isn't functional in this area or something (perhaps) is not set correctly in the xend-config.sxp file. Has anyone been able to login to a xen system successfully? Are any of the facilities in the xend-config file functional with this RH version of xend? > > > OS: RHEL5.0 latest update > kernel: 2.6.18-8.1.14.el5xen > > RPM's: xen-libs-3.0.3-25.0.4.el5 > xen-3.0.3-25.0.4.el5 > python-2.4.3-19.el5 > ----------- > python >>>> import xmlrpclib >>>> xen = xmlrpclib.Server("http://mysys.com:8006") >>>> asess = xen.session.login_with_password("batman", "monkeypus") > > socket.error: (111, 'Connection refused') Take a look at http://libvirt.org/ Remote management works fine, there are command line tools, and interfaces to many different languages. 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 rstevens at internap.com Wed Oct 17 16:29:24 2007 From: rstevens at internap.com (Rick Stevens) Date: Wed, 17 Oct 2007 09:29:24 -0700 Subject: [Fedora-xen] Follow up to "No agpgart? What?" In-Reply-To: <4715AE9A.90401@redhat.com> References: <1192573575.3438.2.camel@prophead.corp.publichost.com> <4715AE9A.90401@redhat.com> Message-ID: <1192638564.6334.13.camel@prophead.corp.publichost.com> On Wed, 2007-10-17 at 07:41 +0100, Richard W.M. Jones wrote: > Rick Stevens wrote: > > (EE) GARTInit: Unable to open /dev/agpgart (No such file or directory) > > (WW) intel(0): /dev/agpgart is either not available, or no memory is > > available > > for allocation. Using pre-allocated memory only. > > (==) intel(0): VideoRam: 7676 KB > > (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded > > (II) intel(0): Allocating 255 scanlines for pixmap cache > > (EE) intel(0): Failed to allocate framebuffer. Is your VideoRAM set too > > low? > > (EE) intel(0): Couldn't allocate video memory > > Are you starting X immediately after booting, or some time later? Standard time. All I did was boot the xen0 kernel instead of the standard one. It works on every other machine I have, just not this one. > I don't think the agpgart message is relevant. What I think is > happening is that the driver cannot allocate enough videoram, or perhaps > cannot allocate it contiguously in physical RAM or something along those > lines. I think it is. The standard kernel does fire up /dev/agpgart and it does allocate memory: (II) intel(0): Kernel reported 488960 total, 1 used (II) intel(0): I830CheckAvailableMemory: 1955836 kB available (==) intel(0): VideoRam: 262144 KB <<<<-----NOTE! (EE) intel(0): [dri] I830CheckDRIAvailable failed: glx not loaded (II) intel(0): Allocating 5472 scanlines for pixmap cache (II) intel(0): Memory allocation layout: (II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB) (II) intel(0): 0x00020000-0x00029fff: HW cursors (40 kB) (II) intel(0): 0x0002a000-0x00031fff: logical 3D context (32 kB) (II) intel(0): 0x00032000-0x00041fff: exa G965 state buffer (64 kB) (II) intel(0): 0x00050000-0x02147fff: front buffer (33760 kB) (II) intel(0): 0x0077f000: end of stolen memory (II) intel(0): 0x02148000-0x02157fff: xaa scratch (64 kB) (II) intel(0): 0x10000000: end of aperture Same xorg.conf file. > In any case you should read the i810 manpage (`man i810') and see if any > of the many tips / configuration settings in that page makes any > difference at all. (Particularly play with increasing or decreasing > VideoRam, and disabling DRI). I'll do that, but under the standard kernel it allocates video RAM just fine. It doesn't under the xen0 kernel. UPDATE: Just tried it. I did screw up and just say "256" rather than "256MB". /dev/agpgart still doesn't exist. The only change I see is a warning in the log: (WW) intel(0): VideoRam configuration found, which is no longer recommended. (II) intel(0): Continuing with default 262144kB VideoRam instead of 256 kB. The 262144kB bit is the same as under the regular kernel but /dev/agpart still doesn't exist. This is more and more a Xen kernel issue. > If that doesn't help then it's probably a general Xen problem, so asking > about this upstream on xen-users[1] or xen-devel[2] lists could help. Yeah, I'm thinking about that. > In any case, if you find a way to fix it please let us know. I'll keep you posted. Side note to Rich...it'd be nice if the list was in your To: as opposed to being in the Cc:. That's why I posted directly to you last time... I tend to use "Reply" not "Reply All". ---------------------------------------------------------------------- - Rick Stevens, Principal Engineer rstevens at internap.com - - CDN Systems, Internap, Inc. http://www.internap.com - - - - Lottery: A tax on people who are bad at math. - ---------------------------------------------------------------------- From rjones at redhat.com Wed Oct 17 17:08:43 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 17 Oct 2007 18:08:43 +0100 Subject: [Fedora-xen] Follow up to "No agpgart? What?" In-Reply-To: <1192638564.6334.13.camel@prophead.corp.publichost.com> References: <1192573575.3438.2.camel@prophead.corp.publichost.com> <4715AE9A.90401@redhat.com> <1192638564.6334.13.camel@prophead.corp.publichost.com> Message-ID: <4716419B.5000609@redhat.com> Rick Stevens wrote: > I think it is. The standard kernel does fire up /dev/agpgart and it > does allocate memory: [...] > I'll do that, but under the standard kernel it allocates video RAM just > fine. It doesn't under the xen0 kernel. It's not really fair to compare Linux running under Xen with Linux running on bare-metal. Linux on baremetal has complete, unhindered access to physical memory, and can hand out access to physical memory mappings to user processes as well (eg. X). Under Xen the situation is somewhat different in that the hypervisor controls physical memory and hands it out to all domains. The "privileged" dom0 has direct access to device registers but not necessarily to all physical memory. > UPDATE: Just tried it. I did screw up and just say "256" rather than > "256MB". /dev/agpgart still doesn't exist. The only change I see is a > warning in the log: > > (WW) intel(0): VideoRam configuration found, which is no longer > recommended. > (II) intel(0): Continuing with default 262144kB VideoRam instead of 256 > kB. > > The 262144kB bit is the same as under the regular kernel but /dev/agpart > still doesn't exist. This is more and more a Xen kernel issue. On my Xen desktop which is running X just fine there is no /dev/agpart. >> If that doesn't help then it's probably a general Xen problem, so asking >> about this upstream on xen-users[1] or xen-devel[2] lists could help. > > Yeah, I'm thinking about that. > >> In any case, if you find a way to fix it please let us know. > > I'll keep you posted. > > Side note to Rich...it'd be nice if the list was in your To: as opposed > to being in the Cc:. That's why I posted directly to you last time... > I tend to use "Reply" not "Reply All". /me blames my crappy MUA. Thunderbird sucks, mutt rules. 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 asraikhn at gmail.com Thu Oct 18 12:59:58 2007 From: asraikhn at gmail.com (Asrai khn) Date: Thu, 18 Oct 2007 17:59:58 +0500 Subject: [Fedora-xen] domU fail to start with error Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route Message-ID: <5f0f8dba0710180559g6c9e96f9m9c98462829a5c821@mail.gmail.com> We have recently upgraded our dom0 to fedora 7 and it was working fine from last couple of days, today on of domU crashed and when i tries to start it fails at error ... xm create -c /etc/xen/vm3.cfg Error: Device 0 (vif) could not be connected. /etc/xen/scripts/vif-route failed in end i have rebooted the host (dom0) and all vms started fine. We never got this sort of problem at FC6. Any help in this regards will be highly appreciated. Askar. -------------- next part -------------- An HTML attachment was scrubbed... URL: From takeshi at uematsu.ws Thu Oct 18 15:45:43 2007 From: takeshi at uematsu.ws (=?ISO-2022-JP?B?GyRCPyI+PjdyGyhC?=) Date: Fri, 19 Oct 2007 00:45:43 +0900 Subject: [Fedora-xen] can't setup virt-install Message-ID: <520fa66b0710180845m3eff15ecx7ec494c036a5cb92@mail.gmail.com> I installed xen domainU using by virt-install command and kickstart. The option of virt-install is following. virt-install -p --ram=256 --name="host1" --file="/var/lib/xen/images/host1" --file-size=5 --nographics --location=http://192.168.1.10/fedora/ --extra-args="console=xvc0 ip=192.168.1.100 netmask=255.255.255.0 gateway=192.168.1.1 dns=192.168.1.10 ks=http://192.168.1.10/fedora/ks.cfg " but error occured while installing domainU. Messages is as following. | Exception Occurred | Traceback (most recent call first): | File "/usr/lib/anaconda/text.py", line 510, in run | if anaconda.isKickstart and not anaconda.id.instClass.ksdata.interactive: | File "/usr/bin/anaconda", line 955, in | | anaconda.intf.run(anaconda) | AttributeError: DefaultInstall instance | has no attribute 'ksdata' If I don't use kickstart file , setup completed. I think that it is no problem in kickstart file(ks.cfg). If you have any infomation about this case, let me know detail. ks.cfg # Kickstart file automatically generated by anaconda. install url --url http://192.168.1.10/fedora/ lang ja_JP.UTF-8 network --device eth0 --bootproto static --ip 192.168.1.100 --netmask 255.255.255.0 --gateway 192.168.1.1 --nameserver 192.168.1.10 --hostname host1.e-uematsu.net rootpw --iscrypted $1$o69YV.yo$rMQTUwIz1CH6HZXlfkQ8Y0 firewall --enabled --port=22:tcp authconfig --enableshadow --enablemd5 selinux --enforcing timezone Asia/Tokyo bootloader --location=mbr --driveorder=xvda --append="console=xvc0" # The following is the partition information you requested # Note that any partitions you deleted are not expressed # here so unless you clear all partitions first, this is # not guaranteed to work clearpart --linux --drives=xvda part /boot --fstype ext3 --size=100 --ondisk=xvda part pv.2 --size=0 --grow --ondisk=xvda volgroup VolGroup00 --pesize=32768 pv.2 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=272 --grow --maxsize=544 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow %packages @admin-tools @editors @japanese-support @text-internet @core @base @hardware-support pax --- Takeshi Uematsu. From Dustin.Henning at prd-inc.com Thu Oct 18 19:59:42 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Thu, 18 Oct 2007 15:59:42 -0400 Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? Message-ID: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> I have a Core 2 Quad with 8 GiB of RAM. When I installed FC7 (2.6.22.9-91.fc7), it only detected 4GiB (BIOS detects 8GiB). I added mem=8G to the kernel line in grub.conf, and then Gnome System Monitor showed 7.1GiB (vs I think 4.0). I then changed that to mem=16G, and the Gnome System Monitor shows 7.8 GiB. /proc/meminfo MemTotal shows 8201832kB, so that seems about right. That said, the problem seems to be solved for the kernel mentioned above. However, and this is why I am submitting this to the fedora-xen mailing list, the virtualization kernel (2.6.20-2936.fc7xen) shows 3.1GiB in Gnome System Monitor and 3214456KB in /proc/meminfo MemTotal. Additionally, "xm info" shows 3327 for total memory, so the problem isn't that it is there but not assigned to dom0. I tried the same thing with grub.conf for xen, but it did not work, mem=8G and mem=16G had no effect (this is shown to be a valid parameter in the Xen manual at [http://tx.downloads.xensource.com/downloads/docs/user/#SECTION0413000000000 0000000]). Since it didn't work on the kernel line, I tried it on the module (vmlinuz) line that has the other FC grub arguments, and that did not work either; then I tried placing that on both lines (also to no avail). I also tried dom0_mem=8G on the kernel line, and that caused a kernel panic stating not enough physical memory (got the same thing with dom0_mem=4G). Finally, as a side note, /proc/meminfo VmallocTotal shows 34359738367kB regardless of all of the above, and I don't know if that is normal or not (swap partition is 2GiB). Please let me know if you have fedora 7 x86_64 xen working with >4GB of memory, if there is any additional information that might be helpful, or if you have any suggestions I might try in order to resolve this. Thank you, Dustin From pi+lists at panelsix.com Fri Oct 19 13:37:26 2007 From: pi+lists at panelsix.com (Pim van Riezen) Date: Fri, 19 Oct 2007 15:37:26 +0200 Subject: [Fedora-xen] FC6 live migrate weirdness Message-ID: <86201F0A-4482-4B66-B94A-33DB8D880509@panelsix.com> Hello, When trying a live migrate, I get the following error: [2007-10-19 15:33:05 xend 4839] DEBUG (XendCheckpoint:83) [xc_save]: / usr/lib64/xen/bin/xc_save 22 45 0 0 1 [2007-10-19 15:33:05 xend 4839] INFO (XendCheckpoint:239) Couldn't enable shadow mode: 12 [2007-10-19 15:33:05 xend 4839] INFO (XendCheckpoint:239) Save exit rc=1 [2007-10-19 15:33:05 xend 4839] ERROR (XendCheckpoint:106) Save failed on domain vps023 (45). Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/ XendCheckpoint.py", line 100, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/lib64/python2.4/site-packages/xen/xend/ XendCheckpoint.py", line 227, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib64/xen/bin/xc_save 22 45 0 0 1 failed [root at yankee ~]# free total used free shared buffers cached Mem: 6286336 1267508 5018828 0 310712 202928 -/+ buffers/cache: 753868 5532468 Swap: 8385920 220 8385700 [root at yankee ~]# uname -a Linux yankee.xl-is.net 2.6.20-1.2962.fc6xen #1 SMP Tue Jun 19 19:10:51 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux Seems I have plenty of RAM left. What's the deal? Cheers, Pi From dlbewley at lib.ucdavis.edu Fri Oct 19 15:46:19 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 19 Oct 2007 08:46:19 -0700 (PDT) Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? In-Reply-To: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> Message-ID: <1701384668.50351192808779750.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Dustin Henning" wrote: > I have a Core 2 Quad with 8 GiB of RAM. When I installed FC7 > (2.6.22.9-91.fc7), it only detected 4GiB (BIOS detects 8GiB). I > added > mem=8G to the kernel line in grub.conf, and then Gnome System Monitor > showed > 7.1GiB (vs I think 4.0). I then changed that to mem=16G, and the > Gnome > System Monitor shows 7.8 GiB. /proc/meminfo MemTotal shows 8201832kB, > so > that seems about right. That said, the problem seems to be solved for > the > kernel mentioned above. > However, and this is why I am submitting this to the fedora-xen > mailing list, the virtualization kernel (2.6.20-2936.fc7xen) shows > 3.1GiB in > Gnome System Monitor and 3214456KB in /proc/meminfo MemTotal. > Additionally, > "xm info" shows 3327 for total memory, so the problem isn't that it is > there > but not assigned to dom0. I tried the same thing with grub.conf for > xen, > but it did not work, mem=8G and mem=16G had no effect (this is shown > to be a > valid parameter in the Xen manual at > [http://tx.downloads.xensource.com/downloads/docs/user/#SECTION0413000000000 > 0000000]). Since it didn't work on the kernel line, I tried it on > the > module (vmlinuz) line that has the other FC grub arguments, and that > did not > work either; then I tried placing that on both lines (also to no > avail). I > also tried dom0_mem=8G on the kernel line, and that caused a kernel > panic > stating not enough physical memory (got the same thing with > dom0_mem=4G). > Finally, as a side note, /proc/meminfo VmallocTotal shows > 34359738367kB regardless of all of the above, and I don't know if that > is > normal or not (swap partition is 2GiB). Please let me know if you > have > fedora 7 x86_64 xen working with >4GB of memory, if there is any > additional > information that might be helpful, or if you have any suggestions I > might > try in order to resolve this. Thank you, > Dustin I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this: Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux # grep 'model name' /proc/cpuinfo model name : AMD Opteron(tm) Processor 852 model name : AMD Opteron(tm) Processor 852 model name : AMD Opteron(tm) Processor 852 model name : AMD Opteron(tm) Processor 852 # grep Total /proc/meminfo MemTotal: 13335552 kB SwapTotal: 5261240 kB VmallocTotal: 34359738367 kB # xm info |grep total total_memory : 16319 I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0. On an identical server running RHEL with no xen and I see something a bit different: Red Hat Enterprise Linux AS release 4 (Nahant Update 5) Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux # grep Total /proc/meminfo MemTotal: 16359284 kB HighTotal: 0 kB LowTotal: 16359284 kB SwapTotal: 5261240 kB VmallocTotal: 536870911 kB HugePages_Total: 0 Not sure if that was helpful. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From Dustin.Henning at prd-inc.com Fri Oct 19 17:29:38 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 19 Oct 2007 13:29:38 -0400 Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? References: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> <1701384668.50351192808779750.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <008301c81275$a02df860$e089e920$@Henning@prd-inc.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dale Bewley >Sent: Friday, October 19, 2007 11:46 >To: fedora-xen >Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB? > >I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this: > >Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > ># grep 'model name' /proc/cpuinfo >model name : AMD Opteron(tm) Processor 852 >model name : AMD Opteron(tm) Processor 852 >model name : AMD Opteron(tm) Processor 852 >model name : AMD Opteron(tm) Processor 852 > ># grep Total /proc/meminfo >MemTotal: 13335552 kB >SwapTotal: 5261240 kB >VmallocTotal: 34359738367 kB > ># xm info |grep total >total_memory : 16319 > >I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0. > > >On an identical server running RHEL with no xen and I see something a bit different: > >Red Hat Enterprise Linux AS release 4 (Nahant Update 5) >Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > ># grep Total /proc/meminfo >MemTotal: 16359284 kB >HighTotal: 0 kB >LowTotal: 16359284 kB >SwapTotal: 5261240 kB >VmallocTotal: 536870911 kB >HugePages_Total: 0 > >Not sure if that was helpful. >-- >Dale Bewley - Unix Administrator - Shields Library - UC Davis >GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 Dale, That could be very helpful, or it might just get someone to blame Intel. Either way, thanks, now I at least know that it should work and I can try to determine why it isn't. As for the MemTotal, you are correct on why it is 13 instead of 16. However, if you shut down one of those domU's, the memory wouldn't necessarily be automatically re-assigned to dom0, and /proc/meminfo is based on what is assigned to dom0. I think "xm info" would be the correct way to see the detected memory in the system once domU's are created or if dom0 isn't assigned all memory. There may be other ways. Thanks, Dustin From Dustin.Henning at prd-inc.com Fri Oct 19 17:34:34 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 19 Oct 2007 13:34:34 -0400 Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? References: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> <1701384668.50351192808779750.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <008401c81276$509879f0$f1c96dd0$@Henning@prd-inc.com> >-----Original Message----- >From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dale Bewley >Sent: Friday, October 19, 2007 11:46 >To: fedora-xen >Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB? > >I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this: > >Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > ># grep 'model name' /proc/cpuinfo >model name : AMD Opteron(tm) Processor 852 >model name : AMD Opteron(tm) Processor 852 >model name : AMD Opteron(tm) Processor 852 >model name : AMD Opteron(tm) Processor 852 > ># grep Total /proc/meminfo >MemTotal: 13335552 kB >SwapTotal: 5261240 kB >VmallocTotal: 34359738367 kB > ># xm info |grep total >total_memory : 16319 > >I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0. > > >On an identical server running RHEL with no xen and I see something a bit different: > >Red Hat Enterprise Linux AS release 4 (Nahant Update 5) >Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > ># grep Total /proc/meminfo >MemTotal: 16359284 kB >HighTotal: 0 kB >LowTotal: 16359284 kB >SwapTotal: 5261240 kB >VmallocTotal: 536870911 kB >HugePages_Total: 0 > >Not sure if that was helpful. >-- >Dale Bewley - Unix Administrator - Shields Library - UC Davis >GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 Dale, Could you tell me if you passed any arguments to the installer during your initial install? Also, can you show me the appropriate portion of your grub.conf? I would like to see if maybe it is different than mine even though they are both pre-packaged installs. I had a machine with 2.6.20-2931.fc7xen, so I copied that to the machine in question, and it also only shows 3.1GiB for me. I compared the config files for that kernel and the one I was using, and they are identical (minus version and date comment lines), so that was as I expected, but it makes it less likely that my problem is a version problem and more likely that something else is haywire. Thanks, Dustin From stephen.fierbaugh at pbti.org Mon Oct 22 16:41:03 2007 From: stephen.fierbaugh at pbti.org (Fierbaugh, Stephen) Date: Mon, 22 Oct 2007 11:41:03 -0500 Subject: [Fedora-xen] Re: Fedora-xen Digest, Vol 23, Issue 15 In-Reply-To: <20071020160010.A951A73141@hormel.redhat.com> References: <20071020160010.A951A73141@hormel.redhat.com> Message-ID: <471CD29F.1010604@pbti.org> unsubscribe fedora-xen-request at redhat.com wrote: > 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: 64-Bit RAM Detection >4GB? (Dustin Henning) > 2. RE: 64-Bit RAM Detection >4GB? (Dustin Henning) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 19 Oct 2007 13:29:38 -0400 > From: "Dustin Henning" > Subject: RE: [Fedora-xen] 64-Bit RAM Detection >4GB? > To: > Message-ID: <008301c81275$a02df860$e089e920$@Henning at prd-inc.com> > Content-Type: text/plain; charset="utf-8" > > >> -----Original Message----- >> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dale Bewley >> Sent: Friday, October 19, 2007 11:46 >> To: fedora-xen >> Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB? >> >> I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this: >> >> Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux >> >> # grep 'model name' /proc/cpuinfo >> model name : AMD Opteron(tm) Processor 852 >> model name : AMD Opteron(tm) Processor 852 >> model name : AMD Opteron(tm) Processor 852 >> model name : AMD Opteron(tm) Processor 852 >> >> # grep Total /proc/meminfo >> MemTotal: 13335552 kB >> SwapTotal: 5261240 kB >> VmallocTotal: 34359738367 kB >> >> # xm info |grep total >> total_memory : 16319 >> >> I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0. >> >> >> On an identical server running RHEL with no xen and I see something a bit different: >> >> Red Hat Enterprise Linux AS release 4 (Nahant Update 5) >> Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux >> >> # grep Total /proc/meminfo >> MemTotal: 16359284 kB >> HighTotal: 0 kB >> LowTotal: 16359284 kB >> SwapTotal: 5261240 kB >> VmallocTotal: 536870911 kB >> HugePages_Total: 0 >> >> Not sure if that was helpful. >> -- >> Dale Bewley - Unix Administrator - Shields Library - UC Davis >> GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 >> > > Dale, > That could be very helpful, or it might just get someone to blame Intel. Either way, thanks, now I at least know that it should work and I can try to determine why it isn't. As for the MemTotal, you are correct on why it is 13 instead of 16. However, if you shut down one of those domU's, the memory wouldn't necessarily be automatically re-assigned to dom0, and /proc/meminfo is based on what is assigned to dom0. I think "xm info" would be the correct way to see the detected memory in the system once domU's are created or if dom0 isn't assigned all memory. There may be other ways. Thanks, > Dustin > > > > > > ------------------------------ > > Message: 2 > Date: Fri, 19 Oct 2007 13:34:34 -0400 > From: "Dustin Henning" > Subject: RE: [Fedora-xen] 64-Bit RAM Detection >4GB? > To: > Message-ID: <008401c81276$509879f0$f1c96dd0$@Henning at prd-inc.com> > Content-Type: text/plain; charset="utf-8" > > >> -----Original Message----- >> From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dale Bewley >> Sent: Friday, October 19, 2007 11:46 >> To: fedora-xen >> Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB? >> >> I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this: >> >> Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux >> >> # grep 'model name' /proc/cpuinfo >> model name : AMD Opteron(tm) Processor 852 >> model name : AMD Opteron(tm) Processor 852 >> model name : AMD Opteron(tm) Processor 852 >> model name : AMD Opteron(tm) Processor 852 >> >> # grep Total /proc/meminfo >> MemTotal: 13335552 kB >> SwapTotal: 5261240 kB >> VmallocTotal: 34359738367 kB >> >> # xm info |grep total >> total_memory : 16319 >> >> I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0. >> >> >> On an identical server running RHEL with no xen and I see something a bit different: >> >> Red Hat Enterprise Linux AS release 4 (Nahant Update 5) >> Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux >> >> # grep Total /proc/meminfo >> MemTotal: 16359284 kB >> HighTotal: 0 kB >> LowTotal: 16359284 kB >> SwapTotal: 5261240 kB >> VmallocTotal: 536870911 kB >> HugePages_Total: 0 >> >> Not sure if that was helpful. >> -- >> Dale Bewley - Unix Administrator - Shields Library - UC Davis >> GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 >> > > Dale, > Could you tell me if you passed any arguments to the installer during your initial install? Also, can you show me the appropriate portion of your grub.conf? I would like to see if maybe it is different than mine even though they are both pre-packaged installs. I had a machine with 2.6.20-2931.fc7xen, so I copied that to the machine in question, and it also only shows 3.1GiB for me. I compared the config files for that kernel and the one I was using, and they are identical (minus version and date comment lines), so that was as I expected, but it makes it less likely that my problem is a version problem and more likely that something else is haywire. Thanks, > Dustin > > > > > > ------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > End of Fedora-xen Digest, Vol 23, Issue 15 > ****************************************** > -- Sincerely Yours, Stephen P. Fierbaugh Pioneer Bible Translators Pronounced: "Fire" as in hot, "Bah" as in humbug! Jesus wept. John 11:35 NIV -------------- next part -------------- An HTML attachment was scrubbed... URL: From jprats at cesca.es Tue Oct 23 08:11:53 2007 From: jprats at cesca.es (Jordi Prats) Date: Tue, 23 Oct 2007 10:11:53 +0200 Subject: [Fedora-xen] Re: Rootkit In-Reply-To: <2941460.47791193120370689.JavaMail.bob.smith@kolumbus.fi> References: <2941460.47791193120370689.JavaMail.bob.smith@kolumbus.fi> Message-ID: <471DACC9.6090900@cesca.es> About this discussion, chkrootkit are for live systems, isn't it? There's any tool to do rootkit analysis on a "dead" system? I'm thinking of check for rootkits on snapshots of the file system of a virtual machine to determine if the running virtual machine is compromised. Thanks, Jordi bob.smith at kolumbus.fi wrote: > Dave Burns kirjoitti: >> > >> While reading this thread it occurred to me that if disk drives >> had a >> > >> read-only switch, then systems would be uncrackable. >> >> Well, that would go a long way to make intrusion more difficult, but >> not impossible. Intruder just mounts something on top of your read >> only partition that looks a lot like your partition but with a few >> well chosen modifications. He then has to hide evidence of his trick, >> which would not be easy (at least for me!), but that's not to say it >> could not be done. In fact I have heard of a very similar approach >> being used (sort of the opposite - an innocuous partition mounted over >> a partition full of rootkit stuff to keep it hidden), though >> apparently the intruder had not perfected it yet, since the admin >> eventually figured out what was going on. >> >> > There are special filesystems ("unionfs" ?) >> > that redirect writes to a read-only file to a copy of the file in a >> > writable partition (I think). >> >> Yeah, but wouldn't that defeat the idea? Are you making it read only >> so that you know for sure it is good and can use it with confidence or >> so that you can easily recover your original files after getting >> (expletive deleted)? This "read-only" partition approach is only worth >> the trouble if it actually takes some capability away from the >> intruder. If the filesystem is read/write but your "originals" are >> read only, that only bothers the intruder if he actually wants to >> erase them. What does he want to erase? Log files, which do not belong >> on a read only filesystem in any case. >> >> You could use it for monitoring - if it was easy to do a check whether >> ps and lsof and other critical executables were actually on the >> read-only part of disk or had been modified. The utility that does the >> check had better be on the read only partition, but what do you use to >> check it? If you're totally hacked you can't be sure that the >> utilities that you execute are actually coming from that disk. You >> might be logged in to an emulator! Might as well use tripwire or aide >> and not bother with the read-onlyness. >> >> This has got me thinking. >> Dave >> >> -- >> fedora-list mailing list >> fedora-list at redhat.com >> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list >> > > Hi, I am glad you are discussing this, because there are issues to > ponder. > About hacking and cracking. A while back I had this idea, well a few > years back, but it was put aside because a university professor > disregarded it as useless. and maybe it is. > The idea was to create sort of(in some way) "encrypted and protected" > executables. This to be able to verify that an executable is what it > is(located on machine X, and compiled on machine x). Further, the > executable would be made so that it could not run on a system on which > it was not allowed to run. That was the basis of the idea. Purely > theoretical. How this could be achieved in reality is beyond my > current knowledgebase, but I am sure that someone else with more > knowledge in encryption and protection than me, could maybe analyse > this further. > (Sure, most machines are loaded with translators and script > interpreters like perl, and PHP and many others, which allows for > making quite much damage through scripting. ) > > Still, it could be something to think about. > best r > Bobo > > > > -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. 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 ...................................................................... From Dustin.Henning at prd-inc.com Tue Oct 23 17:02:40 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 23 Oct 2007 13:02:40 -0400 Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? In-Reply-To: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> References: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> Message-ID: <000001c81596$8587db10$90979130$@Henning@prd-inc.com> The grub installed with Fedora has a bug that causes xen (and sometimes other kernels) to detect the memory wrong. Bug URLs follow: xen-users mailing list archive: [url]http://lists.xensource.com/archives/html/xen-users/2007-08/msg00028.htm l[/url] Bugzilla: [url]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250299[/url] Theoretically, it could be argued that the BIOS is the problem and not grub, I mean, it sounds like Dale's machine was functional without this patch, and MSI isn't exactly a Linux Player. Either way, the patch suggested in those two locations resolved my issue. -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dustin Henning Sent: Thursday, October 18, 2007 16:00 To: fedora-xen at redhat.com Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? I have a Core 2 Quad with 8 GiB of RAM. When I installed FC7 (2.6.22.9-91.fc7), it only detected 4GiB (BIOS detects 8GiB). I added mem=8G to the kernel line in grub.conf, and then Gnome System Monitor showed 7.1GiB (vs I think 4.0). I then changed that to mem=16G, and the Gnome System Monitor shows 7.8 GiB. /proc/meminfo MemTotal shows 8201832kB, so that seems about right. That said, the problem seems to be solved for the kernel mentioned above. However, and this is why I am submitting this to the fedora-xen mailing list, the virtualization kernel (2.6.20-2936.fc7xen) shows 3.1GiB in Gnome System Monitor and 3214456KB in /proc/meminfo MemTotal. Additionally, "xm info" shows 3327 for total memory, so the problem isn't that it is there but not assigned to dom0. I tried the same thing with grub.conf for xen, but it did not work, mem=8G and mem=16G had no effect (this is shown to be a valid parameter in the Xen manual at [http://tx.downloads.xensource.com/downloads/docs/user/#SECTION0413000000000 0000000]). Since it didn't work on the kernel line, I tried it on the module (vmlinuz) line that has the other FC grub arguments, and that did not work either; then I tried placing that on both lines (also to no avail). I also tried dom0_mem=8G on the kernel line, and that caused a kernel panic stating not enough physical memory (got the same thing with dom0_mem=4G). Finally, as a side note, /proc/meminfo VmallocTotal shows 34359738367kB regardless of all of the above, and I don't know if that is normal or not (swap partition is 2GiB). Please let me know if you have fedora 7 x86_64 xen working with >4GB of memory, if there is any additional information that might be helpful, or if you have any suggestions I might try in order to resolve this. Thank you, Dustin From rjones at redhat.com Wed Oct 24 08:14:38 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 24 Oct 2007 09:14:38 +0100 Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? In-Reply-To: <000001c81596$8587db10$90979130$@Henning@prd-inc.com> References: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> <000001c81596$8587db10$90979130$@Henning@prd-inc.com> Message-ID: <471EFEEE.9040005@redhat.com> Dustin Henning wrote: > The grub installed with Fedora has a bug that causes xen (and sometimes > other kernels) to detect the memory wrong. > Bug URLs follow: > xen-users mailing list archive: > [url]http://lists.xensource.com/archives/html/xen-users/2007-08/msg00028.htm > l[/url] > Bugzilla: > [url]https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250299[/url] > > Theoretically, it could be argued that the BIOS is the problem and not grub, > I mean, it sounds like Dale's machine was functional without this patch, and > MSI isn't exactly a Linux Player. Either way, the patch suggested in those > two locations resolved my issue. Thanks for investigating this and posting the follow-up. I did read your original report, but had no idea how to help. 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 accarlson at gmail.com Wed Oct 24 17:21:05 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Wed, 24 Oct 2007 15:21:05 -0200 Subject: [Fedora-xen] Reinstall host, guest management Message-ID: Hi! I have a server with two guests (all Fedora 7). Each one has its own partition. host: /dev/hda1 guest1: /dev/hda2 guest2: /dev/hda3 Suppose that my host fail and I need to reinstall it. After reinstalling, how can I have access to my 2 guests using tools such as virt-manager/virsh/xm? or make them run as the were before the host failed. When I installed both guests, no configuration file was created in /etc/xen Thanks in advance. Regards, -- Augusto Castelan Carlson From berrange at redhat.com Wed Oct 24 18:25:16 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 24 Oct 2007 19:25:16 +0100 Subject: [Fedora-xen] Reinstall host, guest management In-Reply-To: References: Message-ID: <20071024182516.GA10807@redhat.com> On Wed, Oct 24, 2007 at 03:21:05PM -0200, Augusto Castelan Carlson wrote: > Hi! > > I have a server with two guests (all Fedora 7). Each one has its own partition. > > host: /dev/hda1 > guest1: /dev/hda2 > guest2: /dev/hda3 > > Suppose that my host fail and I need to reinstall it. After > reinstalling, how can I have access to my 2 guests using tools such as > virt-manager/virsh/xm? or make them run as the were before the host > failed. > > When I installed both guests, no configuration file was created in /etc/xen Just re-run virt-install, passing in the /dev/hda2 as the guest file system. When the installer pops up, instead of doing an install (which would overwrite your guest), simply use 'virsh destroy' to shut it down immediately. The neccessary guest config file should now have been created so you can re-start with 'virsh start' as usual. I intend to add some form of 'virt-import' tool do make this more simple, so you don't have to do the 'boot the installer & quit' trick. 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 guillaume.chardin at gmail.com Fri Oct 26 10:00:49 2007 From: guillaume.chardin at gmail.com (Guillaume) Date: Fri, 26 Oct 2007 12:00:49 +0200 Subject: [Fedora-xen] problem creating my 1st VM Message-ID: Hi list, I' trying to create my first vm with Xen, and I experience some problems. I follow some How to's and xen docs to build my own config file, but maybe, there are some errors inside it. I have the following problem, after i start my guest domain, the kernel boot & then a kernel panix is displayed : VFS: Cannot open root device "hda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I try to start this Virtual machine from vmware workstation where i install Xen (Dom0 work perfectly). My config is make up of these lines : kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" root = "/dev/hda1 ro" name = "test_Linux" cdrom = "/dev/cdrom" memory = "128" builder = "linux" name = "linux" disk = [ "file:/xenroot/linux/linux.xdi,hda1,w" ] Additionnals questions : a) Does i must use a modified Xen linux kernel, or, can I use a "normal/standard" kernel to boot up my VM? b) Is it possible to start a fresh install of Fedora directly from dvd in a guest domain (I mean without creating & mounting disk image/VM partition and copying root file system in it? If yes, how ? Thanks for your replyes. -- Guillaume From orenault at redhat.com Fri Oct 26 10:21:35 2007 From: orenault at redhat.com (Olivier Renault) Date: Fri, 26 Oct 2007 12:21:35 +0200 Subject: [Fedora-xen] problem creating my 1st VM In-Reply-To: References: Message-ID: <4721BFAF.2030506@redhat.com> Guillaume wrote: > Hi list, > I' trying to create my first vm with Xen, and I experience some problems. > I follow some How to's and xen docs to build my own config file, but > maybe, there are some errors inside it. > I have the following problem, after i start my guest domain, the > kernel boot & then a kernel panix is displayed : > > VFS: Cannot open root device "hda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) > > I try to start this Virtual machine from vmware workstation where i > install Xen (Dom0 work perfectly). > > My config is make up of these lines : > kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" > root = "/dev/hda1 ro" > name = "test_Linux" > cdrom = "/dev/cdrom" > memory = "128" > builder = "linux" > name = "linux" > disk = [ "file:/xenroot/linux/linux.xdi,hda1,w" ] > > Additionnals questions : > a) Does i must use a modified Xen linux kernel, or, can I use a > "normal/standard" kernel to boot up my VM? > b) Is it possible to start a fresh install of Fedora directly from dvd > in a guest domain (I mean without creating & mounting disk image/VM > partition and copying root file system in it? If yes, how ? > > Thanks for your replyes. > Hi, I am not sure how you have installed your VM ? You should try to reinstall the VM using virt-install (command line) / virt-manager (GUI). It is not great to try a virtualisation solution inside another one ( you may have strange behaviour / poor performance ). a) You need to run the xen kernel in order to use xen. b) To install a paravirtualise VM you will need to have an install tree exported as http. You can simply mount the DVD on /var/www/html and start the http server. You may want to read http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart Good luck, Olivier From un1xf00 at yahoo.com Fri Oct 26 11:32:36 2007 From: un1xf00 at yahoo.com (unixfoo) Date: Fri, 26 Oct 2007 04:32:36 -0700 (PDT) Subject: [Fedora-xen] xm mem-set Message-ID: <395263.18284.qm@web34501.mail.mud.yahoo.com> My domU's memory usage is around 512 MB , but it is alloted with 4GB of memory. When i try to xm mem-set and reduce memory on a domU, the memory doesnt decrease to the value specified ( even though the domU is idle and memory is not used up at all ) here is my xen version .. [root at unixfoo ~]# xm info host : unixfoo release : 2.6.18-xen version : #1 SMP Thu Mar 22 14:12:23 PDT 2007 machine : i686 nr_cpus : 1 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 1 threads_per_core : 1 cpu_mhz : 2394 hw_caps : bfebfbff:00000000:00000000:00000080:00004400 total_memory : 503 free_memory : 53 xen_major : 3 xen_minor : 0 xen_extra : -unstable xen_caps : xen-3.0-x86_32p xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xf5800000 xen_changeset : unavailable cc_compiler : gcc version 3.4.6 20060404 (Red Hat 3.4.6-3.1) cc_compile_by : root cc_compile_domain : localhost cc_compile_date : Thu Mar 22 14:12:26 PDT 2007 xend_config_format : 3 [root at unixfoo0~]# any pointers? un1xf00 http://unixfoo.blogspot.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From mnielsen at redhat.com Fri Oct 26 12:01:38 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Fri, 26 Oct 2007 08:01:38 -0400 Subject: [Fedora-xen] problem creating my 1st VM In-Reply-To: <4721BFAF.2030506@redhat.com> References: <4721BFAF.2030506@redhat.com> Message-ID: <4721D722.5060704@redhat.com> In addition, you're presenting the disk as hda1. You probably mean to present the disk as hda so the partition hda1 on hda isn't confused. As Olivier has pointed out though, you appear to have many other issues to work through as well. Mark Olivier Renault wrote: > Guillaume wrote: >> Hi list, >> I' trying to create my first vm with Xen, and I experience some >> problems. >> I follow some How to's and xen docs to build my own config file, but >> maybe, there are some errors inside it. >> I have the following problem, after i start my guest domain, the >> kernel boot & then a kernel panix is displayed : >> >> VFS: Cannot open root device "hda1" or unknown-block(0,0) >> Please append a correct "root=" boot option >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(0,0) >> >> I try to start this Virtual machine from vmware workstation where i >> install Xen (Dom0 work perfectly). >> >> My config is make up of these lines : >> kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" >> root = "/dev/hda1 ro" >> name = "test_Linux" >> cdrom = "/dev/cdrom" >> memory = "128" >> builder = "linux" >> name = "linux" >> disk = [ "file:/xenroot/linux/linux.xdi,hda1,w" ] >> >> Additionnals questions : >> a) Does i must use a modified Xen linux kernel, or, can I use a >> "normal/standard" kernel to boot up my VM? >> b) Is it possible to start a fresh install of Fedora directly from dvd >> in a guest domain (I mean without creating & mounting disk image/VM >> partition and copying root file system in it? If yes, how ? >> >> Thanks for your replyes. >> > Hi, > > I am not sure how you have installed your VM ? You should try to > reinstall the VM using virt-install (command line) / virt-manager (GUI). > > It is not great to try a virtualisation solution inside another one ( > you may have strange behaviour / poor performance ). > > a) You need to run the xen kernel in order to use xen. > > b) To install a paravirtualise VM you will need to have an install > tree exported as http. You can simply mount the DVD on /var/www/html > and start the http server. > > You may want to read > http://fedoraproject.org/wiki/Docs/Fedora7VirtQuickStart > > Good luck, > Olivier > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- A non-text attachment was scrubbed... Name: mnielsen.vcf Type: text/x-vcard Size: 177 bytes Desc: not available URL: From Dustin.Henning at prd-inc.com Fri Oct 26 14:17:36 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 26 Oct 2007 10:17:36 -0400 Subject: [Fedora-xen] problem creating my 1st VM In-Reply-To: References: Message-ID: <001201c817da$f5279320$df76b960$@Henning@prd-inc.com> It has been a while since I have used a paravirtualized vm, so my responses will be vague, but perhaps helpful. Regarding your original install, both previous responses made good points. However, I thought some additional explanation might be helpful: a) -The kernel line you put in your config makes your vm boot that kernel (the one on your local disk), so you are already using a xen kernel to boot that vm. -There are ready made xen compatible installs of OSes on disk images available for download at various places, you should be able to find instructions on how to get thee images into your vm's virtual drive as well. You may already know this base on your question, but I wasn't sure (I learned xen before it came on distros and I haven't read the fedora documentation to see if it mentions that or where you are copying the files from for the vms you create). -Personally, I prefer to use partitions (or even disks) as virtual disks. This can be done by using (for example) phy:/dev/hdb or phy:/dev/hda4 or dev:/mapper/lvmvolgroup/lvmvol (or something, LVM certainly makes the management of multiple virtual but physical disks more manageable) instead of file:/xenroot/linux/linux.xdi in the first portion of the disk= arguments. b) -You can use a normal/standard kernel in an HVM vm. This requires that you have a machine with hardware virtualization, but it allows you to install windows, boot with a non-xen livecd, etc. I think there is an example like /etc/xen/xmexample.hvm for these situations. In such a case, you wouldn't have to fdisk the intended virtual partition because the installer you use when you initially create the machine (windows, linux, whatever) would take care of that. etc) As mentioned by another user, the virtual machine installation executables (virsh-install/virt-install?) will create a virtual machine that is more manageable with fedora tools and uses xen capabilities. I don't know where config files for these domains are installed, and I prefer the manual creation via config files and whatnot so I have more control when the time comes for major changes. I believe the installer provided on Fedora can make paravirtualized and hvm machines, and from the sound of a previous response, it may take care of copying the filesystem on paravirtualized machines as well. I hope this helps or at least doesn't hurt. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Guillaume Sent: Friday, October 26, 2007 06:01 To: fedora-xen at redhat.com Subject: [Fedora-xen] problem creating my 1st VM Hi list, I' trying to create my first vm with Xen, and I experience some problems. I follow some How to's and xen docs to build my own config file, but maybe, there are some errors inside it. I have the following problem, after i start my guest domain, the kernel boot & then a kernel panix is displayed : VFS: Cannot open root device "hda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I try to start this Virtual machine from vmware workstation where i install Xen (Dom0 work perfectly). My config is make up of these lines : kernel = "/boot/vmlinuz-2.6.20-2936.fc7xen" root = "/dev/hda1 ro" name = "test_Linux" cdrom = "/dev/cdrom" memory = "128" builder = "linux" name = "linux" disk = [ "file:/xenroot/linux/linux.xdi,hda1,w" ] Additionnals questions : a) Does i must use a modified Xen linux kernel, or, can I use a "normal/standard" kernel to boot up my VM? b) Is it possible to start a fresh install of Fedora directly from dvd in a guest domain (I mean without creating & mounting disk image/VM partition and copying root file system in it? If yes, how ? Thanks for your replyes. -- Guillaume -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From Nicola.Sabbi at poste.it Fri Oct 26 14:51:33 2007 From: Nicola.Sabbi at poste.it (Nico Sabbi) Date: Fri, 26 Oct 2007 16:51:33 +0200 Subject: [Fedora-xen] no fuse with xen? Message-ID: <200710261651.34066.Nicola.Sabbi@poste.it> Hi, there's no fuse module in kernel-xen. Is it intentional because fuse can't work with it? Thanks, Nico From guillaume.chardin at gmail.com Fri Oct 26 15:23:17 2007 From: guillaume.chardin at gmail.com (Guillaume) Date: Fri, 26 Oct 2007 17:23:17 +0200 Subject: [Fedora-xen] problem creating my 1st VM In-Reply-To: <6624498911533168235@unknownmsgid> References: <6624498911533168235@unknownmsgid> Message-ID: > It has been a while since I have used a paravirtualized vm, so my responses > will be vague, but perhaps helpful. > Regarding your original install, both previous responses made good points. > However, I thought some additional explanation might be helpful: > a) > -The kernel line you put in your config makes your vm boot that kernel (the > one on your local disk), so you are already using a xen kernel to boot that > vm. Is there a problem by using the kernel use to boot up the system (Dom0) ? If I understand, you mean that I have to use a kernel dedicated to boot all DomU ! Why, is there some limitation by using this kernel (Dom0) for running VM ? > -There are ready made xen compatible installs of OSes on disk images > available for download at various places, you should be able to find > instructions on how to get thee images into your vm's virtual drive as well. Ok, but I want first, understand how Xen works, and then, i'll get theses files. I prefer to learn by getting rid of theses problem before, its a godd formation i think. And i tought too, it's more quick to use ready-to-use Xen images files. Thanks for your time :) From Dustin.Henning at prd-inc.com Fri Oct 26 15:46:51 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 26 Oct 2007 11:46:51 -0400 Subject: [Fedora-xen] problem creating my 1st VM In-Reply-To: References: <6624498911533168235@unknownmsgid> Message-ID: <001301c817e7$6da20cc0$48e62640$@Henning@prd-inc.com> There is no problem using the same kernel. Some people compile a dom0 kernel and a domU kernel when they custom build or manually install xen, but it isn't necessary, it just makes for a smaller kernel. It is fine to use the same for both, as it is loaded read-only anyway. I was just pointing out that you were using an existing xen kernel in your physical /boot and not a kernel in your vm's /boot. I don't remember all of the setup of paravirtualized vms since it has been a while, but you might try Mike's suggestion: disk = [ 'file:/xenroot/linux/linux.xdi,hda,w' ] in spite of the fact that xmexample1 had hda1 in the second section of the argument. Whether to use hda or hda1 may depend on the image you are using. Also, since Fedora uses an initial ramdisk, you might need to add this line under your kernel line in your config file: ramdisk = "/boot/initrd-2.6.20-2936.fc7xen" Another thing is, notice I am using ' where you used ". I am not sure if it matters, but I think all of my configs have ' instead of " when inside of []s. Finally, you might need to set up a swap partition. If that was necessary, it would probably mean that you need something more like this: disk = [ 'file:/xenroot/linux/linux.xdi,hda1,w' , 'file:/xenroot/linux/linuxswap.xdi,hda2,w' ] In this example, the linuxswap.xdi would have to be loop-mounted and formatted as swap. Keep in mind that it has been a long time since I have dealt with a paravirtualized guest, and also I am not even familiar with the xdi extension / type of file you are using / where it came from and what documentation it came with. It may be that something on your linux.xdi image isn't xen compatible (perhaps the image was made for hvm), though, and that is why I mentioned downloadable xen-ready images (I was running paravirtualized CentOS on an Ubuntu host with xen manually installed [xen xen kernel vs fedora xen kernel or ubuntu xen kernel]). I doubt I come up with any other ideas on your current situation, but if any of these ideas change anything for you, new information might get you some help from someone else. Dustin -----Original Message----- From: Guillaume [mailto:guillaume.chardin at gmail.com] Sent: Friday, October 26, 2007 11:20 To: Dustin.Henning at prd-inc.com Subject: Re: [Fedora-xen] problem creating my 1st VM 2007/10/26, Dustin Henning : > It has been a while since I have used a paravirtualized vm, so my responses > will be vague, but perhaps helpful. > Regarding your original install, both previous responses made good points. > However, I thought some additional explanation might be helpful: > a) > -The kernel line you put in your config makes your vm boot that kernel (the > one on your local disk), so you are already using a xen kernel to boot that > vm. Is there a problem by using the kernel use to boot up the system (Dom0) ? If I understand, you mean that I have to use a kernel dedicated to boot all DomU ! Why, is there some limitation by using this kernel (Dom0) for running VM ? > -There are ready made xen compatible installs of OSes on disk images > available for download at various places, you should be able to find > instructions on how to get thee images into your vm's virtual drive as well. Ok, but I want first, understand how Xen works, and then, i'll get theses files. I prefer to learn by getting rid of theses problem before, its a godd formation i think. And i tought too, it's more quick to use ready-to-use Xen images files. Thanks for your time :) -- Guillaume From guillaume.chardin at gmail.com Fri Oct 26 15:50:11 2007 From: guillaume.chardin at gmail.com (Guillaume) Date: Fri, 26 Oct 2007 17:50:11 +0200 Subject: [Fedora-xen] Re: problem creating my 1st VM In-Reply-To: References: Message-ID: 2007/10/26, Guillaume : > Hi list, > I' trying to create my first vm with Xen, and I experience some problems. > I follow some How to's and xen docs to build my own config file, but > maybe, there are some errors inside it. > I have the following problem, after i start my guest domain, the > kernel boot & then a kernel panic is displayed : > > VFS: Cannot open root device "hda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) For this problem, it seems that no reference to scsi is made during DomU boot. Maybe SCSI support is loaded with the initrd image. Is there a way to give arguments in VM config file to use any initrd image ? Or I have to "recompile" the kernel and set generic scsi support not in module ! --- Guillaume From Dustin.Henning at prd-inc.com Fri Oct 26 16:04:49 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 26 Oct 2007 12:04:49 -0400 Subject: [Fedora-xen] Re: problem creating my 1st VM In-Reply-To: References: Message-ID: <000701c817e9$ef81f730$ce85e590$@Henning@prd-inc.com> In the e-mail I just sent, I showed an example for using initrd. Try that. However, the virtual hda should not be detected as a generic scsi device, it should be detected as a generic ide device. A virtual sda might be detected as a scsi device, but I don't know if you can even do that in a paravirtualized environment (I think you can in an HVM, but the virtual BIOS won't boot to a scsi device in that situation). The unknown block device error could be happening because the xdi file is "partitioned" and should be connected as hda (as previously suggested by another member and again by myself in my previous [just sent] e-mail) instead of hda1. If that is the case, you wouldn't be able to also add an hda2 and might have to use hdb1 if you need additional partitions / drives on your vm, but if it is "partitioned" it likely has a swap partition anyway. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Guillaume Sent: Friday, October 26, 2007 11:50 To: fedora-xen at redhat.com Subject: [Fedora-xen] Re: problem creating my 1st VM 2007/10/26, Guillaume : > Hi list, > I' trying to create my first vm with Xen, and I experience some problems. > I follow some How to's and xen docs to build my own config file, but > maybe, there are some errors inside it. > I have the following problem, after i start my guest domain, the > kernel boot & then a kernel panic is displayed : > > VFS: Cannot open root device "hda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) For this problem, it seems that no reference to scsi is made during DomU boot. Maybe SCSI support is loaded with the initrd image. Is there a way to give arguments in VM config file to use any initrd image ? Or I have to "recompile" the kernel and set generic scsi support not in module ! --- Guillaume -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From guillaume.chardin at gmail.com Fri Oct 26 16:31:11 2007 From: guillaume.chardin at gmail.com (Guillaume) Date: Fri, 26 Oct 2007 18:31:11 +0200 Subject: [Fedora-xen] Re: problem creating my 1st VM In-Reply-To: <-8839792905199174798@unknownmsgid> References: <-8839792905199174798@unknownmsgid> Message-ID: > In the e-mail I just sent, I showed an example for using initrd. > Try that. Sorry, but I just get your message after I mine :) I try your tips, and it seems to work... The initrd image is loaded and... I have a new error message. I'll investigate on it asap, but for this week its over :) >However, the virtual hda should not be detected as a generic scsi > device, it should be detected as a generic ide device. A virtual sda might > be detected as a scsi device, but I don't know if you can even do that in a > paravirtualized environment (I think you can in an HVM, but the virtual BIOS > won't boot to a scsi device in that situation). I'll try the "hda option" next time. For information about my xdi file, i create it with dd, mount it as a loop device, format it with ext3 FS and after copy my "/" on it. I choose use xdi extension on my own, but its stand for "Xen Disk Image". Its not related with any other ext. Bye :) -- Guillaume From Dustin.Henning at prd-inc.com Fri Oct 26 16:41:15 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Fri, 26 Oct 2007 12:41:15 -0400 Subject: [Fedora-xen] Re: problem creating my 1st VM In-Reply-To: References: <-8839792905199174798@unknownmsgid> Message-ID: <000901c817ef$06762dd0$13628970$@Henning@prd-inc.com> Since your xdi file is mounted loop and formatted ext3, it isn't partitioned, so hda1 is probably the way to go. It won't hurt to try it as hda instead of hda1, but I don't expect that to help. Good luck determining your new problem. Downloading a xen-ready fedora image from someone might be what it takes to fix it, though, something from your real / filesystm might not be compatible with the paravirtualized environment and might be trying to access things that don't exist in said environment. I am not sure on that, but if documentation suggested it, I would think it would work. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Guillaume Sent: Friday, October 26, 2007 12:31 To: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Re: problem creating my 1st VM > In the e-mail I just sent, I showed an example for using initrd. > Try that. Sorry, but I just get your message after I mine :) I try your tips, and it seems to work... The initrd image is loaded and... I have a new error message. I'll investigate on it asap, but for this week its over :) >However, the virtual hda should not be detected as a generic scsi > device, it should be detected as a generic ide device. A virtual sda might > be detected as a scsi device, but I don't know if you can even do that in a > paravirtualized environment (I think you can in an HVM, but the virtual BIOS > won't boot to a scsi device in that situation). I'll try the "hda option" next time. For information about my xdi file, i create it with dd, mount it as a loop device, format it with ext3 FS and after copy my "/" on it. I choose use xdi extension on my own, but its stand for "Xen Disk Image". Its not related with any other ext. Bye :) -- Guillaume -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From dlbewley at lib.ucdavis.edu Fri Oct 26 19:01:47 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 26 Oct 2007 12:01:47 -0700 Subject: [Fedora-xen] 64-Bit RAM Detection >4GB? In-Reply-To: <008401c81276$509879f0$f1c96dd0$@Henning@prd-inc.com> References: <001501c811c1$6c6bbee0$45433ca0$@Henning@prd-inc.com> <1701384668.50351192808779750.JavaMail.root@zebra.lib.ucdavis.edu> <008401c81276$509879f0$f1c96dd0$@Henning@prd-inc.com> Message-ID: <1193425307.20883.7.camel@tofu.lib.ucdavis.edu> On Fri, 2007-10-19 at 13:34 -0400, Dustin Henning wrote: > >-----Original Message----- > >From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dale Bewley > >Sent: Friday, October 19, 2007 11:46 > >To: fedora-xen > >Subject: Re: [Fedora-xen] 64-Bit RAM Detection >4GB? > > > >I have 4 procs with 16G RAM and no mem paramters in grub at all, and it looks like this: > > > >Linux h 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:11:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > > ># grep 'model name' /proc/cpuinfo > >model name : AMD Opteron(tm) Processor 852 > >model name : AMD Opteron(tm) Processor 852 > >model name : AMD Opteron(tm) Processor 852 > >model name : AMD Opteron(tm) Processor 852 > > > ># grep Total /proc/meminfo > >MemTotal: 13335552 kB > >SwapTotal: 5261240 kB > >VmallocTotal: 34359738367 kB > > > ># xm info |grep total > >total_memory : 16319 > > > >I have 3 domU's running with each allocated 1G, so 16-3=13 which I suppose explains the MemTotal line above from the perspective of dom0. > > > > > >On an identical server running RHEL with no xen and I see something a bit different: > > > >Red Hat Enterprise Linux AS release 4 (Nahant Update 5) > >Linux z 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:58:20 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux > > > ># grep Total /proc/meminfo > >MemTotal: 16359284 kB > >HighTotal: 0 kB > >LowTotal: 16359284 kB > >SwapTotal: 5261240 kB > >VmallocTotal: 536870911 kB > >HugePages_Total: 0 > > > >Not sure if that was helpful. > >-- > >Dale Bewley - Unix Administrator - Shields Library - UC Davis > >GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 > > Dale, > Could you tell me if you passed any arguments to the installer during your initial install? Also, can you show me the appropriate portion of your grub.conf? I would like to see if maybe it is different than mine even though they are both pre-packaged installs. I had a machine with 2.6.20-2931.fc7xen, so I copied that to the machine in question, and it also only shows 3.1GiB for me. I compared the config files for that kernel and the one I was using, and they are identical (minus version and date comment lines), so that was as I expected, but it makes it less likely that my problem is a version problem and more likely that something else is haywire. Thanks, > Dustin My install command line was: ksdevice=eth0 console=tty0 console=ttyS0,9600 load_ramdisk=1 initrd=f7/x86_64/initrd.img network ks=http://ks/ks-f7-v40z.cfg kssendmac BOOT_IMAGE=f7/x86_64/vmlinuz My grub entry for the currently running kernel is: title Fedora (2.6.20-2931.fc7xen) root (hd0,0) kernel /xen.gz-2.6.20-2931.fc7 com1=9600 module /vmlinuz-2.6.20-2931.fc7xen ro root=/dev/VGRAID/LVRoot console=ttyS0,9600 module /initrd-2.6.20-2931.fc7xen.img My messy KS and KS post script is attached. During install, I did hit a bug https://bugzilla.redhat.com/show_bug.cgi?id=242107 that I had to work around by running mkinitrd before I rebooted. If I didn't I would be missing the RAID1 module and fail to boot, but that's not related to the memory issue. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 -------------- next part -------------- ################################################################################ # This is a kickstart file for Fedora Core Linux 7 on a # Sun V40z quad Opteron server with 5x 73G SCSI drives in a # RAID5 configuration. This box is to be configured # with serial console access. #------------------------------------------------------------------------------- # # Dale Bewley # Fri Jun 1 08:35:36 PDT 2007 - F7 # - had an error with md1 being already defined - trying to swap md0 and md1 # Fri Apr 20 14:21:47 PDT 2007 - FC6 cleanup and prune down # Fri Apr 6 16:34:56 PDT 2007 # - FC6 update # Wed Sep 27 16:26:47 PDT 2006 # - FC5 cleaned up # Fri Jul 7 15:10:09 PDT 2006 # - FC5 initial # Fri Sep 30 12:28:39 PDT 2005 # - FC4 ################################################################################ ## upgrade or install? install # upgrade ## comment out if you want the machine to wait for you to reboot manually reboot ## install source on URL or CDROM? url --url http://ks/fedora/linux/releases/7/Fedora/x86_64/os #cdrom ## use text mode install since i'll be spying on the serial console text skipx lang en_US.UTF-8 keyboard us timezone America/Los_Angeles ## network setup network --device eth0 --bootproto dhcp network --device eth1 --onboot no --bootproto dhcp ## we'll redo firewalling by hand later firewall --enabled --port=22:tcp ## this could be annoying for now so leave it off selinux --disabled authconfig --enableshadow --enablemd5 ## change this after install rootpw secret ################################################################################ # Setup the disk drives. # 5 SCSI drives (sda through sde) partitioned the same way. # Root partition can't do LVM so put it on its own raid device. # # Drives sda through sde: # Part1 - .5G: part of RAID1 md1 device for /boot # Part2 - Remaining space: RAID5 md0 device split by LVM # Part3 - 1G: Swap. Not much point to RAID swap # Device Boot Start End Blocks Id System # /dev/sde1 * 1 64 514048+ fd Linux raid autodetect # /dev/sde2 65 8793 70115692+ fd Linux raid autodetect # /dev/sde3 8794 8924 1052257+ 82 Linux swap / Solaris # Clear the Master Boot Record zerombr # nuke all existing partitions clearpart --all --initlabel # for /boot on 500M raid1 mirror at md1 part raid.a1 --size=500 --ondisk=sda --asprimary part raid.b1 --size=500 --ondisk=sdb --asprimary part raid.c1 --size=500 --ondisk=sdc --asprimary part raid.d1 --size=500 --ondisk=sdd --asprimary part raid.e1 --size=500 --ondisk=sde --asprimary # swap 1G on each disk part swap --size=1024 --ondisk=sda part swap --size=1024 --ondisk=sdb part swap --size=1024 --ondisk=sdc part swap --size=1024 --ondisk=sdd part swap --size=1024 --ondisk=sde # for LVM on raid5 at md0 using remaining space # (a0 is shorthard for drive *a* on md*0*) part raid.a0 --size=1 --ondisk=sda --asprimary --grow part raid.b0 --size=1 --ondisk=sdb --asprimary --grow part raid.c0 --size=1 --ondisk=sdc --asprimary --grow part raid.d0 --size=1 --ondisk=sdd --asprimary --grow part raid.e0 --size=1 --ondisk=sde --asprimary --grow # create raid5 md0 raid pv.a0e0 --level=RAID5 --fstype="physical volume (LVM)" --device=md1 --spares=1 raid.a0 raid.b0 raid.c0 raid.d0 raid.e0 # create raid1 md1 raid /boot --level=RAID1 --fstype=ext3 --device=md0 --spares=3 raid.a1 raid.b1 raid.c1 raid.d1 raid.e1 # setup LVM on md0 for OS partitions volgroup VGRAID pv.a0e0 logvol / --fstype=ext3 --name=LVRoot --vgname=VGRAID --size=2048 logvol /opt --fstype=ext3 --name=LVOpt --vgname=VGRAID --size=1024 logvol /var --fstype=ext3 --name=LVVar --vgname=VGRAID --size=6144 logvol /usr --fstype=ext3 --name=LVUsr --vgname=VGRAID --size=4096 logvol /home --fstype=ext3 --name=LVHome --vgname=VGRAID --size=1024 logvol /var/lib/xen/images --fstype=ext3 --name=LVXen --vgname=VGRAID --size=20480 # install grub on each drive bootloader --location=mbr --driveorder=sda,sdb,sdc,sdd,sde ################################################################################ # Install packages %packages @base @core pax cracklib-dicts kernel-xen libcap lvm2 ntp smartmontools tzdata vim-enhanced vim-common xen -bluez-libs -bluez-pin -bluez-utils -cairo -cups -cups-libs -gpm -irda-utils -NetworkManager -nfs-utils -nfs-utils-lib -pcmciautils -rp-pppoe -talk -wireless-tools -wpa_supplicant -ypbind -yp-tools ### these are needed for netbackup 5.1 client # xinetd - not in F7 # compat-libstdc++-296 - not in F7 libgcc.i386 ################################################################################ # Final Configuration %post --nochroot cp /tmp/ks.cfg /mnt/sysimage/root/install-ks.cfg cp /proc/cmdline /mnt/sysimage/root/install-cmdline %post # we'll use these values in the extended final config EMAIL=root at mail DIST=f7 MAC_ADDR=`ifconfig eth0 | grep HWaddr | \ sed -e 's/^.*HWaddr \([A-Fa-f0-9:]*\).*$/\1/; s/:/-/g;'` # turn off some things chkconfig gpm off chkconfig netfs off chkconfig ntpd on # put /tmp on swap cuz it's fast and junk goes away on reboot echo -e "none\t\t\t/tmp\t\t\ttmpfs\tdefaults\t0 0" >> /etc/fstab # setup root's profile echo 'alias vi=vim' >> /root/.bash_profile # I want to know about things... echo -e "root:\t\t$EMAIL" >> /etc/aliases newaliases # attempt to get raid1 and raid5 in initrd #mv /boot/initrd-2.6.20-2925.9.fc7xen.img /boot/initrd-2.6.20-2925.9.fc7xen.img.bak #mkinitrd --with=raid1 /boot/initrd-2.6.20-2925.9.fc7xen.img 2.6.20-2925.9.fc7xen ################################################################################ # Extended Final Configuration # Apparently KS will only use the first ksappend line and we want to # call modular scripts depending on the host being setup. Plus the vars # aren't expanded. So we'll serve a meta config from the web server which will # serve up a custom shell script based on the dist ver and MAC. wget -O /root/ks-post-config.sh "http://ks/ks-server.php?mac=${MAC_ADDR}&dist=${DIST}" chmod 700 /root/ks-post-config.sh /root/ks-post-config.sh # tell daddy we are all done cat /root/install.log /root/install-ks.cfg /root/ks-post-config.sh \ | mail -s "${DIST} ks install ${MAC_ADDR}" $EMAIL -------------- next part -------------- A non-text attachment was scrubbed... Name: ks-post-config.sh Type: application/x-shellscript Size: 1723 bytes Desc: not available URL: From kewlemer at gmail.com Sat Oct 27 08:05:17 2007 From: kewlemer at gmail.com (kewlemer) Date: Sat, 27 Oct 2007 01:05:17 -0700 Subject: [Fedora-xen] ARP failing when I ping from host to guest Message-ID: <79cbe6750710270105rf3ed46cr74ac2128f7d421e@mail.gmail.com> I'm running x86_64 Fedora7 host and 32 bit Fedora 7 guest on KVM. Here what the default bridged network setting gave me - HOST - [root at fed-amd64 ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:1A:A0:56:52:E5 inet addr:192.168.1.9 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21a:a0ff:fe56:52e5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:4144 errors:0 dropped:0 overruns:0 frame:0 TX packets:4490 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3143529 (2.9 MiB) TX bytes:1026716 (1002.6 KiB) Interrupt:23 Base address:0x6000 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:11074 errors:0 dropped:0 overruns:0 frame:0 TX packets:11074 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:49074613 (46.8 MiB) TX bytes:49074613 (46.8 MiB) virbr0 Link encap:Ethernet HWaddr 00:FF:EE:14:6D:91 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:61 errors:0 dropped:0 overruns:0 frame:0 TX packets:86 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9261 (9.0 KiB) TX bytes:12220 (11.9 KiB) vnet0 Link encap:Ethernet HWaddr 00:FF:EE:14:6D:91 inet6 addr: fe80::2ff:eeff:fe14:6d91/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:61 errors:0 dropped:0 overruns:0 frame:0 TX packets:61 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:10115 (9.8 KiB) TX bytes:7195 (7.0 KiB) [root at fed-amd64 ~]# Here is what the GUEST landed up with when using the default configuration- [root at fed-guest ~]# ifconfig eth0 Link encap:Ethernet HWaddr 00:16:3E:6B:C6:36 inet addr:192.168.122.195 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::216:3eff:fe6b:c636/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1 RX packets:4144 errors:0 dropped:0 overruns:0 frame:0 TX packets:4490 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3143529 (2.9 MiB) TX bytes:1026716 (1002.6 KiB) Interrupt:23 Base address:0x6000 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:11074 errors:0 dropped:0 overruns:0 frame:0 TX packets:11074 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:49074613 (46.8 MiB) TX bytes:49074613 (46.8 MiB) 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:61 errors:0 dropped:0 overruns:0 frame:0 TX packets:86 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:9261 (9.0 KiB) TX bytes:12220 (11.9 KiB) [root at fed-guest ~]# The problem is that I'm unable to ping from the host to the guest (to 192.168.122.195). tcpdump shows that guest is not responding to ARPs for 192.168.122.195. Can anyone tell me why? When I ping from the guest to to 192.168.122.1 and 192.168.122.195, both go through. But when I ssh into either of them to make sure I'm reaching the host, the ssh lands into the guest itself. This means the ping response on the guest is from itself - so the guest is also unable to reach the host. I googled and looked at the following sitew, but they were of not much help for this problem - http://www.gnome.org/~markmc/virtual-networking.html http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt Am I missing something ? Thanks, KM From kewlemer at gmail.com Sat Oct 27 20:11:14 2007 From: kewlemer at gmail.com (kewlemer) Date: Sat, 27 Oct 2007 13:11:14 -0700 Subject: [Fedora-xen] Re: ARP failing when I ping from host to guest In-Reply-To: <79cbe6750710270105rf3ed46cr74ac2128f7d421e@mail.gmail.com> References: <79cbe6750710270105rf3ed46cr74ac2128f7d421e@mail.gmail.com> Message-ID: <79cbe6750710271311x4d7d8069r644ec359b768ab25@mail.gmail.com> > The problem is that I'm unable to ping from the host to the guest (to > 192.168.122.195). tcpdump shows that guest is not responding to ARPs > for 192.168.122.195. Can anyone tell me why? > To be more specific, I'm doing a tcpdump on guest's eth0(192.168.122.195). When the host pings 192.168.122.195, I see following - tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 12:15:49.058031 arp who-has 192.168.122.195 tell 192.168.122.1 12:15:51.065437 arp who-has 192.168.122.195 tell 192.168.122.1 12:15:52.069123 arp who-has 192.168.122.195 tell 192.168.122.1 12:15:53.071852 arp who-has 192.168.122.195 tell 192.168.122.1 12:15:55.077218 arp who-has 192.168.122.195 tell 192.168.122.1 When the guest's eth0 is receiving ARP for it's right IP address, why is it not responding? Here are the routing tables - HOST- [root at fed-amd64 ~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 [root at fed-amd64 ~]# GUEST- [root at guest~]# netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 0.0.0.0 192.168.122.1 0.0.0.0 UG 0 0 0 eth0 [root at guest ~]# > When I ping from the guest to to 192.168.122.1 and 192.168.122.195, > both go through. But when I ssh into either of them to make sure I'm > reaching the host, the ssh lands into the guest itself. This means the > ping response on the guest is from itself - so the guest is also > unable to reach the host. > Please ignore this. I figured that I have to use host's eth0(192.168.1.9) to access the host from the guest. Thanks, KM From jklein at saugus.k12.ca.us Tue Oct 30 20:02:22 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Tue, 30 Oct 2007 13:02:22 -0700 (PDT) Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <5471223.2281551193773974304.JavaMail.root@do8> Message-ID: <1104266.2282971193774542215.JavaMail.root@do8> Am attempting to update a RHEL4 domU from a custom created Xen kernel (created before RHEL5) to a supported kernel (2.6.9-55.0.9.ELxenU) and RHEL5 host without success. For some reason, the kernel can no longer find xvda. Boots fine on the old kernel and host, so I'm at a bit of a loss. Host has other domUs booted off the same SAN, with no security restrictions, so I don't see how it could be hardware. Copy of configs and partial debug log below. Ideas? Conf: name = "do5" memory = "1024" disk = [ 'phy:/dev/mpath/msa-mpathv0p1,xvda,w', ] vif = [ 'mac=00:16:3e:55:a5:65, bridge=xenbr2' ] vfb = ["type=vnc,vncunused=1"] bootloader="/usr/bin/pygrub" vcpus=1 Grub: root (hd0,0) kernel /vmlinuz-2.6.9-55.0.9.ELxenU ro root=/dev/xvda2 rhgb quiet initrd /initrd-2.6.9-55.0.9.ELxenU.img Debug: [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'do5'], ['memory', '1024'], ['vcpus', 1], ['bootloader', '/usr/bin/pygrub'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.MpxKQP'], ['kernel', '/var/lib/xen/vmlinuz.6u2e9w'], ['args', 'ro root=/dev/xvda2 rhgb quiet']]], ['device', ['vbd', ['uname', 'phy:/dev/mpath/msa-mpathv0p1'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr2'], ['mac', '00:16:3e:55:a5:65']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']]]]) [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'do5'], ['memory', '1024'], ['vcpus', 1], ['bootloader', '/usr/bin/pygrub'], ['image', ['linux', ['ramdisk', '/var/lib/xen/initrd.MpxKQP'], ['kernel', '/var/lib/xen/vmlinuz.6u2e9w'], ['args', 'ro root=/dev/xvda2 rhgb quiet']]], ['device', ['vbd', ['uname', 'phy:/dev/mpath/msa-mpathv0p1'], ['dev', 'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'xenbr2'], ['mac', '00:16:3e:55:a5:65']]], ['device', ['vkbd']], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']]]] [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:397) parseConfig: result is {'shadow_memory': None, 'start_time': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None, 'image': ['linux', ['ramdisk', '/var/lib/xen/initrd.MpxKQP'], ['kernel', '/var/lib/xen/vmlinuz.6u2e9w'], ['args', 'ro root=/dev/xvda2 rhgb quiet']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'do5', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 1024, 'device': [('vbd', ['vbd', ['uname', 'phy:/dev/mpath/msa-mpathv0p1'], ['dev', 'xvda'], ['mode', 'w']]), ('vif', ['vif', ['bridge', 'xenbr2'], ['mac', '00:16:3e:55:a5:65']]), ('vkbd', ['vkbd']), ('vfb', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['display', 'localhost:10.0'], ['xauthority', '/root/.Xauthority']])], 'bootloader': '/usr/bin/pygrub', 'cpu': None, 'maxmem': None} [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:1264) XendDomainInfo.construct: None [2007-10-30 12:41:21 xend.XendDomainInfo 4121] DEBUG (XendDomainInfo:1296) XendDomainInfo.initDomain: 9 1.0 [2007-10-30 12:41:21 xend 4121] DEBUG (balloon:127) Balloon: 1049112 KiB free; need 1048576; done. [2007-10-30 12:41:21 xend 4121] INFO (image:136) buildDomain os=linux dom=9 vcpus=1 [2007-10-30 12:41:21 xend 4121] DEBUG (image:199) dom = 9 [2007-10-30 12:41:21 xend 4121] DEBUG (image:200) image = /var/lib/xen/vmlinuz.6u2e9w [2007-10-30 12:41:21 xend 4121] DEBUG (image:201) store_evtchn = 1 [2007-10-30 12:41:21 xend 4121] DEBUG (image:202) console_evtchn = 2 [2007-10-30 12:41:21 xend 4121] DEBUG (image:203) cmdline = ro root=/dev/xvda2 rhgb quiet [2007-10-30 12:41:21 xend 4121] DEBUG (image:204) ramdisk = /var/lib/xen/initrd.MpxKQP [2007-10-30 12:41:21 xend 4121] DEBUG (image:205) vcpus = 1 [2007-10-30 12:41:21 xend 4121] DEBUG (image:206) features = [2007-10-30 12:41:21 xend 4121] DEBUG (blkif:24) exception looking up device number for xvda: [Errno 2] No such file or directory: '/dev/xvda' -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Tue Oct 30 20:23:08 2007 From: clalance at redhat.com (Chris Lalancette) Date: Tue, 30 Oct 2007 16:23:08 -0400 Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <1104266.2282971193774542215.JavaMail.root@do8> References: <1104266.2282971193774542215.JavaMail.root@do8> Message-ID: <472792AC.4040506@redhat.com> Jim Klein wrote: > Am attempting to update a RHEL4 domU from a custom created Xen kernel > (created before RHEL5) to a supported kernel (2.6.9-55.0.9.ELxenU) and > RHEL5 host without success. For some reason, the kernel can no longer > find xvda. Boots fine on the old kernel and host, so I'm at a bit of a > loss. Host has other domUs booted off the same SAN, with no security > restrictions, so I don't see how it could be hardware. Copy of configs > and partial debug log below. Ideas? Hm, everything below, at a first glance, seems to be right. What does the console output look like from the RHEL-4 kernel (make sure to take rhgb quiet off of the command-line)? Chris Lalancette From xen.mails at gmail.com Tue Oct 30 21:31:19 2007 From: xen.mails at gmail.com (Anand Gupta) Date: Wed, 31 Oct 2007 03:01:19 +0530 Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <472792AC.4040506@redhat.com> References: <1104266.2282971193774542215.JavaMail.root@do8> <472792AC.4040506@redhat.com> Message-ID: I have had similar problems, at last i reverted to use sda instead of xvda. Also i am getting errors about /lib/tls even when its been renamed in dom0 and domU. Any ideas on this ? -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From jklein at saugus.k12.ca.us Tue Oct 30 21:41:44 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Tue, 30 Oct 2007 14:41:44 -0700 (PDT) Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <472792AC.4040506@redhat.com> Message-ID: <22988904.2302011193780504634.JavaMail.root@do8> Interesting: XENBUS: Device with no driver: device/vbd/2048 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 124k freed device-mapper: 4.5.5-ioctl ( 2006-12-01 ) initialised: dm-devel at redhat.com Kernel panic - not syncing: Attempted to kill init! Not sure where to go from here. ----- Original Message ----- From: "Chris Lalancette" To: "Jim Klein" Cc: "fedora-xen" Sent: Tuesday, October 30, 2007 1:23:08 PM (GMT-0800) America/Los_Angeles Subject: Re: [Fedora-xen] RHEL4 DomU Update Problem Jim Klein wrote: > Am attempting to update a RHEL4 domU from a custom created Xen kernel > (created before RHEL5) to a supported kernel (2.6.9-55.0.9.ELxenU) and > RHEL5 host without success. For some reason, the kernel can no longer > find xvda. Boots fine on the old kernel and host, so I'm at a bit of a > loss. Host has other domUs booted off the same SAN, with no security > restrictions, so I don't see how it could be hardware. Copy of configs > and partial debug log below. Ideas? Hm, everything below, at a first glance, seems to be right. What does the console output look like from the RHEL-4 kernel (make sure to take rhgb quiet off of the command-line)? Chris Lalancette -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Tue Oct 30 22:00:05 2007 From: clalance at redhat.com (Chris Lalancette) Date: Tue, 30 Oct 2007 18:00:05 -0400 Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <22988904.2302011193780504634.JavaMail.root@do8> References: <22988904.2302011193780504634.JavaMail.root@do8> Message-ID: <4727A965.9090501@redhat.com> Jim Klein wrote: > Interesting: > > XENBUS: Device with no driver: device/vbd/2048 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 124k freed > device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel at redhat.com > Kernel panic - not syncing: Attempted to kill init! > > Not sure where to go from here. > Believe it or not, those XENBUS errors are actually expected; the xenbus driver is loaded before the virtual disk/network drivers, and it sees that it has these nodes without drivers. However, that does lead me to an idea. If I remember correctly, the Xensource kernels have all of the drivers built-in, while we prefer to do things more modular. I'm guessing that you didn't have the right driver in /etc/modprobe.conf when the kernel was installed, so the initrd doesn't have the right drivers in it. So what you'll want to do is: 1) Boot the RHEL-4 domU into the (working) Xen kernel. 2) Edit /etc/modprobe.conf, and add: alias scsi_hostadapter xenblk 3) Remove the RedHat RHEL-4 kernel (rpm -e), and install it again, which should re-generate the initrd with the right stuff in it. Chris Lalancette From jklein at saugus.k12.ca.us Wed Oct 31 15:49:42 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Wed, 31 Oct 2007 08:49:42 -0700 (PDT) Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <4727A965.9090501@redhat.com> Message-ID: <18824090.2366861193845782646.JavaMail.root@do8> Now it's really interesting. If I just try to boot the system with the disk labeled xvda, I get a huge series of kernel panics (see below.) If I change it to sda (in both the config file and grub) it looks like it might work, but then I get: Freeing unused kernel memory: 124k freed SCSI subsystem initialized Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can't get major 8 with name sd vbd vbd-2048: 19 xlvbd_add at /local/domain/0/backend/vbd/27/2048 Registering block device major 8 register_blkdev: cannot get major 8 for sd xen_blk: can't get major 8 with name sd vbd vbd-2048: 19 xlvbd_add at /local/domain/0/backend/vbd/27/2048 XENBUS: Timeout connecting to device: device/vbd/2048 (state 6) device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel at redhat.com Kernel panic - not syncing: Attempted to kill init! FYI, this wasn't a Xensource kernel before, it was actually a Fedora 5 kernel (2.6.15-1.2054_FC5xenU) I created a yum repository for RHEL4 with the Fedora kernel, and used it to set up the box. Kernel panics (lots of them, all the same): kernel BUG at arch/i386/mm/pgtable-xen.c:306! invalid operand: 0000 [#1] SMP Modules linked in: ext3 jbd dm_mod xenblk sd_mod scsi_mod CPU: 0 EIP: 0061:[] Not tainted VLI EFLAGS: 00010282 (2.6.9-55.0.9.ELxenU) EIP is at pgd_ctor+0x1d/0x26 eax: fffffff4 ebx: 00000000 ecx: f5392000 edx: 00000000 esi: c19fdd80 edi: eca6aaa0 ebp: 00000001 esp: ecb3cd6c ds: 007b es: 007b ss: 0068 Process 10-udev.hotplug (pid: 398, threadinfo=ecb3c000 task=ecb2a070) Stack: c0141b69 ecb4b000 c19fdd80 00000001 ecb4b000 eca6aaa0 c19fdd80 c19fde40 c0141ceb c19fdd80 eca6aaa0 00000001 c19fdd80 eca6aaa0 ecb4b000 00000010 00000001 000000d0 c1a1b080 0000000c c19fde08 c19fdd80 c0141eda c19fdd80 Call Trace: [] cache_init_objs+0x35/0x56 [] cache_grow+0xfb/0x187 [] cache_alloc_refill+0x163/0x19c [] kmem_cache_alloc+0x67/0x97 [] pgd_alloc+0x17/0x336 [] mm_init+0xd7/0x116 [] mm_init+0xe7/0x116 [] copy_mm+0xbb/0x396 [] __cond_resched+0x14/0x3c [] copy_process+0x6b5/0xb0b [] do_fork+0x8a/0x16b [] error_code+0x2b/0x30 [] sys_clone+0x24/0x28 [] syscall_call+0x7/0xb Code: 74 02 66 a5 a8 01 74 01 a4 5e 5b 5e 5f c3 80 3d 04 07 2f c0 00 75 1c 6a 20 6a 00 ff 74 24 0c e8 ce 37 00 00 83 c4 0c 85 c0 74 08 <0f> 0b 32 01 b6 31 27 c0 c3 80 3d 04 07 2f c0 00 75 0d c7 44 24 <0>Fatal exception: panic in 5 seconds ----- Original Message ----- From: "Chris Lalancette" To: "Jim Klein" Cc: "fedora-xen" Sent: Tuesday, October 30, 2007 3:00:05 PM (GMT-0800) America/Los_Angeles Subject: Re: [Fedora-xen] RHEL4 DomU Update Problem Jim Klein wrote: > Interesting: > > XENBUS: Device with no driver: device/vbd/2048 > XENBUS: Device with no driver: device/vif/0 > Freeing unused kernel memory: 124k freed > device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel at redhat.com > Kernel panic - not syncing: Attempted to kill init! > > Not sure where to go from here. > Believe it or not, those XENBUS errors are actually expected; the xenbus driver is loaded before the virtual disk/network drivers, and it sees that it has these nodes without drivers. However, that does lead me to an idea. If I remember correctly, the Xensource kernels have all of the drivers built-in, while we prefer to do things more modular. I'm guessing that you didn't have the right driver in /etc/modprobe.conf when the kernel was installed, so the initrd doesn't have the right drivers in it. So what you'll want to do is: 1) Boot the RHEL-4 domU into the (working) Xen kernel. 2) Edit /etc/modprobe.conf, and add: alias scsi_hostadapter xenblk 3) Remove the RedHat RHEL-4 kernel (rpm -e), and install it again, which should re-generate the initrd with the right stuff in it. Chris Lalancette -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Wed Oct 31 16:25:52 2007 From: clalance at redhat.com (Chris Lalancette) Date: Wed, 31 Oct 2007 12:25:52 -0400 Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <18824090.2366861193845782646.JavaMail.root@do8> References: <18824090.2366861193845782646.JavaMail.root@do8> Message-ID: <4728AC90.2090804@redhat.com> Jim Klein wrote: > > Kernel panics (lots of them, all the same): > kernel BUG at arch/i386/mm/pgtable-xen.c:306! > invalid operand: 0000 [#1] > SMP > Modules linked in: ext3 jbd dm_mod xenblk sd_mod scsi_mod > CPU: 0 > EIP: 0061:[] Not tainted VLI > EFLAGS: 00010282 (2.6.9-55.0.9.ELxenU) > EIP is at pgd_ctor+0x1d/0x26 > eax: fffffff4 ebx: 00000000 ecx: f5392000 edx: 00000000 > esi: c19fdd80 edi: eca6aaa0 ebp: 00000001 esp: ecb3cd6c > ds: 007b es: 007b ss: 0068 > Process 10-udev.hotplug (pid: 398, threadinfo=ecb3c000 task=ecb2a070) > Stack: c0141b69 ecb4b000 c19fdd80 00000001 ecb4b000 eca6aaa0 c19fdd80 > c19fde40 > c0141ceb c19fdd80 eca6aaa0 00000001 c19fdd80 eca6aaa0 ecb4b000 > 00000010 > 00000001 000000d0 c1a1b080 0000000c c19fde08 c19fdd80 c0141eda > c19fdd80 > Call Trace: > [] cache_init_objs+0x35/0x56 > [] cache_grow+0xfb/0x187 > [] cache_alloc_refill+0x163/0x19c > [] kmem_cache_alloc+0x67/0x97 > [] pgd_alloc+0x17/0x336 > [] mm_init+0xd7/0x116 > [] mm_init+0xe7/0x116 > [] copy_mm+0xbb/0x396 > [] __cond_resched+0x14/0x3c > [] copy_process+0x6b5/0xb0b > [] do_fork+0x8a/0x16b > [] error_code+0x2b/0x30 > [] sys_clone+0x24/0x28 > [] syscall_call+0x7/0xb > Code: 74 02 66 a5 a8 01 74 01 a4 5e 5b 5e 5f c3 80 3d 04 07 2f c0 00 75 > 1c 6a 20 6a 00 ff 74 24 0c e8 ce 37 00 00 83 c4 0c 85 c0 74 08 <0f> 0b > 32 01 b6 31 27 c0 c3 80 3d 04 07 2f c0 00 75 0d c7 44 24 > <0>Fatal exception: panic in 5 seconds OK. This crash is a bug in the 4.5 kernel that I've now fixed. It should be fixed when 4.6 comes out. In the meantime, you probably should be able to work around this bug by reducing the amount of memory you are assigning to that domain. Chris Lalancette From xen.mails at gmail.com Wed Oct 31 19:37:59 2007 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 1 Nov 2007 01:07:59 +0530 Subject: [Fedora-xen] Error: (9, 'Bad file descriptor') Message-ID: Dom0 = centos 5 (32bit), 4GB Ram DomU = centos 5 (PV) (32bit) xen 3.1.2 rc1, compiled using XEN_TARGET_X86_PAE=Y kernel 2.6.18, modified to load areca card drivers initrd image created using the following command mkinitrd -v -f --with=aacraid --with=arcmsr --with=sd_mod --with=scsi_mod initrd-2.6.18-xen.img 2.6.18-xen When i issue xm create for a domU which was working earlier i get the following error xm create ldap Using config file "./ldap". Error: (9, 'Bad file descriptor') Log snippet when the error appears [2007-11-01 01:01:09 4605] ERROR (xmlrpclib2:178) Internal error handling xend.domain.create Traceback (most recent call last): File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/util/xmlrpclib2.py", line 131, in _marshaled_dispatch response = self._dispatch(method, params) File "/usr/lib/python2.4/SimpleXMLRPCServer.py", line 406, in _dispatch return func(*params) File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/server/XMLRPCServer.py", line 72, in domain_create info = XendDomain.instance().domain_create(config) File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/XendDomain.py", line 918, in domain_create self._refresh() File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/XendDomain.py", line 402, in _refresh self.domains[domid].update(dom, refresh_shutdown) File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 2198, in update self._update_consoles() File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 792, in _update_consoles self.console_port = self.readDom('console/port') File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/XendDomainInfo.py", line 845, in readDom return xstransact.Read(self.dompath, *args) File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 298, in Read return complete(path, lambda t: t.read(*args)) File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 352, in complete t = xstransact(path) File "/home/xen/xen-3.1-testing.hg/dist/install/usr/lib/python/xen/xend/xenstore/xstransact.py", line 21, in __init__ self.transaction = xshandle().transaction_start() Error: (9, 'Bad file descriptor') Config file kernel = "/boot/vmlinuz-2.6.18-xen" ramdisk = "/boot/initrd-2.6.18-xen.img" name = "ldap" memory = "1024" disk = [ 'phy:/dev/VolGroup00/ldap,sda1,w'] root = "/dev/sda1 ro" vif = [ 'mac=00:16:3e:12:34:a8, bridge=xenbr0', ] uuid = "bee5f62b-7193-a454-e37e-a151a5be8f45" vcpus=7 The above domU was booting up properly so i am guessing its an issue with the way i have setup xen. -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From xen.mails at gmail.com Wed Oct 31 19:51:31 2007 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 1 Nov 2007 01:21:31 +0530 Subject: [Fedora-xen] Re: Error: (9, 'Bad file descriptor') In-Reply-To: References: Message-ID: I also created a fresh domU using the wiki article located at http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU After this since i have to use lvm, i created a new lvm volume, mounted the file, copied the first partition contents to the lvm volume. Now when i try to boot the lvm volume, it gives me the below error mount: could not find filesystem '/dev/root' > Setting up other filesystems. > Setting up new root fs > setuproot: moving /dev failed: No such file or directory > no fstab.sys, mounting internal defaults > setuproot: error mounting /proc: No such file or directory > setuproot: error mounting /sys: No such file or directory > Switching to new root and running init. > unmounting old /dev > unmounting old /proc > unmounting old /sys > switchroot: mount failed: No such file or directory > Kernel panic - not syncing: Attempted to kill init! > Here is the config file name = "new2" memory = "512" disk = [ 'phy:/dev/VolGroup00/new2,xvda1,w',] vif = [ 'bridge=xenbr0', ] bootloader="/usr/bin/pygrub" vcpus=7 extra="single" on_reboot = 'restart' on_crash = 'restart' In the above i tried both xvda and xvda1, they give the same error. /etc/fstab inside the lvm volume /dev/xvda1 / ext3 defaults 1 1 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 Any pointers / ideas on how to fix the problems will be appreciated. -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From xen.mails at gmail.com Wed Oct 31 19:52:29 2007 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 1 Nov 2007 01:22:29 +0530 Subject: [Fedora-xen] Re: Error: (9, 'Bad file descriptor') In-Reply-To: References: Message-ID: Hmm.. somehow i am getting this now. Haven't changed any config of xen, and i am in /root, so why it should show that message. xm list Error: (9, 'Bad file descriptor') Usage: xm list [options] [Domain, ...] List information about all/some domains. -l, --long Output all VM details in SXP --label Include security labels --state= Select only VMs with the specified state -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From xen.mails at gmail.com Wed Oct 31 20:44:31 2007 From: xen.mails at gmail.com (Anand Gupta) Date: Thu, 1 Nov 2007 02:14:31 +0530 Subject: [Fedora-xen] Re: Error: (9, 'Bad file descriptor') In-Reply-To: References: Message-ID: Just did a reinstall of xen by running install.sh inside dist directory, and rebooted dom0, things turned back to normal xm list Name ID Mem VCPUs State Time(s) Domain-0 0 3011 8 r----- 134.9 Strange, but must be something i did... Now if the other problem can get resolved, i can put this box aside and concentrate on other servers :p On 11/1/07, Anand Gupta wrote: > > Hmm.. somehow i am getting this now. Haven't changed any config of xen, > and i am in /root, so why it should show that message. > > xm list > Error: (9, 'Bad file descriptor') > Usage: xm list [options] [Domain, ...] > > List information about all/some domains. > -l, --long Output all VM details in > SXP > --label Include security > labels > --state= Select only VMs with the specified > state > > > -- > regards, > > Anand Gupta -- regards, Anand Gupta -------------- next part -------------- An HTML attachment was scrubbed... URL: From jklein at saugus.k12.ca.us Wed Oct 31 21:10:03 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Wed, 31 Oct 2007 14:10:03 -0700 (PDT) Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <4728AC90.2090804@redhat.com> Message-ID: <21960519.2433571193865003091.JavaMail.root@do8> Thanks for the info - I'll look for the update. I still get the panic, regardless of memory settings. ----- Original Message ----- From: "Chris Lalancette" To: "Jim Klein" Cc: "fedora-xen" Sent: Wednesday, October 31, 2007 9:25:52 AM (GMT-0800) America/Los_Angeles Subject: Re: [Fedora-xen] RHEL4 DomU Update Problem Jim Klein wrote: > > Kernel panics (lots of them, all the same): > kernel BUG at arch/i386/mm/pgtable-xen.c:306! > invalid operand: 0000 [#1] > SMP > Modules linked in: ext3 jbd dm_mod xenblk sd_mod scsi_mod > CPU: 0 > EIP: 0061:[] Not tainted VLI > EFLAGS: 00010282 (2.6.9-55.0.9.ELxenU) > EIP is at pgd_ctor+0x1d/0x26 > eax: fffffff4 ebx: 00000000 ecx: f5392000 edx: 00000000 > esi: c19fdd80 edi: eca6aaa0 ebp: 00000001 esp: ecb3cd6c > ds: 007b es: 007b ss: 0068 > Process 10-udev.hotplug (pid: 398, threadinfo=ecb3c000 task=ecb2a070) > Stack: c0141b69 ecb4b000 c19fdd80 00000001 ecb4b000 eca6aaa0 c19fdd80 > c19fde40 > c0141ceb c19fdd80 eca6aaa0 00000001 c19fdd80 eca6aaa0 ecb4b000 > 00000010 > 00000001 000000d0 c1a1b080 0000000c c19fde08 c19fdd80 c0141eda > c19fdd80 > Call Trace: > [] cache_init_objs+0x35/0x56 > [] cache_grow+0xfb/0x187 > [] cache_alloc_refill+0x163/0x19c > [] kmem_cache_alloc+0x67/0x97 > [] pgd_alloc+0x17/0x336 > [] mm_init+0xd7/0x116 > [] mm_init+0xe7/0x116 > [] copy_mm+0xbb/0x396 > [] __cond_resched+0x14/0x3c > [] copy_process+0x6b5/0xb0b > [] do_fork+0x8a/0x16b > [] error_code+0x2b/0x30 > [] sys_clone+0x24/0x28 > [] syscall_call+0x7/0xb > Code: 74 02 66 a5 a8 01 74 01 a4 5e 5b 5e 5f c3 80 3d 04 07 2f c0 00 75 > 1c 6a 20 6a 00 ff 74 24 0c e8 ce 37 00 00 83 c4 0c 85 c0 74 08 <0f> 0b > 32 01 b6 31 27 c0 c3 80 3d 04 07 2f c0 00 75 0d c7 44 24 > <0>Fatal exception: panic in 5 seconds OK. This crash is a bug in the 4.5 kernel that I've now fixed. It should be fixed when 4.6 comes out. In the meantime, you probably should be able to work around this bug by reducing the amount of memory you are assigning to that domain. Chris Lalancette -------------- next part -------------- An HTML attachment was scrubbed... URL: From mwharris at lib.ucdavis.edu Wed Oct 31 23:52:33 2007 From: mwharris at lib.ucdavis.edu (Mike W. Harris) Date: Wed, 31 Oct 2007 16:52:33 -0700 (PDT) Subject: [Fedora-xen] Auto starting domains on boot with Fedora 7 dom0 Message-ID: <2092018272.318301193874753403.JavaMail.root@zebra.lib.ucdavis.edu> Hi, I have a Fedora 7 dom0 with a few domUs. I'd like to have some of them start when the physical machine reboots. This should be simple, I just put the config file in the /etc/xen/auto directory. Unfortunately we're using libvirt and virt-manager, so we don't have config files. virsh hasn't implemented auto start for xen machines, either. This seems like a pretty common thing to do, has anyone else had any luck? - Mike Harris - Systems University Library - UC Davis