Re: VMware Workstation in F11
Hi Paolo, I know it may not be a direct solution for you, but I was using VMWare server quite happily for a while on F8-F10 and Ubuntu and now moved to VirtualBox 2.2.4 on which I installed winXP to win2K8, F10, F11, SUSE, Debian and Ubuntu with no issues :) Regards, Gescape -Original Message- From: Paolo Galtieri pgalti...@gmail.com Reply-to: Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com To: Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Subject: Re: VMware Workstation in F11 Date: Fri, 10 Jul 2009 07:39:15 -0700 I installed VMware on F11 and the patch and it started fine for me, but when I tried to install WinXP as a guest OS my system locked up solid. By default vmware looks for files in ~./vmware if you moved it and didn't change the config you'll get this error. I also get the errors shown below during the install. Paolo Installing VMware Player 2.5.2 Copying files... Configuring... Traceback (most recent call last): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 73, in emit if self.shouldRollover(record): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 146, in shouldRollover msg = %s\n % self.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 630, in format return fmt.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 421, in format s = self._fmt % record.__dict__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 93: ordinal not in range(128) Traceback (most recent call last): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 73, in emit if self.shouldRollover(record): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 146, in shouldRollover msg = %s\n % self.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 630, in format return fmt.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 421, in format s = self._fmt % record.__dict__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 55: ordinal not in range(128) Traceback (most recent call last): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 73, in emit if self.shouldRollover(record): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 146, in shouldRollover msg = %s\n % self.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 630, in format return fmt.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 421, in format s = self._fmt % record.__dict__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 64: ordinal not in range(128) Traceback (most recent call last): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 73, in emit if self.shouldRollover(record): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 146, in shouldRollover msg = %s\n % self.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 630, in format return fmt.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 421, in format s = self._fmt % record.__dict__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 95: ordinal not in range(128) Traceback (most recent call last): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 73, in emit if self.shouldRollover(record): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 146, in shouldRollover msg = %s\n % self.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 630, in format return fmt.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 421, in format s = self._fmt % record.__dict__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 64: ordinal not in range(128) Traceback (most recent call last): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 73, in emit if self.shouldRollover(record): File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/handlers.py, line 146, in shouldRollover msg = %s\n % self.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 630, in format return fmt.format(record) File /tmp/vmis.TWxHzJ/install/vmware-installer/python/lib/logging/__init__.py, line 421, in format s = self
Re: VMware Workstation in F11
Grzegorz Witkowski wrote: Hi Paolo, I know it may not be a direct solution for you, but I was using VMWare server quite happily for a while on F8-F10 and Ubuntu and now moved to VirtualBox 2.2.4 on which I installed winXP to win2K8, F10, F11, SUSE, Debian and Ubuntu with no issues :) Regards, Gescape You should really read the list guidelines - specifically the parts about top posting and trimming the message you are replying to. There is no need to include the install log from Paolo Galtieri when your reply does not address any part of it. Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: VMware Workstation in F11
On Fri, Jul 10, 2009 at 3:29 PM, Matthew Saltzmanm...@clemson.edu wrote: I performed a fresh install of F11, then installed VMware-Workstation-6.5.2-156735.x86_64.rpm. Installed the patch for kernel-2.6.29 from http://communities.vmware.com/thread/203231. Now, when I try to start a VM, I get a message that the .vmdk file can't be found. The message pop-up lets me browse to the location of the file. File not found: xxx.vmdk This file is required to power on the virtual machine. If this file was moved, please provide its new location. But the file has not been moved, and when I select the file from the browser, VMware still refuses to start. Turning selinux to non-enforcing doesn't help. Problem occurs with Workstation and Player. Everything worked fine with F10, including with a 2.6.29 test kernel. Anybody seen this? Anybody know a solution? Try disabling selinux completely. On my F10 box with vmware server, permissive mode wasn't enough. Regards, Chris -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: VMware Workstation in F11
On Mon, 2009-07-13 at 12:52 +0200, Chris Rouch wrote: On Fri, Jul 10, 2009 at 3:29 PM, Matthew Saltzmanm...@clemson.edu wrote: I performed a fresh install of F11, then installed VMware-Workstation-6.5.2-156735.x86_64.rpm. Installed the patch for kernel-2.6.29 from http://communities.vmware.com/thread/203231. Now, when I try to start a VM, I get a message that the .vmdk file can't be found. The message pop-up lets me browse to the location of the file. File not found: xxx.vmdk This file is required to power on the virtual machine. If this file was moved, please provide its new location. But the file has not been moved, and when I select the file from the browser, VMware still refuses to start. Turning selinux to non-enforcing doesn't help. Problem occurs with Workstation and Player. Everything worked fine with F10, including with a 2.6.29 test kernel. Anybody seen this? Anybody know a solution? Try disabling selinux completely. On my F10 box with vmware server, permissive mode wasn't enough. I got it, actually (noted elsewhere in the thread). It was permissions, but not selinux. For a raw-disk machine, user needs to be in group disk. Apparently, with F11, they finally made /dev/sda* group writable again, so sysadmin doesn't need to do it. VMs still hang on shutdown, but that seems to be a different, known issue with no current workaround. Regards, Chris -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: VMware Workstation in F11
On Fri, 2009-07-10 at 07:39 -0700, Paolo Galtieri wrote: I installed VMware on F11 and the patch and it started fine for me, but when I tried to install WinXP as a guest OS my system locked up solid. By default vmware looks for files in ~./vmware if you moved it and didn't change the config you'll get this error. I also get the errors shown below during the install. I did not move the files--they are still in a subdirectory of ~/vmware. I don't recall if there were errors, but I will re-install and try again. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: VMware Workstation in F11 [SOLVED]
On Fri, 2009-07-10 at 16:49 -0400, Matthew Saltzman wrote: On Fri, 2009-07-10 at 07:39 -0700, Paolo Galtieri wrote: I installed VMware on F11 and the patch and it started fine for me, but when I tried to install WinXP as a guest OS my system locked up solid. By default vmware looks for files in ~./vmware if you moved it and didn't change the config you'll get this error. I also get the errors shown below during the install. I did not move the files--they are still in a subdirectory of ~/vmware. I don't recall if there were errors, but I will re-install and try again. Sorry for the dup. I reinstalled and started vmware as root to get modules built (instead of the command-line command suggested in the patch script). This time, it worked. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: VMware Workstation in F11 [really SOLVED]
On Fri, 2009-07-10 at 20:11 -0400, Matthew Saltzman wrote: On Fri, 2009-07-10 at 16:49 -0400, Matthew Saltzman wrote: On Fri, 2009-07-10 at 07:39 -0700, Paolo Galtieri wrote: I installed VMware on F11 and the patch and it started fine for me, but when I tried to install WinXP as a guest OS my system locked up solid. By default vmware looks for files in ~./vmware if you moved it and didn't change the config you'll get this error. I also get the errors shown below during the install. I did not move the files--they are still in a subdirectory of ~/vmware. I don't recall if there were errors, but I will re-install and try again. Sorry for the dup. I reinstalled and started vmware as root to get modules built (instead of the command-line command suggested in the patch script). This time, it worked. It worked because it was running as root (so that it could build the modules. This VM is a raw disk one, and I needed write access to the raw disks. I added my userid to the disk group and now it works (except it seems to hang on shutdown, but that's a problem for another day). Used to be that I got an informative error message when this happened, about not having write access to the raw disk. Not sure why that's no longer the case. -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
