From info at vsic.net Sun Jul 1 15:29:00 2007 From: info at vsic.net (Frank Morane) Date: Sun, 01 Jul 2007 09:29:00 -0600 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <46857B4C.5010102@sbcglobal.net> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> Message-ID: <4687C83C.6030501@vsic.net> Mike wrote: > Frank Morane wrote: > >> Hi all, >> >> I just did a fresh install of FC7 to see if xen would work out of the box. >> Dom0 boots (with errors in the log - see below) and some Centos 4.4 domU >> boots but are unseable (after recompiling the initrd image with the xen >> driver preloaded) up to the famous long lasting error message "4gb seg >> fixup". At that point it is dead >> >> My question: what id the status of Xen for Fc7? Will it ever fly? >> Is there a Linux distro that works out of the box ? >> > > Hmm. I'm running a F7 dom0 with the following domUs: NetBSD 3.1, FC6, > F7, and a very shaky Solaris 10 b44. > > Xen 3.1 + F7 seems rock solid. > > >> The last usable version I saw was for FC5 as of May 2006, after that all >> version were badly broken and never fixed, I tested ALL of them for >> fc5/fc6 and not a single one worked as published. Only home brewed >> compiled version would work after weeks of trial and error. >> >> Here what the log says from my out of the box install: >> >> >> > > Are you sure you're not missing the domU's console? I noticed that with > at least the FC6 and F7 domUs, the boot output starts on the serial > console, then transfers to the graphical console. I'm not familiar with > the Centos domU's behavior, but it might be something to check. > > Hi, Ok I did add the console as explained in another post BUT it did not solve the issue: I added this line in /etc/inittab # Required by Xen co:2345:respawn:/sbin/mingetty console I still can't get a console BUT I can access via ssh the booted domU; then I saw nash using 95% of the cpu and I killed it. The problem is that this is far from what I want since I cannot access the domU via a console, when I try I get these: printk: 185 messages suppressed. 4gb seg fixup, process ntpd (pid 1230), cs:ip 73:008ac17a printk: 17121 messages suppressed. 4gb seg fixup, process ntpd (pid 1230), cs:ip 73:008ac17a printk: 183 messages suppressed. 4gb seg fixup, process ntpd (pid 1230), cs:ip 73:008ac17a and yes I have the "hwcap 0 nosegneg" in /etc/ld.so.conf. There is critical information missing to get older generation (Centos 4) domU booting on late FC5, FC6 and FC7. Anyway, any additional hints will be appreciated. Regards, -- Frank Morane (Free Thinker) http://www.adventuresinlegalland.com http://www.lysanderspooner.org http://thoreau.eserver.org From rjones at redhat.com Mon Jul 2 08:47:50 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 02 Jul 2007 09:47:50 +0100 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <4686713F.2050303@vsic.net> References: <46854E4C.8030107@vsic.net> <46855E4C.5010905@redhat.com> <4686713F.2050303@vsic.net> Message-ID: <4688BBB6.2060506@redhat.com> Frank Morane wrote: > Richard W.M. Jones wrote: >> Frank Morane wrote: >>> Hi all, >>> >>> I just did a fresh install of FC7 to see if xen would work out of the >>> box. >>> Dom0 boots (with errors in the log - see below) and some Centos 4.4 >>> domU boots but are unseable (after recompiling the initrd image with >>> the xen driver preloaded) up to the famous long lasting error message >>> "4gb seg fixup". At that point it is dead >> >> I don't understand what you mean by "dead". Does the dom0 hang? > No, just the domU. It does nothing more once the "4gb seg fixup" start > spiting. If you have a directory /lib/tls in the guest, try moving it out of the way before the guest boots. You could also try: http://www.redhat.com/archives/fedora-xen/2006-November/msg00142.html See also section 2.5.3 here: http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html#tex2html6 Let us know if any of this works. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Mon Jul 2 08:59:30 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 02 Jul 2007 09:59:30 +0100 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <4687C83C.6030501@vsic.net> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> <4687C83C.6030501@vsic.net> Message-ID: <4688BE72.3020308@redhat.com> Frank Morane wrote: > I still can't get a console BUT I can access via ssh the booted domU; > then I saw nash using 95% of the cpu and I killed it. > > The problem is that this is far from what I want since I cannot access > the domU via a console, when I try I get these: > > printk: 185 messages suppressed. > 4gb seg fixup, process ntpd (pid 1230), cs:ip 73:008ac17a [...] > and yes I have the "hwcap 0 nosegneg" in /etc/ld.so.conf. > There is critical information missing to get older generation (Centos 4) > domU booting on late FC5, FC6 and FC7. nosegneg only works if the kernel supports it, and as far as I can find out, this capability was only added relatively recently (earlier this year). http://www.uwsg.iu.edu/hypermail/linux/kernel/0704.2/2872.html In addition, this flags affects how (or rather, which) glibc is dynamically linked in to the binary. /sbin/nash is statically linked, but /usr/sbin/ntpd is dynamically linked (at least on FC6, and I expect on FC5 too). So if you're getting the above messages concerning ntpd, then it sounds a lot like you're still linking to a version of glibc which is using negative offsets with segment register overrides, which is something that Xen has to emulate, slowly. As to how to fix this: In Debian the fix is well-known. Rename the directory /lib/tls (on 64 bit Fedora: /lib64/tls) as /lib/tls.disabled, and reboot the domU. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Mon Jul 2 09:01:06 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 02 Jul 2007 10:01:06 +0100 Subject: [Fedora-xen] 64bit Hypervisor on 32bit OS In-Reply-To: <262023.82747.qm@web88304.mail.re4.yahoo.com> References: <262023.82747.qm@web88304.mail.re4.yahoo.com> Message-ID: <4688BED2.20405@redhat.com> thewird wrote: > I've been reading about how to make Xen show more then > 16GB of ram and still support 32bit but so far all my > attempts have not worked. FC7 was supposed to be able > to run 32bit guests on its 64bit OS but because of a > feature freeze, this was not possible even though it > still says you can do it in the release notes which I > find ridiculous. Are you sure? FC7 runs 32 bit fullvirt guests fine for me (on 64 bit hardware/hypervisor). I didn't yet try to run a 32 bit paravirt guest though. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Mon Jul 2 13:50:25 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 02 Jul 2007 14:50:25 +0100 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <4688BE72.3020308@redhat.com> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> <4687C83C.6030501@vsic.net> <4688BE72.3020308@redhat.com> Message-ID: <468902A1.7060108@redhat.com> Also you might want to read through and add something to these bugs: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243756 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=244730 Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From songtao.liu at mytum.de Mon Jul 2 14:48:19 2007 From: songtao.liu at mytum.de (Songtao Liu) Date: Mon, 02 Jul 2007 16:48:19 +0200 Subject: [Fedora-xen] VCPU number configuration Message-ID: Hi as when I installed the XenU I initialized the VCPU=1, is it possible to change VCPU=2 Linux localhost.localdomain 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux As far as I know from help, it seems impossible, see the last paragraph. But I dont want to install a new guest :( vcpu-set domain-id vcpu-count Enables the vcpu-count virtual CPUs for the domain in question. Like mem-set, this command can only allocate up to the maximum virtual CPU count configured at boot for the domain. If the vcpu-count is smaller than the current number of active VCPUs, the highest number VCPUs will be hotplug removed. This may be important for pinning purposes. Attempting to set the VCPUs to a number larger than the initially configured VCPU count is an error. Trying to set VCPUs to < 1 will be quietly ignored. Thanks Songtao From email at jasonkohles.com Mon Jul 2 15:10:44 2007 From: email at jasonkohles.com (Jason Kohles) Date: Mon, 2 Jul 2007 11:10:44 -0400 Subject: [Fedora-xen] VCPU number configuration In-Reply-To: References: Message-ID: On Jul 2, 2007, at 10:48 AM, Songtao Liu wrote: > Hi > > as when I installed the XenU I initialized the VCPU=1, is it > possible to change VCPU=2 > > Linux localhost.localdomain 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar > 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux > > As far as I know from help, it seems impossible, see the last > paragraph. But I dont want to install a new guest :( > > vcpu-set domain-id vcpu-count > Enables the vcpu-count virtual CPUs for the domain in > question. Like mem-set, this command can only allocate up to the > maximum > virtual CPU count configured at boot for the domain. > > If the vcpu-count is smaller than the current number of > active VCPUs, the highest number VCPUs will be hotplug removed. > This may > be important for pinning purposes. > > Attempting to set the VCPUs to a number larger than the > initially configured VCPU count is an error. Trying to set VCPUs > to < 1 > will be quietly ignored. > vcpu-set is for changing the number of vcpus while the guest is running (using hotplug support), if you change it in the configuration while the guest is shut down, then this doesn't apply. You don't have to install a new guest, you just have to reboot. -- Jason Kohles email at jasonkohles.com http://www.jasonkohles.com/ "A witty saying proves nothing." -- Voltaire From thewird at yahoo.com Mon Jul 2 20:21:18 2007 From: thewird at yahoo.com (thewird) Date: Mon, 2 Jul 2007 16:21:18 -0400 (EDT) Subject: [Fedora-xen] 64bit Hypervisor on 32bit OS In-Reply-To: <4688BED2.20405@redhat.com> Message-ID: <685606.16565.qm@web88302.mail.re4.yahoo.com> What files did you replace to convert the hypervisor to 64bit? thewird --- "Richard W.M. Jones" wrote: > thewird wrote: > > I've been reading about how to make Xen show more > then > > 16GB of ram and still support 32bit but so far all > my > > attempts have not worked. FC7 was supposed to be > able > > to run 32bit guests on its 64bit OS but because of > a > > feature freeze, this was not possible even though > it > > still says you can do it in the release notes > which I > > find ridiculous. > > Are you sure? FC7 runs 32 bit fullvirt guests fine > for me (on 64 bit > hardware/hypervisor). I didn't yet try to run a 32 > bit paravirt guest > though. > > Rich. > > -- > Emerging Technologies, Red Hat - > http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, > 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. > Registered in > England and Wales under Company Registration No. > 03798903 > From m3freak at thesandhufamily.ca Tue Jul 3 04:27:54 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Tue, 03 Jul 2007 00:27:54 -0400 Subject: [Fedora-xen] Not seeing all RAM Message-ID: <1183436874.6567.9.camel@krs> Hello, I'm running a FC6 dom0, with kernel version, kernel-xen-2.6.19-1.2895.fc6 on a Dell PowerEdge 1600SC. I just upgraded it from 1 GB (2 x 512 MB modules) to 3 GB (2 x 1 GB + 2 x 512 MB). The BIOS sees all of the ram, but kernel does not. All I see when I run free is this: total used free shared buffers cached Mem: 2454528 207876 2246652 0 11032 47380 -/+ buffers/cache: 149464 2305064 Swap: 524280 0 524280 It looks like 512 MB is missing. Here's a bit more detail from dmesg: Memory: 2874124k/2987900k available (2166k kernel code, 104532k reserved, 1100k data, 184k init, 2242436k highmem) So, what happened to the rest of the RAM? I should add that the server is updated with the latest firmware and BIOS. BTW, I appear to be having problems with one of my domUs now too (after the ram upgrade). A PCI device I was handing to the domU is now causing the domU kernel to panic, crashing the domU. I'll try to get a copy of the error message. Any help appreciated. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 00:17:27 up 10:25, 2 users, load average: 0.68, 0.43, 0.26 From itamar at ispbrasil.com.br Tue Jul 3 04:42:35 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Tue, 3 Jul 2007 01:42:35 -0300 Subject: [Fedora-xen] Not seeing all RAM References: <1183436874.6567.9.camel@krs> Message-ID: <000801c7bd2c$959662a0$fe01a8c0@ispbrasil> try a new xen kernel run a yum update -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "Kanwar Ranbir Sandhu" To: Sent: Tuesday, July 03, 2007 1:27 AM Subject: [Fedora-xen] Not seeing all RAM > Hello, > > I'm running a FC6 dom0, with kernel version, > kernel-xen-2.6.19-1.2895.fc6 on a Dell PowerEdge 1600SC. I just > upgraded it from 1 GB (2 x 512 MB modules) to 3 GB (2 x 1 GB + 2 x 512 > MB). The BIOS sees all of the ram, but kernel does not. All I see when > I run free is this: > > total used free shared buffers > cached > Mem: 2454528 207876 2246652 0 11032 > 47380 > -/+ buffers/cache: 149464 2305064 > Swap: 524280 0 524280 > > It looks like 512 MB is missing. > > Here's a bit more detail from dmesg: > > Memory: 2874124k/2987900k available (2166k kernel code, 104532k > reserved, 1100k data, 184k init, 2242436k highmem) > > So, what happened to the rest of the RAM? I should add that the server > is updated with the latest firmware and BIOS. > > BTW, I appear to be having problems with one of my domUs now too (after > the ram upgrade). A PCI device I was handing to the domU is now causing > the domU kernel to panic, crashing the domU. I'll try to get a copy of > the error message. > > Any help appreciated. > > Regards, > > Ranbir > -- > Kanwar Ranbir Sandhu > Linux 2.6.20-1.2944.fc6 i686 GNU/Linux > 00:17:27 up 10:25, 2 users, load average: 0.68, 0.43, 0.26 > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From rjones at redhat.com Tue Jul 3 09:08:28 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 03 Jul 2007 10:08:28 +0100 Subject: [Fedora-xen] 64bit Hypervisor on 32bit OS In-Reply-To: <685606.16565.qm@web88302.mail.re4.yahoo.com> References: <685606.16565.qm@web88302.mail.re4.yahoo.com> Message-ID: <468A120C.7000805@redhat.com> thewird wrote: > What files did you replace to convert the hypervisor > to 64bit? I'm just using a 64 bit F7 as the dom0. We must be talked at crossed purposes now. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Tue Jul 3 09:17:32 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 03 Jul 2007 10:17:32 +0100 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <1183436874.6567.9.camel@krs> References: <1183436874.6567.9.camel@krs> Message-ID: <468A142C.2000608@redhat.com> Kanwar Ranbir Sandhu wrote: > Hello, > > I'm running a FC6 dom0, with kernel version, > kernel-xen-2.6.19-1.2895.fc6 on a Dell PowerEdge 1600SC. I just > upgraded it from 1 GB (2 x 512 MB modules) to 3 GB (2 x 1 GB + 2 x 512 > MB). If this still happens after you've updated to the latest FC6 (IIRC, kernel-xen 2.6.20-1.2952) then please file a bug here: https://bugzilla.redhat.com/bugzilla/index.cgi There are various problems with Xen & memory, although they don't normally happen below the 4 GB boundary (and mostly happen for people with absolutely enormous amounts of memory, like > 60 GB). We'll try and fix them. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From luc.maignan at winxpert.com Tue Jul 3 10:47:16 2007 From: luc.maignan at winxpert.com (Luc MAIGNAN) Date: Tue, 03 Jul 2007 12:47:16 +0200 Subject: [Fedora-xen] XEN error with FC7 Message-ID: <468A2934.3010803@winxpert.com> Hi, I didn't succeed to install an FC7 guest on a FC7 host using virt-install with nographics (the same operation with a FC6 was successfull). In the installation process, I've got first an error : libvir: Xen Daemon error : GET operation failed: and after a while, the installation hangs up. ANy idea please ? BR From thewird at yahoo.com Tue Jul 3 12:21:47 2007 From: thewird at yahoo.com (thewird) Date: Tue, 3 Jul 2007 08:21:47 -0400 (EDT) Subject: [Fedora-xen] libvir: Xen Daemon error : GET/POST operation failed: Message-ID: <293074.5694.qm@web88305.mail.re4.yahoo.com> When I try to install a guest on 64bit FC7 I get the error below. Any ideas? # virt-install Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. yes What is the name of your virtual machine? fedora How much RAM should be allocated (in megabytes)? 500 What would you like to use as the disk (path)? /dev/vg01/LVfedora Would you like to enable graphics support? (yes or no) no What is the virtual CD image, CD device or install location? http://ftp.usf.edu/pub/fedora/linux/core/6/i386/os/ Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving Fedora... 100% |=========================| 849 B 00:00 Retrieving boot.iso... 100% |=========================| 7.9 MB 00:12 libvir: Xen Daemon error : GET operation failed: libvir: Xen Daemon error : POST operation failed: (xend.err 'Device 5632 (vbd) could not be connected. losetup -r /dev/loop0 /var/lib/xen/virtinst-boot.iso.Kkp7nL failed') Traceback (most recent call last): File "/usr/sbin/virt-install", line 629, in main() File "/usr/sbin/virt-install", line 578, in main dom = guest.start_install(conscb,progresscb) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 649, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 666, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirt.libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 5632 (vbd) could not be connected. losetup -r /dev/loop0 /var/lib/xen/virtinst-boot.iso.Kkp7nL failed') From m3freak at thesandhufamily.ca Tue Jul 3 14:07:21 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Tue, 03 Jul 2007 10:07:21 -0400 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <468A142C.2000608@redhat.com> References: <1183436874.6567.9.camel@krs> <468A142C.2000608@redhat.com> Message-ID: <1183471641.6567.14.camel@krs> On Tue, 2007-07-03 at 10:17 +0100, Richard W.M. Jones wrote: > If this still happens after you've updated to the latest FC6 (IIRC, > kernel-xen 2.6.20-1.2952) then please file a bug here: > https://bugzilla.redhat.com/bugzilla/index.cgi Some improvement, but still missing RAM: [root at xenmaster ~]# free total used free shared buffers cached Mem: 2716672 211452 2505220 0 11056 48608 -/+ buffers/cache: 151788 2564884 Swap: 524280 0 524280 [root at xenmaster ~]# grep -i memory /var/log/dmesg Memory: 2874636k/2987900k available (2135k kernel code, 104060k reserved, 1130k data, 176k init, 2242436k highmem) The BIOS reports 3072 MB. I'll file that bug report. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 10:06:21 up 20:14, 2 users, load average: 0.18, 0.20, 0.23 From berrange at redhat.com Tue Jul 3 14:23:38 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 3 Jul 2007 15:23:38 +0100 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <1183436874.6567.9.camel@krs> References: <1183436874.6567.9.camel@krs> Message-ID: <20070703142338.GD8410@redhat.com> On Tue, Jul 03, 2007 at 12:27:54AM -0400, Kanwar Ranbir Sandhu wrote: > Hello, > > I'm running a FC6 dom0, with kernel version, > kernel-xen-2.6.19-1.2895.fc6 on a Dell PowerEdge 1600SC. I just > upgraded it from 1 GB (2 x 512 MB modules) to 3 GB (2 x 1 GB + 2 x 512 > MB). The BIOS sees all of the ram, but kernel does not. All I see when > I run free is this: > > total used free shared buffers > cached > Mem: 2454528 207876 2246652 0 11032 > 47380 > -/+ buffers/cache: 149464 2305064 > Swap: 524280 0 524280 > > It looks like 512 MB is missing. Let me guest - you are running a 32-bit kernel on the machine ? If so the problem is likely that the BOIS is remapping a portion of memory above the 4 GB mark, to make room for PCI device DMA zones. A 32-bit kernel though can only access physical addrs upto 4 GB, so it can't see the remapped memory. > BTW, I appear to be having problems with one of my domUs now too (after > the ram upgrade). A PCI device I was handing to the domU is now causing > the domU kernel to panic, crashing the domU. I'll try to get a copy of > the error message. PCI device mapping to DomUs is insanely fragile, whether it works or not is mostly luck. In this case since you added more memory, the locaiton of the PCI device's DMA zone probably changed and by (bad) luck is no longer accessible to the DomU or something like that. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From m3freak at thesandhufamily.ca Tue Jul 3 14:42:40 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Tue, 03 Jul 2007 10:42:40 -0400 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <20070703142338.GD8410@redhat.com> References: <1183436874.6567.9.camel@krs> <20070703142338.GD8410@redhat.com> Message-ID: <1183473760.6567.21.camel@krs> On Tue, 2007-07-03 at 15:23 +0100, Daniel P. Berrange wrote: > Let me guest - you are running a 32-bit kernel on the machine ? If so > the problem is likely that the BOIS is remapping a portion of memory > above the 4 GB mark, to make room for PCI device DMA zones. A 32-bit > kernel though can only access physical addrs upto 4 GB, so it can't > see the remapped memory. I'm aware of that, but in my case it doesn't make sense: the server only has 3 GB of RAM. The kernel just doesn't see all of it. I was using kernel-xen-2.6.19-1.2895.fc6 and about 512 MB were missing. After upgrading to kernel-xen-2.6.20-1.2962.fc6, the kernel can see more memory, but I'm still missing about 256 MB. I'm going to open a new bug report for this. > PCI device mapping to DomUs is insanely fragile, whether it works or not > is mostly luck. In this case since you added more memory, the locaiton of > the PCI device's DMA zone probably changed and by (bad) luck is no longer > accessible to the DomU or something like that. That's what I figured, though I don't know all of the details. However, with the new kernel being able to see more of the 3 GB, the domU is working again. The pci device I'm hiding from dom0 is being properly handed to the domU. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2944.fc6 i686 GNU/Linux 10:42:35 up 20:50, 2 users, load average: 2.15, 2.16, 1.45 From songtao.liu at mytum.de Tue Jul 3 14:56:17 2007 From: songtao.liu at mytum.de (Songtao Liu) Date: Tue, 03 Jul 2007 16:56:17 +0200 Subject: [Fedora-xen] VCPUs >=2 will lead to failure of guest boot Message-ID: Hi, As no one answer in list of xensource, I turn to here :) still the question about VCPUs. When I set VCPU >= 2, then I can not boot the guest.(the guest kernel is SMP) Guest is 2.6.20-1.2952.fc6 When using Guest Winxp (VCPUs=2) it is OK. How can I make it run with 2 VCPU :( ??? here is some other info: cpuinfo and xen configuration file. Thanks in advance Songtao \Linux localhost.localdomain 2.6.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686 i686 i386 GNU/Linux CPUinfo: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping : 6 cpu MHz : 2168.162 cache size : 4096 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 5422.34 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz stepping : 6 cpu MHz : 2168.162 cache size : 4096 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc up pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 5422.34 # Automatically generated xen config file name = "system2" builder = "hvm" memory = "256" disk = [ 'file:/home/songtao/Xen_Guests/Fedora6,hda,w', ] vif = [ 'type=ioemu, mac=00:16:3e:51:be:52, bridge=xenbr0', ] uuid = "261877a2-1d16-8684-a66b-07170a381d6b" device_model = "/usr/lib/xen/bin/qemu-dm" kernel = "/usr/lib/xen/boot/hvmloader" vnc=1 vncunused=1 apic=1 acpi=1 pae=1 vcpus=2 serial = "pty" # enable serial console on_reboot = 'restart' on_crash = 'restart' xend.log: [2007-07-03 16:17:11 xend 2762] DEBUG (balloon:127) Balloon: 279472 KiB free; need 279144; done. [2007-07-03 16:17:11 xend 2762] INFO (image:136) buildDomain os=hvm dom=1 vcpus=2 [2007-07-03 16:17:11 xend 2762] DEBUG (image:282) dom = 1 [2007-07-03 16:17:11 xend 2762] DEBUG (image:283) image = /usr/lib/xen/boot/hvmloader [2007-07-03 16:17:11 xend 2762] DEBUG (image:284) store_evtchn = 1 [2007-07-03 16:17:11 xend 2762] DEBUG (image:285) memsize = 256 [2007-07-03 16:17:11 xend 2762] DEBUG (image:286) vcpus = 2 [2007-07-03 16:17:11 xend 2762] DEBUG (image:287) pae = 1 [2007-07-03 16:17:11 xend 2762] DEBUG (image:288) acpi = 1 [2007-07-03 16:17:11 xend 2762] DEBUG (image:289) apic = 1 [2007-07-03 16:17:11 xend 2762] DEBUG (image:435) hvm shutdown watch registered [2007-07-03 16:17:11 xend 2762] DEBUG (blkif:24) exception looking up device number for hda: [Errno 2] No such file or directory: '/dev/hda' [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:110) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/1/768'} to /local/domain/1/device/vbd/768. [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:112) DevController: writing {'domain': 'winxp', 'frontend': '/local/domain/1/device/vbd/768', 'dev': 'hda', 'state': '1', 'params': '/home/songtao/Xen_Guests/winxp', 'mode': 'w', 'online': '1', 'frontend-id': '1', 'type': 'file'} to /local/domain/0/backend/vbd/1/768. [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:110) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/domain/0/backend/vif/1/0'} to /local/domain/1/device/vif/0. [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:112) DevController: writing {'bridge': 'xenbr0', 'domain': 'winxp', 'handle': '0', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/1/device/vif/0', 'mac': '00:16:3e:48:1a:3e', 'online': '1', 'frontend-id': '1', 'type': 'ioemu'} to /local/domain/0/backend/vif/1/0. [2007-07-03 16:17:11 xend 2762] INFO (image:418) spawning device models: /usr/lib/xen/bin/qemu-dm ['/usr/lib/xen/bin/qemu-dm', '-d', '1', '-m', '256', '-boot', 'c', '-serial', 'pty', '-vcpus', '2', '-acpi', '-domain-name', 'winxp', '-net', 'nic,vlan=1,macaddr=00:16:3e:48:1a:3e,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vncunused', '-vnclisten', '127.0.0.1'] [2007-07-03 16:17:11 xend 2762] INFO (image:420) device model pid: 3708 [2007-07-03 16:17:11 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:715) Storing VM details: {'shadow_memory': '4', 'uuid': '6d5f109d-cde9-aa57-65d8-48f824a06166', 'on_reboot': 'restart', 'start_time': '1183472231.33', 'on_poweroff': 'destroy', 'name': 'winxp', 'xend/restart_count': '0', 'vcpus': '2', 'vcpu_avail': '3', 'memory': '256', 'on_crash': 'restart', 'image': "(hvm (kernel /usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm) (pae 1) (vcpus 2) (boot c) (serial pty) (vnc 1) (vncunused 1) (display :0.0) (xauthority /root/.xauthP1IB4T) (acpi 1) (apic 1) (vncpasswd 'None'))", 'maxmem': '256'} [2007-07-03 16:17:11 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:750) Storing domain details: {'console/port': '2', 'name': 'winxp', 'console/limit': '1048576', 'vm': '/vm/6d5f109d-cde9-aa57-65d8-48f824a06166', 'domid': '1', 'cpu/0/availability': 'online', 'memory/target': '262144', 'store/ring-ref': '19693', 'cpu/1/availability': 'online', 'store/port': '1'} [2007-07-03 16:17:11 xend 2762] DEBUG (image:458) hvm_shutdown fired, shutdown reason=None [2007-07-03 16:17:11 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:143) Waiting for devices vif. [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:149) Waiting for 0. [2007-07-03 16:17:11 xend 2762] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:486) hotplugStatusCallback 1. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices usb. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vbd. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:149) Waiting for 768. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vbd/1/768/hotplug-status. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:486) hotplugStatusCallback 1. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices irq. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vkbd. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vfb. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices pci. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices ioports. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices tap. [2007-07-03 16:17:12 xend 2762] DEBUG (DevController:143) Waiting for devices vtpm. [2007-07-03 16:17:12 xend 2762] INFO (XendDomain:370) Domain winxp (1) unpaused. [2007-07-03 16:17:59 xend 2762] DEBUG (image:458) hvm_shutdown fired, shutdown reason=halt [2007-07-03 16:17:59 xend.XendDomainInfo 2762] INFO (XendDomainInfo:899) Domain has shutdown: name=winxp id=1 reason=halt. [2007-07-03 16:17:59 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=1 [2007-07-03 16:17:59 xend.XendDomainInfo 2762] DEBUG (XendDomainInfo:1471) XendDomainInfo.destroyDomain(1) [2007-07-03 16:17:59 xend 2762] DEBUG (image:447) hvm shutdown watch unregistered From itamar at ispbrasil.com.br Tue Jul 3 17:03:43 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Tue, 3 Jul 2007 14:03:43 -0300 Subject: [Fedora-xen] Not seeing all RAM References: <1183436874.6567.9.camel@krs> <20070703142338.GD8410@redhat.com> <1183473760.6567.21.camel@krs> Message-ID: <00fe01c7bd94$1e2e51b0$fe01a8c0@ispbrasil> with non xen kernel are you able to see all amount of memory ? have you take a look on your bios to check if your video card is not using your memory ? -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 ----- Original Message ----- From: "Kanwar Ranbir Sandhu" To: "Daniel P. Berrange" Cc: Sent: Tuesday, July 03, 2007 11:42 AM Subject: Re: [Fedora-xen] Not seeing all RAM > On Tue, 2007-07-03 at 15:23 +0100, Daniel P. Berrange wrote: >> Let me guest - you are running a 32-bit kernel on the machine ? If so >> the problem is likely that the BOIS is remapping a portion of memory >> above the 4 GB mark, to make room for PCI device DMA zones. A 32-bit >> kernel though can only access physical addrs upto 4 GB, so it can't >> see the remapped memory. > > I'm aware of that, but in my case it doesn't make sense: the server only > has 3 GB of RAM. The kernel just doesn't see all of it. > > I was using kernel-xen-2.6.19-1.2895.fc6 and about 512 MB were missing. > After upgrading to kernel-xen-2.6.20-1.2962.fc6, the kernel can see more > memory, but I'm still missing about 256 MB. > > I'm going to open a new bug report for this. > >> PCI device mapping to DomUs is insanely fragile, whether it works or not >> is mostly luck. In this case since you added more memory, the locaiton of >> the PCI device's DMA zone probably changed and by (bad) luck is no longer >> accessible to the DomU or something like that. > > That's what I figured, though I don't know all of the details. However, > with the new kernel being able to see more of the 3 GB, the domU is > working again. The pci device I'm hiding from dom0 is being properly > handed to the domU. > > Regards, > > Ranbir > -- > Kanwar Ranbir Sandhu > Linux 2.6.20-1.2944.fc6 i686 GNU/Linux > 10:42:35 up 20:50, 2 users, load average: 2.15, 2.16, 1.45 > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From rstory-l at 2006.revelstone.com Tue Jul 3 18:09:35 2007 From: rstory-l at 2006.revelstone.com (Robert Story) Date: Tue, 3 Jul 2007 14:09:35 -0400 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <4685BD52.2030601@itsbeen.sent.com> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> <4685BD52.2030601@itsbeen.sent.com> Message-ID: <200707031902.l63J2HEA000512@mx1.redhat.com> On Fri, 29 Jun 2007 19:17:54 -0700 FCXen wrote: F> > Are you sure you're not missing the domU's console? I noticed that with F> > at least the FC6 and F7 domUs, the boot output starts on the serial F> > console, then transfers to the graphical console. I'm not familiar with F> > the Centos domU's behavior, but it might be something to check. F> F> I think this is a big problem, it happened to me.* Unfortunately, I was trying F> on FC6 Test 2/3 so I was told to get the F7 release version and try that. F> F> There is no clear step by step how to on how to build GUI-less domUs for FC6 F> or F7 I simply edit the xen config file and comment out the virtual frame buffer line (vfb = [...]), and it works fine w/out a GUI... From dlbewley at lib.ucdavis.edu Tue Jul 3 19:46:33 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Tue, 3 Jul 2007 12:46:33 -0700 (PDT) Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <4685BD52.2030601@itsbeen.sent.com> Message-ID: <1190534330.46171183491993975.JavaMail.root@zebra.lib.ucdavis.edu> > And kudos to those running everything under the sun on an F7 dom0, but > can > someone give those of us who aren't in the secret club a break and > publish a > full step-by-step of how you did it and some config files/settings. Wrapper for virt-install worked on F7 dom0 for FC6 and F7 domU http://bewley.net/linux/fedora/xen/mkxen.sh > Did you > use a copy of the DVD** exactly as it was or change some magical files > after I created a mirror by rsyncing another site. DVD copy should work fine. > copying to disk? Has GUI-less domU installs or installs using a > manually > assigned IPv4 address ever worked for anyone using an F7 dom0, if so > how? I used DHCP. > ** I also didn't know that a remote repo would fail during domU > installs until > someone mentioned it among some other attempts at troubleshooting my > install > failures. My FC6 install was fine against my personal repo over HTTP. My F7 was fine, but quite quite slow. I could watch the http access log and tell it was still working though. My F7 kickstart file which hasn't been optimized but basically it looks like this: ## upgrade or install? install # upgrade ## comment out if you want the machine to wait for you to reboot manually reboot ## install source on URL or CDROM? url --url http://ks/fedora/linux/releases/7/Fedora/x86_64/os #cdrom ## use text mode install since i'll be spying on the serial console text skipx lang en_US.UTF-8 keyboard us timezone America/Los_Angeles ## network setup network --device eth0 --bootproto dhcp #network --device eth1 --onboot no --bootproto dhcp ## we'll redo firewalling by hand later firewall --enabled --port=22:tcp ## this could be annoying for now so leave it off selinux --disabled authconfig --enableshadow --enablemd5 ## change this after install rootpw something ################################################################################ # Setup the disk drives. # Clear the Master Boot Record zerombr # nuke all existing partitions clearpart --all --initlabel # raw partition for boot and a LVM physical volume on remainder part /boot --fstype ext3 --size=100 part pv.01 --size=1 --grow # LVM setup on physical volume volgroup VG0 pv.01 logvol / --fstype=ext3 --name=LVRoot --vgname=VG0 --size=512 logvol /var --fstype=ext3 --name=LVVar --vgname=VG0 --size=1024 logvol /var/www --fstype=ext3 --name=LVVarWww --vgname=VG0 --size=2048 logvol /usr --fstype=ext3 --name=LVUsr --vgname=VG0 --size=2048 logvol /home --fstype=ext3 --name=LVHome --vgname=VG0 --size=100 logvol swap --fstype swap --name=LVSwap --vgname=VG0 --size=512 # install grub bootloader --location=mbr --driveorder=xvda --append="console=xvc0" %packages vim-enhanced ################################################################################ # Final Configuration %post --nochroot cp /tmp/ks.cfg /mnt/sysimage/root/install-ks.cfg cp /proc/cmdline /mnt/sysimage/root/install-cmdline %post echo xvc0 >> /etc/securetty # this was done auto on FC6 domU echo "co:2345:respawn:/sbin/agetty xvc0 9600 vt100-nav" >> /etc/inittab # we'll use these values in the extended final config EMAIL=root at mail DIST=f7 MAC_ADDR=`ifconfig eth0 | grep HWaddr | \ sed -e 's/^.*HWaddr \([A-Fa-f0-9:]*\).*$/\1/; s/:/-/g;'` # put /tmp on swap cuz it's fast and junk goes away on reboot echo -e "none\t\t\t/tmp\t\t\ttmpfs\tdefaults\t0 0" >> /etc/fstab # setup root's profile echo 'alias vi=vim' >> /root/.bash_profile # I want to know about things... echo -e "root:\t\t$EMAIL" >> /etc/aliases newaliases # tell daddy we are all done cat /root/install.log /root/install-ks.cfg \ | mail -s "${DIST} ks install ${MAC_ADDR}" $EMAIL -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From mc-al34luc at sbcglobal.net Wed Jul 4 04:48:31 2007 From: mc-al34luc at sbcglobal.net (Mike) Date: Tue, 03 Jul 2007 21:48:31 -0700 Subject: [Fedora-xen] XEN error with FC7 In-Reply-To: <468A2934.3010803@winxpert.com> References: <468A2934.3010803@winxpert.com> Message-ID: <468B269F.403@sbcglobal.net> Luc MAIGNAN wrote: > Hi, > > I didn't succeed to install an FC7 guest on a FC7 host using > virt-install with nographics (the same operation with a FC6 was > successfull). > > In the installation process, I've got first an error : libvir: Xen > Daemon error : GET operation failed: > > and after a while, the installation hangs up. > > ANy idea please ? Greetings, Luc, Two things: 1) Your dom0 F7 machine can't be runing Selinux in Enforcing mode. There's a denial related to udevd trying to load a kernel module that's a problem. You can confirm this by looking for avc messages in /var/log/messages if you don't have auditd loaded, or /var/log/audit/audit.log if you do. I reported this problem to the Selinux people so they're aware of it. Edit /etc/selinux/conf and set SELINUX to permissive. 2) Your guest may very well be running, despite the nographics setting. If you have a head on your dom0 machine, try turning on the --vnc option and see what happens. If your dom0 is headless, redirect any X output to some other machine that has a head (set DISPLAY, xhost, etc). Run your virt-install, and see if the graphical console of your guest pops up. It did for me, even though I didn't expect it to. Turns out that when booting, the F7 guest console output starts on on the serial line, and finishes up with the graphical console. I posted what to do about this to Fedora-xen a week or so ago, so check the archives. Good luck, Mike > > BR > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From jlagrue at gmail.com Wed Jul 4 15:03:08 2007 From: jlagrue at gmail.com (John Lagrue) Date: Wed, 4 Jul 2007 16:03:08 +0100 Subject: [Fedora-xen] Fedora Xen kernel Message-ID: Because of complications with power management on my HP laptop, I really need to run a 2.6.21 kernel (or later). Does anyone have any idea when a Xen kernel will be available for that build? Currently the Xen kernels are way out of date compared to the standard Fedora kernels. JDL From m3freak at thesandhufamily.ca Wed Jul 4 20:55:01 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Wed, 04 Jul 2007 16:55:01 -0400 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <00fe01c7bd94$1e2e51b0$fe01a8c0@ispbrasil> References: <1183436874.6567.9.camel@krs> <20070703142338.GD8410@redhat.com> <1183473760.6567.21.camel@krs> <00fe01c7bd94$1e2e51b0$fe01a8c0@ispbrasil> Message-ID: <1183582501.3221.10.camel@krs> On Tue, 2007-07-03 at 14:03 -0300, Itamar Reis Peixoto wrote: > with non xen kernel are you able to see all amount of memory ? I haven't tried that, but I will tonight when I get home. I'm expecting the non-xen kernel to see all the RAM. > have you take a look on your bios to check if your video card is not using > your memory ? It could be, but even if it was, it wouldn't be much. I'm running the dom0 on a real server, and the embedded graphics controller is very simple. At most, it's probably using 8 MB if it doesn't have it's own dedicated memory. I'm fairly certain the real problem is a bug in Fedora Core 6's xen kernel. When I upgraded to the lastest kernel version, the kernel picked up more of the RAM. There's still about 256 missing, but it's better than the 512 MB that was missing with the older xen kernel. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2962.fc6 i686 GNU/Linux 16:54:39 up 1 day, 5:38, 3 users, load average: 0.20, 0.11, 0.09 From fcxen at itsbeen.sent.com Thu Jul 5 12:17:19 2007 From: fcxen at itsbeen.sent.com (FCXen) Date: Thu, 05 Jul 2007 05:17:19 -0700 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <1190534330.46171183491993975.JavaMail.root@zebra.lib.ucdavis.edu> References: <1190534330.46171183491993975.JavaMail.root@zebra.lib.ucdavis.edu> Message-ID: <468CE14F.3030506@itsbeen.sent.com> Dale Bewley wrote: >> And kudos to those running everything under the sun on an F7 dom0, but >> can >> someone give those of us who aren't in the secret club a break and >> publish a >> full step-by-step of how you did it and some config files/settings. > > Wrapper for virt-install worked on F7 dom0 for FC6 and F7 domU > http://bewley.net/linux/fedora/xen/mkxen.sh Wow, awesome, thanks. I will try this soon. Not interactive and not static IP but great for server setups. From fcxen at itsbeen.sent.com Thu Jul 5 12:24:39 2007 From: fcxen at itsbeen.sent.com (FCXen) Date: Thu, 05 Jul 2007 05:24:39 -0700 Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <20070703180939.0AD9B3C777@mx5.messagingengine.com> References: <46854E4C.8030107@vsic.net> <46857B4C.5010102@sbcglobal.net> <4685BD52.2030601@itsbeen.sent.com> <20070703180939.0AD9B3C777@mx5.messagingengine.com> Message-ID: <468CE307.8070703@itsbeen.sent.com> Robert Story wrote: > On Fri, 29 Jun 2007 19:17:54 -0700 FCXen wrote: > F> > Are you sure you're not missing the domU's console? I noticed that with > F> > at least the FC6 and F7 domUs, the boot output starts on the serial > F> > console, then transfers to the graphical console. I'm not familiar with > F> > the Centos domU's behavior, but it might be something to check. > F> > F> I think this is a big problem, it happened to me.* Unfortunately, I was trying > F> on FC6 Test 2/3 so I was told to get the F7 release version and try that. > F> > F> There is no clear step by step how to on how to build GUI-less domUs for FC6 * > F> or F7 > > I simply edit the xen config file and comment out the virtual frame buffer > line (vfb = [...]), and it works fine w/out a GUI... How? For creating a domain, "we" (the headless/ssh/GUI-less/text-based people) can't get through the creation process. And I thought that the F7 Xen didn't have config files anymore, that it was all stored in an XML blob in a db somewhere. Is that not the case? I am pretty sure that it is not possible to do an interactive text based creation of a F7 domU on an F7 dom0 via the virt-install command. And since I posted my previous msg there have been at least 2 more people posting (here and the Xen list) with the same problem AFAICT. I'll contact Thomas Chung http://fedoraproject.org/wiki/ThomasChung when I get a chance and ask him to create a Xen F7 QuickStart page so that it can get in the search engines and people can find out that they need to use some other method for doing Xen installs on F7. Unless there actually is a secret way to do it, if that is the case I'll try to send him the actual step for people to follow. * Sorry, I should have said specifically F7... I was testing on F6 test 2/3 so those weren't really FC6. From mikael at t-online.hu Thu Jul 5 13:59:27 2007 From: mikael at t-online.hu (Mikael Bak) Date: Thu, 5 Jul 2007 15:59:27 +0200 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <1183582501.3221.10.camel@krs> References: <1183436874.6567.9.camel@krs> <00fe01c7bd94$1e2e51b0$fe01a8c0@ispbrasil> <1183582501.3221.10.camel@krs> Message-ID: <200707051559.27315.mikael@t-online.hu> On Wednesday 04 July 2007 22:55:01 Kanwar Ranbir Sandhu wrote: > On Tue, 2007-07-03 at 14:03 -0300, Itamar Reis Peixoto wrote: > > with non xen kernel are you able to see all amount of memory ? > > I haven't tried that, but I will tonight when I get home. I'm expecting > the non-xen kernel to see all the RAM. > I expect that too! I have exactly the same problem. The difference is that I'm on Debian 4.0. So this may not be a Fedora-specific problem at all. If I boot the standard Debian 2.6.18-4-amd64 then I have 2061340k total using "top". If I boot Xen kernel 2.6.18-4-xen-amd64 the I only get 1793024k total. Something's eating memory. I'm going to file a report at Debian too. Just thought I drop the note here as well. HTH, Mikael From dlbewley at lib.ucdavis.edu Thu Jul 5 23:44:03 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Thu, 5 Jul 2007 16:44:03 -0700 (PDT) Subject: [Fedora-xen] Xen status for FC7 In-Reply-To: <468CE307.8070703@itsbeen.sent.com> Message-ID: <2110664379.27391183679043650.JavaMail.root@zebra.lib.ucdavis.edu> ----- "FCXen" wrote: > Robert Story wrote: > > I simply edit the xen config file and comment out the virtual frame > buffer > > line (vfb = [...]), and it works fine w/out a GUI... > > How? For creating a domain, "we" (the headless/ssh/GUI-less/text-based > people) > can't get through the creation process. And I thought that the F7 Xen > didn't > have config files anymore, that it was all stored in an XML blob in a > db > somewhere. Is that not the case? Yes, virsh dumpxml NAME > NAME.xml; vi NAME.xml; virsh define NAME.xml but there is no vfb line. > I am pretty sure that it is not possible to do an interactive text > based > creation of a F7 domU on an F7 dom0 via the virt-install command. = fc6 domU = On F7 dom0 if I do a fc6 domU install without a kickstart it begins in my terminal window, throws up a graphical console window if I've done xhost + dom0_server etc. This serial console window just has a dozen lines ending with a memory count. Then back in my terminal the typical anaconda installer shows up and all is fine. == fc6 domU serial console == Bootdata ok (command line is dhcp method=http://ks/fedora/linux/core/6/x86_64) Linux version 2.6.18-1.2798.fc6xen (brewbuilder at hs20-bc1-6.build.redhat.com) (gcc version 4.1.1 20061011 (Red Hat 4.1.1-30)) #1 SMP Mon Oct 16 14:59:01 EDT 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000040800000 (usable) No mptable found. Built 1 zonelists. Total pages: 264192 Kernel command line: dhcp method=http://ks/fedora/linux/core/6/x86_64 Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2588.848 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Software IO TLB disabled Memory: 1013760k/1056768k available (2323k kernel code, 34168k reserved, 1328k data, 172k init) = f7 domU = If I do a f7 domU install without a kickstart it does something similar. virt-install --name=f7-inter --ram=1024 \ --file=/var/lib/xen/images/f7-inter.xen \ --file-size=10 --nographics \ --location=http://ks/fedora/linux/releases/7/Fedora/x86_64/os \ --extra-args='dhcp nofb' \ --bridge=br101 --mac=AA:00:46:8D:7F:C8 --debug It throws up the graphical serial console app but this window contains many more lines and the terminal never fires up anaconda. I tried adding nofb, selinux=0, and noacpi to the extra args. That didn't help. Again, with kickstart it works eventually, but I don't see anything happening. == f7 domU serial console == Linux version 2.6.20-2925.9.fc7xen (kojibuilder at xenbuilder1.fedora.redhat.com) (gcc version 4.1.2 20070502 (Red Hat 4.1.2-12)) #1 SMP Tue May 22 09:29:36 EDT 2007 Command line: dhcp nofb method=http://ks/fedora/linux/releases/7/Fedora/x86_64/os BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000040800000 (usable) end_pfn_map = 264192 Zone PFN ranges: DMA 0 -> 264192 DMA32 264192 -> 264192 Normal 264192 -> 264192 early_node_map[1] active PFN ranges 0: 0 -> 264192 No mptable found. PERCPU: Allocating 26368 bytes of per cpu data Built 1 zonelists. Total pages: 259481 Kernel command line: dhcp nofb method=http://ks/fedora/linux/releases/7/Fedora/x86_64/os Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Xen reported: 2589.272 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Software IO TLB disabled Memory: 1015932k/1056768k available (2207k kernel code, 32024k reserved, 1347k data, 192k init) Calibrating delay using timer specific routine.. 6476.02 BogoMIPS (lpj=12952058) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 256 CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) CPU: L2 Cache: 1024K (64 bytes/line) (SMP-)alternatives turned off Brought up 1 CPUs Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled xen_mem: Initialising balloon driver. usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb PCI: System does not support PCI PCI: System does not support PCI NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 == f7 domU terminal window== That window ends with ... Xen virtual console successfully installed as xvc0 Event-channel device installed. usbcore: registered new interface driver libusual usbcore: registered new interface driver hiddev usbcore: registered new interface driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice TCP bic registered Initializing XFRM netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 XENBUS: Device with no driver: device/vbd/51712 XENBUS: Device with no driver: device/vif/0 Write protecting the kernel read-only data: 938k XInputWireToEvent: UNKNOWN WIRE EVENT! type=110 XInputWireToEvent: UNKNOWN WIRE EVENT! type=110 -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From felix.schwarz at web.de Fri Jul 6 07:43:34 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Fri, 06 Jul 2007 09:43:34 +0200 Subject: [Fedora-xen] How to shutdown a hvm guest gracefully? Message-ID: <468DF2A6.1000302@web.de> Hi, sometimes I forget to shutdown my hvm guests before restarting the host machine. I want to prevent this/automatically shutdown the guests gracefully (as if I typed 'poweroff' on the guest's console) http://fedoraproject.org/wiki/FedoraXenQuickstartFC6: > To gracefully power off a guest use: > # virsh shutdown On my FC6 (x86_64) machine this is only works for pv guests. Unfortunately, I use several hvm guests (e.g. 32 bit guests for FC{5,6,7} which can not be run under the current 64 bit xen in FC7 - AFAIK). However, all these guests are linux machines which can be powered off by sending "Ctrl+Alt+Del". Is there any possibility to gracefully shut down linux hvm guests? fs From admin at dougware.net Fri Jul 6 16:45:20 2007 From: admin at dougware.net (Doug Eubanks) Date: Fri, 06 Jul 2007 12:45:20 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me Message-ID: <20070706164520.520351f7@mail.dougware.net> I've tried the xen kernel on Fedora 6, CentOS 5 and now I'm running Fedora 7. Each time, it seems to hang during or perhaps right after the SCSI hardware is initialized. It doesn't panic, although it sometimes prints messages about USB devices not accepting new addresses (but not always). I am attaching my SCSI and CPU info, if anyone has a suggestion to fix or troubleshoot this I would appreciate any information. [root at DMZServer /]# ls /proc/scsi/ aic7xxx device_info gdth scsi sg [root at DMZServer /]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.76 clflush size : 32 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.02 clflush size : 32 processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.02 clflush size : 32 processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.02 clflush size : 32 -------------- next part -------------- An HTML attachment was scrubbed... URL: From admin at dougware.net Fri Jul 6 16:55:35 2007 From: admin at dougware.net (Doug Eubanks) Date: Fri, 06 Jul 2007 12:55:35 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me Message-ID: <20070706165535.1b581125@mail.dougware.net> I've tried the xen kernel on Fedora 6, CentOS 5 and now I'm running Fedora 7. Each time, it seems to hang during or perhaps right after the SCSI hardware is initialized. It doesn't panic, although it sometimes prints messages about USB devices not accepting new addresses (but not always). I am attaching my SCSI and CPU info, if anyone has a suggestion to fix or troubleshoot this I would appreciate any information. [root at DMZServer /]# ls /proc/scsi/ aic7xxx device_info gdth scsi sg [root at DMZServer /]# cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.76 clflush size : 32 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.02 clflush size : 32 processor : 2 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.02 clflush size : 32 processor : 3 vendor_id : GenuineIntel cpu family : 6 model : 10 model name : Pentium III (Cascades) stepping : 0 cpu MHz : 701.640 cache size : 1024 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse bogomips : 1403.02 clflush size : 32 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Fri Jul 6 19:11:32 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 06 Jul 2007 20:11:32 +0100 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: <20070706164520.520351f7@mail.dougware.net> References: <20070706164520.520351f7@mail.dougware.net> Message-ID: <468E93E4.1060904@redhat.com> Doug Eubanks wrote: > I've tried the xen kernel on Fedora 6, CentOS 5 and now I'm running > Fedora 7. > > Each time, it seems to hang during or perhaps right after the SCSI > hardware is initialized. It doesn't panic, although it sometimes prints > messages about USB devices not accepting new addresses (but not always). We really need to see the kernel messages. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From m3freak at thesandhufamily.ca Mon Jul 9 12:19:04 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Mon, 09 Jul 2007 08:19:04 -0400 Subject: [Fedora-xen] ups connected to serial port, but can't communicate via ttyS0 Message-ID: <1183983544.26037.23.camel@krs> Hi, I tried to use ttyS0 in dom0 for a serial interface UPS, but apcupsd complains that it can't talk to ttyS0. I look through /var/log/messages, and sure enough, xen is using it: Jul 3 09:45:22 xenmaster kernel: Xen virtual console successfully installed as ttyS0 Can that be turned off, so that ttyS0 isn't used by Xen? I tried to do this several months ago, but back then I was told Fedora was working towards fixing the serial port access problems. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2962.fc6 i686 GNU/Linux 08:15:36 up 5 days, 20:58, 3 users, load average: 0.35, 0.18, 0.17 From admin at dougware.net Mon Jul 9 12:49:50 2007 From: admin at dougware.net (Doug Eubanks) Date: Mon, 09 Jul 2007 08:49:50 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: 468E93E4.1060904@redhat.com Message-ID: <20070709124950.46ff924b@mail.dougware.net> So I tried the lastest XEN kernel again on Friday (2.6.20-2925.11.fc7xen). It gets hung in a loop resetting the AIC7xxx adapter. It resets, timesouts, resets again over and over. I have two adapters that use that driver in my system, the on board (which is disabled) and an Adaptec 2940 which has my DLT tape drive attached. Is it possible that the 2.6.20-2925.11.fc7xen kernel has a bug in the AIC7xxxx driver that's been patched in the newer mainline kernel? If anyone needs the specific messages, I will be happy to write them down today (I have to reboot to install another 1G of RAM that's arriving today). Thanks, Doug Eubanks _____ From: Richard W.M. Jones [mailto:rjones at redhat.com] To: Doug Eubanks [mailto:admin at dougware.net] Cc: fedora-xen at redhat.com Sent: Fri, 06 Jul 2007 15:11:32 -0400 Subject: Re: [Fedora-xen] Xen kernel doesn't boot for me Doug Eubanks wrote: > I've tried the xen kernel on Fedora 6, CentOS 5 and now I'm running > Fedora 7. > > Each time, it seems to hang during or perhaps right after the SCSI > hardware is initialized. It doesn't panic, although it sometimes prints > messages about USB devices not accepting new addresses (but not always). We really need to see the kernel messages. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Mon Jul 9 12:56:39 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 09 Jul 2007 13:56:39 +0100 Subject: [Fedora-xen] ups connected to serial port, but can't communicate via ttyS0 In-Reply-To: <1183983544.26037.23.camel@krs> References: <1183983544.26037.23.camel@krs> Message-ID: <46923087.7050407@redhat.com> Kanwar Ranbir Sandhu wrote: > Hi, > > I tried to use ttyS0 in dom0 for a serial interface UPS, but apcupsd > complains that it can't talk to ttyS0. I look through /var/log/messages, > and sure enough, xen is using it: > > Jul 3 09:45:22 xenmaster kernel: Xen virtual console successfully > installed as ttyS0 > > Can that be turned off, so that ttyS0 isn't used by Xen? I tried to do > this several months ago, but back then I was told Fedora was working > towards fixing the serial port access problems. Try the suggestions here: http://phaq.phunsites.net/2007/06/30/xen-console-grabbded-devttys0/ In particular try booting with xencons=off (on the kernel command line, not the Xen hypervisor command line). Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From jonas.weismueller at comsoft.de Mon Jul 9 14:39:50 2007 From: jonas.weismueller at comsoft.de (Weismueller, Jonas) Date: Mon, 09 Jul 2007 16:39:50 +0200 Subject: [Fedora-xen] HVM bridge not working any more Message-ID: <469248B6.5070403@comsoft.de> Hi, I am using xen on F7. My guest config looks like this: ********************************************* kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 512 name = "scp231" vcpus=2 pae=1 acpi=1 vif = [ 'type=ioemu, bridge=virbr0' ] dhcp="off" disk = [ 'phy:/dev/aida/scp-231,hda,w', ',hdc:cdrom,r' ] device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' boot="cda" vnc=1 vncdisplay=1 vncpasswd='' stdvga=0 serial='pty' localtime=1 ********************************************* [root at csli9 ~]# /etc/xen/scripts/network-bridge status ============================================================ 8: eth2: mtu 1500 qdisc noqueue link/ether 00:30:48:31:97:49 brd ff:ff:ff:ff:ff:ff inet 172.16.1.37/16 brd 172.16.255.255 scope global eth2 inet6 fe80::230:48ff:fe31:9749/64 scope link valid_lft forever preferred_lft forever 8: eth2: mtu 1500 qdisc noqueue link/ether 00:30:48:31:97:49 brd ff:ff:ff:ff:ff:ff inet 172.16.1.37/16 brd 172.16.255.255 scope global eth2 inet6 fe80::230:48ff:fe31:9749/64 scope link valid_lft forever preferred_lft forever bridge name bridge id STP enabled interfaces eth2 8000.003048319749 no peth2 virbr0 8000.3a7b564bbcda no tap0 vif1.0 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 172.16.0.0/16 dev eth2 proto kernel scope link src 172.16.1.37 default via 172.16.1.16 dev eth2 Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 172.16.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth2 0.0.0.0 172.16.1.16 0.0.0.0 UG 0 0 0 eth2 ============================================================ [root at csli9 ~]# ifconfig eth2 Link encap:Ethernet HWaddr 00:30:48:31:97:49 inet addr:172.16.1.37 Bcast:172.16.255.255 Mask:255.255.0.0 inet6 addr: fe80::230:48ff:fe31:9749/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15230 errors:0 dropped:0 overruns:0 frame:0 TX packets:3692 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:897539 (876.5 KiB) TX bytes:2761958 (2.6 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:6171 errors:0 dropped:0 overruns:0 frame:0 TX packets:6171 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:51022608 (48.6 MiB) TX bytes:51022608 (48.6 MiB) peth2 Link encap:Ethernet HWaddr 00:30:48:31:97:49 inet6 addr: fe80::230:48ff:fe31:9749/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:240988 errors:0 dropped:0 overruns:0 frame:0 TX packets:3730 errors:0 dropped:0 overruns:0 carrier:0 collisions:539 txqueuelen:100 RX bytes:65841255 (62.7 MiB) TX bytes:2780370 (2.6 MiB) Base address:0x4020 Memory:d8420000-d8440000 tap0 Link encap:Ethernet HWaddr 3A:7B:56:4B:BC:DA inet6 addr: fe80::387b:56ff:fe4b:bcda/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:110 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:7544 (7.3 KiB) TX bytes:510 (510.0 b) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP 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:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 3A:7B:56:4B:BC:DA inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:110 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6004 (5.8 KiB) TX bytes:510 (510.0 b) I would like to use the guest within the subnet of eth2, so 172.16.0.0 . But it doesn't work for any reason? It looks like, that I only can use a 192.168.122.X address in the guest. Any glue how to bridge the interface to be able access the 172.16.0.0 network directly? Regards Jonas -- --------------------------------------------------------------------------- Jonas Weismueller Phone: +49 721 9497-163 COMSOFT GmbH Fax: +49 721 9497-129 Wachhausstrasse 5a http://www.comsoft.de 76227 Karlsruhe, Germany mailto:jonas.weismueller at comsoft.de Gesch?ftsf?hrer: Manfred Jlg, Manfred Schmid Sitz der Gesellschaft: Karlsruhe, Handelsregister: Mannheim HRB 102488 Help save paper - do you really need to print this e-mail? --- Disclaimer --- This mail contains private or confidential information for the eyes of the addressee(s) named within this mail only. Any distribution or usage, in whole or in part, is strictly prohibited. If the context of this message indicates that you may have received this mail by error, please immediately contact and notify the sender and delete this mail from your computers as well as from your mail server. Thank you! --------------------------------------------------------------------------- From rjones at redhat.com Mon Jul 9 14:56:39 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 09 Jul 2007 15:56:39 +0100 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: <20070709124950.46ff924b@mail.dougware.net> References: <20070709124950.46ff924b@mail.dougware.net> Message-ID: <46924CA7.1070201@redhat.com> Doug Eubanks wrote: > So I tried the lastest XEN kernel again on Friday (2.6.20-2925.11.fc7xen). > > It gets hung in a loop resetting the AIC7xxx adapter. It resets, > timesouts, resets again over and over. > > I have two adapters that use that driver in my system, the on board > (which is disabled) and an Adaptec 2940 which has my DLT tape drive > attached. Is it possible that the 2.6.20-2925.11.fc7xen kernel has a > bug in the AIC7xxxx driver that's been patched in the newer mainline kernel? The 2.6.20...xen kernel really is based off the 2.6.20 standard (Fedora) kernel. So if the driver works in 2.6.20-2925 and not in the xen version, it's not because of a bugfix, but because of something else about Xen itself. > If anyone needs the specific messages, I will be happy to write them > down today (I have to reboot to install another 1G of RAM that's > arriving today). Very hard to say without seeing the messages. Assuming that the boot isn't getting you into a shell, setting up a serial console is the easiest way to capture them. Alternately you can try taking a screenshot with a digital camera. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From ehabkost at redhat.com Mon Jul 9 16:43:42 2007 From: ehabkost at redhat.com (Eduardo Habkost) Date: Mon, 9 Jul 2007 13:43:42 -0300 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: <46924CA7.1070201@redhat.com> References: <20070709124950.46ff924b@mail.dougware.net> <46924CA7.1070201@redhat.com> Message-ID: <20070709164342.GA14152@blackpad.ctb.virtua.com.br> On Mon, Jul 09, 2007 at 03:56:39PM +0100, Richard W.M. Jones wrote: > Doug Eubanks wrote: > >So I tried the lastest XEN kernel again on Friday (2.6.20-2925.11.fc7xen). > > > >It gets hung in a loop resetting the AIC7xxx adapter. It resets, > >timesouts, resets again over and over. > > > >I have two adapters that use that driver in my system, the on board > >(which is disabled) and an Adaptec 2940 which has my DLT tape drive > >attached. Is it possible that the 2.6.20-2925.11.fc7xen kernel has a > >bug in the AIC7xxxx driver that's been patched in the newer mainline > >kernel? > > The 2.6.20...xen kernel really is based off the 2.6.20 standard (Fedora) > kernel. So if the driver works in 2.6.20-2925 and not in the xen > version, it's not because of a bugfix, but because of something else > about Xen itself. Actually, it may be because of a missing bugfix, also. It may be because the F7 non-xen kernel is based on a newer upstream kernel version, or because I have missed some fix that went to the F7 non-xen kernel. On FC6, both non-xen and xen kernels come from the same source package, so this wouldn't happen on FC6. But somewhere between Fedora 6 and 7, the non-xen and xen kernels were split, because the non-xen kernel was being rebased faster than we were being able to rebase the xen patches. Being as close as possible to the non-xen kernel is one of my goals, but currently there may be some bits missing. -- Eduardo -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From m3freak at thesandhufamily.ca Mon Jul 9 16:53:55 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Mon, 09 Jul 2007 12:53:55 -0400 Subject: [Fedora-xen] Not seeing all RAM In-Reply-To: <200707051559.27315.mikael@t-online.hu> References: <1183436874.6567.9.camel@krs> <00fe01c7bd94$1e2e51b0$fe01a8c0@ispbrasil> <1183582501.3221.10.camel@krs> <200707051559.27315.mikael@t-online.hu> Message-ID: <1184000035.26037.36.camel@krs> On Thu, 2007-07-05 at 15:59 +0200, Mikael Bak wrote: > I expect that too! > I have exactly the same problem. The difference is that I'm on Debian 4.0. So > this may not be a Fedora-specific problem at all. > > If I boot the standard Debian 2.6.18-4-amd64 then I have 2061340k total > using "top". > If I boot Xen kernel 2.6.18-4-xen-amd64 the I only get 1793024k total. I booted the server with the non-xen kernel, and this is what free reports: [root at xenmaster ~]# free total used free shared buffers cached Mem: 3109504 82904 3026600 0 7084 33652 -/+ buffers/cache: 42168 3067336 Swap: 524280 0 524280 As you can see, all of the RAM is available. So, it's most probably a bug in the xen kernel. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2962.fc6 i686 GNU/Linux 12:52:10 up 6 days, 1:34, 3 users, load average: 0.50, 0.41, 0.31 From m3freak at thesandhufamily.ca Mon Jul 9 17:26:24 2007 From: m3freak at thesandhufamily.ca (Kanwar Ranbir Sandhu) Date: Mon, 09 Jul 2007 13:26:24 -0400 Subject: [Fedora-xen] ups connected to serial port, but can't communicate via ttyS0 In-Reply-To: <46923087.7050407@redhat.com> References: <1183983544.26037.23.camel@krs> <46923087.7050407@redhat.com> Message-ID: <1184001984.26037.42.camel@krs> On Mon, 2007-07-09 at 13:56 +0100, Richard W.M. Jones wrote: > Try the suggestions here: > > http://phaq.phunsites.net/2007/06/30/xen-console-grabbded-devttys0/ > > In particular try booting with xencons=off (on the kernel command line, > not the Xen hypervisor command line). That worked! My Smart UPS 1400 is now being monitored/controlled from dom0 with apcupsd. There were some errors in /var/log/messages, though: Jul 9 12:50:45 xenmaster kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Jul 9 12:50:45 xenmaster kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Jul 9 12:55:02 xenmaster kernel: Kernel command line: ro root=/dev/vg00/root xencons=tty1 Jul 9 12:55:11 xenmaster kernel: WARNING: Failed to register Xen virtual console driver as 'tty1' Jul 9 12:55:14 xenmaster kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A Jul 9 12:55:14 xenmaster kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A I'll try with a different tty later, say tty6. But, I don't know if that will fix the above warning. I have another question: can I hand the serial port to a domU, or does it have to be present in dom0? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.20-1.2962.fc6 i686 GNU/Linux 13:24:02 up 6 days, 2:06, 4 users, load average: 0.20, 0.35, 0.26 From rjones at redhat.com Mon Jul 9 17:58:29 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 09 Jul 2007 18:58:29 +0100 Subject: [Fedora-xen] ups connected to serial port, but can't communicate via ttyS0 In-Reply-To: <1184001984.26037.42.camel@krs> References: <1183983544.26037.23.camel@krs> <46923087.7050407@redhat.com> <1184001984.26037.42.camel@krs> Message-ID: <46927745.1020007@redhat.com> Kanwar Ranbir Sandhu wrote: > On Mon, 2007-07-09 at 13:56 +0100, Richard W.M. Jones wrote: >> Try the suggestions here: >> >> http://phaq.phunsites.net/2007/06/30/xen-console-grabbded-devttys0/ >> >> In particular try booting with xencons=off (on the kernel command line, >> not the Xen hypervisor command line). > > That worked! My Smart UPS 1400 is now being monitored/controlled from > dom0 with apcupsd. > > There were some errors in /var/log/messages, though: > > Jul 9 12:50:45 xenmaster kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = > 4) is a 16550A > Jul 9 12:50:45 xenmaster kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is > a 16550A > Jul 9 12:55:02 xenmaster kernel: Kernel command line: ro > root=/dev/vg00/root xencons=tty1 > Jul 9 12:55:11 xenmaster kernel: WARNING: Failed to register Xen > virtual console driver as 'tty1' > Jul 9 12:55:14 xenmaster kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = > 4) is a 16550A > Jul 9 12:55:14 xenmaster kernel: 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is > a 16550A > > I'll try with a different tty later, say tty6. But, I don't know if > that will fix the above warning. It's absolutely ages since I used serial ports under Linux -- I mean 10 years at least -- but my recollection is that they are called things like ttyS1 (with the 'S' in there). > I have another question: can I hand the serial port to a domU, or does > it have to be present in dom0? There's a bit about this on the Xen wiki: http://wiki.xensource.com/xenwiki/InstallationNotes#head-327388b324997719e864f8740fed06036c799e38 Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From taoj2 at cs.rpi.edu Mon Jul 9 20:08:45 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Mon, 9 Jul 2007 16:08:45 -0400 (EDT) Subject: [Fedora-xen] guest domain couldn't be started Message-ID: <50013.128.213.28.103.1184011725.squirrel@webmail.cs.rpi.edu> Hi, I install a guest Fedora inside the host Fedora. When I use the service xend status to check the status of xend. It shows xend is running. However when I use xm create xen1 to start the guest domain xen1, it failed. The corresponding file xen1 is in /etc/xen/xen1. The error msg is as follows: [root at phillis xen]# xm create xen1 Using config file "./xen1". Going to boot Fedora Core (2.6.19-1.2911.6.5.fc6xen) kernel: /vmlinuz-2.6.19-1.2911.6.5.fc6xen initrd: /initrd-2.6.19-1.2911.6.5.fc6xen.img Error: Device 0 (vif) could not be connected. Could not find bridge device xenbr1 I found the following line in file /etc/xen/xen1, vif = [ 'mac=00:16:3e:5c:5c:31, bridge=xenbr1', ] Why device 0 couldn't be connected? I don't know the usage of the bridge device, xenbr1. Anybody has similar problem ? Or know how to slove this problem? THanks. Best Angel From mmcgrath at redhat.com Tue Jul 10 04:40:08 2007 From: mmcgrath at redhat.com (Mike McGrath) Date: Mon, 09 Jul 2007 23:40:08 -0500 Subject: [Fedora-xen] guest domain couldn't be started In-Reply-To: <50013.128.213.28.103.1184011725.squirrel@webmail.cs.rpi.edu> References: <50013.128.213.28.103.1184011725.squirrel@webmail.cs.rpi.edu> Message-ID: <46930DA8.3080104@redhat.com> taoj2 at cs.rpi.edu wrote: > Hi, > > I install a guest Fedora inside the host Fedora. When I use the > > service xend status > > to check the status of xend. It shows xend is running. > > However when I use > > xm create xen1 > > to start the guest domain xen1, it failed. The corresponding file xen1 is > in /etc/xen/xen1. The error msg is as follows: > > [root at phillis xen]# xm create xen1 > Using config file "./xen1". > Going to boot Fedora Core (2.6.19-1.2911.6.5.fc6xen) > kernel: /vmlinuz-2.6.19-1.2911.6.5.fc6xen > initrd: /initrd-2.6.19-1.2911.6.5.fc6xen.img > Error: Device 0 (vif) could not be connected. Could not find bridge device > xenbr1 > > I found the following line in file /etc/xen/xen1, > vif = [ 'mac=00:16:3e:5c:5c:31, bridge=xenbr1', ] > > Why device 0 couldn't be connected? I don't know the usage of the bridge > device, xenbr1. > > Anybody has similar problem ? Or know how to slove this problem? THanks. > > Best > Angel when you do an ifconfig do you see a xenbr1 or a xenbr0? -Mike From s.jahangir at qut.edu.au Tue Jul 10 06:24:36 2007 From: s.jahangir at qut.edu.au (Selim Jahangir) Date: Tue, 10 Jul 2007 16:24:36 +1000 Subject: [Fedora-xen] guest domain couldn't be started In-Reply-To: <46930DA8.3080104@redhat.com> References: <50013.128.213.28.103.1184011725.squirrel@webmail.cs.rpi.edu> <46930DA8.3080104@redhat.com> Message-ID: <03DD0A35305B7045B436D107CDE9391A7EBF03@beeex03.qut.edu.au> Hi there I have installed Xen virtual machine in Red Hat Enterprise 5 named virtpc1. Now can you tell me how can I get more copy of the virtpc1 named virtpc2, virtpc3 etc ? What I have done so far , I copied the virtpc1 as virtpc2 and virtpc3 in /etc/xen , changed the hostname and file name in config respective in /etc/xen also I copied the disk file in /opt/virtpc1 as virtpc2 and virtpc3. When I type # xm create virtpc1 , it creates domain virtpc1 fine and running fine. But when I type xm create virtpc2 it fails but if I type xm list and I can see two more domains created by the named virtpc1 virtpc1 , same name twice , it supposed to be virtpc1 and virtpc2. Any solution please ? Regards selim From xenguy at gmail.com Tue Jul 10 09:29:37 2007 From: xenguy at gmail.com (Sadique Puthen) Date: Tue, 10 Jul 2007 14:59:37 +0530 Subject: [Fedora-xen] guest domain couldn't be started In-Reply-To: <03DD0A35305B7045B436D107CDE9391A7EBF03@beeex03.qut.edu.au> References: <50013.128.213.28.103.1184011725.squirrel@webmail.cs.rpi.edu> <46930DA8.3080104@redhat.com> <03DD0A35305B7045B436D107CDE9391A7EBF03@beeex03.qut.edu.au> Message-ID: <46935181.7070603@gmail.com> Selim Jahangir wrote: > Hi there > I have installed Xen virtual machine in Red Hat Enterprise 5 named > virtpc1. Now can you tell me how can I get more copy of the virtpc1 > named virtpc2, virtpc3 etc ? > > What I have done so far , > > I copied the virtpc1 as virtpc2 and virtpc3 in /etc/xen , changed the > hostname and file name in config respective in /etc/xen also I copied > the disk file in /opt/virtpc1 as virtpc2 and virtpc3. > > When I type > # xm create virtpc1 , it creates domain virtpc1 fine and running fine. > But when I type xm create virtpc2 it fails but if I type xm list and I > can see two more domains created by the named virtpc1 virtpc1 , same > name twice , it supposed to be virtpc1 and virtpc2. > > Any solution please ? > uuid should be uniq for each guest. Use uuidgen and replace the uuid= parameter on the second and third guest. > Regards > selim > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > From kylet at panix.com Tue Jul 10 10:23:29 2007 From: kylet at panix.com (Kyle Tucker) Date: Tue, 10 Jul 2007 06:23:29 -0400 Subject: [Fedora-xen] CentOS 5 guest sees only one CPU Message-ID: <20070710102329.GA23950@panix.com> Hi, We have set up Xen on Fedora Core 5 Domain0 with a CentOS 5 HVM. This is a Dell Poweredge SC1430 system. We've set vcpus=2 and it will only see one CPU. I've also tried setting cpus="1,2" or "6,7" to no avail. Here's what xm reports when I've set cpus="6,7". # xm vcpu-list Name ID VCPUs CPU State Time(s) CPU Affinity Domain-0 0 0 6 -b- 3304.1 any cpu Domain-0 0 1 1 -b- 245.0 any cpu Domain-0 0 2 0 -b- 198.5 any cpu Domain-0 0 3 5 -b- 901.3 any cpu Domain-0 0 4 4 -b- 192.6 any cpu Domain-0 0 5 2 -b- 236.0 any cpu Domain-0 0 6 0 r-- 240.8 any cpu Domain-0 0 7 3 -b- 200.9 any cpu vm2 67 0 7 -b- 45.2 6-7 vm2 67 1 - --p 0.0 6-7 The following is in vm2's dmesg output, and I suspect the line about not detecting a SMP motherboard begins to point at the issue. Any thoughts on what's up? Thanks. CPU: After generic identify, caps: 8fa9f9bf 00100000 00000000 00000000 0000e215 00000000 00000000 CPU: After vendor identify, caps: 8fa9f9bf 00100000 00000000 00000000 0000e215 00000000 00000000 CPU: L1 I cache: 32K, L1 D cache: 32K CPU: L2 cache: 4096K CPU: After all inits, caps: 8fa9f1bf 00100000 00000000 00000140 0000e215 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Checking 'hlt' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 16k freed CPU0: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz stepping 07 SMP motherboard not detected. Local APIC not detected. Using dummy APIC emulation. Brought up 1 CPUs -- - Kyle --------------------------------------------- kylet at panix.com http://www.panix.com/~kylet --------------------------------------------- From Tony.Johnson at gdc4s.com Mon Jul 9 21:16:00 2007 From: Tony.Johnson at gdc4s.com (Johnson, Tony M) Date: Mon, 9 Jul 2007 17:16:00 -0400 Subject: [Fedora-xen] Trouble installing Windows HVM on 3.1 Message-ID: <34868b7d00004466@gdc4s.com> All, Whether I utilize the DVD or ISO image, once the initial setup is completed, rebooted and restarted, I get the following pop-up: "The file 'asms' on Windows XP Professional Service Pack 2 CD is needed" Has anyone experienced and solved this problem using x64? Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: From rwarsow at online.de Tue Jul 10 16:20:51 2007 From: rwarsow at online.de (Ronald Warsow) Date: Tue, 10 Jul 2007 18:20:51 +0200 Subject: [Fedora-xen] Trouble installing Windows HVM on 3.1 In-Reply-To: <34868b7d00004466@gdc4s.com> References: <34868b7d00004466@gdc4s.com> Message-ID: <4693B1E3.4080405@online.de> Johnson, Tony M wrote: > All, > Whether I utilize the DVD or ISO image, once the initial setup is > completed, rebooted and restarted, > I get the following pop-up: > "The file 'asms' on Windows XP Professional Service Pack 2 CD is needed" > > Has anyone experienced and solved this problem using x64? windows x64 ? or linux x64 and windows x86 ? i compose win iso's with nlite http://en.wikipedia.org/wiki/NLite - unattend installs, - all sp's/updates, - no unneeded grap, - no hassle with asms files/dir's - small iso's - ... > Tony > -- Ronald From rwarsow at online.de Tue Jul 10 20:49:56 2007 From: rwarsow at online.de (Ronald Warsow) Date: Tue, 10 Jul 2007 22:49:56 +0200 Subject: [Fedora-xen] Trouble installing Windows HVM on 3.1 In-Reply-To: <38ad1c36000050e4@gdc4s.com> References: <34868b7d00004466@gdc4s.com> <4693B1E3.4080405@online.de> <38ad1c36000050e4@gdc4s.com> Message-ID: <4693F0F4.2070008@online.de> Johnson, Tony M wrote: > Installing windows XP professional on a core duo with > Fedora x64 installed. Thanks for the pointer I will give > it a try. I assume you have not encountered this issue > because of embedding the asms with NLite. to your above question: up to now i was under the impression that nlite among other things deletes some stuff, esp. asms dir, also. but this is not the case for my lastly created iso. i install that xp (x86) iso's under f7 (x64) with qemu-kvm ! and i believe the internal "mechanics" to do a xp installation with virt-manager under a xen kernel makes not diff. to me. maybe i'm wrong ? but i tried it now and it leads me to your initial question: do you mean the xp installation prompts you for file asms from *GLOBALROOT\DEVICE\CDROM\I386* ??????????? if so then it's described/discussed here: https://virt.108.redhat.com/articles/2007/01/15/xen-guest-installation.pdf page 5... let me know if that was your question ! > > Tony > > -----Original Message----- > From: Ronald Warsow [mailto:rwarsow at online.de] > Sent: Tuesday, July 10, 2007 11:21 AM > To: Johnson, Tony M > Cc: fedora-xen at redhat.com > Subject: Re: [Fedora-xen] Trouble installing Windows HVM on 3.1 > > Johnson, Tony M wrote: >> All, >> Whether I utilize the DVD or ISO image, once the initial setup is >> completed, rebooted and restarted, I get the following pop-up: >> "The file 'asms' on Windows XP Professional Service Pack 2 CD is > needed" >> Has anyone experienced and solved this problem using x64? > > windows x64 ? > or > linux x64 and windows x86 ? > > i compose win iso's with nlite > http://en.wikipedia.org/wiki/NLite > > - unattend installs, > - all sp's/updates, > - no unneeded grap, > - no hassle with asms files/dir's > - small iso's > - ... > >> Tony >> > -- Ronald From admin at dougware.net Wed Jul 11 06:30:11 2007 From: admin at dougware.net (Doug Eubanks) Date: Wed, 11 Jul 2007 02:30:11 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me Message-ID: <153BCF0C-F4E5-4E16-AC23-6EFA055788A1@dougware.net> I am attaching two photos, one is the first error...the second is the loop of errors. Doug It it's not broke, take it apart and fix it.... -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DSC01097m.JPG Type: image/jpeg Size: 80835 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: DSC01104m.JPG Type: image/jpeg Size: 86011 bytes Desc: not available URL: From rjones at redhat.com Wed Jul 11 09:51:15 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 11 Jul 2007 10:51:15 +0100 Subject: [Fedora-xen] Trouble installing Windows HVM on 3.1 In-Reply-To: <34868b7d00004466@gdc4s.com> References: <34868b7d00004466@gdc4s.com> Message-ID: <4694A813.3010409@redhat.com> Johnson, Tony M wrote: > All, > Whether I utilize the DVD or ISO image, once the initial setup is > completed, rebooted and restarted, > I get the following pop-up: > "The file 'asms' on Windows XP Professional Service Pack 2 CD is needed" > Has anyone experienced and solved this problem using x64? > Tony This may be this well-known problem with installing Windows using virt-manager, notably after the first reboot the CD-ROM device disappears and must be readded manually: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242291 (That's a bug report against KVM, but the same happens with Xen for me). Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rjones at redhat.com Wed Jul 11 09:58:01 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 11 Jul 2007 10:58:01 +0100 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: <153BCF0C-F4E5-4E16-AC23-6EFA055788A1@dougware.net> References: <153BCF0C-F4E5-4E16-AC23-6EFA055788A1@dougware.net> Message-ID: <4694A9A9.3070500@redhat.com> Doug Eubanks wrote: > I am attaching two photos, one is the first error...the second is the > loop of errors. Can you try booting with noapic on the kernel command line. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From admin at dougware.net Wed Jul 11 15:25:16 2007 From: admin at dougware.net (Doug Eubanks) Date: Wed, 11 Jul 2007 11:25:16 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: 4694A9A9.3070500@redhat.com Message-ID: <20070711152516.09872a99@mail.dougware.net> It's there, here is my entire kernel line from grub root=/dev/VolGroup_RAID4/root acpi=noirq noapic apm=off rhgb quiet Doug _____ From: Richard W.M. Jones [mailto:rjones at redhat.com] To: Doug Eubanks [mailto:admin at dougware.net] Cc: fedora-xen at redhat.com [mailto:fedora-xen at redhat.com] Sent: Wed, 11 Jul 2007 05:58:01 -0400 Subject: Re: [Fedora-xen] Xen kernel doesn't boot for me Doug Eubanks wrote: > I am attaching two photos, one is the first error...the second is the > loop of errors. Can you try booting with noapic on the kernel command line. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ukhanlists at hotmail.com Wed Jul 11 17:35:23 2007 From: ukhanlists at hotmail.com (Ubaidul Khan) Date: Wed, 11 Jul 2007 13:35:23 -0400 Subject: [Fedora-xen] RHEL 5 - Multiple Bridges with same Hardware Address Message-ID: I am writing this email in the hopes of getting some advice from Xen users. My main concern is performance and stability. Before I get any further, let me explain the environment: 1. I am using redhat enterprise linux 5 with the xen kernel (2.6.18-8.1.1.el5xen). This is on a Sun X4200 with two dual core AMD processors, 16Gb of RAM, a Sun StoredgeTek 3320 attached to the X4200, has a 4 port NIC. 2. eth0 is configured as the primary interface for the Domain-0 and is attached to the xenbr0. I am using network-bridge model to provide networking for the two guest domains. One of the domains is running NFS server and needs to be configured with a private network address(on eth1). 3. So what I did is, I took eth1(on domain-0) and configured it on the private network. Then I created a script called *custom-bridge*(this was mentioned in (http://www.debian-administration.org/articles/470), with the following: +----------------------------------------------------------- | #!/bin/sh | dir=$(dirname "$0") | "$dir/network-bridge" "$@" vifnum=0 netdev=eth0 bridge=xenbr0 | "$dir/network-bridge" "$@" vifnum=3 netdev=eth1 bridge=xenbr1 and modified xend-config.sxp in the following manner: +----------------------------------------------------------- | # The bridge is named xenbr0, by default. To rename the bridge, use | # | # (network-script 'network-bridge bridge=') | # | # It is possible to use the network-bridge script in more complicated | # scenarios, such as having two outgoing interfaces, with two bridges, and | # two fake interfaces per guest domain. To do things like this, write | # yourself a wrapper script, and call network-bridge from it, as appropriate. | # | (network-script 'custom-bridge start') The guest domain comes up fine and I am able to talk on the private network from the guest domain and also from the private network to the guest domain. However, both of the bridges are configured with the same hardware address: xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF I think this is causing the following messages to show up on logs: Jul 9 17:15:25 kernel: peth0: received packet with own address as source address Jul 9 17:19:38 kernel: peth0: received packet with own address as source address Jul 9 17:19:38 kernel: peth0: received packet with own address as source address Jul 9 17:19:42 kernel: peth0: received packet with own address as source address Jul 9 17:30:27 kernel: peth0: received packet with own address as source address Jul 9 17:30:27 kernel: peth0: received packet with own address as source address Jul 10 09:12:19 kernel: peth0: received packet with own address as source address Jul 10 10:06:04 kernel: peth0: received packet with own address as source address Jul 10 10:06:04 kernel: peth0: received packet with own address as source address Jul 10 10:06:05 kernel: peth0: received packet with own address as source address I am also seeing performance degradation. Any advice/suggestion is greatly appreciated. _________________________________________________________________ http://liveearth.msn.com From bst at mobilethink.dk Wed Jul 11 17:55:48 2007 From: bst at mobilethink.dk (Bertho Stultiens) Date: Wed, 11 Jul 2007 19:55:48 +0200 Subject: [Fedora-xen] RHEL 5 - Multiple Bridges with same Hardware Address In-Reply-To: References: Message-ID: <469519A4.8060503@mobilethink.dk> Ubaidul Khan wrote: [snip] > However, both of the bridges are configured with the same hardware > address: > xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > xenbr1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF You cannot have bridges with the same address without causing some serious network problems. You can simply set the second bridge to another address using: # ip link set dev xenbr1 address FE:FF:FF:FF:FF:FE after it is created, but before it enslaves the interfaces. Alternatively, use MAC addresses from the 10:00:00:x:x:x range, which are reserved for private use (and do not set the low bit of the first octet, or you will create a multicast MAC address). -- Greetings Bertho From asraikhn at gmail.com Thu Jul 12 11:47:40 2007 From: asraikhn at gmail.com (Asrai khn) Date: Thu, 12 Jul 2007 16:47:40 +0500 Subject: [Fedora-xen] domUs become unaccessible running 2.6.20-1.2962.fc6xen on host Message-ID: <5f0f8dba0707120447vee80e29u8a5b007e840c26d9@mail.gmail.com> Hi, We have recently update kernel-xen on all of our hosts (3) and its vms all running fc6. kernel-xen 2.6.20-1.2962.fc6xen is doing good on two hosts and all its vms (10), however its giving lot of problem on third host. when i reboots the host into latest kernel-xen the domUs become unaccessible in a while hardly run for 10 minutes, 'xm list' still shows there status but i can't access it from outside. We are using loop back files for domUs File system, for testing i rebooted host into last working kernel 2.6.20-1.2952.fc6xen and domUs into latest kernel-xen and its doing pretty good, which mean latest kernel-xen is only giving problem at host side. when running 2.6.20-1.2962 on host it giving this in /var/log/messages Jul 12 10:42:45 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:42:50 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:42:50 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:42:55 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:42:55 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:00 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:00 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:05 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:05 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:10 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:10 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:15 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:15 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:20 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:20 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:25 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:25 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:30 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:30 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:35 xxxx kernel: printk: 4 messages suppressed. Thanks. Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From admin at dougware.net Thu Jul 12 13:18:08 2007 From: admin at dougware.net (Doug Eubanks) Date: Thu, 12 Jul 2007 09:18:08 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: 20070711152516.09872a99@mail.dougware.net Message-ID: <20070712131808.9742c519@mail.dougware.net> Any more ideas? I added more RAM last night (up to 1.5gigs now) and it still loops on the same error. Is the aic7xxx driver modular or is it built into the kernel? The only thing attached to that device is my DLT tape drive, and I was thinking I could remove it from the modules.conf file, rebuild my initrd and see what happens. Doug _____ From: Doug Eubanks [mailto:admin at dougware.net] To: fedora-xen at redhat.com Sent: Wed, 11 Jul 2007 11:25:16 -0400 Subject: Re: [Fedora-xen] Xen kernel doesn't boot for me It's there, here is my entire kernel line from grub root=/dev/VolGroup_RAID4/root acpi=noirq noapic apm=off rhgb quiet Doug _____ From: Richard W.M. Jones [mailto:rjones at redhat.com] To: Doug Eubanks [mailto:admin at dougware.net] Cc: fedora-xen at redhat.com [mailto:fedora-xen at redhat.com] Sent: Wed, 11 Jul 2007 05:58:01 -0400 Subject: Re: [Fedora-xen] Xen kernel doesn't boot for me Doug Eubanks wrote: > I am attaching two photos, one is the first error...the second is the > loop of errors. Can you try booting with noapic on the kernel command line. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- An HTML attachment was scrubbed... URL: From nooroon at gmail.com Thu Jul 12 15:29:04 2007 From: nooroon at gmail.com (mathieu rohon) Date: Thu, 12 Jul 2007 17:29:04 +0200 Subject: [Fedora-xen] xen 3.1 network Message-ID: <7675761b0707120829q75d536fcrcccd1d674e064e36@mail.gmail.com> Hello, i'd like to understand more deeply xen networking. My purpose is to modify the dscp ip field in guest's packet, to perform Qos, thanks to iptables. I'm using a FC7 with xen 3.1. I've installed a windows guest, with virt-manager, and I have used the default nat network option. Unfortunatelly, i couldn't use the bridge option because no network card was proposed! but this isn't the subject... I was quite surprised when i saw, in my xen-config.sxp : (network-script : network-bridge). it should be network-nat, am I wrong? the ifconfig command displays : lo Link encap:Boucle locale inet adr:127.0.0.1 Masque:255.0.0.0 adr inet6: ::1/128 Scope:H?te UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:731062 errors:0 dropped:0 overruns:0 frame:0 TX packets:731062 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:7695075004 (7.1 GiB) TX bytes:7695075004 (7.1 GiB) tap0 Link encap:Ethernet HWaddr 82:E3:26:59:DC:BF adr inet6: fe80::80e3:26ff:fe59:dcbf/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:17783 errors:0 dropped:0 overruns:0 frame:0 TX packets:513 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:500 RX bytes:24458454 (23.3 MiB) TX bytes:181392 (177.1 KiB) tmpbridge Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet adr:192.168.1.5 Bcast:192.168.1.255 Masque:255.255.255.0 adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:0 (0.0 b) TX bytes:9046 (8.8 KiB) vif11.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP 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 lg file transmission:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) virbr0 Link encap:Ethernet HWaddr 82:E3:26:59:DC:BF inet adr:192.168.122.1 Bcast:192.168.122.255 Masque: 255.255.255.0 adr inet6: fe80::200:ff:fe00:0/64 Scope:Lien UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21958 errors:0 dropped:0 overruns:0 frame:0 TX packets:1377 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 lg file transmission:0 RX bytes:24771762 (23.6 MiB) TX bytes:304511 (297.3 KiB) the "network-bridge status" displays : ============================================================ 1: lo: mtu 16436 qdisc noqueue link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: peth0: mtu 1500 qdisc pfifo_fast qlen 1000 link/ether 00:08:02:f5:71:e6 brd ff:ff:ff:ff:ff:ff 3: virbr0: mtu 1500 qdisc noqueue link/ether 82:e3:26:59:dc:bf brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 inet6 fe80::200:ff:fe00:0/64 scope link valid_lft forever preferred_lft forever 4: tmpbridge: mtu 1500 qdisc noqueue link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff inet 192.168.1.5/24 brd 192.168.1.255 scope global tmpbridge inet6 fe80::200:ff:fe00:0/64 scope link valid_lft forever preferred_lft forever 21: vif11.0: mtu 1500 qdisc pfifo_fast qlen 32 link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff 22: tap0: mtu 1500 qdisc pfifo_fast qlen 500 link/ether 82:e3:26:59:dc:bf brd ff:ff:ff:ff:ff:ff inet6 fe80::80e3:26ff:fe59:dcbf/64 scope link valid_lft forever preferred_lft forever it seems like the network-bridge scripts crashes, because the tmpbridge is not renamed, and when I start the xend service or when I run network-bridge start, the eth0 interface is disable!! can anyone helps me debug this situation? thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas at antony.eu Thu Jul 12 17:36:08 2007 From: thomas at antony.eu (Thomas Antony) Date: Thu, 12 Jul 2007 19:36:08 +0200 Subject: [Fedora-xen] virsh and virt-install examples Message-ID: <46966688.7020409@antony.eu> Hi, I'm running F7 x86_64 with Xen 3.1 and need some advice. I would be really happy if someone give me an example for adding a cdrom (a iso file) to a (running) domain with virsh and install Windows Server 2003 on a lvm lg with virt-install. thank you in advance, Thomas Antony From rjones at redhat.com Thu Jul 12 18:26:40 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Thu, 12 Jul 2007 19:26:40 +0100 Subject: [Fedora-xen] virsh and virt-install examples In-Reply-To: <46966688.7020409@antony.eu> References: <46966688.7020409@antony.eu> Message-ID: <46967260.9000403@redhat.com> Thomas Antony wrote: > Hi, > > I'm running F7 x86_64 with Xen 3.1 and need some advice. > I would be really happy if someone give me an example for adding a cdrom > (a iso file) to a (running) domain with virsh and install Windows Server > 2003 on a lvm lg with virt-install. Thomas, As long as your F7 is up to date, you should have a "virsh attach-device" command. Usage is along these lines: cat > cdrom.xml ^D virsh attach-device DOM cdrom.xml For virt-install I suggest reading the manpage. It has a million complicated options that you have to get right, and I've never installed W2K3 :-( But the manpage has some examples (although unfortunately not of a Windows install). Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From admin at dougware.net Fri Jul 13 16:34:47 2007 From: admin at dougware.net (Doug Eubanks) Date: Fri, 13 Jul 2007 12:34:47 -0400 Subject: [Fedora-xen] Xen kernel doesn't boot for me In-Reply-To: 4694A9A9.3070500@redhat.com Message-ID: <20070713163447.4ea98204@mail.dougware.net> Has there been any word on this yet? I have to admit, I'm getting so frustrated trying to get XEN going. Doug _____ From: Richard W.M. Jones [mailto:rjones at redhat.com] To: Doug Eubanks [mailto:admin at dougware.net] Cc: fedora-xen at redhat.com [mailto:fedora-xen at redhat.com] Sent: Wed, 11 Jul 2007 05:58:01 -0400 Subject: Re: [Fedora-xen] Xen kernel doesn't boot for me Doug Eubanks wrote: > I am attaching two photos, one is the first error...the second is the > loop of errors. Can you try booting with noapic on the kernel command line. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Sat Jul 14 10:31:38 2007 From: justin.conover at gmail.com (Justin Conover) Date: Sat, 14 Jul 2007 05:31:38 -0500 Subject: [Fedora-xen] Unable to open connection to hypervisor 'qemu:///system' Message-ID: virt-manager +kvm wont load up since the last rounds of F7 updates I think. Unable to open connection to hypervisor URI 'qemu:///system': virConnectOpenReadOnly() failed No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 68, in _connect_to_uri conn = self.get_connection(uri, readOnly) File "/usr/share/virt-manager/virtManager/engine.py", line 309, in get_connection conn = vmmConnection(self.get_config(), uri, readOnly) File "/usr/share/virt-manager/virtManager/connection.py", line 74, in __init__ self.vmm = libvirt.openReadOnly(openURI) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 132, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed No such file or directory [root at echelon ~]# lsmod |grep kvm kvm_amd 25813 1 kvm 75969 1 kvm_amd This works: [root at echelon kvm]# /usr/bin/qemu-kvm fedora7_1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From justin.conover at gmail.com Sat Jul 14 10:31:38 2007 From: justin.conover at gmail.com (Justin Conover) Date: Sat, 14 Jul 2007 05:31:38 -0500 Subject: [Fedora-xen] Unable to open connection to hypervisor 'qemu:///system' Message-ID: virt-manager +kvm wont load up since the last rounds of F7 updates I think. Unable to open connection to hypervisor URI 'qemu:///system': virConnectOpenReadOnly() failed No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 68, in _connect_to_uri conn = self.get_connection(uri, readOnly) File "/usr/share/virt-manager/virtManager/engine.py", line 309, in get_connection conn = vmmConnection(self.get_config(), uri, readOnly) File "/usr/share/virt-manager/virtManager/connection.py", line 74, in __init__ self.vmm = libvirt.openReadOnly(openURI) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 132, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed No such file or directory [root at echelon ~]# lsmod |grep kvm kvm_amd 25813 1 kvm 75969 1 kvm_amd This works: [root at echelon kvm]# /usr/bin/qemu-kvm fedora7_1 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- -- fedora-test-list mailing list fedora-test-list at redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list From veillard at redhat.com Sat Jul 14 11:34:49 2007 From: veillard at redhat.com (Daniel Veillard) Date: Sat, 14 Jul 2007 07:34:49 -0400 Subject: [Fedora-xen] Re: Unable to open connection to hypervisor 'qemu:///system' In-Reply-To: References: Message-ID: <20070714113449.GB19239@redhat.com> On Sat, Jul 14, 2007 at 05:31:38AM -0500, Justin Conover wrote: > virt-manager +kvm wont load up since the last rounds of F7 updates I think. > > Unable to open connection to hypervisor URI 'qemu:///system': > virConnectOpenReadOnly() failed No such file > or directory > Traceback (most recent call last): > File "/usr/share/virt-manager/virtManager/engine.py", line 68, in > _connect_to_uri > conn = self.get_connection(uri, readOnly) > File "/usr/share/virt-manager/virtManager/engine.py", line 309, in > get_connection > conn = vmmConnection(self.get_config(), uri, readOnly) > File "/usr/share/virt-manager/virtManager/connection.py", line 74, in > __init__ > self.vmm = libvirt.openReadOnly(openURI) > File "/usr/lib64/python2.5/site-packages/libvirt.py", line 132, in > openReadOnly > if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') > libvirtError: virConnectOpenReadOnly() failed No such file or directory > If you updated libvirt (from 0.2.3 to 0.3.0), make sure you don't have a libvirt_qemud running, if yes kill it and restart the libvirtd service, then you should have a libvirtd daemon running instead. This may or may not be the cause, hard to tell... 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 justin.conover at gmail.com Sat Jul 14 10:31:38 2007 From: justin.conover at gmail.com (Justin Conover) Date: Sat, 14 Jul 2007 05:31:38 -0500 Subject: [Fedora-xen] Unable to open connection to hypervisor 'qemu:///system' Message-ID: virt-manager +kvm wont load up since the last rounds of F7 updates I think. Unable to open connection to hypervisor URI 'qemu:///system': virConnectOpenReadOnly() failed No such file or directory Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/engine.py", line 68, in _connect_to_uri conn = self.get_connection(uri, readOnly) File "/usr/share/virt-manager/virtManager/engine.py", line 309, in get_connection conn = vmmConnection(self.get_config(), uri, readOnly) File "/usr/share/virt-manager/virtManager/connection.py", line 74, in __init__ self.vmm = libvirt.openReadOnly(openURI) File "/usr/lib64/python2.5/site-packages/libvirt.py", line 132, in openReadOnly if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') libvirtError: virConnectOpenReadOnly() failed No such file or directory [root at echelon ~]# lsmod |grep kvm kvm_amd 25813 1 kvm 75969 1 kvm_amd This works: [root at echelon kvm]# /usr/bin/qemu-kvm fedora7_1 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- -- fedora-test-list mailing list fedora-test-list at redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list From justin.conover at gmail.com Sun Jul 15 21:17:11 2007 From: justin.conover at gmail.com (Justin Conover) Date: Sun, 15 Jul 2007 16:17:11 -0500 Subject: [Fedora-xen] Re: Unable to open connection to hypervisor 'qemu:///system' In-Reply-To: <20070714113449.GB19239@redhat.com> References: <20070714113449.GB19239@redhat.com> Message-ID: On 7/14/07, Daniel Veillard wrote: > > On Sat, Jul 14, 2007 at 05:31:38AM -0500, Justin Conover wrote: > > virt-manager +kvm wont load up since the last rounds of F7 updates I > think. > > > > Unable to open connection to hypervisor URI 'qemu:///system': > > virConnectOpenReadOnly() failed No such > file > > or directory > > Traceback (most recent call last): > > File "/usr/share/virt-manager/virtManager/engine.py", line 68, in > > _connect_to_uri > > conn = self.get_connection(uri, readOnly) > > File "/usr/share/virt-manager/virtManager/engine.py", line 309, in > > get_connection > > conn = vmmConnection(self.get_config(), uri, readOnly) > > File "/usr/share/virt-manager/virtManager/connection.py", line 74, in > > __init__ > > self.vmm = libvirt.openReadOnly(openURI) > > File "/usr/lib64/python2.5/site-packages/libvirt.py", line 132, in > > openReadOnly > > if ret is None:raise libvirtError('virConnectOpenReadOnly() failed') > > libvirtError: virConnectOpenReadOnly() failed No such file or directory > > > > If you updated libvirt (from 0.2.3 to 0.3.0), make sure you don't > have a libvirt_qemud running, if yes kill it and restart the libvirtd > service, then you should have a libvirtd daemon running instead. > This may or may not be the cause, hard to tell... > > 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/ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen I don't know how or why but the other day I noticed from another error after downgrading libvirt that the package qemu was missing..... so I installed that, it worked. upgraded to the latest libvirt and libvirt-python and they work. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From felix.schwarz at web.de Mon Jul 16 16:12:05 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Mon, 16 Jul 2007 18:12:05 +0200 Subject: [Fedora-xen] No graphical console for HVM guests in F7? Message-ID: <469B98D5.2030702@web.de> Hi, I recently migrated my Xen guests to a new host running F7 (64 bit), the old one was FC6 (64 bit). After this migration, I do not have a graphical console for my hvm guests when I double click a vm in virt-manager. This worked in FC6 and it still works for pv guests. The only exception is my 32 bit (hvm) Fedora 7 guest which I created at the new host so it uses the new config system. This hvm guest is the only one which has a graphical console. I guess my problem is related to the Xen update from 3.0.3 -> 3.1 but I don't know how to enable graphical consoles... Thank you very much. fs From berrange at redhat.com Mon Jul 16 23:48:57 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 17 Jul 2007 00:48:57 +0100 Subject: [Fedora-xen] No graphical console for HVM guests in F7? In-Reply-To: <469B98D5.2030702@web.de> References: <469B98D5.2030702@web.de> Message-ID: <20070716234857.GC18128@redhat.com> On Mon, Jul 16, 2007 at 06:12:05PM +0200, Felix Schwarz wrote: > Hi, > > I recently migrated my Xen guests to a new host running F7 (64 bit), the > old one was FC6 (64 bit). After this migration, I do not have a graphical > console for my hvm guests when I double click a vm in virt-manager. This > worked in FC6 and it still works for pv guests. > > The only exception is my 32 bit (hvm) Fedora 7 guest which I created at the > new host so it uses the new config system. This hvm guest is the only one > which has a graphical console. > > I guess my problem is related to the Xen update from 3.0.3 -> 3.1 but I > don't know how to enable graphical consoles... Upstream changed the syntax in the config files for this, but there is supposed to be back-compatability support for the old syntax in there. You should file a bug about this not working. Anyway, old syntax was vnc=1 And one or more of vnclisten=1 vncunused=1 vncdisplay=4 vncpassword=xxxxx Now, it uses vfb = [ 'type=vnc,vncunsed=1,vncdisplay=5,vncpassword=xxxxx' ] So you may also wish to try updating the configs Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From felix.schwarz at web.de Tue Jul 17 04:45:28 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Tue, 17 Jul 2007 06:45:28 +0200 Subject: [Fedora-xen] No graphical console for HVM guests in F7? In-Reply-To: <20070716234857.GC18128@redhat.com> References: <469B98D5.2030702@web.de> <20070716234857.GC18128@redhat.com> Message-ID: <469C4968.2020803@web.de> Daniel P. Berrange schrieb: > Upstream changed the syntax in the config files for this, but there is > supposed to be back-compatability support for the old syntax in there. Thank you very much. Adding "vfb = [ 'type=vnc,vncunused=1' ]" fixed the issue for me (although I have to change nearly a dozen vm configurations...). > You should file a bug about this not working. [x] done https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=248497 fs From thewird at yahoo.com Tue Jul 17 09:32:11 2007 From: thewird at yahoo.com (thewird) Date: Tue, 17 Jul 2007 05:32:11 -0400 (EDT) Subject: [Fedora-xen] Xen only showing 16GB of ram out of 28GB Message-ID: <548939.76277.qm@web88312.mail.re4.yahoo.com> I installed FC6 and FC7 and the limit exists on both even though FC7 was supposed to be using a 64bit hypervisor which supports 32bit guests (which isn't the case). After various linux installs (including CentOS) and different configs (even replacing the hypervisor with its 64bit counterpart) I wasn't able to get a system showing all 28GB of ram AND work with 32bit guests. Out of desperation I bought "Virtualization with Xen" on Amazon for more insight. Although the book isn't too helpful since at least half of it if not more, is advertising the commercial XenSource (why would I buy an expensive Xen book if I wanted to use the newb commercial software?) I was able to figure out how to install the latest version of Xen 3.1 from source. I got it to boot perfectly and was expecting to see all of my 28GB of ram when I ran top but to my dismay it only showed 16GB once again... Can someone please help me and tell me what am I doing wrong. Or am I going about this the wrong way? Basically I want to see all of my 28GB of ram and run 32bit guests. I read everywhere this can be done but it never works. Thank you to anyone who can help me solve this. If money is the problem, please say so and that can be arranged. Marco Jorge From berrange at redhat.com Tue Jul 17 11:55:22 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 17 Jul 2007 12:55:22 +0100 Subject: [Fedora-xen] Xen only showing 16GB of ram out of 28GB In-Reply-To: <548939.76277.qm@web88312.mail.re4.yahoo.com> References: <548939.76277.qm@web88312.mail.re4.yahoo.com> Message-ID: <20070717115521.GA25303@redhat.com> On Tue, Jul 17, 2007 at 05:32:11AM -0400, thewird wrote: > I installed FC6 and FC7 and the limit exists on both even though FC7 > was supposed to be using a 64bit hypervisor which supports 32bit guests > (which isn't the case). After various linux installs (including CentOS) > and different configs (even replacing the hypervisor with its 64bit > counterpart) I wasn't able to get a system showing all 28GB of ram AND > work with 32bit guests. > > Out of desperation I bought "Virtualization with Xen" on Amazon for > more insight. Although the book isn't too helpful since at least half > of it if not more, is advertising the commercial XenSource (why would I > buy an expensive Xen book if I wanted to use the newb commercial > software?) I was able to figure out how to install the latest version > of Xen 3.1 from source. I got it to boot perfectly and was expecting to > see all of my 28GB of ram when I ran top but to my dismay it only > showed 16GB once again... What architecture did you compile with Xen 3.1 ? Because of the tricks Xen does on i386, even if you have PAE enabled you stil won't see more than 16 GB of RAM. I believe you need 64-bit HV to see all. You may or may not also need a 64-bit Dom0 - I don't know for sure since I'm not lucky enough to have more than 16 GB of RAM :-( > Can someone please help me and tell me what am I doing wrong. Or am I > going about this the wrong way? Basically I want to see all of my 28GB > of ram and run 32bit guests. I read everywhere this can be done but it > never works. Thank you to anyone who can help me solve this. If money > is the problem, please say so and that can be arranged. We're working on a kernl update for Fedora that will hopefully make it possible to really run 32-bit guests on 64-bit hypervisor. If you did a compile from upstream Xen 3.1 kenrel this should be working for you already though. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From arik at funke.eu Tue Jul 17 11:33:56 2007 From: arik at funke.eu (Arik Raffael Funke) Date: Tue, 17 Jul 2007 13:33:56 +0200 Subject: [Fedora-xen] No adsl in dom0 - Fedora 7 Message-ID: Hi, I am having problems establishing an adsl connection in dom0 (but ONLY in dom0, without xen everything is ok). Following is my setup/situation: 1. Installed clean Fedora 7 (with virtualization option selected) 2. Booted with the non-xen kernel & setup adsl. Adsl connection works without any problems. 3. Rebooted with xen kernel into dom0. 4. adsl connection can no longer be activated These are literally ALL the steps I took with the system. Thus, it is as "out of the box" as it can get. When trying to activate the adsl-connection in the (fedora?) gnome network configuration utility with the "activate" button I get (after about 1-2 minutes): Cannot activate network device dslModem! and in the textbox in the error message window it says: /usr/sbin/adsl-start: line 215: 3470 Terminated $CONNECT "$@" > /dev/null 2>&1 In /var/messages it says: Jul 17 00:08:21 gaia pppd[3494]: pppd 2.4.4 started by root, uid 0 Jul 17 00:08:21 gaia pppd[3494]: Using interface ppp0 Jul 17 00:08:21 gaia pppd[3494]: Connect: ppp0 <--> /dev/pts/1 Jul 17 00:08:52 gaia pppd[3494]: LCP: timeout sending Config-Requests Jul 17 00:08:52 gaia pppd[3494]: Connection terminated. Jul 17 00:08:52 gaia pppd[3494]: Modem hangup Jul 17 00:08:56 gaia pppoe[3495]: Timeout waiting for PADO packets Jul 17 00:08:56 gaia pppd[3494]: Exit. Jul 17 00:08:56 gaia pppoe-connect: PPPoE connection lost; attempting re-connection. Jul 17 00:09:01 gaia pppd[3569]: pppd 2.4.4 started by root, uid 0 Jul 17 00:09:01 gaia pppd[3569]: Using interface ppp0 Jul 17 00:09:01 gaia pppd[3569]: Connect: ppp0 <--> /dev/pts/1 Jul 17 00:09:32 gaia pppd[3569]: LCP: timeout sending Config-Requests Jul 17 00:09:32 gaia pppd[3569]: Connection terminated. Jul 17 00:09:32 gaia pppd[3569]: Modem hangup Jul 17 00:09:36 gaia pppoe[3570]: Timeout waiting for PADO packets Jul 17 00:09:36 gaia pppd[3569]: Exit. Can anybody tell me why adsl does not work in the fedora 7 dom0? It used to work just fine with fedora 6. How do I get it to work? I have however remarked another detail that I believe might be linked to (or the cause of?) my problem. In dom0 when trying to bring up my adsl connection I get the following line before the first error occurs: Jul 17 00:08:21 gaia pppd[3494]: Connect: ppp0 <--> /dev/pts/1 This line puzzles me because in four years I have never seen "/dev/pts/1" used to connect to my adsl modem. It was ALWAYS "/dev/pts/0"! Of course this might a perfectly appropriate renaming of devices as happens a lot with xen but... Can anybody shed any light on this? Cheers, Arik From kraxel at redhat.com Tue Jul 17 12:56:01 2007 From: kraxel at redhat.com (Gerd Hoffmann) Date: Tue, 17 Jul 2007 14:56:01 +0200 Subject: [Fedora-xen] Xen only showing 16GB of ram out of 28GB In-Reply-To: <548939.76277.qm@web88312.mail.re4.yahoo.com> References: <548939.76277.qm@web88312.mail.re4.yahoo.com> Message-ID: <469CBC61.7020308@redhat.com> thewird wrote: > I installed FC6 and FC7 and the limit exists on both even though FC7 > was supposed to be using a 64bit hypervisor which supports 32bit guests > (which isn't the case). WorksForMe[tm]. Test box with a bunch of systems installed, among them fedora7 32bit and fedora7 64bit. Booting the 32bit fedora dom0 with the 64bit hypervisor (aka /boot/xen.gz-) from the 64bit installation works just fine. If you got it right "xm dmesg" looks like this: [ ... ] (XEN) Xen kernel: 64-bit, lsb, compat32 (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc1000000 -> 0xc15e2000 [ ... ] The limitation is that the dom0 kernel backend drivers don't support 32-on-64, so you can't mix 32bit and 64bit domains. As long as dom0 and all guests are identical it works. cheers, Gerd From kraxel at redhat.com Tue Jul 17 13:03:59 2007 From: kraxel at redhat.com (Gerd Hoffmann) Date: Tue, 17 Jul 2007 15:03:59 +0200 Subject: [Fedora-xen] Xen only showing 16GB of ram out of 28GB In-Reply-To: <20070717115521.GA25303@redhat.com> References: <548939.76277.qm@web88312.mail.re4.yahoo.com> <20070717115521.GA25303@redhat.com> Message-ID: <469CBE3F.1000806@redhat.com> Hi, > than 16 GB of RAM. I believe you need 64-bit HV to see all. You may or > may not also need a 64-bit Dom0 - I don't know for sure since I'm not > lucky enough to have more than 16 GB of RAM :-( Dom0 can be 32bit (and must be in fedora7 if you want run 32bit guests and don't wait for the kernel update). With a 32bit hypervisor everything must fit into the hypervisor address space hole. With a 64bit hypervisor only the m2p table must fit into the address space hole. Thus even 32bit guests can see much more memory when running on a 64bit hypervisor. The limit is far beyond 64GB (was some odd number, 166GB IIRC), although I'd be prepared to run into bugs when crossing the 64GB border ... cheers, Gerd From thewird at yahoo.com Tue Jul 17 20:18:38 2007 From: thewird at yahoo.com (thewird) Date: Tue, 17 Jul 2007 16:18:38 -0400 (EDT) Subject: [Fedora-xen] Xen only showing 16GB of ram out of 28GB In-Reply-To: <469CBC61.7020308@redhat.com> Message-ID: <682513.65244.qm@web88315.mail.re4.yahoo.com> > > I installed FC6 and FC7 and the limit exists on both even though > FC7 > > was supposed to be using a 64bit hypervisor which supports 32bit > guests > > (which isn't the case). > > WorksForMe[tm]. Test box with a bunch of systems installed, among > them > fedora7 32bit and fedora7 64bit. Booting the 32bit fedora dom0 with > the > 64bit hypervisor (aka /boot/xen.gz-) from the 64bit > installation works just fine. > > If you got it right "xm dmesg" looks like this: > [ ... ] > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 32-bit, PAE, lsb, paddr 0xc1000000 -> 0xc15e2000 > [ ... ] > > The limitation is that the dom0 kernel backend drivers don't support > 32-on-64, so you can't mix 32bit and 64bit domains. As long as dom0 > and > all guests are identical it works. > > cheers, > Gerd > I've tried this before. I installed FC7 32bit and replaced the xen.gz with its 64bit version. Sure, it boots fine but when I try to boot up/install a 32bit guest, the guest just hangs or pauses and will not run even though the dom0 seems to be working just fine. Marco Jorge From rwarsow at online.de Tue Jul 17 21:51:35 2007 From: rwarsow at online.de (Ronald Warsow) Date: Tue, 17 Jul 2007 23:51:35 +0200 Subject: [Fedora-xen] No adsl in dom0 - Fedora 7 In-Reply-To: References: Message-ID: <469D39E7.6020501@online.de> Arik Raffael Funke wrote: > Hi, > > I am having problems establishing an adsl connection in dom0 (but ONLY > in dom0, without xen everything is ok). Following is my setup/situation: > > 1. Installed clean Fedora 7 (with virtualization option selected) > 2. Booted with the non-xen kernel & setup adsl. Adsl connection works > without any problems. > 3. Rebooted with xen kernel into dom0. > 4. adsl connection can no longer be activated > > These are literally ALL the steps I took with the system. Thus, it is as > "out of the box" as it can get. > > > When trying to activate the adsl-connection in the (fedora?) gnome > network configuration utility with the "activate" button I get (after > about 1-2 minutes): > > Cannot activate network device dslModem! > > and in the textbox in the error message window it says: > > /usr/sbin/adsl-start: line 215: 3470 Terminated $CONNECT > "$@" > /dev/null 2>&1 > > > In /var/messages it says: > > Jul 17 00:08:21 gaia pppd[3494]: pppd 2.4.4 started by root, uid 0 > Jul 17 00:08:21 gaia pppd[3494]: Using interface ppp0 > Jul 17 00:08:21 gaia pppd[3494]: Connect: ppp0 <--> /dev/pts/1 > Jul 17 00:08:52 gaia pppd[3494]: LCP: timeout sending Config-Requests > Jul 17 00:08:52 gaia pppd[3494]: Connection terminated. > Jul 17 00:08:52 gaia pppd[3494]: Modem hangup > Jul 17 00:08:56 gaia pppoe[3495]: Timeout waiting for PADO packets > Jul 17 00:08:56 gaia pppd[3494]: Exit. > Jul 17 00:08:56 gaia pppoe-connect: PPPoE connection lost; attempting > re-connection. > Jul 17 00:09:01 gaia pppd[3569]: pppd 2.4.4 started by root, uid 0 > Jul 17 00:09:01 gaia pppd[3569]: Using interface ppp0 > Jul 17 00:09:01 gaia pppd[3569]: Connect: ppp0 <--> /dev/pts/1 > Jul 17 00:09:32 gaia pppd[3569]: LCP: timeout sending Config-Requests > Jul 17 00:09:32 gaia pppd[3569]: Connection terminated. > Jul 17 00:09:32 gaia pppd[3569]: Modem hangup > Jul 17 00:09:36 gaia pppoe[3570]: Timeout waiting for PADO packets > Jul 17 00:09:36 gaia pppd[3569]: Exit. > > > Can anybody tell me why adsl does not work in the fedora 7 dom0? It used > to work just fine with fedora 6. How do I get it to work? did you try on the command line: pppoe -I eth0 -A to test, if you can see your Access Concentrator ? (assuming your network device is eth0 *and* up) there are some more options for pppoe (currently not installed on my box) to investigate more. > > > I have however remarked another detail that I believe might be linked to > (or the cause of?) my problem. > > In dom0 when trying to bring up my adsl connection I get the following > line before the first error occurs: > > Jul 17 00:08:21 gaia pppd[3494]: Connect: ppp0 <--> /dev/pts/1 > > This line puzzles me because in four years I have never seen > "/dev/pts/1" used to connect to my adsl modem. It was ALWAYS > "/dev/pts/0"! Of course this might a perfectly appropriate renaming of > devices as happens a lot with xen but... > > Can anybody shed any light on this? > > Cheers, > Arik > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Ronald From thewird at yahoo.com Wed Jul 18 09:23:54 2007 From: thewird at yahoo.com (thewird) Date: Wed, 18 Jul 2007 05:23:54 -0400 (EDT) Subject: [Fedora-xen] Paravirtualized on FC5/6 or CentOS4/5 with 64bit hypervisor? Message-ID: <443968.72187.qm@web88307.mail.re4.yahoo.com> I have 32bit FC7 installed and I replaced the hypervisor (xen.gz) with its 64bit version by extracting the RPM in order to allow me to see my 28GB of ram. Everything works fine and I can install both 32bit and 64bit FC7's paravirtualized. However, when I try to install (32bit) FC5/6 or Centos4/5 paravirtualized, it will not work. The VNC windows doesn't pop up and I notice the guest shuts down. They work fine if installed as fully virtualized guests as they should. Anything I need to do to make paravirtualized work with these Distro's? Thanks to everyone whos been helping this Xen beginner along. On a side note, when I tried installing FreeBSD 6.2 fully virtualized, it also didn't work. When I tried installing Debian, the install booted fine and I was setting up the install when virtmanager complained about something saying the install didn't work (even though it was running fine) and closed/deleted the VM. Marco Jorge From asraikhn at gmail.com Wed Jul 18 10:29:23 2007 From: asraikhn at gmail.com (Asrai khn) Date: Wed, 18 Jul 2007 15:29:23 +0500 Subject: [Fedora-xen] easy way to configure domU Message-ID: <5f0f8dba0707180329n398a1bfld3dba708628d7658@mail.gmail.com> Hi I am wondering is there an easy way to configure domU (vm) quickly, atm we are using eg LV (Logical Volumes) to storge root, var and swap for VM and then using disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] to launch it. We takes the tar gunzip of file system of root, var of currently running vm and when need arrives we just have to created LVs and untar the achieves and launch the new vm with very little changes. Only one problem in this approach is that we get little outdated vm which need to update using 'yum'. So is there a way to start new vm fast and using currently updated running vm file system? Thanks. Askar. -------------- next part -------------- An HTML attachment was scrubbed... URL: From arik at funke.eu Wed Jul 18 11:01:48 2007 From: arik at funke.eu (Arik Raffael Funke) Date: Wed, 18 Jul 2007 13:01:48 +0200 Subject: [Fedora-xen] Re: No adsl in dom0 - Fedora 7 In-Reply-To: <469D39E7.6020501@online.de> References: <469D39E7.6020501@online.de> Message-ID: Ronald Warsow wrote: > Arik Raffael Funke wrote: >> I am having problems establishing an adsl connection in dom0 (but ONLY >> in dom0, without xen everything is ok). Following is my setup/situation: ...snipp... >> Can anybody tell me why adsl does not work in the fedora 7 dom0? It >> used to work just fine with fedora 6. How do I get it to work? > > did you try on the command line: > > pppoe -I eth0 -A > > to test, if you can see your Access Concentrator ? > > (assuming your network device is eth0 *and* up) I now did. It just says: pppoe: Timeout waiting for PADO packets Any other ideas that might help me diagnose the problem? - Arik From rob at comwifinet.com Wed Jul 18 13:02:15 2007 From: rob at comwifinet.com (Rob Dyke) Date: Wed, 18 Jul 2007 14:02:15 +0100 Subject: [Fedora-xen] easy way to configure domU In-Reply-To: <5f0f8dba0707180329n398a1bfld3dba708628d7658@mail.gmail.com> References: <5f0f8dba0707180329n398a1bfld3dba708628d7658@mail.gmail.com> Message-ID: <469E0F57.60707@comwifinet.com> Asrai, I build from my own mirror of fedora/rhel installation source using kickstart files... I can build a new domU in about 15 minutes with a tight package selection based on the server task. You could also look at http://xen-tools.org/index.html Rob Asrai khn wrote: > Hi I am wondering is there an easy way to configure domU (vm) quickly, > atm we are using eg LV (Logical Volumes) to storge root, var and swap > for VM and then using > > disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] to launch it. > > We takes the tar gunzip of file system of root, var of currently > running vm and when need arrives we just have to created LVs and > untar the achieves and launch the new vm with very little changes. > > Only one problem in this approach is that we get little outdated vm > which need to update using 'yum'. So is there a way to start new vm > fast and using currently updated running vm file system? > > Thanks. Askar. > ------------------------------------------------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From acathrow at redhat.com Wed Jul 18 13:41:45 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Wed, 18 Jul 2007 09:41:45 -0400 Subject: [Fedora-xen] easy way to configure domU In-Reply-To: <469E0F57.60707@comwifinet.com> References: <5f0f8dba0707180329n398a1bfld3dba708628d7658@mail.gmail.com> <469E0F57.60707@comwifinet.com> Message-ID: <1184766105.19306.22.camel@aic-f7.cathrow.org> On Wed, 2007-07-18 at 14:02 +0100, Rob Dyke wrote: > Asrai, > > I build from my own mirror of fedora/rhel installation source using > kickstart files... I can build a new domU in about 15 minutes with a > tight package selection based on the server task. > > You could also look at http://xen-tools.org/index.html Have you looking into Cobbler for remote provisioning? http://cobbler.et.redhat.com > > Rob > > Asrai khn wrote: > > Hi I am wondering is there an easy way to configure domU (vm) quickly, > > atm we are using eg LV (Logical Volumes) to storge root, var and swap > > for VM and then using > > > > disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] to launch it. > > > > We takes the tar gunzip of file system of root, var of currently > > running vm and when need arrives we just have to created LVs and > > untar the achieves and launch the new vm with very little changes. > > > > Only one problem in this approach is that we get little outdated vm > > which need to update using 'yum'. So is there a way to start new vm > > fast and using currently updated running vm file system? > > > > Thanks. Askar. > > ------------------------------------------------------------------------ > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob at comwifinet.com Wed Jul 18 15:27:43 2007 From: rob at comwifinet.com (Rob Dyke) Date: Wed, 18 Jul 2007 16:27:43 +0100 Subject: [Fedora-xen] easy way to configure domU In-Reply-To: <1184766105.19306.22.camel@aic-f7.cathrow.org> References: <5f0f8dba0707180329n398a1bfld3dba708628d7658@mail.gmail.com> <469E0F57.60707@comwifinet.com> <1184766105.19306.22.camel@aic-f7.cathrow.org> Message-ID: <469E316F.20806@comwifinet.com> I had previously... and now I look again (new shiny website) "Whether you run a large datacenter, a campus lab, or just have a handfull of machines on a home network, cobbler can help you perform installations and updates faster." I have 10 virtual machines over two physical machines.... no shared storage (yet), nothing clustered, all manually created and managed. I think that I can do everything I need to with virt-manager, kickstart... I've been reading around the website - cobbler and koan will clearly meet Asrai's needs rob Andrew Cathrow wrote: > On Wed, 2007-07-18 at 14:02 +0100, Rob Dyke wrote: >> Asrai, >> >> I build from my own mirror of fedora/rhel installation source using >> kickstart files... I can build a new domU in about 15 minutes with a >> tight package selection based on the server task. >> >> You could also look at http://xen-tools.org/index.html >> > > Have you looking into Cobbler for remote provisioning? > > http://cobbler.et.redhat.com > >> Rob >> >> Asrai khn wrote: >> > Hi I am wondering is there an easy way to configure domU (vm) quickly, >> > atm we are using eg LV (Logical Volumes) to storge root, var and swap >> > for VM and then using >> > >> > disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] to launch it. >> > >> > We takes the tar gunzip of file system of root, var of currently >> > running vm and when need arrives we just have to created LVs and >> > untar the achieves and launch the new vm with very little changes. >> > >> > Only one problem in this approach is that we get little outdated vm >> > which need to update using 'yum'. So is there a way to start new vm >> > fast and using currently updated running vm file system? >> > >> > Thanks. Askar. >> > ------------------------------------------------------------------------ >> > >> > -- >> > Fedora-xen mailing list >> > Fedora-xen at redhat.com >> > https://www.redhat.com/mailman/listinfo/fedora-xen >> > >> >> -- >> Fedora-xen mailing list >> Fedora-xen at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-xen >> From arik at funke.eu Wed Jul 18 15:43:52 2007 From: arik at funke.eu (Arik Raffael Funke) Date: Wed, 18 Jul 2007 17:43:52 +0200 Subject: [Fedora-xen] Possible to delegate hardware to domU? Message-ID: Hi, is it possible to hide hardware from dom0 and delegate it to a domU with the out-of-the-box Fedora xen? I.e. with pciback. I would like to delegate a network interface to one of my domU's. Can anybody confirm either that it is or that it is not possible? Thanks. - Arik From arik at funke.eu Wed Jul 18 15:44:40 2007 From: arik at funke.eu (Arik Raffael Funke) Date: Wed, 18 Jul 2007 17:44:40 +0200 Subject: [Fedora-xen] Possible to delegate hardware to domU? Message-ID: Hi, is it possible to hide hardware from dom0 and delegate it to a domU with the out-of-the-box Fedora xen? I.e. with pciback. I would like to delegate a network interface to one of my domU's. Can anybody confirm either that it is or that it is not possible? Thanks. - Arik From chris at tylers.info Wed Jul 18 16:47:11 2007 From: chris at tylers.info (Chris Tyler) Date: Wed, 18 Jul 2007 12:47:11 -0400 Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: <20070718152805.CBCB9732F4@hormel.redhat.com> References: <20070718152805.CBCB9732F4@hormel.redhat.com> Message-ID: <1184777231.4078.327.camel@concord3.proximity.on.ca> On Wed, 2007-07-18 at 11:28 -0400, Asrai khn wrote: > Hi I am wondering is there an easy way to configure domU (vm) quickly, > atm we are using eg LV (Logical Volumes) to storge root, var and swap > for VM and then using disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] > to launch it. > > We takes the tar gunzip of file system of root, var of currently > running vm and when need arrives we just have to created LVs and > untar the achieves and launch the new vm with very little changes. > > Only one problem in this approach is that we get little outdated vm > which need to update using 'yum'. So is there a way to start new vm > fast and using currently updated running vm file system? > > Thanks. Askar. You could use LVM snapshots. They're copy-on-write, so they can be created quickly. Of course, if you start a new VM on a snapshot of a running VM, then the filesystem will not be clean (it will look as though it was from a system that was turned off without being shutdown). -- Chris Tyler http://dailypackage.fedorabook.com/ From bjenkins at cait.org Wed Jul 18 17:17:52 2007 From: bjenkins at cait.org (Bill Jenkins) Date: Wed, 18 Jul 2007 12:17:52 -0500 Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: <1184777231.4078.327.camel@concord3.proximity.on.ca> References: <20070718152805.CBCB9732F4@hormel.redhat.com> <1184777231.4078.327.camel@concord3.proximity.on.ca> Message-ID: <469E4B40.70806@cait.org> Chris Tyler wrote: > On Wed, 2007-07-18 at 11:28 -0400, Asrai khn wrote: > >> Hi I am wondering is there an easy way to configure domU (vm) quickly, >> atm we are using eg LV (Logical Volumes) to storge root, var and swap >> for VM and then using disk = [ 'phy:vg/myvmdisk1,sda1,w', ... ,... ] >> to launch it. >> >> We takes the tar gunzip of file system of root, var of currently >> running vm and when need arrives we just have to created LVs and >> untar the achieves and launch the new vm with very little changes. >> >> Only one problem in this approach is that we get little outdated vm >> which need to update using 'yum'. So is there a way to start new vm >> fast and using currently updated running vm file system? >> >> Thanks. Askar. >> > > You could use LVM snapshots. They're copy-on-write, so they can be > created quickly. Of course, if you start a new VM on a snapshot of a > running VM, then the filesystem will not be clean (it will look as > though it was from a system that was turned off without being shutdown). > > -- > Chris Tyler > http://dailypackage.fedorabook.com/ I've found an easy way is just to use dd. dd if=/dev/VolGroup00/virtual-1 of=/dev/VolGroup00/virtual-2 bs=1M I've tried LVM snapshots, but found that sometimes they seemed to run slowly, and if you made a copy of a copy, they ran even more slowly. Perhaps they work fine under some conditions, but they didn't for me. dd, however, has never failed me. Just remember to start it up in console mode first, and change the ip address. Also, (you probably know this, but), don't forget to change the mac address and uuid when you copy the xen config file (and rename the machine, too.) Bill Jenkins CAIT, Western Illinois University From rwarsow at online.de Wed Jul 18 17:19:32 2007 From: rwarsow at online.de (Ronald Warsow) Date: Wed, 18 Jul 2007 19:19:32 +0200 Subject: [Fedora-xen] Re: No adsl in dom0 - Fedora 7 In-Reply-To: References: <469D39E7.6020501@online.de> Message-ID: <469E4BA4.6000300@online.de> Arik Raffael Funke wrote: > Ronald Warsow wrote: >> Arik Raffael Funke wrote: >>> I am having problems establishing an adsl connection in dom0 (but >>> ONLY in dom0, without xen everything is ok). Following is my >>> setup/situation: > ...snipp... >>> Can anybody tell me why adsl does not work in the fedora 7 dom0? It >>> used to work just fine with fedora 6. How do I get it to work? >> >> did you try on the command line: >> >> pppoe -I eth0 -A >> >> to test, if you can see your Access Concentrator ? >> >> (assuming your network device is eth0 *and* up) > > I now did. It just says: > > pppoe: Timeout waiting for PADO packets > > Any other ideas that might help me diagnose the problem? Does this mean you *can* see the mac address of your AC ? and you can't connect to it ? this and the related links(end of the site) http://en.wikipedia.org/wiki/Point-to-Point_Protocol_over_Ethernet but this should help to investigate: 1. can you ping another box over this link ? no ? => bug/configuration problem with *your* nic/network stack 2. can you see the mac address of your AC ? (pppoe options) no ? AC not reachable => try with none xen kernel: no ? => try later. but you reported this part works with none xen kernel. 3. you can reach your AC (you see the AC mac address) and you need to debug it (see pppoe debug options) to see why => your adsl connection setting is faulty - i try to remember - => /etc/ppp/pppd.conf or something like that; look for debug, esp. timeout parameter settings, there are some ! > > - Arik > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Ronald From suhopdu at umich.edu Wed Jul 18 18:28:50 2007 From: suhopdu at umich.edu (Hope Dundas) Date: Wed, 18 Jul 2007 14:28:50 -0400 (EDT) Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: <469E4B40.70806@cait.org> References: <20070718152805.CBCB9732F4@hormel.redhat.com> <1184777231.4078.327.camel@concord3.proximity.on.ca> <469E4B40.70806@cait.org> Message-ID: On Wed, 18 Jul 2007, Bill Jenkins wrote: > I've found an easy way is just to use dd. > > dd if=/dev/VolGroup00/virtual-1 of=/dev/VolGroup00/virtual-2 bs=1M > > I've tried LVM snapshots, but found that sometimes they seemed to run > slowly, and if you made a copy of a copy, they ran even more slowly. > Perhaps they work fine under some conditions, but they didn't for me. > dd, however, has never failed me. Just remember to start it up in > console mode first, and change the ip address. Also, (you probably know > this, but), don't forget to change the mac address and uuid when you > copy the xen config file (and rename the machine, too.) > > Bill Jenkins > CAIT, Western Illinois University Hi Bill, I've been grappling with just this issue (at least, I *think* we're talking about the same thing) - trying to take an existing 'image' of a virtual box and tweak it to use as a base for creating other virtual boxes. One thing, though - if you're using full virtualization (as we are, under Red Hat Enterprise Linux 5), can you still use the console? I've been trying to start the base domU using 'xm create domainname -c', but it just bounces me to a '?' prompt that doesn't allow any input, and the only way I can get out of it is to use another connection to shutdown the domain. I've also tried using 'xm console domainname' to connect to the domain when it is already running, but I get the same response. Many thanks, Hope Dundas ~~~ Hope Dundas, hope.dundas at umich.edu Database/Systems Administrator Housing Information Technology Office University of Michigan From arik at funke.eu Wed Jul 18 21:19:21 2007 From: arik at funke.eu (Arik Raffael Funke) Date: Wed, 18 Jul 2007 23:19:21 +0200 Subject: [Fedora-xen] Re: No adsl in dom0 - Fedora 7 In-Reply-To: <469E4BA4.6000300@online.de> References: <469D39E7.6020501@online.de> <469E4BA4.6000300@online.de> Message-ID: Ronald Warsow wrote: > Arik Raffael Funke wrote: >> Ronald Warsow wrote: >>> did you try on the command line: >>> >>> pppoe -I eth0 -A >>> >>> to test, if you can see your Access Concentrator ? >>> >>> (assuming your network device is eth0 *and* up) >> >> I now did. It just says: >> >> pppoe: Timeout waiting for PADO packets >> >> Any other ideas that might help me diagnose the problem? > > Does this mean you *can* see the mac address of your AC ? and > you can't connect to it ? No, I cannot see the mac address of the AC when in dom0. Following is the exact result. In non-xen kernel: (adsl works) =============================== [root at gaia ~]# pppoe -I eth0 -A Access-Concentrator: ULMC03-10k Got a cookie: ea 64 c2 d8 c9 f6 70 96 72 27 c2 72 eb 23 fb 1d AC-Ethernet-Address: 00:19:e8:6e:70:31 -------------------------------------------------- [root at gaia ~]# In xen-kernel, dom0: (adsl does not work) ========================================= [root at gaia ~]# pppoe -I eth0 -A pppoe: Timeout waiting for PADO packets [root at gaia ~]# Something must be the problem with the xen-kernel or the linux setup when the xen-kernel is chosen at bootup, or? With best regards, Arik From rwarsow at online.de Wed Jul 18 22:50:56 2007 From: rwarsow at online.de (Ronald Warsow) Date: Thu, 19 Jul 2007 00:50:56 +0200 Subject: [Fedora-xen] Re: No adsl in dom0 - Fedora 7 In-Reply-To: References: <469D39E7.6020501@online.de> <469E4BA4.6000300@online.de> Message-ID: <469E9950.9060905@online.de> Arik Raffael Funke wrote: > Ronald Warsow wrote: >> Arik Raffael Funke wrote: >>> Ronald Warsow wrote: >>>> did you try on the command line: >>>> >>>> pppoe -I eth0 -A >>>> >>>> to test, if you can see your Access Concentrator ? >>>> >>>> (assuming your network device is eth0 *and* up) >>> >>> I now did. It just says: >>> >>> pppoe: Timeout waiting for PADO packets >>> >>> Any other ideas that might help me diagnose the problem? >> >> Does this mean you *can* see the mac address of your AC ? and >> you can't connect to it ? > > No, I cannot see the mac address of the AC when in dom0. Following is > the exact result. > > In non-xen kernel: (adsl works) > =============================== > [root at gaia ~]# pppoe -I eth0 -A > Access-Concentrator: ULMC03-10k > Got a cookie: ea 64 c2 d8 c9 f6 70 96 72 27 c2 72 eb 23 fb 1d > AC-Ethernet-Address: 00:19:e8:6e:70:31 > -------------------------------------------------- > [root at gaia ~]# > > > In xen-kernel, dom0: (adsl does not work) > ========================================= > [root at gaia ~]# pppoe -I eth0 -A > pppoe: Timeout waiting for PADO packets > [root at gaia ~]# > > > Something must be the problem with the xen-kernel or the linux setup > when the xen-kernel is chosen at bootup, or? I'm no developer, (RHCE) only, but i would say so. search for a / fill a bug report then. > > With best regards, > Arik > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Ronald From bjenkins at cait.org Thu Jul 19 01:37:09 2007 From: bjenkins at cait.org (Bill Jenkins) Date: Wed, 18 Jul 2007 20:37:09 -0500 (CDT) Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: Message-ID: <19272508.34431184809029075.JavaMail.root@vanadium.sys.ma.cait.org> We are probably talking about the same thing. We have lots of multiprocessor machines that we like to set up identically. In the case of the latest machines, that means I take one virtual machine, set it up like I like it with LDAP, directory mounts, perl scripts, etc, and then clone that one seven times with dd. As I copy, I boot them into single-user mode and change the hostname and ip, and once over with, I've got eight identical machines, other than hostname and ip. Some of the perl stuff is pretty tedious, so it saves a lot of time. I've found that if I do an "xm create virtualmachinename -c" from the command line, I'll get the normal startup sequence, and then I can enter single user mode and change the ip and such. Sometimes it seems like the command-line console doesn't work, so instead I run virt-manager and get a console window that way. But unless something messed up with dd, I always get a console somewhere. I will mention that I usually stop domains before dd-ing them; I have made good copies of domains while they were running, but sometimes it messes them up...is what I've described what you'd like to accomplish? I've used the procedure to clone probably 50 or so domains. The developers sometimes want a different OS to run apps on, so I just go and re-copy a fresh OS when they do. Oh by the way, I've experimented with dd-ing domains through gzip into a file, and restoring from a file, which works sometimes. Bill Jenkins CAIT,Western Illinois University | | Hi Bill, | | I've been grappling with just this issue (at least, I *think* we're | talking about the same thing) - trying to take an existing 'image' of | a | virtual box and tweak it to use as a base for creating other virtual | boxes. | | One thing, though - if you're using full virtualization (as we are, | under | Red Hat Enterprise Linux 5), can you still use the console? I've been | | trying to start the base domU using 'xm create domainname -c', but it | just | bounces me to a '?' prompt that doesn't allow any input, and the only | way | I can get out of it is to use another connection to shutdown the | domain. | I've also tried using 'xm console domainname' to connect to the domain | | when it is already running, but I get the same response. | | Many thanks, | | Hope Dundas | | ~~~ | Hope Dundas, hope.dundas at umich.edu | Database/Systems Administrator | Housing Information Technology Office | University of Michigan From taoj2 at cs.rpi.edu Thu Jul 19 01:56:45 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Wed, 18 Jul 2007 21:56:45 -0400 (EDT) Subject: [Fedora-xen] Virtual Machine Migration Problems with Fedora Core XEN Message-ID: <1244.128.213.11.199.1184810205.squirrel@webmail.cs.rpi.edu> Hi, (Sorry for the really long question :P) I was trying to do the VM migration with Fedora Core XEN. The configuration is like this: Source Host: Host1, OS is Fedora Core 6 Destination Host: Host2, OS is Fedora Core 6 Both of the two hosts are of the same hardware architecture. I have installed a XEN guest, XEN1, at Host1. The operating system of XEN1 is also Fedora Core 6. What I wanted to do is to migrate XEN1 from Host1 to Host2. Before doing the migration, the xend could be started successfully, and I can use the system tool, Virtual Machine Manager, of Fedora Core to see the information of all domains. To enable the migration, (1) First, I changed the configuration file, /etc/xen/xend-config.sxp at HOST1, change is as following: #(xend-unix-server yes) (xend-relocation-server yes) (xend-relocation-port 8002) (xend-relocation-address ? ?) (xend-relocation-hosts-allow host2) #(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') /etc/xen/xend-config.sxp at HOST2, change is as following: #(xend-unix-server yes) (xend-relocation-server yes) (xend-relocation-port 8002) (xend-relocation-address ? ?) (xend-relocation-hosts-allow host1) #(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$') ?? Should I use (xend-relocation-hosts-allow '') instead of (xend-relocation-hosts-allow host1) ? Then I restart the xend: "service xend restart" However the system tool, Virtual Machine Manager,of Fedora Core, can't run. After I click the "connect", the following error msg appears: Unable to open a connection to the Xen Hypervisor/daemon Verify that: -A Xen host kernel was booted -The Xen service has been started It's weird. Because I can use "service xend status" to show that xend is running and use "xm list" to show that Domain-0 is running. But Virtual Machine Manager doesn't work. ?? (2) Second, configure NFS to export a shared storage via NFS. The shared storage can be accessed from HOST1 and HOST2. (3) Third, run "xm create -c XEN1" However, Some error messages appear, they are as follows: Using config file "/etc/xen/xen1". Going to boot Fedora Core (2.6.19-1.2911.6.5.fc6xen) kernel: /vmlinuz-2.6.19-1.2911.6.5.fc6xen initrd: /initrd-2.6.19-1.2911.6.5.fc6xen.img Started domain xen1 PCI: Fatal: No config space access function found rtc: IRQ 8 is not free. i8042.c: No controller found. What is the reason of this problem? And "xm list" shows that XEN1 is there. ?? Since the guest can't be started. I shutdown it. And following msg appears: hcid[1318]: segfault at 00002aac0123b8a0 rip 00002aaaaacec014 rsp 00007fff7d5f9010 error 4 IPv6 over IPv4 tunneling driver md: stopping all md devices. System halted. (4) To enable the migration, do I need to change the security level and firewall, for example, the firewall should be enabled or disabled, and add any trusted ports besides the default ones. The SELinux should be enforced, permited, or disabled? What changes do I need to make at the source and destination hosts? Thanks for you time. Best Wishes Angel From jerutley at gmail.com Thu Jul 19 02:07:16 2007 From: jerutley at gmail.com (Jeremy Utley) Date: Wed, 18 Jul 2007 19:07:16 -0700 Subject: [Fedora-xen] Re: No adsl in dom0 - Fedora 7 In-Reply-To: References: <469D39E7.6020501@online.de> <469E4BA4.6000300@online.de> Message-ID: On 7/18/07, Arik Raffael Funke wrote: > In xen-kernel, dom0: (adsl does not work) > ========================================= > [root at gaia ~]# pppoe -I eth0 -A > pppoe: Timeout waiting for PADO packets > [root at gaia ~]# > > > Something must be the problem with the xen-kernel or the linux setup > when the xen-kernel is chosen at bootup, or? Remember that as part of the Xen init process, the "real" eth0 is renamed to peth0, and connected to xenbr0 giving your other machines access to the network. It's very possible that this might be screwing with things for your pppoe software - maybe try using peth0 as the interface name on the pppoe command line? However, you're going to run into problems with giving your Xen VM's access to the DSL without some major changes to their init scripts so that your Xen DomU's use a nat provided to them by Dom0. Jeremy From asraikhn at gmail.com Thu Jul 19 12:32:01 2007 From: asraikhn at gmail.com (Asrai khn) Date: Thu, 19 Jul 2007 17:32:01 +0500 Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: <19272508.34431184809029075.JavaMail.root@vanadium.sys.ma.cait.org> References: <19272508.34431184809029075.JavaMail.root@vanadium.sys.ma.cait.org> Message-ID: <5f0f8dba0707190532y661461f0p1085e4ca9abdf5d9@mail.gmail.com> Hi, Thanks every body who have contributed the way you people setup xen VM quickly, now I have lot of options/ideas and I hope next time it wouldn't be hard to setup vm fast :) Thanks and regards, Askar -------------- next part -------------- An HTML attachment was scrubbed... URL: From suhopdu at umich.edu Thu Jul 19 15:08:45 2007 From: suhopdu at umich.edu (Hope Dundas) Date: Thu, 19 Jul 2007 11:08:45 -0400 (EDT) Subject: No UDP? - was Re: [Fedora-xen] Re: easy way to configure domU In-Reply-To: <19272508.34431184809029075.JavaMail.root@vanadium.sys.ma.cait.org> References: <19272508.34431184809029075.JavaMail.root@vanadium.sys.ma.cait.org> Message-ID: Hi Bill, thanks for writing back. :) My odd problem seems to be that I can get nearly everything working on the new, cloned box except for DNS. And in particular, DNS over UDP - I can use dig +tcp to force resolution over TCP, but it otherwise just hangs thusly: ; <<>> DiG 9.3.3rc2 <<>> @x.x.x.x domain.com ; (1 server found) ;; global options: printcmd ;; connection timed out; no servers could be reached [root at hsg-vdev ~]# nslookup behaves the same way. Has anyone else seen this? This is the second clone I've taken of the original box (which has never had any issues with DNS). I'm doing a lot of looking via google, and have seen many references to bad udp checksums, but when I run tcpdump -nvvi eth0 port 53 it shows the checksums as OK. Aside: Because we're using full virtualization (RHEL5, x86_64), the console isn't available by default (needs to be conf'd in grub.conf prior to boot), I wasn't able to access it that way, and so the first boot was to normal runlevel - I couldn't figure out how to make the freshly-created machine boot to single user. I did stop the source machine before doing the dd of it, and got a randomly generated uuid and MAC address. If anyone has seen this behavior before and knows of a fix, please let me know. Many thanks, Hope Dundas > | Hope Dundas, hope.dundas at umich.edu > | Database/Systems Administrator > | Housing Information Technology Office > | University of Michigan From ajwynn at gmail.com Thu Jul 19 16:42:15 2007 From: ajwynn at gmail.com (Tony Wynn) Date: Thu, 19 Jul 2007 11:42:15 -0500 Subject: [Fedora-xen] Hotplug scripts not working error Message-ID: <68f667fc0707190942k5bcb05ber2e4a808acc1e3a5f@mail.gmail.com> Hi, I'm trying to create a Xen image on Fedora 6. I'm using the virt-manager GUI. After it attempts to create the domain, it error out with the following: Unable to complete install 'libvirt.libvirtError virDomainCreateLinux() failed POST operation failed: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.') Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/create.py", line 681, in do_install dom = guest.start_install(False, meter = meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 649, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.4/site-packages/virtinst/Guest.py", line 666, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib64/python2.4/site-packages/libvirt.py", line 503, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST operation failed: (xend.err'Device 0 (vif) could not be connected. Hotplug scripts not working.') ' While configuring the network I chose "Virtual Network" because nothing was displayed in the drop down for "Shared Physical Device". I've searched but haven't been able to find much that seems like it applies. If anyone has any ideas, I would appreciate it. Thanks, Tony -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Thu Jul 19 16:50:27 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 19 Jul 2007 17:50:27 +0100 Subject: [Fedora-xen] [FW: Fedora Core 6 Test Update: python-virtinst-0.200.0-1.fc6] Message-ID: <20070719165027.GD26669@redhat.com> FYI, we have just pushed an update of python-virtinst to updates-testing in FC6, F7 and rawhide which includes the new 'virt-clone' tool for making copies of domains. We also have new improved input validation and manual pages describing both virt-install and virt-clone Assuming no major problems are discovered I'll move it from updates-testing into updates in about a week's time ----- Forwarded message from Daniel Berrange ----- > Date: Thu, 19 Jul 2007 12:19:59 -0400 > From: "Daniel Berrange" > To: fedora-test-list at redhat.com > Subject: Fedora Core 6 Test Update: python-virtinst-0.200.0-1.fc6 > > --------------------------------------------------------------------- > Fedora Test Update Notification > FEDORA-2007-639 > 2007-07-19 > --------------------------------------------------------------------- > > Product : Fedora Core 6 > Name : python-virtinst > Version : 0.200.0 > Release : 1.fc6 > Summary : Python modules for starting Xen guest installations > Description : > virtinst is a module to help in starting installations of Fedora/Red > Hat Enterprise Linux related distributions inside of virtual machines. It > supports both paravirt guests (for which only FC and RHEL guests are > currently supported) as well as fully virtualized guests. It uses > libvirt (http://www.libvirt.org) for starting things. > > Also contained is a simple script virt-install which uses > virtinst in a command line mode. > > --------------------------------------------------------------------- > Update Information: > > This release introduces the virt-clone tool which provides > the ability to clone an existing inactive guest. The disk > images will be copied, new MAC address, UUID and name will > be given to the guest. Documentation is improved with the > addition of manual pages for both virt-install and > virt-clone. Validation of input parameters has been further > enhanced, and re-factored to allow sharing with > virt-manager. The virt-install tool can be used to boot live > CD images, with or without underlying storage. > --------------------------------------------------------------------- > * Wed Jul 18 2007 Daniel P. Berrange - 0.200.0-1.fc6 > - Updated to 0.200.0 > - Added virt-clone tool > - Added manual pages > * Mon Jun 25 2007 Daniel P. Berrange - 0.103.0-2.fc6 > - Re-add missing patch for import statement > > --------------------------------------------------------------------- > This update can be downloaded from: > http://download.fedora.redhat.com/pub/fedora/linux/core/updates/testing/6/ > > 279aed241deb461186143a7dc347a43d977ab2f7 SRPMS/python-virtinst-0.200.0-1.fc6.src.rpm > 279aed241deb461186143a7dc347a43d977ab2f7 noarch/python-virtinst-0.200.0-1.fc6.src.rpm > 4cd9dc9685ae9e2fbd42cbe9298f3f17746111f0 x86_64/python-virtinst-0.200.0-1.fc6.noarch.rpm > 4cd9dc9685ae9e2fbd42cbe9298f3f17746111f0 i386/python-virtinst-0.200.0-1.fc6.noarch.rpm > > This update can be installed with the 'yum' update program. Use 'yum update > package-name' at the command line. For more information, refer to 'Managing > Software with yum,' available at http://fedora.redhat.com/docs/yum/. > --------------------------------------------------------------------- > > -- > fedora-test-list mailing list > fedora-test-list at redhat.com > To unsubscribe: > https://www.redhat.com/mailman/listinfo/fedora-test-list > ----- End forwarded message ----- Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From Travis.Formoso at blueslate.net Thu Jul 19 19:44:48 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 19 Jul 2007 15:44:48 -0400 Subject: [Fedora-xen] Upgrading Xen machines Message-ID: All, Right now I am in the process of migrating our Fedora Core 4 servers to Fedora Core 6. I set up the new xen server and transferred all the files from the old server to the new one. The directory structure has root.img, swap.img, and xmconfig. If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using config file "/xen/sec-int-dns/xmconfig". Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU So it is looking for the older files which it should considering that is what is the xmconfig file. What is the best way to create the xen virtual machine from the root.img file and then do the upgrade to FC6? Any tips and pointers would be helpful - thank you, Travis ________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso at blueslate.net This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From Travis.Formoso at blueslate.net Thu Jul 19 19:51:21 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 19 Jul 2007 15:51:21 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: Minor update: I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and then ran: xm create -c /xen/sec-int-dns/xmconfig and got this error: Error: (22, 'Invalid argument') Thanks -----Original Message----- From: Formoso, Travis Sent: Thursday, July 19, 2007 3:44 PM To: 'fedora-xen at redhat.com' Subject: Upgrading Xen machines All, Right now I am in the process of migrating our Fedora Core 4 servers to Fedora Core 6. I set up the new xen server and transferred all the files from the old server to the new one. The directory structure has root.img, swap.img, and xmconfig. If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using config file "/xen/sec-int-dns/xmconfig". Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU So it is looking for the older files which it should considering that is what is the xmconfig file. What is the best way to create the xen virtual machine from the root.img file and then do the upgrade to FC6? Any tips and pointers would be helpful - thank you, Travis ________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso at blueslate.net This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From berrange at redhat.com Thu Jul 19 19:52:32 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 19 Jul 2007 20:52:32 +0100 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: References: Message-ID: <20070719195232.GI26669@redhat.com> On Thu, Jul 19, 2007 at 03:51:21PM -0400, Formoso, Travis wrote: > Minor update: > > I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and then ran: > > xm create -c /xen/sec-int-dns/xmconfig and got this error: > > Error: (22, 'Invalid argument') I'm guesing you're trying a i386 kernel here ? FC4 is using the obsolete non-PAE kernels, while FC6 and later are all PAE. You can't mix & match a PAE and non-PAE kernels in host & guest. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From Travis.Formoso at blueslate.net Thu Jul 19 19:55:45 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Thu, 19 Jul 2007 15:55:45 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: Looking at the log files I did catch this: [root at xen5 xen]# cat /var/log/xen/xend-debug.log Nothing to flush. Nothing to flush. ERROR: Will only load images built for Xen v3.0 ERROR: Error constructing guest OS Anyone know what I could do to get this up and running? > Minor update: > I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and > > then ran: > xm create -c /xen/sec-int-dns/xmconfig and got this error: > Error: (22, 'Invalid argument') > Thanks --- > All, > Right now I am in the process of migrating our Fedora Core 4 servers to >Fedora Core 6. I set up the new xen server and transferred all the files > > from the old server to the new one. >The directory structure has root.img, swap.img, and xmconfig. >If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using >config file "/xen/sec-int-dns/xmconfig". >Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU >So it is looking for the older files which it should considering that is >what is the xmconfig file. >What is the best way to create the xen virtual machine from the root.img >file and then do the upgrade to FC6? >Any tips and pointers would be helpful - thank you, >Travis ________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso at blueslate.net This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From taoj2 at cs.rpi.edu Fri Jul 20 02:23:38 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Thu, 19 Jul 2007 22:23:38 -0400 (EDT) Subject: [Fedora-xen] New Virtual Machine Migration Problems with Fedora Core XEN Message-ID: <2484.128.213.11.199.1184898218.squirrel@webmail.cs.rpi.edu> Hi, As to the previous email (Virtual Machine Migration Problems with Fedora Core XEN), I have some ways to solve the problem. To enable the Virtual Machine Manager to run, after changing the configuration file /etc/xen/xend-config.sxp, The line #(xend-unix-server yes) shouldn't be commented. However I have some new problems when I did the migration. During the migration process, I can use "xm list" at source and destination hosts to show what domains are running. It shows that XEN1 (the guest domain that I want to migrate from source to destination host) is migrated, since at source host, the domain name, XEN1, becomes migrate-XEN1, and at destination host, one more domain, XEN1, appears. But after the migration is finished, both of the two hosts don't have domain XEN1. As far as I know, the virtual machine migration just migrate XEN1 from one host to another. XEN1 should be at the destination host after the migration completes. right? It seems that XEN1 flies away. ?? Or maybe the migration is not successful. The domain list shown by "xm list" are not real. ?? And at the source host, I can use "xm create -c XEN1" to start the domain XEN1 again. really weird !! And it can be migrated to the same destination again. Anybody has similar experiences before or know how to slove this problem? Thanks for you time. Best Wishes Angel From orenault at redhat.com Thu Jul 19 16:52:01 2007 From: orenault at redhat.com (Olivier Renault) Date: Thu, 19 Jul 2007 18:52:01 +0200 Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: References: <20070718152805.CBCB9732F4@hormel.redhat.com> <1184777231.4078.327.camel@concord3.proximity.on.ca> <469E4B40.70806@cait.org> Message-ID: <469F96B1.8030607@redhat.com> > > One thing, though - if you're using full virtualization (as we are, > under Red Hat Enterprise Linux 5), can you still use the console? I've > been trying to start the base domU using 'xm create domainname -c', but > it just bounces me to a '?' prompt that doesn't allow any input, and the > only way I can get out of it is to use another connection to shutdown > the domain. I've also tried using 'xm console domainname' to connect to > the domain when it is already running, but I get the same response. if you are using full virt the -c will not worked. You can still mount the partition from the VM directly on your system. You may want to look at kpartx ( if you are using lvm in your guest )/ lomount ( if no LVM in guest ) to achieve it. Regards, Olivier From eeraltan at enssat.fr Fri Jul 20 07:35:22 2007 From: eeraltan at enssat.fr (Emre ERALTAN) Date: Fri, 20 Jul 2007 09:35:22 +0200 Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: <469F96B1.8030607@redhat.com> References: <20070718152805.CBCB9732F4@hormel.redhat.com> <1184777231.4078.327.camel@concord3.proximity.on.ca> <469E4B40.70806@cait.org> <469F96B1.8030607@redhat.com> Message-ID: Hi, I have the same console problem with Full Virtualization... As I am not using any graphic card, I would have liked to use a serial console to connect to my Full Virtualized DomU's console. Do anybody knows how to do this ? thanks -- - - - - - - - - - - - - - - - - - - - - - - - - - Emre ERALTAN El?ve ing?nieur 3?me ann?e Electronique et Informatique Industrielle ENSSAT - - - - - - - - - - - - - - - - - - - - - - - - - On 7/19/07, Olivier Renault wrote: > > > > > One thing, though - if you're using full virtualization (as we are, > > under Red Hat Enterprise Linux 5), can you still use the console? I've > > been trying to start the base domU using 'xm create domainname -c', but > > it just bounces me to a '?' prompt that doesn't allow any input, and the > > only way I can get out of it is to use another connection to shutdown > > the domain. I've also tried using 'xm console domainname' to connect to > > the domain when it is already running, but I get the same response. > > if you are using full virt the -c will not worked. > > You can still mount the partition from the VM directly on your system. > You may want to look at kpartx ( if you are using lvm in your guest )/ > lomount ( if no LVM in guest ) to achieve it. > > Regards, > Olivier > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > -------------- next part -------------- An HTML attachment was scrubbed... URL: From clalance at redhat.com Fri Jul 20 12:22:31 2007 From: clalance at redhat.com (Chris Lalancette) Date: Fri, 20 Jul 2007 08:22:31 -0400 Subject: [Fedora-xen] Re: easy way to configure domU In-Reply-To: References: <20070718152805.CBCB9732F4@hormel.redhat.com> <1184777231.4078.327.camel@concord3.proximity.on.ca> <469E4B40.70806@cait.org> <469F96B1.8030607@redhat.com> Message-ID: <46A0A907.2080307@redhat.com> Emre ERALTAN wrote: > Hi, > > I have the same console problem with Full Virtualization... As I am not > using any graphic card, I would have liked to use a serial console to > connect to my Full Virtualized DomU's console. Do anybody knows how to > do this ? > Yes, it is actually all setup, you really just need to tell your virtual machine to use the serial console. So for instance, on the kernel command-line (in grub) inside the domain, you would add: console=ttyS0,115200 to the "kernel" line, and reboot. You should also be able to tell grub to use the serial console to allow you to select kernels, but I haven't tried that personally. Chris Lalancette From cochranb at speakeasy.net Sat Jul 21 17:50:46 2007 From: cochranb at speakeasy.net (Robert L Cochran) Date: Sat, 21 Jul 2007 13:50:46 -0400 Subject: [Fedora-xen] AMD Opteron Quad Core CPU Availability Message-ID: <46A24776.3070102@speakeasy.net> Can anyone suggest a good retail source of AMD Opteron CPUs when the quad core versions become available? Also what would be a good motherboard for these CPUs. I assume the quad core units (all versions and price levels of them) support full virtualization. Thanks Bob Cochran Greenbelt, Maryland, USA From itamar at ispbrasil.com.br Sat Jul 21 18:38:06 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sat, 21 Jul 2007 15:38:06 -0300 Subject: [Fedora-xen] Fw: [Xen-users] Congratulations to Xen team! Message-ID: <003601c7cbc6$4a803db0$fe01a8c0@ispbrasil> fowarding take a look ----- Original Message ----- From: "Tom Mornini" To: "xen-users" Sent: Saturday, July 21, 2007 3:34 PM Subject: [Xen-users] Congratulations to Xen team! > http://kerneltrap.org/node/13917 > > This is very important to us. > > Looking forward to continuous current kernel support! > > -- > -- Tom Mornini, CTO > -- Engine Yard, Ruby on Rails Hosting > -- Support, Scalability, Reliability > -- (866) 518-YARD (9273) > -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 From itamar at ispbrasil.com.br Sat Jul 21 18:38:21 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sat, 21 Jul 2007 15:38:21 -0300 Subject: [Fedora-xen] Fw: [Xen-users] Congratulations to Xen team! Message-ID: <003d01c7cbc6$51acf100$fe01a8c0@ispbrasil> fowarding take a look http://kerneltrap.org/node/13917 ----- Original Message ----- From: "Tom Mornini" To: "xen-users" Sent: Saturday, July 21, 2007 3:34 PM Subject: [Xen-users] Congratulations to Xen team! > http://kerneltrap.org/node/13917 > > This is very important to us. > > Looking forward to continuous current kernel support! > > -- > -- Tom Mornini, CTO > -- Engine Yard, Ruby on Rails Hosting > -- Support, Scalability, Reliability > -- (866) 518-YARD (9273) > -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 From berrange at redhat.com Sat Jul 21 18:47:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 21 Jul 2007 19:47:24 +0100 Subject: [Fedora-xen] Fw: [Xen-users] Congratulations to Xen team! In-Reply-To: <003d01c7cbc6$51acf100$fe01a8c0@ispbrasil> References: <003d01c7cbc6$51acf100$fe01a8c0@ispbrasil> Message-ID: <20070721184724.GB27107@redhat.com> On Sat, Jul 21, 2007 at 03:38:21PM -0300, Itamar Reis Peixoto wrote: > fowarding > > take a look > > http://kerneltrap.org/node/13917 Yes, we welcome this step forward towards a full Xen merge in LKML - it is a critical move for Xen to be sustainable as part of Fedora. It is, however, only a partial solution at this time, so we can't actually make any real use of it in Fedora yet. At minimal we need architecture coverage - x86_64 in particular. Second we need support for using a single bzImage for both bare metal and Xen - the initial merge still produces separate binaries for Xen. Once those two are complete we'll be able to use the mainline kernels for the guest. Focus is then on also merging Dom0 bits - with that we'll have a much more sustainable solution. Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From itamar at ispbrasil.com.br Sat Jul 21 19:14:51 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Sat, 21 Jul 2007 16:14:51 -0300 Subject: [Fedora-xen] Fw: [Xen-users] Congratulations to Xen team! References: <003d01c7cbc6$51acf100$fe01a8c0@ispbrasil> <20070721184724.GB27107@redhat.com> Message-ID: <000a01c7cbcb$6b9895b0$fe01a8c0@ispbrasil> also there are lguest in 2.6.23 lguest will be compiled as module in new fedora kernels ? -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 From berrange at redhat.com Sat Jul 21 19:25:23 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Sat, 21 Jul 2007 20:25:23 +0100 Subject: [Fedora-xen] Fw: [Xen-users] Congratulations to Xen team! In-Reply-To: <000a01c7cbcb$6b9895b0$fe01a8c0@ispbrasil> References: <003d01c7cbc6$51acf100$fe01a8c0@ispbrasil> <20070721184724.GB27107@redhat.com> <000a01c7cbcb$6b9895b0$fe01a8c0@ispbrasil> Message-ID: <20070721192523.GC27107@redhat.com> On Sat, Jul 21, 2007 at 04:14:51PM -0300, Itamar Reis Peixoto wrote: > also there are lguest in 2.6.23 > > lguest will be compiled as module in new fedora kernels ? We've no plans to include lguest in the Fedora kernels at this time. Again it is only available for i386. Its current purpose is as a means for kernel developers to research & experiment with virtualization ideas - not for end users to put into real world use - there is Xen & KVM for real world use in production. There are also no tools for managing lguest instances since it is mostly targetted for kernel hackers. Signs are that some of the ideas from lguest may merge into KVM allowing it to do paravirt without hardware support - if this happens it would be a better choice for Fedora that using lguest directly since we've already got management tools around KVM. So we're basically intending to 'wait & see' wrt to lguest and not enable it in Fedora at this time. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From thewird at yahoo.com Sun Jul 22 01:29:01 2007 From: thewird at yahoo.com (thewird) Date: Sat, 21 Jul 2007 21:29:01 -0400 (EDT) Subject: [Fedora-xen] Fedora 7 Update to 64bit hypervisor simple? Message-ID: <342156.90937.qm@web88312.mail.re4.yahoo.com> I've been trying to get Xen to see all my ram (28GB) and work with 32bit paravirtualized guests for the past 1.5 months. I have been unable to do so after exhausting all the suggestions given in the mailing lists. The closest I could get was by replacing the hypervisor with its 64bit version manually which did work but only Fedora 7 paravirtualized guests would install. It has been mentioned a few times here that a hypervisor update will be made eventually to update it to a 64bit hypervisor which would allow me to see my 28GB of ram and work with 32bit guests. I was thinking I should just put the server live creating guests with 16GB of ram available. What I wanted to know is when the update finally occurs, will I be able to simply do a yum update, reboot, and then all 28GB of ram will show and the previous guests will still continue to work? Will it be that simple? Thanks. Marco Jorge From fedora.lists at burns.me.uk Sun Jul 22 14:31:32 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sun, 22 Jul 2007 15:31:32 +0100 Subject: [Fedora-xen] Win2k3 domU has lost NIC Message-ID: Fedora 7 with xen3.1, and domU HVM Win2K3 all 64bit Was all working fine and domU had been shitdown/restarted several times and still worked. Now the domU starts up, but no NIC but has not NIC, so obviously I can't RDP to the server, but can still get in using VNC console in Device manager, the NIC is now absent and the only yellow question mark is for the "driverless" xenbus PCI device which was there previously. Many other domU using Fedora paravirt are still fine so I don't suspect general xen or bridge issues. from the dom0 dmesg when starting the windows domU I see device vif13.0 entered promiscuous mode ADDRCONF(NETDEV_UP): vif13.0: link is not ready where when starting other domUs I see ADDRCONF(NETDEV_UP): vif12.0: link is not ready ADDRCONF(NETDEV_CHANGE): vif12.0: link becomes ready eth0: port 7(vif12.0) entering learning state eth0: topology change detected, propagating eth0: port 7(vif12.0) entering forwarding state vif12.0: no IPv6 routers present xm dmesg doesn't show anything Can I get any info out of qemu-dm that might help? Suggestions welcome .... From fedora.lists at burns.me.uk Sun Jul 22 14:52:51 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sun, 22 Jul 2007 15:52:51 +0100 Subject: [Fedora-xen] Re: Win2k3 domU has lost NIC In-Reply-To: References: Message-ID: On 22/07/07, Andy Burns wrote: > Now the domU starts up, but has no NIC Info from xend.log [2007-07-22 15:57:11 2743] DEBUG (SrvDomain:76) Starting domain win2k3 False [2007-07-22 15:57:11 2743] DEBUG (XendDomainInfo:1463) XendDomainInfo.constructDomain [2007-07-22 15:57:11 2743] DEBUG (balloon:113) Balloon: 2252 KiB free; need 2048; done. [2007-07-22 15:57:11 2743] DEBUG (XendDomain:443) Adding Domain: 13 [2007-07-22 15:57:11 2743] DEBUG (XendDomainInfo:1517) XendDomainInfo.initDomain: 13 256 [2007-07-22 15:57:12 2743] DEBUG (image:330) args: boot, val: c [2007-07-22 15:57:12 2743] DEBUG (image:330) args: fda, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: fdb, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: soundhw, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: localtime, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: serial, val: pty [2007-07-22 15:57:12 2743] DEBUG (image:330) args: std-vga, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: isa, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: acpi, val: 1 [2007-07-22 15:57:12 2743] DEBUG (image:330) args: usb, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: usbdevice, val: None [2007-07-22 15:57:12 2743] DEBUG (image:330) args: k, val: None [2007-07-22 15:57:12 2743] DEBUG (XendDomainInfo:1549) _initDomain:shadow_memory=0x5, memory_static_max=0x1f400000, memory_static_min =0x0. [2007-07-22 15:57:12 2743] DEBUG (balloon:119) Balloon: 1216 KiB free; 0 to scrub; need 525312; retries: 20. [2007-07-22 15:57:12 2743] DEBUG (balloon:134) Balloon: setting dom0 target to 4638 MiB. [2007-07-22 15:57:12 2743] DEBUG (XendDomainInfo:581) Setting memory target of domain Domain-0 (0) to 4638 MiB. [2007-07-22 15:57:12 2743] DEBUG (XendDomainInfo:873) Storing domain details: {'name': 'Domain-0', 'console/limit': '1048576', 'memor y/target': '4749312', 'vm': '/vm/00000000-0000-0000-0000-000000000000', 'domid': '0', 'cpu/0/availability': 'online', 'cpu/1/availabi lity': 'online', 'control/platform-feature-multiprocessor-suspend': '1'} [2007-07-22 15:57:12 2743] DEBUG (balloon:113) Balloon: 525504 KiB free; need 525312; done. [2007-07-22 15:57:12 2743] INFO (image:129) buildDomain os=hvm dom=13 vcpus=1 [2007-07-22 15:57:12 2743] DEBUG (image:278) domid = 13 [2007-07-22 15:57:12 2743] DEBUG (image:279) image = /usr/lib/xen/boot/hvmloader [2007-07-22 15:57:12 2743] DEBUG (image:280) store_evtchn = 2 [2007-07-22 15:57:12 2743] DEBUG (image:281) memsize = 500 [2007-07-22 15:57:12 2743] DEBUG (image:282) vcpus = 1 [2007-07-22 15:57:12 2743] DEBUG (image:283) pae = 1 [2007-07-22 15:57:12 2743] DEBUG (image:284) acpi = 1 [2007-07-22 15:57:12 2743] DEBUG (image:285) apic = 1 [2007-07-22 15:57:12 2743] INFO (XendDomainInfo:1365) createDevice: vkbd : {'devid': 0, 'uuid': '7e8804b0-7569-63cd-eb69-1813eb032caa ', 'backend': '0'} [2007-07-22 15:57:12 2743] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/doma in/0/backend/vkbd/13/0'} to /local/domain/13/device/vkbd/0. [2007-07-22 15:57:12 2743] DEBUG (DevController:117) DevController: writing {'frontend-id': '13', 'domain': 'win2k3', 'frontend': '/l ocal/domain/13/device/vkbd/0', 'state': '1', 'online': '1'} to /local/domain/0/backend/vkbd/13/0. [2007-07-22 15:57:12 2743] INFO (XendDomainInfo:1365) createDevice: vfb : {'vncunused': '1', 'devid': None, 'type': 'vnc', 'uuid': '3 410926a-9c4e-bc26-19f1-99744c1d498b', 'other_config': {'vncunused': '1', 'type': 'vnc'}} [2007-07-22 15:57:12 2743] DEBUG (DevController:115) DevController: writing {'state': '1', 'backend-id': '0', 'backend': '/local/doma in/0/backend/vfb/13/0'} to /local/domain/13/device/vfb/0. [2007-07-22 15:57:12 2743] DEBUG (DevController:117) DevController: writing {'vncunused': '1', 'domain': 'win2k3', 'frontend': '/loca l/domain/13/device/vfb/0', 'uuid': '3410926a-9c4e-bc26-19f1-99744c1d498b', 'state': '1', 'online': '1', 'frontend-id': '13', 'type': 'vnc'} to /local/domain/0/backend/vfb/13/0. [2007-07-22 15:57:12 2743] INFO (XendDomainInfo:1365) createDevice: vbd : {'uuid': 'ec3cdf4c-1f75-eb4b-6840-f2ab19ddf213', 'bootable' : 1, 'devid': 768, 'driver': 'paravirtualised', 'dev': 'hda:disk', 'uname': 'phy:/dev/vgmirror/lv-w2k3test', 'mode': 'w', 'backend': '0'} [2007-07-22 15:57:12 2743] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'virtual-device': '768', 'device-type ': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/13/768'} to /local/domain/13/device/vbd/768. [2007-07-22 15:57:12 2743] DEBUG (DevController:117) DevController: writing {'domain': 'win2k3', 'frontend': '/local/domain/13/device /vbd/768', 'uuid': 'ec3cdf4c-1f75-eb4b-6840-f2ab19ddf213', 'dev': 'hda', 'state': '1', 'params': '/dev/vgmirror/lv-w2k3test', 'mode': 'w', 'online': '1', 'frontend-id': '13', 'type': 'phy'} to /local/domain/0/backend/vbd/13/768. [2007-07-22 15:57:12 2743] INFO (XendDomainInfo:1365) createDevice: vbd : {'uuid': '733f9e8a-6873-04cf-51fc-3888581cdfbc', 'bootable' : 0, 'devid': 832, 'driver': 'paravirtualised', 'dev': 'hdb:disk', 'uname': 'file:/root/1830_usa_ddk.iso', 'mode': 'w', 'backend': '0 '} [2007-07-22 15:57:12 2743] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'virtual-device': '832', 'device-type ': 'disk', 'state': '1', 'backend': '/local/domain/0/backend/vbd/13/832'} to /local/domain/13/device/vbd/832. [2007-07-22 15:57:12 2743] DEBUG (DevController:117) DevController: writing {'domain': 'win2k3', 'frontend': '/local/domain/13/device /vbd/832', 'uuid': '733f9e8a-6873-04cf-51fc-3888581cdfbc', 'dev': 'hdb', 'state': '1', 'params': '/root/1830_usa_ddk.iso', 'mode': 'w ', 'online': '1', 'frontend-id': '13', 'type': 'file'} to /local/domain/0/backend/vbd/13/832. [2007-07-22 15:57:12 2743] INFO (XendDomainInfo:1365) createDevice: vif : {'bridge': 'eth0', 'uuid': '281b6bcf-9f2b-70cf-8248-ea6ab52 55207', 'script': 'vif-bridge', 'devid': 0, 'mac': '00:16:3e:78:5d:29', 'type': 'netfront', 'backend': '0'} [2007-07-22 15:57:12 2743] DEBUG (DevController:115) DevController: writing {'backend-id': '0', 'mac': '00:16:3e:78:5d:29', 'handle': '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/13/0'} to /local/domain/13/device/vif/0. [2007-07-22 15:57:12 2743] DEBUG (DevController:117) DevController: writing {'bridge': 'eth0', 'domain': 'win2k3', 'handle': '0', 'uu id': '281b6bcf-9f2b-70cf-8248-ea6ab5255207', 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': '/local/domain/13/dev ice/vif/0', 'mac': '00:16:3e:78:5d:29', 'online': '1', 'frontend-id': '13', 'type': 'netfront'} to /local/domain/0/backend/vif/13/0. [2007-07-22 15:57:12 2743] INFO (image:445) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', ' 13', '-vcpus', '1', '-boot', 'c', '-serial', 'pty', '-acpi', '-domain-name', 'win2k3', '-vncunused', '-vnclisten', '127.0.0.1'] [2007-07-22 15:57:12 2743] INFO (image:449) device model pid: 20981 [2007-07-22 15:57:12 2743] DEBUG (XendDomainInfo:2022) Storing VM details: {'on_xend_stop': 'ignore', 'shadow_memory': '5', 'uuid': ' 55999ca9-81c8-5d69-2496-c9d831657acc', 'on_reboot': 'restart', 'start_time': '1185116232.92', 'on_poweroff': 'destroy', 'on_xend_star t': 'ignore', 'on_crash': 'restart', 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'image': '(hvm (kernel /usr/lib/xen/ boot/hvmloader) (acpi 1) (apic 1) (boot c) (device_model /usr/lib64/xen/bin/qemu-dm) (pae 1) (rtc_timeoffset 0) (serial pty) (notes ( SUSPEND_CANCEL 1)))', 'name': 'win2k3'} [2007-07-22 15:57:12 2743] DEBUG (XendDomainInfo:873) Storing domain details: {'console/port': '3', 'name': 'win2k3', 'console/limit' : '1048576', 'vm': '/vm/55999ca9-81c8-5d69-2496-c9d831657acc', 'domid': '13', 'image/suspend-cancel': '1', 'cpu/0/availability': 'onl ine', 'memory/target': '512000', 'control/platform-feature-multiprocessor-suspend': '1', 'store/ring-ref': '127998', 'store/port': '2 '} [2007-07-22 15:57:13 2743] DEBUG (DevController:148) Waiting for devices vif. [2007-07-22 15:57:13 2743] DEBUG (XendDomainInfo:957) XendDomainInfo.handleShutdownWatch [2007-07-22 15:57:13 2743] DEBUG (DevController:153) Waiting for 0. [2007-07-22 15:57:13 2743] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status. [2007-07-22 15:57:13 2743] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vif/13/0/hotplug-status. [2007-07-22 15:57:13 2743] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-07-22 15:57:13 2743] DEBUG (DevController:148) Waiting for devices usb. [2007-07-22 15:57:13 2743] DEBUG (DevController:148) Waiting for devices vbd. [2007-07-22 15:57:13 2743] DEBUG (DevController:153) Waiting for 768. [2007-07-22 15:57:13 2743] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/13/768/hotplug-status. [2007-07-22 15:57:13 2743] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/13/768/hotplug-status. [2007-07-22 15:57:13 2743] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-07-22 15:57:13 2743] DEBUG (DevController:153) Waiting for 832. [2007-07-22 15:57:13 2743] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/13/832/hotplug-status. [2007-07-22 15:57:14 2743] DEBUG (DevController:556) hotplugStatusCallback /local/domain/0/backend/vbd/13/832/hotplug-status. [2007-07-22 15:57:14 2743] DEBUG (DevController:570) hotplugStatusCallback 1. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices irq. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices vkbd. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices vfb. [2007-07-22 15:57:14 2743] DEBUG (vfbif:100) skip waiting for HVM vfb [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices console. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices pci. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices ioports. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices tap. [2007-07-22 15:57:14 2743] DEBUG (DevController:148) Waiting for devices vtpm. From fedora.lists at burns.me.uk Sun Jul 22 20:48:05 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Sun, 22 Jul 2007 21:48:05 +0100 Subject: [Fedora-xen] Re: Win2k3 domU has lost NIC In-Reply-To: <46A3BD17.90602@antony.eu> References: <46A3BD17.90602@antony.eu> Message-ID: On 22/07/07, Thomas Antony wrote: > I have the same problem with F7 x86_64 and all the windows domU's. When > i reboot the server, every windows domU does not have a nic anymore. A > reboot of the windows os does not help. I must shutdown the windows os, > remove and add again a nic with virt-manager and then there is a nic > again. thanks, I hadn't tried to remove and re-add a new NIC, before I do that I will run device manager with the special "set devmgr_show_nonpresent_devices=1" environment variable to see if windows still knows about the NIC, but thinks it is no longer present (maybe due to some MAC address change, though it is present if I use virsh dumpxml) > The paravirtualized F7 domU's are workin well. > I think this is happening since i updated libvirt to version 0.3.0. Not sure if this is identical to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247122 certainly seems that whenever dom0 is rebooted the Windows domU will loose it's NIC. From justin.wickett at duke.edu Sun Jul 22 22:03:15 2007 From: justin.wickett at duke.edu (Justin Wickett) Date: Sun, 22 Jul 2007 15:03:15 -0700 Subject: [Fedora-xen] Virt Machine Manager + Amazon S3 for EC2 usage Message-ID: <3CDBF6BE-888C-42A2-A2CA-D9A5CA34FDAC@duke.edu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey guys, I just saved a minimal FC7 installation to a local file, and am in the process of uploading it to Amazon S3 with the intention of creating an Amazon EC2 virtual instance. The way I formatted my file was quite simple... its just one ext3 root directory (so no swap, boot, LVM, etc... directories). Has anyone done this before? Were you successful? Amazon's Developer Guide suggests using Yum to install the operating system, but I thought that using the Virtual Machine Manager would be a lot easier. Anyways, I am in the (long) process of uploading a 2.5 GB image to S3, so I wanted to hear some feedback as to whether or not this will work as smoothly as I hope before I waste any more time. Thanks in advance! Justin Wickett Duke 2010 http://www.duke.edu/~jyw2 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFGo9QjJSH8HIex+CkRAgTrAJ4uj1CqMb1MkamUsxtAi4TYLgpXkQCbBlZz XsYpqf2GIEw28coizm25+RU= =3kQ2 -----END PGP SIGNATURE----- From tadeas.mengler at miton.cz Mon Jul 23 12:58:42 2007 From: tadeas.mengler at miton.cz (Tadeas Mengler) Date: Mon, 23 Jul 2007 14:58:42 +0200 Subject: [Fedora-xen] network io load Message-ID: <200707231259.l6NCxSrq006442@mx2.redhat.com> Hello I have Xen related issues. I try to describe it as best as I can. While transmitting large amounts of data from domU the IO load increases greatly, thus making the domU unusable. The load is significant even on dom0. The performance of cpus and hard drives is not an issue. We have this problem on all servers with diferent hw configurations. Please do you know the reason of this behaviour, do you have any experience whith such problems? -- -- S pozdravem Tadeas Mengler Linux System Administrator tadeas.mengler at miton.cz 483 367 866, 608 264 866 MITON CZ, s.r.o. | www.miton.cz Jiraskova 9, 466 01 Jablonec nad Nisou Tel.: 483 367 800, fax: 483 710 884 www.stahuj.cz | www.stable.cz | www.otoman.cz | www.vareni.cz From dlutter at redhat.com Mon Jul 23 20:37:04 2007 From: dlutter at redhat.com (David Lutterkort) Date: Mon, 23 Jul 2007 20:37:04 +0000 Subject: [Fedora-xen] Fw: [Xen-users] Congratulations to Xen team! In-Reply-To: <20070721192523.GC27107@redhat.com> References: <003d01c7cbc6$51acf100$fe01a8c0@ispbrasil> <20070721184724.GB27107@redhat.com> <000a01c7cbcb$6b9895b0$fe01a8c0@ispbrasil> <20070721192523.GC27107@redhat.com> Message-ID: <1185223024.17210.8.camel@galia.watzmann.net> On Sat, 2007-07-21 at 20:25 +0100, Daniel P. Berrange wrote: > On Sat, Jul 21, 2007 at 04:14:51PM -0300, Itamar Reis Peixoto wrote: > > also there are lguest in 2.6.23 > > > > lguest will be compiled as module in new fedora kernels ? > > We've no plans to include lguest in the Fedora kernels at this time. Again > it is only available for i386. Its current purpose is as a means for kernel > developers to research & experiment with virtualization ideas - not for end > users to put into real world use - there is Xen & KVM for real world use in > production. One of the biggest restrictions that lguest maintains is that it is guest and host kernel versions are tightly coupled - for the stated purpose of lguest completely appropriate, but definitely limits is usefulness as a replacement for pv Xen. So: even if lguest was in Fedora, you'd probably not get from it what you'd like to get from it. David From Travis.Formoso at blueslate.net Mon Jul 23 20:44:28 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Mon, 23 Jul 2007 16:44:28 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: I was thinking about this more and have not come up with a solid solution. Yes the new box does have Xen 3.0 and the older xen was running FC4 and I will assume Xen 2.0. What is the best way to migrate the FC4 xen server over to the new server running FC6? I want to get the image on the new server and then do an upgrade to it so it is running FC6. Thanks! > On Thu, Jul 19, 2007 at 03:51:21PM -0400, Formoso, Travis wrote: > Minor update: > > I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and then ran: > > xm create -c /xen/sec-int-dns/xmconfig and got this error: > > Error: (22, 'Invalid argument') > I'm guesing you're trying a i386 kernel here ? FC4 is using the obsolete > non-PAE kernels, while FC6 and later are all PAE. You can't mix & match > a PAE and non-PAE kernels in host & guest. Dan. This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From itamar at ispbrasil.com.br Mon Jul 23 23:50:31 2007 From: itamar at ispbrasil.com.br (Itamar Reis Peixoto) Date: Mon, 23 Jul 2007 20:50:31 -0300 Subject: [Fedora-xen] RE: Upgrading Xen machines References: Message-ID: <009401c7cd84$42d12b50$fe01a8c0@ispbrasil> upgrade with yum go to direct to fedora 7 -------------------- Itamar Reis Peixoto e-mail: itamar at ispbrasil.com.br msn: itamarjp at starmedia.com skype: itamarjp icq: 81053601 +55 34 3238 3845 +55 11 4063 5033 From zzojaji at aim.com Tue Jul 24 10:44:28 2007 From: zzojaji at aim.com (zzojaji at aim.com) Date: Tue, 24 Jul 2007 06:44:28 -0400 Subject: [Fedora-xen] Problem with mounting the installation tree for creating new VM on FC7! Message-ID: <8C99BF6BEE88252-284-3A06@FWM-D14.sysops.aol.com> hi all! i'm trying to install a new xen virtual machine on FC7, using virt-manager. the wizard finishes successfully and it start to create a VM, the installation tree has been placed on host drive and shared using NFS, however installing a guest's linux starts but it couldn't mount the installation tree with the error "that directory could not be mounted from the server"!? system specifications are: [root at localhost ~]# uname -r 2.6.20-2925.9.fc7xen [root at localhost ~]# rpm -qa \*xen* xen-libs-3.1.0-0.rc7.1.fc7 xen-3.1.0-0.rc7.1.fc7 kernel-xen-2.6.20-2925.9.fc7 mounting from the host to itself with NFS is OK with this command: [root at localhost ~]# mount -t nfs 192.168.100.99:/root/Desktop/fc7/ /root/Desktop/test1/ where 192.168.100.99 is the host IP and /root/Desktop/fc7/ is the address of installation tree on it! i don't know the problem is with NFS, permissions or any thing else! if more information is needed please just notify me, any advise, comment or solution is helpful! thanks, Zahra Zojaji ________________________________________________________________________ Check Out the new free AIM(R) Mail -- Unlimited storage and industry-leading spam and email virus protection. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pasik at iki.fi Tue Jul 24 11:19:55 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 24 Jul 2007 14:19:55 +0300 Subject: [Fedora-xen] network io load In-Reply-To: <200707231259.l6NCxSrq006442@mx2.redhat.com> References: <200707231259.l6NCxSrq006442@mx2.redhat.com> Message-ID: <20070724111954.GE4106@edu.joroinen.fi> On Mon, Jul 23, 2007 at 02:58:42PM +0200, Tadeas Mengler wrote: > Hello > > I have Xen related issues. I try to describe it as best as I can. > While transmitting large amounts of data from domU the IO load > increases greatly, thus making the domU unusable. The load is > significant even on dom0. The performance of cpus and hard drives is > not an issue. We have this problem on all servers with diferent hw > configurations. Please do you know the reason of this behaviour, do you > have any experience whith such problems? > I'm going to ask you almost the same questions as on centos-list.. Nope, no such experience with many xen hosts. How do you measure this "IO load" ? What effects does it have? What kind of hardware do you have (cpu/mem/nic/disk or raid controller/disks)? Are you running centos5? latest updates installed? or fedora? what fedora version? what kernels? Can you post any performance data? How does this "io load" make domU unusable? I'm sorry byt your problem description lacks a lot of important information.. -- Pasi From Travis.Formoso at blueslate.net Tue Jul 24 13:57:06 2007 From: Travis.Formoso at blueslate.net (Formoso, Travis) Date: Tue, 24 Jul 2007 09:57:06 -0400 Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: <009401c7cd84$42d12b50$fe01a8c0@ispbrasil> Message-ID: Is it possible to update xen to 3.0 on the VM and then transfer to the new server? I want to transfer to the new server first so if I make any mistakes nothing is lost - its a backup DHCP server so it needs to stay in production until it's is rolled over to the new machine. > upgrade with yum > go to direct to fedora 7 -------------------- > Itamar Reis Peixoto This e-mail and any files transmitted with it are for the sole use of Blue Slate Solutions and the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email or any action taken in reliance on this e-mail is strictly prohibited and may be unlawful. From pasik at iki.fi Tue Jul 24 14:02:49 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Tue, 24 Jul 2007 17:02:49 +0300 Subject: [Fedora-xen] network io load In-Reply-To: <200707241206.l6OC6FpH022110@ainavaan.iki.fi> References: <200707231259.l6NCxSrq006442@mx2.redhat.com> <20070724111954.GE4106@edu.joroinen.fi> <200707241206.l6OC6FpH022110@ainavaan.iki.fi> Message-ID: <20070724140249.GF4106@edu.joroinen.fi> On Tue, Jul 24, 2007 at 02:05:28PM +0200, Tadeas Mengler wrote: > Thanks for the reply at first. > > You can see it in htop utility. The load comes from kernelspace. > The symptoms are simillar to those: > http://lists.xensource.com/archives/html/xen-users/2005-06/msg00625.html > What's the process causing the load / cpu-usage? > The speed of for example of coping data across network is very slow > even on gigabit network (about 3 mbit/s), while domU is extremly slow > and unresponsive (all of the tasks). > Is the network performance slow to begin with, or after some time? If after some time, what causes it to get slow? Is network slow from dom0 to the network? Is network slow between dom0 and domU ? What NIC do you have? What software are you using to test the network performance? Have you tried iperf? both tcp and udp-mode? Do you see packet loss with udp? Do you have any errors in logs/dmesg? both dom0 and domU? how about in "xm log" or "xm dmesg" ? Do you have any custom settings or xen scheduling parameters (domain weights) set? Are you using (the default) bridged networking setup with xen? Or a custom one? > The hw varies, mostly supermicro servers, various cpus (different > intels and amds), various ram , mostly sw raid. The disks are sas, sata. > > The distribution is centos5 with recent updates and current kernel from > the distribution. > Ok, it should be fine then. I don't see such problems with my hardware and the same hypervisor/kernels. -- Pasi > > Dne Tue, 24 Jul 2007 14:19:55 +0300 > Pasi K?rkk?inen napsal(a): > > > On Mon, Jul 23, 2007 at 02:58:42PM +0200, Tadeas Mengler wrote: > > > Hello > > > > > > I have Xen related issues. I try to describe it as best as I can. > > > While transmitting large amounts of data from domU the IO load > > > increases greatly, thus making the domU unusable. The load is > > > significant even on dom0. The performance of cpus and hard drives is > > > not an issue. We have this problem on all servers with diferent hw > > > configurations. Please do you know the reason of this behaviour, do > > > you have any experience whith such problems? > > > > > > > I'm going to ask you almost the same questions as on centos-list.. > > > > Nope, no such experience with many xen hosts. > > > > How do you measure this "IO load" ? What effects does it have? > > > > What kind of hardware do you have (cpu/mem/nic/disk or raid > > controller/disks)? > > > > Are you running centos5? latest updates installed? or fedora? what > > fedora version? what kernels? > > > > Can you post any performance data? How does this "io load" make domU > > unusable? > > > > I'm sorry byt your problem description lacks a lot of important > > information.. > > > > -- Pasi > > > > > -- > S pozdravem > > Tadeas Mengler > Senior Linux System Administrator > > tadeas.mengler at miton.cz > 483 367 866, 608 264 866 > > MITON CZ, s.r.o. | www.miton.cz > Jiraskova 9, 466 01 Jablonec nad Nisou > Tel.: 483 367 800, fax: 483 710 884 > > www.stahuj.cz | www.stable.cz | www.otoman.cz | www.vareni.cz -- ^ . . Linux / - \ Choice.of.the .Next.Generation. From thewird at yahoo.com Tue Jul 24 14:15:40 2007 From: thewird at yahoo.com (thewird) Date: Tue, 24 Jul 2007 10:15:40 -0400 (EDT) Subject: [Fedora-xen] RE: Upgrading Xen machines In-Reply-To: Message-ID: <287465.32010.qm@web88305.mail.re4.yahoo.com> > Is it possible to update xen to 3.0 on the VM and then transfer to > the new server? > > I want to transfer to the new server first so if I make any mistakes > nothing is lost - its a backup DHCP server so it needs to stay in > production until it's is rolled over to the new machine. > > > upgrade with yum > > > go to direct to fedora 7 > When Fedora 7 updates to support 64bit hypervisor, will upgrading to 64bit hypervisor affect current guests in any way? Marco Jorge From taoj2 at cs.rpi.edu Tue Jul 24 20:48:07 2007 From: taoj2 at cs.rpi.edu (taoj2 at cs.rpi.edu) Date: Tue, 24 Jul 2007 16:48:07 -0400 (EDT) Subject: [Fedora-xen] Easier Way to configure domainU Message-ID: <43732.128.213.28.16.1185310087.squirrel@webmail.cs.rpi.edu> Hi, I want to configure a new domainU from existing domain. Can I just copy the image file (/var/lib/xen/images/box) and also copy the configuration file of existing domain? The format of configuration file is like this: # Automatically generated xen config file name = "xen2" memory = "1000" disk = [ 'tap:aio:/var/lib/xen/images/box2,xvda,w', ] vif = [ 'mac=xx:xx:xx:xx:xx:xx, bridge=xenbr1', ] vnc=1 vncunused=1 uuid = "9297c728-efe7-025f-3b35-02f92474aa6e" bootloader="/usr/bin/pygrub" vcpus=1 on_reboot = 'restart' on_crash = 'restart' I will change the name to a new name, set vcpu to 4. But I don't know how to get a unique mac address and uuid. Anybody know? And except for create the image file and configuration file, what else do i need to do? PS: I use the Fedora XEN. Thanks for your time. Best Wishes Angel From orenault at redhat.com Wed Jul 25 07:22:42 2007 From: orenault at redhat.com (Olivier Renault) Date: Wed, 25 Jul 2007 09:22:42 +0200 Subject: [Fedora-xen] Easier Way to configure domainU In-Reply-To: <43732.128.213.28.16.1185310087.squirrel@webmail.cs.rpi.edu> References: <43732.128.213.28.16.1185310087.squirrel@webmail.cs.rpi.edu> Message-ID: <46A6FA42.4030409@redhat.com> taoj2 at cs.rpi.edu wrote: > Hi, > > I want to configure a new domainU from existing domain. Can I just copy > the image file (/var/lib/xen/images/box) and also copy the configuration > file of existing domain? Correct. > > The format of configuration file is like this: > > # Automatically generated xen config file > name = "xen2" > memory = "1000" > disk = [ 'tap:aio:/var/lib/xen/images/box2,xvda,w', ] > vif = [ 'mac=xx:xx:xx:xx:xx:xx, bridge=xenbr1', ] > vnc=1 > vncunused=1 > uuid = "9297c728-efe7-025f-3b35-02f92474aa6e" > bootloader="/usr/bin/pygrub" > vcpus=1 > on_reboot = 'restart' > on_crash = 'restart' > > I will change the name to a new name, set vcpu to 4. But I don't know how > to get a unique mac address and uuid. Anybody know? For the mac I tend to randomly change one of the last 6 characters. It is easier for the uuid as you can use the uuidgen command to generate a new one. > > And except for create the image file and configuration file, what else do > i need to do? That should be it. > > PS: I use the Fedora XEN. > > Thanks for your time. > > Best Wishes > Angel > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen From felix.schwarz at web.de Wed Jul 25 12:24:53 2007 From: felix.schwarz at web.de (Felix Schwarz) Date: Wed, 25 Jul 2007 14:24:53 +0200 Subject: [Fedora-xen] No network card in Fedora 7 HVM guest Message-ID: <46A74115.8020803@web.de> I running a Fedora 7/i386 (hvm) guest on a F7 x86_64 host. The guest was created by using virt-manager so it uses the new Xen 3.1 config system. The installation worked fine but now the network card is missing in the DomU. Even lspci in DomU can't detect the nic although it is configured in the Dom0 (virsh dumpxml f7_32_build): ... /usr/lib64/xen/bin/qemu-dm