From jlagrue at gmail.com Tue Sep 4 10:55:19 2007 From: jlagrue at gmail.com (John Lagrue) Date: Tue, 4 Sep 2007 11:55:19 +0100 Subject: [Fedora-xen] virt-manager failure Message-ID: TRying to create a guest using virt-manager on Fedora 7. Upon clicking "Finish" I get this error: Unable to complete install ' virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to bridge 'virbr0' : No such device Any thoughts? From rjones at redhat.com Tue Sep 4 11:06:35 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 04 Sep 2007 12:06:35 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: References: Message-ID: <46DD3C3B.8030505@redhat.com> John Lagrue wrote: > TRying to create a guest using virt-manager on Fedora 7. Upon clicking > "Finish" I get this error: > > Unable to complete install ' > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to > bridge 'virbr0' : No such device > > Any thoughts? What type of networking did you select? Is there any further detail in: /root/.virt-manager/virt-manager.log /var/log/xen/xend.log /var/log/xen/xend-debug.log 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 jlagrue at gmail.com Tue Sep 4 17:43:34 2007 From: jlagrue at gmail.com (John Lagrue) Date: Tue, 4 Sep 2007 18:43:34 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: <46DD3C3B.8030505@redhat.com> References: <46DD3C3B.8030505@redhat.com> Message-ID: On 04/09/07, Richard W.M. Jones wrote: > John Lagrue wrote: > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking > > "Finish" I get this error: > > > > Unable to complete install ' > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to > > bridge 'virbr0' : No such device > > > > Any thoughts? > > What type of networking did you select? > > Is there any further detail in: > /root/.virt-manager/virt-manager.log > /var/log/xen/xend.log > /var/log/xen/xend-debug.log > I selected Virtual Network, default device. There doesn't seem to be anything informative in the virt-manager log file, other than the traceback. I don't use Xen, so those logs don't exist. It would seem to me to be saying that the virbr0 device doesn't exist; how can I check if it does? JDL From yor_on at hotmail.com Tue Sep 4 19:33:33 2007 From: yor_on at hotmail.com (yoron) Date: Tue, 4 Sep 2007 12:33:33 -0700 (PDT) Subject: [Fedora-xen] Going Nuts over XEN in F7 Message-ID: <12485073.post@talk.nabble.com> I use a updated (last was today :) Fedora7 on a quadra core Server (Primergy rx300 s3) Trying XEN and it's 'Virtual Machine Manager' i meet with those problems.. ----------------------- Unable to complete install ' virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/images/test_1_2003 does not exist.') 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.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 563, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/images/test_1_2003 does not exist.') ' ----------------------------------- And try_2 ----------------------------------- Unable to complete install ' virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/test1 does not exist.') 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.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 563, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/test1 does not exist.') ' ----------------------------- So i disable SElinux from :) Guess what :)happens ah ha.. -------------------------------- Summary SELinux is preventing access to files with the label, file_t. Detailed Description SELinux permission checks on files labeled file_t are being denied. file_t is the context the SELinux kernel gives to files that do not have a label.This indicates a serious labeling problem. No files on an SELinux box should ever be labeled file_t. If you have just added a new disk drive to the system you can relabel it using the restorecon command. Otherwise you should relabel the entire files system. Allowing Access You can execute the following command as root to relabel your computer system: "touch /.autorelabel; reboot" Additional Information Source Context system_u:system_r:udev_t:SystemLow-SystemHigh Target Context root:object_r:file_t Target Objects /images/2003_sist [ file ] Affected RPM Packages coreutils-6.9-3.fc7 [application] Policy RPM selinux-policy-2.6.4-38.fc7 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Permissive Plugin Name plugins.file Host Name localhost.localdomain Platform Linux localhost.localdomain 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686 i686 Alert Count 1 First Seen tis 4 sep 2007 17.29.44 Last Seen tis 4 sep 2007 17.29.44 Local ID 804af117-e5d9-4304-a8bd-83f0a26bb4a1 Line Numbers Raw Audit Messages avc: denied { getattr } for comm="readlink" dev=sdb1 egid=0 euid=0 exe="/usr/bin/readlink" exit=0 fsgid=0 fsuid=0 gid=0 items=0 name="2003_sist" path="/images/2003_sist" pid=16317 scontext=system_u:system_r:udev_t:s0-s0:c0.c1023 sgid=0 subj=system_u:system_r:udev_t:s0-s0:c0.c1023 suid=0 tclass=file tcontext=root:object_r:file_t:s0 tty=(none) uid=0 ------------------------ And ---------------------- Summary SELinux is preventing /sbin/losetup (fsadm_t) "read write" to 2003_sist (file_t). Detailed Description SELinux denied /sbin/losetup access to 2003_sist. If this is a swapfile it has to have a file context label of swapfile_t. If you did not intend to use 2003_sist as a swapfile it probably indicates a bug, however it could also signal a intrusion attempt. Allowing Access You can alter the file context by executing chcon -t swapfile_t 2003_sist The following command will allow this access: chcon x-t swapfile_t 2003_sist Additional Information Source Context system_u:system_r:fsadm_t:SystemLow-SystemHigh Target Context root:object_r:file_t Target Objects 2003_sist [ file ] Affected RPM Packages util-linux-2.13-0.54.fc7 [application] Policy RPM selinux-policy-2.6.4-38.fc7 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Permissive Plugin Name plugins.swapfile Host Name localhost.localdomain Platform Linux localhost.localdomain 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686 i686 Alert Count 1 First Seen tis 4 sep 2007 17.29.45 Last Seen tis 4 sep 2007 17.29.45 Local ID db4d705b-dbc9-47b5-b99c-03d97a7c2a85 Line Numbers Raw Audit Messages avc: denied { read, write } for comm="losetup" dev=sdb1 egid=0 euid=0 exe="/sbin/losetup" exit=3 fsgid=0 fsuid=0 gid=0 items=0 name="2003_sist" pid=16450 scontext=system_u:system_r:fsadm_t:s0-s0:c0.c1023 sgid=0 subj=system_u:system_r:fsadm_t:s0-s0:c0.c1023 suid=0 tclass=file tcontext=root:object_r:file_t:s0 tty=(none) uid=0 -------------------------------------------------- Now, will i have to do this every time? ( executing chcon -t swapfile_'whatever_file') Or should i use this? ---------------------------------- " The only way that this file would get created is if the system was booted with selinux=0 (or SELINUX=disabled in /etc/selinux/config). Or if you added a new disk to a machine that was not labeled via SELinux. " As it is a Server we are talking about i would prefere to leave SeLinux on. But as i'm gonna 'play' with a lot of different OS and also using a net ??? ----------------------------------------------- So i tried to close down SeLinux and my firewall too ( unconnected though:) At my first try (two cpu: 1 Gig memory 10 Gig HD (as a file) i got to the beginning of a GUI (W 2003) then when 2003 tried to read in the graphical interface it hung. And when i created a totally new imagefile it wouldn't start :) Here is the output from Virtual Machine Manager (XEN) -------------------------------- ' Kan inte slutf?ra (can't finish ) installationen: 'virDomainCreateLinux() failed POST-operation (failed) misslyckades: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.')' ' and Unable to complete install ' virDomainCreateLinux() failed POST-operation misslyckades: (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.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 563, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.') -------------------------------------- Well :) Can't say that i'm overjoyed (Hotplug scripts not working???), and yes, i did change the 'permissions' on files globally via a rebot before trying anew?? Any one? btw: Gnome locked up after the last attempt and my screen too. Had to 'hard boot' it at the end? Thought that with Xen embedded around the 'OS' such things would be scarce? Also :) What am i missing here? Something more i should think of before trying? (like why i got this crazy idea :) Xen seems to have very specific ideas of how permissions should be depending on where they are. I thought that the beauty with a preinstalled Xen was that this was already taken care off? Is it me 'updating' from Fedora (yum default) that have screwed it up. So i shouldn't update at all?? Cheers. -------------------------- -- View this message in context: http://www.nabble.com/Going-Nuts-over-XEN-in-F7-tf4379858.html#a12485073 Sent from the Fedora Xen mailing list archive at Nabble.com. From yor_on at hotmail.com Tue Sep 4 19:40:58 2007 From: yor_on at hotmail.com (Yoron hamberg) Date: Tue, 04 Sep 2007 21:40:58 +0200 Subject: [Fedora-xen] help :) Message-ID: I use a updated (last was today :) Fedora7 on a quadra core Server (Primergy rx300 s3) Trying XEN and it's 'Virtual Machine Manager' i meet with those problems.. ----------------------- Unable to complete install ' virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/images/test_1_2003 does not exist.') 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.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 563, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/images/test_1_2003 does not exist.') ' ----------------------------------- And try_2 ----------------------------------- Unable to complete install ' virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/test1 does not exist.') 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.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 563, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 768 (vbd) could not be connected. /images/test1 does not exist.') ' ----------------------------- So i disable SElinux from :) Guess what :)happens ah ha.. -------------------------------- Summary SELinux is preventing access to files with the label, file_t. Detailed Description SELinux permission checks on files labeled file_t are being denied. file_t is the context the SELinux kernel gives to files that do not have a label.This indicates a serious labeling problem. No files on an SELinux box should ever be labeled file_t. If you have just added a new disk drive to the system you can relabel it using the restorecon command. Otherwise you should relabel the entire files system. Allowing Access You can execute the following command as root to relabel your computer system: "touch /.autorelabel; reboot" Additional Information Source Context system_u:system_r:udev_t:SystemLow-SystemHigh Target Context root:object_r:file_t Target Objects /images/2003_sist [ file ] Affected RPM Packages coreutils-6.9-3.fc7 [application] Policy RPM selinux-policy-2.6.4-38.fc7 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Permissive Plugin Name plugins.file Host Name localhost.localdomain Platform Linux localhost.localdomain 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686 i686 Alert Count 1 First Seen tis 4 sep 2007 17.29.44 Last Seen tis 4 sep 2007 17.29.44 Local ID 804af117-e5d9-4304-a8bd-83f0a26bb4a1 Line Numbers Raw Audit Messages avc: denied { getattr } for comm="readlink" dev=sdb1 egid=0 euid=0 exe="/usr/bin/readlink" exit=0 fsgid=0 fsuid=0 gid=0 items=0 name="2003_sist" path="/images/2003_sist" pid=16317 scontext=system_u:system_r:udev_t:s0-s0:c0.c1023 sgid=0 subj=system_u:system_r:udev_t:s0-s0:c0.c1023 suid=0 tclass=file tcontext=root:object_r:file_t:s0 tty=(none) uid=0 ------------------------ And ---------------------- Summary SELinux is preventing /sbin/losetup (fsadm_t) "read write" to 2003_sist (file_t). Detailed Description SELinux denied /sbin/losetup access to 2003_sist. If this is a swapfile it has to have a file context label of swapfile_t. If you did not intend to use 2003_sist as a swapfile it probably indicates a bug, however it could also signal a intrusion attempt. Allowing Access You can alter the file context by executing chcon -t swapfile_t 2003_sist The following command will allow this access: chcon x-t swapfile_t 2003_sist Additional Information Source Context system_u:system_r:fsadm_t:SystemLow-SystemHigh Target Context root:object_r:file_t Target Objects 2003_sist [ file ] Affected RPM Packages util-linux-2.13-0.54.fc7 [application] Policy RPM selinux-policy-2.6.4-38.fc7 Selinux Enabled True Policy Type targeted MLS Enabled True Enforcing Mode Permissive Plugin Name plugins.swapfile Host Name localhost.localdomain Platform Linux localhost.localdomain 2.6.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686 i686 Alert Count 1 First Seen tis 4 sep 2007 17.29.45 Last Seen tis 4 sep 2007 17.29.45 Local ID db4d705b-dbc9-47b5-b99c-03d97a7c2a85 Line Numbers Raw Audit Messages avc: denied { read, write } for comm="losetup" dev=sdb1 egid=0 euid=0 exe="/sbin/losetup" exit=3 fsgid=0 fsuid=0 gid=0 items=0 name="2003_sist" pid=16450 scontext=system_u:system_r:fsadm_t:s0-s0:c0.c1023 sgid=0 subj=system_u:system_r:fsadm_t:s0-s0:c0.c1023 suid=0 tclass=file tcontext=root:object_r:file_t:s0 tty=(none) uid=0 -------------------------------------------------- Now, will i have to do this every time? ( executing chcon -t swapfile_'whatever_file') Or should i use this? ---------------------------------- " The only way that this file would get created is if the system was booted with selinux=0 (or SELINUX=disabled in /etc/selinux/config). Or if you added a new disk to a machine that was not labeled via SELinux. " As it is a Server we are talking about i would prefere to leave SeLinux on. But as i'm gonna 'play' with a lot of different OS and also using a net ??? ----------------------------------------------- So i tried to close down SeLinux and my firewall too ( unconnected though:) At my first try (two cpu: 1 Gig memory 10 Gig HD (as a file) i got to the beginning of a GUI (W 2003) then when 2003 tried to read in the graphical interface it hung. And when i created a totally new imagefile it wouldn't start :) Here is the output from Virtual Machine Manager (XEN) -------------------------------- ' Kan inte slutf??ra (can't finish ) installationen: 'virDomainCreateLinux() failed POST-operation (failed) misslyckades: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.')' ' and Unable to complete install ' virDomainCreateLinux() failed POST-operation misslyckades: (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.5/site-packages/virtinst/Guest.py", line 710, in start_install return self._do_install(consolecb, meter) File "/usr/lib/python2.5/site-packages/virtinst/Guest.py", line 727, in _do_install self.domain = self.conn.createLinux(install_xml, 0) File "/usr/lib/python2.5/site-packages/libvirt.py", line 563, in createLinux if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self) libvirtError: virDomainCreateLinux() failed POST-operation misslyckades: (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.') -------------------------------------- Well :) Can't say that i'm overjoyed (Hotplug scripts not working???), and yes, i did change the 'permissions' on files globally via a rebot before trying anew?? Any one? btw: Gnome locked up after the last attempt and my screen too. Had to 'hard boot' it at the end? Thought that with Xen embedded around the 'OS' such things would be scarce? Also :) What am i missing here? Something more i should think of before trying? (like why i got this crazy idea :) Xen seems to have very specific ideas of how permissions should be depending on where they are. I thought that the beauty with a preinstalled Xen was that this was already taken care off? Is it me 'updating' from Fedora (yum default) that have screwed it up. So i shouldn't update at all?? Awwwhh :) Cheers. _________________________________________________________________ Se artisterna upptr?da f?r en gr?n planet http://liveearth.se.msn.com/ From jlagrue at gmail.com Tue Sep 4 22:07:34 2007 From: jlagrue at gmail.com (John Lagrue) Date: Tue, 4 Sep 2007 23:07:34 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: References: <46DD3C3B.8030505@redhat.com> Message-ID: On 04/09/07, John Lagrue wrote: > On 04/09/07, Richard W.M. Jones wrote: > > John Lagrue wrote: > > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking > > > "Finish" I get this error: > > > > > > Unable to complete install ' > > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to > > > bridge 'virbr0' : No such device > > > > > > Any thoughts? > > > > What type of networking did you select? > > > > Is there any further detail in: > > /root/.virt-manager/virt-manager.log > > /var/log/xen/xend.log > > /var/log/xen/xend-debug.log > > > > I selected Virtual Network, default device. There doesn't seem to be > anything informative in the virt-manager log file, other than the > traceback. > > I don't use Xen, so those logs don't exist. > > It would seem to me to be saying that the virbr0 device doesn't exist; > how can I check if it does? > > JDL > It does indeed seem that virbr0 doesn't exist. Is there something that I haven't installed? I only want qemu-kvm, as Xen isn't a viable option for me. JDL From berrange at redhat.com Wed Sep 5 03:20:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 5 Sep 2007 04:20:24 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: References: <46DD3C3B.8030505@redhat.com> Message-ID: <20070905032024.GA8649@redhat.com> On Tue, Sep 04, 2007 at 11:07:34PM +0100, John Lagrue wrote: > On 04/09/07, John Lagrue wrote: > > On 04/09/07, Richard W.M. Jones wrote: > > > John Lagrue wrote: > > > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking > > > > "Finish" I get this error: > > > > > > > > Unable to complete install ' > > > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to > > > > bridge 'virbr0' : No such device > > > > > > > > Any thoughts? > > > > > > What type of networking did you select? > > > > > > Is there any further detail in: > > > /root/.virt-manager/virt-manager.log > > > /var/log/xen/xend.log > > > /var/log/xen/xend-debug.log > > > > > > > I selected Virtual Network, default device. There doesn't seem to be > > anything informative in the virt-manager log file, other than the > > traceback. > > > > I don't use Xen, so those logs don't exist. > > > > It would seem to me to be saying that the virbr0 device doesn't exist; > > how can I check if it does? > > > > JDL > > > > It does indeed seem that virbr0 doesn't exist. Is there something that > I haven't installed? I only want qemu-kvm, as Xen isn't a viable > option for me. virbr0 is (supposed to be) created automatically by libvirt. If it does not exist there are a couple of things to check # virsh net-list --all Name State Autostart ----------------------------------------- default active yes If that shows it active, then try restarting it with virsh net-destroy default virsh net-start default If net-list didn't show it, then it may be deleted or not created in the first place. You can re-create it with virsh net-define /usr/share/libvirt/networks/default.xml virsh net-autostart default virsh net-start default Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From jlagrue at gmail.com Wed Sep 5 08:15:48 2007 From: jlagrue at gmail.com (John Lagrue) Date: Wed, 5 Sep 2007 09:15:48 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: <20070905032024.GA8649@redhat.com> References: <46DD3C3B.8030505@redhat.com> <20070905032024.GA8649@redhat.com> Message-ID: On 05/09/07, Daniel P. Berrange wrote: > On Tue, Sep 04, 2007 at 11:07:34PM +0100, John Lagrue wrote: > > On 04/09/07, John Lagrue wrote: > > > On 04/09/07, Richard W.M. Jones wrote: > > > > John Lagrue wrote: > > > > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking > > > > > "Finish" I get this error: > > > > > > > > > > Unable to complete install ' > > > > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to > > > > > bridge 'virbr0' : No such device > > > > > > > > > > Any thoughts? > > > > > > > > What type of networking did you select? > > > > > > > > Is there any further detail in: > > > > /root/.virt-manager/virt-manager.log > > > > /var/log/xen/xend.log > > > > /var/log/xen/xend-debug.log > > > > > > > > > > I selected Virtual Network, default device. There doesn't seem to be > > > anything informative in the virt-manager log file, other than the > > > traceback. > > > > > > I don't use Xen, so those logs don't exist. > > > > > > It would seem to me to be saying that the virbr0 device doesn't exist; > > > how can I check if it does? > > > > > > JDL > > > > > > > It does indeed seem that virbr0 doesn't exist. Is there something that > > I haven't installed? I only want qemu-kvm, as Xen isn't a viable > > option for me. > > virbr0 is (supposed to be) created automatically by libvirt. If it does not > exist there are a couple of things to check > > # virsh net-list --all > Name State Autostart > ----------------------------------------- > default active yes > > If that shows it active, then try restarting it with > > virsh net-destroy default > virsh net-start default > > If net-list didn't show it, then it may be deleted or not created in the > first place. You can re-create it with > > virsh net-define /usr/share/libvirt/networks/default.xml > virsh net-autostart default > virsh net-start default > Unfortunately, all I get is this: # virsh net-list --all error: failed to connect to the hypervisor error: no valid connection From oehmes at de.ibm.com Wed Sep 5 08:18:31 2007 From: oehmes at de.ibm.com (Sven Oehme) Date: Wed, 5 Sep 2007 10:18:31 +0200 Subject: [Fedora-xen] virt-manager failure In-Reply-To: References: <46DD3C3B.8030505@redhat.com> <20070905032024.GA8649@redhat.com> Message-ID: try virsh -c qemu:///system instead of just virsh .. sven "John Lagrue" Sent by: fedora-xen-bounces at redhat.com 09/05/2007 10:15 AM To "Daniel P. Berrange" cc fedora-xen at redhat.com Subject Re: [Fedora-xen] virt-manager failure On 05/09/07, Daniel P. Berrange wrote: > On Tue, Sep 04, 2007 at 11:07:34PM +0100, John Lagrue wrote: > > On 04/09/07, John Lagrue wrote: > > > On 04/09/07, Richard W.M. Jones wrote: > > > > John Lagrue wrote: > > > > > TRying to create a guest using virt-manager on Fedora 7. Upon clicking > > > > > "Finish" I get this error: > > > > > > > > > > Unable to complete install ' > > > > > virDomainCreateLinux() failed Failed to add tap interface 'vnet0' to > > > > > bridge 'virbr0' : No such device > > > > > > > > > > Any thoughts? > > > > > > > > What type of networking did you select? > > > > > > > > Is there any further detail in: > > > > /root/.virt-manager/virt-manager.log > > > > /var/log/xen/xend.log > > > > /var/log/xen/xend-debug.log > > > > > > > > > > I selected Virtual Network, default device. There doesn't seem to be > > > anything informative in the virt-manager log file, other than the > > > traceback. > > > > > > I don't use Xen, so those logs don't exist. > > > > > > It would seem to me to be saying that the virbr0 device doesn't exist; > > > how can I check if it does? > > > > > > JDL > > > > > > > It does indeed seem that virbr0 doesn't exist. Is there something that > > I haven't installed? I only want qemu-kvm, as Xen isn't a viable > > option for me. > > virbr0 is (supposed to be) created automatically by libvirt. If it does not > exist there are a couple of things to check > > # virsh net-list --all > Name State Autostart > ----------------------------------------- > default active yes > > If that shows it active, then try restarting it with > > virsh net-destroy default > virsh net-start default > > If net-list didn't show it, then it may be deleted or not created in the > first place. You can re-create it with > > virsh net-define /usr/share/libvirt/networks/default.xml > virsh net-autostart default > virsh net-start default > Unfortunately, all I get is this: # virsh net-list --all error: failed to connect to the hypervisor error: no valid connection -- 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 rjones at redhat.com Wed Sep 5 09:48:20 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 05 Sep 2007 10:48:20 +0100 Subject: [Fedora-xen] help :) In-Reply-To: References: Message-ID: <46DE7B64.9090103@redhat.com> Yoron hamberg wrote: > virDomainCreateLinux() failed POST-operation misslyckades: (xend.err > 'Device > 768 (vbd) could not be connected. /images/images/test_1_2003 does not > exist.') As you identified, SELinux is the problem here. The default permissions assume that Xen images are created in /var/lib/xen/images/ and an attempt to create them anywhere else will fail. Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From jlagrue at gmail.com Wed Sep 5 10:19:26 2007 From: jlagrue at gmail.com (John Lagrue) Date: Wed, 5 Sep 2007 11:19:26 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: References: <46DD3C3B.8030505@redhat.com> <20070905032024.GA8649@redhat.com> Message-ID: On 05/09/07, Sven Oehme wrote: > > > try virsh -c qemu:///system instead of just virsh .. > sven Thanks for that Sven. Now I get this: # virsh -c qemu:///system net-list --all Name State Autostart ----------------------------------------- default active yes -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Wed Sep 5 10:22:49 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Wed, 05 Sep 2007 11:22:49 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: References: <46DD3C3B.8030505@redhat.com> <20070905032024.GA8649@redhat.com> Message-ID: <46DE8379.8050503@redhat.com> Does the bridge actually exist? eg: $ /usr/sbin/brctl show bridge name bridge id STP enabled interfaces virbr0 8000.000000000000 no 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 bkearney at redhat.com Wed Sep 5 10:45:51 2007 From: bkearney at redhat.com (Bryan Kearney) Date: Wed, 5 Sep 2007 06:45:51 -0400 Subject: [Fedora-xen] virt-manager failure In-Reply-To: <46DE8379.8050503@redhat.com> References: <46DD3C3B.8030505@redhat.com> <20070905032024.GA8649@redhat.com> <46DE8379.8050503@redhat.com> Message-ID: <3b84df080709050345h74e7cc3ds8a21850caa0b6122@mail.gmail.com> I have noticed that the xen-libs drips the vibr0. If you are using kvm.. it is basically busted. I had to create my own bridge and use that explicitly. On 9/5/07, Richard W.M. Jones wrote: > > Does the bridge actually exist? eg: > > $ /usr/sbin/brctl show > bridge name bridge id STP enabled interfaces > virbr0 8000.000000000000 no > > Rich. > > -- > Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ > Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod > Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in > England and Wales under Company Registration No. 03798903 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From berrange at redhat.com Wed Sep 5 15:12:24 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Wed, 5 Sep 2007 16:12:24 +0100 Subject: [Fedora-xen] virt-manager failure In-Reply-To: <3b84df080709050345h74e7cc3ds8a21850caa0b6122@mail.gmail.com> References: <46DD3C3B.8030505@redhat.com> <20070905032024.GA8649@redhat.com> <46DE8379.8050503@redhat.com> <3b84df080709050345h74e7cc3ds8a21850caa0b6122@mail.gmail.com> Message-ID: <20070905151224.GE5503@redhat.com> On Wed, Sep 05, 2007 at 06:45:51AM -0400, Bryan Kearney wrote: > I have noticed that the xen-libs drips the vibr0. Urm, huh ? What are you trying to say here ? > If you are using kvm.. it > is basically busted. I had to create my own bridge and use that explicitly. This is the desired behaviour - the only reason why Xen provides a xenbr0 is historical baggage. Creating a bridge device out of the box simply does not work if you are using Wifi, or if your network is not online at boot, or if you use network manager to switch between devices on the fly, or if you are booting off iSCSI or NFS root. Xen has some hacky heuristics which sort of work if you are lucky enough to be booting local disk with a permanent hard wired ethernet device, but these break horribly just as often as they work. Our intent is to remove the automatic Xen provided bridge. It is simple to manaully configure a bridge containing eth0 using the config files in /etc/sysconfig/network-scripts. In addiiton libvirt provides virbr0 which is an isolated network device connected to the outside world using forwarding+NAT. The two different network config scenarios are described at http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt 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 achan at jonathan360.com Thu Sep 6 15:20:16 2007 From: achan at jonathan360.com (achan at jonathan360.com) Date: Thu, 06 Sep 2007 11:20:16 -0400 Subject: [Fedora-xen] Xen paravirtualized guest freezes upon boot Message-ID: <46E01AB0.3060405@jonathan360.com> Running xen 3 host and guest OS is FC6. the guest boots but freezes after starting sshd. Also it fails getting IP information for eth0. xend.log doesn't really show anything wrong [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:486) hotplugStatusCallback 1. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices irq. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices vkbd. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices vfb. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices pci. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices ioports. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices tap. [2007-09-06 11:10:54 xend 9068] DEBUG (DevController:143) Waiting for devices vtpm. [2007-09-06 11:10:54 xend 9068] INFO (XendDomain:370) Domain fedora.fc6 (37) unpaused. [2007-09-06 11:14:23 xend.XendDomainInfo 9068] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-09-06 11:14:23 xend.XendDomainInfo 9068] DEBUG (XendDomainInfo:940) XendDomainInfo.handleShutdownWatch [2007-09-06 11:14:34 xend.XendDomainInfo 9068] INFO (XendDomainInfo:899) Domain has shutdown: name=fedora.fc6 id=37 reason=poweroff. [2007-09-06 11:14:34 xend.XendDomainInfo 9068] DEBUG (XendDomainInfo:1463) XendDomainInfo.destroy: domid=37 [2007-09-06 11:14:34 xend.XendDomainInfo 9068] DEBUG (XendDomainInfo:1471) XendDomainInfo.destroyDomain(37) You can see where it locks up at 11:10:54 and doesn't respond until it shut it down. when I mount the img I can see this error "Sep 6 11:12:19 fc6_pristine modprobe: FATAL: Could not load /lib/modules/2.6.20-1.3001.fc6xen/modules.dep: No such file or directory". my xend guest cfg is : kernel = "/boot/vmlinuz-2.6-xenU" memory = 256 name = "fedora.fc6" vif = [ '' ] dhcp = "dhcp" disk = ['file:/usr/virtualServers/fedora.fc6.img,sda1,w', 'file:/usr/virtualServers/fedora.swap,sda2,w'] root = "/dev/sda1 ro" ramdisk = "/boot/initrd-2.6.20-1.3001.fc6.xen.img" extra = "3" Thanks in advanced for any help! From rjones at redhat.com Fri Sep 7 12:24:00 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Fri, 07 Sep 2007 13:24:00 +0100 Subject: [Fedora-xen] Xen paravirtualized guest freezes upon boot In-Reply-To: <46E01AB0.3060405@jonathan360.com> References: <46E01AB0.3060405@jonathan360.com> Message-ID: <46E142E0.20605@redhat.com> achan at jonathan360.com wrote: > Running xen 3 > > host and guest OS is FC6. > > the guest boots but freezes after starting sshd. Also it fails getting > IP information for eth0. If this is a problem with sshd starting, it's very interesting. Can you boot the guest in single user mode and see if you can trigger the bug by starting sshd manually. Also take a look at 'xm dmesg'. Another route is to upgrade to a more recent hypervisor (ie. Fedora 7 as the host). 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 orcalon at hotmail.com Sat Sep 8 05:21:36 2007 From: orcalon at hotmail.com (orcalon) Date: Sat, 08 Sep 2007 05:21:36 +0000 Subject: [Fedora-xen] fedora 7 Xen doesn't want to boot Message-ID: Hello, I installed Fedora 7 on my Asus L3400Tp (5 GB partition for /, 34 GB for /home), and included vairtualisation with xen in the install. My laptop only supports para-virtualisation, but that doesn't bother me. $ grep pae /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm up After install I did yum update, so now I?m with the kernels as shown in the following exerpt of grub.conf: title Fedora (2.6.22.1-41.fc7) root (hd0,0) kernel /boot/vmlinuz-2.6.22.1-41.fc7 ro root=LABEL=/ rhgb quiet initrd /boot/initrd-2.6.22.1-41.fc7.img title Fedora (2.6.20-2925.13.fc7xen) root (hd0,0) kernel /boot/xen.gz-2.6.20-2925.13.fc7 module /boot/vmlinuz-2.6.20-2925.13.fc7xen ro root=LABEL=/ rhgb quiet module /boot/initrd-2.6.20-2925.13.fc7xen.img However, when I try to start xen, de following messages appear: mount: could not find file system '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /procs: No such file or directory setuproot: error mounting /sys: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - Not syncing: Attempted to kill init! And a reboot follows. I start suspecting a bit that the 'module' vmlinuz-2.6.20-2925.13.fc7xen for xen has a different approach of the hardware, that kernel xen.gz-2.6.20-2925.13.fc7 does something strange with it? But what? Some people suggested to use a LVM designater instead of /dev/sda, others to rebuild initrd, or to remove the 'module' in front of initrd and vmlinuz in grub.conf, but none of those suggestions were successful. Anybody any hint? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From jlagrue at gmail.com Sat Sep 8 09:35:09 2007 From: jlagrue at gmail.com (John Lagrue) Date: Sat, 8 Sep 2007 10:35:09 +0100 Subject: [Fedora-xen] Trouble with Ubuntu guest on F7 Message-ID: Trying to create a Ubuntu 7.10 guest on sn F7 host using a fully virtualised system (I can't use Xen) Using virt-manager to create the guest, selecting OS to be Linux, type as generic 2.6 kernel The guest refuses to boot! It shows the lines: ----------------------------- Booting from CD-Rom ISOLINUX 3.36 Debian-2007-08-30 Copyright blah.de.blah....... Loading... ---------------------------- And that's it. Host CPU count goes to the ceiling, but nothing else happens. I get exactly the same behaviour if I do it from the command line with qemu-kvm. The only way I can get it installed is by using qemu -no-kvm After it is installed (which takes hours!) I can run it reasonably well from virt-manager, though mouse behaviour is horrible. When running it from qemu-kvm on the command line the mouse behaves properly. Any thoughts as to what, if anything, I might be doing wrong? JDL From jlagrue at gmail.com Sat Sep 8 18:01:29 2007 From: jlagrue at gmail.com (John Lagrue) Date: Sat, 8 Sep 2007 19:01:29 +0100 Subject: [Fedora-xen] qemu-kvm error message Message-ID: Can anyone throw some light on this? I get the following message when starting qemu-kvm on Fedora 7 Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. But /proc/sys/dev/rtc doesn't exist! JDL From polytropolis at gmail.com Sat Sep 8 20:24:17 2007 From: polytropolis at gmail.com (Claus Reheis) Date: Sat, 08 Sep 2007 22:24:17 +0200 Subject: [Fedora-xen] Guest Installation via local http fails Message-ID: <1189283057.5490.22.camel@localhost.localdomain> Hi all! I found some time and thought about playing around with Xen 3.1 in Fedora 7! I tried to setup Fedora 7 as a para-virtualized guest on a Fedora 7 host with help of a nice howto in the O`Reilly book about Fedora what suggest the folling steps: 1)Setup a network installation server in Dom0: setenforce 0 ln -s /media/disk/ /var/www/html/fedora service httpd start 2)Start the Installation with virt-manager The installation starts up fine until I can choose the installation method!I choose http and after I always get the Error message: "Unable to retrieve http://192.168.0.123/fedora//images/stage2.img " The strange things are the two *//* !I cant get rid of it!I tried any combination who came to my mind, but no success until now... When I open Firefox and go to http://192.168.0.123/fedora/images/stage2.img or localhost/fedora/images/stage2.img the file just downloads fine without any error! I tried the http installation from a fedora server: http://limestone.uoregon.edu/ftp/fedora/linux/7/Fedora/x86_64/os/ No problem either! So what is wrong with my attempt to install from the local server? Thanks for your help, Claus From rwarsow at online.de Sat Sep 8 21:48:35 2007 From: rwarsow at online.de (Ronald Warsow) Date: Sat, 08 Sep 2007 23:48:35 +0200 Subject: [Fedora-xen] Guest Installation via local http fails In-Reply-To: <1189283057.5490.22.camel@localhost.localdomain> References: <1189283057.5490.22.camel@localhost.localdomain> Message-ID: <46E318B3.6050206@online.de> Claus Reheis wrote: > Hi all! > > I found some time and thought about playing around with Xen 3.1 in > Fedora 7! > I tried to setup Fedora 7 as a para-virtualized guest on a Fedora 7 host > with help of a nice howto in the O`Reilly book about Fedora what suggest > the folling steps: > > 1)Setup a network installation server in Dom0: > > setenforce 0 > > ln -s /media/disk/ /var/www/html/fedora > > service httpd start > > 2)Start the Installation with virt-manager > > The installation starts up fine until I can choose the installation > method!I choose http and after I always get the Error message: > > "Unable to retrieve http://192.168.0.123/fedora//images/stage2.img " > > The strange things are the two *//* !I cant get rid of it!I tried any > combination who came to my mind, but no success until now... > > When I open Firefox and go to > > http://192.168.0.123/fedora/images/stage2.img > > or > > localhost/fedora/images/stage2.img > > the file just downloads fine without any error! > I tried the http installation from a fedora server: > > http://limestone.uoregon.edu/ftp/fedora/linux/7/Fedora/x86_64/os/ > > No problem either! > So what is wrong with my attempt to install from the local server? > 1. I'm not sure if the above can work with ln -s ... , so why not to mount directly under /var/www .... 2. your iptables setting for http maybe ? > Thanks for your help, > > Claus > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen -- Ronald From polytropolis at gmail.com Sat Sep 8 22:18:50 2007 From: polytropolis at gmail.com (Claus Reheis) Date: Sun, 09 Sep 2007 00:18:50 +0200 Subject: [Fedora-xen] Guest Installation via local http fails[SOLVED] In-Reply-To: <46E318B3.6050206@online.de> References: <1189283057.5490.22.camel@localhost.localdomain> <46E318B3.6050206@online.de> Message-ID: <1189289930.5490.29.camel@localhost.localdomain> On Sat, 2007-09-08 at 23:48 +0200, Ronald Warsow wrote: > Claus Reheis wrote: > > Hi all! > > > > I found some time and thought about playing around with Xen 3.1 in > > Fedora 7! > > I tried to setup Fedora 7 as a para-virtualized guest on a Fedora 7 host > > with help of a nice howto in the O`Reilly book about Fedora what suggest > > the folling steps: > > > > 1)Setup a network installation server in Dom0: > > > > setenforce 0 > > > > ln -s /media/disk/ /var/www/html/fedora > > > > service httpd start > > > > 2)Start the Installation with virt-manager > > > > The installation starts up fine until I can choose the installation > > method!I choose http and after I always get the Error message: > > > > "Unable to retrieve http://192.168.0.123/fedora//images/stage2.img " > > > > The strange things are the two *//* !I cant get rid of it!I tried any > > combination who came to my mind, but no success until now... > > > > When I open Firefox and go to > > > > http://192.168.0.123/fedora/images/stage2.img > > > > or > > > > localhost/fedora/images/stage2.img > > > > the file just downloads fine without any error! > > I tried the http installation from a fedora server: > > > > http://limestone.uoregon.edu/ftp/fedora/linux/7/Fedora/x86_64/os/ > > > > No problem either! > > So what is wrong with my attempt to install from the local server? > > > > 1. I'm not sure if the above can work with ln -s ... , so why not to > mount directly under /var/www .... ok > > 2. your iptables setting for http maybe ? ok Changed settings from "Virtual Network" to "Shared physical device = eth0" and its workinf fine now... I dont know what did the trick, but I will find out:) Thanks for your help, Claus > > > > -- > > Fedora-xen mailing list > > Fedora-xen at redhat.com > > https://www.redhat.com/mailman/listinfo/fedora-xen > > From kosago at earthlink.net Mon Sep 10 02:21:03 2007 From: kosago at earthlink.net (kosago) Date: Sun, 09 Sep 2007 21:21:03 -0500 Subject: [Fedora-xen] How do Xen 3.1x guest connect to a sound card? Message-ID: <46E4AA0F.6050005@earthlink.net> How do you pass the pci sound card to xen 3.1x guest using virsh? From accarlson at gmail.com Mon Sep 10 13:47:59 2007 From: accarlson at gmail.com (Augusto Castelan Carlson) Date: Mon, 10 Sep 2007 10:47:59 -0300 Subject: [Fedora-xen] restore failed Message-ID: Hi! I have Xen (fedora 7 with xen 3.1.0) running with 2 guests (both fedora 7). At night I save both guest and mount their partitions to do a backup. Then I restore the saved machines. Everything appears to be working fine, but I had some problems with restore this weekend. When I arrived to work, one of the guest was not running properly. I tried to shutdown the machine and start it again, but got the following error when trying to start: virsh # start virtual_machine_name libvir: Xen Daemon error : POST operation failed: (xend.err "'uname'") error: Failed to start domain virtual_machine_name Seeking for any problem in log files I found some errors: [2007-09-07 09:14:16 2285] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it. : : [2007-09-07 09:14:18 2557] DEBUG (XendDomainInfo:1463) XendDomainInfo.constructDomain [2007-09-07 09:14:18 2557] DEBUG (balloon:113) Balloon: 64248 KiB free; need 2048; done. [2007-09-07 09:14:18 2557] ERROR (XendDomainInfo:434) VM resume failed : : I can attach my full log if needed. I did a restore with a previous saved session and the guest is running ok now. What can be done so that those errors do not occur any more? Thanks in advance, -- Augusto Castelan Carlson From rjones at redhat.com Mon Sep 10 14:05:29 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Mon, 10 Sep 2007 15:05:29 +0100 Subject: [Fedora-xen] How do Xen 3.1x guest connect to a sound card? In-Reply-To: <46E4AA0F.6050005@earthlink.net> References: <46E4AA0F.6050005@earthlink.net> Message-ID: <46E54F29.50304@redhat.com> kosago wrote: > How do you pass the pci sound card to xen 3.1x guest using virsh? I'm pretty certain this isn't possible with virsh, although you can probably do it with Xen configuration files / xm. BTW, I'm interested - what PCI soundcard is this? Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From robert at exa-omicron.nl Wed Sep 12 07:10:38 2007 From: robert at exa-omicron.nl (Robert Verspuy) Date: Wed, 12 Sep 2007 09:10:38 +0200 Subject: [Fedora-xen] Fedora 7 + kernel 2.6.20-2931 + Xen + clvmd gives spinlock bug and hangs Message-ID: <46E790EE.5040902@exa-omicron.nl> Hi All, I'm pretty new in the xen and clustering stuff, but I have the following setup: 2 server (2 x dual Xeon 2GHz, 6GB RAM, 2 x 160GB SATA + 4 x 400GB SATA) Running both fedora 7, latest updates (kernel 2.6.20-2931.fc7xen) I want to set this up as both Dom0's are the storage nodes (with GFS2) And both server are running 2 or 3 XEN VM's with the application (2 x bind, 2 x postfix, 1 x mysql, 1 x postgresql). And the possibility to migrate a VM to the other server in case of any problems. The 2 x 160GB is setup as an raid 1, on top of that LVM with local volumes for /boot, / and This should hold the local files the 4 x 400GB is setup as 3 disks RAID 5 and 1 disk spare, giving me about 800GB of usable diskspace. On top op the RAID 5 I have DRBD, to keep both raid devices between both server in sync. With DRBD v8 it is possible to use them active/active, if you use a cluster aware file system (like GFS2) So I've setup openais, and cman. Running on both servers, interacting fine. When starting clvmd, I get the following (on both servers): Sep 10 10:08:55 fosfor kernel: BUG: spinlock already unlocked on CPU#0, dlm_recoverd/4016 (Not tainted) Sep 10 10:08:56 fosfor kernel: lock: ffff88016158fd50, .magic: dead4ead, .owner: /-1, .owner_cpu: -1 Sep 10 10:08:56 fosfor kernel: Sep 10 10:08:56 fosfor kernel: Call Trace: Sep 10 10:08:56 fosfor kernel: [] _raw_spin_unlock+0x2e/0x7f Sep 10 10:08:56 fosfor kernel: [] :dlm:dlm_lowcomms_get_buffer+0xf7/0x1cb Sep 10 10:08:56 fosfor kernel: [] :dlm:create_rcom+0x3a/0xb3 Sep 10 10:08:56 fosfor kernel: [] :dlm:dlm_rcom_status+0x58/0x137 Sep 10 10:08:56 fosfor kernel: [] :dlm:dlm_set_recover_status+0x1a/0x2e Sep 10 10:08:56 fosfor kernel: [] :dlm:dlm_recover_members+0x332/0x3ea Sep 10 10:08:56 fosfor kernel: [] keventd_create_kthread+0x0/0x6a Sep 10 10:08:56 fosfor kernel: [] :dlm:dlm_recoverd+0x399/0x3e3 Sep 10 10:08:56 fosfor kernel: [] :dlm:dlm_recoverd+0x0/0x3e3 Sep 10 10:08:56 fosfor kernel: [] keventd_create_kthread+0x0/0x6a Sep 10 10:08:56 fosfor kernel: [] kthread+0xd0/0xff Sep 10 10:08:56 fosfor kernel: dlm: got connection from 1 Sep 10 10:08:56 fosfor kernel: [] child_rip+0xa/0x12 Sep 10 10:08:56 fosfor kernel: [] keventd_create_kthread+0x0/0x6a Sep 10 10:08:56 fosfor kernel: [] kthread+0x0/0xff Sep 10 10:08:56 fosfor kernel: [] child_rip+0x0/0x12 Sep 10 10:08:56 fosfor kernel: After that, two dlm processes are running at 100% cpu load at one processor. (also on both servers) When I stop the clvmd service, the server hangs (only the server, where I stop the clvmd) According to http://www.redhat.com/archives/linux-cluster/2007-April/msg00133.html and specially http://www.redhat.com/archives/linux-cluster/2007-April/msg00171.html I should use a kernel 2.6.21 or newer. But this is not available for fedora 7 with xen. I also tried to use an older kerne (2.6.20-2925.9.fc7xen) both that doesn't work also. Or can the cause of this problem be located somewhere else? Does anybody know when a newer kernel for fedora 7 with xen will be released (don't see any new kernel in testing also...) Thnx in advance, Robert Verspuy From jprats at cesca.es Thu Sep 13 09:43:04 2007 From: jprats at cesca.es (Jordi Prats) Date: Thu, 13 Sep 2007 11:43:04 +0200 Subject: [Fedora-xen] SET failed on device eth0 ; No such device Message-ID: <46E90628.60500@cesca.es> Hi all, I'm getting this error while trying to bring up my eth1 (is not a wireless card, is a Broadcom NetXtreme II BCM5708 Gigabit Ethernet) Error for wireless request "Set Encode" (8B2A) : SET failed on device eth1 : No such device. SIOCGFFLAGS: No such device Failed to bring up eth1. Anyone knows why is trying to setup a Gigabit ethernet as a wireless card? My /etc/sysconfig/network-scripts/ifcfg-eth1 is: DEVICE=eth1 ONBOOT=yes NETMASK=255.255.255.0 IPADDR=172.16.1.148 GATEWAY=172.16.1.1 TYPE=Ethernet Thanks! Jordi -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... From pasik at iki.fi Thu Sep 13 12:05:04 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 13 Sep 2007 15:05:04 +0300 Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7? Message-ID: <20070913120504.GH5028@edu.joroinen.fi> http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci1271570,00.html "Finally, Klein said the Windows drivers are already included in the latest Fedora 7 updates but he hasn't had a chance to test them yet. "They are clearly sticking to the timeline they suggested at the Red Hat Summit, in that they won't be releasing the paravirt drivers for Windows until after the 5.1 release," Klein said." Could someone comment on this.. Xen in Fedora 7 includes windows paravirtualized drivers?? -- Pasi From berrange at redhat.com Thu Sep 13 13:06:45 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 13 Sep 2007 14:06:45 +0100 Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7? In-Reply-To: <20070913120504.GH5028@edu.joroinen.fi> References: <20070913120504.GH5028@edu.joroinen.fi> Message-ID: <20070913130645.GB23525@redhat.com> On Thu, Sep 13, 2007 at 03:05:04PM +0300, Pasi K?rkk?inen wrote: > > http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci1271570,00.html > > "Finally, Klein said the Windows drivers are already included in the latest > Fedora 7 updates but he hasn't had a chance to test them yet. "They are > clearly sticking to the timeline they suggested at the Red Hat Summit, in > that they won't be releasing the paravirt drivers for Windows until after > the 5.1 release," Klein said." > > Could someone comment on this.. > > Xen in Fedora 7 includes windows paravirtualized drivers?? No, that journalist is wrong. There are not any windows drivers currently available in F7. 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 achan at jonathan360.com Thu Sep 13 13:08:11 2007 From: achan at jonathan360.com (achan at jonathan360.com) Date: Thu, 13 Sep 2007 09:08:11 -0400 Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7? In-Reply-To: <20070913120504.GH5028@edu.joroinen.fi> References: <20070913120504.GH5028@edu.joroinen.fi> Message-ID: <46E9363B.6090206@jonathan360.com> It was my understanding that windows drivers in paravairtualization is not possible because of the windows kernel, not because of lack of drivers. For it to work properly the kernel would need altered which is against the EULA of Microsoft. At least that was my understanding. Pasi K?rkk?inen wrote: > http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci1271570,00.html > > "Finally, Klein said the Windows drivers are already included in the latest > Fedora 7 updates but he hasn't had a chance to test them yet. "They are > clearly sticking to the timeline they suggested at the Red Hat Summit, in > that they won't be releasing the paravirt drivers for Windows until after > the 5.1 release," Klein said." > > Could someone comment on this.. > > Xen in Fedora 7 includes windows paravirtualized drivers?? > > -- Pasi > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From pasik at iki.fi Thu Sep 13 13:12:30 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 13 Sep 2007 16:12:30 +0300 Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7? In-Reply-To: <20070913130645.GB23525@redhat.com> References: <20070913120504.GH5028@edu.joroinen.fi> <20070913130645.GB23525@redhat.com> Message-ID: <20070913131230.GI5028@edu.joroinen.fi> On Thu, Sep 13, 2007 at 02:06:45PM +0100, Daniel P. Berrange wrote: > On Thu, Sep 13, 2007 at 03:05:04PM +0300, Pasi K?rkk?inen wrote: > > > > http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci1271570,00.html > > > > "Finally, Klein said the Windows drivers are already included in the latest > > Fedora 7 updates but he hasn't had a chance to test them yet. "They are > > clearly sticking to the timeline they suggested at the Red Hat Summit, in > > that they won't be releasing the paravirt drivers for Windows until after > > the 5.1 release," Klein said." > > > > Could someone comment on this.. > > > > Xen in Fedora 7 includes windows paravirtualized drivers?? > > No, that journalist is wrong. There are not any windows drivers currently > available in F7. > That's what I thought too.. I was wondering if I had missed something :) Thanks. -- Pasi From pasik at iki.fi Thu Sep 13 13:15:55 2007 From: pasik at iki.fi (Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?=) Date: Thu, 13 Sep 2007 16:15:55 +0300 Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7? In-Reply-To: <46E9363B.6090206@jonathan360.com> References: <20070913120504.GH5028@edu.joroinen.fi> <46E9363B.6090206@jonathan360.com> Message-ID: <20070913131555.GJ5028@edu.joroinen.fi> On Thu, Sep 13, 2007 at 09:08:11AM -0400, achan at jonathan360.com wrote: > It was my understanding that windows drivers in paravairtualization is > not possible because of the windows kernel, not because of lack of > drivers. For it to work properly the kernel would need altered which is > against the EULA of Microsoft. At least that was my understanding. Nope, that's not true. Xensource, Virtual Iron and Novell have Windows paravirtualized drivers available for Xen, but they are commercial and only work with their products.. and I think Redhat is planning to have them later this year as well. I think nothing prevents making opensource windows paravirtualized xen drivers.. the problem is that it's so huge job, that noone has done that yet.. or people/companies who have done that, want to get paid for their work.. -- Pasi > Pasi K?rkk?inen wrote: > >http://searchenterpriselinux.techtarget.com/originalContent/0,289142,sid39_gci1271570,00.html > > > >"Finally, Klein said the Windows drivers are already included in the latest > >Fedora 7 updates but he hasn't had a chance to test them yet. "They are > >clearly sticking to the timeline they suggested at the Red Hat Summit, in > >that they won't be releasing the paravirt drivers for Windows until after > >the 5.1 release," Klein said." > > > >Could someone comment on this.. > > > >Xen in Fedora 7 includes windows paravirtualized drivers?? > > > >-- Pasi > > From berrange at redhat.com Thu Sep 13 13:20:32 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 13 Sep 2007 14:20:32 +0100 Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7? In-Reply-To: <46E9363B.6090206@jonathan360.com> References: <20070913120504.GH5028@edu.joroinen.fi> <46E9363B.6090206@jonathan360.com> Message-ID: <20070913132031.GC23525@redhat.com> On Thu, Sep 13, 2007 at 09:08:11AM -0400, achan at jonathan360.com wrote: > It was my understanding that windows drivers in paravairtualization is > not possible because of the windows kernel, not because of lack of > drivers. For it to work properly the kernel would need altered which is > against the EULA of Microsoft. At least that was my understanding. That is partially true. If you want to use the DDK, then it is not possible to make your drivers GPL, but you could choose other open source licenses I believe. You would end up with a situation where the source was technically one license, but the binary became a different license. eg BSD source, but Combined BSD / Microsoft DDK for the binary. In theory you don't have to use the DDK, but not doing so would involve huge amounts of extra programming work. It all rather sucks, but that's Windows for you. IANAL btw :-) 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 jprats at cesca.es Thu Sep 13 13:31:35 2007 From: jprats at cesca.es (Jordi Prats) Date: Thu, 13 Sep 2007 15:31:35 +0200 Subject: [Fedora-xen] Buf destroying a Windows virtual machine Message-ID: <46E93BB7.9060300@cesca.es> Hi all, I've got this message destroying a Windows-based virtual machine. I'm using this kernel: 2.6.20-2931.fc7xen best regards, [root at inf20 ~]# xm destroy kriptonita Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: ------------[ cut here ]------------[root at inf20 ~]# Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: invalid opcode: 0000 [#2] Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: SMP Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: CPU: 2 Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: EIP: 0061:[] Not tainted VLI Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: EFLAGS: 00210282 (2.6.20-2931.fc7xen #1) Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: EIP is at xen_pgd_pin+0x57/0x62 Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: eax: ffffffea ebx: c1cdcebc ecx: 00000001 edx: 00000000 Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: esi: 00007ff0 edi: 00000000 ebp: c1cdced0 esp: c1cdcebc Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: ds: 007b es: 007b ss: 0069 Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: Process udevd (pid: 526, ti=c1cdc000 task=cb66d530 task.ti=c1cdc000) Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: Stack: 00000002 0028aa31 24631000 0048c620 c171f340 c1cdcedc c1014315 c171f3ac Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: c1cdceec c1014345 c132fb1c 00000000 c1cdcef4 c1014dbc c1cdcf44 c101e8a0 Message from syslogd@ at Thu Jul 12 05:39:34 2007 ... inf20 kernel: ecbb1508 00006059 c12fa300 c1cdcfb8 bfbfb594 01200011 00000000 e46c6070 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: Call Trace: Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] show_trace_log_lvl+0x1a/0x2f Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] show_stack_log_lvl+0x9b/0xa3 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] show_registers+0x194/0x26a Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] die+0x13a/0x24f Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] do_trap+0x79/0x91 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] do_invalid_op+0x97/0xa1 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] error_code+0x35/0x3c Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] __pgd_pin+0x32/0x40 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] mm_pin+0x22/0x2d Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] _arch_dup_mmap+0x27/0x29 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] copy_process+0xb25/0x1135 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] do_fork+0x50/0x117 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] sys_clone+0x33/0x39 Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: [] syscall_call+0x7/0xb Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: ======================= Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: Code: eb fe a1 24 42 38 c1 8b 14 90 81 e2 ff ff ff 7f 89 55 f0 8d 5d ec b9 01 00 00 00 31 d2 be f0 7f 00 00 e8 28 92 fe ff 85 c0 79 04 <0f> 0b eb fe 83 c4 0c 5b 5e 5d c3 55 89 c2 89 e5 56 53 83 ec 0c Message from syslogd@ at Thu Jul 12 05:39:35 2007 ... inf20 kernel: EIP: [] xen_pgd_pin+0x57/0x62 SS:ESP 0069:c1cdcebc [root at inf20 ~]# -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... From jklein at saugus.k12.ca.us Thu Sep 13 16:58:19 2007 From: jklein at saugus.k12.ca.us (Jim Klein) Date: Thu, 13 Sep 2007 09:58:19 -0700 (PDT) Subject: [Fedora-xen] Xen Windows paravirtualized drivers in Fedora 7 Message-ID: <12965766.3256361189702699764.JavaMail.root@do8> Oops! Sorry guys - this was my fault. I had read somewhere (I thought it was on this list) that there was compilable source for paravirt drivers in there, but hadn't actually checked it out before I mentioned it to Jack. I said that I hadn't had a chance to check them out, but I wasn't real clear in my email (was typing on a cell phone, so I wasn't real wordy.) My bad. --Jim >Date: Thu, 13 Sep 2007 14:20:32 +0100 >From: "Daniel P. Berrange" >Subject: Re: [Fedora-xen] Xen Windows paravirtualized drivers in >Fedora 7? >To: "achan at jonathan360.com" >Cc: fedora-xen at redhat.com >Message-ID: <20070913132031.GC23525 at redhat.com> >Content-Type: text/plain; charset=us-ascii > >On Thu, Sep 13, 2007 at 09:08:11AM -0400, achan at jonathan360.com wrote: >> It was my understanding that windows drivers in paravairtualization is >> not possible because of the windows kernel, not because of lack of >> drivers. For it to work properly the kernel would need altered which is >> against the EULA of Microsoft. At least that was my understanding. > >That is partially true. If you want to use the DDK, then it is not possible >to make your drivers GPL, but you could choose other open source licenses >I believe. You would end up with a situation where the source was technically >one license, but the binary became a different license. eg BSD source, but >Combined BSD / Microsoft DDK for the binary. In theory you don't have to >use the DDK, but not doing so would involve huge amounts of extra programming >work. It all rather sucks, but that's Windows for you. IANAL btw :-) > >Dan. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jackley.cesar at gmail.com Thu Sep 13 20:06:55 2007 From: jackley.cesar at gmail.com (Jackley Cesar) Date: Thu, 13 Sep 2007 16:06:55 -0400 Subject: [Fedora-xen] Virt-install with no-graphics Message-ID: <4d8475a60709131306n7a5ef48fn2f5bb7488a94539d@mail.gmail.com> I try to do a guest OS install remotely using virt-install but the installation process hangs with the following error: "Write protecting the kernel read-only data: 938k" Any hint would be helpful - Thanks P.S -Domain-0 is running FC7 From achan at jonathan360.com Thu Sep 13 20:12:28 2007 From: achan at jonathan360.com (achan at jonathan360.com) Date: Thu, 13 Sep 2007 16:12:28 -0400 Subject: [Fedora-xen] Virt-install with no-graphics In-Reply-To: <4d8475a60709131306n7a5ef48fn2f5bb7488a94539d@mail.gmail.com> References: <4d8475a60709131306n7a5ef48fn2f5bb7488a94539d@mail.gmail.com> Message-ID: <46E999AC.5090709@jonathan360.com> I'm not a xen veteran but I can tell you that isn't much information for us to go on :) Did you check your log files? (/var/logs/xen/xend.log) or even the qemu log file. Is this paravirt or fully-virt? What does your guest system config file look like? ~jmd Jackley Cesar wrote: > I try to do a guest OS install remotely using virt-install but the > installation process hangs with the following error: > > "Write protecting the kernel read-only data: 938k" > > > Any hint would be helpful - > > > Thanks > > P.S -Domain-0 is running FC7 > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > From turtlevelo at yahoo.com Fri Sep 14 10:42:18 2007 From: turtlevelo at yahoo.com (Costa Kavanides) Date: Fri, 14 Sep 2007 03:42:18 -0700 (PDT) Subject: [Fedora-xen] domU disregard static IP information at boot time Message-ID: <380454.10060.qm@web30309.mail.mud.yahoo.com> My dom0 has kernel 2.6.20-2931.fc7xen whereas the fully virtualised domU has kernel 2.6.21-1.3194.fc7. I wanted a static IP address for the domU thus I specified it during installation + in the xen config file. Notwithstanding all my efforts to tell it that it has to use a static IP address, whenever domU boots it always look for a DHCP server to get its IP address from. Even changing the lines in ifcfg-eth0 to define a static IP address is not a solution. With next reboot it still wants a DHCP server to provide the IP address. Changing ifcfg-eth0 + issuing an "service network restart" works as long as there is no reboot. As soon as I reboot the odd behaviour prevails. Where may act to change this behaviour? costa ------------------------- domU xen config file -------------------- import os, re arch = os.uname()[4] if re.search('64', arch): arch_libdir = 'lib64' else: arch_libdir = 'lib' kernel = "/usr/lib/xen/boot/hvmloader" builder='hvm' memory = 256 shadow_memory = 8 name = "Test_2_FC7" vif = [ 'type=ioemu, ip=192.168.2.29, mac=00:16:3e:00:00:11, bridge=xenbr0' ] disk = [ \ 'file:/home/XEN/images/FC7_disk_2.img,hda,r', \ 'phy:/dev/cdrom,hdb:cdrom,r', \ ] on_poweroff = 'destroy' on_reboot = 'restart' on_crash = 'restart' device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm' boot = "c" sdl=1 vnc=0 stdvga=0 serial='pty' usbdevice='tablet' ____________________________________________________________________________________ Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV. http://tv.yahoo.com/ From i4varu at yahoo.com Fri Sep 14 13:35:45 2007 From: i4varu at yahoo.com (Valdas) Date: Fri, 14 Sep 2007 06:35:45 -0700 (PDT) Subject: [Fedora-xen] Guest Installation via local http fails In-Reply-To: <1189283057.5490.22.camel@localhost.localdomain> References: <1189283057.5490.22.camel@localhost.localdomain> Message-ID: <12675542.post@talk.nabble.com> I think the problem is, when DomU get's it's ip address,DomU has it's own localhost (127.0.0.1 address), so then it asks you to choose new location enter eth0 ip address for dom0 machine, and the it will find installation. Claus Reheis wrote: > > Hi all! > > I found some time and thought about playing around with Xen 3.1 in > Fedora 7! > I tried to setup Fedora 7 as a para-virtualized guest on a Fedora 7 host > with help of a nice howto in the O`Reilly book about Fedora what suggest > the folling steps: > > 1)Setup a network installation server in Dom0: > > setenforce 0 > > ln -s /media/disk/ /var/www/html/fedora > > service httpd start > > 2)Start the Installation with virt-manager > > The installation starts up fine until I can choose the installation > method!I choose http and after I always get the Error message: > > "Unable to retrieve http://192.168.0.123/fedora//images/stage2.img " > > The strange things are the two *//* !I cant get rid of it!I tried any > combination who came to my mind, but no success until now... > > When I open Firefox and go to > > http://192.168.0.123/fedora/images/stage2.img > > or > > localhost/fedora/images/stage2.img > > the file just downloads fine without any error! > I tried the http installation from a fedora server: > > http://limestone.uoregon.edu/ftp/fedora/linux/7/Fedora/x86_64/os/ > > No problem either! > So what is wrong with my attempt to install from the local server? > > Thanks for your help, > > Claus > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > -- View this message in context: http://www.nabble.com/Guest-Installation-via-local-http-fails-tf4407145.html#a12675542 Sent from the Fedora Xen mailing list archive at Nabble.com. From turtlevelo at yahoo.com Fri Sep 14 15:07:59 2007 From: turtlevelo at yahoo.com (Costa Kavanides) Date: Fri, 14 Sep 2007 08:07:59 -0700 (PDT) Subject: [Fedora-xen] domU disregard static IP information at boot time In-Reply-To: <380454.10060.qm@web30309.mail.mud.yahoo.com> Message-ID: <265694.15592.qm@web30313.mail.mud.yahoo.com> Further searching led me to find this thread http://lists.xensource.com/archives/html/xen-users/2007-01/msg01110.html where the same issue is discussed amongst others. I disabled kudzu (chkconfig kudzu off) and now my network interface static information are properly used at boot time. Costa. --- Costa Kavanides wrote: > My dom0 has kernel 2.6.20-2931.fc7xen whereas the > fully virtualised > domU has kernel 2.6.21-1.3194.fc7. > > I wanted a static IP address for the domU thus I > specified it during > installation + in the xen config file. > > Notwithstanding all my efforts to tell it that it > has > to use a static IP > address, whenever domU boots it always look for a > DHCP > server to get its > IP address from. > Even changing the lines in ifcfg-eth0 to define a > static IP address is not a solution. With next > reboot > it still wants a DHCP server to provide the IP > address. > Changing ifcfg-eth0 + issuing an "service network > restart" works as long as there is no reboot. As > soon > as I reboot the odd behaviour prevails. > > Where may act to change this behaviour? > > costa > ------------------------- > > domU xen config file > -------------------- > import os, re > arch = os.uname()[4] > if re.search('64', arch): > arch_libdir = 'lib64' > else: > arch_libdir = 'lib' > kernel = "/usr/lib/xen/boot/hvmloader" > builder='hvm' > memory = 256 > shadow_memory = 8 > name = "Test_2_FC7" > vif = [ 'type=ioemu, ip=192.168.2.29, > mac=00:16:3e:00:00:11, bridge=xenbr0' ] > disk = [ \ > > 'file:/home/XEN/images/FC7_disk_2.img,hda,r', > \ > 'phy:/dev/cdrom,hdb:cdrom,r', \ > ] > on_poweroff = 'destroy' > on_reboot = 'restart' > on_crash = 'restart' > device_model = '/usr/' + arch_libdir + > '/xen/bin/qemu-dm' > boot = "c" > sdl=1 > vnc=0 > stdvga=0 > serial='pty' > usbdevice='tablet' > > > > > ____________________________________________________________________________________ > Tonight's top picks. What will you watch tonight? > Preview the hottest shows on Yahoo! TV. > http://tv.yahoo.com/ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433 From jlagrue at gmail.com Fri Sep 14 21:21:48 2007 From: jlagrue at gmail.com (John Lagrue) Date: Fri, 14 Sep 2007 22:21:48 +0100 Subject: [Fedora-xen] Resend: qemu-kvm error message Message-ID: Can anyone throw some light on this? I get the following message when starting qemu-kvm on Fedora 7 Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. But /proc/sys/dev/rtc doesn't exist! JDL From selinux at gmail.com Fri Sep 14 21:29:19 2007 From: selinux at gmail.com (Tom London) Date: Fri, 14 Sep 2007 14:29:19 -0700 Subject: [Fedora-xen] Resend: qemu-kvm error message In-Reply-To: References: Message-ID: <4c4ba1530709141429n48e25520n71a466a5fccc59d@mail.gmail.com> On 9/14/07, John Lagrue wrote: > Can anyone throw some light on this? > > I get the following message when starting qemu-kvm on Fedora 7 > > Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal > error, but for better emulation accuracy either use a 2.6 host Linux kernel or > type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. > > > But /proc/sys/dev/rtc doesn't exist! > > JDL > Believe latest kernels 'renamed' this to /proc/sys/dev/hpet/max-user-freq. tom -- Tom London From goodarz.shirazi at stadt-frankfurt.de Fri Sep 14 22:58:29 2007 From: goodarz.shirazi at stadt-frankfurt.de (Shirazi, Goodarz) Date: Sat, 15 Sep 2007 00:58:29 +0200 Subject: [Fedora-xen] Problems running xp guest Message-ID: <4BF62248512F2A4AA5D4FD7E94A011F0017DE068@CITYWMX0032.city.net.ffm> Hi, I'm running FC7 with the 2.6.20-2931.fc7xen kernel and used virt-manager to configure a xp guest domain. I receive the following message after trying to run the xp guest: virsh # start xp (xend.err 'Device 0 (vif) could not be connected. Hotplug scripts not working.') virsh # dumpxml xp xp 0fe4b14b-ce6a-d84c-dc69-1f9e0cce544d hvm /usr/lib/xen/boot/hvmloader 512000 1 destroy restart restart /usr/lib/xen/bin/qemu-dm winxp.iso one provided in such a way: dd if=/dev/cdrom of=/var/lib/xen/images/winxp.iso for an assistance I am very grateful, Goodarz -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at davey.net.au Sun Sep 16 03:03:45 2007 From: lists at davey.net.au (John Arthur) Date: Sun, 16 Sep 2007 12:33:45 +0930 Subject: [Fedora-xen] Problems installing DomU on a new system using virt-manager Message-ID: <002801c7f80e$32298180$f6801eac@tau> Fedora 7 - fully updated with yum. I've just built a new x86_64 system Intel Duo Core 2 E6420 on an Intel DG965WH mb. There appears to be a major bug (amongst many others) in virt-manager which only appears when installing the very first DomU. If I try to install the first DomU connecting to a virtual network the install fails every time right after I configure the network interface when retrieving stage2.img. It just hangs restarting the DomU results in a boot failure message. If I install the first DomU using a shared network the install is successful. Now for the fun part. If then I delete the DomU supposedly returning to a clean slate I can now install DomU's using a virtual network. It appears that installing the first DomU using a shared network changes something that causes virtual network DomU's to install successfully even if the first "shared network" is simply installed and then immediately deleted. Does anyone have any suggestions as to what might be happening? Does virt-manager use any install scripts, if so can they be customized? Regards John From ehabkost at redhat.com Mon Sep 17 14:45:25 2007 From: ehabkost at redhat.com (Eduardo Habkost) Date: Mon, 17 Sep 2007 11:45:25 -0300 Subject: [Fedora-xen] Buf destroying a Windows virtual machine In-Reply-To: <46E93BB7.9060300@cesca.es> References: <46E93BB7.9060300@cesca.es> Message-ID: <20070917144525.GB31763@blackpad.ctb.virtua.com.br> Hi, On Thu, Sep 13, 2007 at 03:31:35PM +0200, Jordi Prats wrote: > Hi all, > I've got this message destroying a Windows-based virtual machine. I'm > using this kernel: 2.6.20-2931.fc7xen > > best regards, > > [root at inf20 ~]# xm destroy kriptonita > > inf20 kernel: EIP is at xen_pgd_pin+0x57/0x62 This one was fixed recently[1], and I have requested it to be pushed to F-7 updates-testing. [1] https://bugzilla.redhat.com/show_bug.cgi?id=252301 -- Eduardo From ehabkost at redhat.com Mon Sep 17 15:00:07 2007 From: ehabkost at redhat.com (Eduardo Habkost) Date: Mon, 17 Sep 2007 12:00:07 -0300 Subject: [Fedora-xen] SET failed on device eth0 ; No such device In-Reply-To: <46E90628.60500@cesca.es> References: <46E90628.60500@cesca.es> Message-ID: <20070917150007.GC31763@blackpad.ctb.virtua.com.br> On Thu, Sep 13, 2007 at 11:43:04AM +0200, Jordi Prats wrote: > Hi all, > I'm getting this error while trying to bring up my eth1 (is not a > wireless card, is a Broadcom NetXtreme II BCM5708 Gigabit Ethernet) > > Error for wireless request "Set Encode" (8B2A) : > SET failed on device eth1 : No such device. > SIOCGFFLAGS: No such device > Failed to bring up eth1. By looking at the ifup scripts, it seems that the real problem is why iwconfig is reporting "No such device" instead of "no wireless extensions". Is eth1 appearing on 'ip link show' and 'ifconfig -a' output? Is it a xen bridge set up by the Xen scripts, or a normal network interface? -- Eduardo From noisilysilent at nerdshack.com Mon Sep 17 16:16:49 2007 From: noisilysilent at nerdshack.com (NoisilySilent) Date: Mon, 17 Sep 2007 18:16:49 +0200 Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt machine, rdesktop connection. Message-ID: <000301c7f946$27c02800$cdda0259@2M9MV1J> Hi, I used to run Windows XP inside a XEN virtual machine on FC6. Everything was perfect. To connect to the Windows XP virtual machine, I used to run rdesktop. Today I installed FC7 from scratch and tried to use my Windows XP virtual machine and I noticed a very strange behaviour: All of this stuff runs on a Dell Latitude D620 laptop. This laptop offers a touchpad, a trackpoint and of course USB ports on which I connect a 3 button wheel mice. FC7 is up to date and all packages are at last date version, including XEN. Now when I connect to the Windows XP virtual machine via rdesktop, after a few minutes the trackpoint and the mouse get weird: when using either the trackpoint or the mouse moving rightwards, the pointer gets "stuck" on the left border of the screen whereas I can still use the touchpad and things don't get messed up. However, when using FC7 without XEN, I don't encounter this trouble. Have you ever heard of such a problem? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From ehabkost at redhat.com Mon Sep 17 17:50:02 2007 From: ehabkost at redhat.com (Eduardo Habkost) Date: Mon, 17 Sep 2007 14:50:02 -0300 Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt machine, rdesktop connection. In-Reply-To: <000301c7f946$27c02800$cdda0259@2M9MV1J> References: <000301c7f946$27c02800$cdda0259@2M9MV1J> Message-ID: <20070917175002.GA7163@blackpad.ctb.virtua.com.br> On Mon, Sep 17, 2007 at 06:16:49PM +0200, NoisilySilent wrote: > > Now when I connect to the Windows XP virtual machine via rdesktop, after a > few minutes the trackpoint and the mouse get weird: when using either the > trackpoint or the mouse moving rightwards, the pointer gets "stuck" on the > left border of the screen whereas I can still use the touchpad and things > don't get messed up. > > However, when using FC7 without XEN, I don't encounter this trouble. > > Have you ever heard of such a problem? I had this weird cursor behaviour last week, on Fedora 7. I was running a Xen kernel, also (2.6.20-2931, probably; but it could be a different version). If I recall correctly, I didn't have any guest running at the time. It happened when I started an Eclipse-based application[1]. The cursor could be moved to the right, but only if I moved the mouse very slowly. On my case, it was a desktop machine, so I didn't have a touchpad, just an USB mouse. However, I didn't manage to reproduce the problem today. Is it easily reproducible, on your case? [1] It was a IDE from QNX I had just installed for testing. -- Eduardo From noisilysilent at nerdshack.com Mon Sep 17 18:15:35 2007 From: noisilysilent at nerdshack.com (NoisilySilent) Date: Mon, 17 Sep 2007 20:15:35 +0200 Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt machine, rdesktop connection. Message-ID: <000f01c7f956$bef8f980$cdda0259@2M9MV1J> Hey, this is EXACTLY the same behavior!!! Actually I think we are facing the same problem. I can move it to the right slowly too. This sounds really similar. Unfortunately, in my situation it is reproducible as it happens every time :( In fact, nothing runs within the host FC7 except Xorg. I thought it might have been a window manager problem as bonobo doesn't start anymore when xen is launched... so I shifted from Gnome to XFCE but this didn't change anything. So, apart from Xorg and rdesktop, nothing runs in FC7, everything runs within the hosted Win XP. What bugs me most is that it doesn't appear when launching anything in particular: I'm simply quietly working in my Windows session and all in a sudden, the pointer gets stuck in the left. Well, this is not that dramatically annoying as I can still use the touchpad, but still it's frustrating: I'm the mouse type, not the touchpad one ;-) -----Message d'origine----- De?: Eduardo Habkost [mailto:ehabkost at redhat.com] Envoy??: lundi 17 septembre 2007 19:50 ??: NoisilySilent Cc?: fedora-xen at redhat.com Objet?: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt machine, rdesktop connection. On Mon, Sep 17, 2007 at 06:16:49PM +0200, NoisilySilent wrote: > > Now when I connect to the Windows XP virtual machine via rdesktop, after a > few minutes the trackpoint and the mouse get weird: when using either the > trackpoint or the mouse moving rightwards, the pointer gets "stuck" on the > left border of the screen whereas I can still use the touchpad and things > don't get messed up. > > However, when using FC7 without XEN, I don't encounter this trouble. > > Have you ever heard of such a problem? I had this weird cursor behaviour last week, on Fedora 7. I was running a Xen kernel, also (2.6.20-2931, probably; but it could be a different version). If I recall correctly, I didn't have any guest running at the time. It happened when I started an Eclipse-based application[1]. The cursor could be moved to the right, but only if I moved the mouse very slowly. On my case, it was a desktop machine, so I didn't have a touchpad, just an USB mouse. However, I didn't manage to reproduce the problem today. Is it easily reproducible, on your case? [1] It was a IDE from QNX I had just installed for testing. -- Eduardo From ehabkost at redhat.com Mon Sep 17 19:01:45 2007 From: ehabkost at redhat.com (Eduardo Pereira Habkost) Date: Mon, 17 Sep 2007 16:01:45 -0300 Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt machine, rdesktop connection. In-Reply-To: <000e01c7f956$71a2b220$cdda0259@2M9MV1J> References: <20070917175002.GA7163@blackpad.ctb.virtua.com.br> <000e01c7f956$71a2b220$cdda0259@2M9MV1J> Message-ID: <20070917190145.GC7163@blackpad.ctb.virtua.com.br> On Mon, Sep 17, 2007 at 08:13:23PM +0200, NoisilySilent wrote: > Hey, this is EXACTLY the same behavior!!! > > Actually I think we are facing the same problem. > I can move it to the right slowly too. > This sounds really similar. > > Unfortunately, in my situation it is reproducible as it happens every time > :( I have managed to reproduce it without using the Eclipse-based application. I simply create a new full-virtualization guest (using virt-install) while moving heavily the mouse cursor. It will eventually get stuck in the left side of the display, when the vncviewer Window is shown. Restarting the X server solves the problem most of times, but I managed to get the cursor stuck on the left if I move the mouse heavily while the X server is restarting. I have found a workaround, also: 'xset m 1/1 1000' (in practice it will disable the mouse acceleration by setting a huge threshold) make the cursor behave properly. Enabling mouse acceleration again gets the cursor stuck again. This makes me believe that this is a Xorg bug, but that may be triggered more easily when running Xen. -- Eduardo From ehabkost at redhat.com Mon Sep 17 21:39:02 2007 From: ehabkost at redhat.com (Eduardo Pereira Habkost) Date: Mon, 17 Sep 2007 18:39:02 -0300 Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt machine, rdesktop connection. In-Reply-To: <20070917190145.GC7163@blackpad.ctb.virtua.com.br> References: <20070917175002.GA7163@blackpad.ctb.virtua.com.br> <000e01c7f956$71a2b220$cdda0259@2M9MV1J> <20070917190145.GC7163@blackpad.ctb.virtua.com.br> Message-ID: <20070917213902.GD7163@blackpad.ctb.virtua.com.br> On Mon, Sep 17, 2007 at 04:01:45PM -0300, Eduardo Pereira Habkost wrote: > > I have managed to reproduce it without using the Eclipse-based > application. > > I simply create a new full-virtualization guest (using virt-install) > while moving heavily the mouse cursor. It will eventually get stuck in > the left side of the display, when the vncviewer Window is shown. I have opened a bug for this: https://bugzilla.redhat.com/show_bug.cgi?id=294011 -- Eduardo From jprats at cesca.es Tue Sep 18 09:44:44 2007 From: jprats at cesca.es (Jordi Prats) Date: Tue, 18 Sep 2007 11:44:44 +0200 Subject: [Fedora-xen] SET failed on device eth0 ; No such device In-Reply-To: <20070917150007.GC31763@blackpad.ctb.virtua.com.br> References: <46E90628.60500@cesca.es> <20070917150007.GC31763@blackpad.ctb.virtua.com.br> Message-ID: <46EF9E0C.6020409@cesca.es> Hi, I suspect it's something related to use multiple network devices. I have this script to setup two bridges, if I disable it all works fine. Anyone? Thank you ! #!/bin/bash #JPC - per crear les dues interficies - 2006 12 22 dir=$(dirname "$0") . "$dir/xen-script-common.sh" . "$dir/xen-network-common.sh" findCommand "$@" case "$command" in start) vifnum=0 bridge=servei netdev=eth0 /etc/xen/scripts/network-bridge start vifnum=1 bridge=dades netdev=eth1 /etc/xen/scripts/network-bridge start ;; stop) vifnum=0 bridge=servei netdev=eth0 /etc/xen/scripts/network-bridge stop vifnum=1 bridge=dades netdev=eth1 /etc/xen/scripts/network-bridge stop ;; status) vifnum=0 bridge=servei netdev=eth0 /etc/xen/scripts/network-bridge status vifnum=1 bridge=dades netdev=eth1 /etc/xen/scripts/network-bridge status ;; *) echo "Unknown command: $command" >&2 echo 'Valid commands are: start, stop, status' >&2 exit 1 esac Eduardo Habkost wrote: > On Thu, Sep 13, 2007 at 11:43:04AM +0200, Jordi Prats wrote: > >> Hi all, >> I'm getting this error while trying to bring up my eth1 (is not a >> wireless card, is a Broadcom NetXtreme II BCM5708 Gigabit Ethernet) >> >> Error for wireless request "Set Encode" (8B2A) : >> SET failed on device eth1 : No such device. >> SIOCGFFLAGS: No such device >> Failed to bring up eth1. >> > > By looking at the ifup scripts, it seems that the real problem is > why iwconfig is reporting "No such device" instead of "no wireless > extensions". Is eth1 appearing on 'ip link show' and 'ifconfig -a' output? > > Is it a xen bridge set up by the Xen scripts, or a normal network > interface? > > -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... From nooroon at gmail.com Tue Sep 18 15:03:42 2007 From: nooroon at gmail.com (mathieu rohon) Date: Tue, 18 Sep 2007 17:03:42 +0200 Subject: [Fedora-xen] Hide the host Message-ID: <7675761b0709180803p353f7464l732e7577ac20ecc1@mail.gmail.com> Hi all, I'd like to use xen with fedora as host, and several OSes as guest (in fact 2). The aim is to use the host as a router for the guests. So i'd like to make the host as thin as possible, in order to provide most power to the guest. Do you know a smart way to do so? I'd also like to hide the host from the user. When the user log in the host, a script is launched, and the appropriated guest start in full screen. Does anyone has already done something similar? thanks for all. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjones at redhat.com Tue Sep 18 17:14:21 2007 From: rjones at redhat.com (Richard W.M. Jones) Date: Tue, 18 Sep 2007 18:14:21 +0100 Subject: [Fedora-xen] Hide the host In-Reply-To: <7675761b0709180803p353f7464l732e7577ac20ecc1@mail.gmail.com> References: <7675761b0709180803p353f7464l732e7577ac20ecc1@mail.gmail.com> Message-ID: <46F0076D.8020302@redhat.com> mathieu rohon wrote: > Hi all, > > I'd like to use xen with fedora as host, and several OSes as guest (in > fact 2). > The aim is to use the host as a router for the guests. > So i'd like to make the host as thin as possible, in order to provide > most power to the guest. Do you know a smart way to do so? > > I'd also like to hide the host from the user. When the user log in the > host, a script is launched, and the appropriated guest start in full > screen. Does anyone has already done something similar? Will the guests be running all the time or do you wish to launch a new guest for each login? The simplest case is probably going to be when you have the guests running all the time. In that case, edit /etc/inittab to disable normal mingetty, and replace with a script which runs a vncviewer and connects to the guest. (Mind you, launching the vncviewer under X is going to be a little more complex ...) Also have a start-up script under /etc/init.d which launches the guests, or make use of the /etc/init.d/xendomains script which does the same thing. Beware that while you want a "thin" dom0, you want to avoid making it too small, because in Xen at least the dom0 runs processes on behalf of the guests. Not least if you have file-backed guests then there is a process called either qemu-dm or tapdisk which takes a significant amount of CPU and RAM. (Guests which have their disks mapped directly to LVs or partitions seem to be much more efficient in this respect). Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3237 bytes Desc: S/MIME Cryptographic Signature URL: From rmigh at hotmail.com Tue Sep 18 18:05:15 2007 From: rmigh at hotmail.com (miguel) Date: Tue, 18 Sep 2007 11:05:15 -0700 Subject: [Fedora-xen] Re: FC7 MOUSE PROBLEMS References: <20070918160011.692B7733CA@hormel.redhat.com> Message-ID: Thanks for submitting the bug report. I reported this problem over 4 months ago, but I never created a bug for it. This problem occurred on 3 different DELL systems I was working with ( 2 laptops and 1 desktop). I'll try your workaround to see If it works on my systems. Thanks ----- Original Message ----- From: To: Sent: Tuesday, September 18, 2007 9:00 AM Subject: Fedora-xen Digest, Vol 22, Issue 17 > Send Fedora-xen mailing list submissions to > fedora-xen at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-xen > or, via email, send a message with subject or body 'help' to > fedora-xen-request at redhat.com > > You can reach the person managing the list at > fedora-xen-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fedora-xen digest..." > > > Today's Topics: > > 1. Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (NoisilySilent) > 2. Re: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (Eduardo Habkost) > 3. RE: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (NoisilySilent) > 4. Re: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (Eduardo Pereira Habkost) > 5. Re: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (Eduardo Pereira Habkost) > 6. Re: SET failed on device eth0 ; No such device (Jordi Prats) > 7. Hide the host (mathieu rohon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 17 Sep 2007 18:16:49 +0200 > From: "NoisilySilent" > Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt > machine, rdesktop connection. > To: > Message-ID: <000301c7f946$27c02800$cdda0259 at 2M9MV1J> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > > > I used to run Windows XP inside a XEN virtual machine on FC6. > > Everything was perfect. > > To connect to the Windows XP virtual machine, I used to run rdesktop. > > > > Today I installed FC7 from scratch and tried to use my Windows XP virtual > machine and I noticed a very strange behaviour: > > > > All of this stuff runs on a Dell Latitude D620 laptop. > > This laptop offers a touchpad, a trackpoint and of course USB ports on > which > I connect a 3 button wheel mice. > > FC7 is up to date and all packages are at last date version, including > XEN. > > Now when I connect to the Windows XP virtual machine via rdesktop, after a > few minutes the trackpoint and the mouse get weird: when using either the > trackpoint or the mouse moving rightwards, the pointer gets "stuck" on the > left border of the screen whereas I can still use the touchpad and things > don't get messed up. > > However, when using FC7 without XEN, I don't encounter this trouble. > > Have you ever heard of such a problem? > > > > Cheers > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.redhat.com/archives/fedora-xen/attachments/20070917/925bade6/attachment.html > > ------------------------------ > > Message: 2 > Date: Mon, 17 Sep 2007 14:50:02 -0300 > From: Eduardo Habkost > Subject: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: NoisilySilent > Cc: fedora-xen at redhat.com > Message-ID: <20070917175002.GA7163 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset=us-ascii > > On Mon, Sep 17, 2007 at 06:16:49PM +0200, NoisilySilent wrote: > >> >> Now when I connect to the Windows XP virtual machine via rdesktop, after >> a >> few minutes the trackpoint and the mouse get weird: when using either the >> trackpoint or the mouse moving rightwards, the pointer gets "stuck" on >> the >> left border of the screen whereas I can still use the touchpad and things >> don't get messed up. >> >> However, when using FC7 without XEN, I don't encounter this trouble. >> >> Have you ever heard of such a problem? > > I had this weird cursor behaviour last week, on Fedora 7. I was running > a Xen kernel, also (2.6.20-2931, probably; but it could be a different > version). > > If I recall correctly, I didn't have any guest running at the time. It > happened when I started an Eclipse-based application[1]. The cursor > could be moved to the right, but only if I moved the mouse very slowly. > > On my case, it was a desktop machine, so I didn't have a touchpad, > just an USB mouse. > > > However, I didn't manage to reproduce the problem today. Is it easily > reproducible, on your case? > > > [1] It was a IDE from QNX I had just installed for testing. > > -- > Eduardo > > > > ------------------------------ > > Message: 3 > Date: Mon, 17 Sep 2007 20:15:35 +0200 > From: "NoisilySilent" > Subject: RE: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: > Message-ID: <000f01c7f956$bef8f980$cdda0259 at 2M9MV1J> > Content-Type: text/plain; charset="iso-8859-1" > > Hey, this is EXACTLY the same behavior!!! > > Actually I think we are facing the same problem. > I can move it to the right slowly too. > This sounds really similar. > > Unfortunately, in my situation it is reproducible as it happens every time > :( > In fact, nothing runs within the host FC7 except Xorg. > I thought it might have been a window manager problem as bonobo doesn't > start anymore when xen is launched... so I shifted from Gnome to XFCE but > this didn't change anything. > So, apart from Xorg and rdesktop, nothing runs in FC7, everything runs > within the hosted Win XP. > > What bugs me most is that it doesn't appear when launching anything in > particular: I'm simply quietly working in my Windows session and all in a > sudden, the pointer gets stuck in the left. > Well, this is not that dramatically annoying as I can still use the > touchpad, but still it's frustrating: I'm the mouse type, not the touchpad > one ;-) > > > > -----Message d'origine----- > De : Eduardo Habkost [mailto:ehabkost at redhat.com] > Envoy? : lundi 17 septembre 2007 19:50 > ? : NoisilySilent > Cc : fedora-xen at redhat.com > Objet : Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt > machine, rdesktop connection. > > On Mon, Sep 17, 2007 at 06:16:49PM +0200, NoisilySilent wrote: > >> >> Now when I connect to the Windows XP virtual machine via rdesktop, after >> a >> few minutes the trackpoint and the mouse get weird: when using either the >> trackpoint or the mouse moving rightwards, the pointer gets "stuck" on >> the >> left border of the screen whereas I can still use the touchpad and things >> don't get messed up. >> >> However, when using FC7 without XEN, I don't encounter this trouble. >> >> Have you ever heard of such a problem? > > I had this weird cursor behaviour last week, on Fedora 7. I was running > a Xen kernel, also (2.6.20-2931, probably; but it could be a different > version). > > If I recall correctly, I didn't have any guest running at the time. It > happened when I started an Eclipse-based application[1]. The cursor > could be moved to the right, but only if I moved the mouse very slowly. > > On my case, it was a desktop machine, so I didn't have a touchpad, > just an USB mouse. > > > However, I didn't manage to reproduce the problem today. Is it easily > reproducible, on your case? > > > [1] It was a IDE from QNX I had just installed for testing. > > -- > Eduardo > > > > > > > ------------------------------ > > Message: 4 > Date: Mon, 17 Sep 2007 16:01:45 -0300 > From: Eduardo Pereira Habkost > Subject: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: NoisilySilent > Cc: fedora-xen at redhat.com > Message-ID: <20070917190145.GC7163 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset=us-ascii > > On Mon, Sep 17, 2007 at 08:13:23PM +0200, NoisilySilent wrote: >> Hey, this is EXACTLY the same behavior!!! >> >> Actually I think we are facing the same problem. >> I can move it to the right slowly too. >> This sounds really similar. >> >> Unfortunately, in my situation it is reproducible as it happens every >> time >> :( > > I have managed to reproduce it without using the Eclipse-based > application. > > I simply create a new full-virtualization guest (using virt-install) > while moving heavily the mouse cursor. It will eventually get stuck in > the left side of the display, when the vncviewer Window is shown. > > Restarting the X server solves the problem most of times, but I managed > to get the cursor stuck on the left if I move the mouse heavily while > the X server is restarting. > > I have found a workaround, also: > > 'xset m 1/1 1000' (in practice it will disable the mouse acceleration > by setting a huge threshold) make the cursor behave properly. Enabling > mouse acceleration again gets the cursor stuck again. This makes me > believe that this is a Xorg bug, but that may be triggered more easily > when running Xen. > > -- > Eduardo > > > > ------------------------------ > > Message: 5 > Date: Mon, 17 Sep 2007 18:39:02 -0300 > From: Eduardo Pereira Habkost > Subject: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: NoisilySilent > Cc: fedora-xen at redhat.com > Message-ID: <20070917213902.GD7163 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset=us-ascii > > On Mon, Sep 17, 2007 at 04:01:45PM -0300, Eduardo Pereira Habkost wrote: > >> >> I have managed to reproduce it without using the Eclipse-based >> application. >> >> I simply create a new full-virtualization guest (using virt-install) >> while moving heavily the mouse cursor. It will eventually get stuck in >> the left side of the display, when the vncviewer Window is shown. > > I have opened a bug for this: > https://bugzilla.redhat.com/show_bug.cgi?id=294011 > > -- > Eduardo > > > > ------------------------------ > > Message: 6 > Date: Tue, 18 Sep 2007 11:44:44 +0200 > From: Jordi Prats > Subject: Re: [Fedora-xen] SET failed on device eth0 ; No such device > To: Eduardo Habkost > Cc: fedora-xen at redhat.com > Message-ID: <46EF9E0C.6020409 at cesca.es> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > I suspect it's something related to use multiple network devices. I have > this script to setup two bridges, if I disable it all works fine. Anyone? > > Thank you ! > > #!/bin/bash > > #JPC - per crear les dues interficies - 2006 12 22 > > dir=$(dirname "$0") > . "$dir/xen-script-common.sh" > . "$dir/xen-network-common.sh" > > findCommand "$@" > > case "$command" in > start) > vifnum=0 bridge=servei netdev=eth0 > /etc/xen/scripts/network-bridge start > vifnum=1 bridge=dades netdev=eth1 > /etc/xen/scripts/network-bridge start > ;; > > stop) > vifnum=0 bridge=servei netdev=eth0 > /etc/xen/scripts/network-bridge stop > vifnum=1 bridge=dades netdev=eth1 > /etc/xen/scripts/network-bridge stop > ;; > > status) > vifnum=0 bridge=servei netdev=eth0 > /etc/xen/scripts/network-bridge status > vifnum=1 bridge=dades netdev=eth1 > /etc/xen/scripts/network-bridge status > ;; > > *) > echo "Unknown command: $command" >&2 > echo 'Valid commands are: start, stop, status' >&2 > exit 1 > esac > > > Eduardo Habkost wrote: >> On Thu, Sep 13, 2007 at 11:43:04AM +0200, Jordi Prats wrote: >> >>> Hi all, >>> I'm getting this error while trying to bring up my eth1 (is not a >>> wireless card, is a Broadcom NetXtreme II BCM5708 Gigabit Ethernet) >>> >>> Error for wireless request "Set Encode" (8B2A) : >>> SET failed on device eth1 : No such device. >>> SIOCGFFLAGS: No such device >>> Failed to bring up eth1. >>> >> >> By looking at the ifup scripts, it seems that the real problem is >> why iwconfig is reporting "No such device" instead of "no wireless >> extensions". Is eth1 appearing on 'ip link show' and 'ifconfig -a' >> output? >> >> Is it a xen bridge set up by the Xen scripts, or a normal network >> interface? >> >> > > > -- > ...................................................................... > __ > / / Jordi Prats > C E / S / C A Dept. de Sistemes > /_/ Centre de Supercomputaci? de Catalunya > > Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona > T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es > ...................................................................... > > > > ------------------------------ > > Message: 7 > Date: Tue, 18 Sep 2007 17:03:42 +0200 > From: "mathieu rohon" > Subject: [Fedora-xen] Hide the host > To: fedora-xen at redhat.com > Message-ID: > <7675761b0709180803p353f7464l732e7577ac20ecc1 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi all, > > I'd like to use xen with fedora as host, and several OSes as guest (in > fact > 2). > The aim is to use the host as a router for the guests. > So i'd like to make the host as thin as possible, in order to provide most > power to the guest. Do you know a smart way to do so? > > I'd also like to hide the host from the user. When the user log in the > host, a script is launched, and the appropriated guest start in full > screen. > Does anyone has already done something similar? > > thanks for all. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.redhat.com/archives/fedora-xen/attachments/20070918/07fd3c7b/attachment.html > > ------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > End of Fedora-xen Digest, Vol 22, Issue 17 > ****************************************** > From debian at herakles.homelinux.org Wed Sep 19 00:16:02 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Wed, 19 Sep 2007 08:16:02 +0800 Subject: [Fedora-xen] Re: FC7 MOUSE PROBLEMS In-Reply-To: References: <20070918160011.692B7733CA@hormel.redhat.com> Message-ID: <46F06A42.6050605@herakles.homelinux.org> miguel wrote: > Thanks for submitting the bug report. I reported this problem over 4 > months ago, but I never created a bug for it. This problem occurred on > 3 different DELL systems I was working with ( 2 laptops and 1 desktop). > I'll try your workaround to see If it works on my systems. > Thanks How I wish people would prune material irrelevant to their contribution! -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From noisilysilent at nerdshack.com Wed Sep 19 16:10:51 2007 From: noisilysilent at nerdshack.com (NoisilySilent) Date: Wed, 19 Sep 2007 18:10:51 +0200 Subject: [Fedora-xen] Re: FC7 MOUSE PROBLEMS In-Reply-To: Message-ID: <001801c7fad7$a6bc4f20$cdda0259@2M9MV1J> Hi, Actually, it didn't work for me :( Cheers -----Message d'origine----- De?: fedora-xen-bounces at redhat.com [mailto:fedora-xen-bounces at redhat.com] De la part de miguel Envoy??: mardi 18 septembre 2007 20:05 ??: fedora-xen at redhat.com Objet?: [Fedora-xen] Re: FC7 MOUSE PROBLEMS Thanks for submitting the bug report. I reported this problem over 4 months ago, but I never created a bug for it. This problem occurred on 3 different DELL systems I was working with ( 2 laptops and 1 desktop). I'll try your workaround to see If it works on my systems. Thanks ----- Original Message ----- From: To: Sent: Tuesday, September 18, 2007 9:00 AM Subject: Fedora-xen Digest, Vol 22, Issue 17 > Send Fedora-xen mailing list submissions to > fedora-xen at redhat.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/fedora-xen > or, via email, send a message with subject or body 'help' to > fedora-xen-request at redhat.com > > You can reach the person managing the list at > fedora-xen-owner at redhat.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Fedora-xen digest..." > > > Today's Topics: > > 1. Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (NoisilySilent) > 2. Re: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (Eduardo Habkost) > 3. RE: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (NoisilySilent) > 4. Re: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (Eduardo Pereira Habkost) > 5. Re: Mouse problem with FC7 uptodate, Windows XP virt machine, > rdesktop connection. (Eduardo Pereira Habkost) > 6. Re: SET failed on device eth0 ; No such device (Jordi Prats) > 7. Hide the host (mathieu rohon) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 17 Sep 2007 18:16:49 +0200 > From: "NoisilySilent" > Subject: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt > machine, rdesktop connection. > To: > Message-ID: <000301c7f946$27c02800$cdda0259 at 2M9MV1J> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > > > I used to run Windows XP inside a XEN virtual machine on FC6. > > Everything was perfect. > > To connect to the Windows XP virtual machine, I used to run rdesktop. > > > > Today I installed FC7 from scratch and tried to use my Windows XP virtual > machine and I noticed a very strange behaviour: > > > > All of this stuff runs on a Dell Latitude D620 laptop. > > This laptop offers a touchpad, a trackpoint and of course USB ports on > which > I connect a 3 button wheel mice. > > FC7 is up to date and all packages are at last date version, including > XEN. > > Now when I connect to the Windows XP virtual machine via rdesktop, after a > few minutes the trackpoint and the mouse get weird: when using either the > trackpoint or the mouse moving rightwards, the pointer gets "stuck" on the > left border of the screen whereas I can still use the touchpad and things > don't get messed up. > > However, when using FC7 without XEN, I don't encounter this trouble. > > Have you ever heard of such a problem? > > > > Cheers > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.redhat.com/archives/fedora-xen/attachments/20070917/925bade6/att achment.html > > ------------------------------ > > Message: 2 > Date: Mon, 17 Sep 2007 14:50:02 -0300 > From: Eduardo Habkost > Subject: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: NoisilySilent > Cc: fedora-xen at redhat.com > Message-ID: <20070917175002.GA7163 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset=us-ascii > > On Mon, Sep 17, 2007 at 06:16:49PM +0200, NoisilySilent wrote: > >> >> Now when I connect to the Windows XP virtual machine via rdesktop, after >> a >> few minutes the trackpoint and the mouse get weird: when using either the >> trackpoint or the mouse moving rightwards, the pointer gets "stuck" on >> the >> left border of the screen whereas I can still use the touchpad and things >> don't get messed up. >> >> However, when using FC7 without XEN, I don't encounter this trouble. >> >> Have you ever heard of such a problem? > > I had this weird cursor behaviour last week, on Fedora 7. I was running > a Xen kernel, also (2.6.20-2931, probably; but it could be a different > version). > > If I recall correctly, I didn't have any guest running at the time. It > happened when I started an Eclipse-based application[1]. The cursor > could be moved to the right, but only if I moved the mouse very slowly. > > On my case, it was a desktop machine, so I didn't have a touchpad, > just an USB mouse. > > > However, I didn't manage to reproduce the problem today. Is it easily > reproducible, on your case? > > > [1] It was a IDE from QNX I had just installed for testing. > > -- > Eduardo > > > > ------------------------------ > > Message: 3 > Date: Mon, 17 Sep 2007 20:15:35 +0200 > From: "NoisilySilent" > Subject: RE: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: > Message-ID: <000f01c7f956$bef8f980$cdda0259 at 2M9MV1J> > Content-Type: text/plain; charset="iso-8859-1" > > Hey, this is EXACTLY the same behavior!!! > > Actually I think we are facing the same problem. > I can move it to the right slowly too. > This sounds really similar. > > Unfortunately, in my situation it is reproducible as it happens every time > :( > In fact, nothing runs within the host FC7 except Xorg. > I thought it might have been a window manager problem as bonobo doesn't > start anymore when xen is launched... so I shifted from Gnome to XFCE but > this didn't change anything. > So, apart from Xorg and rdesktop, nothing runs in FC7, everything runs > within the hosted Win XP. > > What bugs me most is that it doesn't appear when launching anything in > particular: I'm simply quietly working in my Windows session and all in a > sudden, the pointer gets stuck in the left. > Well, this is not that dramatically annoying as I can still use the > touchpad, but still it's frustrating: I'm the mouse type, not the touchpad > one ;-) > > > > -----Message d'origine----- > De : Eduardo Habkost [mailto:ehabkost at redhat.com] > Envoy? : lundi 17 septembre 2007 19:50 > ? : NoisilySilent > Cc : fedora-xen at redhat.com > Objet : Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP virt > machine, rdesktop connection. > > On Mon, Sep 17, 2007 at 06:16:49PM +0200, NoisilySilent wrote: > >> >> Now when I connect to the Windows XP virtual machine via rdesktop, after >> a >> few minutes the trackpoint and the mouse get weird: when using either the >> trackpoint or the mouse moving rightwards, the pointer gets "stuck" on >> the >> left border of the screen whereas I can still use the touchpad and things >> don't get messed up. >> >> However, when using FC7 without XEN, I don't encounter this trouble. >> >> Have you ever heard of such a problem? > > I had this weird cursor behaviour last week, on Fedora 7. I was running > a Xen kernel, also (2.6.20-2931, probably; but it could be a different > version). > > If I recall correctly, I didn't have any guest running at the time. It > happened when I started an Eclipse-based application[1]. The cursor > could be moved to the right, but only if I moved the mouse very slowly. > > On my case, it was a desktop machine, so I didn't have a touchpad, > just an USB mouse. > > > However, I didn't manage to reproduce the problem today. Is it easily > reproducible, on your case? > > > [1] It was a IDE from QNX I had just installed for testing. > > -- > Eduardo > > > > > > > ------------------------------ > > Message: 4 > Date: Mon, 17 Sep 2007 16:01:45 -0300 > From: Eduardo Pereira Habkost > Subject: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: NoisilySilent > Cc: fedora-xen at redhat.com > Message-ID: <20070917190145.GC7163 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset=us-ascii > > On Mon, Sep 17, 2007 at 08:13:23PM +0200, NoisilySilent wrote: >> Hey, this is EXACTLY the same behavior!!! >> >> Actually I think we are facing the same problem. >> I can move it to the right slowly too. >> This sounds really similar. >> >> Unfortunately, in my situation it is reproducible as it happens every >> time >> :( > > I have managed to reproduce it without using the Eclipse-based > application. > > I simply create a new full-virtualization guest (using virt-install) > while moving heavily the mouse cursor. It will eventually get stuck in > the left side of the display, when the vncviewer Window is shown. > > Restarting the X server solves the problem most of times, but I managed > to get the cursor stuck on the left if I move the mouse heavily while > the X server is restarting. > > I have found a workaround, also: > > 'xset m 1/1 1000' (in practice it will disable the mouse acceleration > by setting a huge threshold) make the cursor behave properly. Enabling > mouse acceleration again gets the cursor stuck again. This makes me > believe that this is a Xorg bug, but that may be triggered more easily > when running Xen. > > -- > Eduardo > > > > ------------------------------ > > Message: 5 > Date: Mon, 17 Sep 2007 18:39:02 -0300 > From: Eduardo Pereira Habkost > Subject: Re: [Fedora-xen] Mouse problem with FC7 uptodate, Windows XP > virt machine, rdesktop connection. > To: NoisilySilent > Cc: fedora-xen at redhat.com > Message-ID: <20070917213902.GD7163 at blackpad.ctb.virtua.com.br> > Content-Type: text/plain; charset=us-ascii > > On Mon, Sep 17, 2007 at 04:01:45PM -0300, Eduardo Pereira Habkost wrote: > >> >> I have managed to reproduce it without using the Eclipse-based >> application. >> >> I simply create a new full-virtualization guest (using virt-install) >> while moving heavily the mouse cursor. It will eventually get stuck in >> the left side of the display, when the vncviewer Window is shown. > > I have opened a bug for this: > https://bugzilla.redhat.com/show_bug.cgi?id=294011 > > -- > Eduardo > > > > ------------------------------ > > Message: 6 > Date: Tue, 18 Sep 2007 11:44:44 +0200 > From: Jordi Prats > Subject: Re: [Fedora-xen] SET failed on device eth0 ; No such device > To: Eduardo Habkost > Cc: fedora-xen at redhat.com > Message-ID: <46EF9E0C.6020409 at cesca.es> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi, > I suspect it's something related to use multiple network devices. I have > this script to setup two bridges, if I disable it all works fine. Anyone? > > Thank you ! > > #!/bin/bash > > #JPC - per crear les dues interficies - 2006 12 22 > > dir=$(dirname "$0") > . "$dir/xen-script-common.sh" > . "$dir/xen-network-common.sh" > > findCommand "$@" > > case "$command" in > start) > vifnum=0 bridge=servei netdev=eth0 > /etc/xen/scripts/network-bridge start > vifnum=1 bridge=dades netdev=eth1 > /etc/xen/scripts/network-bridge start > ;; > > stop) > vifnum=0 bridge=servei netdev=eth0 > /etc/xen/scripts/network-bridge stop > vifnum=1 bridge=dades netdev=eth1 > /etc/xen/scripts/network-bridge stop > ;; > > status) > vifnum=0 bridge=servei netdev=eth0 > /etc/xen/scripts/network-bridge status > vifnum=1 bridge=dades netdev=eth1 > /etc/xen/scripts/network-bridge status > ;; > > *) > echo "Unknown command: $command" >&2 > echo 'Valid commands are: start, stop, status' >&2 > exit 1 > esac > > > Eduardo Habkost wrote: >> On Thu, Sep 13, 2007 at 11:43:04AM +0200, Jordi Prats wrote: >> >>> Hi all, >>> I'm getting this error while trying to bring up my eth1 (is not a >>> wireless card, is a Broadcom NetXtreme II BCM5708 Gigabit Ethernet) >>> >>> Error for wireless request "Set Encode" (8B2A) : >>> SET failed on device eth1 : No such device. >>> SIOCGFFLAGS: No such device >>> Failed to bring up eth1. >>> >> >> By looking at the ifup scripts, it seems that the real problem is >> why iwconfig is reporting "No such device" instead of "no wireless >> extensions". Is eth1 appearing on 'ip link show' and 'ifconfig -a' >> output? >> >> Is it a xen bridge set up by the Xen scripts, or a normal network >> interface? >> >> > > > -- > ...................................................................... > __ > / / Jordi Prats > C E / S / C A Dept. de Sistemes > /_/ Centre de Supercomputaci? de Catalunya > > Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona > T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es > ...................................................................... > > > > ------------------------------ > > Message: 7 > Date: Tue, 18 Sep 2007 17:03:42 +0200 > From: "mathieu rohon" > Subject: [Fedora-xen] Hide the host > To: fedora-xen at redhat.com > Message-ID: > <7675761b0709180803p353f7464l732e7577ac20ecc1 at mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi all, > > I'd like to use xen with fedora as host, and several OSes as guest (in > fact > 2). > The aim is to use the host as a router for the guests. > So i'd like to make the host as thin as possible, in order to provide most > power to the guest. Do you know a smart way to do so? > > I'd also like to hide the host from the user. When the user log in the > host, a script is launched, and the appropriated guest start in full > screen. > Does anyone has already done something similar? > > thanks for all. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > https://www.redhat.com/archives/fedora-xen/attachments/20070918/07fd3c7b/att achment.html > > ------------------------------ > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen > > > End of Fedora-xen Digest, Vol 22, Issue 17 > ****************************************** > -- Fedora-xen mailing list Fedora-xen at redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen From jonas.weismueller at comsoft.de Wed Sep 19 16:36:32 2007 From: jonas.weismueller at comsoft.de (Weismueller, Jonas) Date: Wed, 19 Sep 2007 18:36:32 +0200 Subject: [Fedora-xen] Re: FC7 MOUSE PROBLEMS In-Reply-To: <001801c7fad7$a6bc4f20$cdda0259@2M9MV1J> References: <001801c7fad7$a6bc4f20$cdda0259@2M9MV1J> Message-ID: <46F15010.8060707@comsoft.de> NoisilySilent wrote: > Hi, > > Actually, it didn't work for me :( > Play a little bit with xset m x/y . It worked here for me, too. xset m 0/4 always works here. Cheers 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 jprats at cesca.es Thu Sep 20 08:17:25 2007 From: jprats at cesca.es (Jordi Prats) Date: Thu, 20 Sep 2007 10:17:25 +0200 Subject: [Fedora-xen] Bridge network configuration Message-ID: <46F22C95.40008@cesca.es> Hi all, I've installed a Fedora 7 with Xen. I found that every physical interface that I configure to have a bridge attached using the folowing command disappears. vifnum=0 bridge=servei netdev=eth0 /etc/xen/scripts/network-bridge start If it disapears I can'nt set an IP on dom0. Anyone has encountered this issue? [root at inf20 xen]# ifconfig dades Link encap:Ethernet HWaddr 00:1B:78:30:FC:08 inet addr:192.168.22.20 Bcast:0.0.0.0 Mask:255.255.255.0 inet6 addr: fe80::21b:78ff:fe30:fc08/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5521725 errors:0 dropped:0 overruns:0 frame:0 TX packets:4195054 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:180351774 (171.9 MiB) TX bytes:441062239 (420.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:975416 errors:0 dropped:0 overruns:0 frame:0 TX packets:975416 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2203819288 (2.0 GiB) TX bytes:2203819288 (2.0 GiB) peth0 Link encap:Ethernet HWaddr 00:1B:78:30:FC:1C inet6 addr: fe80::21b:78ff:fe30:fc1c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:244707 errors:0 dropped:0 overruns:0 frame:0 TX packets:16 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16583280 (15.8 MiB) TX bytes:4272 (4.1 KiB) Interrupt:18 Memory:f8000000-f8012100 peth1 Link encap:Ethernet HWaddr 00:1B:78:30:FC:08 inet6 addr: fe80::21b:78ff:fe30:fc08/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5612897 errors:0 dropped:0 overruns:0 frame:0 TX packets:7879973 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:286163027 (272.9 MiB) TX bytes:715786780 (682.6 MiB) Interrupt:19 Memory:fa000000-fa012100 virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:41 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:7855 (7.6 KiB) -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... From fedora.lists at burns.me.uk Thu Sep 20 10:39:21 2007 From: fedora.lists at burns.me.uk (Andy Burns) Date: Thu, 20 Sep 2007 11:39:21 +0100 Subject: [Fedora-xen] Virt-install with no-graphics In-Reply-To: <4d8475a60709131306n7a5ef48fn2f5bb7488a94539d@mail.gmail.com> References: <4d8475a60709131306n7a5ef48fn2f5bb7488a94539d@mail.gmail.com> Message-ID: On 13/09/2007, Jackley Cesar wrote: > I try to do a guest OS install remotely using virt-install but the > installation process hangs with the following error: > > "Write protecting the kernel read-only data: 938k" That's quite a common issue at that point, in all probability it hasn't actually hung, it's simply that you are not connected to the proper console that the guest is writing to, if you use --extra-args="console=xvc0" with virt-install, everything should be fine. From dlbewley at lib.ucdavis.edu Thu Sep 20 20:54:05 2007 From: dlbewley at lib.ucdavis.edu (Dale Bewley) Date: Thu, 20 Sep 2007 13:54:05 -0700 Subject: [Fedora-xen] Bridge network configuration In-Reply-To: <46F22C95.40008@cesca.es> References: <46F22C95.40008@cesca.es> Message-ID: <1190321645.26599.4.camel@tofu.lib.ucdavis.edu> On Thu, 2007-09-20 at 10:17 +0200, Jordi Prats wrote: > Hi all, > I've installed a Fedora 7 with Xen. I found that every physical > interface that I configure to have a bridge attached using the folowing > command disappears. > > vifnum=0 bridge=servei netdev=eth0 /etc/xen/scripts/network-bridge start > > If it disapears I can'nt set an IP on dom0. Anyone has encountered this > issue? I recommend you place configs in /etc/sysconfig/network-scripts to configure your bridges. https://www.redhat.com/archives/fedora-xen/2007-August/msg00040.html -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 From jprats at cesca.es Fri Sep 21 07:07:43 2007 From: jprats at cesca.es (Jordi Prats) Date: Fri, 21 Sep 2007 09:07:43 +0200 Subject: [Fedora-xen] Bridge network configuration In-Reply-To: <1190321645.26599.4.camel@tofu.lib.ucdavis.edu> References: <46F22C95.40008@cesca.es> <1190321645.26599.4.camel@tofu.lib.ucdavis.edu> Message-ID: <46F36DBF.5050408@cesca.es> Thank you! It's just what I was looking for! Jordi Dale Bewley wrote: > On Thu, 2007-09-20 at 10:17 +0200, Jordi Prats wrote: > >> Hi all, >> I've installed a Fedora 7 with Xen. I found that every physical >> interface that I configure to have a bridge attached using the folowing >> command disappears. >> >> vifnum=0 bridge=servei netdev=eth0 /etc/xen/scripts/network-bridge start >> >> If it disapears I can'nt set an IP on dom0. Anyone has encountered this >> issue? >> > > I recommend you place configs in /etc/sysconfig/network-scripts to > configure your bridges. > https://www.redhat.com/archives/fedora-xen/2007-August/msg00040.html > > -- ...................................................................... __ / / Jordi Prats C E / S / C A Dept. de Sistemes /_/ Centre de Supercomputaci? de Catalunya Gran Capit?, 2-4 (Edifici Nexus) ? 08034 Barcelona T. 93 205 6464 ? F. 93 205 6979 ? jprats at cesca.es ...................................................................... From jlagrue at gmail.com Sat Sep 22 00:03:28 2007 From: jlagrue at gmail.com (John Lagrue) Date: Sat, 22 Sep 2007 01:03:28 +0100 Subject: [Fedora-xen] Creating and installing Centos under virt-manager Message-ID: All working a treat: created the guest (fully virtualised - I have no time for Xen), setup disk space in a 6Gb file, gave it a name, and pointed the installation source to be the first of 6 .iso files for Centos 5 installation ......then it asks for the second CDRom! How the blazes is one supposed to tell it where to get the file? I'm completely stuck! I thought this was supposed to work with .iso files and I wouldn't have to burn 6 CDs. But what happens now? JDL From debian at herakles.homelinux.org Sat Sep 22 00:09:22 2007 From: debian at herakles.homelinux.org (John Summerfield) Date: Sat, 22 Sep 2007 08:09:22 +0800 Subject: [Fedora-xen] Creating and installing Centos under virt-manager In-Reply-To: References: Message-ID: <46F45D32.4060106@herakles.homelinux.org> John Lagrue wrote: > All working a treat: created the guest (fully virtualised - I have no > time for Xen), setup disk space in a 6Gb file, gave it a name, and > pointed the installation source to be the first of 6 .iso files for > Centos 5 installation > > ......then it asks for the second CDRom! > > How the blazes is one supposed to tell it where to get the file? > > I'm completely stuck! I thought this was supposed to work with .iso > files and I wouldn't have to burn 6 CDs. But what happens now? > Last I read, the ability to change CD was "planned for the future." You're better off using the DVD image. If you can find a .jigdo file and template (I think CentOS does it), then you don't have to download much of CentOS 5 again. Or do a network install: nfs should work really well over a virtual LAN. -- Cheers John -- spambait 1aaaaaaa at coco.merseine.nu Z1aaaaaaa at coco.merseine.nu Please do not reply off-list From mnielsen at redhat.com Sat Sep 22 02:36:16 2007 From: mnielsen at redhat.com (Mark Nielsen) Date: Fri, 21 Sep 2007 22:36:16 -0400 Subject: [Fedora-xen] Creating and installing Centos under virt-manager In-Reply-To: <46F45D32.4060106@herakles.homelinux.org> References: <46F45D32.4060106@herakles.homelinux.org> Message-ID: <46F47FA0.3040503@redhat.com> or create a DVD .iso file from the 6 CDs. I have instructions on my website, www.certifried.com John Summerfield wrote: > John Lagrue wrote: >> All working a treat: created the guest (fully virtualised - I have no >> time for Xen), setup disk space in a 6Gb file, gave it a name, and >> pointed the installation source to be the first of 6 .iso files for >> Centos 5 installation >> >> ......then it asks for the second CDRom! >> >> How the blazes is one supposed to tell it where to get the file? >> >> I'm completely stuck! I thought this was supposed to work with .iso >> files and I wouldn't have to burn 6 CDs. But what happens now? >> > Last I read, the ability to change CD was "planned for the future." > > You're better off using the DVD image. If you can find a .jigdo file > and template (I think CentOS does it), then you don't have to download > much of CentOS 5 again. > > Or do a network install: nfs should work really well over a virtual LAN. > > > From acathrow at redhat.com Sat Sep 22 03:04:48 2007 From: acathrow at redhat.com (Andrew Cathrow) Date: Fri, 21 Sep 2007 23:04:48 -0400 Subject: [Fedora-xen] Creating and installing Centos under virt-manager In-Reply-To: <46F47FA0.3040503@redhat.com> References: <46F45D32.4060106@herakles.homelinux.org> <46F47FA0.3040503@redhat.com> Message-ID: <1190430288.16345.1.camel@aic-desktop.cathrow.org> A network install is the best option but you can always add and remove devices using virsh Have a look in the man page for virsh at attach-disk and detach-disk On Fri, 2007-09-21 at 22:36 -0400, Mark Nielsen wrote: > or create a DVD .iso file from the 6 CDs. I have instructions on my > website, www.certifried.com > > John Summerfield wrote: > > John Lagrue wrote: > >> All working a treat: created the guest (fully virtualised - I have no > >> time for Xen), setup disk space in a 6Gb file, gave it a name, and > >> pointed the installation source to be the first of 6 .iso files for > >> Centos 5 installation > >> > >> ......then it asks for the second CDRom! > >> > >> How the blazes is one supposed to tell it where to get the file? > >> > >> I'm completely stuck! I thought this was supposed to work with .iso > >> files and I wouldn't have to burn 6 CDs. But what happens now? > >> > > Last I read, the ability to change CD was "planned for the future." > > > > You're better off using the DVD image. If you can find a .jigdo file > > and template (I think CentOS does it), then you don't have to download > > much of CentOS 5 again. > > > > Or do a network install: nfs should work really well over a virtual LAN. > > > > > > > > -- > Fedora-xen mailing list > Fedora-xen at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen Andrew Cathrow Red Hat, Inc. (678) 733 0452 - Mobile (404) 437 6178 - Home Office acathrow at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hbrock at redhat.com Mon Sep 24 13:39:18 2007 From: hbrock at redhat.com (Hugh Brock) Date: Mon, 24 Sep 2007 09:39:18 -0400 Subject: [Fedora-xen] Creating and installing Centos under virt-manager In-Reply-To: <1190430288.16345.1.camel@aic-desktop.cathrow.org> References: <46F45D32.4060106@herakles.homelinux.org> <46F47FA0.3040503@redhat.com> <1190430288.16345.1.camel@aic-desktop.cathrow.org> Message-ID: <46F7BE06.2000006@redhat.com> Andrew Cathrow wrote: > A network install is the best option but you can always add and remove > devices using virsh > > Have a look in the man page for virsh at attach-disk and detach-disk > > > > On Fri, 2007-09-21 at 22:36 -0400, Mark Nielsen wrote: >> or create a DVD .iso file from the 6 CDs. I have instructions on my >> website, www.certifried.com >> >> John Summerfield wrote: >> > John Lagrue wrote: >> >> All working a treat: created the guest (fully virtualised - I have no >> >> time for Xen), setup disk space in a 6Gb file, gave it a name, and >> >> pointed the installation source to be the first of 6 .iso files for >> >> Centos 5 installation >> >> >> >> ......then it asks for the second CDRom! >> >> >> >> How the blazes is one supposed to tell it where to get the file? >> >> >> >> I'm completely stuck! I thought this was supposed to work with .iso >> >> files and I wouldn't have to burn 6 CDs. But what happens now? >> >> >> > Last I read, the ability to change CD was "planned for the future." >> > >> > You're better off using the DVD image. If you can find a .jigdo file >> > and template (I think CentOS does it), then you don't have to download >> > much of CentOS 5 again. >> > >> > Or do a network install: nfs should work really well over a virtual LAN. If you don't mind the bleeding edge, the latest release of libvirt supports connecting and disconnecting cdrom backing devices (or isos) from a fullvirt xen guest. The xen guest must have a cdrom device with no "source" line in its xml definition (unfortunately we don't support this with KVM yet although we plan to soon). If you call "virsh attach-device " where "device.xml" is an xml file with a complete device definition like so: then libvirt will attach your host cdrom device to the guest's cdrom device. Then to disconnect the cdrom, call "virsh attach-device " where "device.xml" is an xml file like the above, but with no "source" element. The upcoming release of virt-manager (should be out today if it isn't already) has UI that supports this capability. Again, to be clear, this only works for fully virtualized Xen guests at the moment; we're working on adding it to kvm but have no idea when that will be available. Hope this helps somewhat. Take care, --Hugh -- Red Hat Virtualization Group http://redhat.com/virtualization Hugh Brock | virt-manager http://virt-manager.org hbrock at redhat.com | virtualization library http://libvirt.org From Tameika.Reed at nortelgov.com Mon Sep 24 14:15:07 2007 From: Tameika.Reed at nortelgov.com (Reed, Tameika N) Date: Mon, 24 Sep 2007 10:15:07 -0400 Subject: [Fedora-xen] Changing CDS Message-ID: Here is how I did when doing fully virtualized 1. First find out where the iso is mounted : a. Xm block-list domain-name This should return something similar to following: Vdev BE Handle state evt-ch ring-ref BE-path 768 0 0 1 -1 -2 /local/domain/0/backend/vbd/8/768 5632 0 0 1 -1 -1 /local/domain/0/backend/vbd/8/5632 2. Now after finding that out do the following: Xenstore-read /local/domain/0/backend/vbd/8/5632/params This should return: /root/rhel-5-server-i386-disc1.iso or wherever your isos are stored 3. Now can do the following to change which iso should be read: Xenstore-read /local/domain/0/backend/vbd/8/5632/params /root/rhel-5-server-i386-disc2.iso -------------- next part -------------- An HTML attachment was scrubbed... URL: From jsolan at knouse.com Tue Sep 25 20:17:24 2007 From: jsolan at knouse.com (Jason Solan) Date: Tue, 25 Sep 2007 16:17:24 -0400 Subject: [Fedora-xen] Fedora 7 kernels Message-ID: <1190751444.2896.16.camel@localhost.localdomain> I've had a lot of problems with Fedora 7 and XEN and I've read some messages on this mailing list indicating the F7 kernel is more or less broke with xen. By problems I mean that 32 bit guests on 64 bit dom0 does not work at all for me. Neither paravirtualized (as was a main feature of xen 3.1) or fully virtualized. Combinations I've tried: F7 x86_64 dom0 -> F7 x86 domU PV F7 x86_64 dom0 -> F7 x86 domU HVM RHEL 5 x86_64 dom0 -> F7 x86 domU HVM RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU PV RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU HVM RHEL 5 x86 dom0 -> F7 x86 domU PV -- Only one that works (32 on 32 PV) I had read a while ago (June?) that a kernel update would be coming soon to fix the 32 on 64 PV issue, however I've ran in several new kernels and none seem to fix the issue. https://www.redhat.com/archives/fedora-xen/2007-June/msg00031.html I've also repeatedly tried to run a 32 bit HVM fedora 7 guest on 64 bit machines and had that fail similar to this: http://www.redhat.com/archives/fedora-xen/2007-June/msg00094.html Is there any more work planned for Fedora 7 and xen, or should I just wait until F8? Or am I just doing something wrong and the problems I'm having should be working on the current builds? IMPORTANT: This transmission is sent on behalf of Knouse Foods? for business purposes. It is for the intended recipient only. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you may not disclose, copy or distribute this transmission or take any action in reliance on it. If you received this transmission in error, please notify us immediately by replying to this Email message, and please dispose of and delete this transmission. Thank you. From jlagrue at gmail.com Tue Sep 25 20:23:02 2007 From: jlagrue at gmail.com (John Lagrue) Date: Tue, 25 Sep 2007 21:23:02 +0100 Subject: [Fedora-xen] Qemu goes bonkers - again! Message-ID: I had an installation of WinXP that took a long time to install but finally had running fairly well runing from a commandline call to qemu-kvm (though I never have got the hang of how the network the damned thing!) But then, after a recent update, qemu-kvm would crash every time I tried to run it. OK I thought, there's something new, so I tried to create a new VM. I still can't get anything useful to build with WinXP from virt-manager, but did manage to get it to instal by running qemu-kvm from the command line again. And it works fine. Right up to the moment I install XP SP 2. After that, all I get is this: --------------------------------------------------------------- # qemu-kvm -localtime -no-acpi -m 512 CC3_1 Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal error, but for better emulation accuracy either use a 2.6 host Linux kernel or type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. unhandled vm exit: 0x3f60101 rax 00000000000000b5 rbx 00000000000000b5 rcx 0000000000000000 rdx 000000008053f118 rsi 0000000080551920 rdi 0000000000000000 rsp 00000000804d7000 rbp 000000008053f0a0 r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 0000000000000000 r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 0000000000000000 rip 000000008053f620 rflags 00000002 cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0) ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0) tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0) ldt 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) gdt 8003f000/3ff idt 8003f400/7ff cr0 8001003d cr2 0 cr3 a4a000 cr4 20 cr8 0 efer 0 Aborted --------------------------------------------------------------- I've reinstalled this three times, and it happens every time. Does this mean anything to anyone? JDL From David.Fischer at dhl.com Tue Sep 25 22:01:46 2007 From: David.Fischer at dhl.com (David Fischer (DHL US)) Date: Tue, 25 Sep 2007 15:01:46 -0700 Subject: [Fedora-xen] Question: resize graphic console Message-ID: <1190757706.25779.1.camel@localhost.localdomain> All, The graphics console runs in 800x600 is there an option to change this? thanks -- David R. Fischer Sr Systems Support Engineer DHL Information Services (Americas) 8701 East Hartford Drive Scottsdale, Arizona 85255 USA Contact: +1.480.375.6428 Cell: +1.480.226.3779 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 2649 bytes Desc: not available URL: From david.fischer at dhl.com Tue Sep 25 22:06:45 2007 From: david.fischer at dhl.com (David R. Fischer) Date: Tue, 25 Sep 2007 15:06:45 -0700 Subject: [Fedora-xen] Question: resize graphic console Message-ID: <1190758005.25779.4.camel@localhost.localdomain> All, The graphics console runs in 800x600 is there an option to change this? It is kinda hard to understand how the default of 800x600 is picked up. Is there a configuration file that sets the xen-vncfb setup? thanks David From berrange at redhat.com Tue Sep 25 22:08:46 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Tue, 25 Sep 2007 23:08:46 +0100 Subject: [Fedora-xen] Question: resize graphic console In-Reply-To: <1190757706.25779.1.camel@localhost.localdomain> References: <1190757706.25779.1.camel@localhost.localdomain> Message-ID: <20070925220846.GK17213@redhat.com> On Tue, Sep 25, 2007 at 03:01:46PM -0700, David Fischer (DHL US) wrote: > All, > > The graphics console runs in 800x600 is there an option to change this? Not for paravirt guests, no. Only fullyvirt guests can be resized, and even those are limited to 1024x768 currently. Newer QEMU will be able to provide a VMWare VGA adapter to fully guests which will allow higher resolutions but that's not available yet IIRC. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Thu Sep 27 04:22:08 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 27 Sep 2007 05:22:08 +0100 Subject: [Fedora-xen] Fedora 7 kernels In-Reply-To: <1190751444.2896.16.camel@localhost.localdomain> References: <1190751444.2896.16.camel@localhost.localdomain> Message-ID: <20070927042208.GA16511@redhat.com> On Tue, Sep 25, 2007 at 04:17:24PM -0400, Jason Solan wrote: > I've had a lot of problems with Fedora 7 and XEN and I've read some > messages on this mailing list indicating the F7 kernel is more or less > broke with xen. > By problems I mean that 32 bit guests on 64 bit dom0 does not work at > all for me. Neither paravirtualized (as was a main feature of xen 3.1) > or fully virtualized. The release notes associated with Xen 3.1 turned out to be not quite accurate on the subject of 32-on-64 & we didn't realize this when we made corresponding release notes for Fedora 7. Xen 3.1 lets you run a 32-bit DomU kernel on a 64-bit hypervisor + Dom0 *ONLY IF* the DomU kernel was also based on Xen 3.1. ie, a 32-bit DomU kernel based on older Xen 3.0.* release would will not work on Xen 3.1 Unfortunately all the Fedora kernels for FC6 are 3.0.3 and F7 GA was based on Xen 3.0.4, so neither will work on a Xen 3.1 hypervisor + Dom0. In the current Xen-unstable upstream (which will become Xen 3.2) there is now back-compat support for running older DomU kernels. In the most recent update of Xen in F-7 updates-testing we have included a handful of backports which at least let us boot a 32-bit FC6 and F7 domU installer kernel on a 64-bit F7 / F8 host. There are ongoing fixes in upstream Xen for various stability issues when running 32-on-64 though, so it is not perfect. You may be lucky with our latest updates and have it work, but equally you may not be lucky. We're tracking upstream & will pull in fixes when available. > Combinations I've tried: > F7 x86_64 dom0 -> F7 x86 domU PV Works in basic testing. Has stability problems. > F7 x86_64 dom0 -> F7 x86 domU HVM F7 HVM has been broken since GA for reasons unrelated to the 32-on-64 stuff. A last minute clock-source & bootloader change screwed things up. Yesterday we pushed newer kernel-xen and xen RPMs to updates-testing which hopefully make this work. > RHEL 5 x86_64 dom0 -> F7 x86 domU HVM Not going to work - missing the fix I mention above. > RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU PV Works for me, at least to boot the installer. There are sometimes some stability issues though, since Xen 3.1 was far from complete in its 32-on-64 support. > RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU HVM Not going to work - missing the fix I mention above. > RHEL 5 x86 dom0 -> F7 x86 domU PV -- Only one that works (32 on 32 PV) Matched 32-on-32 and 64-on-64 kernels have always worked. > I had read a while ago (June?) that a kernel update would be coming soon > to fix the 32 on 64 PV issue, however I've ran in several new kernels > and none seem to fix the issue. > https://www.redhat.com/archives/fedora-xen/2007-June/msg00031.html The fix required both kernel-xen & xen updates which are finally available in updates-testing. > I've also repeatedly tried to run a 32 bit HVM fedora 7 guest on 64 bit > machines and had that fail similar to this: F7 HVM guests have known issues, also hopefully now fixed. > http://www.redhat.com/archives/fedora-xen/2007-June/msg00094.html > > Is there any more work planned for Fedora 7 and xen, or should I just > wait until F8? Or am I just doing something wrong and the problems I'm > having should be working on the current builds? Fedora 7 will continue to have updates until its end-of-life. The issue is that even in upstream Xen 32-on-64 doesn't have the same level of stability as 32-on-32, or 64-on-64. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Thu Sep 27 04:25:28 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 27 Sep 2007 05:25:28 +0100 Subject: [Fedora-xen] Creating and installing Centos under virt-manager In-Reply-To: <46F45D32.4060106@herakles.homelinux.org> References: <46F45D32.4060106@herakles.homelinux.org> Message-ID: <20070927042528.GB16511@redhat.com> On Sat, Sep 22, 2007 at 08:09:22AM +0800, John Summerfield wrote: > John Lagrue wrote: > >All working a treat: created the guest (fully virtualised - I have no > >time for Xen), setup disk space in a 6Gb file, gave it a name, and > >pointed the installation source to be the first of 6 .iso files for > >Centos 5 installation > > > >......then it asks for the second CDRom! > > > >How the blazes is one supposed to tell it where to get the file? > > > >I'm completely stuck! I thought this was supposed to work with .iso > >files and I wouldn't have to burn 6 CDs. But what happens now? > > > Last I read, the ability to change CD was "planned for the future." Latest upstream libvirt & virt-manager now has support for this on Xen. The support for KVM will be coming soon too. I hope to get it into Fedora 8, and then subsquently it'll be in a Fedora 7 update. In the meantime our recommendation is to use the 'images/boot.iso' from the install tree, and then point it at an NFS/HTTP/FTP location for the main package install stage. > Or do a network install: nfs should work really well over a virtual LAN. Yep, NFS or HTTP will work. NFS is slighty better if you have limited memory in the guest, since it can execute-in-place, while HTTP needs to use 60 MB or so of RAM just to hold the installer download. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| From berrange at redhat.com Thu Sep 27 04:26:16 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 27 Sep 2007 05:26:16 +0100 Subject: [Fedora-xen] Qemu goes bonkers - again! In-Reply-To: References: Message-ID: <20070927042616.GC16511@redhat.com> On Tue, Sep 25, 2007 at 09:23:02PM +0100, John Lagrue wrote: > I had an installation of WinXP that took a long time to install but > finally had running fairly well runing from a commandline call to > qemu-kvm (though I never have got the hang of how the network the > damned thing!) > > But then, after a recent update, qemu-kvm would crash every time I > tried to run it. OK I thought, there's something new, so I tried to > create a new VM. > > I still can't get anything useful to build with WinXP from > virt-manager, but did manage to get it to instal by running qemu-kvm > from the command line again. And it works fine. Right up to the moment > I install XP SP 2. > > After that, all I get is this: > > --------------------------------------------------------------- > # qemu-kvm -localtime -no-acpi -m 512 CC3_1 > Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal > error, but for better emulation accuracy either use a 2.6 host Linux kernel or > type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root. > unhandled vm exit: 0x3f60101 > rax 00000000000000b5 rbx 00000000000000b5 rcx 0000000000000000 rdx > 000000008053f118 > rsi 0000000080551920 rdi 0000000000000000 rsp 00000000804d7000 rbp > 000000008053f0a0 > r8 0000000000000000 r9 0000000000000000 r10 0000000000000000 r11 > 0000000000000000 > r12 0000000000000000 r13 0000000000000000 r14 0000000000000000 r15 > 0000000000000000 > rip 000000008053f620 rflags 00000002 > cs 0008 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type b l 0 g 0 avl 0) > ds 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) > es 0023 (00000000/ffffffff p 1 dpl 3 db 1 s 1 type 3 l 0 g 1 avl 0) > ss 0010 (00000000/ffffffff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) > fs 0030 (ffdff000/00001fff p 1 dpl 0 db 1 s 1 type 3 l 0 g 1 avl 0) > gs 0000 (00000000/0000ffff p 1 dpl 0 db 0 s 1 type 3 l 0 g 0 avl 0) > tr 0028 (80042000/000020ab p 1 dpl 0 db 0 s 0 type 9 l 0 g 0 avl 0) > ldt 0000 (00000000/0000ffff p 0 dpl 0 db 0 s 0 type 0 l 0 g 0 avl 0) > gdt 8003f000/3ff > idt 8003f400/7ff > cr0 8001003d cr2 0 cr3 a4a000 cr4 20 cr8 0 efer 0 > Aborted > --------------------------------------------------------------- > > I've reinstalled this three times, and it happens every time. Does > this mean anything to anyone? Not a lot, but please file a bugzilla ticket against KVM since various knowledgable people monitor the BZ tickets. 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 deepc2005 at hotmail.com Thu Sep 27 20:40:34 2007 From: deepc2005 at hotmail.com (Maximilian Freisinger) Date: Thu, 27 Sep 2007 16:40:34 -0400 Subject: [Fedora-xen] Using virt Message-ID: Hello, i have some question about virt-manager 1. Where is the script virt-manager uses for installation, and is it possible to modify? 2. Can i set kernelparameter for installation (i would need xfs)? 3. Is it possible to define single lvs as partitions for a new system? THX DC _________________________________________________________________ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE From juerg_ritter at bluewin.ch Thu Sep 27 21:11:24 2007 From: juerg_ritter at bluewin.ch (Juerg Ritter) Date: Thu, 27 Sep 2007 23:11:24 +0200 Subject: [Fedora-xen] ID = VNC Port Message-ID: <46FC1C7C.4030707@bluewin.ch> Hello there! I am wondering if there is a possibility to define that the VNC Port of a virtual machine is always equal to the ID of the machine. That would be very interesting for scripting, and easy to find out on which VNC Display i have to search for a particular machine. Does anybody has an idea? I would like to invoke something like: vncviewer : to connect to this virtual machine. thanks and regards, Juerg From berrange at redhat.com Thu Sep 27 21:21:08 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Thu, 27 Sep 2007 22:21:08 +0100 Subject: [Fedora-xen] ID = VNC Port In-Reply-To: <46FC1C7C.4030707@bluewin.ch> References: <46FC1C7C.4030707@bluewin.ch> Message-ID: <20070927212107.GS17433@redhat.com> On Thu, Sep 27, 2007 at 11:11:24PM +0200, Juerg Ritter wrote: > Hello there! > > I am wondering if there is a possibility to define that the VNC Port of > a virtual machine is always equal to the ID of the machine. That would > be very interesting for scripting, and easy to find out on which VNC > Display i have to search for a particular machine. Does anybody has an idea? You can request an explicit port for a VM, but there is no guarentee tht the request will actually be honoured - if another process is using the port you request, Xen will pick a different port. > I would like to invoke something like: > > vncviewer : In Fedora 7 there is a new tool which avoids the need to know the VNC port at all. Simply tell it the name or ID or UUID of the guest when running, eg with Xen virt-viewer [guest name|id|uuid] Or with KVM you can do virt-viewer --connect qemu:///system [guest name|id|uuid] Basically, virt-viewer contacts libvirt to find out the VNC port and then displays a VNC client window. This VNC client also knows about the new encryption support for VNC servers in Xen, QEMU & KVM, so can be used securely over a remote link. In near future it will also be able to automatically tunnel over SSH when needed. 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 ehabkost at redhat.com Fri Sep 28 01:42:19 2007 From: ehabkost at redhat.com (Eduardo Habkost) Date: Thu, 27 Sep 2007 22:42:19 -0300 Subject: [Fedora-xen] Using virt In-Reply-To: References: Message-ID: <20070928014218.GE4668@blackpad.ctb.virtua.com.br> On Thu, Sep 27, 2007 at 04:40:34PM -0400, Maximilian Freisinger wrote: > > Hello, i have some question about virt-manager > > 1. Where is the script virt-manager uses for installation, and is it possible to modify? It uses the same python modules the virt-install script uses. > 2. Can i set kernelparameter for installation (i would need xfs)? virt-install -x option allows that (for paravirtualized guests). > 3. Is it possible to define single lvs as partitions for a new system? LVM LVs? Yes. Just tell virt-manager (or virt-install) to use the LV as the disk for the guest. -- Eduardo From jsolan at knouse.com Fri Sep 28 13:36:50 2007 From: jsolan at knouse.com (Jason Solan) Date: Fri, 28 Sep 2007 09:36:50 -0400 Subject: [Fedora-xen] Fedora 7 kernels In-Reply-To: <20070927042208.GA16511@redhat.com> References: <1190751444.2896.16.camel@localhost.localdomain> <20070927042208.GA16511@redhat.com> Message-ID: <1190986610.2937.16.camel@localhost.localdomain> Thank you for the detailed and full explanation. I appreciate all the work the Fedora and Red Hat teams have done with the XEN development. I was just very surprised(and frustrated) that a fully virtualized F7 would not work. We have implemented a couple of small domU's (webservers,ntp,etc) on a RHEL 5 32-bit dom0. We were looking for a way to move the vm's to some of our more powerful 64-bit machines. Some of the domU's where FC6 and they worked perfectly in HVM mode. Others were F7 and we were unable to do anything with them. Looking forward to trying out the newer kernels (as well as the RHEL 5.1 release). Again, thanks for the information, its nice to see it all very clearly explained out in one place. On Thu, 2007-09-27 at 05:22 +0100, Daniel P. Berrange wrote: > On Tue, Sep 25, 2007 at 04:17:24PM -0400, Jason Solan wrote: > > I've had a lot of problems with Fedora 7 and XEN and I've read some > > messages on this mailing list indicating the F7 kernel is more or less > > broke with xen. > > By problems I mean that 32 bit guests on 64 bit dom0 does not work at > > all for me. Neither paravirtualized (as was a main feature of xen 3.1) > > or fully virtualized. > > The release notes associated with Xen 3.1 turned out to be not quite > accurate on the subject of 32-on-64 & we didn't realize this when we > made corresponding release notes for Fedora 7. > > Xen 3.1 lets you run a 32-bit DomU kernel on a 64-bit hypervisor + Dom0 > *ONLY IF* the DomU kernel was also based on Xen 3.1. ie, a 32-bit DomU > kernel based on older Xen 3.0.* release would will not work on Xen 3.1 > Unfortunately all the Fedora kernels for FC6 are 3.0.3 and F7 GA was > based on Xen 3.0.4, so neither will work on a Xen 3.1 hypervisor + Dom0. > > In the current Xen-unstable upstream (which will become Xen 3.2) there > is now back-compat support for running older DomU kernels. In the most > recent update of Xen in F-7 updates-testing we have included a handful > of backports which at least let us boot a 32-bit FC6 and F7 domU installer > kernel on a 64-bit F7 / F8 host. > > There are ongoing fixes in upstream Xen for various stability issues > when running 32-on-64 though, so it is not perfect. You may be lucky > with our latest updates and have it work, but equally you may not be > lucky. We're tracking upstream & will pull in fixes when available. > > > Combinations I've tried: > > F7 x86_64 dom0 -> F7 x86 domU PV > > Works in basic testing. Has stability problems. > > > F7 x86_64 dom0 -> F7 x86 domU HVM > > F7 HVM has been broken since GA for reasons unrelated to the 32-on-64 > stuff. A last minute clock-source & bootloader change screwed things > up. Yesterday we pushed newer kernel-xen and xen RPMs to updates-testing > which hopefully make this work. > > > RHEL 5 x86_64 dom0 -> F7 x86 domU HVM > > Not going to work - missing the fix I mention above. > > > RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU PV > > Works for me, at least to boot the installer. There are sometimes some > stability issues though, since Xen 3.1 was far from complete in its > 32-on-64 support. > > > RHEL 5.1 Beta x86_64 dom0 -> F7 x86 domU HVM > > Not going to work - missing the fix I mention above. > > > RHEL 5 x86 dom0 -> F7 x86 domU PV -- Only one that works (32 on 32 PV) > > Matched 32-on-32 and 64-on-64 kernels have always worked. > > > I had read a while ago (June?) that a kernel update would be coming soon > > to fix the 32 on 64 PV issue, however I've ran in several new kernels > > and none seem to fix the issue. > > https://www.redhat.com/archives/fedora-xen/2007-June/msg00031.html > > The fix required both kernel-xen & xen updates which are finally available > in updates-testing. > > > I've also repeatedly tried to run a 32 bit HVM fedora 7 guest on 64 bit > > machines and had that fail similar to this: > > F7 HVM guests have known issues, also hopefully now fixed. > > > http://www.redhat.com/archives/fedora-xen/2007-June/msg00094.html > > > > Is there any more work planned for Fedora 7 and xen, or should I just > > wait until F8? Or am I just doing something wrong and the problems I'm > > having should be working on the current builds? > > > Fedora 7 will continue to have updates until its end-of-life. The issue > is that even in upstream Xen 32-on-64 doesn't have the same level of > stability as 32-on-32, or 64-on-64. > > Dan. IMPORTANT: This transmission is sent on behalf of Knouse Foods? for business purposes. It is for the intended recipient only. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you may not disclose, copy or distribute this transmission or take any action in reliance on it. If you received this transmission in error, please notify us immediately by replying to this Email message, and please dispose of and delete this transmission. Thank you. From juerg_ritter at bluewin.ch Fri Sep 28 18:27:54 2007 From: juerg_ritter at bluewin.ch (Juerg Ritter) Date: Fri, 28 Sep 2007 20:27:54 +0200 Subject: [Fedora-xen] ID = VNC Port In-Reply-To: <20070927212107.GS17433@redhat.com> References: <46FC1C7C.4030707@bluewin.ch> <20070927212107.GS17433@redhat.com> Message-ID: <46FD47AA.2050401@bluewin.ch> Hi Daniel Thanks for your suggestions, I will test that out. I am working on a solution for a RHEL5 environment actually, and as far as i know, this virt-viewer is not part of RHEL5. I think I will find a solution that will work. Probably virsh dumpxml gives me some helpful information which can be included into my script. Many thanks for your help! regards, Juerg Daniel P. Berrange wrote: > On Thu, Sep 27, 2007 at 11:11:24PM +0200, Juerg Ritter wrote: > >> Hello there! >> >> I am wondering if there is a possibility to define that the VNC Port of >> a virtual machine is always equal to the ID of the machine. That would >> be very interesting for scripting, and easy to find out on which VNC >> Display i have to search for a particular machine. Does anybody has an idea? >> > > You can request an explicit port for a VM, but there is no guarentee tht > the request will actually be honoured - if another process is using the > port you request, Xen will pick a different port. > > >> I would like to invoke something like: >> >> vncviewer : >> > > In Fedora 7 there is a new tool which avoids the need to know the VNC > port at all. Simply tell it the name or ID or UUID of the guest when > running, eg with Xen > > virt-viewer [guest name|id|uuid] > > Or with KVM you can do > > virt-viewer --connect qemu:///system [guest name|id|uuid] > > Basically, virt-viewer contacts libvirt to find out the VNC port and > then displays a VNC client window. This VNC client also knows about the > new encryption support for VNC servers in Xen, QEMU & KVM, so can be > used securely over a remote link. In near future it will also be able > to automatically tunnel over SSH when needed. > > Regards, > Dan. > From berrange at redhat.com Fri Sep 28 18:49:05 2007 From: berrange at redhat.com (Daniel P. Berrange) Date: Fri, 28 Sep 2007 19:49:05 +0100 Subject: [Fedora-xen] ID = VNC Port In-Reply-To: <46FD47AA.2050401@bluewin.ch> References: <46FC1C7C.4030707@bluewin.ch> <20070927212107.GS17433@redhat.com> <46FD47AA.2050401@bluewin.ch> Message-ID: <20070928184905.GA14112@redhat.com> On Fri, Sep 28, 2007 at 08:27:54PM +0200, Juerg Ritter wrote: > Hi Daniel > > Thanks for your suggestions, I will test that out. I am working on a > solution for a RHEL5 environment actually, and as far as i know, this > virt-viewer is not part of RHEL5. I think I will find a solution that > will work. Probably virsh dumpxml gives me some helpful > information which can be included into my script. RHEL-5.1 should have 'virsh vncdisplay ', for 5.0 you'd need to look at the tag in the XML. 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 -=|