| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
 Re: [Xen-users] HVM Guest Reboots Dom0
 Looks like a similar problem with Debian Squeeze 64bit rebooting: http://lists.xen.org/archives/html/xen-users/2012-06/msg00305.html . Different network config, but it's still an HVM guest rebooting dom0.
 
 
 On Sat, Jan 5, 2013 at 12:01 PM, Greg Valcourt <greg.valcourt@xxxxxxxxx>  wrote: 
I'm having a little trouble with creating a HVM virtual machine. When I start it, it reboots Dom0. I have successfully created a Paravirtualized VM.
 Here's my setup: Debian Squeeze. After installing the Xen kernel, I downloaded Linux 3.7 from kernel.org. I copied in the XEN kernel config and changed CONFIG_XEN_PCIDEV_BACKEND_PASS=y and CONFIG_XEN_PCIDEV_BACKEND_VPCI=n.
 
 Hardware:
 AMD FX 6200 (svm)
 970A-UD3 (iommu)
 Radeon HD 5770 (for passthru)
 Radeon HD 6670 (boot vga, Dom0)
 
 I'm using the following boot params: dom0_mem=1024M modprobe.blacklist=radeon,drm,microcode xen-pciback.hide=(0000:01:00.0)(0000:01.00.1)
 
 I have an /etc/modprobe.d/pciback.conf that looks like:
 
 options xen-pciback hide=(0000:01:00.0)(0000:01:00.1)
 options loop max_loop=64
 
 blacklist radeon
 blacklist drm
 blacklist microcode
 
 My guest config looks like:
 
 import os, re
 arch = os.uname()[4]
 
 kernel = '/usr/lib64/xen-4.0/boot/hvmloader'
 builder = 'hvm'
 memory = '8192'
 shadow_memory = '64'
 device_model='/usr/lib64/xen-4.0/bin/qemu-dm'
 vcpus=4
 disk = [ 'phy:/dev/xen_guests/windows7,hda,w', 'file:/root/windows7-64bit.cdr,hdc:cdrom,r' ]
 boot='dc'
 name = 'windows7'
 vif = ['type=ioemu, bridge=xenbr0,mac=00:16:3e:FF:FF:FF']
 
 acpi=1     # added later
 apic=1     # added later
 
 #gfx_passthru=1                            # my original intention is to do passthru
 #pci=['01:00.0','01:00.1']
 vnc=1                                             # changed to VNC for troubleshooting
 vncunused=0
 vncviewer=0
 vnclisten = '127.0.0.1'
 vncdisplay=2
 vncconsole=1
 vncpasswd='agoodpassword'
 sdl=0
 >>>
 usbdevice='tablet'
 
 
 stdvga=0                     # this stuff added with VNC config
 serial='pty'
 ne2000 = "0"
 
 Note that I changed from a graphics passthru setup to a vnc setup for troubleshooting. Both setups reboot Dom0.
 
 I have a script to run to get the passthrough working:
 
 echo -n "0000:01:00.0" > /sys/bus/pci/devices/0000\:01\:00.0/driver/unbind
 echo -n "0000:01:00.1" > /sys/bus/pci/devices/0000\:01\:00.1/driver/unbind
 echo -n "0000:01:00.0" > "/sys/bus/pci/drivers/pciback/new_slot"
 echo -n "0000:01:00.1" > "/sys/bus/pci/drivers/pciback/new_slot"
 echo -n "0000:01:00.0" > "/sys/bus/pci/drivers/pciback/bind"
 echo -n "0000:01:00.1" > "/sys/bus/pci/drivers/pciback/bind"
 
 Note that 01:00.0 appears not to be bound, but 01:00.1 is bound (before I run this).
 
 xm pci-list-assignable-devices doesn't list anything, but I'm not getting any error messages about the stub not owning the device anymore when I start the VM.
 
 So what exactly am I doing wrong which causes Dom0 to reboot?
 
 
 
 _______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users 
 |