[SOLVED] QEMU-KVM fails to boot if passed q35 machine type

As I understand it, qemu still uses the PII3X as the default machine type. I had been using -machine type=q35,accel=kvm for a few weeks to learn more about qemu and KVM. With this code I could boot a win7 VM and I confirmed the ICH9 chipset appeared in the device manager.
After a system update I am no longer able to pass that command. I am using the linux-0.2 image located here.
If I enter this code, the system boots normally:
qemu-system-x86_64 -enable-kvm -boot order=c linux-0.2.img
This however does not work and the bios complains that there is no bootable media found (after waiting for pxe):
qemu-system-x86_64 -enable-kvm -boot order=c -M q35 linux-0.2.img
qemu is 1.7.0-2 (built 02/19/14 but this is the only package in pacman's cache)
seabios is 1.7.3.1-2 (built 09/21/13)
I actually tried this on two different machines with the same result. What can I do next to troubleshoot? Thanks.
Last edited by gizzard (2014-04-13 15:55:25)

R00KIE wrote:
The iso should boot, yes. I did try using -M q35 with a WinXP image I have here and it started to boot (I get blue screens and automatic reboots since lots of things change with -M q35).
One different thing I have however is the specification of the interface type for disks. Try using "-drive file=/path/to/image,if=scsi" or "-drive file=/path/to/image,if=virtio", that seems to make it work for me, it still might make Win7 complain though.
I think I'm getting closer thanks to your help. Adding the if variable allows the debian image to boot using the q35 machine type. Here are results of some trials (command and result):
1. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 debian-live-7.4-amd64-standard.iso
- boots fine
user@debian:~$ lspci | grep ACPI
00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
2. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm debian-live-7.4-amd64-standard.iso
- fails to boot
3. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=ide
- fails to boot
4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=scsi
- boots fine
user@debian:~$ lspci | grep AHCI
00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
user@debian:~$ lspci | grep SCSI
00:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=virtio
- boots fine
user@debian:~$ lspci | grep AHCI
00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
user@debian:~$ lspci | grep SCSI
00:03.0 SCSI storage controller: Red Hat, Inc Virtio block device
I will try these options with the win7 VM and report back. I may need to recreate it from scratch, so it might take a little while.

Similar Messages

[solved]qemu-kvm, cant start all guests with latest qemu-kvm

Hi there!
I have a problem when I updated qemu-kvm package from 1.0.1-3 to 1.1.0-1
Some Linux guests can get started without problems but other will die after grub tries to load the kernel.
In my messages log i can find the following error when starting a affected guets:
qemu-kvm[2026]: segfault at 10 ip 00007f2845549d0e sp 00007f283d024c00 error 4 in qemu-system-x86_64[7f2845419000+308000]
After downgrading to the previous version i could start the guests again.
Did anyone had similar problems with the current qemu?
Kind regards
Edit: Upgrade to 1.1.1.1 solves the issue
Last edited by nonsens (2012-07-20 08:17:31)

After some reading I found a workaround:
Edit the VM configuration with
#virsh edit <VM NAME>
and replace 'pc-0.15' with "pc-1.1'
<os>
<type arch='x86_64' machine='pc-1.1'>hvm</type>
<boot dev='hd'/>
</os>
The diff output of the changed /etc/libvirt/qemu/<VM_Name>.xml file with the saved one should look like:
#diff test.xml test.xml.sav
15c15
< <type arch='x86_64' machine='pc-1.1'>hvm</type>
> <type arch='x86_64' machine='pc-0.15'>hvm</type>
Now the changed VM start successful

[SOLVED] qemu-kvm update breaks libvirt

I just recently upgraded to qemu-kvm 0.12.1.2-1
Once I did this I was unable to start my VM's I received:
error: Failed to start domain dns
error: internal error unable to start guest: char device redirected to /dev/pts/1
qemu: '' invalid format
I just rolled back the package using the packages in
/var/cache/pacman/pkg by pacman -U qemu-kvm-0.11.0-1-x86_64.pkg.tar.gz
Last edited by papertigers (2010-02-25 16:01:15)

After deciding to upgrade to the new one and actually figure out what the problem was I discovered it was a simple fix.
To fix the problem I was getting I went into virt-manager and all you have to do is remove the machines hard drive and then reattach it.
I was then able to boot the VM's.

[SOLVED] "Filesystem check failed" during boot process

I was using XFCE on my netbook recently and clicked "shutdown". It logged out to the command prompt and nothing happened. Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update... And moments later it suddenly started the shutdown process.
Now, whenever I boot up, I see the message below. I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
Can anyone suggest what I might need to do to fix the problem?
rootfs: clean, 11026/246512 files, 477083/984576 blocks
home: clean, 4386/527280 files, 237183/2105344 blocks
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
************* FILESYSTEM CHECK FAILED ************
* Please repair manually and reboot. Note that the root
* file system is currently mounted read-only. To remount
* it read-write type: mount -n -o remount,rw /
* when you exit the maintenance shell the system will
* reboot automatically.
Give root password for maintenance
(or type Control-D to continue):
Last edited by esuhl (2012-03-27 01:20:07)

Thank you all for your replies :-)
hadrons123 wrote:What happens when you do try the suggestion given by it?
I don't exactly know how I should "repair manually"... I thought a filesystem check in GParted would have been enough...
lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
Thanks. I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition. The check completed, but the problem persists... I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
fsck from util-linux 2.20.1
e2fsck 1.41.14 (22-Dec-2010)
usr was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
Gcool wrote:
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it? Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...? Anyway, the partition details from /etc/fstab are below.
<file system> <dir> <type> <options> <dump> <pass>
tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext2 defaults,noatime 0 1
/dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
/dev/sdb2 /usr ext2 defaults,noatime 0 1
I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
If I type "umount /dev/sdb2" at the prompt, I get the following error:
umount: /usr: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
I also booted into GParted, but there is no option to "unmount" /dev/sdb2. There is a "mount" option in the menu, but it is greyed out. If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
umount: /dev/sdb2: not mounted
DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
No (as shown above). I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

[SOLVED] qemu-kvm high cpu usage when using pulseaudio alsa-plugin

My Arch system is configured to use pulseaudio. When an application connects to the sound server it will use either a native pulseaudio driver, or the pulseaudio alsa-plugin if it using a alsa driver.
qemu-kvm in 'extra' is not compiled with native pulseaudio support. When running guests with sound hardware support, qemu-kvm connects to the sound server using the pulseaudio alsa-plugin.
The problem I'm seeing is high cpu usage on the Arch host even though cpu usage on the guest is low. Also, the guest is often unresponsive for a period of time when opening sound applications like the mixer or playing audio.
My solution is to recompile qemu-kvm with native pulseaudio support. This eliminates the use of the pulseaudio alsa-plugin on the Arch host and fixes the above problems.
An easy was to do this is run:
yaourt -S qemu-kvm --build
And edit the PKGBUILD changing the line:
--audio-drv-list=alsa,sdl,oss,esd \
To:
--audio-drv-list=pa,alsa,sdl,oss,esd \
Finish building and install. Don't forget to add yourself to the kvm group.
Last edited by bytesize (2010-08-16 02:34:08)

Problem disappeared.
I'm not sure, but i think installing xf86-video-modesetting helped to fix this issue.
I had an error messages in /var/log/Xorg.0.log like this:
(EE) Failed to load module "modesetting" (module does not exist, 0)

[SOLVED] Live USB fail to boot

Booting Arch netinstall and core from a USB fails on waht appears to be "booting the kernel"
After that the screen is flood with what looks like a dump.
The last 5 lines are something like (i quickly copied them down) and each line is preceded by a bunch of numbers:
do_one_initcall +0x35/0x170
? quick_tc86c001_idet +0x22/0x22
kernel_init +0xae/0x13a
? start_kernel +0x35d/0x35d
kernel_thread_helper +0x6/0x10
_ *blinking*
It hangs there and doesn't go away until I reset the machine
iso was torrented but I did a md5 check anyway and then created it using Universal USB installer. It works fine on my laptop.
Hardware
Mother board: Gigabyte GA-Z77-D3H
BIOS: BIOS Date: 02/21/12 15:12:36 Ver: 04.06.05
Processor: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz (4 CPUs), ~5.9GHz
Card name: NVIDIA GeForce GTX 560 Ti
NIC:Atheros AR8151 PCI-E Gigabit Ethernet Controller (NDIS 6.20)
Last edited by glethro (2012-06-17 03:23:54)

glethro wrote:I will leave this as solved as the kernel panic is no longer happening.. But archbot doesn't seem to work either. When in the configure step it shows a fstab file with an entry only for tmp. I booted this and it created the entire file system as read only. I reinstalled and used my own fstab file and was still left with a read-only system.
I successfully installed archlinux using archboot... concerning your fstab issue, I just haven't look this file in the configure step and everything worked fine... did you try editing this file manually without using the archboot installer ?

[SOLVED] Disk check failed at boot.

Hello,
I've got a problem with arch booting. It looks like my cpu doesn't like being left alone fat night. I powered it on today and what I get iss disk check failed error and reboot message. I've tried fsck-ing all partitions and everything seems to be allright. What's more I can mount everything when press ctrl+z when arch tries to reboot and system loading goes on. Any tips? What should I post?
Last edited by muchzill4 (2010-02-05 10:02:48)

You have some messed up file systems. As if you didn't know.=O)
Have you changed fstab? Switched disks around? Try using uuid in fstab instead of '/dev/sdxx'.
Check this thread http://bbs.archlinux.org/viewtopic.php?id=89857
and use
ls -l /dev/disk/by-uuid

[SOLVED] Custom Kernel failed to boot

Hello everyone, this is my first time compiling my own kernel, I was afraid of breaking the base system so I followed the guides on the wiki
http://wiki.archlinux.org/index.php/Ker … n_with_ABS
http://wiki.archlinux.org/index.php/Cus … n_with_ABS
:: Running Hook [filesystems]
:: Loading root filesystem module...
ERROR: Failed to parse block device name for '/dev/sda4'
ERROR: root fs cannot be detected. Try using the rootfstype= kernel paramter.
ERROR: Unable to create/detect root device '/dev/sda4'
I have tried to make an intrid by makeinitcpio -k <my kernel version> -g kernel-SLAB.img but that didn't really do anything.
So I'm just wondering where I have done wrong, the kernel error messages are pertty cryptic so I have no idea, I would really appreciate any help I can get right now.
Here's a list of the files that I have used or related to this problem. Thanks all!
*PKGBUILD
http://www.ualberta.ca/~blu2/kernel26/PKGBUILD
*kernel config file
http://www.ualberta.ca/~blu2/kernel26/config
*GRUB menu.lst
http://www.ualberta.ca/~blu2/kernel26/menu.lst
*mkinitcpio conf
http://www.ualberta.ca/~blu2/kernel26/mkinitcpio.conf
*RC.conf
http://www.ualberta.ca/~blu2/kernel26/rc.conf
Update, HELP NEEDED
To be on the safe side, I decided not to apply any EXTRA patch at all, so I used the kernel26 from /var/abs/core/base/kernel26, ONLY changing the package name and the features I wanted, (I changed the generic m686 MARCH to MK8 (amd semperon processor) and KEPT everything else as is to the .config file in /usr/src/linux-2.6.23.12-ARCH/.config
The package compiled fine but again, but I can't boot properly, giving the same error as previous attempts. The mkinitcpio generated an image that I can boot with the original kernel that came with Arch, but not the kernel I compiled.
I noticed that during boot, when loading udev, for the original kernel, there's a lot of messages showing modules being detected etc., but for my compiled kernel, there's only one message loading the PS2 keyboard, and nothing else, the HOOK filesystem was ran immediately after that. Is there anyway to capture those initial boot messages? Thanks!
I'm not sure what I am doing wrong. Any help is appreciated.
Update
Kernel sucessfully compiled with the help of fwojciec, thank you.
Last edited by blu3ness (2008-01-15 05:42:38)

I can only really tell you how I do it -- I'm not exactly an expert with in-depth knowledge of how kernel works
The way I compile the kernel is by adapting the PKGBUILD for the current kernel from the ABS. I use the script from this thread (http://bbs.archlinux.org/viewtopic.php?id=34815) to rename the kernel and add "make menuconfig" command to the PKGBUILD; I also manually add some patches. If you want to use this script be careful: is a bit old and last time I've tried it changed "kernel26" to kernel26-[myname] in few some source addresses which obviously was not good but also not really difficult to fix.
When I compile the kernel like this I can just do "mkinitcpio -p kernel26-[myname]" and this generates the image without any problems.
Sorry -- that's the best answer I can give you. Perhaps somebody else will have ideas what needs to be done using your method to get the kernel to work. Maybe just looking at the script will give you some ideas...

[solved] netfs/sshfs failing on boot

ok I seem to have a very weird problem and I can not for the life of me figure out a solution.
I have ssh setup with rsa authentication, I am mounting the sshfs share in fstab according to the wiki.
[email protected]:torrents/ /mnt/desktop fuse defaults,users,port=22000,reconnect,allow_other 0 0
On boot netfs fails with the error
Connection reset by peer.
But if I let kde finish loading and start a terminal and type in
/etc/rc.d/netfs start
it mounts just fine. This is where I don't understand why it will not mount when booting. Because I can not replicate the error once the machine is fully booted. I even tried the sleep 20 trick in netfs.
my daemon array looks like this.
DAEMONS=(syslog-ng acpid cpufreq crond hal !net-profiles net-auto-wireless rpcbind nfs-common oss fam sshd ntpd !avahi-daemon netfs)
Any idea is worth a shot so please amuse me
Solution: Delete the /root/.ssh/known_hosts file and then re-authenticate the host machine for root user locally. My known_hosts had two entries and the first entry was not available on the network. I assume this is the reason why netfs was failing. The rsa key of the only working host was the exact same before and after in the known_hosts file.
Last edited by jacko (2009-12-29 16:16:56)

After booting "swapon -s" give me:
Filename Type Size Used Priority
/dev/sda3 partition 8388604 0 -1
So I assume that the swap partition is actually mounted and activated. However, resuming from hibernation always results in output which says "clearing orphan nodes." I know it has something to do with the swap because I was able to get resume to work by activating swap after I manually mounted swap after booting. I can't remember the exact process I used, whether it be through systemctl or swapon. I will see if I can get figure it out again.

[SOLVED] gdm randomly fails on boot

Hello everybody,
I'm new to arch and it took me some time to get everything going, but now it works almost without issues. One not really critical, but very annoying thing is the following:
Sometimes when booting the system (pure systemd setup), gdm will not start (i. e. no graphical login appears). Instead, I'm directed to tty1, have to log in and do systemctl stop/start gdm.service. I have absolutely no idea why it is working sometimes and sometimes not - it seems like a random phenomenon... Here are the Xorg.log files of the situation when everything's working and when it's not:
working: http://pastie.org/private/szwlmvl8pcbcaoe0xurba
failing: http://pastie.org/private/webtcyiyktdwkeke8rb9kq
The output is not very conclusive, in my opinion. What other logfiles could be helpful?
Thanks for your help in advance!
Last edited by michaels (2012-10-24 20:47:19)

1) to push this one a little...
2) to give some more information: Checking the output of journalctl thoroughly, I found out that in the not-working case the gdm error messages (GDM display: display lasted xxx seconds / maximum number of X display failures reached) appear between messages from the kernel. Those indicate that the system is still busy loading kernel modules (device drivers for sound and chipset, in particular). Maybe some modules which are needed for the X server to run properly aren't loaded when systemd attempts to start gdm? Then, how to apply a timeout or, even better, a proper dependency to gdm.service unit?
journal failing: http://pastie.org/private/0k6fjkoievd7k90ytnqdq
journal working (truncated after gdm started successfully): http://pastie.org/private/orbvisc9hbjgmosxplmtra
I also tried to upgrade gdm from [testing] with all its dependencies, but this does not work at all.

[SOLVED] Arch Linux Duke (2007) Fails to Boot

Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch. It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
If you have read this far, you are a trooper. Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
:: Loading udev events [Pass]
:: Mount root Read-only
:: Checking file systems
This is where it stops.
The next thing I see is:
/dev/sda6
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
E2fsck –b 8193 <device>
I then get a sort of character based splash screen that says
**********FILE SYSTEM CHECK FAILED ****************************
* Please repair manually and reboot. Note that the root file system
* is currently mounted read-only. To remount it read-write, type:
* mount –n –o remount,rw /. When you exit the maintenance
* shell, the system will reboot automatically
Give root password for maintenance
At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
/dev/sda6 on / type ext3 (rw)
This is exactly the root partition that the start up complains about. It is clearly there. I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
# mknod “/dev/root2” b 3 6
(“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
image = /boot/vmlinuz26
root = /dev/sda6
label = ArchLinux-Duke
initrd = /boot/kernel26.img
read-only
I am stumped. Thanks in advance for any and all pointers you may be able to offer.
Last edited by mac57 (2014-06-02 17:42:21)

Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next. This is my guess anyway.
I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

[solved] Libvirt "No accelerator found!" but aqemu and qemu-kvm works.

After the latest update to libvirt I have been getting a weird error message when I try to run or install a new VM on multiple machines.
Unable to complete install: 'internal error process exited while connecting to monitor: char device redirected to /dev/pts/1
Could not access KVM kernel module: Permission denied
failed to initialize KVM: Permission denied
No accelerator found!
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 96, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 1943, in do_install
guest.start_install(False, meter=meter)
File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1249, in start_install
noboot)
File "/usr/lib/python2.7/site-packages/virtinst/Guest.py", line 1317, in _create_guest
dom = self.conn.createLinux(start_xml or final_xml, 0)
File "/usr/lib/python2.7/site-packages/libvirt.py", line 2722, in createLinux
if ret is None:raise libvirtError('virDomainCreateLinux() failed', conn=self)
I have hardware virtulization enabled in the BIOS on my machines, as well as the the required kernel modules loaded:
> lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
NUMA node(s): 1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 6
Stepping: 3
CPU MHz: 800.000
BogoMIPS: 4989.39
Virtualization: AMD-V
L1d cache: 64K
L1i cache: 64K
L2 cache: 1024K
NUMA node0 CPU(s): 0,1
> grep -E "(vmx|svm)" /proc/cpuinfo
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr hw_pstate npt lbrv svm_lock nrip_save
> lsmod | ack 'kvm*'
kvm_amd 52055 0
kvm 384721 1 kvm_amd
I am able to create and run VMs using qemu-kvm directly and with using aqemu-git without any issues. I am not sure if the direct cause is with Libvirt or if I am using qemu-kvm-spice from AUR (has not caused an issue before).
Last edited by vendion (2013-02-16 20:15:15)

I had the same problem, however the fix did not work for me.
Tried replacing kvm user and group with qemu (since it exists), same problem.
Reverted and created a kvm user (which did not exist and qemu-kvm package did not create), then the problem changes to
error: Unable to read from monitor: Connection reset by peer
I do not know if it is relevant but when run as root I get:
# qemu-kvm
Could not initialize SDL(No available video device) - exiting
However as the user of the current login a qemu-kvm starts with no problems.
maybe it indicates a systemd/polkit qxl/SDL driver problem or cgroups problem?
my libvirtd.conf I had set the permissions to polkit but commenting it out to get the defaults changes nothing.
a stab in the dark would predict that since systemd/polkit only allows programmes to run on the login session/seat, it is preventing the kvm/qemu user to run a programme since that user has not logged in?
so I changed the user and group in qemu.conf again but this time to root then the following error :
connecting to monitor: chardev: opening backend "pty" failed
changing it to the current session/seat login username and group:
success
On the other hand maybe it is as result of a messed up passwd or groups file causing polkit not to work correctly?
UPDATE: the problem also goes away when I remove a SDL display and then use the trusty old(archaic) VNC. so as I said, my guess is the qxl framebuffer and/or SDL is not being granted permission to use the display by polkit or PAM or systemd or whatever is supposed to be granting it permission. it can probably be fixed with a rule....
Last edited by hawkinstw (2013-03-13 23:16:18)

[SOLVED] KVM Broken After Switch from KVM to Qemu-KVM

Since I made the switch from KVM 88-1 to Qemu-KVM 0.11.0-1 yesterday, my virtual Win XP64 guest OS will not load; I just get a black screen. When I try safe mode, I can see that it is getting stuck on "acpitabl.dat."
Here's the line I've always used to start it up,
qemu-kvm -boot c -m 512 -hda win_xp.img -net nic,vlan=1 -net user,vlan=1 -localtime -k en-us -soundhw ac97 -vga std
Does anyone have any ideas? Thanks in advance.
Last edited by tony5429 (2009-11-27 05:03:43)

I see that my user was not on 'kvm' group after the switch.
When I added my user to de kvm group Qemu-KVM works like a charm.

[SOLVED] Installing Archlinux under QEMU-KVM

Hi all.
In order to kill my 8+ years old choice, I want to give Arch Linux a try.
As I daily use QEMU+KVM also to run pesky commercial OSes, I decided to use it also to test this very promising distro.
I have been trying to follow the installation guide but the istallation is failing in the latest part: GRUB2.
This in turn made my efforts useless.
Is there any "special guide/procedure" in order to intall Arch Linunx under QEMU-KVM?
TIA.
Last edited by Uqbar (2014-11-11 10:38:22)

Hi.
I am downloading latest (2014.11.01) and wil report back with details.
Thanks for listening.
[UPDATE] It worked now! It looks like I did something wrong more than once in the past. Thanks anyway.
Last edited by Uqbar (2014-11-11 10:34:27)

I have an HP2000 and it fails to boot. The HDD test passes, Run in fails at DST Short Test

My sons laptop has always had weird issues with turning off by itself, very slow graphics update, and the wifi constantly dropping out. Last night it stopped booting. I cant get it to boot with any method. I opended up the back and verified the connections are intact at the HDD and the ram. I pulled the HDD and verified it is spinning up. Put it back together and it still fails to boot or enter the diagnostics window. I left it trying to go into diagnostics and after 15 minutes nothing came up so I left it on and went to bed.
This morning it was at the diagnostic window and I ran some tests. The HDD test says that it passes all tests. When I try the run in or start up tests, it fails DST Short Test. Does this sound like a failed hard drive?
I dont have any discs with this machine, can I contact HP for back up discs. Anyone know the cost?
Thanks,

Hey,
The short Disk Self Test ( DST ) error would indicate that the Hard Drive is failing and needs to be replaced.
If your notebook is still under warranty, contact HP and arrange to have the drive replaced - you can check your warranty status Here.
If you live in the US, contact HP Here.
If you are in another part of the world, start Here.
If you are out of warranty and would like a guide on replacing the Hard Drive yourself, please let me know.
THX

[SOLVED] QEMU-KVM fails to boot if passed q35 machine type

Similar Messages

Maybe you are looking for