Mailinglist Archive: opensuse (3337 mails)

< Previous Next >
Re: [SLE] Suse 10 + Parallels (Additional Info)
  • From: Art Fore <art.fore@xxxxxxxxxxx>
  • Date: Wed, 12 Apr 2006 08:13:42 -0700
  • Message-id: <1144854822.19636.85.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
I installed the Parallels Hypervisor 2.1 build 1670 under Suse 10.0 with
WinXPsp1 as guest operating system. So far I have two problems.

1. When starting the VM, I get the following error:

Parallels Workstation encountered a problem with the /dev/rtc device.
This may be caused by one of the following reasons: (1) you do not have
proper system permissions, (2) the device is not found in your host PC,
(3) the device is used by another process. The absence of /dev/rtc
device may downgrade VM performance and make internal timers slow.

linux:~ # dmesg |grep -i real
Real Time Clock Driver v1.12

linux:~ # zcat /proc/config.gz |grep -i rtc
# CONFIG_APM_RTC_IS_GMT is not set
CONFIG_RTC=y
# CONFIG_HPET_RTC_IRQ is not set
CONFIG_SENSORS_RTC8564=m
CONFIG_SND_RTCTIMER=m

linux:~ # hwclock --debug --show
hwclock from util-linux-2.12q
Using /dev/rtc interface to clock.
Last drift adjustment done at 1144781683 seconds after 1969
Last calibration done at 1144781683 seconds after 1969
Hardware clock is on UTC time
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2006/04/11 19:39:50
Hw clock time : 2006/04/11 19:39:50 = 1144784390 seconds since 1969
Tue Apr 11 12:39:50 2006 -0.045644 seconds

linux:~ # cat /proc/interrupts
CPU0
0: 755762 XT-PIC timer
1: 16 XT-PIC i8042
2: 0 XT-PIC cascade
5: 401 XT-PIC Intel 82801DB-ICH4
7: 3 XT-PIC parport0
8: 3 XT-PIC rtc
9: 3 XT-PIC acpi
11: 410996 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3,
ehci_hcd:usb4, yenta, ohci1394, eth0, nvidia
12: 114 XT-PIC i8042
14: 40071 XT-PIC ide0
15: 25354 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 0
MIS: 0

2. When connecting a US B printer or harddrive, I get:

Unable to connect USB device

I tried one suggestion

. Check if an usb-operating group exists in your Linux primary OS.
2. If the group exists:
* Include into this group users who have to have an access to USB
devices.
* Proceed to step 5.
3. If the group does not exist:
* Create a group and include into it users who have to have an access to
USB devices.
* In the /etc/fstab file edit the string that mounts the usbfs. Devgid
parameter should contain the identifier of the group created in the
previous step.

usbfs /proc/bus/usb usbfs devgid=<USB gid>,devmode=0664 0 0

This option will of course only work if you have the relevant support
compiled into your kernel.
4. Restart your Linux primary OS.

This resulted in an error in /var/log/boot.msg:

mount: mount point /proc/bus/usb does not exist

Here is the fstab mod:

usbfs /proc/bus/usb usbfs noauto 0 0

to

usbfs /proc/bus/usb usbfs devgid=1000,devmode=0664 0 0

per the instructions above, after adding USB group which is 1000, I get
the following in the /var/log/boot.msg file:

Without the modification, I do not get the boot.msg error message, but
in either case, I get the Unable to connect USB device error.

Parallels is apparently working on this problem.


< Previous Next >