On Fri, 2006-10-06 at 17:09 +0200, Matthias Hopf wrote:

On Oct 06, 06 23:07:10 +0800, Art Fore wrote:

...

I have a new dual core AMD64 motherboard and would like to get Xen to working, but am not having much success. System contains an Nvidia 7i300 video card. If I use the "nv" driver, which works with Xen but output to the 1680X1050 monitor is unsatisfactory. The driver works under the default X86_64 smp kernel, but not the Xen enabled X86_64 smp kernel. I tried a couple of patches i found on the internet to the NVIDIA driver, but they did not work.

I have a probably working Xen patch for x86_64, patched by Harald Koenig, in my inbox, you can try if you dare to :) Be aware that the patched patch is currently not 32bit(!) clean...

Please tell me about the outcome.

Matthias

email message attachment

...

-------- Forwarded Message -------- From: Harald Koenig <H.Koenig@science-computing.de> To: mhopf@suse.de Cc: Harald Koenig <koenig@science-computing.de>, Harald Koenig <koenig@tat.physik.uni-tuebingen.de> Subject: nvidia driver patch/hack fuer XEN Date: Tue, 19 Sep 2006 23:43:00 +0200

Hallo Matthias,

anbei meine modifizierte version des nvidia-hack-patches fuer 64 bit, IIRC gibts mit dieser fassung noch ein 32bit-issue, vielleicht kommt morgen noch die 32bit-fassung von zuhause zum vergleich...

gefunden haben wir das via google wie folgt:

http://www.google.com/search?q=nvidia+xen+hack+driver+patch&sourceid=mozilla&start=0&start=0&ie=utf-8&oe=utf-8

und hier gibts das (buggy) original:

http://susediary.blogspot.com/2006/06/nvidia-driver-hack-for-xen-kernel-suse... http://susediary.blogspot.com/2006_06_01_susediary_archive.html

Harald Koenig

Thanks for the info. Got a little further with this patch. It did come up with a warning about -no-kernel-specified or something like that, but it did end up with a _success_. Did go ahead and do a startx as user after that and it did go into X which it did not do before. Now I go into Yast, system, virtual machine magagement and select Add. Listed below are the steps. One thing, it originally came with with Permission denied on the ./NVIDIA-Linux-x86_64-1.0-8762-pkg2.run, so I changed it to sh NVIDIA-Linux-x86_64-1.0-8762-pkg2.run, then it went. (I was operating as root from su - login as user) What is the problem there?d Select Run an OS installation program, then Next Select Virtualization Mode, The select Full Vitualization since I have the Dual Core AMD process with the Pacifica virtualization interface. Seclect VM Properties and change the name to WinXP Select Hardware and set Memor Size in MB to 512 (I have 1 GB)) Leave Virtual Graphics Card at Cirrus Logic Leave the Graphics Viewer at SDL. Leave the Virtual Hardware Clock at UTC Select Virtual Disks Change Disk Image Director from /var/lib/xen/images/ to /windows which is a partition that I created during instatllation specifically for the WinXP virtual machine Change Maximum Size of MB to 8192 Leave the Create Sparse Image File checked and Read-Only Access unchecked as shown for default Select Network and change the name to WinXPnetwork Select AMC PCnet as the Virtual Network Card. Select Operating System Installation Select CD/DVD Device Click Accept Get Error Cannot start the Virtual machine. The installation will be aborted. Change the network card to NE200 and try again, same error. Select Details and the following message is shown command: /usr/sbin/xm create /etc/xen/vm/WinXP return Error: Device 0 (vif) could not be connected. Hotplug scripts not working. Using config file "/etc/xen/vm/WinXP". During the above, have thw Win2K installation disk in the cdrom drive.

From the /var/log/messages file I get

Oct 8 02:18:15 linux-p204 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/2/768 Oct 8 02:18:15 linux-p204 logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/2/0 Oct 8 02:18:15 linux-p204 kernel: tun: Universal TUN/TAP device driver, 1.6 Oct 8 02:18:15 linux-p204 kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com> Oct 8 02:18:15 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/2/768/node /dev/loop0 to xenstore. Oct 8 02:18:15 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/2/768/physical-device 7:0 to xenstore. Oct 8 02:18:15 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/2/768/hotplug-status connected to xenstore. Oct 8 02:18:16 linux-p204 ifup: Service network not started and mode 'auto' -> skipping Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/2/0 Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/2/768 Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/vif-bridge: brctl delif WinXPnetwork vif2.0 failed Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/2/768 Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/vif-bridge: ifconfig vif2.0 down failed Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif2.0, bridge WinXPnetwork. Oct 8 02:18:25 linux-p204 ifdown: vif2.0 Oct 8 02:18:25 linux-p204 ifdown: Interface not available and no configuration found. Oct 8 02:18:25 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/2/0 Oct 8 02:20:38 linux-p204 kernel: usb 2-5: USB disconnect, address 4 Oct 8 02:20:38 linux-p204 kernel: usb 2-5: new low speed USB device using ohci_hcd and address 5 Oct 8 02:20:38 linux-p204 kernel: usb 2-5: new device found, idVendor=0a81, idProduct=0101 Oct 8 02:20:38 linux-p204 kernel: usb 2-5: new device strings: Mfr=1, Product=2, SerialNumber=0 Oct 8 02:20:38 linux-p204 kernel: usb 2-5: Product: USB Keyboard Oct 8 02:20:38 linux-p204 kernel: usb 2-5: Manufacturer: CHESEN Oct 8 02:20:38 linux-p204 kernel: usb 2-5: configuration #1 chosen from 1 choice Oct 8 02:20:38 linux-p204 kernel: input: CHESEN USB Keyboard as /class/input/input7 Oct 8 02:20:38 linux-p204 kernel: input: USB HID v1.10 Keyboard [CHESEN USB Keyboard] on usb-0000:00:02.0-5 Oct 8 02:20:38 linux-p204 kernel: input: CHESEN USB Keyboard as /class/input/input8 Oct 8 02:20:38 linux-p204 kernel: input: USB HID v1.10 Device [CHESEN USB Keyboard] on usb-0000:00:02.0-5 Oct 8 02:20:56 linux-p204 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/3/768 Oct 8 02:20:57 linux-p204 logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/3/0 Oct 8 02:20:57 linux-p204 ifup: Service network not started and mode 'auto' -> skipping Oct 8 02:20:57 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/3/768/node /dev/loop0 to xenstore. Oct 8 02:20:57 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/3/768/physical-device 7:0 to xenstore. Oct 8 02:20:57 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/3/768/hotplug-status connected to xenstore. Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/3/0 Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/vif-bridge: brctl delif WinXPnetwork vif3.0 failed Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/3/768 Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/vif-bridge: ifconfig vif3.0 down failed Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif3.0, bridge WinXPnetwork. Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/3/0 Oct 8 02:21:07 linux-p204 ifdown: vif3.0 Oct 8 02:21:07 linux-p204 ifdown: Interface not available and no configuration found. Oct 8 02:21:07 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/3/768 Oct 8 02:25:42 linux-p204 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/4/768 Oct 8 02:25:42 linux-p204 ifup: Service network not started and mode 'auto' -> skipping Oct 8 02:25:42 linux-p204 logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/4/0 Oct 8 02:25:42 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/4/768/node /dev/loop0 to xenstore. Oct 8 02:25:42 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/4/768/physical-device 7:0 to xenstore. Oct 8 02:25:42 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/4/768/hotplug-status connected to xenstore. Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/4/0 Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/vif-bridge: brctl delif WinXPnetwork vif4.0 failed Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/vif-bridge: ifconfig vif4.0 down failed Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif4.0, bridge WinXPnetwork. Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/4/768 Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/4/0 Oct 8 02:25:52 linux-p204 ifdown: vif4.0 Oct 8 02:25:52 linux-p204 ifdown: Interface not available and no configuration found. Oct 8 02:25:52 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/4/768 Oct 8 02:27:31 linux-p204 dhclient: DHCPREQUEST on eth0 to 192.168.1.1 port 67 Oct 8 02:27:31 linux-p204 dhclient: DHCPACK from 192.168.1.1 Oct 8 02:27:31 linux-p204 dhclient: bound to 192.168.1.4 -- renewal in 1451 seconds. Oct 8 02:28:32 linux-p204 logger: /etc/xen/scripts/vif-bridge: online XENBUS_PATH=backend/vif/5/0 Oct 8 02:28:32 linux-p204 logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/5/768 Oct 8 02:28:33 linux-p204 ifup: Service network not started and mode 'auto' -> skipping Oct 8 02:28:33 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/5/768/node /dev/loop0 to xenstore. Oct 8 02:28:33 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/5/768/physical-device 7:0 to xenstore. Oct 8 02:28:33 linux-p204 logger: /etc/xen/scripts/block: Writing backend/vbd/5/768/hotplug-status connected to xenstore. Oct 8 02:28:42 linux-p204 logger: /etc/xen/scripts/vif-bridge: offline XENBUS_PATH=backend/vif/5/0 Oct 8 02:28:42 linux-p204 logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/5/768 Oct 8 02:28:43 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/5/768 Oct 8 02:28:43 linux-p204 logger: /etc/xen/scripts/vif-bridge: brctl delif WinXPnetwork vif5.0 failed Oct 8 02:28:43 linux-p204 logger: /etc/xen/scripts/vif-bridge: ifconfig vif5.0 down failed Oct 8 02:28:43 linux-p204 logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif5.0, bridge WinXPnetwork. Oct 8 02:28:43 linux-p204 ifdown: vif5.0 Oct 8 02:28:43 linux-p204 logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/5/0 Oct 8 02:28:43 linux-p204 ifdown: Interface not available and no configuration found. Questions The selection for the virtual disks are only hd*. I have a real disk hdb, the rest are sda disks. What shoudl the virtual disk be? Any suggestions for changes in the entries or other info would be much appreciated. Does anyone have any suggestions? Art