Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-07-2006, 11:12 AM
|
#1
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
Run existing Winbloze under Linux QEMU?
Hey guys,
qemu-0.8.1, kqemu-1.3.0pre7_2.4.31-i486 (courtesy AlienBob)
I have QEMU setup on one of my Slackware machines. I can point it at my hard drive and LILO gets invoked just like on a power-on reset. But I can only boot another Linux machine. My OpenBSD and Winbloze systems die- OpenBSD during init with an nvram checksum error, and Winbloze just never even seems to start. QEMU stays at 99% CPU and never comes back. I also tried booting Win directly by giving the partition number but I get a blank screen.
If I tell LILO to boot one of my other Linux machines it works perfectly.
Any ideas? I don't have enough space to make a Winbloze image and I don't have a CD, it's a "pre-installed" system (fsck you, Bill Gates)
Thanks,
Rand
Update: I did create an image file on /tmp. I thought it had to be the size of the NTFS partition- it doesn't, it's much smaller. Same results, freezes and won't complete init.
Last edited by Randux; 06-28-2006 at 01:38 PM.
|
|
|
06-07-2006, 11:44 AM
|
#2
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
|
Just a note for anyone who wants to run OpenBSD (and possibly other *BSD variants) under QEMU- I found on the QEMU forum ( http://qemu.dad-answers.com) a post suggesting disabling the kqemu feature with the -no-kqemu option on the qemu command line. I still got the same error message during OpenBSD's init but it did come up and I can use it normally, except that networking isn't working automatically and X is a little sick. It's weird because the screen is running in 640x480 instead of the 1024x768 that the other systems (including Live CDs) came up in.......
Last edited by Randux; 06-07-2006 at 12:01 PM.
|
|
|
06-07-2006, 12:37 PM
|
#3
|
Senior Member
Registered: Nov 2003
Location: London, England
Distribution: Ubuntu
Posts: 1,460
Rep:
|
I got windows XP (pre-SP1 - it's an old CD!) to install with only a few crashes & issues. It worked better with more RAM assigned to it.
|
|
|
06-07-2006, 01:42 PM
|
#4
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
|
I'm not trying to install anything- I'm trying to boot an installed copy. Thanks for mentioning the RAM, DOH! 128M default probably won't work for XP!
|
|
|
06-07-2006, 01:48 PM
|
#5
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
|
Still freezes on boot.
|
|
|
06-07-2006, 01:54 PM
|
#6
|
Member
Registered: Aug 2005
Location: Guadalajara, Jal, Mexico
Distribution: Slackware Linux
Posts: 211
Rep:
|
If you are running from your hardisk, you probably should try the "-snapshot" option.
Note that changes done to the harddrive are not going to be saved.
|
|
|
06-07-2006, 02:24 PM
|
#7
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Original Poster
Rep:
|
I use -snapshot but that doesn't help since Winbloze won't boot
|
|
|
All times are GMT -5. The time now is 02:28 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|