I use Hyper-V at work to run 64-bit VMs close to the metal on Server 2008. It works out so well, I decided to try it at home with Linux, so installed the hypervisor modules and booted up the 11.0 Xen kernel. Or tried to. A message told me I needed to try again with the parameter 'noapic,' so I did. That got me booted to a console, with only part of a file system, an empty /bin directory, and no X server. And no YaST, even character mode. I didn't try for Sax, but I did see a message saying the Nvidia driver wasn't loaded. Is this to be expected? I'll admit I haven't researched it much yet, but on Windows at work it was drop-dead easy. No instructions needed there, provided one has ever used VirtualPC, VMware, or VirtualBox. My processor (64-bit dual AMD) and BIOS both support hardware virtualization, and it's enabled in the BIOS. I didn't imagine it would be this unsatisfying, even the first time. Should I forget about it in this version of openSuSE, or keep trying until I figure out what the problem is? Thanks, Jerry in Bothell, WA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Jerry Houston wrote:
A message told me I needed to try again with the parameter 'noapic,' so I did. That got me booted to a console, with only part of a file system, an empty /bin directory, and no X server. And no YaST, even character mode. I didn't try for Sax, but I did see a message saying the Nvidia driver wasn't loaded.
Before anyone asks, yeah, I logged on with my user account. That's obviously why there wasn't much available. It's hot up in my computer room at the moment, and I wasn't in much of a mood to keep fooling with it until it cools down later. Still, does this generally work in openSuSE 11.0, or should I cut my losses and give up now? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message -----
From: "Jerry Houston"
I use Hyper-V at work to run 64-bit VMs close to the metal on Server 2008. It works out so well, I decided to try it at home with Linux, so installed the hypervisor modules and booted up the 11.0 Xen kernel. Or tried to. [...] but on Windows at work it was drop-dead easy. No instructions needed there, . [...] I didn't imagine it would be this unsatisfying, even the first time.
You should proably just use Windows then. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 16 August 2008 07:16:58 Jerry Houston wrote:
A message told me I needed to try again with the parameter 'noapic,' so I did. That got me booted to a console, with only part of a file system, an empty /bin directory, and no X server. And no YaST, even character mode. I didn't try for Sax, but I did see a message saying the Nvidia driver wasn't loaded.
I've not seen a warning about using the noapic setting before with Xen, and I've had Xen running on openSUSE 11.0 on x8_64 with no problems. Perhaps you have some unusual hardware what requires this with the Xen kernel though. Empty /bin I've never seen before - and this should not have anything to do with Xen itself. If /bin is empty then it's a filesystem issue, and you should look at it from that point. Did /bin reappear as expected when booting the default kernel? Is /bin a separate (network?) mount? If you're using the proprietary nVidia driver for 3d graphics, then this will not work with the Xen kernel. The Xen kernel contains many patches and changes to the default kernel, and the nVidia driver expects certain hardware interfaces to be available which are not there with Xen due to the Xen architecture. Use the open source nv driver without 3d graphics.
Is this to be expected? I'll admit I haven't researched it much yet, but on Windows at work it was drop-dead easy. No instructions needed there, provided one has ever used VirtualPC, VMware, or VirtualBox. My processor (64-bit dual AMD) and BIOS both support hardware virtualization, and it's enabled in the BIOS.
The graphics query I would have expected - the others not. Xen is generally pretty straightforward to set up basic/simple virtual machine instances via vm-install and virt-manager. Also, don't use NetworkManager (although that support is improving - it's easier not to).
I didn't imagine it would be this unsatisfying, even the first time. Should I forget about it in this version of openSuSE, or keep trying until I figure out what the problem is?
You encountered more problems than I'd have expected. Did you consider looking at KVM as a virtualisation option? KVM is a module that is loadable on the default kernel (so you can keep your nVidia settings) and uses the VT features of the AMD/Intel chips. It provides hardware assisted virtualisation so you won't be able to run paravirtual systems - but that may not be your intention anyway. (you can install paravirtual drivers to improve performance though) Jon -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
----- Original Message -----
From: "Jonathan Ervine"
I've had Xen running on openSUSE 11.0 on x8_64 with no problems. Perhaps you
I would love to hear the recipe for this. Especially if it doesn't consist of: * Use one or a few plain sata disks, no raid, hardware or software. * Install the full default desktop system, or any gui at all. * Use one or more gui utils to set up xen and the domU's. * Use the real system console. (vs serial console or telnet/ssh) Even in that case, I guess _any_ known working example recipe would be good. However simple and dumb the procedure ("I clicked Xen, I clicked Yes...") I could at least go through the same motions on a test box and then examin the hopefully working result and from there progress to my desired more useful installation instead of trying to go from 0 to 100 in on step like I've been trying.
have some unusual hardware what requires this with the Xen kernel though. Empty /bin I've never seen before - and this should not have anything to do with Xen itself. If /bin is empty then it's a filesystem issue, and you should look at it from that point. Did /bin reappear as expected when booting the default kernel? Is /bin a separate (network?) mount?
All that happened, obviously, was that he was dropped into the emergency shell in the ramdisk. /bin was not necessarily empty, he just never got as far as mounting the root filesystem, so all he had was the minimal /bin and minimal everything else in the initrd. But his other comments made me feel that the type, quantity, and quality of digging in and debugging required to diagnose and correct that issue would not be fun and interesting for him, and therefor no joy at all to try to help out with. -- Brian K. White brian@aljex.com http://www.myspace.com/KEYofR +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Brian K. White
-
Jerry Houston
-
Jonathan Ervine