KVM mysteries

I have a new 23" Cinema Display that I would like to use with my standard KVM 4 port switch. I would like to be able to switch between my powerbook, a G4, G5 and a PC. I've been looking for a female DVI to male 15 pin cable to plug the Cinema Display to my KVM. Anybody have any experience with this or any suggestions on if it can even be done? I have seen a DVI KVM but the older Macs and PCs don't have DVI.

Looking for a KVM that will perform it's duty on my system.
I Have a 21" Apple Studio Display (CRT). Great monitor for print graphics.
I am running a dual 2g G5:
Machine Model: PowerMac7,2
CPU Type: PowerPC 970 (2.2)
Number Of CPUs: 2
CPU Speed: 2 GHz
L2 Cache (per CPU): 512 KB
Memory: 2.5 GB
Bus Speed: 1 GHz
Boot ROM Version: 5.0.7f0
I also have a G4 450 with scsi connectors that I use to run a very nice Epson scanner. Plenty of RAM and HD space. May be used for Back-ups as well.
I want to use both of these Macs on my single monitor.
I have tried the Belkin flip (regular w/remote button - no video - and the Mac Mini version - chaos! ... opening CD trays, volume up and down, auto monitor switching). I am not alone in that experience as I have found out!
I tried the iogear 2 port USB KVM - no video. Customer support was helpful but unable to solve the problem as they just discovered that it wont support the Studio Displays. I was impressed with their efforts though.
I am currently connecting my Studio Display to the G5 by a VGA to DVI Apple connector.
All this said, is there a reasonably priced KVM that will handle this set-up?
All I need is a 2 port USB KVM. It doesn't have to be pretty either!
Thanks
G5/G4 Mac OS X (10.4.7) Apple 21" Studio Display

Similar Messages

Is KVM VGA Passthrough Possible on Macbook Pro Mid 2014?

I've been using Arch on and off for a couple years on different hardware, and this time I'm trying to get it to work semi-flawlessly on my mid 2014 Macbook Pro. My Linux skills are meager, so I need some help understanding if VGA passthrough is possible on this machine, and if it is, how to set it up. I have hope that it might work after reading this blog and the Arch forums. An outline of my current setup follows. I will also document progress and research for anyone who might want to try this in the future.
Here are the specifications for this machine:
Processor: 2.5 GHz Intel Core i7
Memory: 16 GB 1600 MHz DDR3
Graphics: Intel Iris Pro 1536 MB, Nvidia GT 750M 2 GB
I have successfully dual-booted Mac OS X Yosemite and Arch with EFI on a btrfs partition using this blog and the wiki as starting points. Somlo's research also helped. All the basic functionality works (networking, WiFi, etc.), and I am able to boot the physical Arch partition as a Virtualbox VM with the help of the wiki. However, I'm having trouble with getting the integrated Intel graphics to work. The following command:
lspci | grep VGA
prints the Nvidia card specifications, and nothing about the Intel graphics.
Reading this blog, it looks like someone had to apply a "grub gmux" patch to grub to disable the Nvidia card at boot. I feel uncomfortable installing anything other than the official Arch packages, so I have to know if installing a patched grub is still necessary, and if installing it would still allow me to use VGA passthrough in KVM.
My ambitious to-do list looks like this:
1. Dual-boot Mac OS X and Arch with btrfs. -done
2. Setup the physical Arch partition to boot in Virtualbox. -done
3. Get Intel graphics to work on Arch ideally with OpenGL support. -done
4. Get Enlightenment working as the desktop environment on Arch. -done
5. Get Qemu+KVM to boot off the physical Mac OS X partition. -tbd
6. Enable VGA passthrough for Mac OS X from Qemu+KVM. -tbd
7. Install Windows as a VM in Qemu+KVM. -tbd
8. Enable VGA passthrough for Windows from Qemu+KVM. -tbd
9. Work and do research on Mac OS X from Arch, play hardcore 3D games on WIndows from Arch, play around with Arch, and live happily ever after. -tbd
Can anyone help me with this? Thanks in advance for any hints/input.
Edit:
The Ubuntu forums has something about getting the two graphics cards to be recognised by using `refind` instead of `grub`. I was able to set up `refind` to boot using the `efi-stub`, but:
$ lspci
00:00.0 Host bridge: Intel Corporation Crystal Well DRAM Controller (rev 08)
00:01.0 PCI bridge: Intel Corporation Crystal Well PCI Express x16 Controller (rev 08)
00:01.1 PCI bridge: Intel Corporation Crystal Well PCI Express x8 Controller (rev 08)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d5)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d5)
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GK107 HDMI Audio Controller (rev a1)
03:00.0 Network controller: Broadcom Corporation BCM4360 802.11ac Wireless Network Adapter (rev 03)
04:00.0 Multimedia controller: Broadcom Corporation 720p FaceTime HD Camera
05:00.0 SATA controller: Samsung Electronics Co Ltd Apple PCIe SSD (rev 01)
06:00.0 PCI bridge: Intel Corporation Device 156d
07:00.0 PCI bridge: Intel Corporation Device 156d
07:03.0 PCI bridge: Intel Corporation Device 156d
07:04.0 PCI bridge: Intel Corporation Device 156d
07:05.0 PCI bridge: Intel Corporation Device 156d
07:06.0 PCI bridge: Intel Corporation Device 156d
08:00.0 System peripheral: Intel Corporation Device 156c
still only shows the Nvidia card. The boot options suggested by this blog did not change anything. However, this very helpful discussion led me to this on-going project. I patched the kernel according the instructions in the said project's `readme`, and Arch is now able to see the two graphics cards and an extra Intel audio controller.
$ lspci
00:02.0 VGA compatible controller: Intel Corporation Crystal Well Integrated Graphics Controller (rev 08)[/bold]
00:03.0 Audio device: Intel Corporation Crystal Well HD Audio Controller (rev 08)
01:00.0 VGA compatible controller: NVIDIA Corporation GK107M [GeForce GT 750M Mac Edition] (rev a1)
Also, I was able to fire up Enlightenment using the Intel graphics card and `0xbb`'s `gpu-switch` script. After using some post-installation tips from this, the computer started getting hot. I followed this thread to get it back to normal.
Edit:
So I finally got some time to experiment on this. I ended up installing Gnome 3 after trying out Enlightenment, KDE Plasma 5, and Cinnamon. I thought Gnome 3 and Cinnamon had the best Hi-DPI support of those four. Cinnamon's look was too much trouble for me to configure, so I ended up choosing Gnome 3.
To achieve the graphics card passthrough, I tried setting up and starting a VM in `virt-manager`, but starting the VM would cause Arch to freeze. Finally, I tried following the instructions on the wiki, this thread, and the Arch forums. I haven't yet tried booting the Windows installer, but the following are the steps I took so far:
1. Uninstall all `nvidia` drivers from my system.
2. Blacklist the `nouveau` driver.
3. Add `pci-stub` to the modules array in `mkinitcpio.conf`.
4. Recreate the `initramfs`.
5. Add `intel_iommu=on pci-stub.ids=10de:0fe9,10de:0e1b,8086:156c` to the `refind.conf` `options` line.
- These three IDs are ones for the Nvidia graphics, Nvidia sound, and the "Intel Corporation Device" (probably the HDMI port, or something related to the
ethernet card), which belong to the same "IOMMU group". What was curious was that a Gigabit ethernet controller would appear in the IOMMU group iff I had
an ethernet cable connected to my thunderbolt port. I don't know if I have to add the ID for this, but so far there are no complaints about it in `dmesg`.
6. Install `ovmf-svn` from the AUR.
6. Follow the "Binding a device to vfio-pci" section documented at https://bbs.archlinux.org/viewtopic.php?id=162768.
7. Follow the "Testing if its working out" section documented at https://bbs.archlinux.org/viewtopic.php?id=162768.
So far, the test at step 7 is failing -- I get a `vfio-pci 0000:01:00.0: Invalid ROM contents` complaint in `dmesg`, and I see a prompt in the `qemu` window. I'm supposed to be getting a black `qemu` window, and a prompt on an external monitor which I haven't connected yet. I read the comments on this blog about graphics card ROM and EFI compatibility, and it looks like my graphics card ROM can't be read. I also read that the graphics card ROM would only be read once by qemu/KVM and saved as a file for later use, so all I need to do to get around that is pass a snapshot of the ROM of the Nvidia GT 750M card to qemu/KVM. Apparently, "You can download the 750m rom files directly from Lenovo's website on the support page" according to this thread, but all I see is this. I will continue hunting around for a ROM file for this graphics card.
Last edited by rb3 (2015-06-05 02:01:20)

It`s not beacuse of the case. I have the same problem with a macbook pro retina 15 late 2013 (I7 - 2.3 Ghz, 16 GB, 512 SSD, GT750M) with windows 8.1 on bootcamp. The temperature is higher than yosemite. It gets easily at 80 celsius in a demanding game, while on yosemite it barely reaches 55-60 under heavy load. It`s beacuse of windows, and these are the temperatures, I got the same average 55-60 in windows and 45 celsius in yosemite. I read on the forums and I tried evend with a cooler pad. But it doesn`t seem to be any improvement with lowering the temperature in windows.

[SOLVED] After qemu update: KVM does not work anymore

Hi,
I used to use qemu-kvm, as in
qemu-kvm \
-net nic,vlan=1 -net user,vlan=1 \
-drive file=/home/flash-vm/hdd0,if=virtio,cache=writethrough \
-vga std -vnc localhost:2 -usbdevice tablet \
-m 1024
However, now qemu-kvm has been removed. If I replace "qemu-kvm" with "qemu-system-x86_64" and try to run it with an extra argument "-machine accel=kvm" or "-enable-kvm", what I get is
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied
The kernel modules are there:
# lsmod | grep kvm
kvm_intel 124064 0
kvm 384721 1 kvm_intel
and the processor is
$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 2
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 37
Stepping: 5
CPU MHz: 1197.000
BogoMIPS: 5321.24
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 256K
L3 cache: 3072K
NUMA node0 CPU(s): 0-3
I have added my user to the group kvm as well, as instructed by pacman. Any help would be much appreciated!
Last edited by ffcitatos (2013-03-07 06:47:06)

Interestingly, mine worked without being in the new group. However, I think that's because I hadn't logged out since the update, so the session didn't know that I had been removed from the group. Though I could be missing something.

KVM resolution problem

Hi; I have a 2.16 with an Apple mini DVI to VGA adapter trying to connect to a LCD display through a Belkin KVM. The problem is that the desktop will show up on both monitors momentarily then go blank (both), after a few seconds the MB display will come on at a different resolution and the external display will show "No signal". A few seconds later they will both come back on at a different resolution and then immediately go blank again. This goes on until the DVI connector is pulled.It goes through many different combinations of settings. I think (a dangerous thing) that for some reason the MB and external monitor can't resolve the proper settings and so just goes into a loop of check and reset. My question, is it possible to set a default setting for any external monitor connected so that the two will sync? I have a 1.8 G5 connected also and it has no problems although it is a different situation.

Hi,
I sometimes have problems with my KVM switch too. I have a Dell E172FP Monitor.
In certain scenarios when I change from my PC to Mini the resolution goes to pot. The way I get round it is to do the following :
1. Go to system preferences
2. Go to Displays
3. Click 'detect displays'
It then restores the screen to the proper resolution. It's a bit of a pain. It's almost as though the mac forgets what is connected to it and defaults to facory settings or something.
What KVM switch are you using? I've got a Belkin. Maybe it's got something to do with that too.
Hope this offers some help.
TMan

How do i connect my mac mini to a kvm switch using the hdmi to dvi adapter?

I want to connect my Mac Mini using the HDMI to DVI adapter to a KVM switch cable. I have an Iogear KVM switch. The cable from the KVM switch has a male VGA end connection. I have been trying to determine the right adapter to connect the female DVI connection to the male VGA connector. I will be using the Mac mini and a PC running through the KVM switch. This is doable as the iogear switch is compatible with both a PC and a Mac. Any ideas out there? Thank you.

You would need to get HDMI or DVI to VGA CONVERTER, not a simple adopter. The converter requires USP connection for power. HDMI is only digital while VGA is analogue.
http://www.newegg.com/Product/Product.aspx?Item=N82E16812699001&nm_mc=EMC-IGNEFL 070414&cm_mmc=EMC-IGNEFL070414-_-EMC-070414-Index-_-AudioVideoSplitters-_-126990 01-L019B
If your MIni has a mini displayport or Thunderbolt port yu can get a les expensive mini displayport to VGA afopter.

Mac mini with KVM switch

I'm thinking of getting a Mac mini, but I need my Windows PC for some apps that aren't available on Mac and some other stuff. I can't afford to get a large monitor for a Mini if I get one, but my current PC has a big flat panel display.I noticed the KVM cable way of moving your stuff (a cale taht lets peripherals like monitors, keyboard and mice be connected to two computers so you don't need a separate one for eache computer), and was wondering if that's a possible way of using both without buying monitors, etc. for the Mini.
Is anyone doing this, and if so, what do you think of using the Mini this way? Does it work well, and what are the pros and cons of doing this?
Thanks,
Ilya Smirnov

My experience with my Belkin KVM is also good, with the exception of one thing. I can't switch back to the Mini once I've switched to the PC. I have to unplug the PS2/USB adapter from the Mini and THEN do Scroll Lock-Scroll Lock 2. The KVM then switches, and I can plug back in. Everything works fine after that. It gets cumbersome though if you want to switch seamlessly between the two.
I only use the KVM for the KM part these days since my monitor (Samsung 930b 19" LCD) is able to switch between DVI and VGA by itself. And since I'm using the Windows box mostly for gaming these days, I use the DVI with the PC and the VGA with the Mac. The KVM was able to handle it without any distortion when I ran VGA on both of them. To the best of my knowledge, there isn't a cost-effective DVI KVM switch out there yet. I could be wrong.

Mini won't boot when VGA is attached to KVM -- help!

My mini (Core Duo 1.86MHz, all updates installed) is attached to a Belkin Pro2 4-port KVM (F1DA104T). I've read comments about issues with KVMs being picky with the mini, but the mini won't even completely boot when the VGA cable is attached. I've used this KVM with other 10.4 Macs in the past (G3's, G4's), so I didn't expect problems. The monitor is a Dell 17" LCD (E173FP), which is fine when attached directly to the mini. I've also tried another LCD (different manufacturer) with same results.
The mini boots and I first see the gray screen with the Apple logo, followed by a light blue screen, and that's it. The finder never comes up, and I can't even SSH or VNC into it -- just the blue screen. Once I remove the VGA cable (only video - the keyboard and mouse are both still connected), it will complete the boot and launch the finder. If I boot with no display attached, or attached directly to the LCD w/o the KVM in the path, but then attach the mac to the KVM, I see the display for about two seconds, and then the monitor heads into power save mode. When I VNC into the mini to see what's going on, it's detecting two different displays; when the cable is attached but the KVM isn't on the mac's channel, it's one thing. When I switch over to the mac's channel, it's like I'm plugging in a different display. In any case, the computer is putting out 1024x768x60Hz, which is well within the specs of the monitor and KVM.
I installed SwitchresX and under VNC retrieved the DDC info. Here's what I have for when it's plugged into the KVM and on channel:
DDC block report generated by SwitchResX for display
VGA/SVGA Display
0 1 2 3 4 5 6 7 8 9 A B C D E F
0 | 00 FF FF FF FF FF FF 00 00 00 00 00 00 00 00 00
1 | 0A 0A 01 01 0C 1E 17 BE E8 2D C9 A0 57 47 98 27
2 | 12 48 4C 00 00 00 01 01 01 01 01 01 01 01 01 01
3 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
4 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
5 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
6 | 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01 01
7 | 01 01 01 01 01 01 00 00 00 00 00 00 00 00 00 20
Valid DDC block: checksum passed
EDID Version........1.1
Manufacturer........@@@
Product Code........0 (0000) (0000)
Serial Number.......0
Manufactured........Week 10 of year 2000
Max H Size..........30 cm
Max V Size..........23 cm
Gamma...............2.90
DPMS Supported Features:
Active off Suspend Standby
Display type:
RGB color display
</pre>
So far, I'm stumped. This is a $200+ KVM, supposedly better than many of the cheapies, with listed Mac compatibility. Neither Apple nor Belkin wants to take ownership for this problem. If anyone has any tips on where to look next, I'd be very grateful!
Thanks!
Jeff

Hi BSteely,
Thanks for taking the time to look into this.
The blue screen I see is definitely not being generated by the LCD - it's coming from the Mac. It's coming up just after the gray Apple logo you see when booting. Normally you'd next see the finder pop up, but that never happens as long as the KVM is plugged into the mac (and it's only the VGA connection which is doing this, since the same thing happens with the keyboard/mouse unplugged from the mac). Once I remove the VGA cable, it continues to boot normally. If I hookup the LCD directly to the mac, it also boot normally.
Sorry I wasn't clear about VNC. I'm not seeing two displays at once, I'm seeing two different displays -- one when the kvm is on the mac's channel, and another when it switches away. Funny enough, I'm getting MORE resolution choices when I'm not on channel. The DDC info I posted above is for when I'm on channel.
Jeff

I am trying to setup kvm. Am I on the right track?

I am trying to set up kvm and am a bit confused (probably by old information)
lscpu
Virtualization: AMD-V
L1d cache: 16K
L1i cache: 64K
L2 cache: 2048K
L3 cache: 8192K
NUMA node0 CPU(s): 0-5
grep -E "(vmx|svm|0xc0f)" --color=always /proc/cpuinfo
Worked
zgrep CONFIG_KVM /proc/config.gz
CONFIG_KVM_GUEST=y
# CONFIG_KVM_DEBUG_FS is not set
CONFIG_KVM_APIC_ARCHITECTURE=y
CONFIG_KVM_MMIO=y
CONFIG_KVM_ASYNC_PF=y
CONFIG_KVM_VFIO=y
CONFIG_KVM=m
CONFIG_KVM_INTEL=m
CONFIG_KVM_AMD=m
CONFIG_KVM_MMU_AUDIT=y
CONFIG_KVM_DEVICE_ASSIGNMENT=y
zgrep CONFIG_VIRTIO /proc/config.gz
CONFIG_VIRTIO_BLK=m
CONFIG_VIRTIO_NET=m
CONFIG_VIRTIO_CONSOLE=m
CONFIG_VIRTIO=m
CONFIG_VIRTIO_PCI=m
CONFIG_VIRTIO_BALLOON=m
CONFIG_VIRTIO_MMIO=m
CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES=y
lsmod | grep kvm
kvm_amd 59131 0
kvm 413027 1 kvm_amd
lsmod | grep virtio
[virtio_pci 17389 0
virtio_balloon 12997 0
virtio_scsi 17714 0
virtio_blk 17295 0
virtio_net 26460 0
virtio_ring 17342 5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_scsi
virtio 13058 5 virtio_blk,virtio_net,virtio_pci,virtio_balloon,virtio_scsi
scsi_mod 142915 4 libata,sd_mod,sr_mod,virtio_scsi
Is there any thing else that needs to be set up before I install virt-manager
Confused?
thanks
Dave
Last edited by spottyrover (2014-09-10 04:08:08)

1. tags around your raw output!1. [ code ] tags around your raw output! 1.
Looks pretty now. Always wondered how that was done
2. Did you deplete the usefulness of https://wiki.archlinux.org/index.php/KVM to its entirety?
that is what I am trying to follow.
Is there more modules needed?
Did it work correctly?
It lacks information on how to add modules.
I got it working the first time by following multiple how tos and in the end I do not know which bits I done was needed and which bits was not and they did.
By the way. You did not answer the question.
Am I on the right track?
After all I am in the newbie corner
Dave
Last edited by spottyrover (2014-09-10 04:28:24)

Mac Pro keeps crashing when using with KVM. where to start my investigation

hi guys.
i have recently ordered ATEN CS-1762 KVM switch (2 ports model) to control my Mac and PC with a single keyboard and mouse. This KVM supports USB and DVI. the problem i have is Mac crashing when i switch from PC. I contacted mfg lately and they are unaware of this issue due to not having Mac Pro to test with this appliance. They have tested it with Mac Mini, G4 and G5 though and all was OK. based on this they put a description that this box is compatible with Mac. Anyway, being relatively new Mac user i ask for your help.
here are my steps and some ATEN's thoughts:
1. accroding to ATEN tech support, i should power up my second computer after the first one was started and is running. firstly i start the Mac Pro, 5 mins after that i power up my PC.
2. When both computers are up and running (Mac is in KVM focus), i switch to PC and all seems OK. I have noticed though that if NumLock is activated during the PC session, I won't be able to switch back to Mac. However, even though NumLock is OFF i still may have troubles when switching back to Mac. So it is not the rule, but maybe the clue to start with..
NOTES:
1. if i start PC first, Mac won't start at all. The power led will be on, but there will be no picture on the monitor and it won't accept any keyboard/mouse inputs as well as it will be network inaccessible.
2. I tried looking into Mac's logs but need your help in getting this clear.
here is the log. as you will see it stops at 13:04 and then continues at 13:08 after reboot.
i've seen some parallel's VMs but i don't have Parallels installed. i used to have it, but then it never happened to work so i deleted it from the machine. can this be the case it is still somewhere?
pls guys, any thoughts are very welcome!!!
PS: i can cause Mac to crash the same way if necessary or if log looks inclomplete. the thing forgot to mention is: when Mac crashes and i reboot it, it will not necessarily boot up completely. i've noticed that i would have to reset the KVM switch prior to Mac's successful start up. so maybe i copied the wrong log (not the one immediately after the crash). pls advise here
Alex
EDIT: specs for machines are:
Mac Pro dual 2.6GHz, 1GB (+1GB aftermarket added half a year back, works perfectly), HDD 260GB, Nvidia 7300 256Mb.
PC - Supermicro dual xeon 1.6GHz, 4GB Ram, 4 x 36GB SCSI, Nvidia 5200 256 MB with Windows 2000 Server.
Apr 18 13:03:38 localhost kernel[0]: hi mem tramps at 0xffe00000
Apr 18 13:03:38 localhost kernel[0]: PAE enabled
Apr 18 13:03:38 localhost kernel[0]: 64 bit mode enabled
Apr 18 13:03:38 localhost kernel[0]: standard timeslicing quantum is 10000 us
Apr 18 13:03:38 localhost kernel[0]: vmpagebootstrap: 512109 free pages
Apr 18 13:03:38 localhost kernel[0]: migtable_maxdispl = 71
Apr 18 13:03:38 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 18 13:03:38 localhost kernel[0]: 77 prelinked modules
Apr 18 13:03:38 localhost kernel[0]: ACPI CA 20060421
Apr 18 13:03:38 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=2 LocalApicId=7 Enabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=3 LocalApicId=6 Enabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=4 LocalApicId=0 Disabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=5 LocalApicId=0 Disabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=6 LocalApicId=0 Disabled
Apr 18 13:03:38 localhost kernel[0]: AppleACPICPU: ProcessorApicId=7 LocalApicId=0 Disabled
Apr 18 13:03:38 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Apr 18 13:03:38 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Apr 18 13:03:38 localhost kernel[0]: using 10485 buffer headers and 4096 cluster IO buffer headers
Apr 18 13:03:38 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 18 13:03:38 localhost kernel[0]: Started CPU 01
Apr 18 13:03:38 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 18 13:03:38 localhost kernel[0]: Started CPU 02
Apr 18 13:03:38 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Apr 18 13:03:38 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Apr 18 13:03:38 localhost kernel[0]: Started CPU 03
Apr 18 13:03:38 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Apr 18 13:03:38 localhost kernel[0]: Security auditing service present
Apr 18 13:03:38 localhost kernel[0]: BSM auditing present
Apr 18 13:03:38 localhost kernel[0]: disabled
Apr 18 13:03:38 localhost kernel[0]: rooting via boot-uuid from /chosen: BE5A00F3-0C3D-4125-9DE4-3F2193D3DAA8
Apr 18 13:03:38 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Apr 18 13:03:38 localhost kernel[0]: USB caused wake event (EHCI)
Apr 18 13:03:38 localhost kernel[0]: FireWire (OHCI) TI ID 8025 built-in now active, GUID 0016cbfffe6cfb5c; max speed s800.
Apr 18 13:03:38 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT0 @0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST3160812AS P Media/IOGUIDPartitionScheme/Customer@2
Apr 18 13:03:38 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Apr 18 13:03:38 localhost kernel[0]: jnl: replay_journal: from: 3560448 to: 7934976 (joffset 0x48b341000)
Apr 18 13:03:38 localhost kernel[0]: HFS: Removed 9 orphaned unlinked files
Apr 18 13:03:38 localhost kernel[0]: Jettisoning kernel linker.
Apr 18 13:03:38 localhost kernel[0]: Resetting IOCatalogue.
Apr 18 13:03:38 localhost kernel[0]: PXS1: family specific matching fails
Apr 18 13:03:38 localhost kernel[0]: Matching service count = 1
Apr 18 13:03:38 localhost kernel[0]: Matching service count = 2
Apr 18 13:03:38 localhost kernel[0]: Matching service count = 2
Apr 18 13:03:38 localhost kernel[0]: Matching service count = 2
Apr 18 13:03:38 localhost kernel[0]: Matching service count = 2
Apr 18 13:03:38 localhost kernel[0]: Matching service count = 2
Apr 18 13:03:38 localhost kernel[0]: NVDANV40HAL loaded and registered.
Apr 18 13:03:38 localhost kernel[0]: PXS1: family specific matching fails
Apr 18 13:03:38 localhost kernel[0]: Previous Shutdown Cause: 3
Apr 18 13:03:38 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Apr 18 13:03:38 localhost mDNSResponder-108.4 (Jan 8 2007 20: 39:46)[30]: starting
Apr 18 13:03:38 localhost memberd[38]: memberd starting up
Apr 18 13:03:38 localhost DirectoryService[42]: Launched version 2.1 (v353.6)
Apr 18 13:03:39 localhost lookupd[44]: lookupd (version 369.6) starting - Wed Apr 18 13:03:39 2007
Apr 18 13:03:39 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:01:63:16
Apr 18 13:03:39 localhost configd[34]: No AirPort Driver found.
Apr 18 13:03:39 localhost kernel[0]: AppleIntel8254XEthernet: Ethernet address 00:17:f2:01:63:17
Apr 18 13:03:39 localhost diskarbitrationd[37]: disk0s2 hfs FDAB59BA-2B84-3AD5-AF66-4BD8CFA20261 Macintosh HD /
Apr 18 13:03:40 localhost lookupd[55]: lookupd (version 369.6) starting - Wed Apr 18 13:03:40 2007
Apr 18 13:03:42 localhost kernel[0]: Intel8254x -- Link Up -- 00:17:f2:01:63:16 -- called by interruptOccurred() --
Apr 18 13:03:42 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Apr 18 13:03:42 localhost kernel[0]: -- Auto-Neg Advertise Reg (04d) = 0xde1, Link Partner Ability Reg (05d) = 0x41e1, Gig Advertise Reg (09d) = 0xe00, Gig Link Partner Ability Reg (10d) = 0x4000
Apr 18 13:03:42 localhost mDNSResponder: Adding browse domain local.
Apr 18 13:03:43 localhost loginwindow[62]: Login Window Started Security Agent
Apr 18 13:03:46 localhost kernel[0]: Intel8254x -- Link down -- 00:17:f2:01:63:17 -- called by enableHardware() --
Apr 18 13:03:46 localhost kernel[0]: -- Auto-Neg Advertise Reg (04d) = 0xde1, Link Partner Ability Reg (05d) = 0x0, Gig Advertise Reg (09d) = 0xe00, Gig Link Partner Ability Reg (10d) = 0x4000
Apr 18 13:03:46 Alexs-Computer configd[34]: setting hostname to "Alexs-Computer.local"
Apr 18 13:03:46 Alexs-Computer TabletDriver[71]: RunApplication called while eRelaunching
Apr 18 13:03:52 Alexs-Computer configd[34]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Apr 18 13:03:52 Alexs-Computer configd[34]: posting notification com.apple.system.config.network_change
Apr 18 13:03:52 Alexs-Computer lookupd[82]: lookupd (version 369.6) starting - Wed Apr 18 13:03:52 2007
Apr 18 13:03:52 Alexs-Computer ntpdate[94]: can't find host time.euro.apple.com\n
Apr 18 13:03:52 Alexs-Computer ntpdate[94]: no servers can be used, exiting
Apr 18 13:03:55 Alexs-Computer configd[34]: target=enable-network: disabled
Apr 18 13:04:15 Alexs-Computer configd[34]: posting notification com.apple.system.config.network_change
Apr 18 13:04:15 Alexs-Computer lookupd[148]: lookupd (version 369.6) starting - Wed Apr 18 13:04:15 2007
Apr 18 13:04:15 Alexs-Computer SystemStarter[41]: "/Library/StartupItems/Tablet" failed security check: permissions
Apr 18 13:04:17 Alexs-Computer kernel[0]: Parallels Workstation Hypervisor started.
Apr 18 13:04:17 Alexs-Computer kernel[0]: Parallels Workstation VMM Main driver started.
Apr 18 13:04:18 Alexs-Computer kernel[0]: comparallels_kextPvsvnic: Ethernet address 00:01:23:45:67:89
Apr 18 13:04:19 Alexs-Computer SystemStarter[41]: Parallels VirtualMachine drivers (149) did not complete successfully
Apr 18 13:08:25 localhost kernel[0]: hi mem tramps at 0xffe00000
Apr 18 13:08:25 localhost kernel[0]: PAE enabled
Apr 18 13:08:25 localhost kernel[0]: 64 bit mode enabled
here couple more logs right at the moment of crash (found in paic.log). hopefully then can shed som elight on the troubles:
pls advise
Wed Apr 18 13:04:16 2007
panic(cpu 0 caller 0x001A429B): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00004000, CR3: 0x01019000, CR4: 0x000006e0
EAX: 0x23a3d578, EBX: 0x00000000, ECX: 0x00001000, EDX: 0x00004000
CR2: 0x00004000, EBP: 0x2544bc18, ESI: 0x23a3d578, EDI: 0x00004000
EFL: 0x00010206, EIP: 0x0019637c, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x2544b9d8 : 0x128d08 (0x3cb134 0x2544b9fc 0x131de5 0x0)
0x2544ba18 : 0x1a429b (0x3d0e4c 0x0 0xe 0x3d0670)
0x2544bb28 : 0x19ada4 (0x2544bb40 0x23a39578 0x2544bb98 0x84ae50)
0x2544bc18 : 0x84b148 (0x23a39000 0x2 0x2544bc68 0x1a1738)
0x2544bc38 : 0x8393d4 (0x2544bddc 0x0 0x2544bc68 0x4b0000)
0x2544bd18 : 0x6ca33a (0x23a39000 0x2544bdaa 0x2544bdaa 0x84)
0x2544bd78 : 0x6be697 (0x3c34000 0x2544bdaa 0x2544bdaa 0x84)
0x2544bdf8 : 0x6a72e3 (0x3c34000 0x1 0x2544be48 0x1a1738)
0x2544be18 : 0x6aee4a (0x553f8000 0x0 0x3ff96a27 0x3d87)
0x2544be78 : 0x546b55 (0x3c34000 0x2544beac 0x1 0x1a26ce)
0x2544bec8 : 0x54a1d0 (0x3a21e00 0x3 0x3f60ddf8 0x3d87)
0x2544bee8 : 0x54bc8d (0x3a21e00 0x7abf 0x5cbd220 0x5cbd160)
0x2544bf28 : 0x39c536 (0x3a21e00 0x3a40280 0x8 0x2)
0x2544bf78 : 0x13d7d9 (0x3a40280 0x3a87e78 0x0 0x0)
0x2544bfc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x397fcec) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(4.5.2)@0x6c9000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5e0000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.5)@0x69f000
dependency: com.apple.iokit.IONDRVSupport(1.4.5)@0x6ba000
com.apple.iokit.IONDRVSupport(1.4.5)@0x6ba000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5e0000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.5)@0x69f000
com.apple.iokit.IOGraphicsFamily(1.4.5)@0x69f000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5e0000
com.apple.iokit.IOHIDFamily(1.4.10)@0x531000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386
Wed Apr 18 17:06:26 2007
panic(cpu 1 caller 0x001A429B): Unresolved kernel trap (CPU 1, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x00004000, CR3: 0x01019000, CR4: 0x000006e0
EAX: 0x23a4d578, EBX: 0x00000000, ECX: 0x00001000, EDX: 0x00004000
CR2: 0x00004000, EBP: 0x25443c18, ESI: 0x23a4d578, EDI: 0x00004000
EFL: 0x00010206, EIP: 0x0019637c, CS: 0x00000008, DS: 0x04080010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x254439d8 : 0x128d08 (0x3cb134 0x254439fc 0x131de5 0x0)
0x25443a18 : 0x1a429b (0x3d0e4c 0x1 0xe 0x3d0670)
0x25443b28 : 0x19ada4 (0x25443b40 0x23a49578 0x1 0x4065004)
0x25443c18 : 0x84b148 (0x23a49000 0x2 0x25443c48 0x713bbf)
0x25443c38 : 0x8393d4 (0x25443ddc 0x0 0x25443c68 0x7116c2)
0x25443d18 : 0x6ca33a (0x23a49000 0x25443daa 0x25443daa 0x84)
0x25443d78 : 0x6be697 (0x3c61c00 0x25443daa 0x25443daa 0x84)
0x25443df8 : 0x6a72e3 (0x3c61c00 0x2 0x25443e28 0x1e)
0x25443e18 : 0x6aee4a (0x523e0000 0x0 0xfd8e30e2 0xc93)
0x25443e78 : 0x546b55 (0x3c61c00 0x25443eac 0x2 0x1a26ce)
0x25443ec8 : 0x54a1d0 (0x3a21e00 0x3 0xfcf5a332 0xc93)
0x25443ee8 : 0x54bc8d (0x3a21e00 0x1917 0x4336be0 0x4336b20)
0x25443f28 : 0x39c536 (0x3a21e00 0x3a40280 0x8 0x2)
0x25443f78 : 0x13d7d9 (0x3a40280 0x3a39ff8 0x0 0x3303)
0x25443fc8 : 0x19ac1c (0x0 0x0 0x19e0b5 0x5cb2144) Backtrace terminated-invalid frame pointer 0x0
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(4.5.2)@0x6c9000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5e0000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.5)@0x69f000
dependency: com.apple.iokit.IONDRVSupport(1.4.5)@0x6ba000
com.apple.iokit.IONDRVSupport(1.4.5)@0x6ba000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5e0000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.5)@0x69f000
com.apple.iokit.IOGraphicsFamily(1.4.5)@0x69f000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x5e0000
com.apple.iokit.IOHIDFamily(1.4.10)@0x531000
Kernel version:
Darwin Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007; root:xnu-792.18.15~1/RELEASE_I386

ok so i experimented a little with the hardware and here what i have to the moment:
1. i thought that the usb kb could be the case for mac os to crash so i disconnected the cable from the KVM and plugged normal apple kb to the mac.
2. however when i tried switching back to mac, the machine crashed again.
from what i noticed for the last few days 'working' with this kvm switch was the screen resolution changing while i was switching. meaning the screen flickered for couple of times prior to showing 1280x1024 that was set up in the system. during flickering the resoution became 1024x768. i 've seen it pretty clearly, just it was for half of a second.
also when powering up both machines, they were starting with 1024x768 and not 1280x1024 as was set up. i had to manually change the screen resolution on both machines (pc and mac) every time after successful start up.
so by far my understanding is that kvm switch forces monitor for 1024x768 during switches and on start up. it also causes the OSes (win2K and MacOSX) to lose 1280x1024 and accept 1024x768 as if the monitor was changed and couldn't operate at a higher resolution.
having said that i uploaded this info to kvm mfg (ATEN) and couple more mac forums so that this info may help someone else when ordering a kvm for mac. at the same time i am still open for any thoughts, advices and crazy ideas to get round this bug.
alex

How to use multiple closed MBPs with KVM?

I have an unusual problem I'd eagerly welcome help with:
I have four MacBook Pros (from 2006-2010) that I use in my day-to-day work, since each of them can run an instance of the client software I work on.
As you imagine, this consumes a fair amount of desk space having them side-by-side, as well as the seeming redundancy of having each one's screen showing, since I actually only need to focus on one at a time (commanding it to do tasks I can background for awhile). In addition, I prefer to use the mouse over the trackpad whenever possible.
So I had an inspired idea: I read that you can run a MBP in closed clamshell mode while hooked to an external display. That got me thinking, hmmm, what if I stacked these MBPs in one pile and connected them all to a 4-port KVM, so I could share a monitor, keyboard, and mouse among them?
Then I saw the prices of some 4-port KVMs, and they get fairly pricey, so I'd like to learn from others' experiences on the following specific questions:
Are there heat issues I need to be concerned about? The software I work with tends to ramp up a MBP's fans pretty loud.
Are there KVMs that are known to work best with this config? Some seem more Mac-friendly than others but the ones I'm looking at (Gefen, IOGear) all get mixed reviews thus far. 4 computers sharing 1 DVI display + USB keyboard and mouse seems fine, as 4 sharing 2 seems to jack up the price a lot more, and I don't have a specific need for two monitors.
I've previously gleaned some info about MBPs with KVMs, but haven't come across a setup like the one I'm suggesting. Thanks so much in advance!

I'd say that you ought to look at using class and id attributes in your table elements.
If you have two tables and want seperate color schemes use an id on the <table> element. Then you can select that table in your CSS quite easily.
<table id="greenScheme">
<table id="blueScheme">
#greenScheme tr {
One set of rules here
#blueScheme tr {
Another set of rules here
I don't/haven't used tables that much myself so don't feel confident about writing out some sample CSS for you here. However, it shouldn't be too difficult to work out. Also, I did a fancy table not long ago to put up a price table in a site. A quick google on something like style tables CSS will bring up plenty of tutorial type stuff on styling tables that won't be too arduous.
Martin
Tricia0131 wrote:
searched this site and found this question many times, but all answers suggest how to do it in CSS code.
That might be because it's the best way to do it ;-)

I have 2 old computers(both XP) now connected with a KVM switch, both have same version of FF (11.0) but different profiles, bookmarks & addons. How can easily I make them both the same?

#2 has many years of bookmarks and profiles, #1 is only 3 months old. I would like them both to run the same add-ons and have same profiles. How can I integrate the old to the new and the new to the old? Both are up and running fine. I got the KVM because one has MS Office 7, but couldn't afford to put it on the other one. They also both connect wirelessly to the router which is in the next room (my brother's as he's a gamer and needs a faster connection), so they aren't set up as a regular network although I log on with a password. I'd like to be able to put the entire profile once integrated on a flash drive. Thanks.

Firefox '''Sync''' can synchronize your Profiles. <br />
https://support.mozilla.com/en-US/kb/what-firefox-sync

Can't boot virtio-guest with KVM since kvm-86

Hello,
since kvm-86 I can't boot a Debian Lenny guest machine. When I boot the machine I get the following error:
[ 4.117315] request_module: runaway loop modprobe binfmt-a6e0
[ 4.119330] request_module: runaway loop modprobe binfmt-a6e0
[ 4.121357] request_module: runaway loop modprobe binfmt-a6e0
[ 4.123321] request_module: runaway loop modprobe binfmt-a6e0
[ 4.125318] request_module: runaway loop modprobe binfmt-a6e0
[ 134.220057] INFO: task run-init:1 blocked for more than 120 seconds.
[ 134.221809] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 134.224125] run-init D 00000003 0 1 0
[ 134.225588] d7c3f8a0 00000082 d7c3f8a0 00000003 f4c7cbb7 00000000 d7c3fa2c 00000001
[ 134.228196] 00000000 7fffffff d7c41ef0 d7c41edc 00000002 c02a61ab 00000000 d7c4bfbc
[ 134.230567] d7c133bc c0115f16 00000000 00000003 d7c133c8 d7c133c8 00000002 00000000
[ 134.233429] Call Trace:
[ 134.234227] [<c02a61ab>] schedule_timeout+0x13/0x86
[ 134.235780] [<c0115f16>] __wake_up_common+0x2d/0x52
[ 134.237320] [<c011918a>] __wake_up+0x27/0x38
[ 134.238596] [<c02a5c2f>] wait_for_common+0xa3/0xfd
[ 134.240132] [<c0117195>] default_wake_function+0x0/0x5
[ 134.241734] [<c0126e90>] call_usermodehelper_exec+0x57/0x96
[ 134.243493] [<c0127120>] request_module+0xcc/0xdc
[ 134.244775] [<c016869a>] get_arg_page+0x2a/0x79
[ 134.246263] [<c0168a83>] search_binary_handler+0x169/0x17c
[ 134.248025] [<c0169807>] do_execve+0x12b/0x1b6
[ 134.249406] [<c0102138>] sys_execve+0x2a/0x49
[ 134.250763] [<c01037b2>] syscall_call+0x7/0xb
I tried to reinstall the machine, but during the install process the installer isn't able to create a swap partition. Later, I got the error message "stale NFS file handle" at the console (I don't do anything with nfs here). Same errors with kvm-87 and 88.
I tried to install other distros, but any of them failed to install on the virtio disk one way or another.
Everything works with kvm-84. With kvm-85 libvirt (which I am using) wasn't able to boot from a virtio disk. Note that libvirt has nothing to do with the error/bug described above. This happens since kvm-86 with plain kvm started from the command line, too.
I am switching back to kvm-84 for now.
To reproduce:
Get a Debian Lenny qemu/KVM image and virtio disk and try to boot it. Or try to install Debian Lenny on a virtio disk. There were other errors with other Distros, so I suspect that there is somesthing wrong with kvm since 86.
# uname -r
2.6.30-ARCH
# lsmod|grep kvm
kvm_amd
kvm
/proc/cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 15
model : 75
model name : AMD Athlon(tm) 64 X2 Dual Core Processor 4600+
stepping : 2
cpu MHz : 2400.299
cache size : 512 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp lm 3dnowext 3dnow extd_apicid pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy
bogomips : 4802.62
clflush size : 64
power management: ts fid vid ttp tm stc
Last edited by haary (2009-08-12 23:34:59)

I am also having the same problem, the host is Archlinux with kvm-88 on 64bit, I am going to try aur and see how it goes when I get home.
There is no updated aur package so downgrade it is.
KVM 84 didn't work YES!!!
Last edited by mthode (2009-08-18 02:01:22)

KVM switch and Mavericks don't play well together

I upgraded to Mavericks yesterday, and started having this very annoying problem with my KVM switch, which used to work fine with Mountain Lion. I've been using this KVM switch for my mac mini and PC, in order to share my keyboard and mouse, very stably for several months.
Basically, when switching back and forth, there is a chance that ALL the peripheral devices would stop working in Mavericks. This includes my apple bluetooth keyboard and the magic touchpad, which are not related with USB (or maybe the bluetooth chip is still hooked up via USB inside).
For some reason, screen sharing stops working too, althought the IP I was trying to connect to was the ethernet port.
If I try to do a shutdown -r now via SSH, the system tries to shut itself down, but would get stuck with a spinning animation on the screen.
There is nothing in the system log, no error message.
My KVM switch is an IOGear GCS42UW6. Connected USB devices are: Apple USB keyboard and Logitech G500 mouse.

10.8 worked well with my Mac Mini (2009) connected to IOGEAR KVM model GCS1108. My mouse is from Redmond and the keyboard is a Goldtouch.
Mavericks has a problem with my KVM switch as well. It seems to be a USB problem.
Case 1: The Mini's video is connected to the KVM switch -- mini DVI port to DVI. If the KVM USB cable (known good) is connected, the Mini chimes at boot but no grey Apple logo appears. LCD remains blank white. Boot does not progress.
Case 2: The Mini's video is connected to the KVM switch, as before. If the KVM USB cable is NOT connected, the Mini chimes at boot, the grey logo appears, and boot proceeds normally. Video is fine. I then connect the KVM USB cable to the Mini and use keyboard and mouse. KVM switching works as expected.
If the KVM USB cable is NOT connected but a keyboard and mouse are connected directly to the Mini, the boot sequence is normal. Video works.
The problem is not the hardware, all of which worked well with 10.8 (Mountain Lion). I would downgrade if Apple made 10.8 available from the App Store.

KVM VGA-Passthrough using the new vfio-vga support in kernel = 3.9

This is intented for people who wish to pass-through a GPU to a virtual machine using the KVM hypervisor, QEMU and vfio-pci
NOTE: AMD RADEON 5xxx, 6xxx, 7xxx, 2xx and NVIDIA GEFORCE 7, 8, 4xx, 5xx, 6xx, 7xx 9xx have been reported working with this, passing though an intel IGD is not supported YET
NOTE: THIS IS EXPERIMENTAL SO IT MIGHT NOT WORK ON YOUR SYSTEM
This is the result on my radeon 6950:
This is the result on my geforce 470 gtx:
Recommended reads
Alex Williamson's blog and FAQ for detailed technical information
OVMF whitepaper.
GPU passthrough database by noctavian
At this moment there are two ways to achieve this using KVM: legacy VGA via Seabios or non-VGA (UEFI) via OVMF
The main practical advantage of using OVMF is that on intel systems you no longer need the i915 VGA arbiter patch which also disables DRI on the host
Requirements
AMD-VI/VT-D enabled and working (On intel systems both your MB and you CPU must support it, to find out if you CPU has VT-D support go here: http://ark.intel.com/, you also need to boot with intel_iommu=on to enable it)
At least 2 GPU's, one primary boot device and the card you wish to pass-through
Qemu=>2.0
Aditional kernel patches might be required if you're using an Intel CPU: ACS override patch and i915 VGA arbiter patch, you can find a kernel package with these patches included on AUR: linux-vfio
Aditional requirements for OVMF:
An UEFI compatible GPU (Most modern gpus support this, SEE: Does my graphics card ROM support EFI?
An UEFI compatible GUEST (ex: Windows 7 and up)
OVMF: Gerd Hoffmann's rpms or OVMF-svn from AUR
If you're building your kernel manually this option is required:
CONFIG_VFIO_PCI_VGA=y
Preparing your System
On intel system the i915 VGA arbiter patch is required if:
You're using the IGD on your host
You're doing VGA assignment
NOTE: Enabling this will disable DRI!
If you wish to avoid this, then then you should try OVMF
To enable it add this kernel parameter to your bootloader:
i915.enable_hd_vgaarb=1
Next, we need to prepare the GPU for vfio:
Blacklist radeon or nouveau or nvidia or fglrx on /etc/modprobe.d/blacklist.conf
Example, blacklisting the opensource radeon module:
echo "blacklist radeon" >> /etc/modprobe.d/blacklist.conf
Use pci-stub
In my case since i have 2 radeon cards blacklisting the radeon module is not an option, so i use pci-stub
NOTE: If pci-stub was built as a module, you'll need to modify /etc/mkinitcpio.conf and add pci-stub in the MODULES section, after that you need to update your initramfs like this
mkinitcpio -p linux-mainline
lspci
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] <-- radeon 6950
07:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] <-- radeon 6950 audio
lspci -n
07:00.0 0300: 1002:6719 <-- radeon 6950
07:00.1 0403: 1002:aa80 <-- radeon 6950 audio
Now add this kernel parameter to your bootloader:
pci-stub.ids=1002:6719,1002:aa80
dmesg | grep pci-stub
[ 2.096151] pci-stub: add 1002:6719 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 2.096160] pci-stub 0000:07:00.0: claimed by stub
[ 2.096165] pci-stub: add 1002:AA80 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
[ 2.096174] pci-stub 0000:07:00.1: claimed by stub
[ 2.096178] pci-stub: add 1B21:1042 sub=FFFFFFFF:FFFFFFFF cls=00000000/00000000
Setting up vfio and kvm modules
This is only required if you get this message:
vfio_iommu_type1_attach_group: No interrupt remapping support. Use the module param "allow_unsafe_interrupts" to enable VFIO IOMMU support on this platform
If your board doesn't enable interrupt remapping, you need to add this to your bootloader:
vfio_iommu_type1.allow_unsafe_interrupts=1
Or if vfio-pci was built as a module ( default on arch )
echo "options vfio_iommu_type1 allow_unsafe_interrupts=1" > /etc/modprobe.d/vfio_iommu_type1.conf
Some applications like Passmark Performance Test and SiSoftware Sandra crash the VM without this:
echo "options kvm ignore_msrs=1" >> /etc/modprobe.d/kvm.conf
Binding a device to vfio-pci
We'll use this script to make life easier:
#!/bin/bash
modprobe vfio-pci
for dev in "$@"; do
vendor=$(cat /sys/bus/pci/devices/$dev/vendor)
device=$(cat /sys/bus/pci/devices/$dev/device)
if [ -e /sys/bus/pci/devices/$dev/driver ]; then
echo $dev > /sys/bus/pci/devices/$dev/driver/unbind
fi
echo $vendor $device > /sys/bus/pci/drivers/vfio-pci/new_id
done
Save it as /usr/bin/vfio-bind
chmod 755 /usr/bin/vfio-bind
Bind the GPU and GPU audio:
vfio-bind 0000:07:00.0 0000:07:00.1
Systemd service:
[Unit]
Description=Binds devices to vfio-pci
After=syslog.target
[Service]
EnvironmentFile=-/etc/vfio-pci.cfg
Type=oneshot
RemainAfterExit=yes
ExecStart=-/usr/bin/vfio-bind $DEVICES
[Install]
WantedBy=multi-user.target
cat /etc/vfio-pci.cfg
DEVICES="0000:00:11.0 0000:04:00.0 0000:05:00.0 0000:06:00.0 0000:07:00.0 000:07:00.1"
Testing if its working out
Seabios:
qemu-system-x86_64 -enable-kvm -m 1024 -cpu host,kvm=off \
-smp 4,sockets=1,cores=4,threads=1 \
-device vfio-pci,host=07:00.0,x-vga=on -device vfio-pci,host=07:00.1 \
-vga none
OVMF:
qemu-system-x86_64 -enable-kvm -m 1024 -cpu host,kvm=off \
-smp 4,sockets=1,cores=4,threads=1 \
-drive if=pflash,format=raw,readonly,file=/usr/share/ovmf/x64/ovmf_code_x64.bin \
-drive if=pflash,format=raw,file=/usr/share/ovmf/x64/ovmf_vars_x64.bin \
-device vfio-pci,host=07:00.0 -device vfio-pci,host=07:00.1 \
-vga none
Note:
kvm=off will hide the kvm hypervisor signature, this is required for NVIDIA cards, since its driver will refuse to work on an hypervisor and result in Code 43 on windows (unless you're using a QUADRO)
x-vga=on is required for vga assignment
-vga none disables the default vga device on QEMU, it is also required for vga assignment
You should see a black qemu window on your main display, and seabios/ovmf ouput on your monitor from your passthru'd card saying it cant find anything to boot
If you're using an intel cpu and nothing happens try this:
modprobe -r kvm_intel
modprobe kvm_intel emulate_invalid_guest_state=0
NOTE: There might be some problems using nvidia/fglrx/nouveau drivers on the host gpu, see the ISSUES section below on how to solve this
At this point you're ready to create your vm, you could use libvirt + virt-manager to create your vm using a nice graphical interface, there are
also some interesting examples in this thread, otherwise if you prefer to use the command line continue reading
DISK:
Creating a disk image:
Create a 30Gb raw image:
dd if=/dev/zero of=windows.img bs=1M seek=30000 count=0
Using a VIRTIO controller:
We create our virtio controller for qemu:
-device virtio-scsi-pci,id=scsi
Attaching our hdd:
-drive file=/home/nbhs/windows.img,id=disk,format=raw,if=none -device scsi-hd,drive=disk
Attaching a cdrom:
-drive file=/home/nbhs/windows.iso,id=isocd,if=none -device scsi-cd,drive=isocd
To install windows, you'll need to download the virtio drivers iso from here
Attaching the virtio iso:
-drive file=/home/nbhs/virtio.iso,id=virtiocd,if=none -device ide-cd,bus=ide.1,drive=virtiocd
Windows will complain it cant find a disk to install to, just click browse, find the folder for your os/arch, select "RED HAT VirtIO pass-through controller" then click next.
For more info check out the Archlinux wiki's QEMU section
Using a physical disk or partition:
-drive file=/dev/sdb,id=disk,format=raw,if=none -device scsi-hd,drive=disk
You might need to change the bus depending on the controller you use
If you wish to use a physical partition and be able to read its contents later on, you can follow these guides:
http://fds-team.de/cms/articles/2013-12 … yer-u.html
https://wiki.archlinux.org/index.php/QE … disk_image
Passing a sata disk controller to qemu:
If you dual boot like me you can pass an entire sata controller (in ahci mode) and all the drives attached, and seabios will boot from them.
lspci
00:11.0 SATA controller: Advanced Micro Devices [AMD] nee ATI SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)
Make sure all volumes are unmounted, then bind the controller to vfio:
vfio-bind 0000:00:11.0
Now we pass the controller to the vm:
-device vfio-pci,host=00:11.0
USB:
Its also possible to passthrough a usb controller, in my case an ASMEDIA USB3 Controller:
lspci
04:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
05:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
06:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
Bind them to vfio:
vfio-bind 0000:04:00.0 0000:05:00.0 0000:06:00.0
Pass them to the vm:
-device vfio-pci,host=04:00.0 \
-device vfio-pci,host=05:00.0 \
-device vfio-pci,host=06:00.0
Or a specific device:
lsusb
Bus 004 Device 010: ID 045e:00e1 Microsoft Corp. Wireless Laser Mouse 6000 Reciever <-- mouse
Bus 004 Device 011: ID 045e:074b Microsoft Corp. <-- keyboard
We pass them to the vm:
-usb -usbdevice host:045e:00e1 -usbdevice host:045e:074b
NETWORK:
Please see https://wiki.archlinux.org/index.php/QEMU#Networking
AUDIO EMULATION:
To hear the sound from the vm on your host speakers you'll need to add this lines:
-soundhw hda
You might need to start qemu like this:
QEMU_PA_SAMPLES=128 QEMU_AUDIO_DRV=pa qemu-system-x86_64...
alsa:
QEMU_ALSA_DAC_BUFFER_SIZE=512 QEMU_ALSA_DAC_PERIOD_SIZE=170 QEMU_AUDIO_DRV=alsa qemu-system-x86_64...
Note: these are the settings i found that work great on my system, if you get crackling/skipping audio you might want to try different settings
To see the available drivers and audio options:
qemu-system-x86_64 -audio-help
LOADING YOUR CARD ROM FROM A DUMP/FILE:
modify this line:
-device vfio-pci,host=07:00.0,...... \
change it to this:
-device vfio-pci,host=07:00.0,......,romfile=/path/to/your/gpu/bios.bin \
ISSUES:
Using the latest NVIDIA drivers on the guest will result in code 43, but there's a workarround
Using the latest NVIDIA drivers on the guest using hv enlightenments will result in code 43, see: https://forums.geforce.com/default/topi … 8/#4314318
Using AMD proprieraty drivers on the host, see: https://bbs.archlinux.org/viewtopic.php … 2#p1273412 the only solution atm is using the opensource radeon driver
PERFORMANCE IMPROVEMENTS:
SEE: https://bbs.archlinux.org/viewtopic.php … 1#p1270311
Pin vcpu to pcpu, see http://www.linux-kvm.com/content/tip-ru … cific-cpus
Use cgroups, specifically cpuset, see https://access.redhat.com/site/document … puset.html
Use Hugepages, see http://pic.dhe.ibm.com/infocenter/lnxin … ttunhp.htm
Use Hyper-V enlightenments, see: http://blog.wikichoon.com/2014/07/enabl … h-kvm.html
Last edited by nbhs (2015-04-05 20:01:18)

nbhs wrote:
apoapo wrote:
I finally got some progress.
After trying mainline kernel and with vbios, I went to bios/uefi and turned the Primary VGA card from onboard to pci-express ...
Now I see the seabios in passthroughed screen, but with blinking cursor in it, so i will try some things .
NIce! have you tried running windows with it yet? does it work if you dont load the rom file by hand?
Hi,
I tried it again and I captured this error message if I use the PCI-e card es Primary Card:
qemu-system-x86_64: -device vfio-pci,host=01:00.0,bus=root.1,addr=00.0,multifunction=on,x-vga=on: VFIO 0000:01:00.0 BAR 0 mmap unsupported. Performance may be slow
This was, when I got some seabios picture.
After some reboots I wanted to try it again, I was spammed with errors . Dont have them to show you now... will look for it.
Now I'm With the onboard as primary Card and I found this in dmesg:
[ 0.401391] DMAR: No ATSR found
[ 0.401412] IOMMU 0 0xfed90000: using Queued invalidation
[ 0.401413] IOMMU 1 0xfed91000: using Queued invalidation
[ 0.401415] IOMMU: Setting RMRR:
[ 0.401422] IOMMU: Setting identity map for device 0000:00:02.0 [0xbf800000 - 0xcf9fffff]
[ 0.402590] IOMMU: Setting identity map for device 0000:00:1d.0 [0xbd568000 - 0xbd59afff]
[ 0.402606] IOMMU: Setting identity map for device 0000:00:1a.0 [0xbd568000 - 0xbd59afff]
[ 0.402619] IOMMU: Setting identity map for device 0000:00:14.0 [0xbd568000 - 0xbd59afff]
[ 0.402628] IOMMU: Prepare 0-16MiB unity mapping for LPC
[ 0.402635] IOMMU: Setting identity map for device 0000:00:1f.0 [0x0 - 0xffffff]
[ 0.402717] PCI-DMA: Intel(R) Virtualization Technology for Directed I/O
[ 0.402782] ------------[ cut here ]------------
[ 0.402786] WARNING: at drivers/pci/search.c:46 pci_find_upstream_pcie_bridge+0x83/0x90()
[ 0.402787] Hardware name: To Be Filled By O.E.M.
[ 0.402788] Modules linked in:
[ 0.402790] Pid: 1, comm: swapper/0 Not tainted 3.9.2-1-mainline #1
[ 0.402791] Call Trace:
[ 0.402796] [<ffffffff81058090>] warn_slowpath_common+0x70/0xa0
[ 0.402797] [<ffffffff8105817a>] warn_slowpath_null+0x1a/0x20
[ 0.402799] [<ffffffff8129ea43>] pci_find_upstream_pcie_bridge+0x83/0x90
[ 0.402802] [<ffffffff813b3c7b>] intel_iommu_add_device+0x4b/0x1f0
[ 0.402805] [<ffffffff813ab630>] ? bus_set_iommu+0x50/0x50
[ 0.402806] [<ffffffff813ab65a>] add_iommu_group+0x2a/0x50
[ 0.402809] [<ffffffff8135bf63>] bus_for_each_dev+0x63/0xa0
[ 0.402811] [<ffffffff813ab622>] bus_set_iommu+0x42/0x50
[ 0.402814] [<ffffffff819130b6>] intel_iommu_init+0xa83/0xb7b
[ 0.402816] [<ffffffff818dd10b>] ? memblock_find_dma_reserve+0x124/0x124
[ 0.402818] [<ffffffff818dd11d>] pci_iommu_init+0x12/0x3c
[ 0.402820] [<ffffffff8100210a>] do_one_initcall+0x10a/0x160
[ 0.402823] [<ffffffff818d5037>] kernel_init_freeable+0x15b/0x1dc
[ 0.402824] [<ffffffff818d4881>] ? do_early_param+0x88/0x88
[ 0.402827] [<ffffffff814b55f0>] ? rest_init+0x90/0x90
[ 0.402828] [<ffffffff814b55fe>] kernel_init+0xe/0x190
[ 0.402830] [<ffffffff814dad6c>] ret_from_fork+0x7c/0xb0
[ 0.402832] [<ffffffff814b55f0>] ? rest_init+0x90/0x9

I'm running iTunes Radio on a WinXP PC with a KVM USB switch. With the latest iTunes update, iTunes Radio will no longer continue to stream when I switch to my work PC via the KVM switch. Can this be fixed?

I use a WinXP machine as a dedicated Music PC. I also have a separate "newer" PC to do work on. Each machine shares a Monitor, keyboard, and mouse through a KVM USB switch. I like to stream iTunes radio by starting iTunes on a selected station, then 'switch' to my work PC so that the Music PC will stream iTunes like a radio station through my Audio sound system. This used to work fine up until the latest update to iTunes. Now, when the Music PC detects the KVM switching to the other PC (basically a system hardware disconnect detection), iTunes will stop. Can I turn this 'hardward detection' issue off in iTunes?

Check your i tunes version on the PC. you need the most recent version.
Other potentials -
try a different usb port,
try a different cable.

KVM mysteries

Similar Messages

Maybe you are looking for