XenTools installation error for Linux
-
@krisleslie said in XenTools installation error for Linux:
So let me get this straight, I could have actually piped another command into that?
Possibly, yes.
Likely
mount /dev/cdrom /mnt | sudo ./install.sh -
mount -o ro,exec /dev/disk/by-label/XenServer\x20Tools /mnt
It fails when we point to the "DISK"
-
For the love of GOD if I wasn't happy with finding an answer that would have turned me off! Like it isn't helpful. Maybe I'm wrong but a UX engineer would be like, ummmm FIX THAT!
-
Ok so I found out the installation instructions changed for Linux after a few releases!
Installing XenServer Tools on Linux VMs
-
Select the VM in the Resources pane, right-click, and then click Install XenServer Tools on the shortcut menu. Alternatively, on the VM menu, click Install XenServer Tools.
-
Click Install XenServer Tools on the message dialog to go to the VM's console.
-
As the root user, mount the image into the VM:
mount /dev/xvdd /mnt -
Execute the installation script as the root user:
/mnt/Linux/install.sh
If the kernel has been upgraded, or the VM was upgraded from a previous version, reboot the VM now.
Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state -
-
What they say now is!
Installing XenServer Tools on Linux VMs-
Select the VM in the Resources pane, right-click, and then click Install XenServer Tools on the shortcut menu. Alternatively, on the VM menu, click Install XenServer Tools.
-
Click Install XenServer Tools on the message dialog to go to the VM's console.
-
As the root user, mount the image into the VM:
mount -o ro,exec /dev/disk/by-label/XenServer\x20Tools /mntNote: If mounting the image fails, you can locate the image by running the command
blkid -t LABEL="XenServer Tools"Execute the installation script as the root user:
/mnt/Linux/install.shUnmount the image from the guest by running the command:
umount /mnt If the kernel has been upgraded, or the VM was upgraded from a previous version, reboot the VM now.Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd(or /dev/sdd in Ubuntu 10.10 and later), rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state
-
-
Dustin one day I strive to be proficient like you and SAM
If I see ya beer's on me bro! -
@krisleslie said in XenTools installation error for Linux:
Dustin one day I strive to be proficient like you and SAM
If I see ya beer's on me bro!Ha... I wish I was nearly as proficient as SAM is. . . I squeak by.
-
@krisleslie said in XenTools installation error for Linux:
Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd(or /dev/sdd in Ubuntu 10.10 and later), rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state
This is wrong though... In the latest releases for fedora, ubuntu, and debian, for sure, it is /dev/cdrom
-
@bnrstnr said in XenTools installation error for Linux:
@scottalanmiller said in XenTools installation error for Linux:
Ubuntu fail.
This is what I get every time I mount the XS guest tools ISO on Ubuntu. Every single time...
This isnt an error
It merely states you ahve mounted a read only device, like a cd or dvd
edit: oh wait i see the first one is different. -
@bnrstnr said in XenTools installation error for Linux:
@krisleslie said in XenTools installation error for Linux:
Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd(or /dev/sdd in Ubuntu 10.10 and later), rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state
This is wrong though... In the latest releases for fedora, ubuntu, and debian, for sure, it is /dev/cdrom
Not in Xenserver. The xvd device naming is for Xen.
-
I swear just one decent UX engineer! Just one!
-
@momurda said in XenTools installation error for Linux:
@bnrstnr said in XenTools installation error for Linux:
@krisleslie said in XenTools installation error for Linux:
Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd(or /dev/sdd in Ubuntu 10.10 and later), rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state
This is wrong though... In the latest releases for fedora, ubuntu, and debian, for sure, it is /dev/cdrom
Not in Xenserver. The xvd device naming is for Xen.
Yeah. . . but that shouldn't matter here. As this mounting process is occurring within a VM. The insert operation @krisleslie did you do it from the CLI (of XenServer) or from XO?
-
@dustinb3403 SSH into it via Putty.
-
@krisleslie said in XenTools installation error for Linux:
@dustinb3403 SSH into it via Putty.
So you ran the CLI command within XS to mount the drivers into your guest?
Seems like the difficult approach. . .
-
@dustinb3403 said in XenTools installation error for Linux:
So you ran the CLI command within XS to mount the drivers into your guest?
Seems like the difficult approach. . .Semi off topic, but this is one of those things where I've seen people complain about having to enter UUID's... In the 3-4 years I've been working with XS I've never once had to enter a UUID
-
@bnrstnr said in XenTools installation error for Linux:
@dustinb3403 said in XenTools installation error for Linux:
So you ran the CLI command within XS to mount the drivers into your guest?
Seems like the difficult approach. . .Semi off topic, but this is one of those things where I've seen people complain about having to enter UUID's... In the 3-4 years I've been working with XS I've never once had to enter a UUID
I've only ever had to dig for UUID's when I hit a limit coalescing snapshots from a CR job provided by XO.
The underlying storage, or XS itself simply wasn't fast enough to complete before the next CR ran so I had to delete the parent snapshot.
-
@momurda said in XenTools installation error for Linux:
I only have a problem remembering which to use
/dev/dvd
/dev/sr0
/dev/cdrom
is different for each distro.In Fedora, you can use either
/dev/cdromor/dev/sr0because they are linked. -
@dustinb3403 Please school me brother as Linux isn't my OS of fun but I tend to prefer it over windows!
I installed the vm, putty'd in because I thought that was the right thing! If I did it from the Xen Console I was greeted with the menu for the app and how to navigate to the IP's for it.
-
@krisleslie said in XenTools installation error for Linux:
@dustinb3403 Please school me brother as Linux isn't my OS of fun but I tend to prefer it over windows!
I installed the vm, putty'd in because I thought that was the right thing! If I did it from the Xen Console I was greeted with the menu for the app and how to navigate to the IP's for it.
I would've simply accessed the VM from my XO installation, "installed the xstools", opened the console or SSH'd to the VM and then mounted and installed the drivers into the VM.
The approach you took (at least it appears) is you ssh'd to your XenServer installation, mounted the drivers to your VM by UUID and then went to install them.
-
I did try to just install Xen Tools like I would normally do the windows version, by right clicking on the vm and Install the tools. But when that didn't do anything on screen, that's what raised a flag like oh shit I need to do something CLI.
Had it been something on screen to tell me or better guide me
it would have been a smoother experience. Hence me saying, a UX Engineer needs to be around!
