Since the update to beta9, my Windows 8.1 VM crashes with a BSOD (showing errors related to video_tdr_failure). If I turn off my PCI passthrough (just an AMD 6450), it will boot without issue. This VM was created when beta7 was released to take advantage of the qcow2 format and worked flawlessly in beta7/beta8.

 

My config file that I borrowed from another post in this forum:

name = "Win81_Xen"
builder = "hvm"
# kernel = 'hvmloader' not needed.
# device_model_version = "qemu-xen-traditional" deprecated.

# You can adjust the vcpu and memory lines if you wish.
vcpus = 2
memory = 2048

# Win7x64.iso is the name of my ISO, change it to whatever yours is named.
# When your Windows 7 installation is complete, you can delete the reference to your ISO image below, which is this part:
#  , 'file:/mnt/cache/VMs/Windows7/Win7x64.iso,hdc:cdrom,r'
disk = ['qcow2:/mnt/user/VMshare/Win81_Xen/Win81_Xen.qcow2,hda,w' , 'file:/mnt/cache/VMshare/Win81_Xen/Win81_Xen.iso,hdc:cdrom,r']

# Note: Your bridge name (br0) needs to match the bridge name in the unRAID network settings.
vif = [ 'mac=00:16:3e:ab:56:78,bridge=br0' ]

# When your Windows 7 installation is complete, change this to "c" so you don't boot with the DVD.
boot = "c"

acpi = '1'
apic = '1'
viridian = '1'
xen_platform_pci = '1'
sdl = '0'
vnc = '1'

# This is the IP address of your unRAID server.
vnclisten = '0.0.0.0'

# vncpasswd = '' No password.
stdvga=1
usb = '1'
usbdevice = ['tablet','host:1934:5168']  
localtime = 1
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "destroy"
pci = ['01:00.0','01:00.1']

 

and my syslinux:

default /syslinux/menu.c32
menu title Lime Technology
prompt 0
timeout 50
label unRAID OS
  kernel /bzimage
  append initrd=/bzroot
label unRAID OS Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Memtest86+
  kernel /memtest
label Xen/unRAID OS
  menu default
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage xen-pciback.hide=(01:00.0)(01:00.1) --- /bzroot
label Xen/unRAID OS Safe Mode (no plugins)
  kernel /syslinux/mboot.c32
  append /xen --- /bzimage --- /bzroot unraidsafemode

 

I noticed beta9 updated the Xen package, so I'm assuming my issue is related. I'm hoping it's just a setting that is no longer compatible or something similar. Anyone else on beta9 seeing similar issues or have any suggestions?

Xen was updated to 4.4.1 in beta 9.  The Xen team seems to put GPU pass through low on the priority list compared to other features.  KVM is much better for this.

I had issues with win 8.1 vm on xen after upgrading from beta 7 to beta 9. (constant crashes in mediaportal and the same error you report once)

 

I applied all available 8.1 updates (in vnc mode) and all is well.

 

Peter

I am have the same problem  with seeing video_tdr_failure once.

 

After that the windows vm either won't boot or just loops.

 

Works okay with PCI passthrough off.

 

Applied all patches to windows 8.1 as mentioned in this thread but did not help.

 

Also when i try to boot normal unraid i am getting a lot of messages about dmark and then it can't find the unraid drive.

 

Any ideas?

 

Update:

Rolling back to Xen included in beta 8 gets me back online. I guess this is a good temp fix.

Anyone  know if there is any issue with doing this. I updated to beta 9 due the warning about possible corruption.

 

Thanks

-David

OP, have you tried setting your VNC flag to '0' in your config file?

 

I always set mine to off when I have VGA passthrough active, switching it on only for system and video driver upgrades (where I disable the video card). I've evolved this practice since the early days when having both VGA passthrough and VNC active would result in a phantom second screen in my set-up.

 

If you're getting VGA related errors, I'd go for simplifying related settings as much as possible.

 

Also, try removing the stdvga flag, I don't think I use that.

 

I'm at work right now but will try to post my own config file later for reference as I have no problems.

 

Peter

 

OP, have you tried setting your VNC flag to '0' in your config file?

 

I always set mine to off when I have VGA passthrough active, switching it on only for system and video driver upgrades (where I disable the video card). I've evolved this practice since the early days when having both VGA passthrough and VNC active would result in a phantom second screen in my set-up.

 

If you're getting VGA related errors, I'd go for simplifying related settings as much as possible.

 

Also, try removing the stdvga flag, I don't think I use that.

 

I'm at work right now but will try to post my own config file later for reference as I have no problems.

 

Peter

 

Thanks for the response (and for your blog, it was a big help when I was originally setting things up on b5a). I tried a few of your suggestions with the following results:

 

1)Applied all Win 8.1 updates (including optional) - no change

2)Commented stdvga flag (with VNC active) - booted, but totally ignored my passthrough

3)Changed VNC to 0 (with stdvga commented) - back to the error and looping restarts

 

I'd still appreciate seeing your current config file. It still could be a simple fix.

 

Update:

Rolling back to Xen included in beta 8 gets me back online. I guess this is a good temp fix.

Anyone  know if there is any issue with doing this. I updated to beta 9 due the warning about possible corruption.

 

Thanks

-David

 

Good call on reverting to the Xen package from b8. I replaced mine as well and after a quick autorepair/reboot I'm back to running as expected on my original config file. Thanks for the tip!

 

I'd still be interested in hearing if there are any detrimental effects from running this outdated package.

Xen was updated to 4.4.1 in beta 9.  The Xen team seems to put GPU pass through low on the priority list compared to other features.  KVM is much better for this.

 

I'm not opposed to switching to KVM, in fact I tried when b7 was released (as I got the sense that LT was moving that direction). There's definitely some great work being done on this front, but the current information on the forum is still in flux and seems a little disjointed. It's pretty tough to decipher what the current best practices are. That said, I was able to get a Win 8.1 install running on b7 without passthrough, but ran into a roadblock with the "groups" as my graphics card wasn't isolated. So I switched back to Xen, which was rock-solid (an improvement over b5a for me even) through b7 & b8.

 

I'm still expecting that I'll end up switching, but I'm hoping things become a little more clear as you release b10 and forward. The work with virt manager looks promising. It's also a small matter, but I'm partial to the simple Xen control panel in the current unRAID GUI.

 

In the meantime, I'll probably stick to the previous Xen package unless you think that would expose some vulnerabilities?

 

Thanks for your response and all your hard work since joining the team!

Good to read that reverting to old Xen works for you.

 

I'm also thinking of migrating to KVM but am likewise adopting a wait and see policy as beta progresses. (the recent 'you need BTRFS for docker' followed quickly by 'Actually, you don't need BTRFS for docker' see-saw has put me off committing to anything until there's a bit more stability.

 

Here's my known working Xen Windows 8.1 config that works with beta9 (I didn't need to make any changes). VGA and USB passthrough implemented;

 

name = 'TV1'
builder = 'hvm'
vcpus = '2'
memory = '3072'
device_model_version="qemu-xen-traditional"
disk = [
        'file:/mnt/cache/domains/TV1/TV1.img,hda,w' 
   
]
vif = [ 'mac=00:16:3E:51:20:4D,bridge=xenbr0,model=e1000' ]
on_poweroff = 'destroy'
on_reboot = 'restart'
on_crash = 'restart'
boot = 'c'
acpi = '1'
apic = '1'
viridian = '1'
xen_platform_pci='1'
sdl = '0'
vnc = '0'
vnclisten = '0.0.0.0'
vncpasswd = ''
vncdisplay = 1
stdvga = '0'
usb = '0'
usbdevice=['host:147a:e03e','host:2222:2051','host:0603:00f2']
pci = ['05:00.0','05:00.1']

The most notable change I see is the device_model_version="qemu-xen-traditional" line. I might take one for the team and switch back to the newer Xen and see what this results in. I also totally commented out the stdvga line as opposed to setting it 0. No idea if this will have an effect, but I might give it a go.

 

Update: Trying to change to the traditional device model leaves the VM unbootable. I feel like I should have known as much.

I also have traditional and confirm it fails to boot.

 

My plan is to move to KVM once it settles but for now i have moved many of my xen vm to docker to minimize the number of vm's and pain when the time arrives.

 

Are you able to boot your system into standard unraid? When i try  after it says unpacking intrafs I get all kinds of errors about dmark for about 2 minutes and then it fails to find the unraid usb drive.

 

The xen boot option works as before so not sure whats wrong.

 

I also have traditional and confirm it fails to boot.

 

My plan is to move to KVM once it settles but for now i have moved many of my xen vm to docker to minimize the number of vm's and pain when the time arrives.

 

Are you able to boot your system into standard unraid? When i try  after it says unpacking intrafs I get all kinds of errors about dmark for about 2 minutes and then it fails to find the unraid usb drive.

 

The xen boot option works as before so not sure whats wrong.

 

I did the same with the Docker containers. They're my new favorite toy in unRAID. I'm down to this single VM now.

 

I just tried booting into standard unRAID. It started fine for me, so it's likely a separate issue.

Thanks for giving that a try and confirming it works.

 

I guess I have some debug to do before I can stop booting Xen.

 

Sounds like I'm the lucky one in that mine more or less just worked following upgrade to beta9.

 

Would appreciate people contenting to post findings here - it might help me if/when stuff breaks in beat 10

 

Thanks

 

Did you guys have better luck with 10A?

 

I just tried it earlier today. WIndows 8 vm boots up but no GPU passthrough. WIndows shows sound and graphics with a yellow triangle.

 

Used the same trick of using the old xen exe and all came up fine.

 

Did you guys have better luck with 10A?

 

I just tried it earlier today. WIndows 8 vm boots up but no GPU passthrough. WIndows shows sound and graphics with a yellow triangle.

 

Used the same trick of using the old xen exe and all came up fine.

 

Exactly the same. Still using the older version of Xen.

How do you load an older version of Xen into 6.10a?

How do you load an older version of Xen into 6.10a?

 

Just replace the "xen" file on the flash with the desired version from an older unRAID install (aka v6b8).

 

Out of curiosity, why are you rolling back?

So, I tried the latest Beta 12 and it still seems like Xen is broken.

 

Worked after rolling back Xen as before.

So, I tried the latest Beta 12 and it still seems like Xen is broken.

 

Worked after rolling back Xen as before.

 

Are there instructions for compiling Xen on our own?  4.5 is out, and I would love to give that a run for it's money.

 

8.1 with the ATI Drivers, and 4.4.1, leaves me with just constant reboots and BSOD's.