Re: VirtIO and BSOD On Windows Server 2003
On Wed, Jun 5, 2013 at 3:56 PM, Vadim Rozenfeld vroze...@redhat.com wrote: - Original Message - From: Aaron Clausen mightymartia...@gmail.com To: Vadim Rozenfeld vroze...@redhat.com Sent: Thursday, June 6, 2013 12:45:14 AM Subject: Re: VirtIO and BSOD On Windows Server 2003 On Tue, Jun 4, 2013 at 7:11 PM, Vadim Rozenfeld vroze...@redhat.com wrote: - Original Message - From: Aaron Clausen mightymartia...@gmail.com To: Vadim Rozenfeld vroze...@redhat.com Sent: Wednesday, June 5, 2013 10:05:03 AM Subject: Re: VirtIO and BSOD On Windows Server 2003 On Tue, Jun 4, 2013 at 4:37 PM, Vadim Rozenfeld vroze...@redhat.com wrote: Yes, we have it WHQL certified as a SCSI adapter for all OS'es , except for XP, and it should be available as a part of virtio-win package from fedoraproject site. -- Okay, some further information. The stop code was 0x007f, with the parameter 0x000d; UNEXPECTED_KERNEL_MODE_TRAP Do you have any other VM, like Win7/W2K8, to check with? No, unfortunately. I do have a Server 2012 install (just working as a domain controller/authenticator at the moment), so I know the x64 virtio drivers have no problem. I'm pretty sure this isn't a problem with the driver itself. Doing some googling reveals that there are some problems with some x86 guests, and it's probable that Debian has run with a kernel that doesn't possess the appropriate patches (not for the first time), and unless I want to go to testing (not what I would consider a good idea on a production machine), I'll be stuck with IDE. the difference between WS2K3 and WS2012 is that the first one is only working in IRQ mode, while more modern OS'es operate in MSI interrupt mode. I would start with checking bios version, maybe it worse to download the recent Seabios and build it by yourself. I'm building the new server and maybe I'll throw CentOS or Fedora on it. I'm more a Debian fan myself, but while these guests are running, ide emulation is slow. Yes, according to our performance team the recent viostor driver was 2..6 times faster than IDE, depending on load scenario. Vadim. That didn't make me feel better :) I'm going to try out Fedora today. If the Windows guests work in it, then I'll move to the platform. I like Debian, but running under IDE, particularly for the MS-Exchange server, is just not pleasant. Okay. I set up a CentOS 6.4 x64. Fired up a Windows Server 2003 x64 guest and the second I installed the virtio drivers, I got a BSOD with 0x0007e (a different error, yes, but won't boot until I yank the viostor.sys file). This is on completely different hardware and it's a qcow2 rather than a raw image, so at this point I have to believe that there is something very broken in the virtio drivers. I'm thinking at this time because I need these guests running in a production environment that I'm going to go back to an earlier Debian release. I' m pretty disappointed here. KVM has been rock solid for me for two years, and this is the first trouble I've had. -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: VirtIO and BSOD On Windows Server 2003
On Tue, Jun 4, 2013 at 7:29 AM, Vadim Rozenfeld vroze...@redhat.com wrote: If IDE works fine, try adding another disk as virtio and see it the secondary disk works smoothly as well. That's what I did, and the instant the virtio block driver initialized in BSODed on me with 0x007f (reason code 0x805000f). According to Microsoft this problem occurs because the NTFS driver incorrectly locks the resource when the NTFS driver tries to access the resource. I've attempted to start the guest with the virtio driver cache disabled, but with no success. -- Aaron Clausen mightymartia...@gmail.com -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Fwd: VirtIO and BSOD On Windows Server 2003
On Tue, Jun 4, 2013 at 7:55 AM, Aaron Clausen mightymartia...@gmail.com wrote: On Tue, Jun 4, 2013 at 7:29 AM, Vadim Rozenfeld vroze...@redhat.com wrote: If IDE works fine, try adding another disk as virtio and see it the secondary disk works smoothly as well. That's what I did, and the instant the virtio block driver initialized in BSODed on me with 0x007f (reason code 0x805000f). According to Microsoft this problem occurs because the NTFS driver incorrectly locks the resource when the NTFS driver tries to access the resource. I've attempted to start the guest with the virtio driver cache disabled, but with no success. As a further bit of disclosure, I'm using raw images right now. I'm going to convert one of my Server 2003 guests to qcow2 and see if that makes a difference. -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
VirtIO and BSOD On Windows Server 2003
I've been merrily running a Windows Server 2003 with Exchange vm under an older version of KVM (0.12.5) under Debian 6 (Squeeze), for over a year. I recently built a new kvm server with Debian Wheezy which comes with KVM 1.1.2 and when I moved this guest over, I immediately started getting BSODs (0x007). I disabled virtio block driver and then attempted to upgrade to the latest with no luck. Right now I have it running under IDE, and because the new server is pretty spunky, I don't see any performance issues, but I have another Server 2003 vm that is a file server to move over and I'm concerned that I start getting a few IDE emulated guests and things will start to get ugly. Oddly enough, I have a Server 2012 (x64) running on virtio that moved over without a hitch, so this is clearly a Server 2003 issue. The most obvious solution at the moment is to downgrade to Debian Squeeze, and that's the course I may take for the time being, but that's not much of a long term solution. I've done some research and this does seem to be an issue with Windows XP/Server 2003 guests but clearly the issue here is not just virtio drivers, but interaction between the drivers and a newer version of kvm. Does anybody have any thoughts or workarounds? -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Guest Network Dropouts
I'm running a stock Centos 5.7 on an AMD machine install with KVM 83 on a 2.6.18 kernel. I'm having trouble with a Debian Squeeze guest running on a bridged ethernet (there are three ethernet cards in the machine for different networks) sporadically losing its network connection. I'm running a constant ping on it, and it seems to come and go relatively randomly. Packets will drop for maybe six or seven pings, and then come back up. I'll lose ssh and other connections to the guest. To test if it was some issue with the network hardware, I set up an IP address on this bridge on the Centos host and it runs just fine, so this is clearly related to the guest OS. I've tried changing from virtio to e1000, and it makes no difference. Is there something I'm missing here. I have a near identical setup on another server (though this is an Intel) and have guests running on all three interfaces without an issue. -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
PCI Passthrough Problem
I'm trying once again to get PCI passthrough working (KVM 84 on Ubuntu 9.10), and I'm getting this error : LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin /usr/bin/kvm -S -M pc-0.11 -m 4096 -smp 4 -name mailserver -uuid 76a83471-e94a-3658-fa61-8eceaa74ffc2 -monitor unix:/var/run/libvirt/qemu/mailserver.monitor,server,nowait -localtime -boot c -drive file=,if=ide,media=cdrom,index=2 -drive file=/var/lib/libvirt/images/mailserver.img,if=virtio,index=0,boot=on -drive file=/var/lib/libvirt/images/mailserver-2.img,if=virtio,index=1 -net nic,macaddr=54:52:00:1b:b2:56,vlan=0,model=virtio,name=virtio.0 -net tap,fd=17,vlan=0,name=tap.0 -serial pty -parallel none -usb -usbdevice tablet -vnc 127.0.0.1:0 -k en-us -vga cirrus -pcidevice host=0a:01.0 char device redirected to /dev/pts/0 get_real_device: /sys/bus/pci/devices/:0a:01.0/config: Permission denied init_assigned_device: Error: Couldn't get real device (0a:01.0)! Failed to initialize assigned device host=0a:01.0 Any thoughts? -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Advice for Router Guest
I'm looking at moving from the router I'm running currently (a Linux box) and moving it into a KVM guest. What are the recommendations for the networking of the external interface? Should I just pass the NIC card through via PCI passthrough or is there a recommended way? -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
KVM on Debian
I'm running a production Debian Lenny server using KVM to run a couple of Windows and a couple of Linux guests. All is working well, but I want to give my Server 2003 guest access to a SCSI tape drive. Unfortunately, Debian is pretty conservative, and the version of KVM is too old to support this. Is there a reasonably safe way of upgrading to one of the newer versions of KVM on this server? -- Aaron Clausen mightymartia...@gmail.com -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
