Having a problem, have built some VM's and importet some from JumpBox, but they will not boot from the HD. I am using files for the HDs mixture of ".img" and ".vmdk". I can boot and build from the network and CD/ISO, but after the installation completes it reboots attempts to boot from the HD and nothing happends. No error message is displayed.
Has any one come across this ?
I have been FRUSTRATINGLY trying to upgrade to 10.04 because I was impressed with it, however, as I have predicted, it was a headache. In all actuality, it is WORSE than a headache. Both my desktop and laptop are now decommissioned, (I have Windows 7 on the 2nd laptop, and since Ubuntu/GRUB hasn't installed completely, it won't boot--I have to fix that TOO) leaving me to depend on an old Pentium III in the closet to download and burn CD images, which is STILL failing. Unfortunately, I have burned 9.10 on a rewritable CD, which I erased long ago. I have NO computer now, other than the old Pentium III which was sitting in a closet. I am tired and want to go to sleep, but I am the kind of person who finishes things that were started.
My problem is that I have downloaded (and burned to a CD) Ubuntu 10.04 TWICE, because it's failed to install. I thought that the ISO was corrupted, so I downloaded it and installed it AGAIN. Same thing. I tried making a Live USB Flashdrive install--same old, same old. It's 12:00 MIDNIGHT (Pacific time) and I can't bear to stay up this long like some of you young ones can. Thank goodness for caffeine
I KNEW that I shouldn't have done this, but I went ahead and proceeded to "upgrade". Well, the actual upgrade (thru Ubuntu Update tool) failed, so I decided to do a clean install. Thought that the process, from start to finish, would take 30-40 minutes, but was I wrong! I have been stuck with this issue since 7 P.M.!
Well, to cut to the chase, is anyone else having issues with burning/installing from their own CDs? This Pentium III is only running Fedora Core 6 with 512MB of memory, so it can get a download/burn job done OK. I am using the K3b burner in Fedora and no errors regarding a corrupted ISO appear. Why then, won't it install, after downloading and burning two separate ISOs?
I'm running Fedora x86_64. I need to setup a virtual machine to do some work on ARM platform. Thus, I've installed QEMU.
Code:
qemu --version
QEMU emulator version 0.13.0 (qemu-kvm-0.13.0), Copyright (c) 2003-2008 Fabrice Bellard
Then, I have dowloaded an ISO image of Debian 6.0 armel.Following instructions on official wiki, I have first created an empty disk image,
Code:
qemu-img create -f qcow debian-armel.img 650M
then I have attempted to boot from ISO image;
Code:
qemu -m 512 -hda debian-armel.img -cdrom debian-6.0.1a-armel-CD-1.iso -boot d
Boot process hangs with the message:
Code:
Booting from cdrom...
639 medium detected
Boot failed: Could not read from CDROM (code 0004)
No bootable device
link refers to Fedora 12, but it seems still unresolved...
I've just installed Ubuntu server 10.04 and have set up vsftpd somewhat successfully. I can connect as my root user, and I only have access to my home directory. However, whenever I try to copy a file across a file I receive a 550 Permission denied error.
I've run the command ls -l /home/directory and the result returned is total 0, when I was expecting details of permissions per user. I've tried running chmod -w /home/directory but this doesn't return any result nor change the result of the above ls command.
When I try this yum install kvm qemu libvirt python-virtinst qemu-kvm I become this error
Transaction Check Error: file /usr/share/man/man1/qemu-img.1.gz from install of qemu-img-0.10.5-1.el5.2.x86_64 conflicts with file from package kvm-qemu-img-83-164.el5_5.25.x86_64
how can I resolve this error
qemu-img , create any imagerun qemu -fda bootdiskwin98se.img -hda image.imgand No drive C what's going wrong with qemu-img/qemu?
View 3 Replies View RelatedI posted this over in the VirtualBox forums but was directed to the debian forums as it was the debian fork.VBoxManage and all virtualbox GUI elements are black with white text ("night mode" in other apps) with no borders or other useful Gui bits. Apparently the board image quota is reached (?) but you can see it here: URL...All the guests work, it's just this GUI issue.
Code: Select allii virtualbox 4.3.30-dfsg-1+deb8u1 amd64 x86 virtualization solution - base binaries
rc virtualbox-4.3 4.3.30-101610~Debian~wheezy amd64 Oracle VM VirtualBox
ii virtualbox-dkms 4.3.30-dfsg-1+deb8u1 all x86 virtualization solution - kernel module sources for dkms
ii virtualbox-qt 4.3.30-dfsg-1+deb8u1 amd64 x86 virtualization solution - Qt based user interface
vbox-install log on other board,I upgraded from Debian 7 stable to Debian 8 stable. I haven't used virtualbox in a long time, so maybe I somehow did this myself, but I'm not sure where that is if I did.
I couldn't find anything else in /var/log that would be useful. It's across all users. I checked the launch scripts /usr/bin/virtualbox, /usr/bin/ vbox manage, and /var/lib/virtualbox/*
I tried virt-manager 0.8.0-7 or 0.8.1-1, my guest like fedora 12 i386, ubuntu i686, win xp do not have any sound even they detect the driver(es1370 or ac97) correctly. I doubt it is because of the pulseaudio and the qemu's user. Qemu uses not my user, it uses qemu user.
If I uses qemu-kvm directly, it has sound and work fine.
I'm still having the problem described in this thread (F15 + VirtualBox + USB Extension doesn't work). Does anyone else have this problem, or solutions to it?
http://forums.fedoraforum.org/showthread.php?t=263400
I have a working Windows XP VM hosted by Fedora 15, except for the USB support. code...
After updating to kernel-2.6.33.6-147.fc13.x86_64 (and updating all kmods) VirtualBox guests no longer boot.
I had a Windows guest (from now on refereed as Crapdows) that worked normally. After the update, I could get to the "Start Windows Normally" screen, but then Crapdows refused to boot. At first, I thought it was a crappy M$ bug, but after creating another VM (Doublecrap), and starting from scratch, I was able to get to the "Windows is loading files" screen, and then the guest hangs again.
This problem is generalized to all OS'es I've tried. In Ubuntu, I can get to the language selection screen before the installation freezes. The same applies for Fedora and SUSE guests.
Is it time to get my hammer?
I'm aware of the issues of the ACPI that Toshiba laptops have...
Unfortunately I found out after I bought the laptop.
Auto-boot initiates, and then the screen freezes with this text:
The Karmic installers for ARM CPUs are .img files that are meant to be written directly to Flash media, rather than .iso files that are meant to be burned to CD.
I'd like to run the ARM port of Karmic under the QEMU hardware emulator. This should be possible, because the .img files are sector-for-sector images of a hard disk drive. But when I try, I get a panic because the kernel can't mount the root filesystem.
I think the problem is that hard drives are provided by QEMU by emulating an IDE controller, whereas the ARM .image files are meant to be run from a USB stick. Those are accessed via SCSI rather than IDE.
Perhaps my problem is that the kernel I'm using with QEMU doesn't contain an IDE controller. It appears that QEMU doesn't provide a SCSI emulation, just IDE. An alternative would be to convert the .img installer file to a bootable CD-ROM image. Is there a way I can do that? Here is my command line:
Code:
$ qemu-system-arm -M versatilepb -kernel ~/Documents/Kernels/ARM/vmlinuz-2.6.28-versatile -hda ubuntu-9.10-desktop-armel+dove.img -m 256M -append "root=/dev/sda1 rw"
It doesn't work to say "root=/dev/hda1 rw" - it still can't find the root filesystem.
I just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.
What can I do?
I've just updated my desktop to F13 using preupgrade but now grub won't boot it. The upgrade seemed to go OK, and none of the disk partitions should have changed as far as I'm aware, but now I get an error
VFS: Cannot open root device "UUID=xxx" or unknown block(0,0).
I'm new to these forums. I'm coming from using Ubuntu for a couple of years and now I'm trying to switch to Fedora.
I installed F10 yesterday and all went well, more or less. The system used to freeze randomly but after updating, everything seemed to work fine (I haven't tried audio yet, though).
I have an X1250 integrated graphics system that's working fine in Ubuntu. After playing around with F10 for a while I decided to download and install the latest ATI drivers from AMD's site. The installation posed no problems, but when I reboot the system it will come to a black screen at some point and freeze there.
I searched the web a little and came to this: http://www.fedorafaq.org/#radeon, but I'm not sure if that's current or old news. If it's current and those ATI drivers can't be installed, I'd appreciate some help about removing them.
I have recently updated my Fedora 11 installation which replaced my older 167 kernel with the newer 217 kernel. However, the 217 kernel will not boot completely. It will show the splash loading screen, and then will switch to a rapidly blinking cursor. This cursor blinks for about 5 seconds and then disappears. I can access terminals using ALT+F2, etc. I can log in to these terminals, but init commands do not complete (something about a binary handler). I'm not sure if something is conflicting with an update to X or what is wrong. The most recent kernel that I managed to get to work was Kernel 167, however I cannot find this kernel for download.
Sys info:
AMD Athlon 64 X2 4800+
3GB RAM
nVidia GeForce 8600GT with proprietary drivers
320GB Hard Disk with windows and linux partitions
Fedora 11 32-bit i586
I am a linux newbie.
I had dual boot fedora 9 with windows XP before. Now I decided to change to fedora 11. I choose the option Replace existing linux while installing the fedora 11. My windows used to be in C drive while my linus in D drive. So I thought it would replace the D drive and remain dual boot.
However, after I reboot the computer, I realize that it can only boot linux. My windows partition appear as a File System in linux. code...
I just recently notice that my Fedora 13 is randomly stop at boot. This is a fresh install less than a week and with all the updated kernel and software as of today. I could not get much information from /var/log/messages (only about 3 lines at the time it froze).
It froze straight after it finishes the boot sequence. I can see a mouse cursor but that's about it. The last init sequence I could see before going to X was "atd" (if that helps at all)
This install is on a single Seagate 1.5TB drive without any other drives attached to the system (I rule out if that's problem with the other hard drives)
on Gigabyte P35DS3 mobo on ICH9 port
the mobo has AHCI mode for the hard drive
I got some bad sector on the hard drive (40 sectors)
For some reason, it kept stopping when I cold boot. Once it stop and I press the reset button it normally works.
I found another forum mentioning it can be issue with the video driver. So I here's further information of my system code...
I have a windows and a linux box running DHCP respectively. The problem is whenever my client system boots up, it fetches the dynamic IP from the windows box. What should I do in order for my Linux box to provide dynamic IP's to clients? Both servers are in a single network. connected via switch.
View 1 Replies View RelatedFC13
When rebooting and in Boot Selection Menu , the Arrow keys won't go down through kernel selections. They just won't move.
Is this a Linux or CMOS problem ?
After patiently waiting for 30+ hours during install attempts with the "Virtual Machine Manager", I realized that it wasn't going to happen. So then I read about a possibly working version, qemu-kvm How to use this to get a VM install up and going ? For instance, this command appears to begin an install, but where does it actually create a vm image from that?
qemu-kvm -m 512 -cdrom /iso/Fedora-14-i386-DVD.iso
I've burned the installation media on several different types of media, and i'm getting an error after the 3 bars load (first screen). I've tried the verify and boot option, and it's fine. I'm trying Fedora 10 on a studio xps 1340. The error messageet isCE hpet increasing min_delta_ns to xxxxx nsec twice, thenForce XPAon: 0about 15 times, thenCE hpet increasing min_delta_ns to xxxxx nsec a few more times, this pattern alternates and the xxxxx keeps increasing, starting at something like 10000 and jumping by 50000 each time it reposts.
View 14 Replies View RelatedI am trying to convert my VirtualBox hard drives (.vdi) to VMware Workstation format (.vmdk). I found this link [URL] but cannot find the path for qemu-img. I downloaded Qemu Manager v7.0 from [URL]. Please disregard. I found it.
C:Program Files (x86)QemuManagerqemuqemu-img
I'm running a Windows 7 guest using Virtual Machine Manager to launch my "console" to the VM. I believe it uses VNC to connect to the console. I'd like to have clipboard synchronization so I can copy from the host and paste to the guest.
View 1 Replies View RelatedI just install QEMU and virtual machine manager to use virtualization, but virt-manager cannot run properly. I can create a VM, then mount CDROM ISO, startup. With Windows installation, it runs well until format partition step, after that it is disconected and exit with error related to VNC. I dont know why have this problem cause the packages that I installed is from Fedora repo and I think they have been tested.
Here are some infos:
Fedora 14 - kernel 2.6.35.6-45.fc14.i686.PAE
qemu-2:0.13.0-0.7.rc1.fc14.i686
libvirt-0.8.3-2.fc14.i686
virt-manager-0.8.5-1.fc14.noarch
Anyone familiar with QEMU? I'm attempting to load F15 for testing purposes along with REL 6. This is what happens, all goes well until it is actually starts downloading files to the virtual disk which appears to work until it gets to about 1/2 way completed, then it hard crashes(actually shuts the machine down). Also I had to turn of ACPI because when it is enabled it just hangs the VM altogether. I'm wondering if I should also turn off APIC?
Is there some way of loading a VM in verbose mode or debug mode to see what is happening and maybe causing this hard crash. The log files for QEMU shows nothing other then the normal loading of the virtual machine, its given name, source ISO and things of that nature.
I am facing some strange problem as using 2 nic's on kvm child vm. Secondary interface eth1 is not working on vm but eth0 is working , i am using routing mode, here below details.Platform --> Fedora 13 (for both KVM host and child vm)Start VM using 2 nics support using below command.
/usr/bin/qemu-kvm -M pc -m 256 -smp 1 -name myguest1 -uuid
5dcb91e1 -nographic -monitor
unix:/var/lib/libvirt/qemu/myguest1.monitor,server,nowait -boot c -drive
[code]....
Has anyone seen this error in libvirtd?libvir: QEMU error : out of memoryWhatever it is, I'm pretty sure that's what's keeping my virt-manager from working. There's 12GB of DDR3 on this box, so I really really hope that it's not actually a memory problem. This here is a brand-new whitebox I build just for virtualization on F11. Can anyone here help me make it work?
Edit: This is a 64-bit install. All 12GB are accessible by the OS.
Is anyone familiar with how to correct a glitch with Qemu-KVM that prevents virtual machines (Windows Server guests) from starting after the Linux host has been rebooted? It gives an error constructing a domain in /dev/sr0 because of /usr/share/virt-manager/virtManager/engine.py line 493 [run_domain vm_startup], /usr/share/virt-manager/virtManager/domain.py line 573 [startup self.vm create()] and /usr/lib/python2.6/site-packages/libvirt.py line 287 [create if ret=-1 raise libvirtError].
View 1 Replies View RelatedAfter install glibc-2.10.1-4 (x86_64) package, i couldn't run the qemu-kvm anymore.
SELinux is preventing qemu-kvm (svirt_t) "setrlimit" svirt_t.
SELinux prevented pt_chown from using the terminal 0.