Possible Causing gutsy lockup.

M

mcginleyr1

Bit poster
Whenever I'm in parallels and shutdown an instance of windows xp parallels locks up and locks system resources. Eventually this causes gutsy to completely lockup (mouse and keyboard don't work) I've let it sit for an hour and have it still be locked up. I've tried using killall parallels and killall parallels-linux in the console and it just idles and does nothing. This forces a hard reboot (reset button) and almost every time causes the need for an fsck to be run because of corrupted inodes. I was wondering if there is any advice anyone can give me to get to the root of the problem. By the way i'm running Ubuntu 7.10 Gutsy Gibbon.
 
Sort by date Sort by votes
Same problem in Debian testing

No solution, but I can tell you the problem isn't limited to Ubuntu. Debian testing with kernel 2.6.22 is affected. I was surprised to find build 2204 would compile and run on this kernel, things went sour when I tried to suspend my VM (Windows XP sp2).

So, runs fine but when I try to suspend it goes till about 94% done then locks up the machine. Can't kill parallels when this happens, so need to do a hard reboot - not good. My VM was also broken after this - reverted to a backup. This happened 3 times, it's not a one off. I haven't tried to shutdown the vm as opposed to suspend it yet.

Here's what I found in the kernel.log:
Nov 5 12:22:53 dell kernel: parport0: FIFO is stuck
Nov 5 12:22:53 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:23:56 dell kernel: end_request: I/O error, dev fd0, sector 0
Nov 5 12:23:57 dell last message repeated 7 times
Nov 5 12:23:59 dell kernel: BUG: unable to handle kernel paging request at virtual address 0000d0be
Nov 5 12:23:59 dell kernel: printing eip:
Nov 5 12:23:59 dell kernel: c014ee79
Nov 5 12:23:59 dell kernel: *pde = 00000000
Nov 5 12:23:59 dell kernel: Oops: 0000 [#1]
Nov 5 12:23:59 dell kernel: SMP
Nov 5 12:23:59 dell kernel: Modules linked in: nls_utf8 hfsplus sd_mod usb_storage xt_multiport vmvirtualnic(P) vm_bridge(P) vm_main(PF) hypervisor(P) radeon drm binfmt_misc ppdev lp button ac battery ipv6 xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE ipt_TOS ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink iptable_mangle iptable_filter ip_tables x_tables fuse dm_snapshot dm_mirror dm_mod loop snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi qt1010 zl10353 snd_seq_midi_event snd_seq dvb_usb_gl861 dvb_usb dvb_core snd_timer snd_seq_device firmware_class pcspkr snd dvb_pll psmouse soundcore parport_pc parport serio_raw snd_page_alloc rtc i2c_i801 i2c_core iTCO_wdt shpchp pci_hotplug intel_agp agpgart tsdev evdev ext3 jbd mbcache ide_cd cdrom ide_disk ata_generic libata scsi_mod generic usbhid hid floppy e1000 piix ide_core ehci_hcd uhci_hcd usbcore thermal processor fan
Nov 5 12:23:59 dell kernel: CPU: 0
Nov 5 12:23:59 dell kernel: EIP: 0060:[<c014ee79>] Tainted: PF VLI
Nov 5 12:23:59 dell kernel: EFLAGS: 00210006 (2.6.22-2-686 #1)
Nov 5 12:23:59 dell kernel: EIP is at find_get_page+0x1e/0x48
Nov 5 12:23:59 dell kernel: eax: 0000d0be ebx: 000aa6ec ecx: 0000d0be edx: 00000000
Nov 5 12:23:59 dell kernel: esi: f507291c edi: 000aa6ec ebp: 000aa6ec esp: d45b9dfc
Nov 5 12:23:59 dell kernel: ds: 007b es: 007b fs: 00d8 gs: 0033 ss: 0068
Nov 5 12:23:59 dell kernel: Process parallels-linux (pid: 6790, ti=d45b8000 task=f5de4580 task.ti=d45b8000)
Nov 5 12:23:59 dell kernel: Stack: 00000a00 d45b9eac c014f6a7 00000a00 00000003 db9ad480 db9ad4c8 f507291c
Nov 5 12:23:59 dell kernel: f5072874 000da529 00000000 000aa6ef 000aa6ef 000aa6eb 00000000 da529c00
Nov 5 12:23:59 dell kernel: 00000000 00000000 00001000 000aa6d9 00000020 00000000 00000000 000aa6ee
Nov 5 12:23:59 dell kernel: Call Trace:
Nov 5 12:23:59 dell kernel: [<c014f6a7>] do_generic_mapping_read+0x15c/0x46a
Nov 5 12:23:59 dell kernel: [<c0151373>] generic_file_aio_read+0x164/0x195
Nov 5 12:23:59 dell kernel: [<c014ed17>] file_read_actor+0x0/0xca
Nov 5 12:23:59 dell kernel: [<c0169e03>] do_sync_read+0xc7/0x10a
Nov 5 12:23:59 dell kernel: [<c011e20e>] default_wake_function+0x0/0xc
Nov 5 12:23:59 dell kernel: [<c012c310>] specific_send_sig_info+0x8e/0x99
Nov 5 12:23:59 dell kernel: [<c013319d>] autoremove_wake_function+0x0/0x35
Nov 5 12:23:59 dell kernel: [<c016eda5>] pipe_ioctl+0x50/0x54
Nov 5 12:23:59 dell kernel: [<c0169d3c>] do_sync_read+0x0/0x10a
Nov 5 12:23:59 dell kernel: [<c016a605>] vfs_read+0xa6/0x128
Nov 5 12:23:59 dell kernel: [<c016aa01>] sys_read+0x41/0x67
Nov 5 12:23:59 dell kernel: [<c0103d0e>] sysenter_past_esp+0x6b/0xa1
Nov 5 12:23:59 dell kernel: =======================
Nov 5 12:23:59 dell kernel: Code: 00 00 00 90 5a 89 c8 59 5b 5e 5f 5d c3 56 89 c6 53 89 d3 8d 40 10 e8 6c 65 15 00 8d 46 04 89 da e8 20 f5 07 00 85 c0 89 c1 74 17 <8b> 00 89 ca 25 00 40 02 00 3d 00 40 02 00 75 03 8b 51 0c 90 ff
Nov 5 12:23:59 dell kernel: EIP: [<c014ee79>] find_get_page+0x1e/0x48 SS:ESP 0068:d45b9dfc
Nov 5 12:24:03 dell kernel: parport0: FIFO is stuck
Nov 5 12:24:03 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:25:13 dell kernel: parport0: FIFO is stuck
Nov 5 12:25:13 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:26:23 dell kernel: parport0: FIFO is stuck
Nov 5 12:26:23 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:27:33 dell kernel: parport0: FIFO is stuck
Nov 5 12:27:33 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:28:43 dell kernel: parport0: FIFO is stuck
Nov 5 12:28:43 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:29:53 dell kernel: parport0: FIFO is stuck
Nov 5 12:29:53 dell kernel: parport0: BUSY timeout (1) in compat_write_block_pio
Nov 5 12:30:06 dell kernel: BUG: unable to handle kernel paging request at virtual address 00009a3c
Nov 5 12:30:06 dell kernel: printing eip:
Nov 5 12:30:06 dell kernel: c0150e51
Nov 5 12:30:06 dell kernel: *pde = 00000000
Nov 5 12:30:06 dell kernel: Oops: 0000 [#2]
Nov 5 12:30:06 dell kernel: SMP
Nov 5 12:30:06 dell kernel: Modules linked in: nls_utf8 hfsplus sd_mod usb_storage xt_multiport vmvirtualnic(P) vm_bridge(P) vm_main(PF) hypervisor(P) radeon drm binfmt_misc ppdev lp button ac battery ipv6 xt_limit xt_tcpudp ipt_LOG ipt_MASQUERADE ipt_TOS ipt_REJECT nf_conntrack_irc nf_conntrack_ftp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink iptable_mangle iptable_filter ip_tables x_tables fuse dm_snapshot dm_mirror dm_mod loop snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi qt1010 zl10353 snd_seq_midi_event snd_seq dvb_usb_gl861 dvb_usb dvb_core snd_timer snd_seq_device firmware_class pcspkr snd dvb_pll psmouse soundcore parport_pc parport serio_raw snd_page_alloc rtc i2c_i801 i2c_core iTCO_wdt shpchp pci_hotplug intel_agp agpgart tsdev evdev ext3 jbd mbcache ide_cd cdrom ide_disk ata_generic libata scsi_mod generic usbhid hid floppy e1000 piix ide_core ehci_hcd uhci_hcd usbcore thermal processor fan
Nov 5 12:30:06 dell kernel: CPU: 0
Nov 5 12:30:06 dell kernel: EIP: 0060:[<c0150e51>] Tainted: PF VLI
Nov 5 12:30:06 dell kernel: EFLAGS: 00210097 (2.6.22-2-686 #1)
Nov 5 12:30:06 dell kernel: EIP is at find_get_pages+0x32/0x62
Nov 5 12:30:06 dell kernel: eax: 00000000 ebx: 0000000e ecx: 00000008 edx: 00009a3c
Nov 5 12:30:06 dell kernel: esi: 00000000 edi: da4abb04 ebp: d4e45db0 esp: d4e45d60
Nov 5 12:30:06 dell kernel: ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Nov 5 12:30:06 dell kernel: Process parallels-linux (pid: 6792, ti=d4e44000 task=da099a90 task.ti=d4e44000)
Nov 5 12:30:06 dell kernel: Stack: 0000000e 00000000 d4e45da8 0000000e 00000000 c015531c d4e45db0 d4e45da8
Nov 5 12:30:06 dell kernel: 00000000 c0155815 0000000e 00000000 c014df2b 00000000 00000000 da4abb04
Nov 5 12:30:06 dell kernel: 00000000 ffffffff 00000000 00000000 c1ca4236 c1c27b20 c1c27b40 c1c27b60
Nov 5 12:30:06 dell kernel: Call Trace:
Nov 5 12:30:06 dell kernel: [<c015531c>] pagevec_lookup+0x1c/0x22
Nov 5 12:30:06 dell kernel: [<c0155815>] truncate_inode_pages_range+0x1b2/0x256
Nov 5 12:30:06 dell kernel: [<c014df2b>] handle_fasteoi_irq+0x9c/0xa6
Nov 5 12:30:06 dell kernel: [<f899a8ef>] ext3_delete_inode+0x0/0xba [ext3]
Nov 5 12:30:06 dell kernel: [<c01558d0>] truncate_inode_pages+0x17/0x1a
Nov 5 12:30:06 dell kernel: [<f899a902>] ext3_delete_inode+0x13/0xba [ext3]
Nov 5 12:30:06 dell kernel: [<f899a8ef>] ext3_delete_inode+0x0/0xba [ext3]
Nov 5 12:30:06 dell kernel: [<c017a51f>] generic_delete_inode+0xa1/0x107
Nov 5 12:30:06 dell kernel: [<c0179cfc>] iput+0x60/0x62
Nov 5 12:30:06 dell kernel: [<c0178049>] d_kill+0x2d/0x46
Nov 5 12:30:06 dell kernel: [<c0178137>] dput+0xd5/0xdc
Nov 5 12:30:06 dell kernel: [<c016ad55>] __fput+0x126/0x150
Nov 5 12:30:06 dell kernel: [<c015c908>] remove_vma+0x25/0x36
Nov 5 12:30:06 dell kernel: [<c015c9e9>] exit_mmap+0xd0/0xe7
Nov 5 12:30:06 dell kernel: [<c0121136>] mmput+0x20/0x76
Nov 5 12:30:06 dell kernel: [<c0125a5e>] do_exit+0x1d2/0x6d4
Nov 5 12:30:06 dell kernel: [<c012b01d>] recalc_sigpending+0xb/0x1d
Nov 5 12:30:06 dell kernel: [<c0125fd6>] sys_exit_group+0x0/0xd
Nov 5 12:30:06 dell kernel: [<c012ce54>] get_signal_to_deliver+0x380/0x3ad
Nov 5 12:30:06 dell kernel: [<c0103463>] do_notify_resume+0x84/0x600
Nov 5 12:30:06 dell kernel: [<c013bf69>] do_futex+0x6c/0xa20
Nov 5 12:30:06 dell kernel: [<c013c9df>] sys_futex+0xc2/0xd4
Nov 5 12:30:06 dell kernel: [<c0126f2b>] sys_gettimeofday+0x27/0x53
Nov 5 12:30:06 dell kernel: [<c0103e5a>] work_notifysig+0x13/0x19
Nov 5 12:30:06 dell kernel: =======================
Nov 5 12:30:06 dell kernel: Code: 53 89 cb 83 ec 04 8d 40 10 8b 6c 24 18 e8 9d 45 15 00 89 f1 8d 47 04 89 ea 89 1c 24 e8 9c d5 07 00 31 c9 89 c3 eb 1a 8b 54 8d 00 <8b> 02 25 00 40 02 00 3d 00 40 02 00 75 03 8b 52 0c 90 ff 42 04
Nov 5 12:30:06 dell kernel: EIP: [<c0150e51>] find_get_pages+0x32/0x62 SS:ESP 0068:d4e45d60
Nov 5 12:30:06 dell kernel: Fixing recursive fault but reboot is needed!
 
Upvote 0 Downvote
one more thing

everything works normally on kernel 2.6.18, it's only when I boot with 2.6.22 that I can't suspend, so it definitely seems to be something in the 2.6.22 kernel that causes problems.
 
Upvote 0 Downvote
Lockup on Suspend, not shutdown

Just tried shutting down windows in the VM, as opposed to having parallels suspend the VM. And that worked fine, so for now a workaround is to shutdown each time and not suspend the VM.

Loss of a nice feature though :(

Still, probably wastes less time than rebooting with kernel 2.6.18 just to use parallels ;)
 
Upvote 0 Downvote
Debian testing

I'm running Debian testing not ubuntu. I did run memtest - not at boot, so it won't have tested all the memory, but I found no problems. And everything else is fine. For me this is really specific to suspending a virtual machine whilst using kernel 2.6.22, I can shutdown a vm on 2.6.22 though, and I can suspend and shutdown on 2.6.18. Seems like an incompatability between parallels build 2204 and the debian 2.6.22 kernel to me.
 
Upvote 0 Downvote
Guaranteed lock up when guest OS is running

I was running parallels on Ubuntu 7.04 (feisty)[as host] without issue running an XP instance as a guest.

I bravely upgraded to Ubuntu 7.10 (gutsy) only to find parallels would lock up the entire system.. guest and host! No particular behaviour seemed to trigger the lock up, it would do it whenever the guest OS was up and running!

I upgraded to parallels build 2204 however the problem still existed.

I did a fresh install of 7.10 and then installed parallels 2204. Same problem, system totally locked up requiring a hard reboot.

I've now gone back to 7.04 with parallels 2204 and everything is working perfectly again.. except for the fact I'm back where I started!!! ;)

So something funny going on....
 
Upvote 0 Downvote
Known Issue - Not in Knowledge Base

I had the same issue, trying to install WinXP as the guest OS on Kubuntu 7.10, about 80% way through the install I kept getting a kernel panic and complete freeze. The guy who sits next to me had the same problem (same OS and Parallels build). This is the response from support:

"Unfortunately Parallels Workstation does not support the new Ubuntus
kernels. Parallels Developers are working on this problem. The only
suggestion I can give is to install Ubuntu with an old kernel."

When asking how long until a new build was out I got this:

"Unfortunately I do not know when this release will be.
Please keep an eye on the news on Parallels web site."

I'm just slightly irked because this is the first time I've used Parallels. I bought it because a lot of my coworkers have had a lot of success with it. I paid for it almost a month ago, and I'm still not able to use it. Downgrading my OS is not a feasible option.
 
Upvote 0 Downvote
Ya its definitely not playing friendly with the kernel. It causes all kinds of file system errors. if i run an fsck on startup after using parallels on desktop (killing it to end the windows session) or my laptop i get inode errors. very very bad. And its not a memory issue on my machine i fixed that and it still a crap fest.
 
Upvote 0 Downvote
I'm running Debian testing with self-compiled 2.6.22.14 kernel and parallels doesn't lock up during suspending or shtudown. There must be a patch or config in your kernel that might conflict with parallels. Can you do a diff in the config files between 2.6.18, 2.6.21, (non-locking kernels) and 2.6.22 (locking kernel)? I think a feature in 2.6.22 was activated that the earlier kernels didn't have is causing the lockups.

I'm running parallels 2204 btw.
 
Upvote 0 Downvote
Hello all,

Adrinux, please try decreasing the amount of memory allocated to Parallels and your Guest OS:

1. In Workstation menu click Edit -> Preferences. Set the RAM size 350 MB approximately.
2. Launch your VM but do not start Windows. In Configuration Editor - Memory set RAM size 250 MB or less (please try different levels).

In Options of Configuration Editor - VM Flags set Acceleration level to Normal.
Start your Guest OS.

Waiting for the feedback.

Best regards,
Xenos
 
Upvote 0 Downvote
Hi Xenos,

I tried lowering the memory to 256MB and also put the acceleration in 'normal'. My system (Debian/Sid with a custom 2.6.22 kernel) froze shortly after I started the VM. I didn't even make it to the login screen.

Best Regards,
 
Upvote 0 Downvote
Hello Raghos,

Could you let me know the Workstation build you are using and your processor type?

Please enable Virtualization Support in the Workstation Configuration (Options -> Advanced).

Best regards,
Xenos
 
Upvote 0 Downvote
Hi Xenos,

Sorry for the late response: I've upgraded to 2.6.23, reconfigured parallels with the patch that is going around, and now it is not freezing anymore. Although I don't have network access from the VM anymore.

Oh well.
 
Upvote 0 Downvote
Hi Macaby,

When you have the VM loaded (in the main parallels window) you'll see 'Acceleration' listed. If you either click on that link, or edit the VM options, you'll be able to change the acceleration option.

Cheers.
 
Upvote 0 Downvote
raghos,

If you're talking about the pop-up Parallels window that in my case, says Microsoft Windows Vista, the options I see are...

Memory 1024
Floppy Disk
Hard Disk 1
CD/DVD-ROM 1
Network Adapter 1; Shared networking
Sound
USB Controller

I also don't see anything about acceleration in the pulldown Parallels menu at the top of the screen.
 
Upvote 0 Downvote
Hi Macaby,

Ok, those options are above the options you list. I'm guessing some of these options might be OS-specific, and 'acceleration' is not available for Vista (I'm running XP as guest).

Cheers.
 
Upvote 0 Downvote
You must log in or register to reply here.
Back
Top