LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 04-20-2014, 11:46 AM   #1
the_zone
Member
 
Registered: Nov 2008
Distribution: Slackware
Posts: 38

Rep: Reputation: 0
KVM/Qemu windows 7 going in recovery


I wonder if this a slackware issue but here it goes.

I have installed Qemu 1.3 from slackbuilds on my newly installed Slackware 14.1.
System is a HP ML350 with an Quadcore Xeon and 8GB of memory.
The guest is windows 7 (X17-59465)
It installs OK, boots OK and runs fine for a couple of hours.
Reboot sometimes works but most of the time it (re-)starts in recovery mode.

I installed with the following :

qemu-img create -f qcow2 /images/win7.qcow2 50G

and

emu-system-x86_64 --enable-kvm \
-vnc 0.0.0.0:5 \
-boot d \
-drive file=${DISKIMG},if=ide \
-m 1534 \
-net nic,model=rtl8139 -net tap,ifname=tap1,script=no \
-cdrom ${WIN7IMG} \
-drive file=${VIRTIMG},index=3,media=cdrom \
-rtc base=localtime,clock=host \
-smp cores=1 \
-usbdevice tablet \
-cpu host \
-vga vmware

I have tried the virtio as well but these driver give me even more trouble.

Any one an idea ?

grtz

Simon
 
Old 04-20-2014, 12:22 PM   #2
xode
Member
 
Registered: Aug 2003
Distribution: Mandrake 9.0; FC4; FC8; SUSE 10.3
Posts: 503

Rep: Reputation: 37
The first thing I would do is try to run the windows 7 vm under another linux distribution; it might very well be something obscure in slackware causing that problem. I have had very good results with SUSE (10.3 to be exact).
 
Old 04-20-2014, 03:57 PM   #3
ReaperX7
Senior Member
 
Registered: Jul 2011
Distribution: LFS-SVN, Slackware-14.1, PCBSD-10.0
Posts: 2,849
Blog Entries: 15

Rep: Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742Reputation: 742
It really won't matter the distribution. KVM/qemu works the same regardless of distribution so it's probably a kernel hardware emulation issue.

I would try a different VM like VirtualBox or VMware first and see if it's a VM limitation with KVM/qemu. If not, I would upgrade to the latest stable kernel and then give it a shot.

VirtualBox is one of the most recommended as it's driver support and hardware emulation is fairly modernized and up to date. Get the Oracle official release rather than the OSE. If you need a setup for hardware I know the ICH9 Intel setup with SCSI lsilogic hard disks work generally well for Windows vista/7/8/8.1

Last edited by ReaperX7; 04-20-2014 at 04:01 PM.
 
Old 04-24-2014, 04:26 AM   #4
the_zone
Member
 
Registered: Nov 2008
Distribution: Slackware
Posts: 38

Original Poster
Rep: Reputation: 0
Last night i tried making a VM by using AQEMU.
So far it has not crashed on me.

Even rebooting the host did not lead to Win7 guest crashes as I had before.

best regards


Simon
 
Old 04-28-2014, 04:17 PM   #5
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 519

Rep: Reputation: 137Reputation: 137
@the_zone: compare your command with AQEMU's command line. Sometimes its a question of improper qemu options.
 
Old 04-29-2014, 02:39 AM   #6
the_zone
Member
 
Registered: Nov 2008
Distribution: Slackware
Posts: 38

Original Poster
Rep: Reputation: 0
Unfortunately using aqemu did not resolve my issue.
I have been playing with options, like CPU type and machine type, which was fruitless as well.
In the coming days I want to upgrade to qemu current (1.7.1) and try again.
I really have no clue what to look for.
Is my virtual disk changing? Due to late write back?
So far is I have used sparse and non-sparse files.
 
Old 05-03-2014, 05:08 PM   #7
kingbeowulf
Member
 
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 519

Rep: Reputation: 137Reputation: 137
At this point I would upgrade qemu to 2.0.0 (latest). qemu-1.3 is very old and there have been numerous changs and fixes since then.
 
Old 05-05-2014, 12:28 AM   #8
the_zone
Member
 
Registered: Nov 2008
Distribution: Slackware
Posts: 38

Original Poster
Rep: Reputation: 0
I have indeed upgraded to qemu 2.0.0 this weekend.
First result are not encouraging.
I got an internal KVM crash and qemu dumped all registers contents.

I do not know if this has todo with the machine I created / qemu options since i changed them somewhat.
Hopefully today I start over with the qemu machine options posted above.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Set up qemu-kvm-1.0+noroms as spice enabled qemu server vs qemu-kvm-spice on Ubuntu Precise LXer Syndicated Linux News 0 05-26-2012 07:41 AM
[Debian/Qemu/KVM] Why qemu --enable-kvm works but not kvm directly? gb2312 Linux - Virtualization and Cloud 2 03-21-2011 02:05 PM
LXer: Attempt of qemu-kvm-0.14 patching via Gerds Hoffmann spice/qxl: locking fix for qemu-kvm on LXer Syndicated Linux News 0 03-14-2011 01:20 PM
LXer: Set up RH VirtIO SCSI driver on Windows XP KVM at KVM-QEMU Instance on F14 LXer Syndicated Linux News 14 01-09-2011 12:21 PM
On qemu-kvm, qemu-ifup script not found on Slackware 13 AndrewGaven Linux - Virtualization and Cloud 14 01-29-2010 03:36 AM


All times are GMT -5. The time now is 03:00 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration