From henokmikre at gmail.com Mon Jun 2 17:15:10 2008 From: henokmikre at gmail.com (Henok Mikre) Date: Mon, 2 Jun 2008 13:15:10 -0400 Subject: Subject: Re: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0 on Fedora 8 ? Message-ID: <71fa4fe60806021015i1fd4936dv2df2d93dd3e66cae@mail.gmail.com> This helped me a great deal. Thanks. I just have a few questions... 1) is it best to unmount the /mnt/lvfoo/ before or after kpartx -d? because you have it in your procedure list both before and after kpartx -d. 2) is it possible to explore this dump file by either mounting it or some other method? 3) what is the best procedure to replace this dump file in case of a disk failure? i.e. just install xen and use virt-install? 4) is this the best possible method of backing up a domU? Thanks. Gerd Hoffmann wrote: Anne Facq wrote: Because in Dom0 the device for a paravirt Domu (/dev/vg00/lvfoo in my case) is mapped to a virtual disk /dev/xvda (I created the Domu with virt-install), and the only way I found to mount this Domu filesystem, is to : - get the size of the boot sector of /dev/vg00/lvfoo (with fdisk -ul /dev/vg00/lvfoo) = 63 - compute the offset (multiply by block size) - specify this offset to the mount command : mount -o offset=32256 /dev/vg00/lvfoo /mnt/ Uh, oh, quite complicated and error prone. Can be done much easier. Option (1): Use kpartx, it will create device mapper mappings for your partitions. Try "kpartx -v -a /dev/vg00/lvfoo", should give you /dev/vg00/lvfoop[1234]. "kpartx -d ... " removes the mappings. Option (2): (works only with xen kernel): Configure the device as virtual disk *in Domain-0*: "xm block-attach 0 phy:/dev/vg00/lvfoo xvda w". Gives you /dev/xvda[1234]. "xm block-detach ..." removes it. Many thanks for this solution, it helps me a lot. If this can help someone, here are the steps to backup a Domu (filesystem on LVM in backend and on xvda in frontend) with the dump command from Dom0 (Fedora 8), using one of the 2 solutions you advised, kpartx : ---------------------------------------------------------------- # The DomU named "foo" must be stopped before dump xm shutdown -w foo # Creates device mapper mappings /dev/mapper/lvfoop[1234] for /dev/vg00/lvfoo kpartx -v -a /dev/vg00/lvfoo # Mounts temporarly the filesystem to backup mount /dev/mapper/lvfoop1 /mnt/lvfoo/ # Launches the dump /sbin/dump 0 -L FULL_foo -f /BACKUP-XEN/foo.colddump /mnt/lvfoo/ # Umount the filesystem umount /mnt/lvfoo/ # Removes the mappings kpartx -d /dev/vg00/lvfoo # Unmount the filesystem umount /mnt/lvfoo # The DomU can now be restarted xm create --config /var/lib/xend/.... ---------------------------------------------------------------- Regards, Anne Facq -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Tue Jun 3 23:11:03 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 4 Jun 2008 00:11:03 +0100 Subject: [Fedora-xen] ANNOUNCE: virt-mem: tools for monitoring virtual machines Message-ID: <20080603231103.GA30478@amd.home.annexia.org> I'm pleased to announce this very early pre-alpha release of a further set of tools for monitoring virtual machines. The idea is to provide simple commands which can be run outside the virtual machine to monitor its status. These commands don't require you to log in to the virtual machine, or to install any software, since they work entirely by snooping. So they could be very useful for analyzing guests which are stuck / unresponsive / heavily loaded. Done so far: virt-uname like uname(1), print guest's system information virt-dmesg like dmesg(1), print guest's kernel messages Coming soon: virt-ps like ps(1), lists processes virt-free like free(1), lists free memory and swap If virt-ps works out, I might do a 'top'-like command, although of course I can't call it virt-top. I'm open to other suggestions too. Home page: http://et.redhat.com/~rjones/virt-mem/ Source: http://hg.et.redhat.com/virt/applications/virt-mem--devel ****NOTE**** These require a (forthcoming) patch to libvirt to snoop on virtual machines' memory. At the moment you can run them by using the QEMU memsave command to snapshot kernel memory to a file, and then run the program on the file. The snapshot process is described here: http://felinemenace.org/~andrewg/MikroTik_Router_Security_Analysis_Part2/ Support for Xen is still under investigation, but we believe it should be possible. Example: (qemu) memsave 3222274048 15728640 snap.mem $ virt-uname -A i386 -T i386 -t ~/snap.mem /home/rjones/snap.mem: Linux localhost.localdomain 2.6.24-0.155.rc7.git6.fc9 #1 SMP Tue Jan 15 17:52:31 EST 2008 i686 (none) Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into Xen guests. http://et.redhat.com/~rjones/virt-p2v From petedao at gmail.com Wed Jun 4 19:12:29 2008 From: petedao at gmail.com (Pete Kay) Date: Thu, 5 Jun 2008 03:12:29 +0800 Subject: [Fedora-xen] Unable to install domU on Fedora 8 Message-ID: <7aa8bd9d0806041212h6b0881e0yd4eb516ff1031b0e@mail.gmail.com> Hi, When trying to install Cent domU on fedora 8 dom0, I am getting the following error. I have tried both graphics support Yes and No [root at bogon pete]# virt-install What is the name of your virtual machine? serverA How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (file path)? /dev/serverA Would you like to enable graphics support? (yes or no) no What is the install location? http://mirror.centos.org/centos-5/5/os/x86_64/ Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file CentOS... 590 kB 00:26 Retrieving file vmlinuz.. 100% |=========================| 1.8 MB 01:10 Retrieving file initrd.im 100% |=========================| 5.2 MB 03:17 libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') Domain installation may not have been successful. If it was, you can restart your domain by running 'virsh start serverA'; otherwise, please restart your installation. Thu, 05 Jun 2008 03:09:50 ERROR virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') Traceback (most recent call last): File "/usr/bin/virt-install", line 502, in main() File "/usr/bin/virt-install", line 462, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 813, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 834, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 573, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') [root at bogon pete]# I would appreciate any help on getting xen to work. Thanks, Pete -------------- next part -------------- An HTML attachment was scrubbed... URL: From gastonkeller at gmail.com Wed Jun 4 19:28:42 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Wed, 4 Jun 2008 15:28:42 -0400 Subject: [Fedora-xen] Unable to install domU on Fedora 8 In-Reply-To: <7aa8bd9d0806041212h6b0881e0yd4eb516ff1031b0e@mail.gmail.com> References: <7aa8bd9d0806041212h6b0881e0yd4eb516ff1031b0e@mail.gmail.com> Message-ID: On Wed, Jun 4, 2008 at 3:12 PM, Pete Kay wrote: > Hi, > When trying to install Cent domU on fedora 8 dom0, I am getting the > following error. I have tried both graphics support Yes and No > > [root at bogon pete]# virt-install > What is the name of your virtual machine? serverA > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (file path)? /dev/serverA > Would you like to enable graphics support? (yes or no) no > What is the install location? > http://mirror.centos.org/centos-5/5/os/x86_64/ > > > Starting install... > libvir: Xen Daemon error : GET operation failed: > Retrieving file CentOS... 590 kB 00:26 > Retrieving file vmlinuz.. 100% |=========================| 1.8 MB > 01:10 > Retrieving file initrd.im 100% |=========================| 5.2 MB > 03:17 > libvir: Xen Daemon error : GET operation failed: > libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 51712 > (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') > virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 51712 > (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') > Domain installation may not have been > successful. If it was, you can restart your domain > by running 'virsh start serverA'; otherwise, please > restart your installation. > Thu, 05 Jun 2008 03:09:50 ERROR virDomainCreateLinux() failed POST > operation failed: (xend.err 'Device 51712 (vbd) could not be connected. > losetup /dev/loop0 /dev/serverA failed') > Traceback (most recent call last): > File "/usr/bin/virt-install", line 502, in > main() > File "/usr/bin/virt-install", line 462, in main > dom = guest.start_install(conscb,progresscb) > File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 813, in > start_install > return self._do_install(consolecb, meter) > File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 834, in > _do_install > self.domain = self.conn.createLinux(install_xml, 0) > File "/usr/lib64/python2.5/site-packages/libvirt.py", line 573, in > createLinux > if ret is None:raise libvirtError('virDomainCreateLinux() failed', > conn=self) > libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err > 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA > failed') > [root at bogon pete]# > > > > I would appreciate any help on getting xen to work. Hi, Pete. I have no idea about what it's not working for you, but I would suggest googling for the various posts that talk about similar cases. Use the error message for that: (xend.err 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed'), or parts of it. Gaston > > Thanks, > Pete > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- La ?nica verdad es la realidad. From marceldamasio at gmail.com Wed Jun 4 21:12:47 2008 From: marceldamasio at gmail.com (=?ISO-8859-1?Q?Marcel_Dam=E1sio?=) Date: Wed, 4 Jun 2008 18:12:47 -0300 Subject: [Fedora-xen] Unable to install domU on Fedora 8 In-Reply-To: <7aa8bd9d0806041212h6b0881e0yd4eb516ff1031b0e@mail.gmail.com> References: <7aa8bd9d0806041212h6b0881e0yd4eb516ff1031b0e@mail.gmail.com> Message-ID: <386f83ad0806041412x5ed0c81m76d105855ae06ccb@mail.gmail.com> Hi Pete, I had the same error. Some mirrors couldn't be donwloaded from. I had success with the mirror that is in the virt-install man's page, but it's not good. Then I'd made the download of the whole mirror and done it in localhost, and it worked. If you have success doing this, post here please. I wanna know too. On Wed, Jun 4, 2008 at 4:12 PM, Pete Kay wrote: > Hi, > When trying to install Cent domU on fedora 8 dom0, I am getting the > following error. I have tried both graphics support Yes and No > > [root at bogon pete]# virt-install > What is the name of your virtual machine? serverA > How much RAM should be allocated (in megabytes)? 256 > What would you like to use as the disk (file path)? /dev/serverA > Would you like to enable graphics support? (yes or no) no > What is the install location? > http://mirror.centos.org/centos-5/5/os/x86_64/ > > > Starting install... > libvir: Xen Daemon error : GET operation failed: > Retrieving file CentOS... 590 kB > 00:26 > Retrieving file vmlinuz.. 100% |=========================| 1.8 MB > 01:10 > Retrieving file initrd.im 100% |=========================| 5.2 MB > 03:17 > libvir: Xen Daemon error : GET operation failed: > libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 51712 > (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') > virDomainCreateLinux() failed POST operation failed: (xend.err 'Device > 51712 (vbd) could not be connected. losetup /dev/loop0 /dev/serverA failed') > Domain installation may not have been > successful. If it was, you can restart your domain > by running 'virsh start serverA'; otherwise, please > restart your installation. > Thu, 05 Jun 2008 03:09:50 ERROR virDomainCreateLinux() failed POST > operation failed: (xend.err 'Device 51712 (vbd) could not be connected. > losetup /dev/loop0 /dev/serverA failed') > Traceback (most recent call last): > File "/usr/bin/virt-install", line 502, in > main() > File "/usr/bin/virt-install", line 462, in main > dom = guest.start_install(conscb,progresscb) > File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 813, in > start_install > return self._do_install(consolecb, meter) > File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 834, in > _do_install > self.domain = self.conn.createLinux(install_xml, 0) > File "/usr/lib64/python2.5/site-packages/libvirt.py", line 573, in > createLinux > if ret is None:raise libvirtError('virDomainCreateLinux() failed', > conn=self) > libvirtError: virDomainCreateLinux() failed POST operation failed: > (xend.err 'Device 51712 (vbd) could not be connected. losetup /dev/loop0 > /dev/serverA failed') > [root at bogon pete]# > > > > I would appreciate any help on getting xen to work. > > Thanks, > Pete > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From gfrankliu at gmail.com Fri Jun 6 16:33:21 2008 From: gfrankliu at gmail.com (Frank Liu) Date: Fri, 6 Jun 2008 09:33:21 -0700 Subject: [Fedora-xen] xen network bridge with eth0:1 aliases, tmpbridge? Message-ID: <6723ade0806060933n31624f49jcf08bbf99ec07fe@mail.gmail.com> HI there, I am having some troubles with xen network bridge on Fedora 8. Searching bugzilla gives me https://bugzilla.redhat.com/show_bug.cgi?id=193322 which seems to be old. This is a default fedora 8 installed with default xen installation. I assume I should see a "xenbr0" interface, but instead, I see "tmpbridge" ifconfig -a eth0 Link encap:Ethernet HWaddr 00:19:D1:23:DD:4E inet addr:x.y.z.194 Bcast:x.y.z.199 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:12372 errors:0 dropped:0 overruns:0 frame:0 TX packets:10127 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8667047 (8.2 MiB) TX bytes:1098173 (1.0 MiB) eth0:1 Link encap:Ethernet HWaddr 00:19:D1:23:DD:4E inet addr:x.y.z.195 Bcast:x.y.z.199 Mask:255.255.255.248 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:175 errors:0 dropped:0 overruns:0 frame:0 TX packets:175 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:27960 (27.3 KiB) TX bytes:27960 (27.3 KiB) tmpbridge Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:207.182.131.194 Bcast:207.182.131.199 Mask:255.255.255.248 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:19 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:3318 (3.2 KiB) xend-debug.log says: Error: either "local" is duplicate, or "secondary" is a garbage. Does that mean xen in Fedora 8 still can't deal with eth0:1 alias? In my case, I only want xen to use eth0 to bridge to the domU, and eth0:1 is for some other apps on the dom0. I tried to put a "netdev=eth0" in the xend-config.sxp and that didn't help. Thanks! Frank From henokmikre at gmail.com Fri Jun 6 17:54:02 2008 From: henokmikre at gmail.com (Henok Mikre) Date: Fri, 6 Jun 2008 13:54:02 -0400 Subject: [Fedora-xen] Compiling xen from source: mkinitrd error: No module ehci-hcd Message-ID: <71fa4fe60806061054k2cfa5327w6fdaccb577b5a9d5@mail.gmail.com> Hi, I was trying to compile a xen kernel from source and I am having the following errors: [root at machine xen-3.0.4-testing.hg]# mkinitrd -v -f --with=sd_mod --with=scsi_mod /boot/initrd-2.6.16.38-xen0.img 2.6.16.38-xen0 Creating initramfs Looking for deps of module ehci-hcd No module ehci-hcd found for kernel 2.6.16.38-xen0, aborting. Any thoughts? -------------- next part -------------- An HTML attachment was scrubbed... URL: From marceldamasio at gmail.com Fri Jun 6 18:50:46 2008 From: marceldamasio at gmail.com (=?ISO-8859-1?Q?Marcel_Dam=E1sio?=) Date: Fri, 6 Jun 2008 15:50:46 -0300 Subject: [Fedora-xen] Autostart VM on boot Message-ID: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> Hi, I'm using Fedora 8 as DOM0. I created my virtual machines using virt-install. Now I want to configure them to autostart on DOM0's boot, but I can't. I tried a lot of solutions, but none worked. Could somebody help me? -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidl at matissenetworks.com Fri Jun 6 19:13:59 2008 From: davidl at matissenetworks.com (David Levinger) Date: Fri, 6 Jun 2008 12:13:59 -0700 (PDT) Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> Message-ID: <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> Creating a symlink in /etc/xen/auto that points to the config file of the machine I want to autostart has worked for me in Fedora 8. IE I store my config files in /etc/xen ln ?s /etc/xen/MachineFile /etc/xen/auto/MachineFile Next time I boot the virtual machine starts right up. d _____ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Marcel Dam?sio Sent: Friday, June 06, 2008 11:51 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] Autostart VM on boot Hi, I'm using Fedora 8 as DOM0. I created my virtual machines using virt-install. Now I want to configure them to autostart on DOM0's boot, but I can't. I tried a lot of solutions, but none worked. Could somebody help me? -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From marceldamasio at gmail.com Fri Jun 6 19:20:53 2008 From: marceldamasio at gmail.com (=?ISO-8859-1?Q?Marcel_Dam=E1sio?=) Date: Fri, 6 Jun 2008 16:20:53 -0300 Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> Message-ID: <386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> Ok, but I used virt-install to create the VMs, so I don't have a config file. Trying this solution I found the config files at /var/lib/xend/domains/, all generated by virt-install automatic. So I created a symlink in /etc/xen/auto, but this didn't work. Any other ideas? Could you send me an example of config file machine that works for testing? I don't know how to create a VM from one. On Fri, Jun 6, 2008 at 4:13 PM, David Levinger wrote: > Creating a symlink in /etc/xen/auto that points to the config file of the > machine I want to autostart has worked for me in Fedora 8. > > > > IE I store my config files in /etc/xen > > ln ?s /etc/xen/MachineFile /etc/xen/auto/MachineFile > > Next time I boot the virtual machine starts right up. > > > > d > > > ------------------------------ > > *From:* fedora-xen-bounces at redhat.com [mailto: > fedora-xen-bounces at redhat.com] *On Behalf Of *Marcel Dam?sio > *Sent:* Friday, June 06, 2008 11:51 AM > *To:* fedora-xen at redhat.com > *Subject:* [Fedora-xen] Autostart VM on boot > > > > Hi, > > I'm using Fedora 8 as DOM0. > I created my virtual machines using virt-install. > Now I want to configure them to autostart on DOM0's boot, but I can't. > > I tried a lot of solutions, but none worked. > > Could somebody help me? > > -- > Marcel Dam?sio Moreira > 9? per?odo de Ci?ncia da Computa??o - UFES > (27) 8128-7105 > Estagi?rio do Suporte - DI/UFES > -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From davidl at matissenetworks.com Fri Jun 6 19:33:34 2008 From: davidl at matissenetworks.com (David Levinger) Date: Fri, 6 Jun 2008 12:33:34 -0700 (PDT) Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: <386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> <386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> Message-ID: I use virt-install to install my vm?s as well, but when I used virt-manager (to install) I ran into that other directory path that you mentioned. To install a para-virt example with virt-install I use something like the following: virt-install --bridge=xenbr0 --name=machinename --ram=1024 --vcpus=1 --file=/dev/vgmachine/lvmachine --paravirt --location=http://1.1.1.1/pathto/ks -x "ks=http://1.1.1.1/config.cfg" --vnc Below is an example of a Windows VM that I have that is stored in /etc/xen and worked just fine with the symlink method. If you?d like a linux example or a para-virt example just let me know. name = "MachineName" uuid = "f771623c-acbe-18df-d3a9-e71246c88f2e" maxmem = 1024 memory = 1024 vcpus = 2 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 1 apic = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "phy:/dev/vgcomp/lvmachine,hda,w", "file:/root/bartpe.iso,hdb:cdrom,r" ] vif = [ "mac=00:00:00:00:00:00,bridge=eth0,type=ioemu" ] serial = "pty" _____ From: Marcel Dam?sio [mailto:marceldamasio at gmail.com] Sent: Friday, June 06, 2008 12:21 PM To: David Levinger Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Autostart VM on boot Ok, but I used virt-install to create the VMs, so I don't have a config file. Trying this solution I found the config files at /var/lib/xend/domains/, all generated by virt-install automatic. So I created a symlink in /etc/xen/auto, but this didn't work. Any other ideas? Could you send me an example of config file machine that works for testing? I don't know how to create a VM from one. On Fri, Jun 6, 2008 at 4:13 PM, David Levinger wrote: Creating a symlink in /etc/xen/auto that points to the config file of the machine I want to autostart has worked for me in Fedora 8. IE I store my config files in /etc/xen ln ?s /etc/xen/MachineFile /etc/xen/auto/MachineFile Next time I boot the virtual machine starts right up. d _____ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Marcel Dam?sio Sent: Friday, June 06, 2008 11:51 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] Autostart VM on boot Hi, I'm using Fedora 8 as DOM0. I created my virtual machines using virt-install. Now I want to configure them to autostart on DOM0's boot, but I can't. I tried a lot of solutions, but none worked. Could somebody help me? -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From annefacq at crpp-bordeaux.cnrs.fr Sun Jun 8 09:56:53 2008 From: annefacq at crpp-bordeaux.cnrs.fr (Anne Facq) Date: Sun, 08 Jun 2008 11:56:53 +0200 Subject: Subject: Re: [Fedora-xen] How to backup a Domu filesystem (on LVM) from Dom0 on Fedora 8 ? In-Reply-To: <71fa4fe60806021015i1fd4936dv2df2d93dd3e66cae@mail.gmail.com> References: <71fa4fe60806021015i1fd4936dv2df2d93dd3e66cae@mail.gmail.com> Message-ID: <484BACE5.1030201@crpp-bordeaux.cnrs.fr> Henok Mikre wrote: > This helped me a great deal. Thanks. I just have a few questions... > > 1) is it best to unmount the /mnt/lvfoo/ before or after kpartx -d? because you have it in your procedure list both before and after kpartx -d. The /mnt/lvfoo must be unmounted before the kpartx -d, otherwise it will generate problems on the filesystem of the DomU (because the kpartx -d deletes partition mappings) But the line "umount /mnt/lvfoo" after "kpartx -d" is an error due to a "copy and paste", sorry. So here are the steps to backup a Domu (filesystem on LVM in backend and on xvda in frontend) with the dump command from Dom0 (Fedora 8) : ------------------------------------------------------------ # The DomU named "foo" must be stopped before dump xm shutdown -w foo # Creates device mapper mappings /dev/mapper/lvfoop[1234] for /dev/vg00/lvfoo kpartx -v -a /dev/vg00/lvfoo # Mounts temporarly the filesystem to backup mount /dev/mapper/lvfoop1 /mnt/lvfoo/ # Launches the dump /sbin/dump 0 -L FULL_foo -f /BACKUP-XEN/foo.colddump /mnt/lvfoo/ # Umount the filesystem umount /mnt/lvfoo/ # Removes the mappings kpartx -d /dev/vg00/lvfoo # The DomU can now be restarted xm create --config /var/lib/xend/.... ------------------------------------------------------------ > 2) is it possible to explore this dump file by either mounting it or some other method? You can explore the dump file, using the "restore" command like this restore -if /var/BACKUP-XEN/foo.colddump You can also restore in another filesystem the filesystem (of the Domu) that you backuped, following these steps : lvcreate -L2048 -n lvfoo2 vg00 mkfs.ext3 /dev/vg00/lvfoo2 mkdir /mnt/lvfoo2 mount /dev/vg00/lvfoo2 /mnt/lvvfoo2 cd /mnt/lvfoo2 restore -rf /BACKUP-XEN/foo.colddump > 4) is this the best possible method of backing up a domU? This method works well, but I would be interested in knowing other methods :-) Regards Anne Facq From Gerrard.Geldenhuis at datacash.com Mon Jun 9 12:36:59 2008 From: Gerrard.Geldenhuis at datacash.com (Gerrard Geldenhuis) Date: Mon, 9 Jun 2008 13:36:59 +0100 Subject: [Fedora-xen] Autostart VM on boot References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com><8CF5153ACCCF4A6D889898E37A437F80@nbdavidl><386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> Message-ID: Hmmm, Does that mean you have to have a config file in two different formats if you are using virsh? I configure/build my xen domains using virsh. Do I then need an xm compatible file too to have a vm startup? I'm sure not... if I recall correctly if you create a domain via the gui it starts automatically after boot and that only have xml config files but not sure how to "simulate" that if you create the domains using custom xml config files. Regards ________________________________ From: fedora-xen-bounces at redhat.com on behalf of David Levinger Sent: Fri 2008/06/06 08:33 PM To: 'Marcel Dam?sio' Cc: fedora-xen at redhat.com Subject: RE: [Fedora-xen] Autostart VM on boot I use virt-install to install my vm's as well, but when I used virt-manager (to install) I ran into that other directory path that you mentioned. To install a para-virt example with virt-install I use something like the following: virt-install --bridge=xenbr0 --name=machinename --ram=1024 --vcpus=1 --file=/dev/vgmachine/lvmachine --paravirt --location=http://1.1.1.1/pathto/ks -x "ks=http://1.1.1.1/config.cfg" --vnc Below is an example of a Windows VM that I have that is stored in /etc/xen and worked just fine with the symlink method. If you'd like a linux example or a para-virt example just let me know. name = "MachineName" uuid = "f771623c-acbe-18df-d3a9-e71246c88f2e" maxmem = 1024 memory = 1024 vcpus = 2 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 1 apic = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" sdl = 0 vnc = 1 vncunused = 1 disk = [ "phy:/dev/vgcomp/lvmachine,hda,w", "file:/root/bartpe.iso,hdb:cdrom,r" ] vif = [ "mac=00:00:00:00:00:00,bridge=eth0,type=ioemu" ] serial = "pty" ________________________________ From: Marcel Dam?sio [mailto:marceldamasio at gmail.com] Sent: Friday, June 06, 2008 12:21 PM To: David Levinger Cc: fedora-xen at redhat.com Subject: Re: [Fedora-xen] Autostart VM on boot Ok, but I used virt-install to create the VMs, so I don't have a config file. Trying this solution I found the config files at /var/lib/xend/domains/, all generated by virt-install automatic. So I created a symlink in /etc/xen/auto, but this didn't work. Any other ideas? Could you send me an example of config file machine that works for testing? I don't know how to create a VM from one. On Fri, Jun 6, 2008 at 4:13 PM, David Levinger wrote: Creating a symlink in /etc/xen/auto that points to the config file of the machine I want to autostart has worked for me in Fedora 8. IE I store my config files in /etc/xen ln -s /etc/xen/MachineFile /etc/xen/auto/MachineFile Next time I boot the virtual machine starts right up. d ________________________________ From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of Marcel Dam?sio Sent: Friday, June 06, 2008 11:51 AM To: fedora-xen at redhat.com Subject: [Fedora-xen] Autostart VM on boot Hi, I'm using Fedora 8 as DOM0. I created my virtual machines using virt-install. Now I want to configure them to autostart on DOM0's boot, but I can't. I tried a lot of solutions, but none worked. Could somebody help me? -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES From erenoglu at gmail.com Mon Jun 9 12:49:45 2008 From: erenoglu at gmail.com (Emre ERENOGLU) Date: Mon, 9 Jun 2008 14:49:45 +0200 Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> <386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> Message-ID: Hi, If the guest is created by libvirt (ie virt-install etc.), then I suggest usign virsh to trigger autostarting. Here's what can be done: emre at xenroot:~$ virsh Connecting to uri: qemu:///system Welcome to virsh, the virtualization interactive terminal. Type: 'help' for help with commands 'quit' to quit virsh # list --all Id Name State ---------------------------------- 1 Pardus-PV running - Pardus-2008 shut off virsh # help autostart NAME autostart - autostart a domain SYNOPSIS autostart [--disable] DESCRIPTION Configure a domain to be automatically started at boot. OPTIONS domain name, id or uuid --disable disable autostarting virsh # This system is running KVM, but it would be the same for XEN. try it out and let us know :) Emre On Mon, Jun 9, 2008 at 2:36 PM, Gerrard Geldenhuis < Gerrard.Geldenhuis at datacash.com> wrote: > Hmmm, > Does that mean you have to have a config file in two different formats if > you are using virsh? > > I configure/build my xen domains using virsh. Do I then need an xm > compatible file too to have a vm startup? I'm sure not... if I recall > correctly if you create a domain via the gui it starts automatically after > boot and that only have xml config files but not sure how to "simulate" that > if you create the domains using custom xml config files. > > Regards > > ________________________________ > > From: fedora-xen-bounces at redhat.com on behalf of David Levinger > Sent: Fri 2008/06/06 08:33 PM > To: 'Marcel Dam?sio' > Cc: fedora-xen at redhat.com > Subject: RE: [Fedora-xen] Autostart VM on boot > > > > I use virt-install to install my vm's as well, but when I used virt-manager > (to install) I ran into that other directory path that you mentioned. > > > > To install a para-virt example with virt-install I use something like the > following: > > virt-install --bridge=xenbr0 --name=machinename --ram=1024 --vcpus=1 > --file=/dev/vgmachine/lvmachine --paravirt --location= > http://1.1.1.1/pathto/ks -x "ks=http://1.1.1.1/config.cfg" --vnc > > > > Below is an example of a Windows VM that I have that is stored in /etc/xen > and worked just fine with the symlink method. If you'd like a linux example > or a para-virt example just let me know. > > > > name = "MachineName" > > uuid = "f771623c-acbe-18df-d3a9-e71246c88f2e" > > maxmem = 1024 > > memory = 1024 > > vcpus = 2 > > builder = "hvm" > > kernel = "/usr/lib/xen/boot/hvmloader" > > boot = "c" > > pae = 1 > > acpi = 1 > > apic = 1 > > on_poweroff = "destroy" > > on_reboot = "restart" > > on_crash = "restart" > > device_model = "/usr/lib64/xen/bin/qemu-dm" > > sdl = 0 > > vnc = 1 > > vncunused = 1 > > disk = [ "phy:/dev/vgcomp/lvmachine,hda,w", > "file:/root/bartpe.iso,hdb:cdrom,r" ] > > vif = [ "mac=00:00:00:00:00:00,bridge=eth0,type=ioemu" ] > > serial = "pty" > > > > ________________________________ > > From: Marcel Dam?sio [mailto:marceldamasio at gmail.com] > Sent: Friday, June 06, 2008 12:21 PM > To: David Levinger > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Autostart VM on boot > > > > Ok, but I used virt-install to create the VMs, so I don't have a config > file. > > Trying this solution I found the config files at /var/lib/xend/domains/, > all generated by virt-install automatic. > > So I created a symlink in /etc/xen/auto, but this didn't work. > > Any other ideas? > > Could you send me an example of config file machine that works for testing? > I don't know how to create a VM from one. > > On Fri, Jun 6, 2008 at 4:13 PM, David Levinger > wrote: > > Creating a symlink in /etc/xen/auto that points to the config file of the > machine I want to autostart has worked for me in Fedora 8. > > > > IE I store my config files in /etc/xen > > ln -s /etc/xen/MachineFile /etc/xen/auto/MachineFile > > Next time I boot the virtual machine starts right up. > > > > d > > > > ________________________________ > > From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] > On Behalf Of Marcel Dam?sio > Sent: Friday, June 06, 2008 11:51 AM > To: fedora-xen at redhat.com > Subject: [Fedora-xen] Autostart VM on boot > > > > Hi, > > I'm using Fedora 8 as DOM0. > I created my virtual machines using virt-install. > Now I want to configure them to autostart on DOM0's boot, but I can't. > > I tried a lot of solutions, but none worked. > > Could somebody help me? > > -- > Marcel Dam?sio Moreira > 9? per?odo de Ci?ncia da Computa??o - UFES > (27) 8128-7105 > Estagi?rio do Suporte - DI/UFES > > > > > -- > Marcel Dam?sio Moreira > 9? per?odo de Ci?ncia da Computa??o - UFES > (27) 8128-7105 > Estagi?rio do Suporte - DI/UFES > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- Emre -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.schwarz at web.de Mon Jun 9 16:59:54 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Mon, 09 Jun 2008 18:59:54 +0200 Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> <386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> Message-ID: <484D618A.7090207@web.de> Emre ERENOGLU wrote: > This system is running KVM, but it would be the same for XEN. try it out > and let us know :) At least for me (Fedora 8) this does not work with Xen: virsh # autostart server3 libvir: error : this function is not supported by the hypervisor: virDomainSetAutostart error: Failed to mark domain server3 as autostarted I guess I should grab some more time and convert my Xen build machines to KVM. ;-) fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From crobinso at redhat.com Mon Jun 9 19:18:19 2008 From: crobinso at redhat.com (Cole Robinson) Date: Mon, 09 Jun 2008 15:18:19 -0400 Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: <484D618A.7090207@web.de> References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> <8CF5153ACCCF4A6D889898E37A437F80@nbdavidl> <386f83ad0806061220n4b9c20f8uf8da84e477ab79cf@mail.gmail.com> <484D618A.7090207@web.de> Message-ID: <484D81FB.7010005@redhat.com> Felix Schwarz wrote: > Emre ERENOGLU wrote: >> This system is running KVM, but it would be the same for XEN. try it out >> and let us know :) > > At least for me (Fedora 8) this does not work with Xen: > > virsh # autostart server3 > libvir: error : this function is not supported by the hypervisor: > virDomainSetAutostart > error: Failed to mark domain server3 as autostarted > > I guess I should grab some more time and convert my Xen build machines to KVM. > ;-) > > fs > Autostarting xen VM's via libvirt isn't supported in the version in F-8, but it is supported upstream as of about a month ago. You can try building from upstream or wait for a new release to be cut, at which point it may be backported to f-8. - Cole From ametzger at silkspeed.com Mon Jun 9 21:51:39 2008 From: ametzger at silkspeed.com (Aaron Metzger) Date: Mon, 09 Jun 2008 17:51:39 -0400 Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> Message-ID: <484DA5EB.5010405@silkspeed.com> Marcel Dam?sio wrote: > Hi, > > I'm using Fedora 8 as DOM0. > I created my virtual machines using virt-install. > Now I want to configure them to autostart on DOM0's boot, but I can't. > > I tried a lot of solutions, but none worked. > > Could somebody help me? > Marcel: Do you have domain definitions in: /var/lib/xend/domains Shutdown the xend. Edit /var/lib/xend/domains//config.sxp Add these two lines to the domain definition: (on_xend_start start) (on_xend_stop shutdown) Make sure that "xend" and "xendomains" start automatically in your "init.d". By the way, I also have these actions in my config.sxp and can't remember if these were the default values after virt-install or not. (actions_after_crash restart) (actions_after_shutdown destroy) (actions_after_reboot restart) Let me know how it goes for you. -- Good luck, Aaron From marceldamasio at gmail.com Tue Jun 10 19:13:56 2008 From: marceldamasio at gmail.com (=?ISO-8859-1?Q?Marcel_Dam=E1sio?=) Date: Tue, 10 Jun 2008 16:13:56 -0300 Subject: [Fedora-xen] Autostart VM on boot In-Reply-To: <484DA5EB.5010405@silkspeed.com> References: <386f83ad0806061150x25427229q1b46c4c226b17dd@mail.gmail.com> <484DA5EB.5010405@silkspeed.com> Message-ID: <386f83ad0806101213u471e59c2s54a42ce8bf1f1f12@mail.gmail.com> Hi Aaron, Thanks a lot for helping me. It worked. I added into *'/var/lib/xend/domains/**/config.sxp' *these lines: * (on_xend_start start) (on_xend_stop shutdown)* Now, the VMs are really auto starting and shutting down! Thanks for helping me. On Mon, Jun 9, 2008 at 6:51 PM, Aaron Metzger wrote: > Marcel Dam?sio wrote: > >> Hi, >> >> I'm using Fedora 8 as DOM0. >> I created my virtual machines using virt-install. >> Now I want to configure them to autostart on DOM0's boot, but I can't. >> >> I tried a lot of solutions, but none worked. >> >> Could somebody help me? >> >> > Marcel: > > Do you have domain definitions in: > > /var/lib/xend/domains > > Shutdown the xend. > > Edit > > /var/lib/xend/domains//config.sxp > > > Add these two lines to the domain definition: > > (on_xend_start start) > (on_xend_stop shutdown) > > Make sure that "xend" and "xendomains" start automatically in your > "init.d". > > > By the way, I also have these actions in my config.sxp and can't remember > if these were the default values after virt-install or not. > > (actions_after_crash restart) > (actions_after_shutdown destroy) > (actions_after_reboot restart) > > > Let me know how it goes for you. > > -- > Good luck, > Aaron > > -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From tournesol33 at gmail.com Wed Jun 11 02:54:24 2008 From: tournesol33 at gmail.com (tournesol) Date: Wed, 11 Jun 2008 11:54:24 +0900 Subject: [Fedora-xen] Installing Para Virtualized guest using ISO file Message-ID: <484F3E60.1050105@gmail.com> Hi. Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to install Para Virtualized guest OS ? Waiting for your help. From takebe_akio at jp.fujitsu.com Wed Jun 11 03:51:27 2008 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Wed, 11 Jun 2008 12:51:27 +0900 Subject: [Fedora-xen] Installing Para Virtualized guest using ISO file In-Reply-To: <484F3E60.1050105@gmail.com> References: <484F3E60.1050105@gmail.com> Message-ID: <39C8CB766CF23Etakebe_akio@jp.fujitsu.com> Hi, >Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to >install Para Virtualized guest OS ? > >Waiting for your help. Do you install vsftpd? If so, you mount ISO to /var/ftp/pub, and vsftpd start, then you can install the local ftp server, I think. Best Regards, Akio Takebe From orenault at redhat.com Wed Jun 11 12:25:17 2008 From: orenault at redhat.com (Olivier Renault) Date: Wed, 11 Jun 2008 14:25:17 +0200 Subject: [Fedora-xen] Installing Para Virtualized guest using ISO file In-Reply-To: <39C8CB766CF23Etakebe_akio@jp.fujitsu.com> References: <484F3E60.1050105@gmail.com> <39C8CB766CF23Etakebe_akio@jp.fujitsu.com> Message-ID: <484FC42D.9000900@redhat.com> Akio Takebe wrote: > Hi, > >> Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to >> install Para Virtualized guest OS ? >> >> Waiting for your help. > Do you install vsftpd? If so, you mount ISO to /var/ftp/pub, > and vsftpd start, then you can install the local ftp server, > I think. > You can not install using the iso as such for a pv system. You will need to install it through HTTP / NFS / FTP / ... ( I am normally using http, & I am unsure if NFS is now supported ). Install httpd server yum -y install httpd create a directory to mount your iso mkdir /var/www/html/pub mount -o loop /path-to-your-iso-image /var/www/html/pub turn off SELinux & Firewall setenforce 0 iptables -F service httpd start You should now be ready to install your Vm from http:///pub Hope this help. Olivier NB ; do not use localhost for the IP of dom0 From gastonkeller at gmail.com Wed Jun 11 13:42:55 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Wed, 11 Jun 2008 09:42:55 -0400 Subject: [Fedora-xen] Installing Para Virtualized guest using ISO file In-Reply-To: <484F3E60.1050105@gmail.com> References: <484F3E60.1050105@gmail.com> Message-ID: On Tue, Jun 10, 2008 at 10:54 PM, tournesol wrote: > Hi. > > Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to > install Para Virtualized guest OS ? Here there is a Fedora 8 Quick Start guide to create Xen guests: http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart#Building_a_Fedora_Guest_System_using_virt-install I have installed guests using NFS and also FTP. If you already have the ISO, you can do what Olivier mentioned to use HTTP or also mount the ISO and share it through NFS. See you, Gaston > > Waiting for your help. > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- La ?nica verdad es la realidad. From sysmandosys at yahoo.co.in Thu Jun 12 03:44:11 2008 From: sysmandosys at yahoo.co.in (aswath Aswath) Date: Thu, 12 Jun 2008 09:14:11 +0530 (IST) Subject: [Fedora-xen] i need fedora 9 digit DVD In-Reply-To: <20080611160014.8834661A0F7@hormel.redhat.com> Message-ID: <755380.94318.qm@web94107.mail.in2.yahoo.com> HI. i need Fedora 9 to free ship it. so send me through post> --- On Wed, 11/6/08, fedora-xen-request at redhat.com <fedora-xen-request at redhat.com> wrote: From: fedora-xen-request at redhat.com <fedora-xen-request at redhat.com> Subject: Fedora-xen Digest, Vol 31, Issue 9 To: fedora-xen at redhat.com Date: Wednesday, 11 June, 2008, 4:00 PM Send Fedora-xen mailing list submissions to fedora-xen at redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/fedora-xen or, via email, send a message with subject or body 'help' to fedora-xen-request at redhat.com You can reach the person managing the list at fedora-xen-owner at redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Fedora-xen digest..." Today's Topics: 1. Re: Autostart VM on boot ( Marcel Dam?sio ) 2. Installing Para Virtualized guest using ISO file (tournesol) 3. Re: Installing Para Virtualized guest using ISO file (Akio Takebe) 4. Re: Installing Para Virtualized guest using ISO file (Olivier Renault) 5. Re: Installing Para Virtualized guest using ISO file ( Gast?n Keller ) ---------------------------------------------------------------------- Message: 1 Date: Tue, 10 Jun 2008 16:13:56 -0300 From: " Marcel Dam?sio " <marceldamasio at gmail.com> Subject: Re: [Fedora-xen] Autostart VM on boot To: "Aaron Metzger" <ametzger at silkspeed.com> Cc: fedora-xen at redhat.com Message-ID: <386f83ad0806101213u471e59c2s54a42ce8bf1f1f12 at mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" Hi Aaron, Thanks a lot for helping me. It worked. I added into *'/var/lib/xend/domains/<UUID>**/config.sxp' *these lines: * (on_xend_start start) (on_xend_stop shutdown)* Now, the VMs are really auto starting and shutting down! Thanks for helping me. On Mon, Jun 9, 2008 at 6:51 PM, Aaron Metzger <ametzger at silkspeed.com> wrote: > Marcel Dam?sio wrote: > >> Hi, >> >> I'm using Fedora 8 as DOM0. >> I created my virtual machines using virt-install. >> Now I want to configure them to autostart on DOM0's boot, but I can't. >> >> I tried a lot of solutions, but none worked. >> >> Could somebody help me? >> >> > Marcel: > > Do you have domain definitions in: > > /var/lib/xend/domains > > Shutdown the xend. > > Edit > > /var/lib/xend/domains/<UUID>/config.sxp > > > Add these two lines to the domain definition: > > (on_xend_start start) > (on_xend_stop shutdown) > > Make sure that "xend" and "xendomains" start automatically in your > "init.d". > > > By the way, I also have these actions in my config.sxp and can't remember > if these were the default values after virt-install or not. > > (actions_after_crash restart) > (actions_after_shutdown destroy) > (actions_after_reboot restart) > > > Let me know how it goes for you. > > -- > Good luck, > Aaron > > -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7105 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/fedora-xen/attachments/20080610/0eb4f83b/attachment.html ------------------------------ Message: 2 Date: Wed, 11 Jun 2008 11:54:24 +0900 From: tournesol <tournesol33 at gmail.com> Subject: [Fedora-xen] Installing Para Virtualized guest using ISO file To: fedora-xen at redhat.com Message-ID: <484F3E60.1050105 at gmail.com> Content-Type: text/plain; charset=ISO-2022-JP Hi. Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to install Para Virtualized guest OS ? Waiting for your help. ------------------------------ Message: 3 Date: Wed, 11 Jun 2008 12:51:27 +0900 From: Akio Takebe <takebe_akio at jp.fujitsu.com> Subject: Re: [Fedora-xen] Installing Para Virtualized guest using ISO file To: tournesol <tournesol33 at gmail.com>, fedora-xen at redhat.com Message-ID: <39C8CB766CF23Etakebe_akio at jp.fujitsu.com> Content-Type: text/plain; charset=us-ascii Hi, >Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to >install Para Virtualized guest OS ? > >Waiting for your help. Do you install vsftpd? If so, you mount ISO to /var/ftp/pub, and vsftpd start, then you can install the local ftp server, I think. Best Regards, Akio Takebe ------------------------------ Message: 4 Date: Wed, 11 Jun 2008 14:25:17 +0200 From: Olivier Renault <orenault at redhat.com> Subject: Re: [Fedora-xen] Installing Para Virtualized guest using ISO file To: Akio Takebe <takebe_akio at jp.fujitsu.com> Cc: fedora-xen at redhat.com Message-ID: <484FC42D.9000900 at redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Akio Takebe wrote: > Hi, > >> Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to >> install Para Virtualized guest OS ? >> >> Waiting for your help. > Do you install vsftpd? If so, you mount ISO to /var/ftp/pub, > and vsftpd start, then you can install the local ftp server, > I think. > You can not install using the iso as such for a pv system. You will need to install it through HTTP / NFS / FTP / ... ( I am normally using http, & I am unsure if NFS is now supported ). Install httpd server yum -y install httpd create a directory to mount your iso mkdir /var/www/html/pub mount -o loop /path-to-your-iso-image /var/www/html/pub turn off SELinux & Firewall setenforce 0 iptables -F service httpd start You should now be ready to install your Vm from http://<ip of dom0>/pub Hope this help. Olivier NB ; do not use localhost for the IP of dom0 ------------------------------ Message: 5 Date: Wed, 11 Jun 2008 09:42:55 -0400 From: " Gast?n Keller " <gastonkeller at gmail.com> Subject: Re: [Fedora-xen] Installing Para Virtualized guest using ISO file To: tournesol <tournesol33 at gmail.com> Cc: fedora-xen at redhat.com Message-ID: <bd6e1f920806110642g67f32ca5p3bb2e702b73e8ba2 at mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 On Tue, Jun 10, 2008 at 10:54 PM, tournesol <tournesol33 at gmail.com> wrote: > Hi. > > Are there any ideas that can use ISO file(ex: Fedora-8-i386-DVD.iso) to > install Para Virtualized guest OS ? Here there is a Fedora 8 Quick Start guide to create Xen guests: http://fedoraproject.org/wiki/Docs/Fedora8VirtQuickStart#Building_a_Fedora_Guest_System_using_virt-install I have installed guests using NFS and also FTP. If you already have the ISO, you can do what Olivier mentioned to use HTTP or also mount the ISO and share it through NFS. See you, Gaston > > Waiting for your help. > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -- La ?nica verdad es la realidad. ------------------------------ -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen End of Fedora-xen Digest, Vol 31, Issue 9 ***************************************** Did you know? You can CHAT without downloading messenger. Go to http://in.messenger.yahoo.com/webmessengerpromo.php/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Thu Jun 12 12:20:44 2008 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Thu, 12 Jun 2008 17:50:44 +0530 Subject: [Fedora-xen] i need fedora 9 digit DVD In-Reply-To: <755380.94318.qm@web94107.mail.in2.yahoo.com> References: <755380.94318.qm@web94107.mail.in2.yahoo.com> Message-ID: <4851149C.7060807@fedoraproject.org> aswath Aswath wrote: > HI. i need Fedora 9 to free ship it. so send me through post> Contact your local linux user group or refer http://fedoraproject.org/wiki/Distribution/FreeMedia Rahul From christian.nitschmann at e-siqia.de Thu Jun 12 08:57:44 2008 From: christian.nitschmann at e-siqia.de (Christian Nitschmann) Date: Thu, 12 Jun 2008 10:57:44 +0200 Subject: [Fedora-xen] vm create test ="losetup /dev/loop0 /data/xen/domains/test/disk.img failed" Message-ID: <4850E508.5060506@e-siqia.de> Dear mailing-list after several attempts to start a xen linux-vm on a Fedora 8 XEN-System (Quadcore Xeon-System with 8GB RAM and VT/PAE enabled), i now really need your help. I sucessfully created and installed a new debian etch-vm with the well known debootstrap-script. I got 10 unused loop-devices which should really be enough for at least one xen-machine. When i try to start the new debian-etch-machine with "*xm create /etc/xen/test -c*" i always get the error message: ------------------------------- Using config file "./test". Error: Device 2049 (vbd) could not be connected. losetup /dev/loop0 /data/xen/domains/test/disk.img failed ------------------------------- *xend.log:* ----------------------------------------------------- [2008-06-11 11:24:09 2528] DEBUG (XendDomainInfo:1555) XendDomainInfo.constructDomain [2008-06-11 11:24:09 2528] DEBUG (balloon:116) Balloon: 131072 KiB free; need 2048; done. [2008-06-11 11:24:09 2528] DEBUG (XendDomain:443) Adding Domain: 1 [2008-06-11 11:24:09 2528] DEBUG (XendDomainInfo:1609) XendDomainInfo.initDomain: 1 256 [2008-06-11 11:24:09 2528] DEBUG (XendDomainInfo:1640) _initDomain:shadow_memory=0x0, memory_static_max=0x8000000, memory_static_min=0x0. [2008-06-11 11:24:09 2528] DEBUG (balloon:116) Balloon: 131072 KiB free; need 131072; done. [2008-06-11 11:24:09 2528] INFO (image:129) buildDomain os=linux dom=1 vcpus=1 [2008-06-11 11:24:09 2528] DEBUG (image:198) domid = 1 [2008-06-11 11:24:09 2528] DEBUG (image:199) memsize = 128 [2008-06-11 11:24:09 2528] DEBUG (image:200) image = /boot/vmlinuz-2.6.21.7-3.fc8xen [2008-06-11 11:24:09 2528] DEBUG (image:201) store_evtchn = 1 [2008-06-11 11:24:09 2528] DEBUG (image:202) console_evtchn = 2 [2008-06-11 11:24:09 2528] DEBUG (image:203) cmdline = root=/dev/sda1 ro ip=:1.2.3.4::::eth0:dhcp [2008-06-11 11:24:09 2528] DEBUG (image:204) ramdisk = /boot/initrd-2.6.21.7-3.fc8xen.img [2008-06-11 11:24:09 2528] DEBUG (image:205) vcpus = 1 [2008-06-11 11:24:09 2528] DEBUG (image:206) features = [2008-06-11 11:24:09 2528] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid': '1681e256-5ca1-49d6-c570-f08bb2f3c0a1', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'sda1', 'uname': 'file:/data/xen/domains/test/disk.img', 'mode': 'w'} [2008-06-11 11:24:09 2528] DEBUG (DevController:117) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/2049'} to /local/domain/1/device/vbd/2049. [2008-06-11 11:24:09 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'frontend': '/local/domain/1/device/vbd/2049', 'uuid': '1681e256-5ca1-49d6-c570-f08bb2f3c0a1', 'dev': 'sda1', 'state': '1', 'params': '/data/xen/domains/test/disk.img', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/2049. [2008-06-11 11:24:09 2528] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid': '114d9b70-e03a-ccfc-53f1-760b433d1247', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'sda2', 'uname': 'file:/data/xen/domains/test/swap.img', 'mode': 'w'} [2008-06-11 11:24:09 2528] DEBUG (DevController:117) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/2050'} to /local/domain/1/device/vbd/2050. [2008-06-11 11:24:09 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'frontend': '/local/domain/1/device/vbd/2050', 'uuid': '114d9b70-e03a-ccfc-53f1-760b433d1247', 'dev': 'sda2', 'state': '1', 'params': '/data/xen/domains/test/swap.img', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/2050. [2008-06-11 11:24:09 2528] INFO (XendDomainInfo:1458) createDevice: vif : {'mac': '00:16:3e:12:88:a1', 'uuid': '74139f26-9d03-53a5-3ac7-0e2a5e7f2f59'} [2008-06-11 11:24:09 2528] DEBUG (DevController:117) DevController: writing {'mac': '00:16:3e:12:88:a1', 'handle': '0', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2008-06-11 11:24:09 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'handle': '0', 'uuid': '74139f26-9d03-53a5-3ac7-0e2a5e7f2f59', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:12:88:a1', 'online': '1', 'frontend-id': '1'} to /local/domain/0/backend/vif/1/0. [2008-06-11 11:24:09 2528] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '95a38774-70eb-1714-fe37-5ab47b436608', 'on_reboot': 'restart', 'start_time': '1213176249.91', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel /boot/vmlinuz-2.6.21.7-3.fc8xen) (ramdisk /boot/initrd-2.6.21.7-3.fc8xen.img) (args 'root=/dev/sda1 ro ip=:1.2.3.4::::eth0:dhcp ') (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': 'test'} [2008-06-11 11:24:09 2528] DEBUG (XendDomainInfo:956) Storing domain details: {'console/ring-ref': '2261948', 'image/entry': '3238002688', 'console/port': '2', 'store/ring-ref': '2261949', 'image/loader': 'generic', 'vm': '/vm/95a38774-70eb-1714-fe37-5ab47b436608', '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': '131072', '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': 'test', 'domid': '1', 'image/xen-version': 'xen-3.0', 'store/port': '1'} [2008-06-11 11:24:09 2528] DEBUG (DevController:117) DevController: writing {'protocol': 'x86_32-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/1/0'} to /local/domain/1/device/console/0. [2008-06-11 11:24:09 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'protocol': 'vt100', 'uuid': '6af035fd-4e60-53d0-db0f-eb5c2a03fa3a', 'frontend': '/local/domain/1/device/console/0', 'state': '1', 'location': '2', 'online': '1', 'frontend-id': '1'} to /local/domain/0/backend/console/1/0. [2008-06-11 11:24:09 2528] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2008-06-11 11:24:10 2528] DEBUG (DevController:150) Waiting for devices vif. [2008-06-11 11:24:10 2528] DEBUG (DevController:155) Waiting for 0. [2008-06-11 11:24:10 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2008-06-11 11:24:10 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2008-06-11 11:24:10 2528] DEBUG (DevController:608) hotplugStatusCallback 1. [2008-06-11 11:24:10 2528] DEBUG (DevController:150) Waiting for devices usb. [2008-06-11 11:24:10 2528] DEBUG (DevController:150) Waiting for devices vbd. [2008-06-11 11:24:10 2528] DEBUG (DevController:155) Waiting for 2049. [2008-06-11 11:24:10 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status. [2008-06-11 11:24:10 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vbd/1/2049/hotplug-status. [2008-06-11 11:24:10 2528] DEBUG (DevController:608) hotplugStatusCallback 2. [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=1 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:1821) XendDomainInfo.destroyDomain(1) [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:1479) Removing vif/0 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:1479) Removing vbd/2049 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:1479) Removing vbd/2050 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:1479) Removing console/0 [2008-06-11 11:24:10 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 [2008-06-12 11:24:40 2528] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name', 'test'], ['memory', '128'], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop', 'ignore'], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6.21.7-3.fc8xen'], ['ramdisk', '/boot/initrd-2.6.21.7-3.fc8xen.img'], ['ip', ':1.2.3.4::::eth0:dhcp'], ['root', '/dev/sda1 ro']]], ['device', ['vbd', ['uname', 'file:/data/xen/domains/test/disk.img'], ['dev', 'sda1'], ['mode', 'w']]], ['device', ['vbd', ['uname', 'file:/data/xen/domains/test/swap.img'], ['dev', 'sda2'], ['mode', 'w']]], ['device', ['vif']]]) [2008-06-12 11:24:40 2528] DEBUG (XendDomainInfo:1555) XendDomainInfo.constructDomain [2008-06-12 11:24:40 2528] DEBUG (balloon:116) Balloon: 131072 KiB free; need 2048; done. [2008-06-12 11:24:40 2528] DEBUG (XendDomain:443) Adding Domain: 2 [2008-06-12 11:24:40 2528] DEBUG (XendDomainInfo:1609) XendDomainInfo.initDomain: 2 256 [2008-06-12 11:24:40 2528] DEBUG (XendDomainInfo:1640) _initDomain:shadow_memory=0x0, memory_static_max=0x8000000, memory_static_min=0x0. [2008-06-12 11:24:40 2528] DEBUG (balloon:116) Balloon: 131072 KiB free; need 131072; done. [2008-06-12 11:24:40 2528] INFO (image:129) buildDomain os=linux dom=2 vcpus=1 [2008-06-12 11:24:40 2528] DEBUG (image:198) domid = 2 [2008-06-12 11:24:40 2528] DEBUG (image:199) memsize = 128 [2008-06-12 11:24:40 2528] DEBUG (image:200) image = /boot/vmlinuz-2.6.21.7-3.fc8xen [2008-06-12 11:24:40 2528] DEBUG (image:201) store_evtchn = 1 [2008-06-12 11:24:40 2528] DEBUG (image:202) console_evtchn = 2 [2008-06-12 11:24:40 2528] DEBUG (image:203) cmdline = root=/dev/sda1 ro ip=:1.2.3.4::::eth0:dhcp [2008-06-12 11:24:40 2528] DEBUG (image:204) ramdisk = /boot/initrd-2.6.21.7-3.fc8xen.img [2008-06-12 11:24:40 2528] DEBUG (image:205) vcpus = 1 [2008-06-12 11:24:40 2528] DEBUG (image:206) features = [2008-06-12 11:24:41 2528] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid': 'a80a5da8-49f0-8a5b-8ab1-315586fbc043', 'bootable': 1, 'driver': 'paravirtualised', 'dev': 'sda1', 'uname': 'file:/data/xen/domains/test/disk.img', 'mode': 'w'} [2008-06-12 11:24:41 2528] DEBUG (DevController:117) DevController: writing {'virtual-device': '2049', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/2/2049'} to /local/domain/2/device/vbd/2049. [2008-06-12 11:24:41 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'frontend': '/local/domain/2/device/vbd/2049', 'uuid': 'a80a5da8-49f0-8a5b-8ab1-315586fbc043', 'dev': 'sda1', 'state': '1', 'params': '/data/xen/domains/test/disk.img', 'mode': 'w', 'online': '1', 'frontend-id': '2', 'type': 'file'} to /local/domain/0/backend/vbd/2/2049. [2008-06-12 11:24:41 2528] INFO (XendDomainInfo:1458) createDevice: vbd : {'uuid': '464904a6-f7b0-d5dd-6e87-f031694ca985', 'bootable': 0, 'driver': 'paravirtualised', 'dev': 'sda2', 'uname': 'file:/data/xen/domains/test/swap.img', 'mode': 'w'} [2008-06-12 11:24:41 2528] DEBUG (DevController:117) DevController: writing {'virtual-device': '2050', 'device-type': 'disk', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vbd/2/2050'} to /local/domain/2/device/vbd/2050. [2008-06-12 11:24:41 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'frontend': '/local/domain/2/device/vbd/2050', 'uuid': '464904a6-f7b0-d5dd-6e87-f031694ca985', 'dev': 'sda2', 'state': '1', 'params': '/data/xen/domains/test/swap.img', 'mode': 'w', 'online': '1', 'frontend-id': '2', 'type': 'file'} to /local/domain/0/backend/vbd/2/2050. [2008-06-12 11:24:41 2528] INFO (XendDomainInfo:1458) createDevice: vif : {'mac': '00:16:3e:28:7f:4a', 'uuid': 'c9e74d33-67b3-3ecf-549d-ed9b7ed4009b'} [2008-06-12 11:24:41 2528] DEBUG (DevController:117) DevController: writing {'mac': '00:16:3e:28:7f:4a', 'handle': '0', 'protocol': 'x86_32-abi', 'backend-id': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/2/0'} to /local/domain/2/device/vif/0. [2008-06-12 11:24:41 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'handle': '0', 'uuid': 'c9e74d33-67b3-3ecf-549d-ed9b7ed4009b', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/2/device/vif/0', 'mac': '00:16:3e:28:7f:4a', 'online': '1', 'frontend-id': '2'} to /local/domain/0/backend/vif/2/0. [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:2116) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '0', 'uuid': '1ab9d29a-b2ff-ec05-4748-7efc1bf86f18', 'on_reboot': 'restart', 'start_time': '1213262681.16', 'on_poweroff': 'destroy', 'on_xend_start': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'image': "(linux (kernel /boot/vmlinuz-2.6.21.7-3.fc8xen) (ramdisk /boot/initrd-2.6.21.7-3.fc8xen.img) (args 'root=/dev/sda1 ro ip=:1.2.3.4::::eth0:dhcp ') (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': 'test'} [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:956) Storing domain details: {'console/ring-ref': '2261948', 'image/entry': '3238002688', 'console/port': '2', 'store/ring-ref': '2261949', 'image/loader': 'generic', 'vm': '/vm/1ab9d29a-b2ff-ec05-4748-7efc1bf86f18', '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': '131072', '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': 'test', 'domid': '2', 'image/xen-version': 'xen-3.0', 'store/port': '1'} [2008-06-12 11:24:41 2528] DEBUG (DevController:117) DevController: writing {'protocol': 'x86_32-abi', 'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/console/2/0'} to /local/domain/2/device/console/0. [2008-06-12 11:24:41 2528] DEBUG (DevController:119) DevController: writing {'domain': 'test', 'protocol': 'vt100', 'uuid': 'f116d906-4a3d-351b-68c1-19d4bec0fb5c', 'frontend': '/local/domain/2/device/console/0', 'state': '1', 'location': '2', 'online': '1', 'frontend-id': '2'} to /local/domain/0/backend/console/2/0. [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1040) XendDomainInfo.handleShutdownWatch [2008-06-12 11:24:41 2528] DEBUG (DevController:150) Waiting for devices vif. [2008-06-12 11:24:41 2528] DEBUG (DevController:155) Waiting for 0. [2008-06-12 11:24:41 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status. [2008-06-12 11:24:41 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vif/2/0/hotplug-status. [2008-06-12 11:24:41 2528] DEBUG (DevController:608) hotplugStatusCallback 1. [2008-06-12 11:24:41 2528] DEBUG (DevController:150) Waiting for devices usb. [2008-06-12 11:24:41 2528] DEBUG (DevController:150) Waiting for devices vbd. [2008-06-12 11:24:41 2528] DEBUG (DevController:155) Waiting for 2049. [2008-06-12 11:24:41 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vbd/2/2049/hotplug-status. [2008-06-12 11:24:41 2528] DEBUG (DevController:594) hotplugStatusCallback /local/domain/0/backend/vbd/2/2049/hotplug-status. [2008-06-12 11:24:41 2528] DEBUG (DevController:608) hotplugStatusCallback 2. [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1802) XendDomainInfo.destroy: domid=2 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1821) XendDomainInfo.destroyDomain(2) [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1479) Removing vif/0 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1479) Removing vbd/2049 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2049 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1479) Removing vbd/2050 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/2050 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:1479) Removing console/0 [2008-06-12 11:24:41 2528] DEBUG (XendDomainInfo:569) XendDomainInfo.destroyDevice: deviceClass = console, device = console/0 ---------------------------------------- *xen-hotplug.log:* ------------------------------- Nothing to flush. /data/xen/domains/test/disk.img: Permission denied xenstore-read: couldn't read path backend/vbd/2/2049/node ------------------------------- The entire directory is world-accessible and writable, so there should be no permission-problems with accessing the disk-images (VBD). I am using the root-account to start the xen-vm. *The configuration-file for the "test"-vm looks like this:* ------------------------------- # Configuration file for the Xen instance vm01.example.com, created on # Mon Jun 2 17:06:01 2008. # Kernel + memory size kernel = '/boot/vmlinuz-2.6.21.7-3.fc8xen' ramdisk = '/boot/initrd-2.6.21.7-3.fc8xen.img' memory = '128' # Disk device(s). root = '/dev/sda1 ro' disk = [ 'file:/data/xen/domains/test/disk.img,sda1,w', 'file:/data/xen/domains/test/swap.img,sda2,w' ] # Hostname name = 'test' # Networking dhcp = 'dhcp' vif = [ '' ] # Behaviour on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' --------------------------------- An attempt to mount the disk-images to an unused-loop-device with losetup works without any problems. ---------------------------------- [root at dmxen xen]# losetup /dev/loop0 /data/xen/domains/test/disk.img [root at dmxen xen]# losetup -a /dev/loop0: [0902]:192479239 (/data/xen/domains/test/disk.img) ---------------------------------- System details: _Kernel:_ Linux dmxen 2.6.21.7-3.fc8xen #1 SMP Thu Mar 20 14:57:53 EDT 2008 i686 i686 i386 GNU/Linux Xen-Version: Xen 3.1.2 Any help and information would be very welcome. Thanks in advance Christian From felix.schwarz at web.de Sun Jun 15 12:46:57 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Sun, 15 Jun 2008 14:46:57 +0200 Subject: [Fedora-xen] Xenner: How to manage domains with virsh? Message-ID: <48550F41.9030707@web.de> Hi, I got xenner to run on Fedora 9. And so far it seems that it is able to run at least some of my paravirtualized guests which I created on Xen/Fedora 8. Now the problem is how I can manage these domains using virsh? I can start a Xenner domain using "xenner (and bunch of options)". Everything seems to be fine. But "virsh list" does not show any active domains. So how can add the configuration to virsh so that I can do something like "virsh start mydomain"? Is this possible at all in the current Xenner (using Fedora 9 with all released updates but nothing from updates-testing)? fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From gvm999 at gmail.com Sun Jun 15 13:26:25 2008 From: gvm999 at gmail.com (gvm999) Date: Sun, 15 Jun 2008 15:26:25 +0200 Subject: [Fedora-xen] Virtual Machine Manager Message-ID: Hi all, This is probably a stupid question, but I can't figure it out... I want to try Virtual Machine Manager. When I create a new machine, there is asked for a "Install Media url". I want to install FreeBSD as a virtual machine, however, what url should I specify then? Or is this only for redhat systems? (fedora/centos?) Greetings! -------------- next part -------------- An HTML attachment was scrubbed... URL: From markmc at redhat.com Tue Jun 17 14:30:59 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Tue, 17 Jun 2008 15:30:59 +0100 Subject: [Fedora-xen] xen network bridge with eth0:1 aliases, tmpbridge? In-Reply-To: <6723ade0806060933n31624f49jcf08bbf99ec07fe@mail.gmail.com> References: <6723ade0806060933n31624f49jcf08bbf99ec07fe@mail.gmail.com> Message-ID: <1213713059.31834.33.camel@muff> On Fri, 2008-06-06 at 09:33 -0700, Frank Liu wrote: > Does that mean xen in Fedora 8 still can't deal with eth0:1 alias? > > In my case, I only want xen to use eth0 to bridge to the domU, and > eth0:1 is for some other apps on the dom0. I tried to put a > "netdev=eth0" in the xend-config.sxp and that didn't help. This is the fix: http://xenbits.xensource.com/xen-unstable.hg?rev/7b7700a30e52 It's not in F8, so feel free to open a bug about it if you wish. Cheers, Mark. From gastonkeller at gmail.com Tue Jun 17 18:14:55 2008 From: gastonkeller at gmail.com (=?ISO-8859-1?Q?Gast=F3n_Keller?=) Date: Tue, 17 Jun 2008 14:14:55 -0400 Subject: [Fedora-xen] Virtual Machine Manager In-Reply-To: References: Message-ID: On 6/15/08, gvm999 wrote: > Hi all, > > This is probably a stupid question, but I can't figure it out... > > I want to try Virtual Machine Manager. > When I create a new machine, there is asked for a "Install Media url". > > I want to install FreeBSD as a virtual machine, however, what url should I > specify then? I have never used it, but I guess it is asking for an url to an installation tree of the distribution you want. Gaston > Or is this only for redhat systems? (fedora/centos?) > > Greetings! > -- La ?nica verdad es la realidad. From cowan at bnl.gov Tue Jun 17 19:50:56 2008 From: cowan at bnl.gov (Matt Cowan) Date: Tue, 17 Jun 2008 15:50:56 -0400 (EDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 Message-ID: Anytime I shutdown or restart (the guest will successfully restart) an f9 guest on an f8 dom0 it causes virt-manager to hang and virt-install to fail. Attempts to restart virt-manager hang at "Connecting". no luck restarting xend, libvirtd, or even xenstored, only solution I've found is a dom0 reboot! Same problem on 2 different host systems, different hardware, dom0 installed by different people. I have no trouble with <=f8 guests on either of these boxes. more details at https://bugzilla.redhat.com/show_bug.cgi?id=429403#c7 I assume other people are successfully running f9 guests on f8 dom0?! No one else having this issue? thanks. -matt From xjakub at fi.muni.cz Tue Jun 17 19:57:04 2008 From: xjakub at fi.muni.cz (Milos Jakubicek) Date: Tue, 17 Jun 2008 21:57:04 +0200 Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: References: Message-ID: <48581710.3020607@fi.muni.cz> Matt Cowan wrote: > > I assume other people are successfully running f9 guests on f8 dom0?! Hm, yesterday I even didn't manage to install it -- virt-install crashed immediately (while installing f8 guests worked fine), I wonder if it is currently supported(?). (If it should I'll try again and file a bug then with details) -- Regards, Milos From gcox at capitalinvestigating.com Tue Jun 17 16:22:33 2008 From: gcox at capitalinvestigating.com (Greg Cox) Date: Tue, 17 Jun 2008 12:22:33 -0400 Subject: [Fedora-xen] RE: Fedora-xen Digest, Vol 31, Issue 11 In-Reply-To: <20080617160011.92A4D619CFD@hormel.redhat.com> Message-ID: <200806171809.m5HI9Ko5022383@mx3.redhat.com> At which point do you receive the error message? I ran into a similar problem where an xp guest would loose its mapping/path to the install media or image after the initial reboot during the XP installation. After several months of banging my head against a wall, I finally found an interface to set it manually in the machine details screen> Hardware Tab. Setting the variable here will reconnect the device upon the next guest boot. A quick Google revealed this is a common issue but I was not able to find the solution posted anywhere. When I have some time, I plan on posting it in a few of the popular fedora forums. Hopefully this helps, if not repost with a few more specifics and one of the veterans may be able to steer you in the right direction. G'luck G -----Original Message----- From: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] On Behalf Of fedora-xen-request at redhat.com Sent: Tuesday, June 17, 2008 12:00 PM To: fedora-xen at redhat.com Subject: Fedora-xen Digest, Vol 31, Issue 11 Send Fedora-xen mailing list submissions to fedora-xen at redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/fedora-xen or, via email, send a message with subject or body 'help' to fedora-xen-request at redhat.com You can reach the person managing the list at fedora-xen-owner at redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of Fedora-xen digest..." Today's Topics: 1. Virtual Machine Manager (gvm999) 2. Re: xen network bridge with eth0:1 aliases, tmpbridge? (Mark McLoughlin) ---------------------------------------------------------------------- Message: 1 Date: Sun, 15 Jun 2008 15:26:25 +0200 From: gvm999 Subject: [Fedora-xen] Virtual Machine Manager To: fedora-xen at redhat.com Message-ID: Content-Type: text/plain; charset="iso-8859-1" Hi all, This is probably a stupid question, but I can't figure it out... I want to try Virtual Machine Manager. When I create a new machine, there is asked for a "Install Media url". I want to install FreeBSD as a virtual machine, however, what url should I specify then? Or is this only for redhat systems? (fedora/centos?) Greetings! -------------- next part -------------- An HTML attachment was scrubbed... URL: https://www.redhat.com/archives/fedora-xen/attachments/20080615/c59bb23f/att achment.html ------------------------------ Message: 2 Date: Tue, 17 Jun 2008 15:30:59 +0100 From: Mark McLoughlin Subject: Re: [Fedora-xen] xen network bridge with eth0:1 aliases, tmpbridge? To: Frank Liu Cc: fedora-xen at redhat.com Message-ID: <1213713059.31834.33.camel at muff> Content-Type: text/plain On Fri, 2008-06-06 at 09:33 -0700, Frank Liu wrote: > Does that mean xen in Fedora 8 still can't deal with eth0:1 alias? > > In my case, I only want xen to use eth0 to bridge to the domU, and > eth0:1 is for some other apps on the dom0. I tried to put a > "netdev=eth0" in the xend-config.sxp and that didn't help. This is the fix: http://xenbits.xensource.com/xen-unstable.hg?rev/7b7700a30e52 It's not in F8, so feel free to open a bug about it if you wish. Cheers, Mark. ------------------------------ -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen End of Fedora-xen Digest, Vol 31, Issue 11 ****************************************** From dlbewley at lib.ucdavis.edu Wed Jun 18 23:29:09 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Wed, 18 Jun 2008 16:29:09 -0700 Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <48581710.3020607@fi.muni.cz> References: <48581710.3020607@fi.muni.cz> Message-ID: <1213831749.5295.7.camel@tofu.lib.ucdavis.edu> On Tue, 2008-06-17 at 21:57 +0200, Milos Jakubicek wrote: > Matt Cowan wrote: > > > > I assume other people are successfully running f9 guests on f8 dom0?! > > Hm, yesterday I even didn't manage to install it -- virt-install crashed > immediately (while installing f8 guests worked fine), I wonder if it is > currently supported(?). > > (If it should I'll try again and file a bug then with details) I have installed F9 domU on F8 dom0. Haven't done anything but login to it yet. Dom0: 2.6.21.7-3.fc8xen x86_64 DomU: 2.6.25-2.fc9.x86_64.xen x86_64 virt-install --name=fedora9 \ --ram=512 \ --file=/var/lib/xen/images/fedora9.xen \ --file-size=5 \ --nographics \ --location=http://ks/fedora/linux/releases/9/Fedora/x86_64/os \ --extra-args=dhcp ks=http://ks/ks-f9-xen.cfg \ --bridge=br101 \ --mac=AA:00:48:59:98:B3 \ --uuid=00000000-0000-0000-0000-AA00485998B3 \ --debug -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From martin at jpmvrealtime.com Thu Jun 19 00:23:10 2008 From: martin at jpmvrealtime.com (Martin Vuille) Date: Thu, 19 Jun 2008 00:23:10 +0000 (UTC) Subject: [Fedora-xen] No Dom0 support in Fedora 9 and Fedora 8 EOL Message-ID: I'm putting together a virtualized server. I was planning to use Fedora 9, until I found out that Fedora 9 won't run as a Dom0, so I ended up using Fedora 8 instead. I also learned that the standard EOL policy is to discontinue support for release N one month after the release of release N+2. Since Dom0 support isn't expected until Fedora 10, it sounds like this means that I will have to upgrade my system in the first month immediately following the release of Fedora 10, or lose support. Neither option seems particularly reasonable to me. Since upgrading from Fedora 8 to Fedora 9 isn't an option for anyone using Xen, I am wondering if there is any plan to extend Fedora 8's support period beyond the usual one month? MV From felix.schwarz at web.de Thu Jun 19 05:34:26 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Thu, 19 Jun 2008 07:34:26 +0200 Subject: [Fedora-xen] No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: References: Message-ID: <4859EFE2.4090101@web.de> Martin Vuille schrieb: > Since upgrading from Fedora 8 to Fedora 9 isn't an option for > anyone using Xen, I am wondering if there is any plan to extend > Fedora 8's support period beyond the usual one month? Frankly I don't know but I don't think that this is very likely to happen. If upgrading is an issue for you, you should look at RHEL (or one of the 'gratis' clones like CentOS). fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From cowan at bnl.gov Thu Jun 19 05:34:37 2008 From: cowan at bnl.gov (Matt Cowan) Date: Thu, 19 Jun 2008 01:34:37 -0400 (EDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <1213831749.5295.7.camel@tofu.lib.ucdavis.edu> References: <48581710.3020607@fi.muni.cz> <1213831749.5295.7.camel@tofu.lib.ucdavis.edu> Message-ID: On Wed, 18 Jun 2008, Dale Bewley wrote: >> Matt Cowan wrote: >>> I assume other people are successfully running f9 guests on f8 dom0?! ... > I have installed F9 domU on F8 dom0. Haven't done anything but login to > it yet. ... does virt-manager still work? can you virt-install another domU? how about after you shutdown the f9 domU? -matt From felix.schwarz at web.de Thu Jun 19 05:36:35 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Thu, 19 Jun 2008 07:36:35 +0200 Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: <4859EFE2.4090101@web.de> References: <4859EFE2.4090101@web.de> Message-ID: <4859F063.6090704@web.de> Oh, and besides that I'm note sure if running Xen/Dom0 on Fedora 8 is advisable from a security pov: I think the xen kernel (2.6.21) lacks quite a few security patches that the normal Fedora kernel already got... fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From addw at phcomp.co.uk Thu Jun 19 09:28:35 2008 From: addw at phcomp.co.uk (Alain Williams) Date: Thu, 19 Jun 2008 10:28:35 +0100 Subject: [Fedora-xen] No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: References: Message-ID: <20080619092835.GP20591@mint.phcomp.co.uk> On Thu, Jun 19, 2008 at 12:23:10AM +0000, Martin Vuille wrote: > I'm putting together a virtualized server. I was planning to use > Fedora 9, until I found out that Fedora 9 won't run as a Dom0, so > I ended up using Fedora 8 instead. Damn - I have just run into the buffers because of that. I have just reinstalled my test box with Fedora 9 ... wanted to run several guests under it. Shame it was not flagged up bigger somewhere. -- 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 martin at jpmvrealtime.com Thu Jun 19 09:40:57 2008 From: martin at jpmvrealtime.com (Martin Vuille) Date: Thu, 19 Jun 2008 09:40:57 +0000 (UTC) Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL References: <4859EFE2.4090101@web.de> Message-ID: Felix Schwarz wrote in news:4859EFE2.4090101 at web.de: > Martin Vuille schrieb: >> Since upgrading from Fedora 8 to Fedora 9 isn't an option >> for anyone using Xen, I am wondering if there is any plan to >> extend Fedora 8's support period beyond the usual one month? > > Frankly I don't know but I don't think that this is very > likely to happen. If upgrading is an issue for you, you > should look at RHEL (or one of the 'gratis' clones like > CentOS). I don't have an issue with upgrading; I chose Fedora because I wanted a distro that was at the leading edge. But that doesn't mean that I want to upgrade to the latest Fedora release on the same day it's released. I will upgrade during the one-month grace period if I have to, but I would have been more comfortable with a little more wiggle room. MV From martin at jpmvrealtime.com Thu Jun 19 09:41:57 2008 From: martin at jpmvrealtime.com (Martin Vuille) Date: Thu, 19 Jun 2008 09:41:57 +0000 (UTC) Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL References: <4859EFE2.4090101@web.de> <4859F063.6090704@web.de> Message-ID: Felix Schwarz wrote in news:4859F063.6090704 at web.de: > Oh, and besides that I'm note sure if running Xen/Dom0 on > Fedora 8 is advisable from a security pov: I think the xen > kernel (2.6.21) lacks quite a few security patches that the > normal Fedora kernel already got... OK, so what would you recommend then? MV From addw at phcomp.co.uk Thu Jun 19 10:02:16 2008 From: addw at phcomp.co.uk (Alain Williams) Date: Thu, 19 Jun 2008 11:02:16 +0100 Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: References: <4859EFE2.4090101@web.de> <4859F063.6090704@web.de> Message-ID: <20080619100216.GS20591@mint.phcomp.co.uk> On Thu, Jun 19, 2008 at 09:41:57AM +0000, Martin Vuille wrote: > Felix Schwarz wrote in > news:4859F063.6090704 at web.de: > > > Oh, and besides that I'm note sure if running Xen/Dom0 on > > Fedora 8 is advisable from a security pov: I think the xen > > kernel (2.6.21) lacks quite a few security patches that the > > normal Fedora kernel already got... > > OK, so what would you recommend then? What are your requirements ? Perhaps: * Modern Dom0 * Ability to run LVM * ISO image to install from For me: * x86_64 * something that comes with X windows -- 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 sa212+fcxen at cyconix.com Thu Jun 19 11:40:10 2008 From: sa212+fcxen at cyconix.com (Evan Lavelle) Date: Thu, 19 Jun 2008 12:40:10 +0100 Subject: [Fedora-xen] No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: <20080619092835.GP20591@mint.phcomp.co.uk> References: <20080619092835.GP20591@mint.phcomp.co.uk> Message-ID: <485A459A.9050601@cyconix.com> Alain Williams wrote: > On Thu, Jun 19, 2008 at 12:23:10AM +0000, Martin Vuille wrote: >> I'm putting together a virtualized server. I was planning to use >> Fedora 9, until I found out that Fedora 9 won't run as a Dom0, so >> I ended up using Fedora 8 instead. > > Damn - I have just run into the buffers because of that. > I have just reinstalled my test box with Fedora 9 ... wanted to > run several guests under it. Shame it was not flagged up bigger somewhere. I'm currently on an F8 Dom0 at the moment, but I'll need to upgrade Xen fairly soon. At the moment, it seems to me that one of the Solaris distros is the way to go, particularly since they have built-in Windows PV drivers. There also seems to be a lot of development activity. -Evan From marceldamasio at gmail.com Thu Jun 19 21:56:22 2008 From: marceldamasio at gmail.com (=?ISO-8859-1?Q?Marcel_Dam=E1sio?=) Date: Thu, 19 Jun 2008 18:56:22 -0300 Subject: [Fedora-xen] How to change hostname from cloned VMs Message-ID: <386f83ad0806191456q70f9c0cdsa4c42c9afe7d26b9@mail.gmail.com> Hi all! I have a question not specifically about virtualization. I'm using virt-clone to clone my VMs. But the new VMs generated have the same hostname as the original. How can I change my VMs hostname without impact any application? There are a lot of places that I can change the hostname, but I don't know the right and garanteed way to do that change. -- Marcel Dam?sio Moreira 9? per?odo de Ci?ncia da Computa??o - UFES (27) 8128-7106 Estagi?rio do Suporte - DI/UFES -------------- next part -------------- An HTML attachment was scrubbed... URL: From veillard at redhat.com Fri Jun 20 07:51:39 2008 From: veillard at redhat.com (Daniel Veillard) Date: Fri, 20 Jun 2008 03:51:39 -0400 Subject: [Fedora-xen] How to change hostname from cloned VMs In-Reply-To: <386f83ad0806191456q70f9c0cdsa4c42c9afe7d26b9@mail.gmail.com> References: <386f83ad0806191456q70f9c0cdsa4c42c9afe7d26b9@mail.gmail.com> Message-ID: <20080620075139.GB27072@redhat.com> On Thu, Jun 19, 2008 at 06:56:22PM -0300, Marcel Dam?sio wrote: > Hi all! > > I have a question not specifically about virtualization. > I'm using virt-clone to clone my VMs. > But the new VMs generated have the same hostname as the original. > > How can I change my VMs hostname without impact any application? > There are a lot of places that I can change the hostname, but I don't know > the right and garanteed way to do that change. I don't think there is a 'right and garanteed way to do that change'. many things may embed the host name, like application configuration files, certificates, etc. Some things can be automated, like grepping for the hostname in /etc/ subtree, changing /etc/sysconfig/network is one safe thing to do automatically but you really can't guarantee to provide a recipe which will work in all cases for all software, since each can use its own way. Based on your set and your environment I think there is always some specifics which need to be aplied after cloning, like forcing regeneration of machine certificates, ssh keys, the applications configuration and plugging the new clone in your infrastructure (DNS/DHCP/...) it's always a bit more than just the hostname from my viewpoint, and very hard to generalize because it quickly get very specific. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard at redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/ From almamatex at gmail.com Fri Jun 20 10:19:00 2008 From: almamatex at gmail.com (Alma Matex) Date: Fri, 20 Jun 2008 12:19:00 +0200 Subject: [Fedora-xen] Assign IP and CONFIG_IP_PNP problem Message-ID: <240853650806200319w188fc58cu6667f51ceb3ee9be@mail.gmail.com> Hi, I'm new to Xen and I'm having problem with Xen networking. I read that one could set the IP address of a new virtual machine in the configuration file with the vif statement. For example: vif = [ 'mac=00:00:00:00:00:01, bridge=virbr0' ] ip = "10.10.10.1" My problem is that when the virtual machine start it doesn't get the IP. Insted it uses dhcp to get one. I found that the xen kernel must be compiled with the CONFIG_IP_PNP option set, but my kernel doesn't seem to have it. Infact: grep CONFIG_IP_PNP /boot/config-2.6.21.7-3.fc8xen gives me: # CONFIG_IP_PNP is not set Is this one the only problem? Is there a way to get a fedora precompiled kernel with this option set? Thanks Regards Matteo -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Fri Jun 20 21:25:33 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 20 Jun 2008 17:25:33 -0400 Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: References: <4859EFE2.4090101@web.de> Message-ID: <20080620212533.GA12531@thinkpad.comcastbusiness.net> On Thu, Jun 19, 2008 at 09:40:57AM +0000, Martin Vuille wrote: > Felix Schwarz wrote in > news:4859EFE2.4090101 at web.de: > > Martin Vuille schrieb: > >> Since upgrading from Fedora 8 to Fedora 9 isn't an option > >> for anyone using Xen, I am wondering if there is any plan to > >> extend Fedora 8's support period beyond the usual one month? > > > > Frankly I don't know but I don't think that this is very > > likely to happen. If upgrading is an issue for you, you > > should look at RHEL (or one of the 'gratis' clones like > > CentOS). > > I don't have an issue with upgrading; I chose Fedora because I > wanted a distro that was at the leading edge. > > But that doesn't mean that I want to upgrade to the latest Fedora > release on the same day it's released. I will upgrade during the > one-month grace period if I have to, but I would have been more > comfortable with a little more wiggle room. You'll need to ask Dan Berrange to be certain, but I'm pretty sure the plan is to have a dom0 kernel ready some time during the lifetime of F9. The reason we don't have an F9 dom0 kernel right now is because there *isn't one*. Ask XenSource to provide something more recent than > 2 year old Linux 2.6.18 support! Red Hat are committing two full time developers right now to fix this situation, but it is NOT our fault. You might also want to try out KVM. Rich. From rjones at redhat.com Fri Jun 20 21:27:07 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 20 Jun 2008 17:27:07 -0400 Subject: [Fedora-xen] Virtual Machine Manager In-Reply-To: References: Message-ID: <20080620212707.GB12531@thinkpad.comcastbusiness.net> On Sun, Jun 15, 2008 at 03:26:25PM +0200, gvm999 wrote: > This is probably a stupid question, but I can't figure it out... > > I want to try Virtual Machine Manager. > When I create a new machine, there is asked for a "Install Media url". > > I want to install FreeBSD as a virtual machine, however, what url should I > specify then? > Or is this only for redhat systems? (fedora/centos?) For FreeBSD, download an ISO and use the CD/ISO method. However last time I tried it, FreeBSD couldn't be installed. You might want to check on the status of bugs at http://bugzilla.redhat.com Rich. From rjones at redhat.com Fri Jun 20 21:30:42 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 20 Jun 2008 17:30:42 -0400 Subject: [Fedora-xen] Xenner: How to manage domains with virsh? In-Reply-To: <48550F41.9030707@web.de> References: <48550F41.9030707@web.de> Message-ID: <20080620213042.GC12531@thinkpad.comcastbusiness.net> On Sun, Jun 15, 2008 at 02:46:57PM +0200, Felix Schwarz wrote: > I got xenner to run on Fedora 9. And so far it seems that it is able to > run at least some of my paravirtualized guests which I created on > Xen/Fedora 8. > > Now the problem is how I can manage these domains using virsh? I can > start a Xenner domain using "xenner (and bunch of options)". Everything > seems to be fine. > > But "virsh list" does not show any active domains. So how can add the > configuration to virsh so that I can do something like "virsh start > mydomain"? > Is this possible at all in the current Xenner (using Fedora 9 with all > released updates but nothing from updates-testing)? I'm not exactly sure if support for Xenner has actually gone into libvirt yet. I know Dan is working on a patch. At the moment libvirtd only tries to manage qemu/kvm/xenner processes which are started up by it. The reason is that the daemon keeps a pipe open to the qemu monitor so it can issue commands. If you start a guest up by hand, then libvirtd doesn't know about it and doesn't have access to the monitor. We did discuss a way to work around this, but it's not in libvirtd at this time. Rich. From martin at jpmvrealtime.com Fri Jun 20 21:48:17 2008 From: martin at jpmvrealtime.com (Martin Vuille) Date: Fri, 20 Jun 2008 21:48:17 +0000 (UTC) Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL References: <4859EFE2.4090101@web.de> <20080620212533.GA12531@thinkpad.comcastbusiness.net> Message-ID: "Richard W.M. Jones" wrote in news:20080620212533.GA12531 at thinkpad.comcastbusiness.net: > > You'll need to ask Dan Berrange to be certain, but I'm pretty > sure the plan is to have a dom0 kernel ready some time during > the lifetime of F9. > > The reason we don't have an F9 dom0 kernel right now is > because there *isn't one*. Ask XenSource to provide > something more recent than > 2 year old Linux 2.6.18 support! > Red Hat are committing two full time developers right now to > fix this situation, but it is NOT our fault. > Thanks for the clarification. I'll keep on the lookout for updates in F9. MV From felix.schwarz at web.de Sat Jun 21 08:22:54 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Sat, 21 Jun 2008 10:22:54 +0200 Subject: [Fedora-xen] Re: Xenner: How to manage domains with virsh? In-Reply-To: <20080620213042.GC12531@thinkpad.comcastbusiness.net> References: <48550F41.9030707@web.de> <20080620213042.GC12531@thinkpad.comcastbusiness.net> Message-ID: <485CBA5E.4050206@web.de> Richard W.M. Jones wrote: > I'm not exactly sure if support for Xenner has actually gone > into libvirt yet. I know Dan is working on a patch. (...) Thanks for your explanation, Rich. Much appreciated :-) And thanks to all those developers making Xen+paravirt_ops a reality! fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From berrange at redhat.com Sun Jun 22 19:45:15 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 22 Jun 2008 20:45:15 +0100 Subject: [Fedora-xen] Xenner: How to manage domains with virsh? In-Reply-To: <20080620213042.GC12531@thinkpad.comcastbusiness.net> References: <48550F41.9030707@web.de> <20080620213042.GC12531@thinkpad.comcastbusiness.net> Message-ID: <20080622194515.GB2123@redhat.com> On Fri, Jun 20, 2008 at 05:30:42PM -0400, Richard W.M. Jones wrote: > On Sun, Jun 15, 2008 at 02:46:57PM +0200, Felix Schwarz wrote: > > I got xenner to run on Fedora 9. And so far it seems that it is able to > > run at least some of my paravirtualized guests which I created on > > Xen/Fedora 8. > > > > Now the problem is how I can manage these domains using virsh? I can > > start a Xenner domain using "xenner (and bunch of options)". Everything > > seems to be fine. > > > > But "virsh list" does not show any active domains. So how can add the > > configuration to virsh so that I can do something like "virsh start > > mydomain"? > > Is this possible at all in the current Xenner (using Fedora 9 with all > > released updates but nothing from updates-testing)? > > I'm not exactly sure if support for Xenner has actually gone > into libvirt yet. I know Dan is working on a patch. You'll need libvirt 0.4.3 to get Xenner working. You'll also need newer virt-install (from unreleased upstream source repos) and newer virt-manager Realistically we're looking at Fedora 10 for general availability of Xenner support with good feature coverage & reliability. Once it is finished, it'll be as simple as just using --paravirt instead of --hvm when running virt-install and it'll automatically use Xenner. Regards, Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From berrange at redhat.com Sun Jun 22 19:47:04 2008 From: berrange at redhat.com (Daniel P. Berrange) Date: Sun, 22 Jun 2008 20:47:04 +0100 Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: References: <4859EFE2.4090101@web.de> <20080620212533.GA12531@thinkpad.comcastbusiness.net> Message-ID: <20080622194704.GC2123@redhat.com> On Fri, Jun 20, 2008 at 09:48:17PM +0000, Martin Vuille wrote: > "Richard W.M. Jones" wrote in > news:20080620212533.GA12531 at thinkpad.comcastbusiness.net: > > > > > You'll need to ask Dan Berrange to be certain, but I'm pretty > > sure the plan is to have a dom0 kernel ready some time during > > the lifetime of F9. > > > > The reason we don't have an F9 dom0 kernel right now is > > because there *isn't one*. Ask XenSource to provide > > something more recent than > 2 year old Linux 2.6.18 support! > > Red Hat are committing two full time developers right now to > > fix this situation, but it is NOT our fault. > > > > Thanks for the clarification. I'll keep on the lookout for updates > in F9. Fedora 9 is basically DomU only and we're still working on getting the x86_64 patches accepted in upstream LKML trees. Best guess is that this will be 2.6.27 . In parallel we're still working on Dom0 support with pvops http://fedoraproject.org/wiki/Features/XenPvopsDom0 Daniel. -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| From kraxel at redhat.com Mon Jun 23 08:53:24 2008 From: kraxel at redhat.com (Gerd Hoffmann) Date: Mon, 23 Jun 2008 10:53:24 +0200 Subject: [Fedora-xen] Xenner: How to manage domains with virsh? In-Reply-To: <48550F41.9030707@web.de> References: <48550F41.9030707@web.de> Message-ID: <485F6484.8080501@redhat.com> Felix Schwarz wrote: > Hi, > > I got xenner to run on Fedora 9. And so far it seems that it is able to > run at least some of my paravirtualized guests which I created on > Xen/Fedora 8. Grab 0.37 from updates-testing, try again every guest, file bugs (or drop me a note) if you still have guests which don't boot. > Now the problem is how I can manage these domains using virsh? I can > start a Xenner domain using "xenner (and bunch of options)". Everything > seems to be fine. > But "virsh list" does not show any active domains. So how can add the > configuration to virsh so that I can do something like "virsh start > mydomain"? You must create a xml config file for them, look the format documentation at libvirt.org and /usr/share/doc/xenner-0.37/{libvirt,testinstall}.xml It still has some rougth edges, some of them should go away with the libvirt 0.4.3 release. cheers, Gerd -- http://kraxel.fedorapeople.org/xenner/ From martin at gamesplace.info Mon Jun 23 22:01:51 2008 From: martin at gamesplace.info (Martin =?ISO-8859-1?Q?J=FCrgens?=) Date: Tue, 24 Jun 2008 00:01:51 +0200 Subject: [Fedora-xen] Does my kernel support svm? Message-ID: <1214258511.2830.9.camel@medora> Hi, I read the Virtualization guide and installed a Xen kernel on my Fedora 8 system. The problem is that the Virtualization Guide says that I'd issue xm dmesg | grep SVM to find out if my Kernel supports svm. It says the following: # xm dmesg | grep SVM (XEN) AMD SVM: ASIDs disabled. (XEN) HVM: SVM enabled (XEN) AMD SVM: ASIDs disabled. As I can't select "hardware acceleration" in virt-manager I think that it means that something's wrong and I currently can't use svm. Does anyone have an idea about what's wrong? Thank you, Martin From dblack at vantage.com Tue Jun 24 16:12:12 2008 From: dblack at vantage.com (Dustin Black) Date: Tue, 24 Jun 2008 12:12:12 -0400 Subject: [Fedora-xen] Xen guests on the local network Message-ID: <1214323932.5023.4.camel@dblaptop> I find that Fedora 8 is using a DHCP service via libvirtd/qemu to assign addresses to any guests that I create. I also see that libvirtd enables ip forwarding and creates iptables entries to allow the Xen server to act as a router for the guests. I need to change this setup such that the guests appear on the same network as the Xen server, and are able to receive DHCP assignments from another server on the network. It may be that I just haven't chosen the right terms to search for, but I can't seem to find any documentation or reference to disabling or bypassing the qemu dhcp assignment and libvirt routing. Any help would be much appreciated. -Dustin Black From markmc at redhat.com Wed Jun 25 13:57:25 2008 From: markmc at redhat.com (Mark McLoughlin) Date: Wed, 25 Jun 2008 14:57:25 +0100 Subject: [Fedora-xen] Xen guests on the local network In-Reply-To: <1214323932.5023.4.camel@dblaptop> References: <1214323932.5023.4.camel@dblaptop> Message-ID: <1214402245.3560.13.camel@muff> On Tue, 2008-06-24 at 12:12 -0400, Dustin Black wrote: > I find that Fedora 8 is using a DHCP service via libvirtd/qemu to assign > addresses to any guests that I create. I also see that libvirtd enables > ip forwarding and creates iptables entries to allow the Xen server to > act as a router for the guests. > > I need to change this setup such that the guests appear on the same > network as the Xen server, and are able to receive DHCP assignments from > another server on the network. > > It may be that I just haven't chosen the right terms to search for, but > I can't seem to find any documentation or reference to disabling or > bypassing the qemu dhcp assignment and libvirt routing. Any help would > be much appreciated. Try this: http://wiki.libvirt.org/page/Networking Cheers, Mark. From dblack at vantage.com Wed Jun 25 14:42:54 2008 From: dblack at vantage.com (Dustin Black) Date: Wed, 25 Jun 2008 10:42:54 -0400 Subject: [Fedora-xen] Xen guests on the local network In-Reply-To: <1214402245.3560.13.camel@muff> References: <1214323932.5023.4.camel@dblaptop> <1214402245.3560.13.camel@muff> Message-ID: <1214404974.5023.38.camel@dblaptop> On Wed, 2008-06-25 at 09:57 -0400, Mark McLoughlin wrote: > On Tue, 2008-06-24 at 12:12 -0400, Dustin Black wrote: > > I find that Fedora 8 is using a DHCP service via libvirtd/qemu to assign > > addresses to any guests that I create. I also see that libvirtd enables > > ip forwarding and creates iptables entries to allow the Xen server to > > act as a router for the guests. > > > > I need to change this setup such that the guests appear on the same > > network as the Xen server, and are able to receive DHCP assignments from > > another server on the network. > > > > It may be that I just haven't chosen the right terms to search for, but > > I can't seem to find any documentation or reference to disabling or > > bypassing the qemu dhcp assignment and libvirt routing. Any help would > > be much appreciated. > > Try this: > > http://wiki.libvirt.org/page/Networking > > Cheers, > Mark. > Aaah... A very good resource, thank you. I also found this, which got me going in the right direction: http://www.mail-archive.com/fedora-xen at redhat.com/msg01527.html Regards, -Dustin From rjones at redhat.com Thu Jun 26 07:19:07 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 26 Jun 2008 08:19:07 +0100 Subject: [Fedora-xen] Re: No Dom0 support in Fedora 9 and Fedora 8 EOL In-Reply-To: <20080620212533.GA12531@thinkpad.comcastbusiness.net> References: <4859EFE2.4090101@web.de> <20080620212533.GA12531@thinkpad.comcastbusiness.net> Message-ID: <20080626071907.GA7898@thinkpad> On Fri, Jun 20, 2008 at 05:25:33PM -0400, Richard W.M. Jones wrote: > The reason we don't have an F9 dom0 kernel right now is because > there *isn't one*. Ask XenSource to provide something more recent > than > 2 year old Linux 2.6.18 support! Red Hat are committing > two full time developers right now to fix this situation, but it > is NOT our fault. It's been pointed out to me that Jeremy Fitzhardinge (at XenSource) is driving the pv_ops work which will bring a modern dom0 into Fedora 9 or 10. I don't want to forget or diminish Jeremy's crucial efforts. Rich. From fedora.lists at burns.me.uk Fri Jun 27 12:19:52 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Fri, 27 Jun 2008 13:19:52 +0100 Subject: [Fedora-xen] PCI passthrough Message-ID: I have an F8 dom0 (which could become a CentOS 5.2 dom0 if that would make anything easier) I'd like an F9 domU to have access to a PCI DVB tuner for a mythtv backend. I understand that I need to add "pciback.hide=(XX:YY.Z)" and possibly "pciback.permissive" to grub.conf for the dom0 How should I add the details of the corresponding "pci = ['XX:YY.Z']" to the domU config? I've looked in the documentation of the XML format at http://libvirt.org/formatdomain.html but can't see relevant tags. From dlbewley at lib.ucdavis.edu Fri Jun 27 16:30:03 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 27 Jun 2008 09:30:03 -0700 (PDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: Message-ID: <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> ----- "Matt Cowan" wrote: > On Wed, 18 Jun 2008, Dale Bewley wrote: > >> Matt Cowan wrote: > >>> I assume other people are successfully running f9 guests on f8 > dom0?! > ... > > I have installed F9 domU on F8 dom0. Haven't done anything but login > to > > it yet. > ... > > does virt-manager still work? > can you virt-install another domU? > how about after you shutdown the f9 domU? > > -matt I installed a new f9 domU with virt-isntall and from within the domU I issued a 'shutdown -h now'. Virt-manager still shows it as running, but 'virsh list --all' shows it as 'no state'. Virsh console can't find it. # virsh console f9test libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain 0 I right clicked in virt-manager and selected shutdown. Nothing happend. # virsh shutdown f9test libvir: Xen Daemon error : POST operation failed: (xend.err 'Domain cannot be shutdown') Domain f9test is being shutdown # virsh destroy f9test libvir: Xen Daemon error : POST operation failed: (xend.err "(3, 'No such process')") libvir: Xen error : failed Xen syscall ioctl 3166208 error: Failed to destroy domain f9test So, I started another pre-existing f9 domU in the virt-manager gui. Came up OK. Shut it down via the virt-manager gui and it behaves the same as the other test. Says 'running' in virt-manager and virsh says: # virsh console fedora95 libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain 0 So, I restarted xend and now virt-manager shows the correct states and virsh list shows 'shut off' state. I'm on libvirt-0.4.2-1.fc8 and see there is an update. I'll test some more later and also try to confirm this is different from f8 domU behavior. -- 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 Jun 27 21:33:39 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Fri, 27 Jun 2008 14:33:39 -0700 Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> References: <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <1214602419.16631.35.camel@tofu.lib.ucdavis.edu> > So, I restarted xend and now virt-manager shows the correct states and virsh > list shows 'shut off' state. I'm on libvirt-0.4.2-1.fc8 and see there is an > update. I'll test some more later and also try to confirm this is different > from f8 domU behavior. I updated to libvirt-0.4.3-1.fc8 and restarted libvirtd and virt-manager. I then started a f9 domU in virt-manager and shut it back down. That left me with the following. Virt-manager still lists it as "Running" but the CPU graph is blank. # virsh list --all Id Name State ---------------------------------- ...snip... - f9test no state # virsh start f9test error: Domain is already active # virsh console f9test libvir: Xen Daemon error : GET operation failed: xend_get: error from xen daemon: libvir: Xen Daemon error : failed Xen syscall xenDaemonDomainDumpXMLByID failed to find this domain 0 So, I installed a f8 domU with virt-install and then shut it down in virt-manager. It acted the same way. Once shutdown, I can't do anything with the domU in virt-manager or virsh until I restart xend. At which time virt-manager display updates with the correct state for each domain. Enviro: xen-3.1.2-2.fc8 libvirt-0.4.3-1.fc8 virt-manager-0.5.3-2.fc8 kernel-xen-2.6.21.7-3.fc8 x86_64 -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From paul at xelerance.com Fri Jun 27 21:56:37 2008 From: paul at xelerance.com (Paul Wouters) Date: Fri, 27 Jun 2008 17:56:37 -0400 (EDT) Subject: [Fedora-xen] xen to kvm migration question Message-ID: Hi, Although I was very happy with xen, it seems xen is losing out and kvm is the way to go. I had two migration questions that I couldn't find answers for. 1) Does kvm also run with para_virt (eg without VT capable cpu, but also just to be slightly more effecient). virt-manager only gave me a qemu option on my old amd64 cpu. 2) I boot all my xens using kernel+initrd outside a rootfs image, instead of a bootable virtual disk. Is that possible with kvm, or will I be stuck creating bootable disk images? Paul From felix.schwarz at web.de Fri Jun 27 22:26:46 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Sat, 28 Jun 2008 00:26:46 +0200 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: References: Message-ID: <48656926.8080601@web.de> Paul Wouters schrieb: > 1) Does kvm also run with para_virt (eg without VT capable cpu, but also > just to be slightly more effecient). virt-manager only gave me a qemu > option on my old amd64 cpu. While KVM can run paravirtualized Xen guests using xenner (still in development!), KVM needs always virtualization support in the CPU. fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From Alex.Upton at instinet.com Fri Jun 27 22:31:18 2008 From: Alex.Upton at instinet.com (Alex.Upton at instinet.com) Date: Fri, 27 Jun 2008 18:31:18 -0400 Subject: [Fedora-xen] AUTO: Alex Upton is out of the office (returning 06/28/2008) Message-ID: I am out of the office until 06/28/2008. I'm out of the office, please direct any support related issues to the "TSG SA" team. Any issues in need of escalation should be sent directly to Bob Sinko during this time. Thank you, Alex Note: This is an automated response to your message "Re: [Fedora-xen] xen to kvm migration question" sent on 6/27/2008 6:26:46 PM. This is the only notification you will receive while this person is away. ***************************************************************** <<>> In compliance with applicable rules and regulations, Instinet reviews and archives incoming and outgoing email communications, copies of which may be produced at the request of regulators. This message is intended only for the personal and confidential use of the recipients named above. If the reader of this email is not the intended recipient, you have received this email in error and any review, dissemination, distribution or copying is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and permanently delete the copy you received. Instinet accepts no liability for any content contained in the email, or any errors or omissions arising as a result of email transmission. Any opinions contained in this email constitute the sender's best judgment at this time and are subject to change without notice. Instinet does not make recommendations of a particular security and the information contained in this email should not be considered as a recommendation, an offer or a solicitation of an offer to buy and sell securities. ***************************************************************** -------------- next part -------------- An HTML attachment was scrubbed... URL: From avi at qumranet.com Sat Jun 28 04:10:41 2008 From: avi at qumranet.com (Avi Kivity) Date: Sat, 28 Jun 2008 07:10:41 +0300 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: References: Message-ID: <4865B9C1.5020705@qumranet.com> Paul Wouters wrote: > 2) I boot all my xens using kernel+initrd outside a rootfs image, instead > of a bootable virtual disk. Is that possible with kvm, or will I be > stuck creating bootable disk images? > > qemu provides -kernel and -initrd flags for this; however I don't know if virt-manager supports this. I find that a kernel+initrd inside the guest disk image is much more maintainable; for example 'yum update kernel' will update your guest kernel rather than having to copy files around. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. From paul at xelerance.com Sat Jun 28 05:02:46 2008 From: paul at xelerance.com (Paul Wouters) Date: Sat, 28 Jun 2008 01:02:46 -0400 (EDT) Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: <4865B9C1.5020705@qumranet.com> References: <4865B9C1.5020705@qumranet.com> Message-ID: On Sat, 28 Jun 2008, Avi Kivity wrote: > qemu provides -kernel and -initrd flags for this; however I don't know if > virt-manager supports this. So with kvm i am still using qemu? > I find that a kernel+initrd inside the guest disk image is much more > maintainable; for example 'yum update kernel' will update your guest kernel > rather than having to copy files around. I find it much easier to mount fs images, then to go hunt for offset's for mount in disk images. Also, during the xen2->xen3 and the non-PAE to PAE migrations, I liked my kernel and initrd separately :) Paul From Alistair.J.McGhie at usa.dupont.com Sat Jun 28 08:01:37 2008 From: Alistair.J.McGhie at usa.dupont.com (Alistair J McGhie) Date: Sat, 28 Jun 2008 04:01:37 -0400 Subject: [Fedora-xen] Alistair J McGhie/AE/DuPont is out of the office. Message-ID: I will be out of the office starting 06/28/2008 and will not return until 07/08/2008. I will respond to your message when I return. Alistair This communication is for use by the intended recipient and contains information that may be Privileged, confidential or copyrighted under applicable law. If you are not the intended recipient, you are hereby formally notified that any use, copying or distribution of this e-mail, in whole or in part, is strictly prohibited. Please notify the sender by return e-mail and delete this e-mail from your system. Unless explicitly and conspicuously designated as "E-Contract Intended", this e-mail does not constitute a contract offer, a contract amendment, or an acceptance of a contract offer. This e-mail does not constitute a consent to the use of sender's contact information for direct marketing purposes or for transfers of data to third parties. Francais Deutsch Italiano Espanol Portugues Japanese Chinese Korean http://www.DuPont.com/corp/email_disclaimer.html From felix.schwarz at web.de Sat Jun 28 08:56:11 2008 From: felix.schwarz at web.de (Felix Schwarz) Date: Sat, 28 Jun 2008 10:56:11 +0200 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: References: <4865B9C1.5020705@qumranet.com> Message-ID: <4865FCAB.2020001@web.de> Paul Wouters wrote: > So with kvm i am still using qemu? Yes, qemu is the heart of Xen and KVM when it comes to full virtualization. fs -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3299 bytes Desc: S/MIME Cryptographic Signature URL: From fedora.lists at burns.me.uk Sat Jun 28 09:42:03 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 28 Jun 2008 10:42:03 +0100 Subject: [Fedora-xen] Re: PCI passthrough In-Reply-To: References: Message-ID: 2008/6/27 Andy Burns : > I have an F8 dom0 (which could become a CentOS 5.2 dom0 if that would > make anything easier) I'd like an F9 domU to have access to a PCI DVB > tuner for a mythtv backend. OK, I've re-read some old threads that I'd forgotten about, and realised F9 hasn't got pci passthrough support. So to change plan, will either F8 or CentOS5.2 domU's support pci passthrough, on top of either F8 or CentOS5.2 dom0? Since this is a home machine I'm inclined to stay on Fedora rather than shift it to CentOS is possible, otherwise I don't get to play with new features. I really hope Xen options are less restricted again for F10, I don't intend this to sound like like a whine, I know people are working hard on paravirt_ops, it's just that losing options is always hard to swallow. From avi at qumranet.com Sat Jun 28 10:03:22 2008 From: avi at qumranet.com (Avi Kivity) Date: Sat, 28 Jun 2008 13:03:22 +0300 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: References: <4865B9C1.5020705@qumranet.com> Message-ID: <48660C6A.80607@qumranet.com> Paul Wouters wrote: > On Sat, 28 Jun 2008, Avi Kivity wrote: > > >> qemu provides -kernel and -initrd flags for this; however I don't know if >> virt-manager supports this. >> > > So with kvm i am still using qemu? > > Yes; qemu provides emulation for the disk, network, and display devices, etc. >> I find that a kernel+initrd inside the guest disk image is much more >> maintainable; for example 'yum update kernel' will update your guest kernel >> rather than having to copy files around. >> > > I find it much easier to mount fs images, then to go hunt for offset's for > mount in disk images. Linux 2.6.26 supports partitionable loops devices, so you can loopback mount your disk image and then mount filesystems off /dev/loop0p1, /dev/loop0p2, etc. > Also, during the xen2->xen3 and the non-PAE to PAE > migrations, I liked my kernel and initrd separately :) > kvm supports pae and nonpae regardless of how the host kernel was compiled, so you can happily run an pae guest on top of a nonpae host. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. From fedora.lists at burns.me.uk Sat Jun 28 10:36:58 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 28 Jun 2008 11:36:58 +0100 Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <1214602419.16631.35.camel@tofu.lib.ucdavis.edu> References: <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> <1214602419.16631.35.camel@tofu.lib.ucdavis.edu> Message-ID: 2008/6/27 Dale Bewley : > I then started a f9 domU in virt-manager and shut it back down. That > left me with the following. Virt-manager still lists it as "Running" but > the CPU graph is blank. I'm seeing the same F8 dom0, fully updated F9 paravirt domU fully updated after shutting down the domU virt-manager still shows its status as "Running", clicking Pause or Shutdown have no effect from a command line I get the following # virsh list --all Id Name State ---------------------------------- 0 Domain-0 running - mythbe no state # virsh shutdown mythbe libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err 'Domain cannot be shutdown') Domain mythbe is being shutdown # virsh destroy mythbe libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err "(3, 'No such process')") libvir: Xen error : failed Xen syscall ioctl 3166208 error: Failed to destroy domain mythbe # virsh start mythbe error: Domain is already active # yum list | egrep "(virt|xen).*installed" kernel-xen.x86_64 2.6.21.7-3.fc8 installed libvirt.x86_64 0.4.3-1.fc8 installed libvirt-python.x86_64 0.4.3-1.fc8 installed python-virtinst.noarch 0.300.2-4.fc8 installed virt-manager.x86_64 0.5.3-2.fc8 installed virt-viewer.x86_64 0.0.2-2.fc8 installed xen.x86_64 3.1.2-2.fc8 installed xen-libs.x86_64 3.1.2-2.fc8 installed From fedora.lists at burns.me.uk Sat Jun 28 10:47:30 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 28 Jun 2008 11:47:30 +0100 Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: References: <1502121513.597141214584203310.JavaMail.root@zebra.lib.ucdavis.edu> <1214602419.16631.35.camel@tofu.lib.ucdavis.edu> Message-ID: 2008/6/28 Andy Burns : > I'm seeing the same Just a quick follow-up, to give xm results instead of virsh results # xm list Name ID Mem VCPUs State Time(s) Domain-0 0 7544 4 r----- 96.8 mythbe 1 512 1 ------ 11.8 # xm destroy mythbe This gives no error message, but still doesn't stop the domU [root at localhost ~]# xm start mythbe This *does* restart the domU But using xm shutdown instead of virsh shutdown, virt-manager or shutting down from inside the dom0 still leaves the domU dangling. From rjones at redhat.com Sat Jun 28 15:20:50 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Sat, 28 Jun 2008 16:20:50 +0100 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: References: Message-ID: <20080628152050.GA12884@thinkpad> On Fri, Jun 27, 2008 at 05:56:37PM -0400, Paul Wouters wrote: > Although I was very happy with xen, it seems xen is losing out and kvm > is the way to go. I had two migration questions that I couldn't find > answers for. > > 1) Does kvm also run with para_virt (eg without VT capable cpu, but also > just to be slightly more effecient). virt-manager only gave me a qemu > option on my old amd64 cpu. KVM requires a hardware virt-capable CPU. These are quite common, (if your CPU was made within the last two years or so) but note there are at least two major 'generations' of virt technology in CPUs. In particular very new CPUs from both Intel and AMD support some form of virtualized page tables, which can be very beneficial. Intel describes them here: http://www.intel.com/technology/itj/2006/v10i3/1-hardware/8-virtualization-future.htm [Question: does EPT / NPT only affect 32 bit?] The second area where Xen had a traditional advantage was in paravirtualizing disk, network and a few other devices. Linux now supports something called virtio, a standard for virtualized disk and network devices, and KVM (and others) support this. Here's some more info about virtio: http://lwn.net/Articles/239238/ As for your problem with virt-manager, can you please tell us what it says in /root/.virt-manager.log and the output of 'virsh -c qemu:///system capabilities' command, and the contents of /proc/cpuinfo. > 2) I boot all my xens using kernel+initrd outside a rootfs image, instead > of a bootable virtual disk. Is that possible with kvm, or will I be > stuck creating bootable disk images? KVM has some command line options to do this, namely -kernel and -initrd. Rich. From rjones at redhat.com Sat Jun 28 15:23:38 2008 From: rjones at redhat.com (Richard W.M. Jones) Date: Sat, 28 Jun 2008 16:23:38 +0100 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: References: <4865B9C1.5020705@qumranet.com> Message-ID: <20080628152338.GB12884@thinkpad> On Sat, Jun 28, 2008 at 01:02:46AM -0400, Paul Wouters wrote: > On Sat, 28 Jun 2008, Avi Kivity wrote: > > qemu provides -kernel and -initrd flags for this; however I don't know if > > virt-manager supports this. > > So with kvm i am still using qemu? Sort of. KVM uses a fork of qemu, although the two code bases seem to be regularly synched up. Anyway, the command line arguments are broadly similar. Remember that virt-manager is using libvirt, and libvirt hides the qemu command line behind a configuration file (and also hides any differences): http://libvirt.org/formatdomain.html Rich. From fedora.lists at burns.me.uk Sat Jun 28 17:10:24 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 28 Jun 2008 18:10:24 +0100 Subject: [Fedora-xen] Re: PCI passthrough In-Reply-To: References: Message-ID: 2008/6/28 Andy Burns : > to change plan, will either F8 or CentOS5.2 domU's support pci > passthrough, on top of either F8 or CentOS5.2 dom0? I've kept F8 as dom0 and now using CentOS5.2 as domU I've added pciback.hide=(08.01.0) to grub.conf for dom0 but it seems that pciback options are not understood at boot time (due to it being a module?) I'm aware I may be able to handle preventing dom0 handling the device better in the long term with /etc/modprobe.conf, but for now I'm running a little script in dom0 rmmod saa7134 modprobe pciback SLOT=0000:08:01.0 echo -n $SLOT > /sys/bus/pci/drivers/pciback/new_slot echo -n $SLOT > /sys/bus/pci/drivers/pciback/bind I've created a new domU using the centosplus kernel to get extra V4L drivers with the following /etc/xen/ style config file memory = 1024 name = "mythbe" vif = [ 'mac=00:16:3E:76:E8:92, bridge=eth0' ] disk = [ 'phy:/dev/vgr1/lvmythroot,xvda,w' ] pci = ['08:01.0'] bootloader = "/usr/bin/pygrub" vcpus = 1 on_reboot = 'restart' on_crash = 'restart' The domU starts OK, and the pci device is present # lspci -v 00:00.0 Multimedia controller: Philips Semiconductors SAA7130 Video Broadcast Decoder (rev 01) Subsystem: Compro Technology, Inc. Videomate DVB-T200 Flags: bus master, medium devsel, latency 64, IRQ 17 Memory at febffc00 (32-bit, non-prefetchable) [size=1K] Capabilities: [40] Power Management version 1 I assume it is normal that the bus/slot/function numbers are not the same in domU as in dom0? I can load the driver for the card in the domU # lsmod | grep saa saa7134 159017 0 video_buf 59717 1 saa7134 compat_ioctl32 41793 1 saa7134 ir_kbd_i2c 42961 1 saa7134 i2c_core 56129 2 saa7134,ir_kbd_i2c ir_common 63173 2 saa7134,ir_kbd_i2c videodev 58049 1 saa7134 v4l1_compat 44613 2 saa7134,videodev v4l2_common 57153 3 saa7134,compat_ioctl32,videodev However, I am seeing an error in dmesg of domU # dmesg | grep saa saa7130/34: v4l2 driver version 0.2.14 loaded saa7130[0]: found at 0000:00:00.0, rev: 1, irq: 17, latency: 64, mmio: 0xfebffc00 saa7130[0]: subsystem: 185b:c901, board: Compro Videomate DVB-T200 [card=71,autodetected] saa7130[0]: can't ioremap() MMIO memory saa7134: probe of 0000:00:00.0 failed with error -5 Any suggestions? From dlbewley at lib.ucdavis.edu Sat Jun 28 19:20:06 2008 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Sat, 28 Jun 2008 12:20:06 -0700 (PDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: Message-ID: <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> I opened a bug and noticed the same effect for f8 domUs as well as f9 domUs while gathering info. Anyone else seeing that too? https://bugzilla.redhat.com/show_bug.cgi?id=453276 -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From fedora.lists at burns.me.uk Sat Jun 28 19:36:25 2008 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sat, 28 Jun 2008 20:36:25 +0100 Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> References: <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: 2008/6/28 Dale Bewley : > I opened a bug and noticed the same effect for f8 domUs as well as f9 domUs while gathering info. Anyone else seeing that too? I don't have an F8 domU, as mentioned I do see it with an F9 domU, also with a Win2K3 domU but don't see any problem with a centOS5.2 domU From avi at qumranet.com Sun Jun 29 13:54:53 2008 From: avi at qumranet.com (Avi Kivity) Date: Sun, 29 Jun 2008 16:54:53 +0300 Subject: [Fedora-xen] xen to kvm migration question In-Reply-To: <20080628152050.GA12884@thinkpad> References: <20080628152050.GA12884@thinkpad> Message-ID: <4867942D.2020707@qumranet.com> Richard W.M. Jones wrote: > On Fri, Jun 27, 2008 at 05:56:37PM -0400, Paul Wouters wrote: > >> Although I was very happy with xen, it seems xen is losing out and kvm >> is the way to go. I had two migration questions that I couldn't find >> answers for. >> >> 1) Does kvm also run with para_virt (eg without VT capable cpu, but also >> just to be slightly more effecient). virt-manager only gave me a qemu >> option on my old amd64 cpu. >> > > KVM requires a hardware virt-capable CPU. These are quite common, > (if your CPU was made within the last two years or so) > but note there are at least two major 'generations' of virt > technology in CPUs. In particular very new CPUs from both Intel > and AMD support some form of virtualized page tables, which can be > very beneficial. Intel describes them here: > > http://www.intel.com/technology/itj/2006/v10i3/1-hardware/8-virtualization-future.htm > > [Question: does EPT / NPT only affect 32 bit?] > No, it's applicable to both 32- and 64- bit guests. The KVM NPT implementation does not work for 32-bit nonpae hosts (it will fall back to not using NPT), so if you have a recent AMD processor and you are using a 32-bit installation, use the pae kernel for best performance. The kvm NPT and EPT implementations were introduced in Linux 2.6.26. -- error compiling committee.c: too many arguments to function From cowan at bnl.gov Mon Jun 30 15:35:17 2008 From: cowan at bnl.gov (Matt Cowan) Date: Mon, 30 Jun 2008 11:35:17 -0400 (EDT) Subject: [Fedora-xen] problems with f9 guest on f8 dom0 In-Reply-To: <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> References: <1309857660.613961214680806547.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: On Sat, 28 Jun 2008, Dale Bewley wrote: > I opened a bug and noticed the same effect for f8 domUs as well as > f9 domUs while gathering info. Anyone else seeing that too? ... I haven't had any problems with f8 domU. My usual symptom is slightly different than what you seem to experience. When I shutdown an f9 domU, resource display in virt-manager hangs for me, usually displaying the problem domU as shutdown, and no longer updates the cpu usage plots for remaining domu or dom0; although the virt-manager interface itself (buttons,menus) seems responsive, and more painfully, restarting xend and/or libvirtd doesn't help :( I do have *one* f9 domU on one of our test boxes installed by someone else in my group, and shutting that one down seems to more closely resemble your symptoms; the cpu charts in virt-manager keep running, domU remains listed as running, but using no resources, but if I disconnect and try to reconnect, or restart virt-manager; it can't connect, and restaring xend and/or libvirtd doesn't help :( Looks like most of you responding to this thread are using x86_64; I'm just running i686. -matt