similar to: pygrub error booting iso

I am trying to install CentOS from an ISO image file but the installer does not see a CD-ROM drive. The VNC viewer works but the CentOS installer indicates "Unable to find any devices of the type needed for this installation type." Then it prompts with "[Select driver] [Use a driver disk] [Back]". I have tried several variations of the "disk" paramater, all

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

I am running a Debian Squeeze Xen 4.0.1 Hypervisor and 2.6.32-5-xen-amd64 dom0. My xen-tools.conf: lvm = vg00 size = 100Gb # Disk image size. memory = 2048Mb # Memory size swap = 2G # Swap size # noswap = 1 # Don''t use swap at all for the new system. fs = ext4 # use the EXT3 filesystem for the disk image. dist = `xt-guess-suite-and-mirror --suite` # Default

Hi libvirt 5.2.0 should support maxGrantFrames setting for xen (changelog). I get ever an error if I use it in the config: <domain type='xen'> <name>satan.chao5.int</name> <uuid>f1f96b1c-fb75-4707-afb7-604d696d29cc</uuid> <memory unit='KiB'>3145728</memory> <currentMemory unit='KiB'>3145728</currentMemory>

I''m running the 2.6.31.6 pv_ops dom0 kernel, libvirt 0.7.0 and Xen 3.4.1. When I try connecting to the Xen hypervisor using virsh it gives me a "Connection refused": root@grp-01-23-02:~# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 1020 4 r----- 858.3 root@grp-01-23-02:~# virsh -c

Hi Is there any docs, howtos, etc, if i am installed eg. CentOS 5 to as domU as fully virtualized and now i am wanting to use it PV drivers. Any help how migration can be done? Terveisin/Regards, Pekka Panula, Net Servant Oy - A Sofor company pekka.panula@sofor.fi _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Confirmed this issue. To reproduce: Install a fresh Wheezy AMD64 guest under Xen 4.1 (hypervirtualized, boot from the debian-7.1.0-amd64-CD-1.iso). Use "entire disk" automatic layout for partitioning, this creates /dev/xvda1 for / and /dev/xvda5 for swap. It will create /boot/grub/grub.cfg with many references to (/dev/xvda,msdos1) which works fine when the machine is booted

I''ve got a CentOS 5.3 dom0 with Xen 3.4.1-rc5 (or so). I''ve tried the same stuff below with 3.4.0, no difference. I''m trying to install 2009.06 PV domU based on instructions from [1] and [2]. I can run the install fine, I can also get the kernel and boot archive (from [2]) after the install. But for the life of me I can''t get the installed domU to boot. If I

All, I have successfully installed CentOS 7 on a PV environment, and have been trying to see if I can can get a CentOS 8 install running. Hardware does not support virtualization extensions, hence the PV environment and I cant do HVM for the install then migrate. My understanding is that PV support is in the kernel, and that the distro of Linux shouldn't technically matter. But currently

I''m trying to add extra zvols to a Solaris10 DomU, sv_113 Dom0 I can use virsh attach-disk <name> <zvol> hdb --device phy to attach the zvol as c0d1. Replacing hdb by hdd gives me c1d1 but then that is it. Being able to attach several more zvols would be nice but even being able to get at c1d0 would be useful Am I missing something or can I only attach to hda/hdb/hdd?

Hi, In general, PV tends not to be supported in newer distribution releases. This is mostly due to HVM performance and flexibility nowadays, which just was not the case back in the days when PV ruled. I am curious why you are trying PV. -yoctozepto On Sat, Sep 19, 2020 at 6:41 PM 9f9dcad3f78905b03201--- via CentOS-virt <centos-virt at centos.org> wrote: > > All, > > Just

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

Hi, Ive just tried Xen 4.0 on Gentoo with 2.6.32 (also tried 2.6.31) forward ported dom0 kernel, Xen itself seems to boot up successfully and everything else on the system is working normally, but when I try to start a domain xm create appears to hang and eventually I get a hotplug scripts error: Error: Device 2049 (vbd) could not be connected. /etc/xen/scripts/block failed; error detected.

I setup postfix/dovecot on a new machine and now all works well with the small exception of dovecot triggering selinux avc denials on some temp... files here is a sample alert: Summary SELinux is preventing /usr/libexec/dovecot/deliver (dovecot_deliver_t) "link" to temp.localhost.678.40caaf5592891c46 (user_home_dir_t). Detailed Description SELinux denied access requested

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hello, I must be missing something very very basic. Because I am having trouble launching some vm''s that I recently built whereas I don''t have any problem at all launching some older images I made in very much the same way! First there is vm01 which works just fine: [root@lcent5-1:/etc/xen]$:xm create vm01 Using config file "./vm01". Started domain vm01

Hi all, I''ve got xen-4.1.1 running with linux-3.0.0-rc5 and am trying to start my first guest, f14-x86_64, which does boot on bare metal. The configs below show kernel, ramdisk, and disk assignments for the virtual machine. They also show that the virtual machine uses the target disk devices. The last section shows part of the boot sequence starting with the disk assignments,

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hi I am having some problems installing a paravirt RHEL guest on a deb amd64 xen machine uname -a = Linux debxen 2.6.20-1-xen-amd64 #1 SMP Tue Apr 24 22:23:22 UTC 2007 x86_64 GNU/Linux ============== xm info ============== host : debxen release : 2.6.20-1-xen-amd64 version : #1 SMP Tue Apr 24 22:23:22 UTC 2007 machine : x86_64

Dear *, I''m more used to work with RedHat like OSes. Still, I did not denied the request from a user who wants a domU based on ubunto. I usually use virt-install to do the job, with a script similar to this one: #!/bin/sh BASE=SL-4.7-i386-pv \ virt-install --nographics \ --nonsparse \ --paravirt \ --noreboot \