[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Xen 4.2 Windows 8 Issues
On 10/22/2013 08:11 AM, Shane Johnson wrote:
John,
I'm not an expert, but the only thing I see in your config that I
questioned is the passing of keyboard and mouse to the VM. You would
have to have a separate mouse and keyboard and block Dom0 from taking
control of them with a boot parameter then pass them to the DomU.
Where you are using VNC this doesn't make a lot of sense to me. VNC
will emulate the keyboard and mouse for you that is why the tablet
line is in there to VNC tracks correctly. If you need more info on
the PCI passthrough the wiki has some great information.
Hope this helps
Shane
On Mon, Oct 21, 2013 at 7:53 PM, John Wargo <wargo.john25@xxxxxxxxx> wrote:
I started with Fedora 19 (KDE) and have installed Xen 4.2 on it. I followed
the install guide, with the exception of the network bridge, as my current
wireless card doesn't support it (I'm working on getting a wired
connection).
My (relevant) hardware setup:
AMD FX6300
ASUS m5a99x evo r2.0 (IOMMU & Virtualization enabled)
Radeon 6670 (Dedicated Dom0)
Radeon 7850 (Passthrough to windows)
As the title suggests, I've been trying to install Windows 8, and I've run
into the following issue:
- Install completes successfully (Until reboot)
- Install process completes setting up devices
- Install process fails (hangs) after that with no graphical output.
The VM will just hang there, and if I don't kill it in about 1 minute, will
bring down my entire system. (Including Dom0)
Here is my configuration:
# Name for the HVM
name = "win8"
# Use HVM
builder = "hvm"
# Create 4 cpus on physical cores 2-5
vcpus = 4
cpus = "2-5"
# 8GB memory
memory = 8192
# Use lvm for windows root, and pass in cdrom for install
disk = ['phy:/dev/fedora_hypervisor/windows,hda,w',
'phy:/dev/sr0,hdc:cdrom,r']
# Uncomment and configure once br0 is created
#vif
# Boot cd rom
boot = "d" #"c"
# Use vnc for display
vnc = 1
# No vnc password
vncpasswd = ""
# Emulate VGA
vga = "stdvga"
# Provide graphics device
nographic = 1
# Emulate usb bus
usb = 1
# Use absolute coordinates for vnc
usbdevice = 'tablet'
# Use graphics card (Radeon 7850) as secondary / optional
gfx_passthrough = 0
# Pass through various PCI devices
# 2:00.0 - Radeon 7850
# 2:00.1 - Radeon 7850 (Sound)
# 0:12.0 - USB Devices (Mouse / Keyboard)
pci = ['02:00.0', '02:00.1', '00:12.0']
# Allow windows to see the local time
localtime = 1
# Pass some PCI information to windows
viridian=1
I've also tried using irqs=[18], but that did nothing...
Afterwards, I get a notification informing me that IRQ 18 was disabled..
Message from syslogd@Hypervisor at Oct 21 20:28:19 ...
kernel:[ 1312.294827] Disabling IRQ #18
xl dmesg output:
ss = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
[truncated output, only first 10 iterations are shown...]
What is the best way to go about solving this problem?
As always just ask for more info,
-John
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
It seemed to fix the irq error, however I'm still getting the
IO_PAGE_FAULT errors.
I'll go through the debugging page on the wiki, and see what I can't dig
up..
-John
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users
|
