From songtao.liu at mytum.de Fri Nov 2 08:53:21 2007 From: songtao.liu at mytum.de (Songtao Liu) Date: Fri, 02 Nov 2007 09:53:21 +0100 Subject: [Fedora-xen] HVM Xen guest CPUs allocation Message-ID: I use intel Core2 on my test PC. It seems that the configuration of Xen config file cpus="1" does not work,I want to set it load on processor1, but HVM guest will always load on processor0? Any one has ideas for this problem? Thanks From clalance at redhat.com Fri Nov 2 12:37:44 2007 From: clalance at redhat.com (Chris Lalancette) Date: Fri, 02 Nov 2007 08:37:44 -0400 Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <21960519.2433571193865003091.JavaMail.root@do8> References: <21960519.2433571193865003091.JavaMail.root@do8> Message-ID: <472B1A18.4020703@redhat.com> Jim Klein wrote: > Thanks for the info - I'll look for the update. I still get the panic, > regardless of memory settings. > Hm, OK. Can you try one of the kernels from here: http://people.redhat.com/~jbaron/rhel4/ These are the pre-release 4.6 kernels (not officially supported, of course), and should have the fix for your problem. Chris Lalancette From clalance at redhat.com Fri Nov 2 16:40:16 2007 From: clalance at redhat.com (Chris Lalancette) Date: Fri, 02 Nov 2007 12:40:16 -0400 Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <14878860.2581371194020827095.JavaMail.root@do8> References: <14878860.2581371194020827095.JavaMail.root@do8> Message-ID: <472B52F0.2030206@redhat.com> Jim Klein wrote: > Closer. It doesn't panic any more and even sees all the partitions and > mounts, but stalls at the following point: > > SCSI subsystem initialized > Registering block device major 202 > Using cfq io scheduler > xvda: xvda1 xvda2 xvda3 xvda4 < xvda5 > > device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel at redhat.com > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > SELinux: Disabled at runtime. > > Processor spins all the way up to 97 percent and sits there. An xm > shutdown works (md: stopping all md devices. md: md0 switched to > read-only mode. Power down.) so it seems to be stuck in a loop. OK. That probably means you are all the way booted, and just not seeing the init output. You can try one of two things here: 1) Add "console=xvc0" to the kernel command-line when booting the RHEL-4 kernel; that should force the init output to go to the serial console. 2) Use virt-manager to view the console. At least there you should be able to see what is going on. Chris Lalancette From jklein at saugus.k12.ca.us Fri Nov 2 16:36:54 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Fri, 2 Nov 2007 09:36:54 -0700 (PDT) Subject: [Fedora-xen] RHEL4 DomU Update Problem In-Reply-To: <472B52F0.2030206@redhat.com> Message-ID: <15080340.2583011194021414420.JavaMail.root@do8> You are correct! Sorry, forgot that RHEL5 Xen sent output in a different direction. All is well now - thanks a million! You just saved me countless hours migrating domains! ----- Original Message ----- From: "Chris Lalancette" To: "Jim Klein" Cc: "Fedora Xen" Sent: Friday, November 2, 2007 9:40:16 AM (GMT-0800) America/Los_Angeles Subject: Re: [Fedora-xen] RHEL4 DomU Update Problem Jim Klein wrote: > Closer. It doesn't panic any more and even sees all the partitions and > mounts, but stalls at the following point: > > SCSI subsystem initialized > Registering block device major 202 > Using cfq io scheduler > xvda: xvda1 xvda2 xvda3 xvda4 < xvda5 > > device-mapper: 4.5.5-ioctl (2006-12-01) initialised: dm-devel at redhat.com > kjournald starting. Commit interval 5 seconds > EXT3-fs: mounted filesystem with ordered data mode. > SELinux: Disabled at runtime. > > Processor spins all the way up to 97 percent and sits there. An xm > shutdown works (md: stopping all md devices. md: md0 switched to > read-only mode. Power down.) so it seems to be stuck in a loop. OK. That probably means you are all the way booted, and just not seeing the init output. You can try one of two things here: 1) Add "console=xvc0" to the kernel command-line when booting the RHEL-4 kernel; that should force the init output to go to the serial console. 2) Use virt-manager to view the console. At least there you should be able to see what is going on. Chris Lalancette -------------- next part -------------- An HTML attachment was scrubbed... URL: From accarlson at gmail.com Mon Nov 5 12:48:28 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Mon, 5 Nov 2007 10:48:28 -0200 Subject: [Fedora-xen] xen and lvm Message-ID: Hi! I'm using fedora 7 for both host and guests. I would like to be able to borrow unused space from one guest to be used in another one. Looking for how to do that I only found instructions from people that creates logical volumes and install the system using debootstrap. I would like to use virt-manager to install my guests with lvm. How can I do the partitioning for guests during my host install? Thanks in advance. Regards, -- Augusto From rjones at redhat.com Mon Nov 5 16:17:45 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 05 Nov 2007 16:17:45 +0000 Subject: [Fedora-xen] xen and lvm In-Reply-To: References: Message-ID: <472F4229.6050605@redhat.com> Augusto Castelan Carlson wrote: > I'm using fedora 7 for both host and guests. I would like to be able > to borrow unused space from one guest to be used in another one. > > Looking for how to do that I only found instructions from people that > creates logical volumes and install the system using debootstrap. I > would like to use virt-manager to install my guests with lvm. How can > I do the partitioning for guests during my host install? I think a number of separate issues to address here. The advantages of LVM when combined with virtualisation or Xen are that you can create guest partitions easily and flexibly, that they can have nice names, and that you can resize and also delete them simply. LVM also lets you do this flexibly across physical disks, add extra physical disks if you run out of space, and so on. So the basic command you need is: lvcreate -L 10G -n myguest VolGroup00 which would create a 10 GB partition called /dev/VolGroup00/myguest within an existing volume group called VolGroup00. (This isn't going to be a tutorial about LVM - there are plenty out there, go and use Google). With the partition created above, just use the name of the partition directly within the virt-manager creation dialog. Forthcoming versions of virt-manager will be able to do the provisioning of LVM storage more automatically. If you want to follow this work, take a look at libvir-list. This doesn't address directly your problem "to be able to borrow unused space from one guest to be used in another one". All that you'll get with basic LVM is the ability to resize one guest down and another guest up. If all your guests are "related" -- that is they are derived from say a single distribution, there are several options: run an NFS server and share parts of the guests' filesystems, eg. home directories or /usr if you're feeling adventurous. You could also look at LVM snapshotting, which will let guests "share" a single installation, but writes all modifications to their private partitions. The disadvantage of snapshotting is that although your guests start small, they grow indefinitely over time and later common changes cannot be shared. 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 keith at karsites.net Mon Nov 5 17:06:11 2007 From: keith at karsites.net (Keith Roberts) Date: Mon, 5 Nov 2007 17:06:11 +0000 (GMT) Subject: [Fedora-xen] Upgrading base Fedora installation with xen Message-ID: I'm wondering if it would be possible to upgrade from one version of Fedora to another newer version using xen, without any down-time, apart from rebooting the machine to activate the new installation? Something like this; 1) create a secondary linux root partition. 2) from the current active linux partition use xen to install the new version of Fedora on the secondary linux root partition. 3) compile and install any programs to /usr/local/xyz for the new kernel on the new linux root partition. 4) tweak and setup the new linux installation on the secondary partition, so it is ready to boot into. 5) reboot the machine so that the new Fedora root partition is now the active root partition. So in theory, going from an older Fedora root partition, to a completely new installation of Fedora would only incurr the downtime of having to reboot the machine, into the ready and functioning new Fedora installation on the new root partition? Is this possible, and has anyone tried it yet please? I got as far a running xen on my machine OK, but KDE and X crashed when I tried to do anything else. Kind Regards Keith Roberts ------------------------------------------------------------ http://www.karsites.net http://www.raised-from-the-dead.org.uk This email address is challenge-response protected with http://www.tmda.net ------------------------------------------------------------ From amos.shapira at gmail.com Mon Nov 5 21:28:37 2007 From: amos.shapira at gmail.com (Amos Shapira) Date: Tue, 6 Nov 2007 08:28:37 +1100 Subject: [Fedora-xen] Upgrading base Fedora installation with xen In-Reply-To: References: Message-ID: <9c2cca270711051328p582e3e10r7f606f8fdd713913@mail.gmail.com> On 06/11/2007, Keith Roberts wrote: > > I'm wondering if it would be possible to upgrade from one > version of Fedora to another newer version using xen, > without any down-time, apart from rebooting the machine to > activate the new installation? I'm not a Fedora expert (I'm from the Debian camp, where such a question is irrelevant :^), but I'm not sure that you need Xen to do this. Instead, I'd look around for: 1. "yum --installroot...". That's how I got a 64-bit Centos 4.4 running under Xen under Debian. See http://wiki.xensource.com/xenwiki/Centos4Yuminstallation 2. If jailtime.org has the version you want then download the image from there, dump it on an LVM volume using "dd", mount it and tweak it to boot with the programs you want. You might be able to test it using Xen (or Qemu?) before trying to boot it normally. The idea is that you don't have to hassle with setting up Xen just to get the installation process running - there could be simpler ways to get the basic file system layout on your disk. Cheers, --Amos -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian at herakles.homelinux.org Tue Nov 6 06:00:01 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 06 Nov 2007 15:00:01 +0900 Subject: [Fedora-xen] What is XendInvalidDomain? Message-ID: <473002E1.4000104@herakles.homelinux.org> Google shows where it was introduced (it maps to a xend_ error), but not what it means. Traceback (most recent call last): File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 140, in process resource = self.getResource() File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 172, in getResource return self.getServer().getResource(self) File "/usr/lib64/python2.5/site-packages/xen/web/httpserver.py", line 351, in getResource return self.root.getRequestResource(req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 39, in getRequestResource return findResource(self, req) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 26, in findResource next = resource.getPathResource(pathElement, request) File "/usr/lib64/python2.5/site-packages/xen/web/resource.py", line 49, in getPathResource val = self.getChild(path, request) File "/usr/lib64/python2.5/site-packages/xen/web/SrvDir.py", line 71, in getChild val = self.get(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 52, in get return self.domain(x) File "/usr/lib64/python2.5/site-packages/xen/xend/server/SrvDomainDir.py", line 44, in domain dom = self.xd.domain_lookup(x) File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 524, in domain_lookup raise XendInvalidDomain(str(domid)) XendInvalidDomain: I've been trying to run this command: virsh undefine ClarkConnect-4.2 probably you won't be surprised that virt-manager hangs too, and needs a little force from KDE. At one point I found it appropriate to killall sleep vtpm-delete as there were several of each apparently going noplace. I know of these: Nov 6 12:49:29 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:51:04 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:52:40 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:54:15 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:55:50 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:57:26 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 12:59:01 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:00:36 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:02:13 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:03:48 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:05:23 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:06:59 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:08:36 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:10:12 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:11:47 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:11:55 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:13:22 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:14:58 potoroo logger:last message repeated 2 times Nov 6 13:16:33 potoroo logger:last message repeated 2 times Nov 6 13:18:09 potoroo logger:last message repeated 2 times Nov 6 13:19:44 potoroo logger:last message repeated 2 times Nov 6 13:19:50 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:21:20 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Nov 6 13:22:55 potoroo logger:last message repeated 2 times Nov 6 13:24:31 potoroo logger:last message repeated 2 times Nov 6 13:26:06 potoroo logger:last message repeated 2 times Nov 6 13:27:42 potoroo logger:last message repeated 2 times Nov 6 13:29:17 potoroo logger:last message repeated 2 times Nov 6 13:30:53 potoroo logger:last message repeated 2 times Nov 6 13:32:28 potoroo logger:last message repeated 2 times but a little debugging code in /etc/xen/scripts/locking.sh hasn't case any light on my difficulties. I am running: [root at potoroo ~]# rpm -qf /etc/fedora-release /etc/xen/ /usr/bin/virt-manager fedora-release-8-2 xen-3.1.0-12.fc8 virt-manager-0.5.2-2.fc8 -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From debian at herakles.homelinux.org Tue Nov 6 06:20:09 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 06 Nov 2007 15:20:09 +0900 Subject: [Fedora-xen] What is XendInvalidDomain? In-Reply-To: <473002E1.4000104@herakles.homelinux.org> References: <473002E1.4000104@herakles.homelinux.org> Message-ID: <47300799.3070304@herakles.homelinux.org> John Summerfield wrote: > Google shows where it was introduced (it maps to a xend_ error), but not > but a little debugging code in /etc/xen/scripts/locking.sh hasn't case > any light on my difficulties. > > I am running: > [root at potoroo ~]# rpm -qf /etc/fedora-release /etc/xen/ > /usr/bin/virt-manager > fedora-release-8-2 > xen-3.1.0-12.fc8 > virt-manager-0.5.2-2.fc8 Would this be related, or is it something else? [root at potoroo ~]# /etc/init.d/xendomains restart Shutting down Xen domains: Name(save).!(shut)./etc/init.d/xendomains: line 306: 27462 Terminated watchdog_xm save !/etc/init.d/xendomains: line 188: 27473 Terminated watchdog_xm shutdown DebianEtch(save)/etc/init.d/xendomains: line 306: 27473 Terminated watchdog_xm shutdown .!(shut)./etc/init.d/xendomains: line 306: 27490 Terminated watchdog_xm save !/etc/init.d/xendomains: line 188: 27501 Terminated watchdog_xm shutdown /etc/init.d/xendomains: line 188: 27501 Terminated watchdog_xm shutdown FreeBSD-7(save)/etc/init.d/xendomains: line 306: 27501 Terminated watchdog_xm shutdown .!(shut)./etc/init.d/xendomains: line 306: 27525 Terminated watchdog_xm save !/etc/init.d/xendomains: line 188: 27536 Terminated watchdog_xm shutdown NetBSD-3.1(save)/etc/init.d/xendomains: line 306: 27536 Terminated watchdog_xm shutdown .!(shut)./etc/init.d/xendomains: line 306: 27553 Terminated watchdog_xm save !/etc/init.d/xendomains: line 188: 27564 Terminated watchdog_xm shutdown windows(save)/etc/init.d/xendomains: line 306: 27564 Terminated watchdog_xm shutdown .!(shut)./etc/init.d/xendomains: line 306: 27581 Terminated watchdog_xm save !/etc/init.d/xendomains: line 188: 27592 Terminated watchdog_xm shutdown SHUTDOWN_ALL ./etc/init.d/xendomains: line 306: 27592 Terminated watchdog_xm shutdown /etc/init.d/xendomains: line 306: 27613 Terminated watchdog_xm shutdown 1 [root at potoroo ~]# -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From accarlson at gmail.com Tue Nov 6 12:34:05 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Tue, 6 Nov 2007 10:34:05 -0200 Subject: [Fedora-xen] xen and lvm In-Reply-To: <472F4229.6050605@redhat.com> References: <472F4229.6050605@redhat.com> Message-ID: Hi! On 11/5/07, Richard W.M. Jones wrote: > The advantages of LVM when combined with virtualisation or Xen are that > you can create guest partitions easily and flexibly, that they can have > nice names, and that you can resize and also delete them simply. LVM > also lets you do this flexibly across physical disks, add extra physical > disks if you run out of space, and so on. > So the basic command you need is: > > lvcreate -L 10G -n myguest VolGroup00 > > which would create a 10 GB partition called /dev/VolGroup00/myguest > within an existing volume group called VolGroup00. (This isn't going to > be a tutorial about LVM - there are plenty out there, go and use Google). > > With the partition created above, just use the name of the partition > directly within the virt-manager creation dialog. Forthcoming versions > of virt-manager will be able to do the provisioning of LVM storage more > automatically. If you want to follow this work, take a look at libvir-list. > > This doesn't address directly your problem "to be able to borrow unused > space from one guest to be used in another one". All that you'll get > with basic LVM is the ability to resize one guest down and another guest up. I pointed /dev/VolGroup00/myguest within virt-manager and installed the guest. Suppose that I need to add an extra physical disk or instead of borrow, only resize one guest down and another guest up. I did a lvextend to add 1G to myguest, but how can I make my guest see that change? In lvm How To they use the command resize2fs to resize the filesystem, but I do not realize how to apply that changes to guests using LVM or partitioned by the guest installer. I tried to use the guest drive partitioned as /dev/xvda1 (boot), /dev/xvda2 (/) and /dev/xvda3 (/home) and also with LVM. How can I make the guest see that change? Thanks! Regards, -- Augusto From debian at herakles.homelinux.org Wed Nov 7 00:14:58 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 07 Nov 2007 09:14:58 +0900 Subject: [Fedora-xen] What is XendInvalidDomain? In-Reply-To: <47300799.3070304@herakles.homelinux.org> References: <473002E1.4000104@herakles.homelinux.org> <47300799.3070304@herakles.homelinux.org> Message-ID: <47310382.1080009@herakles.homelinux.org> John Summerfield wrote: > SHUTDOWN_ALL ./etc/init.d/xendomains: line 306: 27592 Terminated > watchdog_xm shutdown > /etc/init.d/xendomains: line 306: 27613 Terminated watchdog_xm shutdown 1 > [root at potoroo ~]# Have I offended folk? Does nobody know? Can't someone even tell me (nicely) where to go? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From dlbewley at lib.ucdavis.edu Wed Nov 7 01:59:13 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 6 Nov 2007 17:59:13 -0800 (PST) Subject: [Fedora-xen] xen and lvm In-Reply-To: Message-ID: <1428477277.451871194400753416.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Augusto Castelan Carlson" wrote: > On 11/5/07, Richard W.M. Jones wrote: > > The advantages of LVM when combined with virtualisation or Xen are > that > > you can create guest partitions easily and flexibly, that they can > have > > nice names, and that you can resize and also delete them simply. > LVM > > also lets you do this flexibly across physical disks, add extra > physical > > disks if you run out of space, and so on. > > > So the basic command you need is: > > > > lvcreate -L 10G -n myguest VolGroup00 > > > > which would create a 10 GB partition called /dev/VolGroup00/myguest > > within an existing volume group called VolGroup00. (This isn't > going to > > be a tutorial about LVM - there are plenty out there, go and use > Google). > > > > With the partition created above, just use the name of the > partition > > directly within the virt-manager creation dialog. Forthcoming > versions > > of virt-manager will be able to do the provisioning of LVM storage > more > > automatically. If you want to follow this work, take a look at > libvir-list. > > > > This doesn't address directly your problem "to be able to borrow > unused > > space from one guest to be used in another one". All that you'll > get > > with basic LVM is the ability to resize one guest down and another > guest up. > > I pointed /dev/VolGroup00/myguest within virt-manager and installed > the guest. > > Suppose that I need to add an extra physical disk or instead of > borrow, only resize one guest down and another guest up. > > I did a lvextend to add 1G to myguest, but how can I make my guest > see > that change? > In lvm How To they use the command resize2fs to resize the > filesystem, > but I do not realize how to apply that changes to guests using LVM or > partitioned by the guest installer. > > I tried to use the guest drive partitioned as /dev/xvda1 (boot), > /dev/xvda2 (/) and /dev/xvda3 (/home) and also with LVM. > > How can I make the guest see that change? If I understand... You created a LV called myguest in dom0 and within your domU you have used fdisk to partition /dev/xvda and layered LVM on top of one of those partitions. Now you've expanded myguest and want to see that space gain in the domU. I think what you should have done is turn /dev/xvda into a PV inside your domU. At that point you can use pvresize in your domU to take advantage of any space you may add to the myguest LV in dom0. I'm not sure how you'd account for a change in /dev/xvda otherwise. Someone else may know. In your domU, you are working at the device level below the filesystem level. Resizefs doesn't immediately come into play. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From debian at herakles.homelinux.org Wed Nov 7 04:24:42 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 07 Nov 2007 13:24:42 +0900 Subject: [Fedora-xen] f7 guest on f8t3 Message-ID: <47313E0A.3050700@herakles.homelinux.org> This is my command line, it's similar to one that worked for Debian etch and ClarkConnect 4.2 (and Windows XP): virt-install --name=Fedora7 --ram=384 --vcpus=2 --file=/var/lib/xen/images/Fedora7.img --file-size=4 --vnc --hvm --cdrom=/net/ns/var/local/mirrors/linux/Fedora/7/Fedora/x86_64/iso/F-7-x86_64-DVD.iso --os-type=linux os-variant=fedora7 Windows is fine Debian's fine ClarkConnect's fine f7 took ages loading ata_piix4 (actually it was a little further than this, that's just want was on the install screen). Ages > half an hour after which I went off to lunch. I cam back and, to my pleasant surprise, it was at the "choose your language" screen. From there things went smoothly until I chose to install from my CDROM which, of course, is that NFS mount I just booted from. Just to be absolutely clear: The host CPU is EMT-64 and virtualisation-capable. It's running 64-bit Linux. selinux is in whingealotmode, not enforcing. It's whingeing a lot, but that's for another time. The ISO image is automounted, and as it booted and loaded some stuff off it, it seems clear to me that access is fine. I've looked at the list's archive, the closest I found is an unaswered question from Greg Huber on June 13. I'm running xen 3.1, he had 3.0.? and he got much further than I can. A lot of possibly-relevant messages scrolled of the screen (fortunately I said "vga=791" so I have a reasonable number), but I can see kernel messages back to its recognising sda. There's nothing to suggest it found the virtual DVD-ROM drive. I'll scout around for some IA32 binaries, it doesn't matter a lot which I install for the purpose of this test. In the meantime, are there any pointers? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From debian at herakles.homelinux.org Wed Nov 7 04:43:39 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 07 Nov 2007 13:43:39 +0900 Subject: [Fedora-xen] f7 guest on f8t3 In-Reply-To: <47313E0A.3050700@herakles.homelinux.org> References: <47313E0A.3050700@herakles.homelinux.org> Message-ID: <4731427B.1040607@herakles.homelinux.org> John Summerfield wrote: > > This is my command line, it's similar to one that worked for Debian etch > and ClarkConnect 4.2 (and Windows XP): > > virt-install --name=Fedora7 --ram=384 --vcpus=2 > --file=/var/lib/xen/images/Fedora7.img --file-size=4 --vnc --hvm > --cdrom=/net/ns/var/local/mirrors/linux/Fedora/7/Fedora/x86_64/iso/F-7-x86_64-DVD.iso > --os-type=linux os-variant=fedora7 > > Windows is fine > Debian's fine > ClarkConnect's fine > > f7 took ages loading ata_piix4 (actually it was a little further than > this, that's just want was on the install screen). Ages > half an hour > after which I went off to lunch. The screen shot's like this, but a different module. This has been running for ages before the other screen shots. http://58.6.192.22/f1.png > A lot of possibly-relevant messages scrolled of the screen (fortunately > I said "vga=791" so I have a reasonable number), but I can see kernel > messages back to its recognising sda. There's nothing to suggest it > found the virtual DVD-ROM drive. I may have misinterpreted something, there's something about ata2 in the messages. Screen shots at http://58.6.192.22/f2.png http://58.6.192.22/f3.png -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From profosslists at gmail.com Wed Nov 7 09:06:43 2007 From: profosslists at gmail.com (=?ISO-8859-1?Q?Rapha=EBl_Bauduin?=) Date: Wed, 7 Nov 2007 10:06:43 +0100 Subject: [Fedora-xen] Profoss virtualisation call for papers Message-ID: <6d9aab700711070106mf519d54n3b7346d8ee15a4fe@mail.gmail.com> Hi, Profoss is organising events to spread objective information about professional uses of Free and Open Source based solutions, and is looking for speakers for its next event about virtualisation, taking place in Brussels on 22nd and 23rd january. If you have deployed a Free or Open Source virtualisation technology in a demanding professional environment, if you're a services company with extended expertise with virtualisation, or if you have developed a virtualisation software under an open source license, or built a product based on open source technology, and want to share your experience with your peers, please don't hesitate to submit your proposal as described below. Talks should not be commercial shows, but bring interesting information for professional ICT users, based on real world experience. It is not a xen specific event. Each speaker get a 50 minutes slot, and talks are to be given in english. Travel and hotel costs for speakers are taken in charge by the organisation. Please submit your proposal at http://www.profoss.eu/events/january-2008-virtualisation/call-for-papers If you have further questions, don't hesitate to send a mail to info at profoss dot eu thanks Raph From rjones at redhat.com Wed Nov 7 12:03:24 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 07 Nov 2007 12:03:24 +0000 Subject: [Fedora-xen] xen and lvm In-Reply-To: References: <472F4229.6050605@redhat.com> Message-ID: <4731A98C.2010309@redhat.com> Augusto Castelan Carlson wrote: > I did a lvextend to add 1G to myguest, but how can I make my guest see > that change? > In lvm How To they use the command resize2fs to resize the filesystem, > but I do not realize how to apply that changes to guests using LVM or > partitioned by the guest installer. > > I tried to use the guest drive partitioned as /dev/xvda1 (boot), > /dev/xvda2 (/) and /dev/xvda3 (/home) and also with LVM. > > How can I make the guest see that change? I think pvresize is the command (in the guest). However I'd strongly suggest that you take a look at a few FAQs and HOWTOs, for example: http://tldp.org/HOWTO/LVM-HOWTO/index.html http://tldp.org/HOWTO/LVM-HOWTO/extendlv.html Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Wed Nov 7 12:05:32 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 07 Nov 2007 12:05:32 +0000 Subject: [Fedora-xen] What is XendInvalidDomain? In-Reply-To: <47310382.1080009@herakles.homelinux.org> References: <473002E1.4000104@herakles.homelinux.org> <47300799.3070304@herakles.homelinux.org> <47310382.1080009@herakles.homelinux.org> Message-ID: <4731AA0C.30500@redhat.com> John Summerfield wrote: > John Summerfield wrote: > >> SHUTDOWN_ALL ./etc/init.d/xendomains: line 306: 27592 Terminated >> watchdog_xm shutdown >> /etc/init.d/xendomains: line 306: 27613 Terminated watchdog_xm shutdown 1 >> [root at potoroo ~]# > > Have I offended folk? > Does nobody know? > Can't someone even tell me (nicely) where to go? I read the initial report, but there wasn't really enough information to help. Restart the machine and tell us what operation(s) fails, with what error messages, and what you were expecting it to do. 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 ametzger at silkspeed.com Wed Nov 7 13:29:37 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Wed, 07 Nov 2007 08:29:37 -0500 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart Message-ID: <4731BDC1.8050902@silkspeed.com> I am trying to migrate my virtualization infrastructure from a pure Xen implementation to the more versatile Fedora virt-manager Xen/KVM environment. While doing this, I have hit some snags related to areas in which pure Xen documentation no longer applies due to the presence of lib-virt et al. First a minor comment on the Fedora8VirtQuickStart (draft I know): The section: > Building a Fedora Guest System using `virt-manager` no longer applies because between Fedora 7 and Fedora 8 there no longer appears to be a "New" button or a "File New" option in virt-manager. It would appear that the only way to create a DomU is by way of virt-install. Now, my problem. I have successfully created fully functional guest VMs which work perfectly in every way but, in the context of lib-virt and virsh, I can not figure out how to get the guest machines to be started automatically when the host machine boots. In a pure Xen environment, you symbolically link the "/etc/xen/" file into "/etc/xen/auto". After using virt-install to create the guest, the domain configuration files end up over in "/var/lib/xend/domains". I have tried to symbolically link the whole domain directory to "/etc/xen/auto", I have tried to link the configuration file to "/etc/xen/auto". I have tried to export the configuration as XML using virsh and then put that under "/etc/xen/auto". Nothing works and there is no indication from the xend.log that it is even trying to start the guest domains on bootup. I also tried to use: virsh autostart and get the error: libvir: error : this function is not supported by the hypervisor: virDomainSetAutostart So, my question is, is it possible to properly manage the start up and shut down of guest domains on host start up and shutdown or is that just not supported yet. If there is a way to do this, it would be a very helpful section to add to the Quick Start document because I would expect anyone migrating from a pure Xen environment to have the same issue. Google reveals that several have asked this question in the past on Fedora 7 etc and I have not seen any answer other than people suggesting to link the configuration file under "/etc/xen/auto". Thanks, Aaron From ametzger at silkspeed.com Wed Nov 7 14:56:27 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Wed, 07 Nov 2007 09:56:27 -0500 Subject: [Fedora-xen] Restore Failed In-Reply-To: <4731BDC1.8050902@silkspeed.com> References: <4731BDC1.8050902@silkspeed.com> Message-ID: <4731D21B.2090905@silkspeed.com> In my previous post, I was asking questions about how to get guest VMs to cleanly shutdown and start back up when the host shuts down and starts back up. > Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart I have made some progress on this issue by complete accident. Previously I had a Fedora7 guest stored in an LVM partition. I just tried a Fedora8-RC3 guest stored in a regular file. Now the behavior is that if the guest is running when the host is shut down, it appears to try to start it back up after the host boots back up. BUT, the guest restore fails with the following: I would greatly appreciate any tips on how to stabilize this environment to get clean guest shutdowns and start ups when the host shuts down and starts up. Thanks in advance. > [2007-11-07 09:45:40 2414] INFO (SrvDaemon:338) Xend Daemon started > [2007-11-07 09:45:40 2414] INFO (SrvDaemon:342) Xend changeset: unavailable. > [2007-11-07 09:45:40 2414] INFO (SrvDaemon:349) Xend version: Unknown. > [2007-11-07 09:45:40 2414] DEBUG (XendDomainInfo:126) XendDomainInfo.recreate({'max_vcpu_id': 3, 'cpu_time': 12024165224L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0, 'online_vcpus': 4, 'domid': 0, 'paused': 0, 'crashed': 0, 'running': 1, 'maxmem_kb': 17179869180L, 'shutdown': 0, 'mem_kb': 8124200L, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'blocked': 0, 'name': 'Domain-0'}) > [2007-11-07 09:45:40 2414] INFO (XendDomainInfo:143) Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000. at /local/domain/0 > [2007-11-07 09:45:40 2414] DEBUG (XendDomainInfo:2026) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_reboot': 'restart', 'image': '(linux (kernel ))', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '4', 'vcpu_avail': '15', 'name': 'Domain-0'} > [2007-11-07 09:45:40 2414] DEBUG (XendDomainInfo:875) Storing domain details: {'cpu/3/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '8124200', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} > [2007-11-07 09:45:40 2414] DEBUG (XendDomain:443) Adding Domain: 0 > [2007-11-07 09:45:40 2414] DEBUG (XendDomain:379) number of vcpus to use is 0 > [2007-11-07 09:45:40 2414] DEBUG (XendDomainInfo:875) Storing domain details: {'cpu/3/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '8124200', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} > [2007-11-07 09:45:40 2414] DEBUG (XendDomainInfo:959) XendDomainInfo.handleShutdownWatch > [2007-11-07 09:45:40 2414] DEBUG (XendDomainInfo:233) XendDomainInfo.createDormant({'vcpus_params': {}, 'PV_args': '', 'features': '', 'cpus': [], 'devices': {'9138bd07-7b37-af28-37ce-e9303b5c6f8d': ('vfb', {'vncunused': '1', 'other_config': {'vncunused': '1', 'type': 'vnc'}, 'type': 'vnc', 'uuid': '9138bd07-7b37-af28-37ce-e9303b5c6f8d'}), '2f1154f7-b1fc-e94f-3ebc-a7ec9b8e2977': ('vkbd', {'uuid': '2f1154f7-b1fc-e94f-3ebc-a7ec9b8e2977', 'backend': '0'}), '91c7caa0-3dfa-fc65-a81e-b76c88fe321f': ('vbd', {'uuid': '91c7caa0-3dfa-fc65-a81e-b76c88fe321f', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'xvda:disk', 'uname': 'file:/root/subversion.vm', 'mode': 'w', 'backend': '0'}), '2a06c796-f2a2-c96b-bd33-383ccf9a731a': ('vif', {'bridge': 'eth0', 'mac': '00:16:3e:1f:a4:ec', 'script': 'vif-bridge', 'uuid': '2a06c796-f2a2-c96b-bd33-383ccf9a731a', 'backend': '0'})}, 'vcpu_avail': 1L, 'VCPUs_live': 1, 'PV_bootloader': '/usr/bin/pygrub', 'actions_after_crash': 'restart', 'vbd_refs' : ['91c7caa0-3dfa-fc65-a81e-b76c88fe321f'], 'PV_ramdisk': '', 'is_control_domain': False, 'name_label': 'subversion', 'VCPUs_at_startup': 1, 'HVM_boot_params': {}, 'platform': {'rtc_timeoffset': '0'}, 'cpu_weight': 256, 'console_refs': ['9138bd07-7b37-af28-37ce-e9303b5c6f8d'], 'cpu_cap': 0, 'vif_refs': ['2a06c796-f2a2-c96b-bd33-383ccf9a731a'], 'on_xend_stop': 'ignore', 'memory_static_min': 0, 'HVM_boot_policy': '', 'VCPUs_max': 1, 'start_time': 1194445904.5699999, 'memory_static_max': 1073741824, 'actions_after_shutdown': 'destroy', 'on_xend_start': 'ignore', 'memory_dynamic_max': 1073741824, 'actions_after_suspend': '', 'is_a_template': False, 'memory_dynamic_min': 1073741824, 'uuid': '7b6bbe1a-6669-7e7e-b17a-c5d0562b4e59', 'PV_kernel': '', 'cpu_time': 39.113985640999999, 'shadow_memory': 0, 'PV_bootloader_args': '', 'notes': {'HV_START_LOW': '4118806528', 'FEATURES': 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode _kernel', 'VIRT_BASE': '3221225472', 'GUEST_VERSION': '2.6', 'PADDR_OFFSET': '3221225472', 'GUEST_OS': 'linux', 'HYPERCALL_PAGE': '3238006784', 'LOADER': 'generic', 'SUSPEND_CANCEL': '1', 'PAE_MODE': 'yes', 'ENTRY': '3238002688', 'XEN_VERSION': 'xen-3.0'}, 'other_config': {}, 'actions_after_reboot': 'restart', 'status': '1', 'vtpm_refs': [], 'security': None}) > [2007-11-07 09:45:40 2414] ERROR (XendDomainInfo:2332) bridge_to_network > Traceback (most recent call last): > File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 2330, in get_dev_xenapi_config > config.get('bridge')).get_uuid() > File "/usr/lib64/python2.5/site-packages/xen/xend/XendNode.py", line 510, in bridge_to_network > raise Exception('Cannot find network for bridge %s' % bridge) > Exception: Cannot find network for bridge eth0 > [2007-11-07 09:45:40 2414] INFO (SrvServer:180) unix path=/var/lib/xend/xend-socket > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VBD.set_device not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VBD.set_mode not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VBD.set_type not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VM.get_auto_power_on not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VM.set_auto_power_on not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VM.set_VCPUs_max not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VM.set_VCPUs_at_startup not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: debug.get_all not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: console.get_other_config not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: console.set_other_config not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VIF.get_network not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VIF.set_device not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VIF.set_MAC not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: VIF.set_MTU not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: session.get_all_records not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: event.get_record not found > [2007-11-07 09:45:40 2414] WARNING (XendAPI:672) API call: event.get_all not found > [2007-11-07 09:45:43 2414] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xen-api.sock; authentication has been disabled for this server. > [2007-11-07 09:45:43 2414] INFO (XMLRPCServer:149) Opening Unix domain socket XML-RPC server on /var/run/xend/xmlrpc.sock. > [2007-11-07 09:45:44 2414] DEBUG (XendDomainInfo:210) XendDomainInfo.restore(['domain', ['domid', '4'], ['on_crash', 'restart'], ['uuid', '7b6bbe1a-6669-7e7e-b17a-c5d0562b4e59'], ['bootloader_args'], ['vcpus', '1'], ['name', 'subversion'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['bootloader', '/usr/bin/pygrub'], ['maxmem', '1024'], ['memory', '1024'], ['shadow_memory', '0'], ['vcpu_avail', '1'], ['cpu_weight', '256'], ['cpu_cap', '0'], ['features'], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['start_time', '1194445904.57'], ['cpu_time', '19.492313782'], ['online_vcpus', '1'], ['image', ['linux', ['kernel'], ['rtc_timeoffset', '0'], ['notes', ['HV_START_LOW', '4118806528'], ['FEATURES', 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel'], ['VIRT_BASE', '3221225472'], ['GUEST_VERSION', '2.6'], ['PADDR_OFFSET', '3221225472'], ['GUEST_OS', 'linux'], ['HYPERCALL_PAGE', '3238006784'], [ 'LOADER', 'generic'], ['SUSPEND_CANCEL', '1'], ['PAE_MODE', 'yes'], ['ENTRY', '3238002688'], ['XEN_VERSION', 'xen-3.0']]]], ['status', '2'], ['state', '-b----'], ['store_mfn', '2154297'], ['console_mfn', '2154296'], ['device', ['vif', ['bridge', 'eth0'], ['mac', '00:16:3e:1f:a4:ec'], ['script', 'vif-bridge'], ['uuid', '2a06c796-f2a2-c96b-bd33-383ccf9a731a'], ['backend', '0']]], ['device', ['vbd', ['uname', 'file:/root/subversion.vm'], ['uuid', '91c7caa0-3dfa-fc65-a81e-b76c88fe321f'], ['mode', 'w'], ['dev', 'xvda:disk'], ['backend', '0'], ['bootable', '1']]], ['device', ['vkbd', ['backend', '0']]], ['device', ['vfb', ['vncunused', '1'], ['type', 'vnc'], ['uuid', '9138bd07-7b37-af28-37ce-e9303b5c6f8d']]]]) > [2007-11-07 09:45:44 2414] DEBUG (XendDomainInfo:1465) XendDomainInfo.constructDomain > [2007-11-07 09:45:44 2414] DEBUG (balloon:113) Balloon: 131072 KiB free; need 2048; done. > [2007-11-07 09:45:44 2414] DEBUG (XendDomain:443) Adding Domain: 1 > [2007-11-07 09:45:44 2414] DEBUG (XendDomainInfo:2026) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '7b6bbe1a-6669-7e7e-b17a-c5d0562b4e59', 'on_reboot': 'restart', 'start_time': '1194445904.57', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel ) (rtc_timeoffset 0) (notes (HV_START_LOW 4118806528) (FEATURES 'writable_page_tables|writable_descriptor_tables|auto_translated_physmap|pae_pgdir_above_4gb|supervisor_mode_kernel') (VIRT_BASE 3221225472) (GUEST_VERSION 2.6) (PADDR_OFFSET 3221225472) (GUEST_OS linux) (HYPERCALL_PAGE 3238006784) (LOADER generic) (SUSPEND_CANCEL 1) (PAE_MODE yes) (ENTRY 3238002688) (XEN_VERSION xen-3.0)))", 'name': 'subversion'} > [2007-11-07 09:45:44 2414] INFO (XendDomainInfo:1367) createDevice: vkbd : {'uuid': '417e4cd7-3e82-a982-ff62-53a0b89fb649', 'backend': '0'} > [2007-11-07 09:45:44 2414] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vkbd/1/0'} to /local/domain/1/device/vkbd/0. > [2007-11-07 09:45:44 2414] DEBUG (DevController:117) DevController: writing {'frontend-id': '1', 'domain': 'subversion', 'frontend': '/local/domain/1/device/vkbd/0', 'state': '1', 'online': '1'} to /local/domain/0/backend/vkbd/1/0. > [2007-11-07 09:45:44 2414] INFO (XendDomainInfo:1367) createDevice: vfb : {'vncunused': '1', 'other_config': {'vncunused': '1', 'type': 'vnc'}, 'type': 'vnc', 'uuid': '9138bd07-7b37-af28-37ce-e9303b5c6f8d'} > [2007-11-07 09:45:44 2414] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vfb/1/0'} to /local/domain/1/device/vfb/0. > [2007-11-07 09:45:44 2414] DEBUG (DevController:117) DevController: writing {'vncunused': '1', 'domain': 'subversion', 'frontend': '/local/domain/1/device/vfb/0', 'uuid': '9138bd07-7b37-af28-37ce-e9303b5c6f8d', 'state': '1', 'online': '1', 'frontend-id': '1', 'type': 'vnc'} to /local/domain/0/backend/vfb/1/0. > [2007-11-07 09:45:44 2414] DEBUG (vfbif:78) No VNC passwd configured for vfb access > [2007-11-07 09:45:44 2414] DEBUG (vfbif:9) Spawn: ['/usr/lib64/xen/bin/qemu-dm', '-M', 'xenpv', '-d', '1', '-domain-name', 'subversion', '-vnc', '127.0.0.1:0', '-vncunused'] > [2007-11-07 09:45:44 2414] INFO (XendDomainInfo:1367) createDevice: vbd : {'uuid': '91c7caa0-3dfa-fc65-a81e-b76c88fe321f', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'xvda:disk', 'uname': 'file:/root/subversion.vm', 'mode': 'w', 'backend': '0'} > [2007-11-07 09:45:44 2414] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'virtual-device': '51712', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/51712'} to /local/domain/1/device/vbd/51712. > [2007-11-07 09:45:44 2414] DEBUG (DevController:117) DevController: writing {'domain': 'subversion', 'frontend': '/local/domain/1/device/vbd/51712', 'uuid': '91c7caa0-3dfa-fc65-a81e-b76c88fe321f', 'dev': 'xvda', 'state': '1', 'params': '/root/subversion.vm', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/51712. > [2007-11-07 09:45:44 2414] INFO (XendDomainInfo:1367) createDevice: vif : {'bridge': 'eth0', 'mac': '00:16:3e:1f:a4:ec', 'script': 'vif-bridge', 'uuid': '2a06c796-f2a2-c96b-bd33-383ccf9a731a', 'backend': '0'} > [2007-11-07 09:45:44 2414] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:1f:a4:ec', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. > [2007-11-07 09:45:44 2414] DEBUG (DevController:117) DevController: writing {'bridge': 'eth0', 'domain': 'subversion', 'handle': '0', 'uuid': '2a06c796-f2a2-c96b-bd33-383ccf9a731a', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:1f:a4:ec', 'online': '1', 'frontend-id': '1'} to /local/domain/0/backend/vif/1/0. > [2007-11-07 09:45:44 2414] DEBUG (XendDomainInfo:875) Storing domain details: {'image/entry': '3238002688', 'console/port': '2', 'image/loader': 'generic', 'vm': '/vm/7b6bbe1a-6669-7e7e-b17a-c5d0562b4e59', 'control/platform-feature-multiprocessor-suspend': '1', 'image/hv-start-low': '4118806528', 'image/guest-os': 'linux', 'image/features/writable-descriptor-tables': '1', 'image/virt-base': '3221225472', 'memory/target': '1048576', 'image/guest-version': '2.6', 'image/features/supervisor-mode-kernel': '1', 'image/pae-mode': 'yes', 'console/limit': '1048576', 'image/paddr-offset': '3221225472', 'image/hypercall-page': '3238006784', 'image/suspend-cancel': '1', 'cpu/0/availability': 'online', 'image/features/pae-pgdir-above-4gb': '1', 'image/features/writable-page-tables': '1', 'image/features/auto-translated-physmap': '1', 'name': 'subversion', 'domid': '1', 'image/xen-version': 'xen-3.0', 'store/port': '1'} > [2007-11-07 09:45:44 2414] DEBUG (XendCheckpoint:202) restore:shadow=0x0, _static_max=0x40000000, _static_min=0x0, > [2007-11-07 09:45:44 2414] DEBUG (balloon:119) Balloon: 131064 KiB free; 0 to scrub; need 1048576; retries: 20. > [2007-11-07 09:45:44 2414] DEBUG (balloon:134) Balloon: setting dom0 target to 7037 MiB. > [2007-11-07 09:45:44 2414] DEBUG (XendDomainInfo:583) Setting memory target of domain Domain-0 (0) to 7037 MiB. > [2007-11-07 09:45:44 2414] DEBUG (XendDomainInfo:875) Storing domain details: {'cpu/3/availability': 'online', 'name': 'Domain-0', 'console/limit': '1048576', 'memory/target': '7205888', 'cpu/2/availability': 'online', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availability': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} > [2007-11-07 09:45:45 2414] DEBUG (balloon:113) Balloon: 1049376 KiB free; need 1048576; done. > [2007-11-07 09:45:45 2414] DEBUG (XendCheckpoint:214) [xc_restore]: /usr/lib64/xen/bin/xc_restore 4 1 1 2 0 0 0 > [2007-11-07 09:45:45 2414] INFO (XendCheckpoint:350) xc_domain_restore start: p2m_size = 40800 > [2007-11-07 09:45:45 2414] INFO (XendCheckpoint:350) ERROR Internal error: read extended-info signature failed > [2007-11-07 09:45:45 2414] INFO (XendCheckpoint:350) Restore exit with rc=1 > [2007-11-07 09:45:45 2414] DEBUG (XendDomainInfo:1713) XendDomainInfo.destroy: domid=1 > [2007-11-07 09:45:45 2414] DEBUG (XendDomainInfo:1730) XendDomainInfo.destroyDomain(1) > [2007-11-07 09:45:45 2414] ERROR (XendDomainInfo:1742) XendDomainInfo.destroy: xc.domain_destroy failed. > Traceback (most recent call last): > File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomainInfo.py", line 1736, in destroyDomain > xc.domain_destroy(self.domid) > Error: (3, 'No such process') > [2007-11-07 09:45:45 2414] ERROR (XendDomain:1104) Restore failed > Traceback (most recent call last): > File "/usr/lib64/python2.5/site-packages/xen/xend/XendDomain.py", line 1099, in domain_restore_fd > return XendCheckpoint.restore(self, fd, paused=paused) > File "/usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line 218, in restore > forkHelper(cmd, fd, handler.handler, True) > File "/usr/lib64/python2.5/site-packages/xen/xend/XendCheckpoint.py", line 338, in forkHelper > raise XendError("%s failed" % string.join(cmd)) > XendError: /usr/lib64/xen/bin/xc_restore 4 1 1 2 0 0 0 failed From ametzger at silkspeed.com Wed Nov 7 15:38:02 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Wed, 07 Nov 2007 10:38:02 -0500 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <47324ed80711070726x77cf1385l5b33d4c82a2c7329@mail.gmail.com> References: <4731BDC1.8050902@silkspeed.com> <47324ed80711070726x77cf1385l5b33d4c82a2c7329@mail.gmail.com> Message-ID: <4731DBDA.20009@silkspeed.com> yonas Abraham wrote: >> >> So, my question is, is it possible to properly manage the start up and >> shut down of guest domains on host start up and shutdown or is that just >> not supported yet. >> >> If there is a way to do this, it would be a very helpful section to add >> to the Quick Start document because I would expect anyone migrating from >> a pure Xen environment to have the same issue. Google reveals that >> several have asked this question in the past on Fedora 7 etc and I have >> not seen any answer other than people suggesting to link the >> configuration file under "/etc/xen/auto". >> >> Thanks, >> Aaron > > > I am in same boat as you. I want to know how to atuo start an image in > F7 or F8. I have seen this question asked several times and I have > seen no answer. May be it is not posible to do it. > I think I have it figured out! Edit your "/var/lib/xend/domains//config.sxp" file. Look for the lines containing (on_xend_start ignore) (on_xend_stp ignore) and change them to be (on_xend_start start) (on_xend_stop shutdown) This will restart the domain when the xend daemon starts. Mine still fails for the case where I "reboot" the host instead of shutdown, powerup because it seems like it can not restart from the virtual machine image saved in "/var/lib/xen/save". I tried to post a log file with that failure to this list but it looks like the e-mail was to large to post or something because it hasn't shown up in this list yet. At least now I have a solution which will work when my UPS shuts down the server during a power outage. -- Aaron From debian at herakles.homelinux.org Wed Nov 7 22:06:29 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 08 Nov 2007 07:06:29 +0900 Subject: [Fedora-xen] What is XendInvalidDomain? In-Reply-To: <4731AA0C.30500@redhat.com> References: <473002E1.4000104@herakles.homelinux.org> <47300799.3070304@herakles.homelinux.org> <47310382.1080009@herakles.homelinux.org> <4731AA0C.30500@redhat.com> Message-ID: <473236E5.9040609@herakles.homelinux.org> Richard W.M. Jones wrote: > John Summerfield wrote: >> John Summerfield wrote: >> >>> SHUTDOWN_ALL ./etc/init.d/xendomains: line 306: 27592 Terminated >>> watchdog_xm shutdown >>> /etc/init.d/xendomains: line 306: 27613 Terminated watchdog_xm >>> shutdown 1 >>> [root at potoroo ~]# >> >> Have I offended folk? >> Does nobody know? >> Can't someone even tell me (nicely) where to go? > > I read the initial report, but there wasn't really enough information to > help. Restart the machine and tell us what operation(s) fails, with > what error messages, and what you were expecting it to do. I was trying to find what the message actually means, I think my chances of solving the underlying problem are quite good, once I know what it's talking about. The problem arose when my install of ClarkConnect failed (it reckoned it needed more disk space than I offered), and I tried various ways to "undefine" it. virt-install doesn't recognise a failed install, so it figured it should boot the crook virtual disk. I now have a working CC (I had to explicitly delete the disk image, virt-install doesn't resize it), and am having dismal results with Fedora 7:-( -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From Dustin.Henning at prd-inc.com Wed Nov 7 22:15:12 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Wed, 7 Nov 2007 17:15:12 -0500 Subject: [Fedora-xen] What is XendInvalidDomain? In-Reply-To: <473236E5.9040609@herakles.homelinux.org> References: <473002E1.4000104@herakles.homelinux.org> <47300799.3070304@herakles.homelinux.org> <47310382.1080009@herakles.homelinux.org> <4731AA0C.30500@redhat.com> <473236E5.9040609@herakles.homelinux.org> Message-ID: <001401c8218b$aac9ecf0$005dc6d0$@Henning@prd-inc.com> John, I don't remember for sure, but it kinda looks to me like xendomains (service to start and stop xen domains) is performing a shutdown instead of a save. If that is true, then the terminated could be a successful shutdown or a timeout while waiting for shutdown (at which point the domain is destroyed). In either case, your restore failures would be because of bad files in /var/lib/xen/save (or something like that) from a previous failed save. Deleting those files would get rid of your restore errors and the domains would start normally when xendomains started back up (as they presumably do now). This timeout during xendomains shutdown is configurable (even to forever), but I don't remember where. What to do on xendomains shutdown (save or shutdown) is also configurable (likely in the same file, search for a xendomains.conf?). Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of John Summerfield Sent: Wednesday, November 07, 2007 17:06 To: Fedora Xen Subject: Re: [Fedora-xen] What is XendInvalidDomain? Richard W.M. Jones wrote: > John Summerfield wrote: >> John Summerfield wrote: >> >>> SHUTDOWN_ALL ./etc/init.d/xendomains: line 306: 27592 Terminated >>> watchdog_xm shutdown >>> /etc/init.d/xendomains: line 306: 27613 Terminated watchdog_xm >>> shutdown 1 >>> [root at potoroo ~]# >> >> Have I offended folk? >> Does nobody know? >> Can't someone even tell me (nicely) where to go? > > I read the initial report, but there wasn't really enough information to > help. Restart the machine and tell us what operation(s) fails, with > what error messages, and what you were expecting it to do. I was trying to find what the message actually means, I think my chances of solving the underlying problem are quite good, once I know what it's talking about. The problem arose when my install of ClarkConnect failed (it reckoned it needed more disk space than I offered), and I tried various ways to "undefine" it. virt-install doesn't recognise a failed install, so it figured it should boot the crook virtual disk. I now have a working CC (I had to explicitly delete the disk image, virt-install doesn't resize it), and am having dismal results with Fedora 7:-( -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From debian at herakles.homelinux.org Wed Nov 7 23:02:00 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 08 Nov 2007 08:02:00 +0900 Subject: [Fedora-xen] f7 guest on f8t3 In-Reply-To: <47313E0A.3050700@herakles.homelinux.org> References: <47313E0A.3050700@herakles.homelinux.org> Message-ID: <473243E8.2080204@herakles.homelinux.org> John Summerfield wrote: > > This is my command line, it's similar to one that worked for Debian etch > and ClarkConnect 4.2 (and Windows XP): > > virt-install --name=Fedora7 --ram=384 --vcpus=2 > --file=/var/lib/xen/images/Fedora7.img --file-size=4 --vnc --hvm > --cdrom=/net/ns/var/local/mirrors/linux/Fedora/7/Fedora/x86_64/iso/F-7-x86_64-DVD.iso > --os-type=linux os-variant=fedora7 > > Windows is fine > Debian's fine > ClarkConnect's fine > > f7 took ages loading ata_piix4 (actually it was a little further than > this, that's just want was on the install screen). Ages > half an hour > after which I went off to lunch. > > I cam back and, to my pleasant surprise, it was at the "choose your > language" screen. F7 for IA32 isn't going this well;-( [root at potoroo ~]# \rm /var/lib/xen/images/Fedora7.img [root at potoroo ~]# virt-install --name=Fedora7 --ram=384 --vcpus=2 --file=/var/lib/xen/images/Fedora7.img --file-size=4 --vnc --hvm --location=http://fedora.demo.lan/linux/7/Fedora/i386/os/ --os-type=linux os-variant=fedora7 Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file fedora.cs 100% |=========================| 2.8 kB 00:00 Retrieving file boot.iso. 100% |=========================| 7.7 MB 00:19 libvir: Xen Daemon error : GET operation failed: Creating storage file... 100% |=========================| 4.0 GB 00:00 Creating domain... 0 B 00:00 I's been up over 17 hours. There's a screen shot at http://58.6.192.22/ia32f1.png It's not yet switching to other consoles, I have no more info, Here's the output from "xm top" xentop - 07:27:00 Xen 3.1.0-rc7-2950.fc8 2 domains: 1 running, 1 blocked, 0 paused, 0 crashed, 0 dying, 0 shutdown Mem: 2071872k total, 1664364k used, 407508k free CPUs: 2 @ 1862MHz NAME STATE CPU(sec) CPU(%) MEM(k) MEM(%) MAXMEM(k) MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) VBDS VBD_OO VBD_RD VBD_WR SSID Domain-0 -----r 39667 13.5 1215488 58.7 no limit n/a 2 0 0 0 0 0 0 0 0 Fedora7 --b--- 3382 0.0 401280 19.4 409600 19.8 2 1 0 0 2 0 0 0 0 VBD 5632 [16: 0] OO: 0 RD: 0 WR: 0 VBD 768 [ 3: 0] OO: 0 RD: 0 WR: 0 It doesn't seem to me to be using much disk I/O or CPU. Here's the host software: [root at potoroo ~]# rpm -qa '*xen*' virt\* ;uname -a xen-libs-3.1.0-13.fc8 jaxen-1.1-1jpp.2.fc7 virt-manager-0.5.2-2.fc8 virt-viewer-0.0.2-2.fc8 xen-libs-3.1.0-13.fc8 xen-3.1.0-13.fc8 kernel-xen-2.6.21-2950.fc8 Linux potoroo.demo.lan 2.6.21-2950.fc8xen #1 SMP Tue Oct 23 12:23:33 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux [root at potoroo ~]# -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From debian at herakles.homelinux.org Wed Nov 7 23:15:50 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 08 Nov 2007 08:15:50 +0900 Subject: [Fedora-xen] What is XendInvalidDomain? In-Reply-To: <001401c8218b$aac9ecf0$005dc6d0$@Henning@prd-inc.com> References: <473002E1.4000104@herakles.homelinux.org> <47300799.3070304@herakles.homelinux.org> <47310382.1080009@herakles.homelinux.org> <4731AA0C.30500@redhat.com> <473236E5.9040609@herakles.homelinux.org> <001401c8218b$aac9ecf0$005dc6d0$@Henning@prd-inc.com> Message-ID: <47324726.1030105@herakles.homelinux.org> Dustin Henning wrote: > John, > I don't remember for sure, but it kinda looks to me like xendomains > (service to start and stop xen domains) is performing a shutdown instead of > a save. If that is true, then the terminated could be a successful shutdown > or a timeout while waiting for shutdown (at which point the domain is > destroyed). In either case, your restore failures would be because of bad > files in /var/lib/xen/save (or something like that) from a previous failed > save. Deleting those files would get rid of your restore errors and the > domains would start normally when xendomains started back up (as they > presumably do now). This timeout during xendomains shutdown is configurable > (even to forever), but I don't remember where. What to do on xendomains > shutdown (save or shutdown) is also configurable (likely in the same file, > search for a xendomains.conf?). > Dustin > hi, Dustin My real, original, problem was trying to get rid of the domain that failed to install, so I could have another go. I was unable to find what the error message means - see the subject line. The errors in the second post arose while I was trying to work around the original problem. They look to me like errors in the shell script; they could be symptoms of the original problem, but they're not it. There is currently nothing in /var/lib/xen/save. The timeout is set in /etc/xen/scripts/locking.sh. I don't understand what it does, but it seems to me it doesn't do what's wanted. The "unknown" in this message seems to arise because the lock's not held: Nov 6 12:49:29 potoroo logger: /etc/xen/scripts/vtpm-delete: Forced to steal lock on /var/run/xen-hotplug/vtpmdb from unknown! Judging from the number of the messages and their frequency, the script is looping. > -----Original Message----- > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of John Summerfield > Sent: Wednesday, November 07, 2007 17:06 > To: Fedora Xen > Subject: Re: [Fedora-xen] What is XendInvalidDomain? > > Richard W.M. Jones wrote: >> John Summerfield wrote: >>> John Summerfield wrote: >>> >>>> SHUTDOWN_ALL ./etc/init.d/xendomains: line 306: 27592 Terminated >>>> watchdog_xm shutdown >>>> /etc/init.d/xendomains: line 306: 27613 Terminated watchdog_xm >>>> shutdown 1 >>>> [root at potoroo ~]# >>> Have I offended folk? >>> Does nobody know? >>> Can't someone even tell me (nicely) where to go? >> I read the initial report, but there wasn't really enough information to >> help. Restart the machine and tell us what operation(s) fails, with >> what error messages, and what you were expecting it to do. > > I was trying to find what the message actually means, I think my chances > of solving the underlying problem are quite good, once I know what it's > talking about. > > > The problem arose when my install of ClarkConnect failed (it reckoned it > needed more disk space than I offered), and I tried various ways to > "undefine" it. virt-install doesn't recognise a failed install, so it > figured it should boot the crook virtual disk. > > I now have a working CC (I had to explicitly delete the disk image, > virt-install doesn't resize it), and am having dismal results with > Fedora 7:-( > > > > -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From debian at herakles.homelinux.org Wed Nov 7 23:20:39 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Thu, 08 Nov 2007 08:20:39 +0900 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <4731DBDA.20009@silkspeed.com> References: <4731BDC1.8050902@silkspeed.com> <47324ed80711070726x77cf1385l5b33d4c82a2c7329@mail.gmail.com> <4731DBDA.20009@silkspeed.com> Message-ID: <47324847.3080806@herakles.homelinux.org> Aaron Metzger wrote: > yonas Abraham wrote: Why am I seeing Aaron's messages, but not Yonas'? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From accarlson at gmail.com Thu Nov 8 16:31:55 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Thu, 8 Nov 2007 14:31:55 -0200 Subject: [Fedora-xen] xen and lvm In-Reply-To: <4731A98C.2010309@redhat.com> References: <472F4229.6050605@redhat.com> <4731A98C.2010309@redhat.com> Message-ID: Hi! On 11/7/07, Richard W.M. Jones wrote: > Augusto Castelan Carlson wrote: > > I did a lvextend to add 1G to myguest, but how can I make my guest see > > that change? > > In lvm How To they use the command resize2fs to resize the filesystem, > > but I do not realize how to apply that changes to guests using LVM or > > partitioned by the guest installer. > > > > I tried to use the guest drive partitioned as /dev/xvda1 (boot), > > /dev/xvda2 (/) and /dev/xvda3 (/home) and also with LVM. > > > > How can I make the guest see that change? > > I think pvresize is the command (in the guest). However I'd strongly > suggest that you take a look at a few FAQs and HOWTOs, for example: > > http://tldp.org/HOWTO/LVM-HOWTO/index.html > http://tldp.org/HOWTO/LVM-HOWTO/extendlv.html Thanks, it works! With the new space unallocated in the guest a have created a new partition, create a new PV, extended the VG and the LV. To resize the guest down, the procedure is different as the file system can't be reduced on-line... I'm having no success reducing the files system. After reducing, I can restart it ("kernel panic, not syncing"). I tried to resize down the guest accessing the LV through the host with 1) kpartx, pvscan, lvchange, e2fsck, resize2fs, lvreduce and also 2) doing the resize2fs through the host and the rest in the guest. Both approaches failed for me. Are these the correct way to do that? Or there is a better way to do that? Thanks! Regards, -- Augusto From mathewbrown at fastmail.fm Tue Nov 13 10:31:45 2007 From: mathewbrown at fastmail.fm (Mathew Brown) Date: Tue, 13 Nov 2007 02:31:45 -0800 Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress Message-ID: <1194949905.14232.1221018051@webmail.messagingengine.com> Hi, I was wondering what the differences between Fedora 8's Xen and XenExpress v4 are (besides the limits of 4GB or RAM and four virtual hosts). Is the functionality and stability the same or is Fedora's Xen more cutting-edge? Thank you for your help. -- Mathew Brown mathewbrown at fastmail.fm -- http://www.fastmail.fm - The way an email service should be From mathewbrown at fastmail.fm Tue Nov 13 10:32:37 2007 From: mathewbrown at fastmail.fm (Mathew Brown) Date: Tue, 13 Nov 2007 02:32:37 -0800 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop Message-ID: <1194949957.14326.1221018141@webmail.messagingengine.com> Hi, I was considering installing a minimal Fedora 8 setup with the Xen kernel and then performing most of my work in several different DomUs (perhaps Fedora of Ubuntu) as well as running Windows in a VMware setup (don't currently have hardware virtualization support). Note that this is on a laptop. Are there any specific issues that I should be aware of (such as suspend/resume issues, etc.) and does anyone have any specific recommendations? Thank you for your help. -- Mathew Brown mathewbrown at fastmail.fm -- http://www.fastmail.fm - Access your email from home and the web From rjones at redhat.com Tue Nov 13 11:33:13 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 13 Nov 2007 11:33:13 +0000 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop In-Reply-To: <1194949957.14326.1221018141@webmail.messagingengine.com> References: <1194949957.14326.1221018141@webmail.messagingengine.com> Message-ID: <47398B79.5030708@redhat.com> Mathew Brown wrote: > Hi, > I was considering installing a minimal Fedora 8 setup with the Xen > kernel and then performing most of my work in several different DomUs > (perhaps Fedora of Ubuntu) as well as running Windows in a VMware > setup (don't currently have hardware virtualization support). Note > that this is on a laptop. Are there any specific issues that I should > be aware of (such as suspend/resume issues, etc.) and does anyone have > any specific recommendations? Thank you for your help. Xen and laptops aren't really friends with each other. In particular power management doesn't work so the laptop will run hot and eat batteries, suspend/resume are unlikely to work, and so on. Also it's difficult to mix different hypervisors. I don't think you can run Xen & VMWare at the same time. Have you thought about using qemu instead? A QEmu guest is just an ordinary Linux process, so much more predictable. It's a shame that your laptop doesn't have HVM. What is the processor? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Tue Nov 13 11:35:53 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 13 Nov 2007 11:35:53 +0000 Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress In-Reply-To: <1194949905.14232.1221018051@webmail.messagingengine.com> References: <1194949905.14232.1221018051@webmail.messagingengine.com> Message-ID: <47398C19.5040901@redhat.com> Mathew Brown wrote: > Hi, > I was wondering what the differences between Fedora 8's Xen and > XenExpress v4 are (besides the limits of 4GB or RAM and four virtual > hosts). Is the functionality and stability the same or is Fedora's > Xen more cutting-edge? Thank you for your help. I'm not very familiar with XenExpress, but I'm fairly sure that the management software used by XE is some proprietary code. Fedora uses libvirt and virt-manager for management, has no artificial limitations on memory, CPUs, guests etc., and is completely open source. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From thewird at yahoo.com Tue Nov 13 11:41:40 2007 From: thewird at yahoo.com (thewird) Date: Tue, 13 Nov 2007 06:41:40 -0500 (EST) Subject: Fwd: Re: [Fedora-xen] Fedora's Xen Compared to XenExpress Message-ID: <851393.13838.qm@web88308.mail.re4.yahoo.com> Note: forwarded message attached. -------------- next part -------------- An embedded message was scrubbed... From: thewird Subject: Re: [Fedora-xen] Fedora's Xen Compared to XenExpress Date: Tue, 13 Nov 2007 06:40:40 -0500 (EST) Size: 1234 URL: From rjones at redhat.com Tue Nov 13 11:50:32 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 13 Nov 2007 11:50:32 +0000 Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress In-Reply-To: <733245.70843.qm@web88303.mail.re4.yahoo.com> References: <733245.70843.qm@web88303.mail.re4.yahoo.com> Message-ID: <47398F88.3050908@redhat.com> thewird wrote: > --- "Richard W.M. Jones" wrote: >> Mathew Brown wrote: >>> Hi, >>> I was wondering what the differences between Fedora 8's Xen and >>> XenExpress v4 are (besides the limits of 4GB or RAM and four >> virtual >>> hosts). Is the functionality and stability the same or is >> Fedora's >>> Xen more cutting-edge? Thank you for your help. >> I'm not very familiar with XenExpress, but I'm fairly sure that the >> management software used by XE is some proprietary code. Fedora uses >> >> libvirt and virt-manager for management, has no artificial >> limitations >> on memory, CPUs, guests etc., and is completely open source. > > Does Fedora 8 have any way to limit the network speed on the guests? I assume, though I've not tried it, that you should be able to use ordinary Linux mechanisms such as the 'tc(8)' command to enforce a traffic control and shaping on the vifX.0 devices. To be honest, it's a bit of an unusual request: mostly people complain about not getting enough network performance :-) Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From thewird at yahoo.com Tue Nov 13 12:02:43 2007 From: thewird at yahoo.com (thewird) Date: Tue, 13 Nov 2007 07:02:43 -0500 (EST) Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress In-Reply-To: <47398F88.3050908@redhat.com> Message-ID: <607849.84212.qm@web88311.mail.re4.yahoo.com> --- "Richard W.M. Jones" wrote: > thewird wrote: > > --- "Richard W.M. Jones" wrote: > >> Mathew Brown wrote: > >>> Hi, > >>> I was wondering what the differences between Fedora 8's Xen and > >>> XenExpress v4 are (besides the limits of 4GB or RAM and four > >> virtual > >>> hosts). Is the functionality and stability the same or is > >> Fedora's > >>> Xen more cutting-edge? Thank you for your help. > >> I'm not very familiar with XenExpress, but I'm fairly sure that > the > >> management software used by XE is some proprietary code. Fedora > uses > >> > >> libvirt and virt-manager for management, has no artificial > >> limitations > >> on memory, CPUs, guests etc., and is completely open source. > > Does Fedora 8 have any way to limit the network speed on the > > guests? > > I assume, though I've not tried it, that you should be able to use > ordinary Linux mechanisms such as the 'tc(8)' command to enforce a > traffic control and shaping on the vifX.0 devices. > > To be honest, it's a bit of an unusual request: mostly people > complain > about not getting enough network performance :-) Reason being the only reason I'm still using XenEnterprise for my VPS's is because of the network limiter and the nice graphs which (which I could live without). With XenSource being bought out by Citrix and the price tripling for a license, I'm looking for alternatives. I asked the datacenter already to ship me one of my dual-core's so I could test Fedora 8 at home. Marco Jorge From rjones at redhat.com Tue Nov 13 12:21:24 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 13 Nov 2007 12:21:24 +0000 Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress In-Reply-To: <607849.84212.qm@web88311.mail.re4.yahoo.com> References: <607849.84212.qm@web88311.mail.re4.yahoo.com> Message-ID: <473996C4.4070707@redhat.com> thewird wrote: > Reason being the only reason I'm still using XenEnterprise for my VPS's > is because of the network limiter and the nice graphs which (which I > could live without). With XenSource being bought out by Citrix and the > price tripling for a license, I'm looking for alternatives. I asked the > datacenter already to ship me one of my dual-core's so I could test > Fedora 8 at home. If you want to make nice graphs, then I've recently contributed a patch to collectd which collects stats through libvirt: http://mailman.verplant.org/pipermail/collectd/2007-November/001297.html (I think the patch is in the latest released tarball). http://collectd.org/ Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From berrange at redhat.com Tue Nov 13 13:57:01 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 13 Nov 2007 13:57:01 +0000 Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress In-Reply-To: <47398F88.3050908@redhat.com> References: <733245.70843.qm@web88303.mail.re4.yahoo.com> <47398F88.3050908@redhat.com> Message-ID: <20071113135701.GA17462@redhat.com> On Tue, Nov 13, 2007 at 11:50:32AM +0000, Richard W.M. Jones wrote: > thewird wrote: > >--- "Richard W.M. Jones" wrote: > >>Mathew Brown wrote: > >>>Hi, > >>> I was wondering what the differences between Fedora 8's Xen and > >>> XenExpress v4 are (besides the limits of 4GB or RAM and four > >>virtual > >>> hosts). Is the functionality and stability the same or is > >>Fedora's > >>> Xen more cutting-edge? Thank you for your help. > >>I'm not very familiar with XenExpress, but I'm fairly sure that the > >>management software used by XE is some proprietary code. Fedora uses > >> > >>libvirt and virt-manager for management, has no artificial > >>limitations > >>on memory, CPUs, guests etc., and is completely open source. > > > >Does Fedora 8 have any way to limit the network speed on the guests? > > I assume, though I've not tried it, that you should be able to use > ordinary Linux mechanisms such as the 'tc(8)' command to enforce a > traffic control and shaping on the vifX.0 devices. Yes, if you modified the '/etc/xen/scripts/vif-bridge' script you could make it run 'tc' against the vifX.0 devices when bringing up a guest to give it a fixed data limit. 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 Tue Nov 13 15:08:15 2007 From: guillaume.chardin at gmail.com (Guillaume) Date: Tue, 13 Nov 2007 16:08:15 +0100 Subject: [Fedora-xen] Prb manualy creating new VM. Message-ID: Hi, after a previous thread I start & some feedback you gave to me, about creating xen VM I ask you for your help. Here is the problem : `mount`. It was unable to find the disk/device to mount it as root (/). After the linux kernel bootup (domU) I create the VM by theses steps: i'm on fedora 8 with xen 3.1.0-13 a) #fdisk /dev/sda create a new part (sda4) type linux b)format it with #mkfs.ext3 /dev/sda4 c)Copy on it all files from my distrib with : #cp -a / /mnt/sda4 Edit the /mnt/sda4/etc/fstab to meet the reqs for the VM. d)Start the vm from config file (see below). #xm create testvm.conf -c Booom! failed :'( I check every thing i can, fstab, VM config file & test several things... But i was unable to fix the problem. Someone can help me, point out whats wrong ? Thanks, --- Guillaume ---begin of xenVM config file--- kernel = "/boot/vmlinuz-2.6.21-2950.fc8xen" ramdisk = "/boot/initrd-2.6.21-2950.fc8xen.img" root = "root=/dev/sda1 ro" #extra = "1" memory = "128" name = "Fedora-8-Guest" disk = [ 'phy:sda4,sda1,w' ] ---EOF--- ---begin of boot--- #xm create testvm.conf -c Using config file "./testvm.conf". Started domain Fedora-8-Guest Linux version 2.6.21-2950.fc8xen (kojibuilder at xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) #1 SMP Tue Oct 23 12:24:34 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000008800000 end: 0000000008800000 type: 1 Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Detected 2001.289 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c136c000 soft=c134c000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 2000.198 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 118016k/139264k available (2071k kernel code, 12968k reserved, 1080k data, 188k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc1319000 - 0xc1348000 ( 188 kB) .data : 0xc1205e5e - 0xc1313fd4 (1080 kB) .text : 0xc1000000 - 0xc1205e5e (2071 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4070.78 BogoMIPS (lpj=8141572) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 13k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 98304 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7064k freed audit: initializing netlink socket (disabled) audit(1194965135.393:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring 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.102 (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 Linux version 2.6.21-2950.fc8xen (kojibuilder at xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) #1 SMP Tue Oct 23 12:24:34 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000008800000 end: 0000000008800000 type: 1 Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Detected 2001.289 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c136c000 soft=c134c000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 2000.198 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 118016k/139264k available (2071k kernel code, 12968k reserved, 1080k data, 188k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc1319000 - 0xc1348000 ( 188 kB) .data : 0xc1205e5e - 0xc1313fd4 (1080 kB) .text : 0xc1000000 - 0xc1205e5e (2071 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4070.78 BogoMIPS (lpj=8141572) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 13k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 98304 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7064k freed audit: initializing netlink socket (disabled) audit(1194965135.393:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring 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.102 (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 hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Freeing unused kernel memory: 188k freed Write protecting the kernel read-only data: 795k Red Hat nash version 6.0.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading mbcache.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading ata_piix.ko module Waiting for driver initialization. Loading ata_generic.ko module Loading BusLogic.ko module Creating root device. Mounting root filesystem. 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 Booting has failed. ---End of boot--- ---begin of fstab (domU)--- # cat /mnt/etc/fstab /dev/sda1 / ext3 defaults 1 1 ---end of file--- From Dustin.Henning at prd-inc.com Tue Nov 13 15:49:36 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 13 Nov 2007 10:49:36 -0500 Subject: [Fedora-xen] Prb manualy creating new VM. In-Reply-To: References: Message-ID: <005001c8260c$cb29dac0$617d9040$@Henning@prd-inc.com> Try changing this line: disk = [ 'phy:sda4,sda1,w' ] to this: disk = [ 'phy:/dev/sda4,sda1,w' ] I had to do that for my domU's when I was uing paravirtualization a few versions ago. I can't remember if that was all I had to do, but you might also try this line (I think it would only be more appropriate in an HVM environment where the partition had been fdisked as well): disk = [ 'phy:/dev/sda4,hda,w' ] Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Guillaume Sent: Tuesday, November 13, 2007 10:08 To: Fedora-xen at redhat.com Subject: [Fedora-xen] Prb manualy creating new VM. Hi, after a previous thread I start & some feedback you gave to me, about creating xen VM I ask you for your help. Here is the problem : `mount`. It was unable to find the disk/device to mount it as root (/). After the linux kernel bootup (domU) I create the VM by theses steps: i'm on fedora 8 with xen 3.1.0-13 a) #fdisk /dev/sda create a new part (sda4) type linux b)format it with #mkfs.ext3 /dev/sda4 c)Copy on it all files from my distrib with : #cp -a / /mnt/sda4 Edit the /mnt/sda4/etc/fstab to meet the reqs for the VM. d)Start the vm from config file (see below). #xm create testvm.conf -c Booom! failed :'( I check every thing i can, fstab, VM config file & test several things... But i was unable to fix the problem. Someone can help me, point out whats wrong ? Thanks, --- Guillaume ---begin of xenVM config file--- kernel = "/boot/vmlinuz-2.6.21-2950.fc8xen" ramdisk = "/boot/initrd-2.6.21-2950.fc8xen.img" root = "root=/dev/sda1 ro" #extra = "1" memory = "128" name = "Fedora-8-Guest" disk = [ 'phy:sda4,sda1,w' ] ---EOF--- ---begin of boot--- #xm create testvm.conf -c Using config file "./testvm.conf". Started domain Fedora-8-Guest Linux version 2.6.21-2950.fc8xen (kojibuilder at xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) #1 SMP Tue Oct 23 12:24:34 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000008800000 end: 0000000008800000 type: 1 Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Detected 2001.289 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c136c000 soft=c134c000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 2000.198 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 118016k/139264k available (2071k kernel code, 12968k reserved, 1080k data, 188k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc1319000 - 0xc1348000 ( 188 kB) .data : 0xc1205e5e - 0xc1313fd4 (1080 kB) .text : 0xc1000000 - 0xc1205e5e (2071 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4070.78 BogoMIPS (lpj=8141572) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 13k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 98304 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7064k freed audit: initializing netlink socket (disabled) audit(1194965135.393:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring 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.102 (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 Linux version 2.6.21-2950.fc8xen (kojibuilder at xenbuilder2.fedora.redhat.com) (gcc version 4.1.2 20070925 (Red Hat 4.1.2-32)) #1 SMP Tue Oct 23 12:24:34 EDT 2007 BIOS-provided physical RAM map: sanitize start sanitize bail 0 copy_e820_map() start: 0000000000000000 size: 0000000008800000 end: 0000000008800000 type: 1 Xen: 0000000000000000 - 0000000008800000 (usable) 0MB HIGHMEM available. 136MB LOWMEM available. NX (Execute Disable) protection: active Zone PFN ranges: DMA 0 -> 34816 Normal 34816 -> 34816 HighMem 34816 -> 34816 early_node_map[1] active PFN ranges 0: 0 -> 34816 ACPI in unprivileged domain disabled Detected 2001.289 MHz processor. Built 1 zonelists. Total pages: 34544 Kernel command line: root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c136c000 soft=c134c000 PID hash table entries: 1024 (order: 10, 4096 bytes) Xen reported: 2000.198 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Software IO TLB disabled vmalloc area: c9000000-f4ffe000, maxmem 2d7fe000 Memory: 118016k/139264k available (2071k kernel code, 12968k reserved, 1080k data, 188k init, 0k highmem) virtual kernel memory layout: fixmap : 0xf5315000 - 0xf57fe000 (5028 kB) pkmap : 0xf5000000 - 0xf5200000 (2048 kB) vmalloc : 0xc9000000 - 0xf4ffe000 ( 703 MB) lowmem : 0xc0000000 - 0xc8800000 ( 136 MB) .init : 0xc1319000 - 0xc1348000 ( 188 kB) .data : 0xc1205e5e - 0xc1313fd4 (1080 kB) .text : 0xc1000000 - 0xc1205e5e (2071 kB) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 4070.78 BogoMIPS (lpj=8141572) Security Framework v1.0.0 initialized SELinux: Initializing. selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 2048K Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 13k freed Brought up 1 CPUs NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub Setting up standard PCI resources ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 98304 bytes) TCP bind hash table entries: 8192 (order: 4, 65536 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered checking if image is initramfs... it is Freeing initrd memory: 7064k freed audit: initializing netlink socket (disabled) audit(1194965135.393:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) ksign: Installing public key data Loading keyring 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.102 (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 hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 drivers/rtc/hctosys.c: unable to open rtc device (rtc0) Freeing unused kernel memory: 188k freed Write protecting the kernel read-only data: 795k Red Hat nash version 6.0.19 starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes Setting up hotplug. Creating block device nodes. Loading ehci-hcd.ko module Loading ohci-hcd.ko module Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 Loading mbcache.ko module Loading jbd.ko module Loading ext3.ko module Loading scsi_mod.ko module SCSI subsystem initialized Loading sd_mod.ko module Loading libata.ko module Loading ata_piix.ko module Waiting for driver initialization. Loading ata_generic.ko module Loading BusLogic.ko module Creating root device. Mounting root filesystem. 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 Booting has failed. ---End of boot--- ---begin of fstab (domU)--- # cat /mnt/etc/fstab /dev/sda1 / ext3 defaults 1 1 ---end of file--- -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From guillaume.chardin at gmail.com Tue Nov 13 16:39:27 2007 From: guillaume.chardin at gmail.com (Guillaume) Date: Tue, 13 Nov 2007 17:39:27 +0100 Subject: [Fedora-xen] Prb manualy creating new VM. In-Reply-To: <6512084851740472597@unknownmsgid> References: <6512084851740472597@unknownmsgid> Message-ID: 2007/11/13, Dustin Henning : > Try changing this line: > disk = [ 'phy:/dev/sda4,sda1,w' ] I change the line to "disk = [ 'phy:/dev/sda4,sda1,w' ]" but that not working too. > disk = [ 'phy:/dev/sda4,hda,w' ] I test this line previously in this day but same result. Is there a way to check if disk are detected by kernel while booting ? -- Guillaume From bench at silentmedia.com Tue Nov 13 16:40:52 2007 From: bench at silentmedia.com (Ben) Date: Tue, 13 Nov 2007 08:40:52 -0800 Subject: [Fedora-xen] Fedora's Xen Compared to XenExpress In-Reply-To: <607849.84212.qm@web88311.mail.re4.yahoo.com> References: <607849.84212.qm@web88311.mail.re4.yahoo.com> Message-ID: <2C69F7B3-EE1D-44F5-9D7C-D1EBE0A3C9C2@silentmedia.com> If you're thinking of using Fedora Xen in production, my advice is to use RHEL or CentOS instead. Maybe things have gotten better, but in the FC5 and FC6 days, I was burned many times by "upgrading" only to find that the new xen had a bug with the new kernel, and that there was no good way to roll back upgrades to Xen, just the kernel. It may be that you need features not available in RHEL or CentOS, but I didn't, and I've been a much happier camper on something where I don't have to fear updates quite as much. On Nov 13, 2007, at 4:02 AM, thewird wrote: > Reason being the only reason I'm still using XenEnterprise for my > VPS's > is because of the network limiter and the nice graphs which (which I > could live without). With XenSource being bought out by Citrix and the > price tripling for a license, I'm looking for alternatives. I asked > the > datacenter already to ship me one of my dual-core's so I could test > Fedora 8 at home. From addw at phcomp.co.uk Tue Nov 13 17:17:01 2007 From: addw at phcomp.co.uk (Alain Williams) Date: Tue, 13 Nov 2007 17:17:01 +0000 Subject: [Fedora-xen] Prb manualy creating new VM. In-Reply-To: References: <6512084851740472597@unknownmsgid> Message-ID: <20071113171701.GG5493@mint.phcomp.co.uk> On Tue, Nov 13, 2007 at 05:39:27PM +0100, Guillaume wrote: > 2007/11/13, Dustin Henning : > > Try changing this line: > > disk = [ 'phy:/dev/sda4,sda1,w' ] > I change the line to "disk = [ 'phy:/dev/sda4,sda1,w' ]" but that not > working too. I missed the start of this thread, but ... I had problems attaching disks and resolved it by a line like: disk = [ 'phy:mapper/LaLvg0-MailDisk,xvda,w', 'phy:mapper/LaLvg0-MailHome,xvdb,w' ] The important thing was the change from sda or sda1 to xvda. After that things worked. -- Alain Williams Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php Chairman of UKUUG: http://www.ukuug.org/ #include From Dustin.Henning at prd-inc.com Tue Nov 13 17:25:04 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Tue, 13 Nov 2007 12:25:04 -0500 Subject: [Fedora-xen] Prb manualy creating new VM. In-Reply-To: <20071113171701.GG5493@mint.phcomp.co.uk> References: <6512084851740472597@unknownmsgid> <20071113171701.GG5493@mint.phcomp.co.uk> Message-ID: <005101c8261a$2120ebf0$6362c3d0$@Henning@prd-inc.com> I thought about mentioning this possibility, but I wasn't sure on the syntax. I am also not sure whether it is Fedora specific or whether the ability to use sda instead of xvda is XenSource specific (aside from in HVMs where you need "real" devices). Alain, in this case was mapper/LaLvg0-MailDisk partitioned with fdisk, or was it just a regularly formatted (i.e. ext3) lvm partition? Also, from your provided line, it looks like /dev/ isn't necessary after the phy: in Fedora Xen where it was necessary in the XenSource version I last paravirtualized in. Is it accurate to assume that you copied that line from a working config on a Fedora Xen machine? Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Alain Williams Sent: Tuesday, November 13, 2007 12:17 To: Guillaume Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Prb manualy creating new VM. On Tue, Nov 13, 2007 at 05:39:27PM +0100, Guillaume wrote: > 2007/11/13, Dustin Henning : > > Try changing this line: > > disk = [ 'phy:/dev/sda4,sda1,w' ] > I change the line to "disk = [ 'phy:/dev/sda4,sda1,w' ]" but that not > working too. I missed the start of this thread, but ... I had problems attaching disks and resolved it by a line like: disk = [ 'phy:mapper/LaLvg0-MailDisk,xvda,w', 'phy:mapper/LaLvg0-MailHome,xvdb,w' ] The important thing was the change from sda or sda1 to xvda. After that things worked. -- Alain Williams Linux Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php Chairman of UKUUG: http://www.ukuug.org/ #include -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From jlagrue at gmail.com Tue Nov 13 21:04:49 2007 From: jlagrue at gmail.com (John Lagrue) Date: Tue, 13 Nov 2007 21:04:49 +0000 Subject: [Fedora-xen] Fedora 8, qemu-kvm and networking Message-ID: Having installed F8 and tried out the latest virt-manager, I have to say I'm impressed. But........I am still utterly baffled by guest networking. What I *want* to do is have a Windows XP guest that runs on the same network as my laptop, the host; in other words, the guest should be able to access all the network that the laptop can see. But I can't for the life of me find out how to do this. I'll put up,if I have to, with the guest only working through the eth0 interface (though it would be nicer if it could work via wireless too). But I can't find any documentation that discusses this that isn't either at least a year old, or is written for someone who already knows the answer and understands the jargon of virtual networking. Can anyone help, or at least point me to a reasonably clear how-to ? Note that I am not running XEN ( I need Windows) and am doing this with qemu-kvm. John -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathewbrown at fastmail.fm Wed Nov 14 15:58:55 2007 From: mathewbrown at fastmail.fm (Mathew Brown) Date: Wed, 14 Nov 2007 07:58:55 -0800 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop In-Reply-To: <47398B79.5030708@redhat.com> References: <1194949957.14326.1221018141@webmail.messagingengine.com> <47398B79.5030708@redhat.com> Message-ID: <1195055935.19145.1221286627@webmail.messagingengine.com> On Tue, 13 Nov 2007 11:33:13 +0000, "Richard W.M. Jones" said: > Mathew Brown wrote: > > Hi, > > I was considering installing a minimal Fedora 8 setup with the Xen > > kernel and then performing most of my work in several different DomUs > > (perhaps Fedora of Ubuntu) as well as running Windows in a VMware > > setup (don't currently have hardware virtualization support). Note > > that this is on a laptop. Are there any specific issues that I should > > be aware of (such as suspend/resume issues, etc.) and does anyone have > > any specific recommendations? Thank you for your help. > > Xen and laptops aren't really friends with each other. In particular > power management doesn't work so the laptop will run hot and eat > batteries, suspend/resume are unlikely to work, and so on. I remember on the Xen mailing list that they wanted to encourage people to start using Xen on laptops to help troubleshoot power management related issues. > Also it's difficult to mix different hypervisors. I don't think you can > run Xen & VMWare at the same time. > > Have you thought about using qemu instead? A QEmu guest is just an > ordinary Linux process, so much more predictable. It's a shame that > your laptop doesn't have HVM. What is the processor? I just rechecked. I have the HP nc6320 and just came across a post that says that they released a BIOS update to enable virtualization :) I hope to try it out. But even then, how stable is Windows under Xen (I plan on running a lot of appliactions and trying to port my current Windows setup + applications to it). I was planning on using P2V and make a VMware virtual machine image of my current setup and then use that under VMware. That would definitely be the easier approach. Also, Qemu is very very slow. VirtualBox is a better approach. However, neither VirtualBox or Qemu are really what I'm looking at (I've used both in the past). Thanks for your 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 -- Mathew Brown mathewbrown at fastmail.fm -- http://www.fastmail.fm - The professional email service From berrange at redhat.com Wed Nov 14 16:01:22 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 14 Nov 2007 16:01:22 +0000 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop In-Reply-To: <1195055935.19145.1221286627@webmail.messagingengine.com> References: <1194949957.14326.1221018141@webmail.messagingengine.com> <47398B79.5030708@redhat.com> <1195055935.19145.1221286627@webmail.messagingengine.com> Message-ID: <20071114160122.GF29823@redhat.com> On Wed, Nov 14, 2007 at 07:58:55AM -0800, Mathew Brown wrote: > > On Tue, 13 Nov 2007 11:33:13 +0000, "Richard W.M. Jones" > said: > > Mathew Brown wrote: > > > Hi, > > > I was considering installing a minimal Fedora 8 setup with the Xen > > > kernel and then performing most of my work in several different DomUs > > > (perhaps Fedora of Ubuntu) as well as running Windows in a VMware > > > setup (don't currently have hardware virtualization support). Note > > > that this is on a laptop. Are there any specific issues that I should > > > be aware of (such as suspend/resume issues, etc.) and does anyone have > > > any specific recommendations? Thank you for your help. > > > > Xen and laptops aren't really friends with each other. In particular > > power management doesn't work so the laptop will run hot and eat > > batteries, suspend/resume are unlikely to work, and so on. > > I remember on the Xen mailing list that they wanted to encourage people > to start using Xen on laptops to help troubleshoot power management > related issues. There's no troubleshooting to be done. It is quite simply not implemented. There is no suspend/hibernate support. CPU scaling is useless because Dom0 can't neccessarily see all physical CPUs, and has no info about the activity of the guest. The split Dom0/HV architecture is a loosing battle for ths kind of stuff which is why we recoomend KVM as the only viable solution for laptops. 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 mathewbrown at fastmail.fm Wed Nov 14 16:11:48 2007 From: mathewbrown at fastmail.fm (Mathew Brown) Date: Wed, 14 Nov 2007 08:11:48 -0800 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop In-Reply-To: <20071114160122.GF29823@redhat.com> References: <1194949957.14326.1221018141@webmail.messagingengine.com> <47398B79.5030708@redhat.com> <1195055935.19145.1221286627@webmail.messagingengine.com> <20071114160122.GF29823@redhat.com> Message-ID: <1195056708.22401.1221288897@webmail.messagingengine.com> Thanks for the clarification. My bad :) Also, if it was a minimal xen kernel and I had the DomU's running, I should be able to use save/restore on the DomUs (where I would be doing 90%+ of my typical work) to simulate suspending. On Wed, 14 Nov 2007 16:01:22 +0000, "Daniel P. Berrange" said: > On Wed, Nov 14, 2007 at 07:58:55AM -0800, Mathew Brown wrote: > > > > On Tue, 13 Nov 2007 11:33:13 +0000, "Richard W.M. Jones" > > said: > > > Mathew Brown wrote: > > > > Hi, > > > > I was considering installing a minimal Fedora 8 setup with the Xen > > > > kernel and then performing most of my work in several different DomUs > > > > (perhaps Fedora of Ubuntu) as well as running Windows in a VMware > > > > setup (don't currently have hardware virtualization support). Note > > > > that this is on a laptop. Are there any specific issues that I should > > > > be aware of (such as suspend/resume issues, etc.) and does anyone have > > > > any specific recommendations? Thank you for your help. > > > > > > Xen and laptops aren't really friends with each other. In particular > > > power management doesn't work so the laptop will run hot and eat > > > batteries, suspend/resume are unlikely to work, and so on. > > > > I remember on the Xen mailing list that they wanted to encourage people > > to start using Xen on laptops to help troubleshoot power management > > related issues. > > There's no troubleshooting to be done. It is quite simply not > implemented. > There is no suspend/hibernate support. CPU scaling is useless because > Dom0 can't neccessarily see all physical CPUs, and has no info about the > activity of the guest. > > The split Dom0/HV architecture is a loosing battle for ths kind of stuff > which is why we recoomend KVM as the only viable solution for laptops. > > 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 > -=| -- Mathew Brown mathewbrown at fastmail.fm -- http://www.fastmail.fm - A fast, anti-spam email service. From rjones at redhat.com Wed Nov 14 16:21:21 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 14 Nov 2007 16:21:21 +0000 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop In-Reply-To: <1195055935.19145.1221286627@webmail.messagingengine.com> References: <1194949957.14326.1221018141@webmail.messagingengine.com> <47398B79.5030708@redhat.com> <1195055935.19145.1221286627@webmail.messagingengine.com> Message-ID: <473B2081.5070908@redhat.com> Mathew Brown wrote: > On Tue, 13 Nov 2007 11:33:13 +0000, "Richard W.M. Jones" > said: >> Have you thought about using qemu instead? A QEmu guest is just an >> ordinary Linux process, so much more predictable. It's a shame that >> your laptop doesn't have HVM. What is the processor? > > > I just rechecked. I have the HP nc6320 and just came across a post that > says that they released a BIOS update to enable virtualization :) This isn't uncommon. Most BIOSes disable virtualization at boot time by writing to a processor-specific register (which, on Intel, cannot be unset without booting). This is a security feature to stop a particular form of near undetectable rootkit. So you need BIOS support and this is commonly supplied through BIOS upgrades - eg. Lenovo did this for the Thinkpad models which support HVM. > hope to try it out. But even then, how stable is Windows under Xen (I Xen upstream certainly support Windows under Xen. Of course you absolutely do need hardware virt support in your processor. It may not surprise you to know that we don't use very much Windows round here, so I can't personally comment on how well it works. 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 mathewbrown at fastmail.fm Thu Nov 15 07:19:00 2007 From: mathewbrown at fastmail.fm (Mathew Brown) Date: Wed, 14 Nov 2007 23:19:00 -0800 Subject: [Fedora-xen] Minimal Fedora 8 Xen Setup for Laptop In-Reply-To: <473B2081.5070908@redhat.com> References: <1194949957.14326.1221018141@webmail.messagingengine.com> <47398B79.5030708@redhat.com> <1195055935.19145.1221286627@webmail.messagingengine.com> <473B2081.5070908@redhat.com> Message-ID: <1195111140.11652.1221423503@webmail.messagingengine.com> Hi Richard, Just out of curiosity. How is running VMware different from running Qemu with kqemu? From my understanding, both of them rely on a kernel driver (or more than one) and a process running. So why shouldn't running vmware server under a Xen Dom0 works? Thanks for your help. On Wed, 14 Nov 2007 16:21:21 +0000, "Richard W.M. Jones" said: > Mathew Brown wrote: > > On Tue, 13 Nov 2007 11:33:13 +0000, "Richard W.M. Jones" > > said: > >> Have you thought about using qemu instead? A QEmu guest is just an > >> ordinary Linux process, so much more predictable. It's a shame that > >> your laptop doesn't have HVM. What is the processor? > > > > > > I just rechecked. I have the HP nc6320 and just came across a post that > > says that they released a BIOS update to enable virtualization :) > > This isn't uncommon. Most BIOSes disable virtualization at boot time by > writing to a processor-specific register (which, on Intel, cannot be > unset without booting). This is a security feature to stop a particular > form of near undetectable rootkit. So you need BIOS support and this is > commonly supplied through BIOS upgrades - eg. Lenovo did this for the > Thinkpad models which support HVM. > > > hope to try it out. But even then, how stable is Windows under Xen (I > > Xen upstream certainly support Windows under Xen. Of course you > absolutely do need hardware virt support in your processor. It may not > surprise you to know that we don't use very much Windows round here, so > I can't personally comment on how well it works. > > 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 -- Mathew Brown mathewbrown at fastmail.fm -- http://www.fastmail.fm - A fast, anti-spam email service. From dlbewley at lib.ucdavis.edu Thu Nov 15 18:55:18 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Thu, 15 Nov 2007 10:55:18 -0800 (PST) Subject: [Fedora-xen] dom0 F7 crashes tcp_tso_segment oops - new kernel lag time Message-ID: <703764171.19681195152918547.JavaMail.root@zebra.lib.ucdavis.edu> Running 2.6.20-2936.fc7xen x86_64 quad CPU, 16G. We have a dom0 with bridges riding on top of a VLAN interface. # brctl show bridge name bridge id STP enabled interfaces br101 8000.00093d139ae9 no eth0 br6 8000.00093d139ae9 no vif2.0 vif1.0 eth0.6 ... Inside a F7 domU on br6 we are running tc (via shorewall) to limit the bandwidth of a mirror server. On Monday I throttled the bandwidth down far below the demand. Since then we are starting to see dom0 crash and reboot with nothing in the log. Crashes happened on Tues around 9am and Thursday (today) around 4am and 9am. I caught the console during the most recent crash: Unable to handle kernel NULL pointer dereference at 0000000000000030 RIP: [] tcp_tso_segment+0x1d8/0x285 PGD 3db8f1067 PUD 3db8f2067 PMD 0 Oops: 0000 [1] SMP last sysfs file: /devices/xen-backend/vbd-2-51712/statistics/wr_sect CPU 1 Modules linked in: loop netbk xenblktap blkbk autofs4 8021q bridge nf_conntrack_netbios_ns ipt_LdPid: 0, comm: swapper Not tainted 2.6.20-2936.fc7xen #1 RIP: e030:[] [] tcp_tso_segment+0x1d8/0x285 RSP: e02b:ffff880002f77950 EFLAGS: 00010216 RAX: 0000000000007a21 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000010130000 RSI: 0000000000000000 RDI: 0000000087e8b626 RBP: 000000000000fa87 R08: 0000000187e8b625 R09: 0000000000000000 R10: 000000009b9a7b25 R11: 0000000000000003 R12: ffff88034ecab034 R13: 0000000017acfe00 R14: 0000000000000020 R15: 00000000ffff0000 FS: 00002aaaab0ff230(0000) GS:ffffffff80580080(0000) knlGS:0000000000000000 We are up to date with patches. After the first 2 crashes and before the 3rd I upgraded from xen-3.1.0-6.fc7 to xen-3.1.0-8.fc7 and rebooted dom0 for good measure. I did some googling and found this: http://lists.openwall.net/netdev/2007/02/09/16 which seems pretty similar. Assuming this is the problem and there is a fix I'm left to ask what is the ETA for a new xen kernel and what is the typical lag time? Current state is 2.6.23.1-21.fc7 vs. 2.6.20-2936.fc7xen -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From debian at herakles.homelinux.org Thu Nov 15 22:11:12 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Fri, 16 Nov 2007 07:11:12 +0900 Subject: [Fedora-xen] Attaching a virtual CD to an existing domu? Message-ID: <473CC400.4060804@herakles.homelinux.org> Pls note, you cannot reply off-list.. I have a Debian Etch system, I want to install more software and it's asking for the DVD. I created the system a few days ago, I think this is the commaind I used: virt-install --name=DebianEtch --ram=384 --vcpus=1 --file=/var/lib/xen/images/DebianEtch.img --file-size=3 --vnc --hvm --cdrom=/var/lib/xen/images/debian-40r1-i386-DVD-1.iso --os-type=unix I've tried various incantations: [root at potoroo mail]# virsh attach-disk DebianEtch /var/lib/xen/images/debian-40r1-i386-DVD-1.iso /dev/hde --driver file --type cdrom --mode readonly libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 8448 not connected') [root at potoroo mail]# virsh attach-disk DebianEtch /var/lib/xen/images/debian-40r1-i386-DVD-1.iso /dev/hdc --driver file --type cdrom --mode readonly libvir: Xen Daemon error : POST operation failed: (xend.err "Refusing to reconfigure device vbd:5632 to {'uname': 'file:/var/lib/xen/images/debian-40r1-i386-DVD-1.iso', 'mode': 'r', 'dev': '/dev/hdc:cdrom'}") [root at potoroo mail]# virsh attach-disk DebianEtch /var/lib/xen/images/debian-40r1-i386-DVD-1.iso /dev/hdb --driver file --type cdrom --mode readonly libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 832 not connected') [root at potoroo mail]# None of those messages gives me any idea of what's wrong. I tried the xm command too: This is based on the manual page. The man page is wrong: xm block-attach DebianEtch file://var/lib/xen/images/debian-40r1-i386-DVD-1.iso /dev/hdd ro DebianEtch thinks its CD drive is /dev/hdc, so I really want the CD attached to that. [root at potoroo mail]# xm block-attach DebianEtch file://var/lib/xen/images/debian-40r1-i386-DVD-1.iso /dev/hdc r Error: Device /dev/hdc (5632, vbd) is already connected. Usage: xm block-attach [BackDomain] Create a new virtual block device. [root at potoroo mail]# This seems to work: [root at potoroo mail]# xm block-attach DebianEtch file://var/lib/xen/images/debian-40r1-i386-DVD-1.iso /dev/hdb r [root at potoroo mail]# but DebianEtch doesn't know about it. How _should_ this work? I note block-detach doesn't seem to do anything: [root at potoroo mail]# xm block-detach DebianEtch 832 [root at potoroo mail]# xm block-detach DebianEtch 5696 [root at potoroo mail]# xm block-detach DebianEtch 5632 [root at potoroo mail]# xm list DebianEtch --long | less [root at potoroo mail]# xm block-list DebianEtch Vdev BE handle state evt-ch ring-ref BE-path 768 0 0 1 -1 -1 /local/domain/0/backend/vbd/3/768 5632 0 0 1 -1 -1 /local/domain/0/backend/vbd/3/5632 5696 0 0 1 -1 -1 /local/domain/0/backend/vbd/3/5696 832 0 0 1 -1 -1 /local/domain/0/backend/vbd/3/832 [root at potoroo mail]# Is there a particular reason the install DVD image doesn't, by default, remain attached? -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From thomas.vonsteiger at bluewin.ch Sat Nov 17 07:59:39 2007 From: thomas.vonsteiger at bluewin.ch (Thomas von Steiger) Date: Sat, 17 Nov 2007 08:59:39 +0100 Subject: [Fedora-xen] xenbr0 missing on fedora 8 Message-ID: <000601c828ef$cdac1200$3201a8c0@athlon> Hello, I try to kickstart domU's on fedora 8 because there is no xenbr0. The only bridge i can found is virbr0 and this bridge is running on 192.168.22.0 My kickstart source is located on 192.168.1.0 and new guest's can't access this network. "virsh net-list" list network "default" with state "active" and "autostart". How I can bring back automatically xenbr0 on eth0 without create ifcfg-xenbr0 ? Many thanks Thomas No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.0 - Release Date: 16.11.2007 00:00 From rjones at redhat.com Mon Nov 19 11:40:25 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 19 Nov 2007 11:40:25 +0000 Subject: [Fedora-xen] Fedora 8, qemu-kvm and networking In-Reply-To: References: Message-ID: <47417629.5030205@redhat.com> John Lagrue wrote: > Having installed F8 and tried out the latest virt-manager, I have to say I'm > impressed. > > But........I am still utterly baffled by guest networking. > > What I *want* to do is have a Windows XP guest that runs on the same network > as my laptop, the host; in other words, the guest should be able to access > all the network that the laptop can see. But I can't for the life of me find > out how to do this. I'm fairly sure this is not possible. Guests created with virt-manager (ie. libvirt) will want to talk to the bridge created by libvirtd. ie. They'll be started up with the following qemu -net options: /usr/bin/qemu-kvm [...] -net nic,macaddr=00:16:3e:86:61:81,vlan=0 -net tap,fd=12,script=,vlan=0 Networking is handled through a bridge (usually called virbr0) and IP addresses are assigned from a "private range", by default 192.168.122.X. The assignment of addresses and NAT to the "outside world" is done by a dnsmasq process. All of this means that the Windows guest won't be on the same network as the host, ie. broadcasts etc won't work. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Mon Nov 19 11:43:35 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 19 Nov 2007 11:43:35 +0000 Subject: [Fedora-xen] dom0 F7 crashes tcp_tso_segment oops - new kernel lag time In-Reply-To: <703764171.19681195152918547.JavaMail.root@zebra.lib.ucdavis.edu> References: <703764171.19681195152918547.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <474176E7.4010202@redhat.com> Dale Bewley wrote: > Running 2.6.20-2936.fc7xen x86_64 quad CPU, 16G. > > We have a dom0 with bridges riding on top of a VLAN interface. > > # brctl show > bridge name bridge id STP enabled interfaces > br101 8000.00093d139ae9 no eth0 > br6 8000.00093d139ae9 no vif2.0 > vif1.0 > eth0.6 > ... > > Inside a F7 domU on br6 we are running tc (via shorewall) to limit the bandwidth of a mirror server. On Monday I throttled the bandwidth down far below the demand. Since then we are starting to see dom0 crash and reboot with nothing in the log. > > Crashes happened on Tues around 9am and Thursday (today) around 4am and 9am. I caught the console during the most recent crash: > > Unable to handle kernel NULL pointer dereference at 0000000000000030 RIP: > [] tcp_tso_segment+0x1d8/0x285 > PGD 3db8f1067 PUD 3db8f2067 PMD 0 > Oops: 0000 [1] SMP > last sysfs file: /devices/xen-backend/vbd-2-51712/statistics/wr_sect > CPU 1 > Modules linked in: loop netbk xenblktap blkbk autofs4 8021q bridge nf_conntrack_netbios_ns ipt_LdPid: 0, comm: swapper Not tainted 2.6.20-2936.fc7xen #1 > RIP: e030:[] [] tcp_tso_segment+0x1d8/0x285 > RSP: e02b:ffff880002f77950 EFLAGS: 00010216 > RAX: 0000000000007a21 RBX: 0000000000000000 RCX: 0000000000000000 > RDX: 0000000010130000 RSI: 0000000000000000 RDI: 0000000087e8b626 > RBP: 000000000000fa87 R08: 0000000187e8b625 R09: 0000000000000000 > R10: 000000009b9a7b25 R11: 0000000000000003 R12: ffff88034ecab034 > R13: 0000000017acfe00 R14: 0000000000000020 R15: 00000000ffff0000 > FS: 00002aaaab0ff230(0000) GS:ffffffff80580080(0000) knlGS:0000000000000000 > > We are up to date with patches. After the first 2 crashes and before the 3rd I upgraded from xen-3.1.0-6.fc7 to xen-3.1.0-8.fc7 and rebooted dom0 for good measure. > > I did some googling and found this: > http://lists.openwall.net/netdev/2007/02/09/16 > which seems pretty similar. > > Assuming this is the problem and there is a fix I'm left to ask what is the ETA for a new xen kernel and what is the typical lag time? > > Current state is 2.6.23.1-21.fc7 vs. 2.6.20-2936.fc7xen I wonder if it is worth your while trying the Xen stack & kernel from F8? Currently kernel-xen 2.6.21-2950 and xen 3.1.0-13. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Mon Nov 19 11:53:34 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 19 Nov 2007 11:53:34 +0000 Subject: [Fedora-xen] Attaching a virtual CD to an existing domu? In-Reply-To: <473CC400.4060804@herakles.homelinux.org> References: <473CC400.4060804@herakles.homelinux.org> Message-ID: <4741793E.1070103@redhat.com> John Summerfield wrote: > Is there a particular reason the install DVD image doesn't, by default, > remain attached? There's a (faulty) assumption here that after the first boot the DVD image is no longer needed, so we unmount it. This is/was due to be fixed (mainly because it's completely the wrong thing to do for Windows) but my Bugzilla-fu isn't up to it this morning and I can't find the tracker bug. Anyway, easiest thing in Debian is probably just to edit /etc/apt/sources.list and remove the CD-ROM lines. With those removed, apt will just go to the network to get updates rather than trying and failing to mount local CDs. 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 dlbewley at lib.ucdavis.edu Mon Nov 19 18:20:24 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Mon, 19 Nov 2007 10:20:24 -0800 (PST) Subject: [Fedora-xen] dom0 F7 crashes tcp_tso_segment oops - new kernel lag time In-Reply-To: <474176E7.4010202@redhat.com> Message-ID: <1482635762.83471195496424469.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Richard W.M. Jones" wrote: > Dale Bewley wrote: > > Current state is 2.6.23.1-21.fc7 vs. 2.6.20-2936.fc7xen > > I wonder if it is worth your while trying the Xen stack & kernel from > > F8? Currently kernel-xen 2.6.21-2950 and xen 3.1.0-13. If you think that is safe-ish, I can try it. However, I have not had a crash since I posted. Maybe thanks to a slight tapering off of F8 mirror traffic on this box. What's the process of the above kernel and xen releases making it into F7-Updates? I assume the user population is a bit smaller in this realm, so focus is always on the dev release and updates are more ad hoc? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From dlbewley at lib.ucdavis.edu Mon Nov 19 18:56:32 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Mon, 19 Nov 2007 10:56:32 -0800 (PST) Subject: [Fedora-xen] xenbr0 missing on fedora 8 In-Reply-To: <000601c828ef$cdac1200$3201a8c0@athlon> Message-ID: <1840949286.84531195498592051.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Thomas von Steiger" wrote: > Hello, > > I try to kickstart domU's on fedora 8 because there is no xenbr0. > The only bridge i can found is virbr0 and this bridge is running on > 192.168.22.0 > My kickstart source is located on 192.168.1.0 and new guest's can't > access > this network. > > "virsh net-list" list network "default" with state "active" and > "autostart". > How I can bring back automatically xenbr0 on eth0 without create > ifcfg-xenbr0 ? > It sounds like all you really care about is having the bridge on the correct subnet since you don't want to mess with network-scripts. Try this # virsh net-dumpxml default > net.xml Edit net.xml then do a # virsh net-define net.xml -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From samfw at redhat.com Mon Nov 19 19:19:13 2007 From: samfw at redhat.com (Sam Folk-Williams) Date: Mon, 19 Nov 2007 14:19:13 -0500 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <4731BDC1.8050902@silkspeed.com> References: <4731BDC1.8050902@silkspeed.com> Message-ID: <4741E1B1.3070809@redhat.com> Aaron Metzger wrote: > > I am trying to migrate my virtualization infrastructure from a pure Xen > implementation to the more versatile Fedora virt-manager Xen/KVM > environment. While doing this, I have hit some snags related to areas > in which pure Xen documentation no longer applies due to the presence of > lib-virt et al. > > First a minor comment on the Fedora8VirtQuickStart (draft I know): > > The section: > >> Building a Fedora Guest System using `virt-manager` > > no longer applies because between Fedora 7 and Fedora 8 there no longer > appears to be a "New" button or a "File New" option in virt-manager. It > would appear that the only way to create a DomU is by way of virt-install. > The doc needs updating. I did some updating this weekend. The button is not as obvious now but it is still there (you have to right-click on the hypervisor to see the "New" option. I'm not sure why this changed, but I have updated that bit. Th anks, Sam > Now, my problem. > > I have successfully created fully functional guest VMs which work > perfectly in every way but, in the context of lib-virt and virsh, I can > not figure out how to get the guest machines to be started automatically > when the host machine boots. In a pure Xen environment, you > symbolically link the "/etc/xen/" file into "/etc/xen/auto". > After using virt-install to create the guest, the domain configuration > files end up over in "/var/lib/xend/domains". I have tried to > symbolically link the whole domain directory to "/etc/xen/auto", I have > tried to link the configuration file to "/etc/xen/auto". I have tried > to export the configuration as XML using virsh and then put that under > "/etc/xen/auto". Nothing works and there is no indication from the > xend.log that it is even trying to start the guest domains on bootup. > > I also tried to use: > > virsh autostart > > and get the error: > > libvir: error : this function is not supported by the hypervisor: > virDomainSetAutostart > > So, my question is, is it possible to properly manage the start up and > shut down of guest domains on host start up and shutdown or is that just > not supported yet. > > If there is a way to do this, it would be a very helpful section to add > to the Quick Start document because I would expect anyone migrating from > a pure Xen environment to have the same issue. Google reveals that > several have asked this question in the past on Fedora 7 etc and I have > not seen any answer other than people suggesting to link the > configuration file under "/etc/xen/auto". > > Thanks, > Aaron > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From debian at herakles.homelinux.org Tue Nov 20 05:57:29 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Tue, 20 Nov 2007 14:57:29 +0900 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <4741E1B1.3070809@redhat.com> References: <4731BDC1.8050902@silkspeed.com> <4741E1B1.3070809@redhat.com> Message-ID: <47427749.3040907@herakles.homelinux.org> Sam Folk-Williams wrote: > Aaron Metzger wrote: >> >> I am trying to migrate my virtualization infrastructure from a pure >> Xen implementation to the more versatile Fedora virt-manager Xen/KVM >> environment. While doing this, I have hit some snags related to areas >> in which pure Xen documentation no longer applies due to the presence >> of lib-virt et al. >> >> First a minor comment on the Fedora8VirtQuickStart (draft I know): >> >> The section: >> >>> Building a Fedora Guest System using `virt-manager` >> >> no longer applies because between Fedora 7 and Fedora 8 there no >> longer appears to be a "New" button or a "File New" option in >> virt-manager. It would appear that the only way to create a DomU is >> by way of virt-install. >> > > The doc needs updating. I did some updating this weekend. The button is > not as obvious now but it is still there (you have to right-click on the > hypervisor to see the "New" option. I'm not sure why this changed, but I > have updated that bit. That's bizarre. According to the web site, you employed "UI Interface Designers." I think you need new designers, that's far from intuitive. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 Please do not reply off-list From samfw at redhat.com Tue Nov 20 16:01:14 2007 From: samfw at redhat.com (Sam Folk-Williams) Date: Tue, 20 Nov 2007 11:01:14 -0500 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <47427749.3040907@herakles.homelinux.org> References: <4731BDC1.8050902@silkspeed.com> <4741E1B1.3070809@redhat.com> <47427749.3040907@herakles.homelinux.org> Message-ID: <474304CA.8010703@redhat.com> John Summerfield wrote: > Sam Folk-Williams wrote: >> Aaron Metzger wrote: >>> >>> I am trying to migrate my virtualization infrastructure from a pure >>> Xen implementation to the more versatile Fedora virt-manager Xen/KVM >>> environment. While doing this, I have hit some snags related to >>> areas in which pure Xen documentation no longer applies due to the >>> presence of lib-virt et al. >>> >>> First a minor comment on the Fedora8VirtQuickStart (draft I know): >>> >>> The section: >>> >>>> Building a Fedora Guest System using `virt-manager` >>> >>> no longer applies because between Fedora 7 and Fedora 8 there no >>> longer appears to be a "New" button or a "File New" option in >>> virt-manager. It would appear that the only way to create a DomU is >>> by way of virt-install. >>> >> >> The doc needs updating. I did some updating this weekend. The button >> is not as obvious now but it is still there (you have to right-click >> on the hypervisor to see the "New" option. I'm not sure why this >> changed, but I have updated that bit. > > That's bizarre. According to the web site, you employed "UI Interface > Designers." > > I think you need new designers, that's far from intuitive. > Lucky for us they are happy to take suggestions and improve! Figured this out - They had to remove the global new button, because the UI now allows multiple hypervisor connections. So you need to be able to have a new button that is linked to a specific connection. The button is now there for each hypervisor on the right side. I didn't see the button before. If you right-click, that's a second way to access it. I don't think it will be too hard to make the button more obvious. -Sam > > From berrange at redhat.com Tue Nov 20 16:08:36 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 20 Nov 2007 16:08:36 +0000 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <47427749.3040907@herakles.homelinux.org> References: <4731BDC1.8050902@silkspeed.com> <4741E1B1.3070809@redhat.com> <47427749.3040907@herakles.homelinux.org> Message-ID: <20071120160836.GF31236@redhat.com> On Tue, Nov 20, 2007 at 02:57:29PM +0900, John Summerfield wrote: > Sam Folk-Williams wrote: > >Aaron Metzger wrote: > >> > >>I am trying to migrate my virtualization infrastructure from a pure > >>Xen implementation to the more versatile Fedora virt-manager Xen/KVM > >>environment. While doing this, I have hit some snags related to areas > >>in which pure Xen documentation no longer applies due to the presence > >>of lib-virt et al. > >> > >>First a minor comment on the Fedora8VirtQuickStart (draft I know): > >> > >>The section: > >> > >>>Building a Fedora Guest System using `virt-manager` > >> > >>no longer applies because between Fedora 7 and Fedora 8 there no > >>longer appears to be a "New" button or a "File New" option in > >>virt-manager. It would appear that the only way to create a DomU is > >>by way of virt-install. > >> > > > >The doc needs updating. I did some updating this weekend. The button is > >not as obvious now but it is still there (you have to right-click on the > >hypervisor to see the "New" option. I'm not sure why this changed, but I > >have updated that bit. > > That's bizarre. According to the web site, you employed "UI Interface > Designers." > > I think you need new designers, that's far from intuitive. I've already stated this will be fixed in the next release to make it more obvious again. In the meantime, patches are welcomed, or you can just continue whining & making sarcastic comments. 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 kamron22 at yahoo.com Tue Nov 20 16:30:20 2007 From: kamron22 at yahoo.com (Kamron B) Date: Tue, 20 Nov 2007 08:30:20 -0800 (PST) Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <47427749.3040907@herakles.homelinux.org> Message-ID: <316900.40491.qm@web31103.mail.mud.yahoo.com> --- John Summerfield wrote: > Sam Folk-Williams wrote: > > Aaron Metzger wrote: > >> > >> I am trying to migrate my virtualization > infrastructure from a pure > >> Xen implementation to the more versatile Fedora > virt-manager Xen/KVM > >> environment. While doing this, I have hit some > snags related to areas > >> in which pure Xen documentation no longer applies > due to the presence > >> of lib-virt et al. > >> > >> First a minor comment on the > Fedora8VirtQuickStart (draft I know): > >> > >> The section: > >> > >>> Building a Fedora Guest System using > `virt-manager` > >> > >> no longer applies because between Fedora 7 and > Fedora 8 there no > >> longer appears to be a "New" button or a "File > New" option in > >> virt-manager. It would appear that the only way > to create a DomU is > >> by way of virt-install. > >> > > > > The doc needs updating. I did some updating this > weekend. The button is > > not as obvious now but it is still there (you have > to right-click on the > > hypervisor to see the "New" option. I'm not sure > why this changed, but I > > have updated that bit. > > That's bizarre. According to the web site, you > employed "UI Interface > Designers." > > I think you need new designers, that's far from > intuitive. > > > > -- > > Cheers > John > > -- spambait > 1aaaaaaa at coco.merseine.nu > Z1aaaaaaa at coco.merseine.nu > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html > http://support.microsoft.com/kb/555375 > > Please do not reply off-list > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ From kamron22 at yahoo.com Tue Nov 20 16:42:08 2007 From: kamron22 at yahoo.com (Kamron B) Date: Tue, 20 Nov 2007 08:42:08 -0800 (PST) Subject: [Fedora-xen] Slow Disk I/O with Xen in Linux In-Reply-To: <316900.40491.qm@web31103.mail.mud.yahoo.com> Message-ID: <125080.1629.qm@web31102.mail.mud.yahoo.com> The issue is described bellow: When running Windows Vista ultimate in a domain with two vcpus, and then do a heavy disk IO in domain0, the Vista will blue screen with such message "a clock interrupt was not received on a secondary processor within the allocated time interval" with Bug Check 0x101. This bug can always be reproduced by running the memory testing from Linux Performance Testing suite in domain 0. Note: domain 0 must use the hard disk as swap place. I need some helps from Linux expert. Why the system is very slow when you access the hard disk frequently under Linux? Does it allowed to preempt when do disk i/o access from 2.6.18 Linux kernel? The detailed process of disk I/O handler under Linux. The interrupt status, the cpu status and buffer lock ____________________________________________________________________________________ Be a better pen pal. Text or chat with friends inside Yahoo! Mail. See how. http://overview.mail.yahoo.com/ From ametzger at silkspeed.com Tue Nov 20 18:55:33 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Tue, 20 Nov 2007 13:55:33 -0500 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM Message-ID: <47432DA5.8060403@silkspeed.com> First let me say that I love the way virtualization has been integrated into Fedora! Thanks to all who have done this work. I have a simple question which is a little off-topic but I know that the experience is contained in this group of folks. Using the final release of Fedora 8 plus all released patches, I created an LVM volume group and an Ext3 logical volume upon which I am storing all of my Xen virtual machine images as normal files. I tried to use the system-config-lvm tool to create a snapshot of the logical volume and assigned it to a mount point that I created under "/mnt/vmbackups" and checked the box to have it mounted at boot time. When I rebooted the machine, the boot failed when It tried to access the snapshot logical volume. I'm not going to include the specific errors here because my question is much more general. Do snapshots of logical volumes work under Fedora 8? Google revealed some historical discussions about snapshots not working in the transition from LVM1 to LVM2. Is that the case? Is anyone successful creating logical volume snapshots under Fedora 8? Alternatively, is there any other reliable way to make a self-consistent copy of a running Xen virtual machine image for the case where the Xen virtual machine is held in a regular file system file? Is LVM my only option? Thanks in advance for any and all help. -- Aaron From samfw at redhat.com Wed Nov 21 15:16:31 2007 From: samfw at redhat.com (Sam Folk-Williams) Date: Wed, 21 Nov 2007 10:16:31 -0500 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <47432DA5.8060403@silkspeed.com> References: <47432DA5.8060403@silkspeed.com> Message-ID: <47444BCF.2010909@redhat.com> Hi, Aaron Metzger wrote: > First let me say that I love the way virtualization has been integrated > into Fedora! Thanks to all who have done this work. > > I have a simple question which is a little off-topic but I know that the > experience is contained in this group of folks. > > Using the final release of Fedora 8 plus all released patches, I created > an LVM volume group and an Ext3 logical volume upon which I am storing > all of my Xen virtual machine images as normal files. > > I tried to use the system-config-lvm tool to create a snapshot of the > logical volume and assigned it to a mount point that I created under > "/mnt/vmbackups" and checked the box to have it mounted at boot time. > > When I rebooted the machine, the boot failed when It tried to access the > snapshot logical volume. I'm not going to include the specific errors > here because my question is much more general. > > Do snapshots of logical volumes work under Fedora 8? Google revealed > some historical discussions about snapshots not working in the > transition from LVM1 to LVM2. Is that the case? Is anyone successful > creating logical volume snapshots under Fedora 8? > They definitely work. Thought there might be a better approach. For example, the simplest way is to make a separate LV for each quest. Then you make a snapshot of that LV to "clone" that guest, or to save it as a backup. > Alternatively, is there any other reliable way to make a self-consistent > copy of a running Xen virtual machine image for the case where the Xen > virtual machine is held in a regular file system file? Is LVM my only > option? For a single file you can just copy the file... with, say, cp or dd. -Sam > > Thanks in advance for any and all help. > > -- > Aaron > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From ametzger at silkspeed.com Wed Nov 21 21:15:30 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Wed, 21 Nov 2007 16:15:30 -0500 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <47444BCF.2010909@redhat.com> References: <47432DA5.8060403@silkspeed.com> <47444BCF.2010909@redhat.com> Message-ID: <47449FF2.7090906@silkspeed.com> Sam Folk-Williams wrote: > > >> Alternatively, is there any other reliable way to make a >> self-consistent copy of a running Xen virtual machine image for the >> case where the Xen virtual machine is held in a regular file system >> file? Is LVM my only option? > > For a single file you can just copy the file... with, say, cp or dd. > Thanks for the reply, but I thought that this is not a valid thing to do for a RUNNING guest. I think that the file will be changing too rapidly (guest machine swap etc) to get a self-consistent copy using just "cp" or "dd". Right? -- Aaron M. From pbruna at it-linux.cl Wed Nov 21 21:59:28 2007 From: pbruna at it-linux.cl (Patricio A. Bruna) Date: Wed, 21 Nov 2007 18:59:28 -0300 (CLST) Subject: [Fedora-xen] VMs configuration files Message-ID: <23662316.17581195682368611.JavaMail.root@lisa.itlinux.cl> Hi, How can i define another folder for store the VMs configurations files, for default is /etc/xen Thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: From armbru at redhat.com Thu Nov 22 07:25:24 2007 From: armbru at redhat.com (Markus Armbruster) Date: Thu, 22 Nov 2007 08:25:24 +0100 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <47449FF2.7090906@silkspeed.com> (Aaron Metzger's message of "Wed\, 21 Nov 2007 16\:15\:30 -0500") References: <47432DA5.8060403@silkspeed.com> <47444BCF.2010909@redhat.com> <47449FF2.7090906@silkspeed.com> Message-ID: <87abp63fob.fsf@pike.pond.sub.org> Aaron Metzger writes: > Sam Folk-Williams wrote: >> >> >>> Alternatively, is there any other reliable way to make a >>> self-consistent copy of a running Xen virtual machine image for the >>> case where the Xen virtual machine is held in a regular file system >>> file? Is LVM my only option? >> >> For a single file you can just copy the file... with, say, cp or dd. >> > > Thanks for the reply, but I thought that this is not a valid thing to > do for a RUNNING guest. I think that the file will be changing too > rapidly (guest machine swap etc) to get a self-consistent copy using > just "cp" or "dd". Right? Right. From rjones at redhat.com Fri Nov 23 10:14:38 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 23 Nov 2007 10:14:38 +0000 Subject: [Fedora-xen] Re: unionfs question In-Reply-To: <4746A640.7020105@cs.tu-berlin.de> References: <4746A640.7020105@cs.tu-berlin.de> Message-ID: <4746A80E.4010509@redhat.com> Christoph H?ger wrote: > I have a more general question about unionfs: > I want to build a xen machine with a save base-image and a temporary > write image that can be saved or thrown away on demand. So I thought > about using unionfs to mount both these images as /. > The problem is: unionfs does not mount images but directories that are > already mounted. So I would need to mount those two images somewhere > else. Obviuosly this would happen somewhere above / (e.g. /workimage and > /rootimage). Could unionfs handle this? > Or is there even a better way? LVM + snapshots. http://tldp.org/HOWTO/LVM-HOWTO/snapshotintro.html BTW, there is a fedora-xen list for discussion of Xen issues. 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 nooroon at gmail.com Fri Nov 23 10:22:17 2007 From: nooroon at gmail.com (mathieu rohon) Date: Fri, 23 Nov 2007 11:22:17 +0100 Subject: [Fedora-xen] recompile for using sdl and vnc Message-ID: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> Hello, I'm using fedora 7 with xen 3.1 from binaries rpm. I try to use the sdl display, but when i configure my VM with * * no window pops up. Thanks to goolgle, I've found someone how got the same issue, and it seems that qemu-dm was not compile whith sdl support. What is the best way to recompile qemu-dm whith sdl support? In fact, I'd like to have sdl for local display of my VM, and vnc for remote access to it. What configuration should I use to do so? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From sct at redhat.com Fri Nov 23 12:00:20 2007 From: sct at redhat.com (Stephen C. Tweedie) Date: Fri, 23 Nov 2007 12:00:20 +0000 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <47432DA5.8060403@silkspeed.com> References: <47432DA5.8060403@silkspeed.com> Message-ID: <1195819220.6590.4.camel@sisko.scot.redhat.com> Hi, On Tue, 2007-11-20 at 13:55 -0500, Aaron Metzger wrote: > I tried to use the system-config-lvm tool to create a snapshot of the > logical volume and assigned it to a mount point that I created under > "/mnt/vmbackups" and checked the box to have it mounted at boot time. OK, that should work... *IF* you are careful about some of the gotchas concerning snapshots. Namely... if you're mounting them, be aware that the original filesystem and its snapshot will both have the same UUID and filesystem label. So if you try to mount-by-label (eg. "LABEL=foo" in fstab), you can't guarantee which one will be picked up. Now, filesystems set up by anaconda on LVM should be specified in /etc/fstab by their LVM path, not by their label. But if you have set up the fstab entry yourself by label, then you might well confuse the system. > When I rebooted the machine, the boot failed when It tried to access the > snapshot logical volume. I'm not going to include the specific errors > here because my question is much more general. Well, in general it should work.. we'd need to see the error to know if there's a special-case you've fallen into. Cheers, Stephen From kamal.behpoornia at intel.com Tue Nov 20 16:36:17 2007 From: kamal.behpoornia at intel.com (Behpoornia, Kamal) Date: Tue, 20 Nov 2007 08:36:17 -0800 Subject: [Fedora-xen] RE: The BSOD 0x101 description In-Reply-To: References: Message-ID: The issue is described bellow: When running Windows Vista ultimate in a domain with two vcpus, and then do a heavy disk IO in domain0, the Vista will blue screen with such message "a clock interrupt was not received on a secondary processor within the allocated time interval" with Bug Check 0x101. This bug can always be reproduced by running the memory testing from Linux Performance Testing suite in domain 0. Note: domain 0 must use the hard disk as swap place. I need some helps from Linux expert. 1. Why the system is very slow when you access the hard disk frequently under Linux? 2. Does it allowed to preempt when do disk i/o access from 2.6.18 Linux kernel? 3. The detailed process of disk I/O handler under Linux. The interrupt status, the cpu status and buffer lock. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Fri Nov 23 14:17:22 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 23 Nov 2007 14:17:22 +0000 Subject: [Fedora-xen] RE: The BSOD 0x101 description In-Reply-To: References: Message-ID: <4746E0F2.4000402@redhat.com> Behpoornia, Kamal wrote: > The issue is described bellow: > When running Windows Vista ultimate in a domain with two vcpus, > and then do a heavy disk IO in domain0, the Vista will blue screen with > such message "a clock interrupt was not received on a secondary > processor within the allocated time interval" with Bug Check 0x101. > This bug can always be reproduced by running the memory testing from > Linux Performance Testing suite in domain 0. Note: domain 0 must use the > hard disk as swap place. > > I need some helps from Linux expert. > 1. Why the system is very slow when you access the hard disk > frequently under Linux? > 2. Does it allowed to preempt when do disk i/o access from 2.6.18 > Linux kernel? > 3. The detailed process of disk I/O handler under Linux. The > interrupt status, the cpu status and buffer lock. Can you open a bug report about this at http://bugzilla.redhat.com please. Be sure to include all details of your system, in particular exact version numbers for each relevant component (kernel, xen, etc.) 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 armbru at redhat.com Fri Nov 23 16:12:16 2007 From: armbru at redhat.com (Markus Armbruster) Date: Fri, 23 Nov 2007 17:12:16 +0100 Subject: [Fedora-xen] recompile for using sdl and vnc In-Reply-To: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> (mathieu rohon's message of "Fri\, 23 Nov 2007 11\:22\:17 +0100") References: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> Message-ID: <871wahx7of.fsf@pike.pond.sub.org> "mathieu rohon" writes: > Hello, > > I'm using fedora 7 with xen 3.1 from binaries rpm. > I try to use the sdl display, but when i configure my VM with > > * > * > no window pops up. > Thanks to goolgle, I've found someone how got the same issue, and it > seems that qemu-dm was not compile whith sdl support. > What is the best way to recompile qemu-dm whith sdl support? > > In fact, I'd like to have sdl for local display of my VM, and vnc for > remote access to it. > What configuration should I use to do so? > > Thanks Support for the SDL display in libvirt is incomplete[*]. You'd have to bypass libvirt to use it. Are you sure you really need SDL? It has a serious usability problem: if you close its window, the PV framebuffer backend terminates, and you have to reboot the guest to get another one[**]. Why can't you stick to VNC? It works fine locally. Sorry, I can't answer you question on qemu-dm. [*] https://bugzilla.redhat.com/show_bug.cgi?id=240233 [**] Actually, you can restart the backend by hand, if you know what you're doing. Cheesy hacks in the backend make this work. From berrange at redhat.com Fri Nov 23 16:41:50 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 23 Nov 2007 16:41:50 +0000 Subject: [Fedora-xen] recompile for using sdl and vnc In-Reply-To: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> References: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> Message-ID: <20071123164150.GD11721@redhat.com> On Fri, Nov 23, 2007 at 11:22:17AM +0100, mathieu rohon wrote: > Hello, > > I'm using fedora 7 with xen 3.1 from binaries rpm. > I try to use the sdl display, but when i configure my VM with > > * > * > no window pops up. > Thanks to goolgle, I've found someone how got the same issue, and it > seems that qemu-dm was not compile whith sdl support. > What is the best way to recompile qemu-dm whith sdl support? > > In fact, I'd like to have sdl for local display of my VM, and vnc for > remote access to it. You can't have both. You have to choose one, and VNC is the only sane one to choose. SDL sucks because if your X session dies, it kills the SDL window & thus kills your VM. Not cool. The 'virt-viewer' program can be used to popup a minimal window for a VNC display whether local or remote. 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 debian at herakles.homelinux.org Sun Nov 25 05:53:08 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 25 Nov 2007 14:53:08 +0900 Subject: [Fedora-xen] Re: unionfs question In-Reply-To: <4746A80E.4010509@redhat.com> References: <4746A640.7020105@cs.tu-berlin.de> <4746A80E.4010509@redhat.com> Message-ID: <47490DC4.3050305@herakles.homelinux.org> Richard W.M. Jones wrote: > Christoph H??ger wrote: >> I have a more general question about unionfs: >> I want to build a xen machine with a save base-image and a temporary >> write image that can be saved or thrown away on demand. So I thought >> about using unionfs to mount both these images as /. >> The problem is: unionfs does not mount images but directories that are >> already mounted. So I would need to mount those two images somewhere >> else. Obviuosly this would happen somewhere above / (e.g. /workimage >> and /rootimage). Could unionfs handle this? >> Or is there even a better way? > > LVM + snapshots. > > http://tldp.org/HOWTO/LVM-HOWTO/snapshotintro.html > > BTW, there is a fedora-xen list for discussion of Xen issues. There is, but this doesn't seem to me to be a xen question; take xen out of it, and the question still stands. That said, there is z xen solution documented in /usr/share/doc/xen-3.0.3/pdf/user.pdf " 6.3 Using LVM-backed VBDs" in my Sl5 system. Read the information for the version of xen you're running. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From debian at herakles.homelinux.org Sun Nov 25 09:45:40 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sun, 25 Nov 2007 18:45:40 +0900 Subject: [Fedora-xen] Newbie Virt Questions and comments on wiki/Docs/Fedora8VirtQuickStart In-Reply-To: <20071120160836.GF31236@redhat.com> References: <4731BDC1.8050902@silkspeed.com> <4741E1B1.3070809@redhat.com> <47427749.3040907@herakles.homelinux.org> <20071120160836.GF31236@redhat.com> Message-ID: <47494444.7070909@herakles.homelinux.org> Daniel P. Berrange wrote: > On Tue, Nov 20, 2007 at 02:57:29PM +0900, John Summerfield wrote: >> Sam Folk-Williams wrote: >>> Aaron Metzger wrote: >>>> I am trying to migrate my virtualization infrastructure from a pure >>>> Xen implementation to the more versatile Fedora virt-manager Xen/KVM >>>> environment. While doing this, I have hit some snags related to areas >>>> in which pure Xen documentation no longer applies due to the presence >>>> of lib-virt et al. >>>> >>>> First a minor comment on the Fedora8VirtQuickStart (draft I know): >>>> >>>> The section: >>>> >>>>> Building a Fedora Guest System using `virt-manager` >>>> no longer applies because between Fedora 7 and Fedora 8 there no >>>> longer appears to be a "New" button or a "File New" option in >>>> virt-manager. It would appear that the only way to create a DomU is >>>> by way of virt-install. >>>> >>> The doc needs updating. I did some updating this weekend. The button is >>> not as obvious now but it is still there (you have to right-click on the >>> hypervisor to see the "New" option. I'm not sure why this changed, but I >>> have updated that bit. >> That's bizarre. According to the web site, you employed "UI Interface >> Designers." >> >> I think you need new designers, that's far from intuitive. > > I've already stated this will be fixed in the next release to make it more > obvious again. In the meantime, patches are welcomed, or you can just > continue whining & making sarcastic comments. I'm pleased it's being changed. If you think I was making sarcastic comments, you've mistaken my intent. It was heartfelt, and on reflection, fair comment. I really do not like the UI design. As for patches, not from me. I can struggle out a bit of Perl if I must, but Python has me beaten. My time's better spent helping people come to terms with getting their Linux systems working. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From rjones at redhat.com Mon Nov 26 08:32:50 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 26 Nov 2007 08:32:50 +0000 Subject: [Fedora-xen] VMs configuration files In-Reply-To: <23662316.17581195682368611.JavaMail.root@lisa.itlinux.cl> References: <23662316.17581195682368611.JavaMail.root@lisa.itlinux.cl> Message-ID: <474A84B2.1000705@redhat.com> Patricio A. Bruna wrote: > How can i define another folder for store the VMs configurations files, for default is /etc/xen I don't think it's possible to change /etc/xen, but if you use the libvirt-based tools you can store your XML configuration files wherever you like: mkdir myconfigs; cd myconfigs virsh dumpxml domname > domname.xml # to get XML config virsh define domname.xml # to change XML config 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 nooroon at gmail.com Mon Nov 26 14:18:19 2007 From: nooroon at gmail.com (mathieu rohon) Date: Mon, 26 Nov 2007 15:18:19 +0100 Subject: [Fedora-xen] recompile for using sdl and vnc In-Reply-To: <20071123164150.GD11721@redhat.com> References: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> <20071123164150.GD11721@redhat.com> Message-ID: <7675761b0711260618v6d3ba304m733926efc9e7dffb@mail.gmail.com> With sdl display, I don't any mouse and keyboard issues, that's not the case in VNC. Tha fact that te VM dies when the X session dies is not a matter for me. My aim is to have a Windows VM which works as if it was not in a VM. Thanks to sdl display, the windows VM is more fluid. But I'd like to use VNC if I can have the same result. In a second hand, I'd like to have a local AND remote display. With VNC, I can't have both at the same time. I though that I could have it thanks to SDL (for local) and VNC (for remote). Is there a way, with VNC, to configure two access (local and remote) to the VM at the same time? 2007/11/23, Daniel P. Berrange : > > On Fri, Nov 23, 2007 at 11:22:17AM +0100, mathieu rohon wrote: > > Hello, > > > > I'm using fedora 7 with xen 3.1 from binaries rpm. > > I try to use the sdl display, but when i configure my VM with > > > > * > > * > > no window pops up. > > Thanks to goolgle, I've found someone how got the same issue, and it > > seems that qemu-dm was not compile whith sdl support. > > What is the best way to recompile qemu-dm whith sdl support? > > > > In fact, I'd like to have sdl for local display of my VM, and vnc for > > remote access to it. > > You can't have both. You have to choose one, and VNC is the only sane > one to choose. SDL sucks because if your X session dies, it kills the > SDL window & thus kills your VM. Not cool. The 'virt-viewer' program > can be used to popup a minimal window for a VNC display whether local > or remote. > > Dan. > -- > |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 > -=| > |=- Perl modules: http://search.cpan.org/~danberr/ > -=| > |=- Projects: http://freshmeat.net/~danielpb/ > -=| > |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B > 9505 -=| > -------------- next part -------------- An HTML attachment was scrubbed... URL: From spencer at beyondabstraction.net Mon Nov 26 16:37:13 2007 From: spencer at beyondabstraction.net (Spencer Shimko) Date: Mon, 26 Nov 2007 11:37:13 -0500 Subject: [Fedora-xen] ppc64 xen support Message-ID: Hi, I was looking for any information people may have on running Fedora 8 Xen on a PPC64 platform. Xen appears to support ppc64 but none of the Fedora pages seem to mention it and Fedora doesn't have a ppc64 Xen kernel. Anyone taken a swing at this or have any thoughts on where I should focus my efforts? Thanks, Spencer From berrange at redhat.com Mon Nov 26 16:40:51 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Mon, 26 Nov 2007 16:40:51 +0000 Subject: [Fedora-xen] ppc64 xen support In-Reply-To: References: Message-ID: <20071126164051.GQ31847@redhat.com> On Mon, Nov 26, 2007 at 11:37:13AM -0500, Spencer Shimko wrote: > Hi, > > I was looking for any information people may have on running Fedora 8 Xen on > a PPC64 platform. Xen appears to support ppc64 but none of the Fedora pages > seem to mention it and Fedora doesn't have a ppc64 Xen kernel. Libvirt & the tools stack is able to build on PPC & we've have patches to fix PPC portability issues. The main blocker is that we don't have a PPC kernel for Xen that is usable. Without that we can't build the Xen userspace. > Anyone taken a swing at this or have any thoughts on where I should focus my > efforts? You should probably ask on the Fedora PPC mailing list http://lists.infradead.org/mailman/listinfo/fedora-ppc 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 spencer at beyondabstraction.net Mon Nov 26 18:20:23 2007 From: spencer at beyondabstraction.net (Spencer Shimko) Date: Mon, 26 Nov 2007 13:20:23 -0500 Subject: [Fedora-xen] ppc64 xen support In-Reply-To: <20071126164051.GQ31847@redhat.com> Message-ID: On 11/26/07 11:40 AM, "Daniel P. Berrange" wrote: > On Mon, Nov 26, 2007 at 11:37:13AM -0500, Spencer Shimko wrote: >> Hi, >> >> I was looking for any information people may have on running Fedora 8 Xen on >> a PPC64 platform. Xen appears to support ppc64 but none of the Fedora pages >> seem to mention it and Fedora doesn't have a ppc64 Xen kernel. > > Libvirt & the tools stack is able to build on PPC & we've have patches to > fix PPC portability issues. The main blocker is that we don't have a PPC > kernel for Xen that is usable. Without that we can't build the Xen userspace. > >> Anyone taken a swing at this or have any thoughts on where I should focus my >> efforts? > > You should probably ask on the Fedora PPC mailing list Thanks Dan. The libvirt + tool stack is working fine as your described. Running qemu VMs works as advertised for x86 emulation. I had noticed the Xen userland components missing as well and it makes sense now. Guess I'll focus on the kernel side for now. > > http://lists.infradead.org/mailman/listinfo/fedora-ppc Ah, another nice low-volume list :) I see your August thread in their archives: http://lists.infradead.org/pipermail/fedora-ppc/2007-August/001033.html I'm going to cross-post for now as responses might be of interest to subscribers of both lists. Any additional comments on the state of kernel-level Xen support from the PPC contingent? --Spencer > > Dan, From abraxis at telkomsa.net Mon Nov 26 19:31:23 2007 From: abraxis at telkomsa.net (Neil Thompson) Date: Mon, 26 Nov 2007 21:31:23 +0200 Subject: [Fedora-xen] Paravirt Gutsy Gibbon on F8? Message-ID: <20071126193123.GC6611@eeyore.32.boerneef.vornavalley> Hi all, Before I tear out what little hair I have left, has anyone managed to get Gutsy running in paravirt on F8? If so, please could you tell me how? (In short, simple sentences :-) I've tried just about everything, from installing it under KVM/QEMU and cutting the partitions out, to downloading xen images and nothing works properly - even if I run using the ubuntu supplied kernels. The downloaded from xensource kernels sort of work, until I try supplying an initrd to get consoles and things like that working and then the vm just sits there, eating up CPU. The ubuntu xen kernels also just boot to a particular point and stop - also eating CPU. Logs/dmesg available on request. Unfortunately, some people at work without much taste ;-} have decided they need to use ubuntu, and I have no wish to change my OS while labbing this stuff. TIA -- Cheers! (Relax...have a homebrew) Neil THEOREM: VI is perfect. PROOF: VI in roman numerals is 6. The natural numbers < 6 which divide 6 are 1, 2, and 3. 1+2+3 = 6. So 6 is a perfect number. Therefore, VI is perfect. QED -- Arthur Tateishi From rjones at redhat.com Tue Nov 27 14:14:22 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 27 Nov 2007 14:14:22 +0000 Subject: [Fedora-xen] recompile for using sdl and vnc In-Reply-To: <7675761b0711260618v6d3ba304m733926efc9e7dffb@mail.gmail.com> References: <7675761b0711230222u329e63f2hd83b611511a80619@mail.gmail.com> <20071123164150.GD11721@redhat.com> <7675761b0711260618v6d3ba304m733926efc9e7dffb@mail.gmail.com> Message-ID: <474C263E.7020705@redhat.com> mathieu rohon wrote: > With sdl display, I don't any mouse and keyboard issues, that's not the case > in VNC. Tha fact that te VM dies when the X session dies is not a matter for > me. > My aim is to have a Windows VM which works as if it was not in a VM. Thanks > to sdl display, the windows VM is more fluid. But I'd like to use VNC if I > can have the same result. Have you tried virt-viewer (it's in recent Fedora) instead of vncviewer or the default virt-manager widget? Also I've found that setting up libvirt to use a USB graphics tablet instead of the default PS/2 mouse improves mouse handling no end. > In a second hand, I'd like to have a local AND remote display. With VNC, I > can't have both at the same time. I though that I could have it thanks to > SDL (for local) and VNC (for remote). VNC should support screen sharing, if that's what you want. Or do you mean two separate displays? Perhaps rdesktop would suit you. > Is there a way, with VNC, to configure two access (local and remote) to the > VM at the same time? vncviewer -Shared. Not sure if there is a virt-viewer option for this. 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 dlbewley at lib.ucdavis.edu Tue Nov 27 22:20:32 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 27 Nov 2007 14:20:32 -0800 (PST) Subject: [Fedora-xen] dom0 F7 crashes tcp_tso_segment oops - new kernel lag time In-Reply-To: <1482635762.83471195496424469.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <2041431216.212181196202032261.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Dale Bewley" wrote: > ----- "Richard W.M. Jones" wrote: > > Dale Bewley wrote: > > > Current state is 2.6.23.1-21.fc7 vs. 2.6.20-2936.fc7xen > > > > I wonder if it is worth your while trying the Xen stack & kernel > from > > > > F8? Currently kernel-xen 2.6.21-2950 and xen 3.1.0-13. > > If you think that is safe-ish, I can try it. However, I have not had a > crash since I posted. Maybe thanks to a slight tapering off of F8 > mirror traffic on this box. > > What's the process of the above kernel and xen releases making it into > F7-Updates? I assume the user population is a bit smaller in this > realm, so focus is always on the dev release and updates are more ad > hoc? After a period of maybe 11 days of stable uptime we have had 4 crashes in the last 24 hours due to this tcp_tso_segment bug. Since there aren't many domUs on here *yet*, I think we're just going to go ahead and upgrade to F8 now. We'll gain the 2.6.21 kernel and hopefully somewhat more developer attention in general. I'm not sure why the 2.6.21 kernel-xen isn't backported from f8 to f7. Doesn't the most recent release get pretty much all the same updates? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From ametzger at silkspeed.com Wed Nov 28 03:53:41 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Tue, 27 Nov 2007 22:53:41 -0500 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <1195819220.6590.4.camel@sisko.scot.redhat.com> References: <47432DA5.8060403@silkspeed.com> <1195819220.6590.4.camel@sisko.scot.redhat.com> Message-ID: <474CE645.2050002@silkspeed.com> Stephen C. Tweedie wrote: > Hi, > > > Well, in general it should work.. we'd need to see the error to know if > there's a special-case you've fallen into. > A follow-up to describe what I have found regarding Fedora 8 and my attempts to use LVM snapshots to hold Xen guest images. Maybe it will help others. In general, I was unable to create any LVM snapshot with an out of the box configuration of a 64 bit Fedora 8 until I manually loaded the "dm-snapshot" kernel module. modprobe dm-snapshot Then, I was able to create a snapshot volume and all seemed fine until I rebooted the machine. The boot sequence failed with a message about "unable to expand snapshot volume" which I assume was caused again by the lack of the "dm-snapshot" module. I used the rescue disk to remove the snapshot volume and was able to boot my machine once again. I found a number of postings on the debian mailing lists from 2005 regarding the same issue and peoples attempts to get the "dm-snapshot" module to load during boot. I played around with modules.conf.d configuration to try to get the module to load on boot but didn't have any success. Do I need to make a custom boot/initrd script or am I on the wrong track? Ideas are welcome. In the mean time, I have resigned myself to just not ever rebooting the machine while any snapshot volumes exist. -- Aaron From debian at herakles.homelinux.org Wed Nov 28 09:13:13 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 28 Nov 2007 18:13:13 +0900 Subject: [Fedora-xen] Problem with network install, network wrong Message-ID: <474D3129.3000904@herakles.homelinux.org> I'm using the click-through wizard to try to network-install F8, fully-vertualised, on F8. My dhcpd configuration gives special treatment to PXE clients which it recognises: class "pxeclients" { match if substring (option vendor-class-identifier, 0, 9) = "PXEClient"; option vendor-class-identifier "PXEClient"; # At least one of the vendor-specific option must be set. We set # the MCAST IP address to 0.0.0.0 to tell the bootrom to still use # TFTP (address 0.0.0.0 is considered as "no address") # option PXE.mtftp-ip 192.168.9.1; vendor-option-space PXE; option PXE.mtftp-ip 0.0.0.0; vendor-option-space PXE; } and later, pool { allow members of "pxeclients"; default-lease-time 1800; max-lease-time 3600; range 192.168.9.150 192.168.9.169; filename "/PXE/pxelinux.0"; } I give etherboot clients special (different). treatment too. class "Etherboot" { match if substring (option vendor-class-identifier, 0, 13) = "Etherboot-5.0"; option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff; option vendor-class-identifier "Etherboot-5.0"; filename "tftpboot.vc"; } and IBM thin clients. Unfortunately, virt-manager tells the user it's using PXE, but something tells the DHCPD server it's etherboot. Here's a bit of 17:57:56.001102 IP (tos 0x0, ttl 60, id 0, offset 0, flags [none], proto 17, length: 576) Possum.demo.lan.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:16:3e:3a:0b:74, length: 548, xid:0x3e4202c2, flags: [none] (0x0000) Client Ethernet Address: 00:16:3e:3a:0b:74 Vendor-rfc1048: DHCP:REQUEST SID:ns.demo.lan RQ:Possum.demo.lan MSZ:1500 VC:"Etherboot-5.4" PR:SM+DG+HN+VO+RP+T128+T129+T130+T150 T150:175.5.1.16.236.129.57.177.2.3.0 17:57:56.004481 IP (tos 0x10, ttl 16, id 0, offset 0, flags [none], proto 17, length: 328) ns.demo.lan.bootps > Possum.demo.lan.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length: 300, xid:0x3e4202c2, flags: [none] (0x0000) Your IP: Possum.demo.lan Server IP: ns.demo.lan Client Ethernet Address: 00:16:3e:3a:0b:74 Vendor-rfc1048: DHCP:ACK SID:ns.demo.lan LT:84400 SM:255.255.255.0 DG:ns.demo.lan For this application, the "boot rom" needs to claim it's PXE. btw I can also recognise Macs (good to deal with openfirmware) Anaconda (a shame it won't use the filename I return), debian-installer -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From debian at herakles.homelinux.org Wed Nov 28 09:14:36 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 28 Nov 2007 18:14:36 +0900 Subject: [Fedora-xen] Problem with network install, console late to attach Message-ID: <474D317C.5030801@herakles.homelinux.org> Complicating my other network install is the problem that by the time the console's displayed, the boot process is all over. The "BIOS" needs to wait longer. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu -- Advice http://webfoot.com/advice/email.top.php http://www.catb.org/~esr/faqs/smart-questions.html http://support.microsoft.com/kb/555375 You cannot reply off-list:-) From dlbewley at lib.ucdavis.edu Wed Nov 28 21:22:07 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 28 Nov 2007 13:22:07 -0800 (PST) Subject: [Fedora-xen] kernel-xen crash dump analysis Message-ID: <1520014867.240791196284927831.JavaMail.root@zebra.lib.ucdavis.edu> After upgrading to F8 I still had a dom0 crash last night, but didn't catch any output. I think it's still the null pointer dereference in tcp_tso_segment, possibly brought to prominence by traffic shaping in a busy domU. I'd like to catch a crash dump the next time it happens so I can (hopefully) intelligently report this bug somewhere. I'm looking at http://fedoraproject.org/wiki/FC6KdumpKexecHowTo http://www.redhatmagazine.com/2007/08/15/a-quick-overview-of-linux-kernel-crash-dump-analysis/ There is no mention of Xen. I don't see a kernel-xen-debuginfo rpm for f8 or even f7, but there is one for f9 in rawhide it appears. Is kernel-debuginfo sufficient even if running xen? The versions differ, so I would imagine not. # yum --enablerepo=fedora-debuginfo list kernel-xen-debuginfo kernel-debuginfo Available Packages kernel-debuginfo.x86_64 2.6.23.1-49.fc8 updates-debuginf # rpm -q kernel kernel-xen kernel-2.6.23.1-49.fc8 kernel-xen-2.6.21-2950.fc8 Any advice on how capture some useful info from a crashing dom0 kernel? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From dlbewley at lib.ucdavis.edu Wed Nov 28 22:05:25 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 28 Nov 2007 14:05:25 -0800 (PST) Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <474CE645.2050002@silkspeed.com> Message-ID: <2006289882.246231196287525701.JavaMail.root@zebra.lib.ucdavis.edu> > Do I need to make a custom boot/initrd script or am I on the wrong > track? Ideas are welcome. Does your initrd contain dm-snapshot.ko? # cat initrd-2.6.21-2950.fc8xen.img | gunzip | cpio -vt | grep snapshot -rw------- 1 root root 34608 Nov 27 08:43 lib/dm-snapshot.ko -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From dlopez at humnet.ucla.edu Thu Nov 29 00:31:47 2007 From: dlopez at humnet.ucla.edu (Lopez, Denise) Date: Wed, 28 Nov 2007 16:31:47 -0800 Subject: [Fedora-xen] Best practices questions Message-ID: Hi all, I am in the process of building a new Xen server from scratch and wanted to ask a couple of questions about best practices. First, should the guest domains be image files or LVM's or just regular ext3 partitions? What are the pros and/or cons of each? Second, since the Dom0 is supposed to be kept secure, and most of my servers I don't install any X11 server on, is there any security risk installing an X11 server on the Dom0 in order to take advantage of the virt-manager GUI interface? Thank you in advance for any thoughts and or opinions. Denise Lopez UCLA - Center for Digital Humanities Network Services Linux Systems Engineer 337 Charles E. Young Drive East PPB 1020 Los Angeles, CA 90095-1499 310/206-8216 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 2230 bytes Desc: image001.jpg URL: From smooge at gmail.com Thu Nov 29 00:39:24 2007 From: smooge at gmail.com (Stephen John Smoogen) Date: Wed, 28 Nov 2007 17:39:24 -0700 Subject: [Fedora-xen] Best practices questions In-Reply-To: References: Message-ID: <80d7e4090711281639u479be25bl10172a3a662b167f@mail.gmail.com> On Nov 28, 2007 5:31 PM, Lopez, Denise wrote: > > > > > Hi all, > > > > I am in the process of building a new Xen server from scratch and wanted to > ask a couple of questions about best practices. > > > > First, should the guest domains be image files or LVM's or just regular ext3 > partitions? What are the pros and/or cons of each? > Are you talking about inside the guests or where the guests are in DomO? For the guests files on Dom0, I am using image files stored on DomO's LVM.. though I may follow some howtos on shared storage so that failover works in the future. Inside the guests, I am using ext3 direct in the image versus using LVM+ext3. I wanted things to be simple to understand for myself. > > > Second, since the Dom0 is supposed to be kept secure, and most of my > servers I don't install any X11 server on, is there any security risk > installing an X11 server on the Dom0 in order to take advantage of the > virt-manager GUI interface? > > I do not know of any major security issues... but you should use security in depth. 1) secure the logins 2) firewall the machine so that only ssh X port forwarding is available 3) keep the system up-2-date. 4) follow other best practices for securing a system. -- Stephen J Smoogen. -- CSIRT/Linux System Administrator How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" From dlopez at humnet.ucla.edu Thu Nov 29 00:42:44 2007 From: dlopez at humnet.ucla.edu (Lopez, Denise) Date: Wed, 28 Nov 2007 16:42:44 -0800 Subject: [Fedora-xen] Best practices questions In-Reply-To: <80d7e4090711281639u479be25bl10172a3a662b167f@mail.gmail.com> References: <80d7e4090711281639u479be25bl10172a3a662b167f@mail.gmail.com> Message-ID: Are you talking about inside the guests or where the guests are in DomO? I was talking about where the guests are in Dom0. Denise Lopez -----Original Message----- From: Stephen John Smoogen [mailto:smooge at gmail.com] Sent: Wednesday, November 28, 2007 4:39 PM To: Lopez, Denise Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Best practices questions On Nov 28, 2007 5:31 PM, Lopez, Denise wrote: > > > > > Hi all, > > > > I am in the process of building a new Xen server from scratch and wanted to > ask a couple of questions about best practices. > > > > First, should the guest domains be image files or LVM's or just regular ext3 > partitions? What are the pros and/or cons of each? > Are you talking about inside the guests or where the guests are in DomO? For the guests files on Dom0, I am using image files stored on DomO's LVM.. though I may follow some howtos on shared storage so that failover works in the future. Inside the guests, I am using ext3 direct in the image versus using LVM+ext3. I wanted things to be simple to understand for myself. > > > Second, since the Dom0 is supposed to be kept secure, and most of my > servers I don't install any X11 server on, is there any security risk > installing an X11 server on the Dom0 in order to take advantage of the > virt-manager GUI interface? > > I do not know of any major security issues... but you should use security in depth. 1) secure the logins 2) firewall the machine so that only ssh X port forwarding is available 3) keep the system up-2-date. 4) follow other best practices for securing a system. -- Stephen J Smoogen. -- CSIRT/Linux System Administrator How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" From ametzger at silkspeed.com Thu Nov 29 03:54:27 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Wed, 28 Nov 2007 22:54:27 -0500 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <2006289882.246231196287525701.JavaMail.root@zebra.lib.ucdavis.edu> References: <2006289882.246231196287525701.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <474E37F3.80208@silkspeed.com> Dale Bewley wrote: >> Do I need to make a custom boot/initrd script or am I on the wrong >> track? Ideas are welcome. > > Does your initrd contain dm-snapshot.ko? > > # cat initrd-2.6.21-2950.fc8xen.img | gunzip | cpio -vt | grep snapshot > -rw------- 1 root root 34608 Nov 27 08:43 lib/dm-snapshot.ko > Dale: No, it does not. Is the solution as simple as adding it? If so, what is the procedure to correctly create/build a custom initrd? Thanks, Aaron From unixfoo at users.sourceforge.net Thu Nov 29 07:57:06 2007 From: unixfoo at users.sourceforge.net (unixfoo) Date: Thu, 29 Nov 2007 13:27:06 +0530 Subject: [Fedora-xen] Xen : virsh error Message-ID: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> Greetings, When I try to use "virsh", I get the below error. ( xm list returns details though ). I use Fedora 8 and xen. [root at un1xf00 ~]# virsh virsh: error: failed to connect to the hypervisor [root at un1xf00 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 4885 4 r----- 399430.4 webhttp10000 11 2048 2 -b---- 65141.6 webhttp10001 18 2560 2 -b---- 358.0 webhttp10002 14 2048 2 -b---- 81720.5 [root at un1xf00 ~]# Any configuration to be done for virsh. Please help -unixfoo http://unixfoo.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From neohtm at gmail.com Thu Nov 29 08:19:17 2007 From: neohtm at gmail.com (Stephen Neoh) Date: Thu, 29 Nov 2007 16:19:17 +0800 Subject: [Fedora-xen] Fail to install fedora domU Message-ID: I just had installed Fedora 7 with virtualization package using installation DVD. I run the virtual manager and try to install a para-virtualize fedora domU. I had followed all the steps which i found in http://www.howtoforge.com/xen_gui_fedora_7_desktop but still it shows that a message that says failed to locate the disk image. I even had 'yum install vnc' and yet the same error still occurs. Do i need to manually create a disk.img file before setting up a domU? Need help on this... Neohtm -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Thu Nov 29 09:38:14 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 29 Nov 2007 09:38:14 +0000 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> Message-ID: <474E8886.9090700@redhat.com> unixfoo wrote: > Greetings, > > When I try to use "virsh", I get the below error. ( xm list returns details > though ). I use Fedora 8 and xen. > > [root at un1xf00 ~]# virsh > virsh: error: failed to connect to the hypervisor > [root at un1xf00 ~]# xm list [works] What's the output of "virsh list --all"? What version of libvirt & Xen? If "virsh list --all" shows an error or no output consistently, then please file a bug report (http://bugzilla.redhat.com/). It would be helpful if you could attach to this report the output of: strace -o /tmp/log -s 1024 -f virsh list --all (the /tmp/log file) Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Thu Nov 29 09:51:57 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 29 Nov 2007 09:51:57 +0000 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <474E37F3.80208@silkspeed.com> References: <2006289882.246231196287525701.JavaMail.root@zebra.lib.ucdavis.edu> <474E37F3.80208@silkspeed.com> Message-ID: <474E8BBD.3080401@redhat.com> Aaron Metzger wrote: > Dale Bewley wrote: >>> Do I need to make a custom boot/initrd script or am I on the wrong >>> track? Ideas are welcome. >> >> Does your initrd contain dm-snapshot.ko? >> >> # cat initrd-2.6.21-2950.fc8xen.img | gunzip | cpio -vt | grep snapshot >> -rw------- 1 root root 34608 Nov 27 08:43 lib/dm-snapshot.ko >> > > Dale: > > No, it does not. > > Is the solution as simple as adding it? > If so, what is the procedure to correctly create/build a custom initrd? "initrd" is built for you when you install the kernel package. The step by step process goes something like this: (1) When the kernel RPM is installed, an RPM script runs (see 'rpm -q --scripts kernel'): /sbin/new-kernel-pkg --package kernel --mkinitrd --depmod --install $version (2) new-kernel-pkg is a shell script which amongst other things runs mkinitrd: /sbin/mkinitrd --allow-missing -f $initrdfile $version (3) mkinitrd is also a shell script which probes the current machine and decides which drivers the machine needs to boot and mount the root filesystem, and combines those drivers and a big shell script together into an initrd image. (Which is a kind of ramdisk available before the kernel has finished booting). The whole thing is a bit crap to be honest ... Anyway, if you read the mkinitrd script you'll see that if a dm module other than 'linear' is used in some dmtable entry (see 'dmsetup table' command) then mkinitrd will include the snapshot module, in case it's being used. Actually, on my system mkinitrd appears to be broken so that it never probes for anything in the dmtable at all, so maybe there's a real bug going on here. You can run new-kernel-pkg at any time to rebuild initrd, and the details above should tell you what's going on. Do file a bugzilla if there is a real problem in mkinitrd script. 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 Dustin.Henning at prd-inc.com Thu Nov 29 13:03:20 2007 From: Dustin.Henning at prd-inc.com (Dustin Henning) Date: Thu, 29 Nov 2007 08:03:20 -0500 Subject: [Fedora-xen] Best practices questions In-Reply-To: References: <80d7e4090711281639u479be25bl10172a3a662b167f@mail.gmail.com> Message-ID: <003101c83288$37b0e4e0$a712aea0$@Henning@prd-inc.com> Denise, Personally, I recommend lvm or partitions in Dom0 vs image files for performance reasons. The choice to use LVM or partitions can really safely be left to whichever you are more comfortable with. If you want to be able to resize DomUs, then lvm might be useful, but if that can be done, it is probably quite complicated. Dustin -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Lopez, Denise Sent: Wednesday, November 28, 2007 19:43 To: fedora-xen at redhat.com Subject: RE: [Fedora-xen] Best practices questions Are you talking about inside the guests or where the guests are in DomO? I was talking about where the guests are in Dom0. Denise Lopez -----Original Message----- From: Stephen John Smoogen [mailto:smooge at gmail.com] Sent: Wednesday, November 28, 2007 4:39 PM To: Lopez, Denise Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Best practices questions On Nov 28, 2007 5:31 PM, Lopez, Denise wrote: > > > > > Hi all, > > > > I am in the process of building a new Xen server from scratch and wanted to > ask a couple of questions about best practices. > > > > First, should the guest domains be image files or LVM's or just regular ext3 > partitions? What are the pros and/or cons of each? > Are you talking about inside the guests or where the guests are in DomO? For the guests files on Dom0, I am using image files stored on DomO's LVM.. though I may follow some howtos on shared storage so that failover works in the future. Inside the guests, I am using ext3 direct in the image versus using LVM+ext3. I wanted things to be simple to understand for myself. > > > Second, since the Dom0 is supposed to be kept secure, and most of my > servers I don't install any X11 server on, is there any security risk > installing an X11 server on the Dom0 in order to take advantage of the > virt-manager GUI interface? > > I do not know of any major security issues... but you should use security in depth. 1) secure the logins 2) firewall the machine so that only ssh X port forwarding is available 3) keep the system up-2-date. 4) follow other best practices for securing a system. -- Stephen J Smoogen. -- CSIRT/Linux System Administrator How far that little candle throws his beams! So shines a good deed in a naughty world. = Shakespeare. "The Merchant of Venice" -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From dlbewley at lib.ucdavis.edu Thu Nov 29 16:04:23 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Thu, 29 Nov 2007 08:04:23 -0800 (PST) Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <474E37F3.80208@silkspeed.com> Message-ID: <445831587.257611196352263949.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Aaron Metzger" wrote: > Dale Bewley wrote: > >> Do I need to make a custom boot/initrd script or am I on the wrong > > >> track? Ideas are welcome. > > > > Does your initrd contain dm-snapshot.ko? > > > > # cat initrd-2.6.21-2950.fc8xen.img | gunzip | cpio -vt | grep > snapshot > > -rw------- 1 root root 34608 Nov 27 08:43 > lib/dm-snapshot.ko > > > Dale: > > No, it does not. > > Is the solution as simple as adding it? > If so, what is the procedure to correctly create/build a custom > initrd? If mkinitrd doesn't include what you want (in my case it doesn't know to include raid1 and raid456 modules) you can include it by hand. Example: VER=`uname -r` INITRD=/boot/initrd-${VER}.img if [ -f $INITRD ]; then mv $INITRD $INITRD.bak mkinitrd --with=raid1 --with=raid456 $INITRD $VER else echo "Can not find $INITRD" echo "Are you really fixing kernel ${VER}?" fi -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From ametzger at silkspeed.com Fri Nov 30 03:13:30 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Thu, 29 Nov 2007 22:13:30 -0500 Subject: [Fedora-xen] Slightly off-topic question about Xen+LVM In-Reply-To: <445831587.257611196352263949.JavaMail.root@zebra.lib.ucdavis.edu> References: <445831587.257611196352263949.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <474F7FDA.9050804@silkspeed.com> Dale Bewley wrote: > > If mkinitrd doesn't include what you want (in my case it doesn't know to include raid1 and raid456 modules) you can include it by hand. Example: > > VER=`uname -r` > INITRD=/boot/initrd-${VER}.img > if [ -f $INITRD ]; then > mv $INITRD $INITRD.bak > mkinitrd --with=raid1 --with=raid456 $INITRD $VER > else > echo "Can not find $INITRD" > echo "Are you really fixing kernel ${VER}?" > fi > Dale: Your instructions worked perfectly to allow me to add "dm-snapshot" to my initrd. Thank you very much for your insight. You made my day. -- Aaron From neohtm at gmail.com Fri Nov 30 03:23:07 2007 From: neohtm at gmail.com (neohtm) Date: Fri, 30 Nov 2007 11:23:07 +0800 Subject: [Fedora-xen] Problems with fedora 7 paravirtualize Message-ID: <007301c83300$5b992980$12cb7c80$@com> I'm using Fedora 7 with xen's virt-manager. I'd manage to install a full virtualized WinXp domU after changing the settings in .xml files. Now I would like to try to install the paravirtualize fedora 7 using virt-manager I'm using this install media address > http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ And the virt-manager console was managed to show up the installation screen. After the normal steps of the installation, the console was hanged when it shows the 'Retrieving image2' I even had tried to used the Fedora 7 installation DVD as the installation media but it's cant detect the cdrom when the installation begins. I'd googled and find out that I can export the DVD using a FTP/NFS/HTTP from dom0 host, but how to do this? According to Sadique, the Fedora 8 seems to have a better and easy virt-manager to manipulate the Xen virtualization. How to upgrade the fedora 7's virt-manager to fedora 8's? --Stephen Neohtm,Malaysia -------------- next part -------------- An HTML attachment was scrubbed... URL: From unixfoo at users.sourceforge.net Fri Nov 30 04:09:57 2007 From: unixfoo at users.sourceforge.net (unixfoo) Date: Fri, 30 Nov 2007 09:39:57 +0530 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <474E8886.9090700@redhat.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <474E8886.9090700@redhat.com> Message-ID: <97c69f7d0711292009s6e8812a2o84c3f00634b6d6c2@mail.gmail.com> Hi, virsh list --all also gives me the same error. Attached the strace log. Let me know if you find any issues. Will log an issue with bugzilla. thx http://unixfoo.blogspot.com On Nov 29, 2007 3:08 PM, Richard W.M. Jones wrote: > unixfoo wrote: > > Greetings, > > > > When I try to use "virsh", I get the below error. ( xm list returns details > > though ). I use Fedora 8 and xen. > > > > [root at un1xf00 ~]# virsh > > virsh: error: failed to connect to the hypervisor > > [root at un1xf00 ~]# xm list > [works] > > What's the output of "virsh list --all"? What version of libvirt & Xen? > > If "virsh list --all" shows an error or no output consistently, then > please file a bug report (http://bugzilla.redhat.com/). It would be > helpful if you could attach to this report the output of: > > strace -o /tmp/log -s 1024 -f virsh list --all > > (the /tmp/log file) > > 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: virshlog.txt.gz Type: application/x-gzip Size: 8005 bytes Desc: not available URL: From ametzger at silkspeed.com Fri Nov 30 04:23:51 2007 From: ametzger at silkspeed.com (Aaron Metzger) Date: Thu, 29 Nov 2007 23:23:51 -0500 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <97c69f7d0711292009s6e8812a2o84c3f00634b6d6c2@mail.gmail.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <474E8886.9090700@redhat.com> <97c69f7d0711292009s6e8812a2o84c3f00634b6d6c2@mail.gmail.com> Message-ID: <474F9057.70004@silkspeed.com> unixfoo wrote: > Hi, > > virsh list --all also gives me the same error. > Is your libvirtd daemon running? /etc/init.d/libvirtd start > Attached the strace log. Let me know if you find any issues. Will log > an issue with bugzilla. > > thx > > http://unixfoo.blogspot.com > > On Nov 29, 2007 3:08 PM, Richard W.M. Jones wrote: >> unixfoo wrote: >>> Greetings, >>> >>> When I try to use "virsh", I get the below error. ( xm list returns details >>> though ). I use Fedora 8 and xen. >>> >>> [root at un1xf00 ~]# virsh >>> virsh: error: failed to connect to the hypervisor >>> [root at un1xf00 ~]# xm list >> [works] >> >> What's the output of "virsh list --all"? What version of libvirt & Xen? >> >> If "virsh list --all" shows an error or no output consistently, then >> please file a bug report (http://bugzilla.redhat.com/). It would be >> helpful if you could attach to this report the output of: >> >> strace -o /tmp/log -s 1024 -f virsh list --all >> >> (the /tmp/log file) >> >> 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 >> >> >> ------------------------------------------------------------------------ >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen From rjones at redhat.com Fri Nov 30 10:18:11 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 30 Nov 2007 10:18:11 +0000 Subject: [Fedora-xen] Problems with fedora 7 paravirtualize In-Reply-To: <007301c83300$5b992980$12cb7c80$@com> References: <007301c83300$5b992980$12cb7c80$@com> Message-ID: <474FE363.4040404@redhat.com> neohtm wrote: > I'm using Fedora 7 with xen's virt-manager. I'd manage to install a full > virtualized WinXp domU after changing the settings in .xml files. Now I > would like to try to install the paravirtualize fedora 7 using virt-manager > > > > I'm using this install media address > > http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ That's actually FC6. > And the virt-manager console was managed to show up the installation screen. > After the normal steps of the installation, the console was hanged when it > shows the 'Retrieving image2' Yes, I've heard of bugs like this too ... > I even had tried to used the Fedora 7 installation DVD as the installation > media but it's cant detect the cdrom when the installation begins. I'd > googled and find out that I can export the DVD using a FTP/NFS/HTTP from > dom0 host, but how to do this? > > > > According to Sadique, the Fedora 8 seems to have a better and easy > virt-manager to manipulate the Xen virtualization. How to upgrade the fedora > 7's virt-manager to fedora 8's? You'll probably want to upgrade more than just virt-manager. At least libvirt, python-virtinst, xen and kernel-xen. Enable the Fedora development repository while installing these by doing: yum --enablerepo=development install xen [etc...] 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 unixfoo at users.sourceforge.net Fri Nov 30 16:04:46 2007 From: unixfoo at users.sourceforge.net (unixfoo) Date: Fri, 30 Nov 2007 21:34:46 +0530 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <474F9057.70004@silkspeed.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <474E8886.9090700@redhat.com> <97c69f7d0711292009s6e8812a2o84c3f00634b6d6c2@mail.gmail.com> <474F9057.70004@silkspeed.com> Message-ID: <97c69f7d0711300804s27a1894dt3a8811708d00160d@mail.gmail.com> My machine doesnt even have the /etc/init.d/libvirtd . May be im missing something. Let me chk the rpm and get back. Thanks for the help. http://unixfoo.blogspot.com On Nov 30, 2007 9:53 AM, Aaron Metzger wrote: > unixfoo wrote: > > Hi, > > > > virsh list --all also gives me the same error. > > > > Is your libvirtd daemon running? > > > /etc/init.d/libvirtd start > > > > > Attached the strace log. Let me know if you find any issues. Will log > > an issue with bugzilla. > > > > thx > > > > http://unixfoo.blogspot.com > > > > On Nov 29, 2007 3:08 PM, Richard W.M. Jones wrote: > >> unixfoo wrote: > >>> Greetings, > >>> > >>> When I try to use "virsh", I get the below error. ( xm list returns > details > >>> though ). I use Fedora 8 and xen. > >>> > >>> [root at un1xf00 ~]# virsh > >>> virsh: error: failed to connect to the hypervisor > >>> [root at un1xf00 ~]# xm list > >> [works] > >> > >> What's the output of "virsh list --all"? What version of libvirt & > Xen? > >> > >> If "virsh list --all" shows an error or no output consistently, then > >> please file a bug report (http://bugzilla.redhat.com/). It would be > >> helpful if you could attach to this report the output of: > >> > >> strace -o /tmp/log -s 1024 -f virsh list --all > >> > >> (the /tmp/log file) > >> > >> 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 > >> > >> > >> > ------------------------------------------------------------------------ > >> > >> -- > >> Fedora-xen mailing list > >> Fedora-xen at redhat.com > >> https://www.redhat.com/mailman/listinfo/fedora-xen > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidl at matissenetworks.com Fri Nov 30 18:36:52 2007 From: davidl at matissenetworks.com (David Levinger) Date: Fri, 30 Nov 2007 10:36:52 -0800 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? Message-ID: Hello all, I was working with Xen and Cent OS and by default a virtual networking driver called Xenbr0 was created that acted as a "pass through" for the virtual machine. IE that machine contacted our real DHCP server and requested an IP address and all was well. However, on Fedora Core 8 it seems that the default networking setup is to use virbr0 and to have a totally different subnet and the host machine assigning IP addresses to the guests... How can I get back to just a pure network bridge that had the guests contact our DHCP server for leases? Thanks! David **************************************************************************** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. **************************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Fri Nov 30 18:59:09 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 30 Nov 2007 18:59:09 +0000 Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 Message-ID: <20071130185909.GA32711@redhat.com> This is a friendly alert of the major plans we have for Xen kernels in Fedora 9 timeframe... Since we first added Xen in Fedora Core 5, our kernels have been based on a forward-port of XenSource's upstream Xen kernels, to new LKML. For a long time we ported their 2.6.16 tree to 2.6.18. Now we do ports of their 2.6.18 tree to 2.6.21/22/23, etc. At the same time, upstream Linux gained Xen support for i386 DomU, and shortly x86_64 DomU, and is generally getting ever more virtualization capabilities. As everyone knows, we have tended to lag behind Fedora's state-of-the-art bare metal kernels by several releases due to the effort required to port Xen to newer LKML releases. Despite our best efforts, this lag has been getting worse, not better. We have taken the decision, that this situation is unacceptable for Fedora 9. We simply cannot spend more time forward porting Xen kernels. Either Xen has to be dropped entirely, or we need a different strategy for dealing with the kernels. Since people seeem to use Xen, we have decided not to drop it :-) So the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops. LKML already has i386 pv_ops + Xen DomU. We intend to build on this to add: - x64_64 pv_ops - x86_64 Xen DomU on pv_ops - i386 & x86_64 Xen Dom0 on pv_ops - memory balloon - paravirt framebuffer - save/restore All of this based on same LKML release as Fedora bare metal. If all goes to plan it may even be in the base kernel RPM, instead of kernel-xen, but thats a minor concern compared to the actual coding. Getting all this done for Fedora 9 is seriously ambitious, but it is the only long term sustainable option, other than dropping Xen entirely. What this means though, is that Fedora 9 Xen will certainly be going through periods of instability and will certainly be even buggier than normal. F9 may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no PCI device passthrough, or CPU hotplug). On the plus side though we will be 100% back in sync with bare metal kernel versions & hopefully even have a lot of this stuff merged in LKML to make ongoing maintainence sustainable. Short term pain; Long term gain! I have not got any ETA on when any of these kernel changes will appear in rawhide - some time before the F9 feature freeze date is best guesstimate. We will alert people when the time comes. There is a F9 feature page with some amount of info about the plan... http://fedoraproject.org/wiki/Features/XenPvops In terms of Fedora 6/7/8 maintainence... The kernel-xen in these existing releases already lags behind the bare metal kernel version by 2-3 releases. We do not intend to continue trying to rebase the kernel-xen in existing Fedora releases. It will be essentially important bug-fix mode only. This is neccessary to enable maximum resources to be focused on the critical Fedora 9 Xen work. Regards, Dan ...on behalf of some very busy Fedora Xen kernel developers :-) -- |=- 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 tony at emitony.com Fri Nov 30 19:17:43 2007 From: tony at emitony.com (Tony Coffman) Date: Fri, 30 Nov 2007 14:17:43 -0500 Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 In-Reply-To: <20071130185909.GA32711@redhat.com> References: <20071130185909.GA32711@redhat.com> Message-ID: <475061D7.6080207@emitony.com> All I can say is Bravo! Thank you and the entire Fedora Xen kernel team for undertaking this quite substantial effort. Regards, --Tony Daniel P. Berrange wrote: > So the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops. > LKML already has i386 pv_ops + Xen DomU. We intend to build on this to > add: > > - x64_64 pv_ops > - x86_64 Xen DomU on pv_ops > - i386 & x86_64 Xen Dom0 on pv_ops > - memory balloon > - paravirt framebuffer > - save/restore > > All of this based on same LKML release as Fedora bare metal. If all goes to > plan it may even be in the base kernel RPM, instead of kernel-xen, but thats > a minor concern compared to the actual coding. > > Getting all this done for Fedora 9 is seriously ambitious, but it is the only > long term sustainable option, other than dropping Xen entirely. > From paul at xelerance.com Fri Nov 30 19:44:13 2007 From: paul at xelerance.com (Paul Wouters) Date: Fri, 30 Nov 2007 14:44:13 -0500 (EST) Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 In-Reply-To: <20071130185909.GA32711@redhat.com> References: <20071130185909.GA32711@redhat.com> Message-ID: On Fri, 30 Nov 2007, Daniel P. Berrange wrote: > This is a friendly alert of the major plans we have for Xen kernels in > Fedora 9 timeframe... Thanks for the warning. > Since we first added Xen in Fedora Core 5, our kernels have been based on > a forward-port of XenSource's upstream Xen kernels, to new LKML. For a > long time we ported their 2.6.16 tree to 2.6.18. Now we do ports of their > 2.6.18 tree to 2.6.21/22/23, etc. Welcome to my world of KLIPS and NETKEY/XFRM and trying to merge that into one IPsec stack so that problem goes away. Unfortunately, upstream moves rather independantly. Though having the lwm.net site, which at least semi documents API changes, makes the work a bit easier. > At the same time, upstream Linux gained > Xen support for i386 DomU, and shortly x86_64 DomU, and is generally > getting ever more virtualization capabilities. I am somewhat confused here? Upstream gained xen support but you're forward porting xen support? > As everyone knows, we have tended to lag behind Fedora's state-of-the-art > bare metal kernels by several releases due to the effort required to port > Xen to newer LKML releases. Despite our best efforts, this lag has been > getting worse, not better. Which is mostly due to XenSource going all "windows centric". Which got worse when they were bought by Citrix. XenSource (an awful name for a company relying on closed source code for their enterprise version), has not put in the sources to keep up to date, probably partially also for not getting included upstream. > We have taken the decision, that this situation is unacceptable for Fedora 9. > We simply cannot spend more time forward porting Xen kernels. Either Xen has > to be dropped entirely, or we need a different strategy for dealing with the > kernels. Since people seeem to use Xen, we have decided not to drop it :-) Being onf of those people, thank you very much. And to add to that, xen has been almost exclusively usable for serious deployment within Fedora. It has always been far superiod to other distro's integration or using xensource source code itself. I might have cursed a bit on the initrd sillyness, and the PAE incompatibility, but other then that, all our servers are now fully xenified and run more stable then ever before as real iron machines needing physical reboots too often. > So the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops. > LKML already has i386 pv_ops + Xen DomU. We intend to build on this to > add: I might be mixing up things, but are you saying you are focussing on adding paravirt to lguest? And replace xen? > Getting all this done for Fedora 9 is seriously ambitious, but it is the only > long term sustainable option, other than dropping Xen entirely. I understand that too well. > What this means though, is that Fedora 9 Xen will certainly be going through > periods of instability and will certainly be even buggier than normal. F9 > may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no > PCI device passthrough, or CPU hotplug). On the plus side though we will be > 100% back in sync with bare metal kernel versions & hopefully even have a > lot of this stuff merged in LKML to make ongoing maintainence sustainable. > Short term pain; Long term gain! I think most deployments are simple paravirts with no other hardware then virtual disks and virtual network cards. So that might not be as bad as it sounds. > Dan ...on behalf of some very busy Fedora Xen kernel developers :-) Thanks for all the work on virtualization. Most endusers won't really care what powers it under the hood, as long as they can simply re-use their disk images of older fedora releases on newer fedora releases with perhaps only the addition of the newer kernel modules inside the old disk image. Regards, Paul From berrange at redhat.com Fri Nov 30 19:49:34 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 30 Nov 2007 19:49:34 +0000 Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 In-Reply-To: References: <20071130185909.GA32711@redhat.com> Message-ID: <20071130194934.GD32711@redhat.com> On Fri, Nov 30, 2007 at 02:44:13PM -0500, Paul Wouters wrote: > On Fri, 30 Nov 2007, Daniel P. Berrange wrote: > > At the same time, upstream Linux gained > > Xen support for i386 DomU, and shortly x86_64 DomU, and is generally > > getting ever more virtualization capabilities. > > I am somewhat confused here? Upstream gained xen support but you're forward > porting xen support? Upstream gained support for i386, DomU Xen support only - that's far from a complete solution, hence F8 still uses a forward port. This F9 plan is basically about finishing the upstream Xen to support all the features we need for Fedora & avoid any more forward porting. > > So the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops. > > LKML already has i386 pv_ops + Xen DomU. We intend to build on this to > > add: > > I might be mixing up things, but are you saying you are focussing on adding > paravirt to lguest? And replace xen? No, lguest is just another user of pv_ops. This is explicitly still a Xen paravirt solution - we'll still have a Xen 3.x hypervisor underneath, with same Xen 3.0 hypervisor ABI. So F6/7/8 guests should work on F9 host, and F9 guest should still work on F6/7/8 host. ABI compatability is key because that's what makes Xen, Xen :-) lguest (at this time) is still basically a tool for research & development, not real world production use. > > What this means though, is that Fedora 9 Xen will certainly be going through > > periods of instability and will certainly be even buggier than normal. F9 > > may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no > > PCI device passthrough, or CPU hotplug). On the plus side though we will be > > 100% back in sync with bare metal kernel versions & hopefully even have a > > lot of this stuff merged in LKML to make ongoing maintainence sustainable. > > Short term pain; Long term gain! > > I think most deployments are simple paravirts with no other hardware then virtual > disks and virtual network cards. So that might not be as bad as it sounds. Yep, we're basically prioritizing our work to address most common & important areas first. Eventually we may get to stuff like PCI passthrough & CPU hotplug but its longer term low priority stuff. Regards, -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From dlbewley at lib.ucdavis.edu Fri Nov 30 21:24:37 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 30 Nov 2007 13:24:37 -0800 (PST) Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 In-Reply-To: <20071130185909.GA32711@redhat.com> Message-ID: <426596516.301321196457877130.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Daniel P. Berrange" wrote: > This is a friendly alert of the major plans we have for Xen kernels in > Fedora 9 timeframe... Thanks for the pro-active communication! This sounds like a great idea. Is there a list we can lurk on to monitor progress? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From dlbewley at lib.ucdavis.edu Fri Nov 30 21:40:13 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 30 Nov 2007 13:40:13 -0800 (PST) Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: Message-ID: <848376826.301651196458813872.JavaMail.root@zebra.lib.ucdavis.edu> This changed from FC6 to F7 with the nifty new http://www.libvirt.org/. You want to disable the default network that libvirt sets up and configure your settings in /etc/sysconfig/network-scripts/. Configure /etc/xen/xend-config.sxp by changing "(network-script network-bridge)" to "(network-script /bin/true)". Also see: # virsh net-list # virsh net-destroy This may help you with the bridge configuration: https://www.redhat.com/archives/fedora-xen/2007-August/msg00040.html -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From davidl at matissenetworks.com Fri Nov 30 22:04:30 2007 From: davidl at matissenetworks.com (David Levinger) Date: Fri, 30 Nov 2007 14:04:30 -0800 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <848376826.301651196458813872.JavaMail.root@zebra.lib.ucdavis.edu> References: <848376826.301651196458813872.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: Thank Dale for your quick reply! I've definitely started to realize that libvirt was what was creating the 192.168.122 subnet but I'm still unclear on what I'd need to do to go back to something like xenbr0. What would I end up putting into /etc/sysconfi/network-scripts after changing the line to /bin/true that would allow my xen guests to just get IPs on the same subnet that the host is on. Just passing communication through. Thanks again and my apologies if this sounds like a stupid question :-) David -----Original Message----- From: Dale Bewley [mailto:dlbewley at lib.ucdavis.edu] Sent: Friday, November 30, 2007 1:40 PM To: David Levinger Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? This changed from FC6 to F7 with the nifty new http://www.libvirt.org/. You want to disable the default network that libvirt sets up and configure your settings in /etc/sysconfig/network-scripts/. Configure /etc/xen/xend-config.sxp by changing "(network-script network-bridge)" to "(network-script /bin/true)". Also see: # virsh net-list # virsh net-destroy This may help you with the bridge configuration: https://www.redhat.com/archives/fedora-xen/2007-August/msg00040.html -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 ************************************************************************ **** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. ************************************************************************ **** From hbrock at redhat.com Fri Nov 30 22:11:37 2007 From: hbrock at redhat.com (Hugh O. Brock) Date: Fri, 30 Nov 2007 17:11:37 -0500 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: References: <848376826.301651196458813872.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <20071130221137.GM19942@redhat.com> On Fri, Nov 30, 2007 at 02:04:30PM -0800, David Levinger wrote: > Thank Dale for your quick reply! I've definitely started to realize that > libvirt was what was creating the 192.168.122 subnet but I'm still > unclear on what I'd need to do to go back to something like xenbr0. > > What would I end up putting into /etc/sysconfi/network-scripts after > changing the line to /bin/true that would allow my xen guests to just > get IPs on the same subnet that the host is on. Just passing > communication through. > > Thanks again and my apologies if this sounds like a stupid question :-) > > David Hi David. The instructions you need to set up bridging on a Fedora or RHEL installation are at http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt . Basically what you wind up doing is disabling Xen bridging altogether and using your linux distribution's networking scripts to set the bridge up reliably for your guests. The only reason not to use Xen's native bridging is that it tries to be distro-agnostic and the result is predictably poor. Once you disable that (by the "/bin/true" change above) and set up the bridge as described, you should have no difficulty. Best of luck, --Hugh From berrange at redhat.com Fri Nov 30 22:14:36 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 30 Nov 2007 22:14:36 +0000 Subject: [Fedora-xen] FYI: The plan for Xen kernels in Fedora 9 In-Reply-To: <426596516.301321196457877130.JavaMail.root@zebra.lib.ucdavis.edu> References: <20071130185909.GA32711@redhat.com> <426596516.301321196457877130.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <20071130221436.GF32711@redhat.com> On Fri, Nov 30, 2007 at 01:24:37PM -0800, Dale Bewley wrote: > ----- "Daniel P. Berrange" wrote: > > This is a friendly alert of the major plans we have for Xen kernels in > > Fedora 9 timeframe... > > Thanks for the pro-active communication! This sounds like a great idea. > Is there a list we can lurk on to monitor progress? This list for Fedora significant updates, or xen-devel for specific tech details, of the virtualization list at OSDL Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From dlbewley at lib.ucdavis.edu Fri Nov 30 22:27:13 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 30 Nov 2007 14:27:13 -0800 (PST) Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: Message-ID: <41660047.303331196461633705.JavaMail.root@zebra.lib.ucdavis.edu> ----- "David Levinger" wrote: > Thank Dale for your quick reply! I've definitely started to realize > that > libvirt was what was creating the 192.168.122 subnet but I'm still > unclear on what I'd need to do to go back to something like xenbr0. > > What would I end up putting into /etc/sysconfi/network-scripts after > changing the line to /bin/true that would allow my xen guests to just > get IPs on the same subnet that the host is on. Just passing > communication through. > > Thanks again and my apologies if this sounds like a stupid question > :-) > > David I have a bridge on VLAN 6 so I call it br6 you can use xenbr0 is you like. Mine mostly looks something like this after removing the VLAN trunk complication: # cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes BRIDGE=br6 # cat ifcfg-br6 DEVICE=br6 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=10.10.6.1 NETMASK=255.255.255.0 NETWORK=10.10.6.0 BROADCAST=10.10.6.255 Now your primary IP of your dom0 lives on the br6 interface. Your domU's will be on the same VLAN and should see your DHCP server. Don't forget to enable IP forwarding. # grep phys /etc/sysconfig/iptables -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT # grep forward /etc/sysctl.conf # Controls IP packet forwarding net.ipv4.ip_forward = 1 p.s. use 'brctl show' to see your bridges. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From davidl at matissenetworks.com Fri Nov 30 23:12:28 2007 From: davidl at matissenetworks.com (David Levinger) Date: Fri, 30 Nov 2007 15:12:28 -0800 Subject: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? In-Reply-To: <41660047.303331196461633705.JavaMail.root@zebra.lib.ucdavis.edu> References: <41660047.303331196461633705.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: Thanks to both of you guys for helping me out with this! I think I've gotten the idea and now have eth0 up and functional in the way you described! However, I realized that there is one additional thing that I would like to do and that is have eth0 and eth1 bonded together and have the Xen machines use that bond just like they are currently using the eth0 device. I tried doing this in the way that I normally would, bonding them together, however, it didn't seem happy afterward. Have either of you guys done that and if so are there some gotchas I might have missed? Either way, thank you so much for helping me out with this and explaining it! It is very much appreciated! David -----Original Message----- From: Dale Bewley [mailto:dlbewley at lib.ucdavis.edu] Sent: Friday, November 30, 2007 2:27 PM To: David Levinger Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Fedora Core 8 + Xenbr0 + network bridging? ----- "David Levinger" wrote: > Thank Dale for your quick reply! I've definitely started to realize > that > libvirt was what was creating the 192.168.122 subnet but I'm still > unclear on what I'd need to do to go back to something like xenbr0. > > What would I end up putting into /etc/sysconfi/network-scripts after > changing the line to /bin/true that would allow my xen guests to just > get IPs on the same subnet that the host is on. Just passing > communication through. > > Thanks again and my apologies if this sounds like a stupid question > :-) > > David I have a bridge on VLAN 6 so I call it br6 you can use xenbr0 is you like. Mine mostly looks something like this after removing the VLAN trunk complication: # cat ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes BRIDGE=br6 # cat ifcfg-br6 DEVICE=br6 TYPE=Bridge BOOTPROTO=static ONBOOT=yes IPADDR=10.10.6.1 NETMASK=255.255.255.0 NETWORK=10.10.6.0 BROADCAST=10.10.6.255 Now your primary IP of your dom0 lives on the br6 interface. Your domU's will be on the same VLAN and should see your DHCP server. Don't forget to enable IP forwarding. # grep phys /etc/sysconfig/iptables -A FORWARD -m physdev --physdev-is-bridged -j ACCEPT # grep forward /etc/sysctl.conf # Controls IP packet forwarding net.ipv4.ip_forward = 1 p.s. use 'brctl show' to see your bridges. -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 ************************************************************************ **** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. ************************************************************************ **** From annefacq at crpp-bordeaux.cnrs.fr Fri Nov 30 23:15:50 2007 From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq) Date: Sat, 01 Dec 2007 00:15:50 +0100 Subject: [Fedora-xen] Cannot create domU with virt-install when VT is enabled on DELL PowerEdge 1950 Message-ID: <475099A6.1030403@crpp-bordeaux.cnrs.fr> Hello I've got a dom0 on Fedora 8 running on a DELL PowerEdge 1950 ** With "Virtulization Technology" enabled in the BIOS of the DELL PowerEdge 1950, I've got problems using virt-install These problems are on Fedora 8 32 bits and on Fedora 8 64 bits : - with 'virt-install --parav ...' installation freezes randomly - with 'virt-install --hvm ...' the domU freezes after "Creating domain..." : ------------------------ Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file fedora.cs 100% |=========================| 2.8 kB 00:00 Retrieving file boot.iso. 100% |=========================| 9.2 MB 00:01 libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:01 ------------------------ - NB : with virt-manager the installation the domU freezes after clicking the "Finish" button ** With "VT" disabled in the BIOS, I've successfully created a Fedora 8 domU (with virt-install). And if I reboot the PowerEdge with VT enabled, I can start a domU (created with VT disabled). So the problem with VT is only during the installation phase. Any ideas ? Did anybody succeed in installing domU whith "Virtualization Technology" enabled on a PowerEdge 1950 Thanks in advance Anne Facq -- Anne Facq System Engineer CRPP - Centre de Recherche Paul Pascal Mel : annefacq at crpp-bordeaux.cnrs.fr Tel : 05 56 84 56 62 Fax : 05 56 84 56 00 http://www.crpp-bordeaux.cnrs.fr/~annefacq From dbradley at soundscribe.com Wed Nov 28 22:35:00 2007 From: dbradley at soundscribe.com (dbradley) Date: Wed, 28 Nov 2007 14:35:00 -0800 Subject: [Fedora-xen] kernel-xen crash dump analysis In-Reply-To: <1520014867.240791196284927831.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <00b501c8320e$e9e79b60$0c02a8c0@bradleyland.local> I monitor my main dom0 machine with ttywatch and capture the output from any crashes on the "other" machine. I had a lot of crash problems with FC5. Now running FC6, no crashes. I'm assuming you're getting a crash dump on the console and would like to capture that dump as text. If so, ttywatch is the ticket. -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Dale Bewley Sent: Wednesday, November 28, 2007 1:22 PM To: fedora-xen Subject: [Fedora-xen] kernel-xen crash dump analysis After upgrading to F8 I still had a dom0 crash last night, but didn't catch any output. I think it's still the null pointer dereference in tcp_tso_segment, possibly brought to prominence by traffic shaping in a busy domU. I'd like to catch a crash dump the next time it happens so I can (hopefully) intelligently report this bug somewhere. I'm looking at http://fedoraproject.org/wiki/FC6KdumpKexecHowTo http://www.redhatmagazine.com/2007/08/15/a-quick-overview-of-linux-kerne l-crash-dump-analysis/ There is no mention of Xen. I don't see a kernel-xen-debuginfo rpm for f8 or even f7, but there is one for f9 in rawhide it appears. Is kernel-debuginfo sufficient even if running xen? The versions differ, so I would imagine not. # yum --enablerepo=fedora-debuginfo list kernel-xen-debuginfo kernel-debuginfo Available Packages kernel-debuginfo.x86_64 2.6.23.1-49.fc8 updates-debuginf # rpm -q kernel kernel-xen kernel-2.6.23.1-49.fc8 kernel-xen-2.6.21-2950.fc8 Any advice on how capture some useful info from a crashing dom0 kernel? -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.9/1157 - Release Date: 11/28/2007 12:29 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.9/1157 - Release Date: 11/28/2007 12:29 PM From unixfoo at users.sourceforge.net Fri Nov 30 04:02:16 2007 From: unixfoo at users.sourceforge.net (unixfoo) Date: Fri, 30 Nov 2007 09:32:16 +0530 Subject: [Fedora-xen] Xen : virsh error In-Reply-To: <474E8886.9090700@redhat.com> References: <97c69f7d0711282357n62a6b7d8p7dfabd1c1d3258d0@mail.gmail.com> <474E8886.9090700@redhat.com> Message-ID: <97c69f7d0711292002n327e8771ka442f8e529000e78@mail.gmail.com> Hi, virsh list --all also gives me the same error. Attached the strace log. Let me know if you find any issues. Will log an issue with bugzilla. thx http://unixfoo.blogspot.com On Nov 29, 2007 3:08 PM, Richard W.M. Jones wrote: > > unixfoo wrote: > > Greetings, > > > > When I try to use "virsh", I get the below error. ( xm list returns details > > though ). I use Fedora 8 and xen. > > > > [root at un1xf00 ~]# virsh > > virsh: error: failed to connect to the hypervisor > > [root at un1xf00 ~]# xm list > [works] > > What's the output of "virsh list --all"? What version of libvirt & Xen? > > If "virsh list --all" shows an error or no output consistently, then > please file a bug report (http://bugzilla.redhat.com/). It would be > helpful if you could attach to this report the output of: > > strace -o /tmp/log -s 1024 -f virsh list --all > > (the /tmp/log file) > > Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 > -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: virshlog.txt URL: