On Sat, Jul 11, 2015 at 9:28 AM, Ruzsinszky Attila <
ruzsinszky.att...@gmail.com> wrote:
> Hi,
>
> Do you need the exact error message (the codes)?
>
>
The error message "No system disk" means the disk is booting from a KVM
perspective so no.
> I don't want Virtio. I want to boot my image first.
I agree with Pierre.
Basically the image you have from CloneZilla has lots of settings inside it
that tell the image itself where the boot drive is.
The way I've done it in the past is to mount the image using whatever
filesystem it uses (NTFS in this case). Make sure it is writable. And then
star
- What format is the image is?
- Can you post an XML file of the VM config?
Changing the driver to VirtIO via registry edits may exacerbate the
problem. I've never done this but wouldn't it make sense to stick to the
more supported IDE drive emulation until you get it booted and thus remove
possib
y” prompt) saying what I described before.
>
>
>
> Ctrl-Alt-F1 and similar keys do nothing.
>
>
>
> *From:* Jeff Tchang [mailto:jeff.tch...@gmail.com]
> *Sent:* Friday, July 10, 2015 1:15 PM
>
> *To:* KARR, DAVID
> *Cc:* libvirt-users@redhat.com
> *Subject:* Re: [
usly
> need to get a .xsession file, but I’m not sure if the absence of that file
> implies something more “high-level”. I’m vaguely familiar with what goes
> into .xsession, although I haven’t worked with X11 for ~25 years or so.
>
>
>
> *From:* Jeff Tchang [mailto:jeff.t
ption is part of the interface for configuring
> this. What are some things I’ll have to do for this?
>
>
>
> *From:* Jeff Tchang [mailto:jeff.tch...@gmail.com]
> *Sent:* Thursday, July 09, 2015 11:21 AM
> *To:* KARR, DAVID
> *Cc:* libvirt-users@redhat.com
> *Subje
I actually find I do almost all my VM management inside the virsh command.
If the VM appears to exist inside virsh but is in a shut off state then you
should try to start it.
VNC can also be SSH port forwarded (which I have done before).
Not sure if this will help but this is the command I use to
Just thought I would share my experience trying to get the virtio windows
drivers loaded. I kept using the wrong ones and getting a blue screen until
I realized I needed to use my distribution's virtio packages. Wrote up a
quick article:
http://www.returnbooleantrue.com/2015/04/making-your-windows
